Merge pull request #289621 from MicrosoftDocs/main

10/31/2024 PM Publish

Author: Taojunshen

.openpublishing.publish.config.json

@@ -236,6 +236,12 @@
             "branch": "main",
             "branch_mapping": {}
         },
+        {
+            "path_to_root": "azure-iot-operations-samples-m3",
+            "url": "https://github.com/Azure-Samples/explore-iot-operations",
+            "branch": "release-m3",
+            "branch_mapping": {}
+        },
         {
             "path_to_root": "azure-iot-sdk-node",
             "url": "https://github.com/Azure/azure-iot-sdk-node",

.openpublishing.redirection.json

@@ -108,7 +108,7 @@
     {
       "source_path_from_root": "/articles/application-insights/app-insights-analytics-diagnostics.md",
       "redirect_url": "/azure/application-insights/app-insights-analytics",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/application-insights/app-insights-analytics-reference.md",
@@ -118,7 +118,7 @@
     {
       "source_path_from_root": "/articles/application-insights/app-insights-azure.md",
       "redirect_url": "/azure/application-insights/app-insights-overview",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/application-insights/app-insights-developer-analytics.md",
@@ -133,7 +133,7 @@
     {
       "source_path_from_root": "/articles/application-insights/app-insights-java-eclipse.md",
       "redirect_url": "/azure/application-insights/app-insights-java-quick-start",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/application-insights/app-insights-pricing-enterprise-details.md",

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: article
-ms.date: 01/12/2023
+ms.date: 10/30/2024
 ms.author: danlep
 ms.custom: engagement-fy23
 ---
@@ -54,12 +54,12 @@ Using key vault certificates is recommended because it helps improve API Managem
 
 ### Developer, Basic, Standard, or Premium tier
 
-To receive and verify client certificates over HTTP/2 in the Developer, Basic, Basic v2, Standard, Standard v2, or Premium tiers, you must enable the **Negotiate client certificate** setting on the **Custom domain** blade as shown below.
+To receive and verify client certificates over HTTP/2 in the Developer, Basic, Standard, or Premium tiers, you must enable the **Negotiate client certificate** setting on the **Custom domain** blade as shown below.
 
 ![Negotiate client certificate](./media/api-management-howto-mutual-certificates-for-clients/negotiate-client-certificate.png)
 
-### Consumption tier
-To receive and verify client certificates in the Consumption tier, you must enable the **Request client certificate** setting on the **Custom domains** blade as shown below.
+### Consumption, Basic v2, Standard v2 tier
+To receive and verify client certificates in the Consumption, Basic v2, or Standard v2 tier, you must enable the **Request client certificate** setting on the **Custom domains** blade as shown below.
 
 ![Request client certificate](./media/api-management-howto-mutual-certificates-for-clients/request-client-certificate.png)
 

articles/api-management/media/redirect-content-urls-policy/original-response.png

@@ -14,7 +14,7 @@ ms.author: danlep
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-The `redirect-content-urls` policy rewrites (masks) links in the response body so that they point to the equivalent link via the gateway. Use in the outbound section to rewrite response body links to the backend service to make them point to the gateway. Use in the inbound section for an opposite effect.
+The `redirect-content-urls` policy rewrites (masks) links in the response body. Use in the outbound section to rewrite response body links to the backend service to make them point to the gateway instead. For example, you might do this to hide URLs of the original backend service when they appear in the response. Use in the inbound section for an opposite effect.
 
 > [!NOTE]
 >  This policy does not change any header values such as `Location` headers. To change header values, use the [set-header](set-header-policy.md) policy.
@@ -44,6 +44,14 @@ The `redirect-content-urls` policy rewrites (masks) links in the response body s
 <redirect-content-urls />
 ```
 
+For example, consider the following image, which shows an API response body that includes the original backend service URLs.
+
+:::image type="content" source="media/redirect-content-urls-policy/original-response.png" alt-text="Screenshot showing original outbound response in test console in the portal.":::
+
+After the `redirect-content-urls` policy is configured in the outbound section, the response body is rewritten to point to the gateway, in this case, `https://apim-hello-world.azure-api.net`.
+
+:::image type="content" source="media/redirect-content-urls-policy/test-replaced-url.png" alt-text="Screenshot showing replaced URLs in test console in the portal.":::
+
 ## Related policies
 
 * [Transformation](api-management-policies.md#transformation)

articles/api-management/media/redirect-content-urls-policy/test-replaced-url.png

@@ -65,7 +65,7 @@ The token format varies slightly according to the provider. See the following ta
 > [!NOTE]
 > The GitHub provider for App Service authentication does not support customized sign-in and sign-out.
 
-If the provider token is validated successfully, the API returns with an `authenticationToken` in the response body, which is your session token. 
+If the provider token is validated successfully, the API returns with an `authenticationToken` in the response body, which is your session token. To get more information on the user claims, see [Work with user identities in Azure App Service authentication](configure-authentication-user-identities.md).
 
 ```json
 {

articles/api-management/redirect-content-urls-policy.md

@@ -32,6 +32,8 @@ The _pricing tier_ of an App Service plan determines what App Service features y
 
 Each tier also provides a specific subset of App Service features. These features include custom domains and TLS/SSL certificates, autoscaling, deployment slots, backups, Traffic Manager integration, and more. The higher the tier, the more features that are available. To find out which features are supported in each pricing tier, see [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/windows/#pricing).
 
+You can find more comparisons between plans at [App Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits).
+
 <a name="new-pricing-tier-premiumv3"></a>
 
 ## PremiumV3 pricing tier

articles/app-service/configure-authentication-customize-sign-in-out.md

@@ -59,7 +59,7 @@ In addition to execution time, when using one or more always ready instances, yo
 >[!IMPORTANT]
 >In this article, prices are only provided to help understand example calculations. Always check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) when estimating costs you might incur while running your functions in the Flex Consumtion plan. 
 
-For the examples in this section, consider the example prices in this table for pay-as-you-go in East US.
+For the examples in this section, consider the discounted preview pricing in this table for pay-as-you-go in East US.
 
 | Mode        | Meter             | Free monthly grants        | Consumption rates        |
 | ------------| ----------------- | -------------------------- | ------------------------ |