Fix Container Apps sessions doc warnings

Author: jeffwmartinez

articles/container-apps/sessions-custom-container.md

@@ -55,7 +55,7 @@ Session pools support **Liveness** and **Startup** probe types. For more informa
 
 When you create or update a session pool, specify probes in the `properties.customContainerTemplate.containers` section of your request payload.
 
-For the full API specification, see [SessionPools API](/rest/api/resource-manager/containerapps/container-apps-session-pools/create-or-update?view=rest-resource-manager-containerapps-2025-07-01&tabs=HTTP).
+For the full API specification, see [SessionPools API](/rest/api/resource-manager/containerapps/container-apps-session-pools/create-or-update?view=rest-resource-manager-containerapps-2025-07-01&tabs=HTTP&preserve-view=true).
 
 #### Example
 
@@ -101,7 +101,7 @@ For the full API specification, see [SessionPools API](/rest/api/resource-manage
 
 If your session pool isn't maintaining the expected number of healthy `readySessionInstances`, consider the following:
 
-1. **Check container logs** - Review session container logs to identify issues with probe endpoints or container startup. See [View logs for custom container session pools](../code-interpreter/bring-your-own-code-interpreter/tutorials/custom-container-logs.md).
+1. **Check container logs** - Review session container logs to identify issues with probe endpoints or container startup. See [View logs for custom container session pools](troubleshooting.md#view-logs).
 2. **Verify probe configuration** - Ensure probe paths, ports, and thresholds are configured correctly for your application.
 3. **Review container health** - Check for issues inside your container that prevent probe endpoints from responding successfully.
 

articles/container-apps/sessions-tutorial-shell-mcp.md

@@ -133,58 +133,12 @@ Deploy a session pool by using an ARM template with the MCP server enabled.
 
 1. Deploy the template:
 
-## Create a shell session pool with MCP server
-
-Use an ARM template to create a shell session pool with MCP server enabled.
-
-1. Create a deployment template file named `deploy.json`:
-
-   ```json
-   {
-       "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
-       "contentVersion": "1.0.0.0",
-       "parameters": {
-           "name": { "type": "String" },
-           "location": { "type": "String" }
-       },
-       "resources": [
-             {
-               "type": "Microsoft.App/sessionPools",
-               "apiVersion": "2025-10-02-preview",
-               "name": "[parameters('name')]",
-               "location": "[parameters('location')]",
-               "properties": {
-                   "poolManagementType": "Dynamic",
-                   "containerType": "Shell", # Set the "containerType" property to "Shell"
-                   "scaleConfiguration": {
-                       "maxConcurrentSessions": 5
-                   },
-                   "sessionNetworkConfiguration": {
-                       "status": "EgressEnabled"
-                   },
-                   "dynamicPoolConfiguration": {
-                       "lifecycleConfiguration": {
-                           "lifecycleType": "Timed",
-                           "coolDownPeriodInSeconds": 300
-                       }
-                   },
-                   "mcpServerSettings": { 
-                       "isMCPServerEnabled": true # Add the "mcpServerSettings" section to enable the MCP server
-                   }
-               }
-           }
-       ]
-   }
-   ```
-
-2. Deploy the ARM template.
-
-   ```azurecli
-   az deployment group create \
-     --resource-group $RESOURCE_GROUP \
-     --template-file deploy.json \
-     --parameters name=$SESSION_POOL_NAME location=$LOCATION
-   ```
+    ```azurecli
+    az deployment group create \
+      --resource-group $RESOURCE_GROUP \
+      --template-file deploy.json \
+      --parameters name=$SESSION_POOL_NAME location=$LOCATION
+    ```
 
 ## Get the MCP server endpoint