Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into swa/access-token

Author: craigshoemaker

.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",
@@ -3599,6 +3599,16 @@
       "source_path_from_root": "/articles/third-party-notices.md",
       "redirect_url": "https://github.com/MicrosoftDocs/azure-docs/blob/main/ThirdPartyNotices.md",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/glossary.md",
+      "redirect_url": "/azure/reliability/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/resiliency-recommendations/recommend-cosmos-db-nosql.md",
+      "redirect_url": "/azure/reliability/reliability-cosmos-db-nosql",
+      "redirect_document_id": false
     }
   ]
 }

articles/active-directory-b2c/whats-new-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory business-to-customer (B2C)"
 description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
-ms.date: 10/01/2024
+ms.date: 11/04/2024
 ms.service: azure-active-directory
 ms.subservice: b2c
 ms.topic: whats-new
@@ -19,6 +19,16 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
 
+## October 2024
+
+### Updated articles
+
+- [Secure APIs used for API connectors in Azure AD B2C](secure-rest-api.md) - ROPC flow updates
+- [Application types that can be used in Active Directory B2C](application-types.md) - Implicit grant flow updates
+- [Configure authentication in a sample single-page application by using Azure AD B2C](configure-authentication-sample-spa-app.md) - Implicit grant flow updates
+- [Single-page application sign-in using the OAuth 2.0 implicit flow in Azure Active Directory B2C](implicit-flow-single-page-application.md) - Implicit grant flow updates
+- [Register a single-page application in Azure Active Directory B2C](tutorial-register-spa.md) - Implicit grant flow updates
+
 ## September 2024
 
 ### Updated articles
@@ -33,9 +43,3 @@ This month, we changed Twitter to X in numerous articles and code samples.
 
 - [Tutorial: Configure Keyless with Azure Active Directory B2C](partner-keyless.md) - Editorial updates
 
-## July 2024
-
-### Updated articles
-
-- [Developer notes for Azure Active Directory B2C](custom-policy-developer-notes.md) - Updated Twitter to X
-- [Custom email verification with SendGrid](custom-email-sendgrid.md) - Updated the localization script

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/api-management-howto-use-azure-monitor.md

@@ -7,7 +7,7 @@ author: dlepow
 ms.service: azure-api-management
 ms.custom: engagement-fy23, devdivchpfy22
 ms.topic: tutorial
-ms.date: 08/26/2024
+ms.date: 11/01/2024
 ms.author: danlep
 ---
 # Tutorial: Monitor published APIs
@@ -37,24 +37,24 @@ In this tutorial, you learn how to:
 
 ## View metrics of your APIs
 
-API Management emits [metrics](/azure/azure-monitor/essentials/data-platform-metrics) every minute, giving you near real-time visibility into the state and health of your APIs. The following are the most frequently used metrics. For a list of all available metrics, see [supported metrics](/azure/azure-monitor/essentials/metrics-supported#microsoftapimanagementservice).
+API Management emits [metrics](/azure/azure-monitor/essentials/data-platform-metrics) every minute, giving you near real-time visibility into the state and health of your APIs. The following are the most frequently used metrics. For a list of all available metrics, see [supported metrics](/azure/azure-monitor/reference/supported-metrics/microsoft-apimanagement-service-metrics).
 
 * **Capacity** - helps you make decisions about upgrading/downgrading your API Management services. The metric is emitted per minute and reflects the estimated gateway capacity at the time of reporting. The metric ranges from 0-100 calculated based on gateway resources such as CPU and memory utilization and other factors.
 
     > [!TIP]
-    > In the [v2 service tiers](v2-service-tiers-overview.md), API Management replaced the capacity metric with separate CPU and memory utilization metrics. These metrics can also be used for scaling decisions and troubleshooting. [Learn more](api-management-capacity.md)
+    > In the [v2 service tiers](v2-service-tiers-overview.md), API Management has replaced the capacity metric with separate CPU and memory utilization metrics. These metrics can also be used for scaling decisions and troubleshooting. [Learn more](api-management-capacity.md)
 
 * **Requests** - helps you analyze API traffic going through your API Management services. The metric is emitted per minute and reports the number of gateway requests with dimensions. Filter requests by response codes, location, hostname, and errors.
 
 > [!IMPORTANT]
-> The following metrics have been retired: Total Gateway Requests, Successful Gateway Requests, Unauthorized Gateway Requests, Failed Gateway Requests, Other Gateway Requests. Please migrate to the Requests metric which provides equivalent functionality.
+> The following metrics have been retired: Total Gateway Requests, Successful Gateway Requests, Unauthorized Gateway Requests, Failed Gateway Requests, Other Gateway Requests. Please migrate to the Requests metric which provides closely similar functionality.
 
 :::image type="content" source="media/api-management-howto-use-azure-monitor/apim-monitor-metrics-1.png" alt-text="Screenshot of Metrics in API Management Overview":::
 
 To access metrics:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance. On the **Overview** page, on the **Monitor** tab, review key metrics for your APIs.
-1. To investigate metrics in detail, select **Metrics** from the left menu.
+1. To investigate metrics in detail, select **Monitoring** > **Metrics** from the left menu.
 
     :::image type="content" source="media/api-management-howto-use-azure-monitor/api-management-metrics-blade.png" alt-text="Screenshot of Metrics item in Monitoring menu in the portal.":::
 
@@ -73,15 +73,14 @@ You can receive [alerts](/azure/azure-monitor/alerts/alerts-metric-overview) bas
 To configure an example alert rule based on a request metric:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-1. Select **Alerts** from the left menu.
+1. Select **Monitoring** > **Alerts** from the left menu.
 
     :::image type="content" source="media/api-management-howto-use-azure-monitor/alert-menu-item.png" alt-text="Screenshot of Alerts option in Monitoring menu in the portal.":::
 
 1. Select **+ Create** > **Alert rule**.
-1. In the **Select a signal** window on the **Condition** tab:
-    1. In **Signal type**, select **Metrics**.
+1. On the **Condition** tab:
     1. In **Signal name**, select **Requests**.
-    1. In **Alert logic**, specify a **Threshold value**, which is the number of occurrences after which the alert should be triggered.
+    1. In **Alert logic**, review or modify the default values for the alert. For example, update the static **Threshold**, which is the number of occurrences after which the alert should be triggered.
     1. In **Split by dimensions**, in **Dimension name**, select **Gateway Response Code Category**.
     1. In **Dimension values**, select **4xx**, for client errors such as unauthorized or invalid requests. If the dimension value doesn't appear, select **Add custom value** and enter **4xx**.
     1. In **When to evaluate**, accept the default settings, or select other settings to configure how often the rule runs. Select **Next**.
@@ -94,13 +93,13 @@ To configure an example alert rule based on a request metric:
 
 1. On the **Details** tab of **Create an alert rule**, enter a name and description of the alert rule and select the severity level.
 1. Optionally configure the remaining settings. Then, on the **Review + create** tab, select **Create**.
-1. Now, test the alert rule by calling the Conference API without an API key. For example:
+1. Optionally test the alert rule by using an HTTP client to simulate a request that triggers the alert. For example, run the following command in a terminal, substituting the API Management hostname with the hostname of your API Management instance:
 
     ```bash
-    curl GET https://apim-hello-world.azure-api.net/conference/speakers HTTP/1.1 
+    curl GET https://contoso.azure-api.net/non-existent-endpoint HTTP/1.1 
     ```
 
-    An alert triggers based on the evaluation period, and it will send email to [email protected].
+    An alert triggers based on the evaluation period, and it will send email to [email protected]. 
 
     Alerts also appear on the **Alerts** page for the API Management instance.
 
@@ -111,7 +110,7 @@ To configure an example alert rule based on a request metric:
 Activity logs provide insight into the operations on your API Management services. Using activity logs, you can determine the "what, who, and when" for any write operations (PUT, POST, DELETE) taken on your API Management services.
 
 > [!NOTE]
-> Activity logs do not include read (GET) operations or operations performed in the Azure portal or using the original Management APIs.
+> Activity logs do not include read (GET) operations or operations performed in the Azure portal.
 
 You can access activity logs in your API Management service, or access logs of all your Azure resources in Azure Monitor. 
 
@@ -136,7 +135,7 @@ Resource logs (Azure Monitor logs) provide rich information about API Management
 To configure resource logs:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-2. Select **Diagnostic settings**.
+2. Select **Monitoring** > **Diagnostic settings**.
 
     :::image type="content" source="media/api-management-howto-use-azure-monitor/api-management-diagnostic-logs-blade.png" alt-text="Screenshot of Diagnostic settings item in Monitoring menu in the portal.":::
 
@@ -155,7 +154,7 @@ To configure resource logs:
 
 For more information, see [Create diagnostic settings to send platform logs and metrics to different destinations](/azure/azure-monitor/essentials/diagnostic-settings).
  
-## View diagnostic data in Azure Monitor
+## View logs and metrics in Azure Monitor
 
 If you enable collection of logs or metrics in a Log Analytics workspace, it can take a few minutes for data to appear in Azure Monitor. 
 
@@ -177,7 +176,7 @@ To view the data:
 
 For more information about using resource logs for API Management, see:
 
-* [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial), or try the [Log Analytics demo environment](https://ms.portal.azure.com/#view/Microsoft_OperationsManagementSuite_Workspace/LogsDemo.ReactView).
+* [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial).
 
 * [Overview of log queries in Azure Monitor](/azure/azure-monitor/logs/log-query-overview).
 
@@ -191,14 +190,14 @@ For details about the logging settings, see [Diagnostic logging settings referen
 
 To configure logging settings for all APIs:
 
-1. In the left menu of your API Management instance, select **APIs** > **All APIs**.
+1. In the left menu of your API Management instance, select **APIs** > **APIs** > **All APIs**.
 1. Select the **Settings** tab from the top bar.
 1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
 1. Review the settings and make changes if needed. Select **Save**. 
 
 To configure logging settings for a specific API:
 
-1. In the left menu of your API Management instance, select **APIs** and then the name of the API.
+1. In the left menu of your API Management instance, select **APIs** > **APIs** and then the name of the API.
 1. Select the **Settings** tab from the top bar.
 1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
 1. Review the settings and make changes if needed. Select **Save**. 

articles/api-management/limit-concurrency-policy.md

@@ -16,6 +16,8 @@ ms.author: danlep
 
 The `limit-concurrency` policy prevents enclosed policies from executing by more than the specified number of requests at any time. When that number is exceeded, new requests will fail immediately with the `429` Too Many Requests status code.
 
+[!INCLUDE [api-management-rate-limit-accuracy](../../includes/api-management-rate-limit-accuracy.md)]
+
 [!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
 
 ## Policy statement
@@ -40,6 +42,10 @@ The `limit-concurrency` policy prevents enclosed policies from executing by more
 - [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
 -  [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
 
+### Usage notes
+
+* The maximum number of requests enforced by API Management is lower when multiple capacity units are deployed in a region.
+
 ## Example
 
 The following example demonstrates how to limit number of requests forwarded to a backend based on the value of a context variable.