Merge pull request #312619 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-04 23:00 UTC

Author: learn-build-service-prod[bot]

articles/active-directory-b2c/service-limits.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 01/22/2026
+ms.date: 03/02/2026
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -186,7 +186,7 @@ The following table lists the administrative configuration limits in the Azure A
 
 ## Region specific service limits 
 
-As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. Only SMS verification is subject to these limits.
+As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. These limits apply to both SMS and Voice verification.
 
 | Region Code | Region Name                                    | Limit per tenant per 60 minutes | Limit per tenant per 24 hours            |                         
 |:----------- |:---------------------------------------------- |:------------------------------- | :----------------------------------------|

articles/api-management/amazon-bedrock-passthrough-llm-api.md

@@ -15,7 +15,7 @@ ms.custom: template-how-to, build-2024
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-In this article, you import an Amazon Bedrock language model API into your API Management instance as a passthrough API. This example shows a model that's hosted on an inference provider other than Azure AI services. Use AI gateway policies and other capabilities in API Management to simplify integration, improve observability, and enhance control over the model endpoints.
+In this article, you import an Amazon Bedrock language model API into your API Management instance as a passthrough API. This example shows a model that's hosted on an inference provider other than Foundry Tools. Use AI gateway policies and other capabilities in API Management to simplify integration, improve observability, and enhance control over the model endpoints.
 
 For more information about managing AI APIs in API Management, see:
 

articles/api-management/azure-ai-foundry-api.md

@@ -24,11 +24,11 @@ Learn more about managing AI APIs in API Management:
 
 ## Client compatibility options
 
-API Management supports two client compatibility options for AI APIs from Microsoft Foundry. When you import the API using the wizard, choose the option suitable for your model deployment. The option determines how clients call the API and how the API Management instance routes requests to the AI service.
+API Management supports two client compatibility options for AI APIs from Microsoft Foundry. When you import the API using the wizard, choose the option suitable for your model deployment. The option determines how clients call the API and how the API Management instance routes requests to the Foundry Tool.
 
 * **Azure OpenAI** - Manage Azure OpenAI in Microsoft Foundry model deployments. 
 
-    Clients call the deployment at an `/openai` endpoint such as `/openai/deployments/my-deployment/chat/completions`. Deployment name is passed in the request path. Use this option if your AI service only includes Azure OpenAI model deployments. 
+    Clients call the deployment at an `/openai` endpoint such as `/openai/deployments/my-deployment/chat/completions`. Deployment name is passed in the request path. Use this option if your Foundry Tool only includes Azure OpenAI model deployments. 
 
 * **Azure AI** - Manage model endpoints in Microsoft Foundry that are exposed through the [Azure AI Model Inference API](/azure/ai-studio/reference/reference-model-inference-api).
 
@@ -38,7 +38,7 @@ API Management supports two client compatibility options for AI APIs from Micros
 
 - An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
 
-- An Azure AI service in your subscription with one or more models deployed. Examples include models deployed in Microsoft Foundry or Azure OpenAI.
+- A Foundry Tool in your subscription with one or more models deployed. Examples include models deployed in Microsoft Foundry or Azure OpenAI.
 
 ## Import Microsoft Foundry API using the portal
 
@@ -47,8 +47,8 @@ Use the following steps to import an AI API to API Management.
 When you import the API, API Management automatically configures:
 
 * Operations for each of the API's REST API endpoints
-* A system-assigned identity with the necessary permissions to access the AI service deployment.
-* A [backend](backends.md) resource and a [set-backend-service](set-backend-service-policy.md) policy that direct API requests to the AI service endpoint.
+* A system-assigned identity with the necessary permissions to access the Foundry Tool deployment.
+* A [backend](backends.md) resource and a [set-backend-service](set-backend-service-policy.md) policy that direct API requests to the Azure AI Services endpoint.
 * Authentication to the backend using the instance's system-assigned managed identity.
 * (optionally) Policies to help you monitor and manage the API.
 
@@ -59,10 +59,10 @@ To import a Microsoft Foundry API to API Management:
 1. Under **Create from Azure resource**, select **Microsoft Foundry**.
 
     :::image type="content" source="media/azure-ai-foundry-api/ai-foundry-api.png" alt-text="Screenshot of creating an OpenAI-compatible API in the portal." :::
-1. On the **Select AI service** tab:
-    1. Select the **Subscription** in which to search for AI services. To get information about the model deployments in a service, select the **deployments** link next to the service name.
+1. On the **Select AI Service** tab:
+    1. Select the **Subscription** in which to search for Foundry Tools. To get information about the model deployments in a service, select the **deployments** link next to the service name.
        :::image type="content" source="media/azure-ai-foundry-api/deployments.png" alt-text="Screenshot of deployments for an AI service in the portal.":::
-    1. Select an AI service. 
+    1. Select a Foundry Tool. 
     1. Select **Next**.
 1. On the **Configure API** tab:
     1. Enter a **Display name** and optional **Description** for the API.

articles/api-management/breaking-changes/identity-provider-adal-retirement-sep-2025.md

@@ -23,7 +23,7 @@ This change will have no effect on the availability of your API Management servi
 
 Your service is impacted by this change if:
 
-* You've configured an [Microsoft Entra ID](../api-management-howto-aad.md) or [Azure AD B2C](../api-management-howto-aad-b2c.md) identity provider for user account authentication using the ADAL and use the provided developer portal.
+* You've configured a [Microsoft Entra ID](../api-management-howto-aad.md) or [Azure AD B2C](../api-management-howto-aad-b2c.md) identity provider for user account authentication using the ADAL and use the provided developer portal.
 
 ## What is the deadline for the change?
 

articles/api-management/edit-api.md

@@ -1,5 +1,5 @@
 ---
-title: Edit an API in the Azure Portal  | Microsoft Docs
+title: Edit an API in the Azure portal  | Microsoft Docs
 description: Learn how to use API Management to edit an API or its swagger.
 services: api-management
 author: dlepow

articles/api-management/front-door-api-management.md

@@ -143,7 +143,7 @@ The following are high level steps to add an endpoint for the developer portal t
 For more information and details about settings, see [How to configure an origin for Azure Front Door](../frontdoor/how-to-configure-origin.md#create-a-new-origin-group).
 
 > [!NOTE]
-> If you've configured an [Microsoft Entra ID](api-management-howto-aad.md) or [Microsoft Entra External ID](/entra/external-id/customers/overview-customers-ciam) identity provider for the developer portal, you need to update the corresponding app registration with an additional redirect URL to Front Door. In the app registration, add the URL for the developer portal endpoint configured in your Front Door profile.
+> If you've configured a [Microsoft Entra ID](api-management-howto-aad.md) or [Microsoft Entra External ID](/entra/external-id/customers/overview-customers-ciam) identity provider for the developer portal, you need to update the corresponding app registration with an additional redirect URL to Front Door. In the app registration, add the URL for the developer portal endpoint configured in your Front Door profile.
 
 ## Related content
 

articles/api-management/genai-gateway-capabilities.md

@@ -68,7 +68,7 @@ For example, to onboard a model deployed in Microsoft Foundry or another provide
 
 More information:
 
-* [Import an Microsoft Foundry API](azure-ai-foundry-api.md)
+* [Import a Microsoft Foundry API](azure-ai-foundry-api.md)
 * [Import a language model API](openai-compatible-llm-api.md)
 * [Expose a REST API as an MCP server](export-rest-mcp-server.md)
 * [Expose and govern an existing MCP server](expose-existing-mcp-server.md)
@@ -130,7 +130,7 @@ More information:
 
 An AI gateway secures and controls access to your AI APIs. By using the AI gateway, you can:
 
-* Use managed identities to authenticate to Azure AI services, so you don't need API keys for authentication
+* Use managed identities to authenticate to AI services in Azure, so you don't need API keys for authentication
 * Configure OAuth authorization for AI apps and agents to access APIs or MCP servers by using API Management's credential manager
 * Apply policies to automatically moderate LLM prompts by using [Azure AI Content Safety](/azure/ai-services/content-safety/overview)
 

articles/api-management/openai-compatible-llm-api.md

@@ -15,7 +15,7 @@ ms.custom: template-how-to
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-You can import OpenAI-compatible language model endpoints to your API Management instance, or import non-compatible models as passthrough APIs. For example, manage self-hosted LLMs or those hosted on inference providers other than Azure AI services. Use AI gateway policies and other API Management capabilities to simplify integration, improve observability, and enhance control over model endpoints.
+You can import OpenAI-compatible language model endpoints to your API Management instance, or import non-compatible models as passthrough APIs. For example, manage self-hosted LLMs or those hosted on inference providers other than Foundry Tools. Use AI gateway policies and other API Management capabilities to simplify integration, improve observability, and enhance control over model endpoints.
 
 Learn more about managing AI APIs in API Management:
 

articles/api-management/sap-api.md

@@ -1,5 +1,5 @@
 ---
-title: Import an SAP API by Using the Azure Portal | Microsoft Docs
+title: Import an SAP API by Using the Azure portal | Microsoft Docs
 titleSuffix:
 description: Learn how to import OData metadata from SAP as an API to Azure API Management, either directly or by converting the metadata to an OpenAPI specification.
 ms.service: azure-api-management

articles/api-management/self-hosted-gateway-enable-azure-ad.md

@@ -16,7 +16,7 @@ ms.author: danlep
 
 The Azure API Management [self-hosted gateway](self-hosted-gateway-overview.md) needs connectivity with its associated cloud-based API Management instance for reporting status, checking for and applying configuration updates, and sending metrics and events. 
 
-This article shows you how to enable the self-hosted gateway to authenticate to its associated cloud instance by using an [Microsoft Entra ID app](../active-directory/develop/app-objects-and-service-principals.md), using a client secret or certificate. By using Microsoft Entra authentication, you can configure longer expiry times for secrets and use standard steps to manage and rotate secrets. For other authentication options, see [Self-hosted gateway authentication options](self-hosted-gateway-authentication-options.md). 
+This article shows you how to enable the self-hosted gateway to authenticate to its associated cloud instance by using a [Microsoft Entra ID app](../active-directory/develop/app-objects-and-service-principals.md), using a client secret or certificate. By using Microsoft Entra authentication, you can configure longer expiry times for secrets and use standard steps to manage and rotate secrets. For other authentication options, see [Self-hosted gateway authentication options](self-hosted-gateway-authentication-options.md). 
 
 ## Scenario overview