Merge branch 'MicrosoftDocs:main' into main

Author: jainsabal

.openpublishing.redirection.json

@@ -6963,8 +6963,12 @@
       "source_path": "articles/reliability/migrate-sql-database.md",
       "redirect_url": "/azure/azure-sql/database/enable-zone-redundancy",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/reliability/migrate-app-gateway-v2.md",
+      "redirect_url": "/azure/reliability/reliability-application-gateway-v2",
+      "redirect_document_id": false
     }
-    
   ]
 }
 

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

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 07/15/2025
+ms.date: 07/29/2025
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -211,17 +211,22 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 261 | Madagascar | 10 | 30 |
 | 263 | Zimbabwe | 10 | 30 |
 | 265 |	Malawi  |	10	| 30 |
+| 266 | Lesotho | 10 | 30 |
+| 359 | Bulgaria | 20 | 100 
 | 373 |	Moldova |	20	| 100 |
 | 375 |	Belarus   |	10	| 30 |
+| 380 | Ukraine | 50 | 200 |
 | 381 | Serbia | 50 | 200 |
 | 386 | Slovenia | 10 | 50 |
 | 501 |  Belize| 10  |  30  |
-| 502 | Guatemala | 10 | 50 
+| 502 | Guatemala | 10 | 50 | 
 | 503 | El Salvador | 10 | 30 |
+| 504 | Honduras | 50 | 200 |
 | 52 | Mexico | 100 | 500 |
 | 53 | Cuba | 10 | 30 |
 | 58 |	Venezuela|	10	| 30 |
 | 591 | Bolivia | 10 | 30 |
+| 593 | Ecuador | 20 | 100 |
 | 60 | Malaysia | 50 | 200 |
 | 62 |  Indonesia | 50  |  200 |
 | 63 |  Philippines   | 50  |  200 |
@@ -239,6 +244,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 961 |	Lebanon  |	10	| 30 |
 | 963 |	Syria  |	10	| 30 |
 | 964 | Iraq | 50 | 200 |
+| 965 | Kuwait | 50 | 200 |
 | 967 |	Yemen	|10	| 30 |
 | 970 |  State of Palestine| 10  |  30  |
 | 972 |	Israel  |	50	| 200 |
@@ -250,7 +256,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 994 | Azerbaijan | 50 | 200 | 
 | 995 | Georgia | 10 | 30 |
 | 996 |	Kyrgyzstan  |	10	| 30 |
-| 998 | Uzbekistan | 10 | 30 
+| 998 | Uzbekistan | 10 | 30 |
 
 ## Next steps
 

articles/application-gateway/.openpublishing.redirection.application-gateway.json

@@ -344,6 +344,11 @@
             "source_path_from_root": "/articles/application-gateway/scripts/waf-custom-rules-powershell.md",
             "redirect_url": "/previous-versions/azure/application-gateway/scripts/waf-custom-rules-powershell",
             "redirect_document_id": false
+        },
+        {
+           "source_path_from_root": "/articles/application-gateway/classic-to-resource-manager.md",
+           "redirect_url": "/azure/virtual-machines/migration/migration-classic-resource-manager-faq",
+           "redirect_document_id": false
         }
     ]
 }

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

@@ -37,6 +37,7 @@ For scale-in events, Application Gateway drains existing connections for 5 minut
 
 ## Next steps
 
+- Learn more about zone redundancy in [Reliability for Application Gateway v2](../reliability/reliability-application-gateway-v2.md)
 - Learn how to [Schedule autoscaling for Application Gateway](application-gateway-externally-managed-scheduled-autoscaling.md)
 - Learn more about [Application Gateway v2](overview-v2.md)
 - [Create an autoscaling, zone redundant application gateway with a reserved virtual IP address using Azure PowerShell](tutorial-autoscale-ps.md)

articles/application-gateway/application-gateway-tls-version-retirement.md

@@ -5,7 +5,7 @@ services: application gateway
 author: jaesoni
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 07/29/2025
+ms.date: 07/31/2025
 ms.author: mbender
 ms.custom:
   - build-2025
@@ -14,7 +14,7 @@ ms.custom:
 
 # Managing your Application Gateway with TLS 1.0 and 1.1 retirement
 
-Starting **31st August 2025**, Azure Application Gateway will no longer support **TLS (Transport Layer Security) versions 1.0 and 1.1**. This change aligns with the [Azure-wide retirement](https://azure.microsoft.com/updates?id=update-retirement-tls1-0-tls1-1-versions-azure-services) of these TLS versions to enhance the security. As the owner of an Application Gateway resource, you should review both the Frontend clients and Backend servers TLS connections that may be using these older versions.
+On **31st August 2025**, Azure Application Gateway will no longer support **TLS (Transport Layer Security) versions 1.0 and 1.1**. This change aligns with the [Azure-wide retirement](https://azure.microsoft.com/updates?id=update-retirement-tls1-0-tls1-1-versions-azure-services) of these TLS versions to enhance the security. As the owner of an Application Gateway resource, you should review both the Frontend clients and Backend servers TLS connections that can be using these older versions.
 
 ## Frontend TLS connections
 
@@ -29,7 +29,7 @@ With deprecation of TLS versions 1.0 and 1.1, the **older Predefined TLS policie
 
 ### Predefined policies for V2 SKUs
 
-The predefined policies 20150501 and 20170401 that support TLS v1.0 and 1.1 will be discontinued and can no longer be associated with an Application Gateway resource after August 2025. It's advised to transition to one of the recommended TLS policies, 20220101 or 20220101S. Alternatively, the 20170401S policy may be used if specific cipher suites are required. 
+The predefined policies 20150501 and 20170401 that support TLS v1.0 and 1.1 will be discontinued and can no longer be associated with an Application Gateway resource after August 2025. Transition to one of the recommended TLS policies, 20220101 or 20220101S is advised. Alternatively, the 20170401S policy can be used if specific cipher suites are required. 
 
 ![A diagram showing predefined policies for V2 SKUs.](media/application-gateway-tls-version-retirement/v2-retiring-tls-policies.png)
 
@@ -102,11 +102,44 @@ To determine whether clients connecting to your Application Gateway resource are
 You can also check the [Application Gateway Access logs](monitor-application-gateway-reference.md#access-log-category) to view this information in log format.
 
 > [!NOTE]
-> The metrics and logs for the V1 SKUs do not provide client TLS protocol information.
+> The metrics and logs for the V1 SKUs don't provide client TLS protocol information.
 
 ### Error information
 Once support for TLS versions 1.0 and 1.1 is discontinued, clients may encounter errors such as `curl: (35) error:0A000410:SSL routines::sslv3 alert handshake failure`. Depending on the browser being used, various messages indicating TLS handshake failures may be displayed.
 
+## FAQs
+
+### What does a default TLS policy mean?
+A default TLS policy for Application Gateway is a packaged set of supported TLS versions and cipher suites. This allows customers to begin using secured traffic by only configuring HTTPS or TLS listeners and backend settings, without any extra configuration for TLS version or ciphers. Application Gateway uses one of its predefined policies as the default.
+
+### How will the default TLS policies be impacted after legacy TLS versions 1.0 and 1.1 retirement?
+Until September 2025, V2 SKUs utilize two [default TLS policies](application-gateway-ssl-policy-overview.md#default-tls-policy) based on the API version specified during resource deployment. Deployments using API version **2023-02-01 or later** apply `AppGwSslPolicy20220101` by default, while earlier API versions use `AppGwSslPolicy20150501`. With the deprecation of TLS 1.0 and 1.1, the older `AppGwSslPolicy20150501` policy, will be discontinued. So, `AppGwSslPolicy20220101` will become the default policy for all V2 gateways.
+
+The default policy for the V1 SKU will remain unchanged since `AppGwSslPolicy20220101` won't be introduced for this retiring SKU.
+
+> [!NOTE]
+> A default TLS policy is applied only when the "Default" option is selected in the Portal or when no TLS policy is specified within the resource configuration by means such as REST, PowerShell, or AzCLI.
+> 
+> Accordingly, using a default policy in configuration isn't same as explicitly selecting `AppGwSslPolicy20150501` policy, even if `AppGwSslPolicy20150501` is the default policy for your API version.
+
+### Which TLS policies in Application Gateway are getting deprecated?
+The predefined policies `AppGwSslPolicy20150501` and `AppGwSslPolicy20170401` that support TLS versions 1.0 and 1.1 will be removed from the Azure Resource Manager configuration. Similarly, the Custom policy will stop supporting TLS versions 1.0 and 1.1 along with their associated cipher suites. This applies to both V1 and V2 SKUs.
+
+### Will Application Gateway product team automatically update the configuration to a supported TLS policy? 
+Application Gateway won't modify any resource having customer-defined TLS configurations. Only the default TLS policy for gateways that have not explicitly set a TLS policy or lack any TLS-related settings (such as HTTPS or TLS listeners) will be automatically updated to use `AppGwSslPolicy20220101`.
+
+### Will my gateway go in a Failed state?
+If you have chosen any deprecating TLS policy in the configuration of your gateway and don’t update it to a supported policy by August 2025, your gateway will enter a Failed state when performing a configuration update.
+
+A nonfunctional TLS configuration, such a SSLProfile not linked to any listener, won't have any impact on the control plane of the gateway.
+
+### How is the release for this change planned?
+Given the scale of our fleet, after 30 August 2025, the deprecation of TLS versions will be implemented separately for the Data and Control Planes (in that order). Any region-specific details won't be available; therefore, we strongly advise you to take all necessary actions before this retirement date.
+
+### Is there any potential impact if I haven’t selected any TLS policy and my gateway uses only HTTP/TCP configurations?
+If your gateway doesn't use any TLS configuration—either through SSLPolicy, SSLProfile, HTTPS, or TLS Listeners—there will be no impact after August 2025.
+
+
 
 ## Next steps