Resolved conflict

Author: rolyon

.openpublishing.redirection.json

@@ -379,6 +379,16 @@
       "redirect_url": "/previous-versions/azure/partner-solutions/logzio/troubleshoot",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/security/fundamentals/ocsp-sha-1-sunset.md",
+      "redirect_url": "/azure/security/fundamentals/azure-CA-details",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/security/fundamentals/tls-certificate-changes.md",
+      "redirect_url": "/azure/security/fundamentals/azure-CA-details",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/event-grid/event-schema-storage-actions.md",
       "redirect_url": "/azure/storage-actions/overview",
@@ -2294,6 +2304,11 @@
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/tutorial-create-vm-using-go-sdk",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/app-service/manage-disaster-recovery.md",
+      "redirect_url": "/azure/architecture/web-apps/guides/multi-region-app-service/multi-region-app-service",
+      "redirect_document_id": false
+    },       
     {
       "source_path_from_root": "/articles/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk.md",
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk",
@@ -6723,6 +6738,11 @@
       "source_path": "articles/notification-hubs/xamarin-notification-hubs-push-notifications-android-gcm.md",
       "redirect_url": "/dotnet/maui/data-cloud/push-notifications",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/storage/files/geo-redundant-storage-for-large-file-shares.md",
+      "redirect_url": "/azure/storage/files/files-redundancy",
+      "redirect_document_id": false
     }
   ]
 }

articles/api-management/TOC.yml

@@ -263,7 +263,7 @@
     href: set-edit-policies.md
   - name: Author policies using Microsoft Copilot in Azure
     href: /azure/copilot/author-api-management-policies?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
-  - name: Debug policies in VS Code
+  - name: Create and debug policies in VS Code
     href: api-management-debug-policies.md
   - name: Policy expressions
     href: api-management-policy-expressions.md

articles/api-management/api-management-debug-policies.md

@@ -1,72 +1,140 @@
 ---
-title: Debug Azure API Management policies in Visual Studio Code | Microsoft Docs
-description: Learn how to debug Azure API Management Policies using the Azure API Management Visual Studio Code extension
+title: Create and debug Azure API Management policies in VS Code
+description: Learn how to create, understand, and debug Azure API Management Policies with Copilot assistance using the Azure API Management Visual Studio Code extension.
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 09/22/2020
+ms.date: 03/27/2025
 ms.author: danlep
+ms.collection: ce-skilling-ai-copilot
 ---
 
-# Debug Azure API Management policies in Visual Studio Code
+# Create, understand, and debug Azure API Management policies in Visual Studio Code
 
-[!INCLUDE [api-management-availability-developer](../../includes/api-management-availability-developer.md)]
+[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-[Policies](api-management-policies.md) in Azure API Management provide powerful capabilities that help API publishers address cross-cutting concerns such as authentication, authorization, throttling, caching, and transformation. Policies are a collection of statements that are executed sequentially on the request or response of an API. 
+This article explains how to use the [Azure API Management Extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement) to create, understand, and debug Azure API Management policies with AI assistance from [GitHub Copilot for Azure](/azure/developer/github-copilot-azure/introduction). 
 
-This article describes how to debug API Management policies using the [Azure API Management Extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement). 
+Azure API Management [policies](api-management-howto-policies.md) are a sequence of statements that address cross-cutting concerns like authentication, authorization, throttling, caching, and transformation, applied to API requests or responses.
 
 ## Prerequisites
 
-* Create an API Management Developer-tier instance by following this [quickstart](get-started-create-service-instance.md) first.
+* [Visual Studio Code](https://code.visualstudio.com/) and the latest version of [Azure API Management Extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement). 
 
-* Install [Visual Studio Code](https://code.visualstudio.com/) and the latest version of [Azure API Management Extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement). 
+* The following extensions are needed for the specified scenarios:
+
+    * [GitHub Copilot for Azure extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azure-github-copilot) - to create and explain policies
+    * [REST Client extension](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) - for policy debugging
+
+* An API Management instance. If you need to create one, see this [quickstart](vscode-create-service-instance.md).
 
 * Import an API to your API Management instance. For example steps, see [Tutorial: Use the API Management Extension for Visual Studio Code to import and manage APIs](visual-studio-code-tutorial.md).
 
 ## Restrictions and limitations
 
-* This feature uses the built-in (service-level) all-access subscription (display name "Built-in all-access subscription") for debugging. 
+* Policy debugging is currently supported only in the API Management Developer tier.
+
+* Policy debugging uses the built-in (service-level) all-access subscription (display name "Built-in all-access subscription"). You must be a service owner to use this subscription.
+ 
+## Create a policy using GitHub Copilot for Azure
+
+The Azure API Management extension integrates with GitHub Copilot for Azure to help you create a draft of a policy. With AI assistance, create and edit policies in a user-friendly way. 
+
+To create a policy:
+
+1. Open the API Management extension in Visual Studio Code.
+1. Select the API Management instance you want to work with.
+1. Select the policy scope that you want to work with.
+    * To create a policy that applies to all APIs in the instance, select **Global Policy**.
+    * To create a policy that applies to a specific API, under **APIs**, select the API, and then select **Policy**.
+    * To create a policy that applies to a specific API operation, select the operation, and then select **Policy**.
+
+1. In the policy editor window that appears, right-click and select **Copilot** > **Draft APIM Policies**. The Copilot Chat window appears.
+1. In the Copilot Chat window, enter a prompt in natural language to create a policy. Examples:
+    
+    ```copilot-prompt
+    @azure I want to limit requests to 100 calls per minute
+    ```
+
+    ```copilot-prompt
+    @azure Create a policy that sets the backend URL to https://mybackend.contoso.com and adds a custom header to the request
+    ```
+1. Copilot generates a policy draft in the chat window. You can refine the prompt if you want Copilot to change the output. 
+
+1. When you're ready, select the **Copy** button to copy the policy to the clipboard, or select **Apply in Editor** to insert the policy in the editor window. If you are satisfied with the change in the policy XML, select **Keep**.
+
+:::image type="content" source="media/api-management-debug-policies/draft-policy.gif" alt-text="Animation showing drafting of an API Management policy in VS Code.":::
+
+> [!TIP]
+> Check in the **Problems** window for explanation of any issues in the policy XML.
+
+## Explain a policy using GitHub Copilot for Azure
 
-[!INCLUDE [api-management-tracing-alert](../../includes/api-management-tracing-alert.md)]
+Copilot can help explain an existing policy in your API Management instance. 
 
-## Initiate a debugging session
+To receive an explanation:
 
-1. Launch Visual Studio Code
-2. Navigate to the API Management extension under Azure extensions
-3. Find the API Management instance to debug
-4. Find the API and operation to debug
-5. Right click on the operation and select **Start policy debugging**
+1. Open the API Management extension in Visual Studio Code.
+1. Select the API Management instance you want to work with.
+1. Select the policy scope that you want to work with.
+    * To explain a policy that applies to all APIs in the instance, select **Global Policy**.
+    * To explain a policy that applies to a specific API, under **APIs**, select the API, and then select **Policy**.
+    * To explain a policy that applies to a specific API operation, select the operation, and then select **Policy**.
 
-At this point, the extension will try to initiate and establish a debugging session with the API Management gateway.
+1. In the policy editor window that appears, right-click and select **Copilot** > **Explain APIM Policies**. 
+1. An overview and explanation of policies in the policy XML document are generated in the Copilot Chat window.
 
-![initiate debugging](media/api-management-debug-policies/initiate-debugging-session.png)
+:::image type="content" source="media/api-management-debug-policies/draft-policy.gif" alt-text="Animation showing explanation of an API Management policy in VS Code.":::
 
-## Send a test request
-When the debugging session is established, the extension will open a new editor that allows us to create and send a test HTTP request to this operation leveraging the [REST Client extension](https://marketplace.visualstudio.com/items?itemName=humao.rest-client).
+## Debug policies using the VS Code extension
 
-You will notice the **Ocp-Apim-Debug** header has already been added to the request. This header is required and the value must be set to the service-level, all-access subscription key to trigger the debugging functionality in the API Management gateway.
+The Azure API Management extension for Visual Studio Code provides a debugging experience that allows you to step through the policy pipeline or set a breakpoint when you send a request to the gateway.
 
-Modify the HTTP request in the editor according to your test scenario. Then click **send request** to send the test request to the API Management gateway.
+### Initiate a debugging session
 
-![send a test request](media/api-management-debug-policies/rest-client.png)
+1. Open the API Management extension in Visual Studio Code.
+3. Select the API Management instance to debug.
+4. Select the API and operation to debug.
+5. Right click on the operation and select **Start Policy Debugging**.
 
-## Debug policies
-After the test HTTP request is sent, the extension will open the debugging window showing the effective policies of this operation and stop at the first effective policy. 
+At this point, the extension starts to establish a debugging session with the API Management gateway. Check the progress in the **Debug Console** window.
 
-![debug policies](media/api-management-debug-policies/main-window.png)
+:::image type="content" source="media/api-management-debug-policies/initiate-debugging-session.png" alt-text="Screenshot if initiating a policy debugging session in Visual Studio Code.":::
+
+> [!NOTE]
+> Starting a debugging session also enables request tracing for the duration of the session, to help you diagnose and solve issues.
+
+### Send a test request
+
+When the debugging session is established, the REST Client extension opens a new editor that allows you to create and send a test HTTP request to the gateway.
+
+The **Ocp-Apim-Debug** header is added automatically to the request. This header is required and the value must be set to the service-level, all-access subscription key to trigger the debugging functionality in the API Management gateway.
+
+Modify the HTTP request in the editor according to your test scenario. Then click **Send Request** to send the test request to the API Management gateway.
+
+
+:::image type="content" source="media/api-management-debug-policies/rest-client.png" alt-text="Screenshot of sending a test request in Visual Studio Code.":::
+
+### Debug policies
+
+After the test HTTP request is sent, the extension opens the debugging window, which shows the effective policies of this operation and stops at the first effective policy. 
+
+:::image type="content" source="media/api-management-debug-policies/main-window.png" alt-text="Screenshot of the debugging window in Visual Studio Code.":::
 
 To follow the policy pipeline, you can single-step through individual policies or set a breakpoint at a policy and step directly to that policy. 
 
-In the **Variables** panel, you can inspect values of system-created and user-created variables. In the **Breakpoints** panel, you can see the list of all breakpoints that have been set. In the **Call Stack** panel, you can see the current effective policy scope. 
+* In the **Variables** panel, inspect values of system-created and user-created variables. 
+* In the **Breakpoints** panel, view the list of all breakpoints that have been set. 
+* In the **Call Stack** panel, view the current effective policy scope. 
 
 If there is an error during policy execution, you will see the details of the error at the policy where it happened. 
 
-![exceptions](media/api-management-debug-policies/exception.png)
+Exit the debugging session by clicking the **Stop** button when you are finished.
 
-> [!TIP]
-> Remember to exit the debug session by clicking the **Stop** button when you are finished.
+:::image type="content" source="media/api-management-debug-policies/exception.png" alt-text="Screenshot of a policy exception in Visual Studio Code.":::
 
+> [!TIP]
+> To review the request trace, select the value of the `Ocp-Apim-Trace-Location` header that is provided in the HTTP response. 
 
 ## Related content
 

articles/api-management/api-management-howto-api-inspector.md

@@ -172,7 +172,7 @@ To help automate these steps with the [Visual Studio Code REST Client](https://m
 @requestBody = // Data to send
 @tenantId = // Tenant ID
  
-POST https://login.microsoftonline.com/{{tenandId}}/oauth2/token
+POST https://login.microsoftonline.com/{tenantId}/oauth2/token
 content-type: application/x-www-form-urlencoded
  
 grant_type=client_credentials&client_id={{clientId}}&client_secret={{clientSecret}}&resource=https%3A%2F%2Fmanagement.azure.com%2F

articles/api-management/api-management-howto-cache-external.md

@@ -41,7 +41,7 @@ To complete this tutorial, you need to:
 
 + [Create an Azure API Management instance](get-started-create-service-instance.md)
 + Understand [caching in Azure API Management](api-management-howto-cache.md)
-+ Have an [Azure Cache for Redis](../azure-cache-for-redis/quickstart-create-redis.md), [Azure Managed Redis](../azure-cache-for-redis/quickstart-create-managed-redis.md), or another Redis-compatible cache available. 
++ Have an [Azure Cache for Redis](../azure-cache-for-redis/quickstart-create-redis.md), [Azure Managed Redis](../redis/quickstart-create-managed-redis.md), or another Redis-compatible cache available. 
 
     > [!IMPORTANT]
     > Azure API Management uses a Redis connection string to connect to the cache. If you use Azure Cache for Redis or Azure Managed Redis, enable access key authentication in your cache to use a connection string. Currently, you can't use Microsoft Entra authentication to connect Azure API Management to Azure Cache for Redis or Azure Managed Redis.

articles/api-management/azure-openai-enable-semantic-caching.md

@@ -15,7 +15,7 @@ ms.collection: ce-skilling-ai-copilot
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-Enable semantic caching of responses to Azure OpenAI API requests to reduce bandwidth and processing requirements imposed on the backend APIs and lower latency perceived by API consumers. With semantic caching, you can return cached responses for identical prompts and also for prompts that are similar in meaning, even if the text isn't the same. For background, see [Tutorial: Use Azure Cache for Redis as a semantic cache](../azure-cache-for-redis/cache-tutorial-semantic-cache.md).
+Enable semantic caching of responses to Azure OpenAI API requests to reduce bandwidth and processing requirements imposed on the backend APIs and lower latency perceived by API consumers. With semantic caching, you can return cached responses for identical prompts and also for prompts that are similar in meaning, even if the text isn't the same. For background, see [Tutorial: Use Azure Cache for Redis as a semantic cache](../redis/tutorial-semantic-cache.md).
 
 > [!NOTE]
 > The configuration steps in this article enable semantic caching for Azure OpenAI APIs. These steps can be generalized to enable semantic caching for corresponding large language model (LLM) APIs available through the [Azure AI Model Inference API](/azure/ai-studio/reference/reference-model-inference-api). 
@@ -27,9 +27,9 @@ Enable semantic caching of responses to Azure OpenAI API requests to reduce band
     * Chat Completion API - Deployment used for API consumer calls 
     * Embeddings API - Deployment used for semantic caching
 * The API Management instance must be configured to use managed identity authentication to the Azure OpenAI APIs. For more information, see [Authenticate and authorize access to Azure OpenAI APIs using Azure API Management ](api-management-authenticate-authorize-azure-openai.md#authenticate-with-managed-identity).
-* An [Azure Cache for Redis Enterprise](../azure-cache-for-redis/quickstart-create-redis-enterprise.md) or [Azure Managed Redis](../azure-cache-for-redis/quickstart-create-managed-redis.md) instance. The **RediSearch** module must be enabled on the Redis cache.
+* An [Azure Cache for Redis Enterprise](../azure-cache-for-redis/quickstart-create-redis-enterprise.md) or [Azure Managed Redis](../redis/quickstart-create-managed-redis.md) instance. The **RediSearch** module must be enabled on the Redis cache.
     > [!NOTE]
-    > You can only enable the **RediSearch** module when creating a new Azure Redis Enterprise or Azure Managed Redis cache. You can't add a module to an existing cache. [Learn more](../azure-cache-for-redis/cache-redis-modules.md)
+    > You can only enable the **RediSearch** module when creating a new Azure Redis Enterprise or Azure Managed Redis cache. You can't add a module to an existing cache. [Learn more](../redis/redis-modules.md)
 * External cache configured in the Azure API Management instance. For steps, see [Use an external Redis-compatible cache in Azure API Management](api-management-howto-cache-external.md).
 
 

articles/api-management/azure-openai-semantic-cache-lookup-policy.md

@@ -45,7 +45,7 @@ Use the `azure-openai-semantic-cache-lookup` policy to perform cache lookup of r
 
 | Attribute         | Description                                            | Required | Default |
 | ----------------- | ------------------------------------------------------ | -------- | ------- |
-| score-threshold	| Similarity score threshold used to determine whether to return a cached response to a prompt. Value is a decimal between 0.0 and 1.0. [Learn more](../azure-cache-for-redis/cache-tutorial-semantic-cache.md#change-the-similarity-threshold). | Yes |	N/A |
+| score-threshold	| Similarity score threshold used to determine whether to return a cached response to a prompt. Value is a decimal between 0.0 and 1.0. [Learn more](../redis/tutorial-semantic-cache.md#change-the-similarity-threshold). | Yes |	N/A |
 | embeddings-backend-id | [Backend](backends.md) ID for OpenAI embeddings API call. |	Yes |	N/A |
 | embeddings-backend-auth | Authentication used for Azure OpenAI embeddings API backend. | Yes. Must be set to `system-assigned`. | N/A |
 | ignore-system-messages | Boolean. If set to `true`, removes system messages from a GPT chat completion prompt before assessing cache similarity. | No | false |