Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us429364-seo-top25-vnet

Author: asudbring

.openpublishing.redirection.json

@@ -6879,6 +6879,11 @@
       "redirect_url": "/azure/sre-agent/troubleshoot-azure-container-apps",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/sre-agent/permissions.md",
+      "redirect_url": "/azure/sre-agent/security-context",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/reliability/whats-new.md",
       "redirect_url": "/azure/reliability/overview",

articles/active-directory-b2c/partner-whoiam.md

@@ -60,7 +60,7 @@ The following diagram shows the implementation architecture.
 
     * [Key Vault](https://azure.microsoft.com/services/key-vault/): Store passwords
     * [App Service](https://azure.microsoft.com/services/app-service/): Host the BRIMS API and admin portal services
-    * [Microsoft Entra ID](https://azure.microsoft.com/services/active-directory/): Authenticate administrative users for the portal
+    * [Microsoft Entra ID](https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id): Authenticate administrative users for the portal
     * [Azure Cosmos DB](https://azure.microsoft.com/services/cosmos-db/): Store and retrieve settings
     * [Application Insights overview](/azure/azure-monitor/app/app-insights-overview) (optional): Sign in to the API and the portal
 

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

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 05/11/2024
+ms.date: 07/15/2025
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -197,6 +197,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 228 |  Togo  | 10  |  30  |
 | 233 |	Ghana|	10	| 30 |
 | 234 | Nigeria | 20 | 100 |
+| 235 | Chad | 10 | 30 |
 | 236 |	Central African Republic  |	10	| 30 |
 | 238 | Cape Verde | 10 | 30 |
 | 249 |  Sudan | 10  |  30  |
@@ -212,6 +213,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 265 |	Malawi  |	10	| 30 |
 | 373 |	Moldova |	20	| 100 |
 | 375 |	Belarus   |	10	| 30 |
+| 381 | Serbia | 50 | 200 |
 | 386 | Slovenia | 10 | 50 |
 | 501 |  Belize| 10  |  30  |
 | 502 | Guatemala | 10 | 50 
@@ -236,10 +238,13 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 95 |	Myanmar (Burma) | 10	| 30 |
 | 961 |	Lebanon  |	10	| 30 |
 | 963 |	Syria  |	10	| 30 |
+| 964 | Iraq | 50 | 200 |
 | 967 |	Yemen	|10	| 30 |
 | 970 |  State of Palestine| 10  |  30  |
 | 972 |	Israel  |	50	| 200 |
+| 975 | Bhutan | 20 | 100 |
 | 976 |	Mongolia  |	10	| 30 |
+| 977 | Nepal | 20 | 100 |
 | 992 | Tajikistan | 10 | 30 |
 | 993 | Turkmenistan | 10 | 30 |
 | 994 | Azerbaijan | 50 | 200 | 

articles/api-management/api-management-capacity.md

@@ -56,6 +56,8 @@ Available aggregations for these metrics are as follows.
 
 In the Developer, Basic, Standard, and Premium tiers, the **Capacity** metric is available for making decisions about scaling or upgrading an API Management instance. Its construction is complex and imposes certain behavior.
 
+[!INCLUDE [capacity-change.md](../../includes/api-management-capacity-change.md)]
+
 Available aggregations for this metric are as follows.
 
 * **Avg** - Average percentage of capacity used across gateway processes in every [unit](upgrade-and-scale.md) of an API Management instance. 
@@ -171,6 +173,7 @@ Use capacity metrics for making decisions whether to scale an API Management ins
 + Ignore sudden spikes that are most likely not related to an increase in load (see [Capacity metric behavior](#capacity-metric-behavior) section for explanation).
 + As a general rule, upgrade or scale your instance when a capacity metric value exceeds **60% - 70%** for a long period of time (for example, 30 minutes). Different values may work better for your service or scenario.
 + If your instance or workspace gateway is configured with only 1 unit, upgrade or scale it when a capacity metric value exceeds **40%** for a long period. This recommendation is based on the need to reserve capacity for guest OS updates in the underlying service platform.
++ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric. 
 
 > [!TIP]  
 > If you are able to estimate your traffic beforehand, test your API Management instance or workspace gateway on workloads you expect. You can increase the request load gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.

articles/app-service/configure-ssl-certificate.md

@@ -55,7 +55,7 @@ You can add up to 1,000 private certificates per webspace.
 
 ## Create a free managed certificate
 
-The free App Service managed certificate is a turn-key solution for helping to secure your custom DNS name in App Service. Without any action from you, this TLS/SSL server certificate is fully managed by App Service and is automatically renewed continuously in six-month increments, 45 days before expiration, as long as the prerequisites that you set up stay the same. All the associated bindings are updated with the renewed certificate. You create and bind the certificate to a custom domain, and let App Service do the rest.
+The free App Service managed certificate is a turn-key solution for helping to secure your custom DNS name in App Service. Without any action from you, this TLS/SSL server certificate is fully managed by App Service and is automatically renewed, as long as the prerequisites that you set up stay the same. All the associated bindings are updated with the renewed certificate. You create and bind the certificate to a custom domain, and let App Service do the rest.
 
 Before you create a free managed certificate, make sure that you [meet the prerequisites](#prerequisites) for your app.
 

articles/application-gateway/application-gateway-configure-listener-specific-ssl-policy.md

@@ -5,80 +5,118 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 02/18/2022
+ms.date: 07/09/2025
 ms.author: mbender
 # Customer intent: As a cloud administrator, I want to configure listener-specific SSL policies on my Application Gateway, so that I can enhance security and performance by applying different SSL settings for each listener based on my application requirements.
 ---
 
 # Configure listener-specific SSL policies on Application Gateway through portal
 
+This article describes how to use the Azure portal to configure listener-specific SSL policies on your Azure Application Gateway. Listener-specific SSL policies allow you to configure specific listeners to use different SSL policies from each other. You can still set a default SSL policy that all listeners use unless overridden by the listener-specific SSL policy. 
 This article describes how to use the Azure portal to configure listener-specific SSL policies on your Application Gateway. Listener-specific SSL policies allow you to configure specific listeners to use different SSL policies from each other. You'll still be able to set a default SSL policy that all listeners use unless overwritten by the listener-specific SSL policy. 
 
 > [!IMPORTANT]
 > Starting **August 31, 2025**, all clients and backend servers interacting with Azure Application Gateway must use Transport Layer Security (TLS) 1.2 or higher, as [support for TLS 1.0 and 1.1 will be discontinued](https://azure.microsoft.com/updates/azure-application-gateway-support-for-tls-10-and-tls-11-will-end-by-31-august-2025).
 
 > [!NOTE]
-> Only Standard_v2 and WAF_v2 SKUs support listener specific policies as listener specific policies are part of SSL profiles, and SSL profiles are only supported on v2 gateways. 
+> Only Standard_v2 and WAF_v2 SKUs support listener-specific policies. Listener-specific policies are part of SSL profiles, and SSL profiles are only supported on v2 Application Gateways. 
 
 
 
-If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+## Prerequisites
+
+Before you begin, ensure you have:
+
+- An Azure subscription. If you don't have one, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+- An existing Azure Application Gateway (Standard_v2 or WAF_v2 SKU)
+- Appropriate permissions to modify Application Gateway configurations
 
 ## Create a new Application Gateway
 
+First, create a new Application Gateway as you would normally through the portal. There are no more steps needed during creation to configure listener-specific SSL policies. For more information on how to create an Application Gateway in the portal, see the [portal quickstart tutorial](./quick-create-portal.md).
+
 First create a new Application Gateway as you would usually through the portal - there are no extra steps needed in the creation to configure listener-specific SSL policies. For more information on how to create an Application Gateway in portal, check out our [portal quickstart tutorial](./quick-create-portal.md).
 
 ## Set up a listener-specific SSL policy
 
-Before you proceed, here are some important points related to listener-specific SSL policy.
+Before you proceed, here are some important considerations for listener-specific SSL policies:
+
+SSL-Policies
+- We recommend using TLS 1.2 or higher
+- You don't need to configure client authentication on an SSL profile to associate it with a listener. You can configure only client authentication, only listener-specific SSL policy, or both in your SSL profile.
+- Use a [2022 Predefined](./application-gateway-ssl-policy-overview.md#predefined-tls-policy) or Custom v2 policy, enhances SSL security and performance for the entire Application Gateway (SSL Policy and SSL Profile). Therefore, you can't have different listeners using both legacy and new SSL policies simultaneously.
 
 - We recommend using TLS 1.2 as this version will be mandated in the future.
 - You don't have to configure client authentication on an SSL profile to associate it to a listener. You can have only client authentication or listener-specific SSL policy configured, or both configured in your SSL profile.
 - Using a [2022 Predefined](./application-gateway-ssl-policy-overview.md#predefined-tls-policy) or Customv2 policy enhances SSL security and performance for the entire gateway (SSL Policy and SSL Profile). Therefore, you cannot have different listeners on both old and new SSL (predefined or custom) policies.
 
-  Consider this example, you're currently using SSL Policy and SSL Profile with "older" policies/ciphers. To use a "new" Predefined or Customv2 policy for any one of them will also require you to upgrade the other configuration. You may use the new predefined policies, or customv2 policy, or combination of these across the gateway.
+  **Example scenario**: If you're currently using SSL Policy and SSL Profile with "legacy" policies/ciphers, upgrading to a "new" Predefined or Custom v2 policy for any component requires upgrading the other configuration as well. You can use the new predefined policies, Custom v2 policy, or a combination.
+
+SSL-Policies
+To set up a listener-specific SSL policy, you need to first go to the **SSL settings** tab in the Azure portal and create a new SSL profile. When you create an SSL profile, you see two tabs: **Client Authentication** and **SSL Policy**. The **SSL Policy** tab is used to configure a listener-specific SSL policy. The **Client Authentication** tab is where you upload client certificates for mutual authentication. For more information, see [Configuring mutual authentication](./mutual-authentication-portal.md).
 
 To set up a listener-specific SSL policy, you need to first go to the **SSL settings** tab in the Portal and create a new SSL profile. When you create an SSL profile, you see two tabs: **Client Authentication** and **SSL Policy**. The **SSL Policy** tab is to configure a listener-specific SSL policy. The **Client Authentication** tab is where to upload a client certificate for mutual authentication - for more information, check out [Configuring a mutual authentication](./mutual-authentication-portal.md).
 
-1. Search for **Application Gateway** in portal, select **Application gateways**, and click on your existing Application Gateway.
+1. Search for **Application Gateway** in the portal, select **Application gateways**, and select your existing Application Gateway.
 
 2. Select **SSL settings** from the left-side menu.
 
-3. Click on the plus sign next to **SSL Profiles** at the top to create a new SSL profile.
+3. Select the plus sign next to **SSL Profiles** at the top to create a new SSL profile.
+
+4. Enter a name under **SSL Profile Name**. In this example, we name our SSL profile *applicationGatewaySSLProfile*. 
 
-4. Enter a name under **SSL Profile Name**. In this example, we call our SSL profile *applicationGatewaySSLProfile*. 
+5. Go to the **SSL Policy** tab and check the **Enable listener-specific SSL Policy** checkbox. 
 
-5. Go to the **SSL Policy** tab and check the **Enable listener-specific SSL Policy** box. 
+6. Configure your listener-specific SSL policy according to your requirements. You can choose between predefined SSL policies and customizing your own SSL policy. For more information on SSL policies, see [SSL policy overview](./application-gateway-ssl-policy-overview.md). We recommend using TLS 1.2 or higher.
 
-6. Set up your listener-specific SSL policy given your requirements. You can choose between predefined SSL policies and customizing your own SSL policy. For more information on SSL policies, visit [SSL policy overview](./application-gateway-ssl-policy-overview.md). We recommend using TLS 1.2
+   > [!NOTE]
+   > This policy is the latest version of the SSL policy available, which is recommended to ensure the best SSL security. If your gateway is configured to handle older traffic, you may need to choose an older policy to ensure that all traffic is handled correctly.
 
 7. Select **Add** to save.
 
-    ![Add listener specific SSL policy to SSL profile](./media/application-gateway-configure-listener-specific-ssl-policy/listener-specific-ssl-policy-ssl-profile.png)
+    :::image type="content" source="./media/application-gateway-configure-listener-specific-ssl-policy/listener-specific-ssl-policy-ssl-profile.png" alt-text="Screenshot of adding listener-specific SSL policy to SSL profile in Azure portal.":::
 
 ## Associate the SSL profile with a listener
 
-Now that we've created an SSL profile with a listener-specific SSL policy, we need to associate the SSL profile to the listener to put the listener-specific policy in action. 
+Now you created an SSL profile with a listener-specific SSL policy. You need to associate the SSL profile with the listener to activate the listener-specific policy. 
 
-1. Navigate to your existing Application Gateway. If you just completed the steps above, you don't need to do anything here. 
+1. Navigate to your existing Application Gateway.
 
 2. Select **Listeners** from the left-side menu. 
 
-3. Click on **Add listener** if you don't already have an HTTPS listener set up. If you already have an HTTPS listener, click on it from the list. 
+3. Select on **Add listener** if you don't already have an HTTPS listener set up. If you already have an HTTPS listener, Select on it from the list.
 
-4. Fill out the **Listener name**, **Frontend IP**, **Port**, **Protocol**, and other **HTTPS Settings** to fit your requirements.
+4. Fill out the **Listener name**, **Frontend IP**, **Port**, and other HTTPS Settings to fit your requirements.
 
-5. Check the **Enable SSL Profile** checkbox so that you can select which SSL Profile to associate with the listener. 
+5. Select Add to save your new listener with the SSL profile associated to it.
 
-6. Select the SSL profile you created from the dropdown list. In this example, we choose the SSL profile we created from the earlier steps: *applicationGatewaySSLProfile*. 
+6.  Check to see **SSL Policy** is correct or select **Change** for choose another SSL Policy. The options available include:
+    - Default
+    - Predefined
+    - Custom
+    - CustomV2
+Select the SSL profile you created from the dropdown list. In this example, we choose the SSL profile created in the earlier steps: *applicationGatewaySSLProfile*. 
 
-7. Continue configuring the remainder of the listener to fit your requirements. 
+7. Select on tab **Listener TLS Certificates** on the second tab. 
 
-8. Click **Add** to save your new listener with the SSL profile associated to it. 
+8. Select **+ Add Certificate**.
 
-    ![Associate SSL profile to new listener](./media/mutual-authentication-portal/mutual-authentication-listener-portal.png)        
+9. Fill out the **Certificate name**, **PFX Certificate File**, **Type** , and other **Password** to fit your requirements.
+
+10. Select **Add** to save your new listener TLS Certificate with the SSL profile associated to it.
+
+11. Continue configuring the remainder of the listener according to your requirements. 
+
+    :::image type="content" source="./media/application-gateway-configure-listener-specific-ssl-policy/listener-certificate.png" alt-text="Screenshot of SSL profile association for a new listener.":::   
 
 ### Limitations
+SSL-Policies
+
+There are current limitations with Azure Application Gateway regarding SSL policies:
+
+- Different listeners using the same port can't have SSL policies (predefined or custom) with different TLS protocol versions. 
+- Configuring the same TLS version for different listeners works for setting cipher suite preferences for each listener. 
+- To use different TLS protocol versions for separate listeners, you must use distinct ports for each listener.
 There is a limitation right now on Application Gateway that different listeners using the same port cannot have SSL policies (predefined or custom) with different TLS protocol versions. Choosing the same TLS version for different listeners work for configuring cipher suite preference for each listener. However, to use different TLS protocol versions for separate listeners, you need to use distinct ports for each.
 
 ## Next steps