Merge pull request #313777 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-27 06:00 UTC

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

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

@@ -5,7 +5,7 @@ ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: how-to
-ms.date: 10/07/2025
+ms.date: 03/24/2026
 ms.update-cycle: 180-days
 ms.collection: ce-skilling-ai-copilot
 ms.custom: template-how-to, build-2024
@@ -21,32 +21,31 @@ Learn more about managing AI APIs in API Management:
 
 * [AI gateway capabilities in Azure API Management](genai-gateway-capabilities.md)
 
-
 ## 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 Foundry tool.
 
-* **Azure OpenAI** - Manage Azure OpenAI in Microsoft Foundry model deployments. 
+* **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 Foundry tool 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).
+* **Azure AI**: Manage model endpoints in Microsoft Foundry that are exposed through the [Azure AI Model Inference API](/rest/api/aifoundry/modelinference/).
 
     Clients call the deployment at a `/models` endpoint such as `/my-model/models/chat/completions`. Deployment name is passed in the request body. Use this option if you want flexibility to switch between models exposed through the Azure AI Model Inference API and those deployed in Azure OpenAI in Foundry Models.
 
 ## Prerequisites
 
-- An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
+* An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
 
-- A Foundry tool 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
 
-Use the following steps to import an AI API to API Management. 
+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
+* Operations for each of the API's REST API endpoints.
 * 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.
@@ -62,37 +61,38 @@ To import a Microsoft Foundry API to API Management:
 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 a Foundry tool. 
+    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.
     1. In **Base path**, enter a path that your API Management instance uses to access the deployment endpoint.
-    1. Optionally select one or more **Products** to associate with the API.  
+    1. Optionally, select one or more **Products** to associate with the API.  
     1. In **Client compatibility**, select either of the following based on the types of client you intend to support. See [Client compatibility options](#client-compatibility-options) for more information.
-        * **Azure OpenAI** - Select this option if your clients only need to access Azure OpenAI in Microsoft Foundry model deployments.
-        * **Azure AI** - Select this option if your clients need to access other models in Microsoft Foundry. 
+        * **Azure OpenAI**: Select this option if your clients only need to access Azure OpenAI in Microsoft Foundry model deployments.
+        * **Azure AI**: Select this option if your clients need to access other models in Microsoft Foundry.
     1. Select **Next**.
 
         :::image type="content" source="media/azure-ai-foundry-api/client-compatibility.png" alt-text="Screenshot of Microsoft Foundry API configuration in the portal.":::
 
-1. On the **Manage token consumption** tab, optionally enter settings or accept defaults that define the following policies to help monitor and manage the API:
+1. On the **Manage token consumption** tab, optionally enter settings, or accept defaults that define the following policies to help monitor and manage the API:
     * [Manage token consumption](llm-token-limit-policy.md)
-    * [Track token usage](llm-emit-token-metric-policy.md) 
-1. On the **Apply semantic caching** tab, optionally enter settings or accept defaults that define the policies to help optimize performance and reduce latency for the API:
+    * [Track token usage](llm-emit-token-metric-policy.md)
+1. On the **Apply semantic caching** tab, optionally enter settings, or accept defaults that define the policies to help optimize performance and reduce latency for the API:
     * [Enable semantic caching of responses](azure-openai-enable-semantic-caching.md)
-1. On the **AI content safety**, optionally enter settings or accept defaults to configure the Azure AI Content Safety service to block prompts with unsafe content:
+1. On the **AI content safety**, optionally enter settings, or accept defaults to configure the Azure AI Content Safety service to block prompts with unsafe content:
     * [Enforce content safety checks on LLM requests](llm-content-safety-policy.md)
 1. Select **Review**.
-1. After settings are validated, select **Create**. 
+1. After settings are validated, select **Create**.
 
 ## Test the AI API
 
-To ensure that your AI API is working as expected, test it in the API Management test console. 
+To ensure that your AI API is working as expected, test it in the API Management test console.
+
 1. Select the API you created in the previous step.
 1. Select the **Test** tab.
 1. Select an operation that's compatible with the model deployment.
     The page displays fields for parameters and headers.
-1. Enter parameters and headers as needed. Depending on the operation, you might need to configure or update a **Request body**. Here's a very basic example request body for a chat completions operation:
+1. Enter parameters and headers as needed. Depending on the operation, you might need to configure or update a **Request body**. Here's a basic example request body for a chat completions operation:
 
     ```json
     {
@@ -113,5 +113,4 @@ To ensure that your AI API is working as expected, test it in the API Management
 
     When the test is successful, the backend responds with a successful HTTP response code and some data. Appended to the response is token usage data to help you monitor and manage your language model token consumption.
 
-
 [!INCLUDE [api-management-define-api-topics.md](../../includes/api-management-define-api-topics.md)]

articles/event-grid/use-cases.md

@@ -1,65 +1,75 @@
 ---
-title: Use cases for using Azure Event Grid
-description: This article provides a list of use cases that show you how to use both Message Queuing Telemetry Transport (MQTT) and HTTP messaging capabilities of Event Grid. 
+title: Azure Event Grid Use Cases for Event-Driven Apps
+description: This article provides a list of use cases that show you how to use both Message Queuing Telemetry Transport (MQTT) and HTTP messaging capabilities of Event Grid.
 ms.topic: concept-article
 author: robece
 ms.author: robece
+ms.reviewer: spelluru
 ms.custom:
   - references_regions
   - build-2024
-ms.date: 02/04/2025
+ms.date: 03/26/2026
 # Customer intent: As an architect or a developer, I want to know what Azure Event Grid is and how it can help me with creating event-driven applications. 
 ---
 
 # Azure Event Grid use cases
 
-This article provides you with a few sample use cases for using Azure Event Grid. 
+This article provides several sample use cases for using Azure Event Grid. 
 
 > [!NOTE]
-> If you are new to Azure Event Grid, read through the [Azure Event Grid overview](overview.md) article before proceeding further. 
+> If you're new to Azure Event Grid, read the [Azure Event Grid overview](overview.md) before proceeding. 
 
 ## MQTT messaging use cases
-Azure Event Grid’s MQTT broker feature enables you to accomplish the following scenarios.
+
+Azure Event Grid's MQTT broker feature enables you to accomplish the following scenarios.
 
 ### Ingest IoT telemetry
+
 :::image type="content" source="media/overview/ingest-telemetry.png" alt-text="High-level diagram of Event Grid that shows IoT clients using MQTT protocol to send messages to a cloud app." lightbox="media/overview/ingest-telemetry-high-res.png" border="false":::
 
-Ingest telemetry using a **many-to-one messaging** pattern. For example, use Event Grid to send telemetry from multiple IoT devices to a cloud application. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.
+Ingest telemetry by using a **many-to-one messaging** pattern. For example, use Event Grid to send telemetry from multiple IoT devices to a cloud application. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.
 
 ### Command and control
+
 :::image type="content" source="media/overview/command-control.png" alt-text="High-level diagram of Event Grid that shows a cloud application sending a command message over MQTT to a device using request and response topics." lightbox="media/overview/command-control-high-res.png" border="false":::
 
-Control your MQTT clients using the **request-response** (one-to-one) message pattern. For example, use Event Grid to send a command from a cloud application to an IoT device. 
+Control your MQTT clients by using the **request-response** (one-to-one) message pattern. For example, use Event Grid to send a command from a cloud application to an IoT device. 
 
 ### Broadcast alerts
+
 :::image type="content" source="media/overview/broadcast-alerts.png" alt-text="High-level diagram of Event Grid that shows a cloud application sending an alert message over MQTT to several devices." lightbox="media/overview/broadcast-alerts-high-res.png" border="false":::
 
-Broadcast alerts to a fleet of clients using the **one-to-many** messaging pattern. For example, use Event Grid to send an alert from a cloud application to multiple IoT devices. This pattern enables the application to publish only one message that the service replicates for every interested client.
+Broadcast alerts to a fleet of clients by using the **one-to-many** messaging pattern. For example, use Event Grid to send an alert from a cloud application to multiple IoT devices. This pattern enables the application to publish only one message that the service replicates for every interested client.
 
 ### Integrate MQTT data
+
 :::image type="content" source="media/overview/integrate-data.png" alt-text="Diagram that shows several IoT devices sending health data over MQTT to Event Grid." lightbox="media/overview/integrate-data-high-res.png" border="false":::
 
 Integrate data from your MQTT clients by routing MQTT messages to Azure services and custom endpoints through [push delivery](overview.md#push-delivery) or [pull delivery](overview.md#pull-delivery). For example, use Event Grid to route telemetry from your IoT devices to Event Hubs and then to Azure Stream Analytics to gain insights from your device telemetry.
 
 ## Push delivery use cases
-Event Grid’s push delivery allows you to realize the following use cases.
+Event Grid push delivery enables the following use cases.
 
 ### Build event-driven serverless solutions
+
 :::image type="content" source="media/overview/build-event-serverless.png" alt-text="Diagram that shows Azure Functions publishing events to Event Grid using HTTP. Event Grid then sends those events to Azure Logic Apps." lightbox="media/overview/build-event-serverless-high-res.png" border="false":::
 
-Use Event Grid to build serverless solutions with Azure Functions Apps, Logic Apps, and API Management. Using serverless services with Event Grid affords you a level of productivity, effort economy, and integration superior to that of classical computing models where you have to procure, manage, secure, and maintain all infrastructure deployed.  
+Use Event Grid to build serverless solutions with Azure Functions Apps, Logic Apps, and API Management. By using serverless services with Event Grid, you get a level of productivity, effort economy, and integration that's superior to classical computing models where you have to procure, manage, secure, and maintain all infrastructure deployed.  
 
 ### Receive events from Azure services
+
 :::image type="content" source="media/overview/receive-events-azure.png" alt-text="Diagram that shows Blob Storage publishing events to Event Grid over HTTP." lightbox="media/overview/receive-events-azure-high-res.png" border="false":::
 
-Event Grid can receive events from 20+ Azure services so that you can automate your operations. For example, you can configure Event Grid to receive an event when a new blob has been created on an Azure Storage Account so that your downstream application can read and process its content. For a list of all supported Azure services and events, see [System topics](system-topics.md).
+Event Grid can receive events from more than 20 Azure services so that you can automate your operations. For example, you can configure Event Grid to receive an event when a new blob is created on an Azure Storage Account so that your downstream application can read and process its content. For a list of all supported Azure services and events, see [System topics](system-topics.md).
 
 ### Receive events from your applications
+
 :::image type="content" source="media/overview/receive-events-apps.png" alt-text="Diagram that shows customer application publishing events to Event Grid using HTTP. Event Grid sends those events to webhooks or Azure services." lightbox="media/overview/receive-events-apps-high-res.png" border="false":::
 
 Your own service or application publishes events to Event Grid that subscriber applications process. Event Grid features [Namespace Topics](concepts-event-grid-namespaces.md#namespace-topics) to address integration and routing requirements at scale with a simple resource model. You can also use [Custom Topics](custom-topics.md) to meet basic integration requirements and [Domains](event-domains.md) for a simple management and routing model when you need to distribute events to hundreds or thousands of different groups.
 
 ### Receive events from partner (SaaS providers)
+
 :::image type="content" source="media/overview/receive-saas-providers.png" alt-text="Diagram that shows an external partner application publishing event to Event Grid using HTTP." lightbox="media/overview/receive-saas-providers-high-res.png" border="false":::
 
 A multitenant SaaS provider or platform can publish their events to Event Grid through a feature called [Partner Events](partner-events-overview.md). You can [subscribe to those events](subscribe-to-partner-events.md) and automate tasks, for example. Events from the following partners are currently available:
@@ -69,14 +79,17 @@ A multitenant SaaS provider or platform can publish their events to Event Grid t
 - [Tribal Group](subscribe-to-tribal-group-events.md)
 
 ## Pull delivery use cases
-Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#push-and-pull-delivery). With this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized using pull delivery.
+
+Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#push-and-pull-delivery). By using this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized by using pull delivery.
 
 ### Receive events at your own pace
+
 :::image type="content" source="media/overview/pull-events-at-your-own-pace.png" alt-text="High-level diagram of a publisher and consumer application." lightbox="media/overview/pull-events-at-your-own-pace-high-res.png" border="false":::
 
-One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid affords clients full control on events consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.
+One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid gives clients full control over event consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.
 
 ### Consume events over a private link
+
 :::image type="content" source="media/overview/consume-private-link-pull-api.png" alt-text="High-level diagram of a consumer app inside a virtual network reading events from Event Grid over a private endpoint inside the virtual network." lightbox="media/overview/consume-private-link-pull-api-high-res.png" border="false":::
 
 You can configure **private links** to connect to Azure Event Grid to **publish and read** CloudEvents through a [private endpoint](../private-link/private-endpoint-overview.md) in your virtual network. Traffic between your virtual network and Event Grid travels the Microsoft backbone network.

articles/frontdoor/domain.md

@@ -106,7 +106,7 @@ The following table summarizes the features available with managed TLS certifica
 | Consideration | Subdomain | Apex domain | Wildcard domain |
 |-|-|-|-|
 | Managed TLS certificates available | Yes | Yes | Yes |
-| Managed TLS certificates are rotated automatically | Yes | See below | Yes |
+| Managed TLS certificates are rotated automatically | Yes | See below | No |
 
 When you use Azure Front Door-managed TLS certificates with apex domains, the automated certificate rotation might require you to revalidate your domain ownership. For more information, see [Apex domains in Azure Front Door](apex-domain.md#azure-front-door-managed-tls-certificate-rotation).