Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us423405-01

Author: TimShererWithAquent

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/private-multi-access-edge-compute-mec/index.yml",
+      "redirect_url": "/previous-versions/azure/private-multi-access-edge-compute-mec/index",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/network-watcher/traffic-analytics-schema-update.md",
       "redirect_url": "/previous-versions/azure/network-watcher/traffic-analytics-schema-update",

articles/api-management/api-management-region-availability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 04/29/2025
+ms.date: 05/28/2025
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -47,12 +47,10 @@ Information in the following table is updated regularly. Capacity availability i
 | Switzerland North | ✅ |✅ |  | |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
-| West Europe  | ✅ | ✅ | | ✅<sup>1</sup> |
+| West Europe  | ✅ | ✅ | | ✅ |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 
-<sup>1</sup> Request access to this region by emailing `[email protected]` 
-
 ## Related content
 
 Learn more about:

articles/app-service/includes/quickstart-java/quickstart-java-javase.md

@@ -205,7 +205,7 @@ With all the configuration ready in your [pom.xml](https://github.com/Azure-Samp
     Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When the deployment completes, you see the following output:
 
     ```output
-    [INFO] Successfully deployed the artifact to https://<app-name>.azurewebsites.net
+    [INFO] Successfully deployed the artifact to <URL>
     [INFO] ------------------------------------------------------------------------
     [INFO] BUILD SUCCESS
     [INFO] ------------------------------------------------------------------------
@@ -214,23 +214,23 @@ With all the configuration ready in your [pom.xml](https://github.com/Azure-Samp
     [INFO] ------------------------------------------------------------------------
     ```
 
-    Your application is ready at `http://<appName>.azurewebsites.net/`. 
+    Your application is ready.
 
 ### [Spring Boot](#tab/springboot)
 
-Open the URL `http://<appName>.azurewebsites.net/greeting` with your local web browser (note the `/greeting` path), and you should see:
+Get the default domain for your app in the Azure portal by selecting **Overview** for your app. Append `/greeting`. You should see:
 
 :::image type="content" source="../../media/quickstart-java/springboot-hello-world-in-browser-azure-app-service.png" alt-text="Screenshot of Spring Boot Hello World web app running in Azure App Service.":::
 
 ### [Quarkus](#tab/quarkus)
 
-Open the URL `http://<appName>.azurewebsites.net/hello` with your local web browser (note the `/hello` path), and you should see:
+Get the default domain for your app in the Azure portal by selecting **Overview** for your app. Append `/hello`. You should see:
 
 :::image type="content" source="../../media/quickstart-java/quarkus-hello-world-in-browser-azure-app-service.png" alt-text="Screenshot of Quarkus web app running in Azure App Service.":::
 
 ### [Embedded Tomcat](#tab/embeddedtomcat)
 
-Open the URLl with your local web browser, and you should see:
+Open the URL with your local web browser, and you should see:
 
 :::image type="content" source="../../media/quickstart-java/embedded-tomcat-hello-world-in-browser-azure-app-service.png" alt-text="Screenshot of embedded Tomcat web app running in Azure App Service.":::
 

articles/app-service/includes/quickstart-java/quickstart-java-jboss.md

@@ -120,7 +120,7 @@ With all the configuration ready in your *pom.xml* file, you can deploy your Jav
 mvn package azure-webapp:deploy -DskipTests
 ```
 
-Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready at `http://<appName>.azurewebsites.net/` (`http://petstoreee7-1745409173307.azurewebsites.net` in the demo). Open the URL with your local web browser, you should see
+Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready. In this demo, the URL is `http://petstoreee7-1745409173307.azurewebsites.net`. Open the URL with your local web browser, you should see
 
 ![Screenshot of Maven Hello World web app running in Azure App Service.](../../media/quickstart-java/jboss-sample-in-app-service.png)
 

articles/app-service/includes/quickstart-java/quickstart-java-linux-maven-pivot.md

@@ -266,7 +266,7 @@ mvn package azure-webapp:deploy -DskipTests
 
 -----
 
-Once deployment is completed, your application is ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1590394316693.azurewebsites.net` in the demo). Open the url with your local web browser, you should see
+Once deployment is completed, your application is ready at `http://helloworld-1590394316693.azurewebsites.net` in the demo. Open the url with your local web browser, you should see
 
 # [Java SE](#tab/javase)
 

articles/app-service/includes/quickstart-java/quickstart-java-tomcat.md

@@ -110,7 +110,7 @@ With all the configuration ready in your *pom.xml* file, you can deploy your Jav
 ```azurecli-interactive
 mvn package azure-webapp:deploy
 ```
-Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready at `http://<appName>.azurewebsites.net/` (`http://helloworld-1745408005556.azurewebsites.net` in the demo). Open the URL with your local web browser, you should see
+Once you select from a list of available subscriptions, Maven deploys to Azure App Service. When deployment completes, your application is ready. In this demo, the URL is `http://helloworld-1745408005556.azurewebsites.net`. Open the URL with your local web browser, you should see
 
 ![Screenshot of Maven Hello World web app running in Azure App Service.](../../media/quickstart-java/java-hello-world-in-browser-azure-app-service.png)
 

articles/app-service/includes/quickstart-php/quickstart-php-windows-pivot.md

@@ -78,7 +78,7 @@ To complete this quickstart:
     When the web app has been created, the Azure CLI shows output similar to the following example:
 
     <pre>
-    Local git is configured with url of 'https://&lt;username&gt;@&lt;app-name&gt;.scm.azurewebsites.net/&lt;app-name&gt;.git'
+    Local git is configured with url of &lt;URL>
     {
       "availabilityState": "Normal",
       "clientAffinityEnabled": true,
@@ -95,14 +95,10 @@ To complete this quickstart:
     You've created an empty new web app, with git deployment enabled.
 
     > [!NOTE]
-    > The URL of the Git remote is shown in the `deploymentLocalGitUrl` property, with the format `https://<username>@<app-name>.scm.azurewebsites.net/<app-name>.git`. Save this URL as you need it later.
+    > The URL of the Git remote is shown in the `deploymentLocalGitUrl` property. Save this URL as you need it later.
     >
 
-1. Browse to your newly created web app. Replace _&lt;app-name>_ with your unique app name created in the prior step.
-
-    ```bash
-    http://<app-name>.azurewebsites.net
-    ```
+1. Browse to your newly created web app. 
 
     Here's what your new web app should look like:
 
@@ -131,18 +127,14 @@ To complete this quickstart:
   remote: Finished successfully.
   remote: Running post deployment command(s)...
   remote: Deployment successful.
-  To https://&lt;app-name&gt;.scm.azurewebsites.net/&lt;app-name&gt;.git
+  To &lt;URL>
       cc39b1e..25f1805  main -> main
   </pre>
 
 ## Browse to the app
 
 Browse to the deployed application using your web browser.
 
-```
-http://<app-name>.azurewebsites.net
-```
-
 The PHP sample code is running in an Azure App Service web app.
 
 ![Sample app running in Azure](../../media/quickstart-php/hello-world-in-browser.png)

articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md

@@ -1,21 +1,21 @@
 ---
-title: 'Invoke an OpenAPI App Service web app from Azure AI Agent Service'
-description: Learn how to integrate App Service with AI Agent Service and get started with agentic AI
+title: 'Invoke an OpenAPI App Service web app from Azure AI Foundry Agent Service'
+description: Learn how to integrate App Service with AI Foundry Agent Service and get started with agentic AI
 author: seligj95
 ms.author: jordanselig
-ms.date: 04/25/2025
+ms.date: 05/28/2025
 ms.topic: article
 ms.custom: devx-track-dotnet
 ms.collection: ce-skilling-ai-copilot
 ---
 
-# Invoke an OpenAPI App Service web app from Azure AI Agent Service
+# Invoke an OpenAPI App Service web app from Azure AI Foundry Agent Service
 
-[Azure AI Agent Service](/azure/ai-services/agents/overview) allows you to create AI agents tailored to your needs through custom instructions and augmented by advanced tools like code interpreter, and custom functions. You can now connect your Azure AI Agent to an external API using an [OpenAPI 3.0](https://www.openapis.org/what-is-openapi) specified tool, allowing for scalable interoperability with various applications. 
+[Azure AI Foundry Agent Service](/azure/ai-services/agents/overview) allows you to create AI agents tailored to your needs through custom instructions and augmented by advanced tools like code interpreter, and custom functions. You can now connect your Azure AI Agent to an external API using an [OpenAPI 3.0](https://www.openapis.org/what-is-openapi) specified tool, allowing for scalable interoperability with various applications. 
 
-Azure App Service is a fully managed platform for building, deploying, and scaling web apps and APIs. If your API is hosted on Azure App Service, you can connect your AI Agent to the API using the OpenAPI specification. The OpenAPI specification defines the API and how to interact with it. You can then use natural language to invoke the API through your AI Agent.
+Azure App Service is a fully managed platform for building, deploying, and scaling web apps and APIs. If your API is hosted on Azure App Service, you can connect your AI Agent to the API using the OpenAPI specification. The OpenAPI specification defines the API and how to interact with it. You can then use natural language to invoke the API through your AI Agent. This tool is powerful because it allows you to add AI agent capabilities to your existing apps with minimal code changes. Also, this agent has the ability to directly interact with your app. There's no need for significant code changes or implementation work other thank minor updates to interact with the agent using the available SDKs.
 
-In this tutorial, you're using an Azure AI Agent to invoke an API hosted on Azure App Service. By the end of this tutorial, you have a fashion assistant chat application running in App Service using an AI agent from the Azure AI Agent Service.
+In this tutorial, you're using an Azure AI Foundry Agent to invoke an existing API hosted on Azure App Service. By the end of this tutorial, you have a fashion assistant chat application running in App Service using an AI agent from the Azure AI Foundry Agent Service.
 
 :::image type="content" source="media/invoke-openapi-web-app-from-azure-ai-agent-service/browse-app.png" alt-text="A screenshot showing an AI agent running within App Service.":::
 
@@ -137,10 +137,10 @@ azd down
 1. **Chat Not Working**
    - Verify that the environment variables (`AzureAIAgent__ConnectionString` and `AzureAIAgent__AgentId`) are correctly set in the App Service environment variables.
    - Check that the AI Agent is properly created and configured with the correct OpenAPI tool.
-   - Ensure the OpenAPI specification URL is accessible from the Azure AI Agent Service.
+   - Ensure the OpenAPI specification URL is accessible from the Azure AI Foundry Agent Service.
    - Ensure the App Service URL is updated in the `swagger.json` provided to the OpenAPI Specified Tool.
 1. **Permission Issues**
-   - If you encounter authentication errors, ensure that your App Service's managed identity has proper permissions to access the Azure AI Agent Service. The managed identity needs at least the `Microsoft.MachineLearningServices/workspaces/agents/action` permission to interact with the Agent. The provided "Azure AI Developer role" has this permission and should be sufficient. If you decide to change this role, be sure it has the necessary permission.
+   - If you encounter authentication errors, ensure that your App Service's managed identity has proper permissions to access the Azure AI Foundry Agent Service. The managed identity needs at least the `Microsoft.MachineLearningServices/workspaces/agents/action` permission to interact with the Agent. The provided "Azure AI Developer role" has this permission and should be sufficient. If you decide to change this role, be sure it has the necessary permission.
 1. **API Issues**
    - If the agent is unable to perform actions on the inventory or cart, check the API routes in the OpenAPI specification.
    - Verify that the API endpoints are responding correctly by testing them directly in the Swagger UI at `/api/docs`.
@@ -183,7 +183,7 @@ Beyond basic interactions, the AI agent can handle more complex scenarios:
 
 ## Security Considerations
 
-- The application uses Azure managed identities for secure authentication to Azure AI Agent Service in production environments.
+- The application uses Azure managed identities for secure authentication to Azure AI Foundry Agent Service in production environments.
 - You can further secure your app and agent using any of the standard practices and Azure resources. For secure Azure AI Agent infrastructure templates, see the [azureai-samples repo](https://github.com/Azure-Samples/azureai-samples/tree/main/scenarios/Agents/setup).
 
 ## Next steps
@@ -197,4 +197,4 @@ Now that you learned how to connect your AI Agent to an API on Azure App Service
 > [Tutorial: Run chatbot in App Service with a Phi-4 sidecar extension (ASP.NET Core)](tutorial-ai-slm-dotnet.md)
 
 > [!div class="nextstepaction"]
-> [Deploy a .NET Blazor app connected to Azure SQL and Azure OpenAI on Azure App Service](./deploy-intelligent-apps-dotnet-to-azure-sql.md)
+> [Deploy a .NET Blazor app connected to Azure SQL and Azure OpenAI on Azure App Service](./deploy-intelligent-apps-dotnet-to-azure-sql.md)

articles/app-service/overview-access-restrictions.md

@@ -130,6 +130,8 @@ In this scenario, you're accessing your site through a private endpoint and are
 
 Traffic from Azure Front Door to your application originates from a well known set of IP ranges defined in the `AzureFrontDoor.Backend` service tag. Using a service tag restriction rule, you can restrict traffic to only originate from Azure Front Door. To ensure traffic only originates from your specific instance, you need to further filter the incoming requests based on the unique http header that Azure Front Door sends called X-Azure-FDID. You can find the Front Door ID in the portal.
 
+Alternatively, [Azure Private Link](../frontdoor/private-link.md) enables you to access Azure PaaS services and services hosted in Azure over a private endpoint in your virtual network. Traffic between your virtual network and the service goes over the Microsoft backbone network, eliminating exposure to the public Internet. Azure Front Door Premium can connect to your origin using Private Link. Your origin can be hosted in a virtual network or hosted as a PaaS service such as an Azure Web App. Private Link removes the need for your origin to be accessed publicly. To learn how to connect Azure Front Door to your App Service app with private link, see [Connect Azure Front Door Premium to an App Service (Web App or Function App) origin with Private Link](../frontdoor/standard-premium/how-to-enable-private-link-web-app.md).  
+
 ## Next steps
 > [!NOTE]
 > Access restriction rules that block public access to your site can also block services such as log streaming. If you require these, you will need to allow your App Service's IP address in your restrictions.

articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md

@@ -273,7 +273,7 @@ The most common causes of this error are:
 Because App Service authentication is a feature in Azure, it's not possible for the same code to work in your local environment. Unlike the app running in Azure, your local code doesn't benefit from the authentication middleware from App Service. You have a few alternatives:
 
 - Connect to SQL Database from your local environment with [`Active Directory Interactive`](/sql/connect/ado-net/sql/azure-active-directory-authentication#using-active-directory-interactive-authentication). The authentication flow doesn't sign in the user to the app itself, but it does connect to the back-end database with the signed-in user, and allows you to test database authorization locally.
-- Manually copy the access token from `https://<app-name>.azurewebsites.net/.auth/me` into your code, in place of the `X-MS-TOKEN-AAD-ACCESS-TOKEN` request header.
+- Manually copy the access token into your code, in place of the `X-MS-TOKEN-AAD-ACCESS-TOKEN` request header.
 - If you deploy from Visual Studio, use remote debugging of your App Service app.
 
 #### What happens when access tokens expire?