Merge pull request #301126 from MicrosoftDocs/main

6/10/2025 AM Publish

Author: Taojunshen

articles/api-management/send-one-way-request-policy.md

@@ -89,6 +89,6 @@ This example uses the `send-one-way-request` policy to send a message to a Slack
 
 ## Related policies
 
-* [Intergration and external communication](api-management-policies.md#integration-and-external-communication)
+* [Integration and external communication](api-management-policies.md#integration-and-external-communication)
 
 [!INCLUDE [api-management-policy-ref-next-steps](../../includes/api-management-policy-ref-next-steps.md)]

articles/app-service/overview-ai-integration.md

@@ -5,7 +5,7 @@ author: cephalin
 ms.author: cephalin
 ms.service: azure-app-service
 ms.topic: overview
-ms.date: 05/17/2025
+ms.date: 06/06/2025
 ms.custom:
   - build-2025
 ---
@@ -14,7 +14,7 @@ ms.custom:
 
 This article guides you to language-specific tutorials and resources to help you build intelligent applications with App Service.
 
-Azure App Service makes it easy to integrate AI capabilities into your web applications across multiple programming languages and frameworks. Whether you want to use powerful Azure OpenAI models, deploy local small language models (SLMs) directly with your apps, or implement advanced patterns like retrieval augmented generation (RAG), App Service provides the flexible, secure platform you need for AI-powered applications.
+Azure App Service makes it easy to integrate AI capabilities into your web applications across multiple programming languages and frameworks. Whether you want to use powerful Azure OpenAI models, deploy local small language models (SLMs) directly with your apps, host Model Context Protocol (MCP) servers or implement advanced patterns like retrieval augmented generation (RAG), App Service provides the flexible, secure platform you need for AI-powered applications.
 
 App Service offers several advantages for developing and deploying AI-powered applications:
 
@@ -62,6 +62,16 @@ Implement AI capabilities in your Python web applications:
 - [Run a chatbot with a local SLM (FastAPI)](tutorial-ai-slm-fastapi.md) - Deploy a FastAPI application with a local SLM sidecar.
 - [Azure AI Foundry tutorial: Deploy an enterprise chat web app](/azure/ai-foundry/tutorials/deploy-chat-web-app?toc=/azure/app-service/toc.json&bc=/azure/bread/toc.json) - Deploy fully integrated AI web app straight from your deployment in Azure AI Foundry. 
 
+## Model Context Protocol (MCP) servers
+
+Host [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) in your web applications:
+
+- [Host a .NET MCP server on Azure App Service](https://github.com/Azure-Samples/remote-mcp-webapp-dotnet) - Deploy an MCP server with .NET.
+- [Host a Node.js MCP server on Azure App Service](https://github.com/Azure-Samples/remote-mcp-webapp-node) - Deploy an MCP server with Node.js.
+- [Host a Python MCP server on Azure App Service](https://github.com/Azure-Samples/remote-mcp-webapp-python) - Deploy an MCP server with Python.
+- [Host a Pyton MCP server with key-based authorization on Azure App Service](https://github.com/Azure-Samples/remote-mcp-webapp-python-auth) - Deploy an MCP server with Python and key-based authorization.
+- [Host a Pyton MCP server with OAuth 2.0 authorization on Azure App Service](https://github.com/Azure-Samples/remote-mcp-webapp-python-auth-oauth) - Deploy an MCP server with Python and [Open Authorization (OAuth) 2.0 authorization with Micrososft Entra ID](/entra/architecture/auth-oauth2).
+
 ## More resources
 
 - [Azure OpenAI Service documentation](/azure/ai-services/openai/)

articles/automation/automation-child-runbooks.md

@@ -42,16 +42,18 @@ The parameters of a child runbook called inline can be of any data type, includi
 Currently, PowerShell 5.1 is supported and only certain runbook types can call each other:
 
 * A [PowerShell runbook](automation-runbook-types.md#powershell-runbooks) and a [graphical runbook](automation-runbook-types.md#graphical-runbooks) can call each other inline, because both are PowerShell based.
-* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) and a graphical PowerShell Workflow runbook can call each other inline, because both are PowerShell Workflow based.
+* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) can call another PowerShell Workflow runbook inline.
 * The PowerShell types and the PowerShell Workflow types can't call each other inline. They must use `Start-AzAutomationRunbook`.
 
 > [!IMPORTANT]
-> Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2 
+  > * Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 and PowerShell 7.2 
   **Workaround**: Use `Start-AutomationRunbook` ([internal cmdlet](/azure/automation/shared-resources/modules#internal-cmdlets)) or `Start-AzAutomationRunbook` (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) to start another runbook from parent runbook.
+  > * Executing child scripts using Graphical PowerShell Workflow runbooks is not supported.
+  **Workaround**: Use Start-AzAutomationRunbook (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) from within the parent runbook (via an InlineScript block) to start another runbook.
 
-The publish order of runbooks matters only for PowerShell Workflow and graphical PowerShell Workflow runbooks.
+The publish order of runbooks matters only for PowerShell Workflow runbooks.
 
-When your runbook calls a graphical or PowerShell Workflow child runbook by using inline execution, it uses the name of the runbook. The name must start with `.\\` to specify that the script is in the local directory.
+When your runbook calls a PowerShell Workflow child runbook by using inline execution, it uses the name of the runbook. The name must start with `.\\` to specify that the script is in the local directory.
 
 ### Example
 

articles/automation/troubleshoot/runbooks.md

@@ -11,6 +11,41 @@ ms.custom: has-adal-ref, devx-track-azurepowershell
 
  This article describes runbook issues that might occur and how to resolve them. For general information, see [Runbook execution in Azure Automation](../automation-runbook-execution.md).
 
+## Graphical PowerShell Workflow runbooks with child runbooks fail to execute
+
+### Issue
+Graphical PowerShell Workflow runbooks with child runbooks fail to execute as expected.
+
+### Cause
+To improve the security posture of Graphical PowerShell Workflow runbooks, the service no longer executes Graphical PowerShell Workflow runbooks with child scripts.
+
+### Resolution
+
+Workaround is to use Start-AzAutomationRunbook (from [Az.Automation module](/powershell/module/Az.Automation/Start-AzAutomationRunbook)) from within the parent runbook to start child runbook. For example, use the InlineScript block:
+
+```
+
+$job = Start-AzAutomationRunbook `
+
+    -AutomationAccountName "MyAccount" `
+
+    -ResourceGroupName "MyRG" `
+
+    -Name "ReusableTaskRunbook" `
+
+    -Parameters @{ TaskId = '1234' }
+
+ 
+
+#Optional: Wait for job completion
+
+do {
+
+    Start-Sleep -Seconds 5
+
+    $jobStatus = Get-AzAutomationJob -Id $job.Id -AutomationAccountName "MyAccount" -ResourceGroupName "MyRG"} while ($jobStatus.Status -ne "Completed")
+
+```
 
 ## It is no longer possible to use cmdlets from imported non-default modules in graphical PowerShell runbooks
 

articles/azure-functions/flex-consumption-plan.md

@@ -147,6 +147,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
 + **Triggers**: While all triggers are fully supported in a Flex Consumption plan, the Blob storage trigger only supports the [Event Grid source](./functions-event-grid-blob-trigger.md). Non-C# function apps must use version `[4.0.0, 5.0.0)` of the [extension bundle](./extension-bundles.md), or a later version. 
 + **Regions**: Not all regions are currently supported. To learn more, see [View currently supported regions](flex-consumption-how-to.md#view-currently-supported-regions).
 + **Deployments**: Deployment slots aren't currently supported.
++ **Proxies**: Functions Proxies aren't supported. Consider integrating your function apps with Azure API Management.
 + **Scale**: The lowest maximum scale is currently `40`. The highest currently supported value is `1000`. 
 + **Managed dependencies**: [Managed dependencies in PowerShell](functions-reference-powershell.md#managed-dependencies-feature) aren't supported by Flex Consumption. You must instead [upload modules with app content](functions-reference-powershell.md#including-modules-in-app-content).
 + **Diagnostic settings**: Diagnostic settings aren't currently supported.

articles/azure-health-insights/radiology-insights/TOC.yml

@@ -80,8 +80,8 @@ items:
            href: /java/api/overview/azure/health-insights-radiologyinsights-readme
          - name: Python
            href: /python/api/overview/azure/healthinsights-radiologyinsights-readme
-#         still being finalized- name: JavaScript
-#           href: /javascript/api/overview/azure/health-insights-radiologyinsights-rest-readme
+         - name: JavaScript
+           href: /javascript/api/overview/azure/health-insights-radiologyinsights-rest-readme?view=azure-node-latest
 - name: Resources
   items:
      - name: FAQ

articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md

@@ -148,13 +148,6 @@ You need to assign a public switched telephone network (PSTN) number to your Res
 
 1. Also, if you plan to make outbound PSTN calls using your Resource Accounts assigned phone number, now is a good time to assign a [Microsoft Teams Calling Plan](/microsoftteams/calling-plans-for-office-365).
 
-### CCaaS Developer: Configure Call Automation to use preproduction environment 
-
-Use the following code snippet in C# to set use of preproduction environment for Teams Phone extensibility. The Next-PMA preprod environment has the latest code base and bug fixes. 
-
-```csharp
-CallAutomationClient callAutomationClient = new CallAutomationClient(new Uri("https://nextpma.plat.skype.com:6448"), acsConnectionString); 
-```
 
 ### CCaaS Developer: Get Resource Account Information
 

articles/confidential-computing/create-confidential-vm-from-compute-gallery.md

@@ -30,7 +30,7 @@ The resulting image version can be used only to create confidential VMs.
 This image version can be replicated within the source region **but cannot be replicated to a different region** or across subscriptions currently.
 
 > [!NOTE]
-> If you want to create an image from a Windows confidential VM that has confidential compute disk encryption enabled with a platform-managed key or a customer-managed key, you can only create a specialized image. This limitation exists because the generalization tool (**sysprep**), might not be able to generalized the encrypted image source. This limitation applies to the OS disk, which is implicitly created along with the Windows confidential VM, and the snapshot created from this OS disk.
+> If you want to create an image from a Windows confidential VM that has confidential compute disk encryption enabled with a platform-managed key or a customer-managed key, you can create a specialized or generalized image.
 
 ### Create a Confidential VM type image using Confidential VM capture
 

articles/container-apps/includes/java-get-started-introduction-and-prerequisites-and-install-azure-container-apps-cli-extension.md

@@ -19,7 +19,7 @@ By the end of this tutorial, you deploy a web application that you can manage th
 
 ## Prerequisites
 
-- An Azure subscription. [Create one for free.](https://azure.microsoft.com/free/).
+- An Azure subscription. [Create one for free](https://azure.microsoft.com/free/).
 - The `Contributor` or `Owner` permission on the Azure subscription. For more information, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml?tabs=current).
 - [A GitHub account](https://github.com/join).
 - [Git](https://git-scm.com/downloads)

articles/nat-gateway/nat-availability-zones.md

@@ -58,7 +58,7 @@ A zonal promise for zone isolation scenarios exists when a virtual machine insta
 *Figure 3: Zonal isolation by creating zonal stacks with the same zone NAT gateway, public IPs, and virtual machines provide the best method of ensuring zone resiliency against outages.*
 
 > [!NOTE]
-> Creating zonal stacks for each availability zone within a region is the most effective method for building zone-resiliency against outages for NAT gateway. However, ths configuration only safeguards the remaining availability zones where the outage did **not** take place. With this configuration, failure of outbound connectivity from a zone outage is isolated to the specific zone affected. The outage won't affect the other zonal stacks where other NAT gateways are deployed with their own subnets and zonal public IPs. 
+> Creating zonal stacks for each availability zone within a region is the most effective method for building zone-resiliency against outages for NAT gateway. However, this configuration only safeguards the remaining availability zones where the outage did **not** take place. With this configuration, failure of outbound connectivity from a zone outage is isolated to the specific zone affected. The outage won't affect the other zonal stacks where other NAT gateways are deployed with their own subnets and zonal public IPs. 
 
 ### Integration of inbound with a standard load balancer