Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+	{
+            "source_path": "articles/communication-services/tutorials/file-sharing-tutorial.md",
+            "redirect_URL": "/azure/communication-services/tutorials/file-sharing-tutorial-acs-chat",
+            "redirect_document_id": false
+        },
         {
           "source_path": "articles/azure-resource-manager/bicep/bicep-import-providers.md",
           "redirect_URL": "bicep-import",
@@ -24477,9 +24482,9 @@
             "redirect_document_id": false
         },
         {
-          "source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
-          "redirect_url": "/azure/azure-functions/functions-bindings-cache",
-          "redirect_document_id": false
+            "source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
+            "redirect_url": "/azure/azure-functions/functions-bindings-cache",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-configure-authentication.md",
@@ -24511,6 +24516,21 @@
             "redirect_url": "/azure/bastion/bastion-connect-vm-ssh-linux",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/app-service/overview-disaster-recovery.md",
+            "redirect_url": "/azure/reliability/reliability-app-service",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-functions/functions-geo-disaster-recovery.md",
+            "redirect_url": "/azure/reliability/reliability-functions",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/hdinsight/hdinsight-business-continuity.md",
+            "redirect_url": "/azure/reliability/reliability-hdinsight",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/reliability/reliability-postgre-flexible.md",
             "redirect_url": "/azure/reliability/reliability-postgresql-flexible-server",
@@ -24531,8 +24551,5 @@
             "redirect_url": "/azure/orbital/overview",
             "redirect_document_id": false
         }
-
-
-        
     ]
 }

articles/active-directory/authentication/concept-authentication-phone-options.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 09/13/2023
+ms.date: 09/23/2023
 
 ms.author: justinha
 author: justinha
@@ -40,7 +40,7 @@ If users don't want their mobile phone number to be visible in the directory but
 Microsoft doesn't guarantee consistent text message or voice-based Microsoft Entra multifactor authentication prompt delivery by the same number. In the interest of our users, we may add or remove short codes at any time as we make route adjustments to improve text message deliverability. Microsoft doesn't support short codes for countries/regions besides the United States and Canada.
 
 > [!NOTE]
-> Starting July 2023, we will apply delivery method optimizations such that tenants with a free or trial subscription may receive a text message or voice call.
+> We apply delivery method optimizations such that tenants with a free or trial subscription may receive a text message or voice call.
 
 ### Text message verification
 
@@ -52,7 +52,9 @@ Android users can enable RCS on their devices. RCS offers encryption and other i
 
 :::image type="content" source="media/concept-authentication-methods/brand.png" alt-text="Screenshot of Microsoft branding in RCS messages.":::
 
-Some users with phone numbers that have country codes belonging to India, Indonesia and New Zealand may receive their verification codes via WhatsApp. Like RCS, these messages are similar to SMS, but have more Microsoft branding and a verified checkmark. Only users that have WhatsApp will receive verification codes via this channel. To determine whether a user has WhatsApp, we silently attempt delivering them a message via the app using the phone number they already registered for text message verification and see if it's successfully delivered. If users don't have any internet connectivity or uninstall WhatsApp, they'll receive their verification codes via SMS. The phone number associated with Microsoft's WhatsApp Business Agent is: *+1 (217) 302 1989*.
+Some users with phone numbers that have country codes belonging to India, Indonesia, and New Zealand may receive their verification codes in WhatsApp. Like RCS, these messages are similar to SMS, but have more Microsoft branding and a verified checkmark. Only users that have WhatsApp receive verification codes via this channel. To check if a user has WhatsApp, we silently try to deliver them a message in the app by using the phone number they registered for text message verification. If users don't have any internet connectivity or uninstall WhatsApp, they'll receive SMS verification codes. The phone number associated with Microsoft's WhatsApp Business Agent is: *+1 (217) 302 1989*.
+
+:::image type="content" border="true" source="media/concept-authentication-methods/code.png" alt-text="Screenshot of confirmation.":::
 
 ### Phone call verification
 
@@ -69,9 +71,9 @@ With office phone call verification during SSPR or Microsoft Entra multifactor a
 If you have problems with phone authentication for Microsoft Entra ID, review the following troubleshooting steps:
 
 * "You've hit our limit on verification calls" or "You've hit our limit on text verification codes" error messages during sign-in
-   * Microsoft may limit repeated authentication attempts that are performed by the same user or organization in a short period of time. This limitation does not apply to Microsoft Authenticator or verification codes. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes.
+   * Microsoft may limit repeated authentication attempts that are performed by the same user or organization in a short period of time. This limitation doesn't  apply to Microsoft Authenticator or verification codes. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes.
 * "Sorry, we're having trouble verifying your account" error message during sign-in
-   * Microsoft may limit or block voice or text message authentication attempts that are performed by the same user, phone number, or organization due to high number of voice or text message authentication attempts. If you are experiencing this error, you can try another method, such as Authenticator App or verification code, or reach out to your admin for support.
+   * Microsoft may limit or block voice or text message authentication attempts that are performed by the same user, phone number, or organization due to high number of voice or text message authentication attempts. If you experience this error, you can try another method, such as Authenticator or verification code, or reach out to your admin for support.
 * Blocked caller ID on a single device.
    * Review any blocked numbers configured on the device.
 * Wrong phone number or incorrect country/region code, or confusion between personal phone number versus work phone number.

articles/active-directory/authentication/media/concept-authentication-methods/code.png

@@ -6,7 +6,7 @@ author: asudbring
 ms.author: allensu
 ms.subservice: aks-networking
 ms.topic: how-to
-ms.date: 02/27/2023
+ms.date: 09/22/2023
 
 #Customer intent: As a cluster operator or developer, I want to create and manage static IP address resources in Azure that I can use beyond the lifecycle of an individual Kubernetes service deployed in an AKS cluster.
 ---
@@ -91,6 +91,7 @@ This article shows you how to create a static public IP address and assign it to
       annotations:
         service.beta.kubernetes.io/azure-load-balancer-resource-group: <node resource group>
         service.beta.kubernetes.io/azure-load-balancer-ipv4: <public IP address>
+        service.beta.kubernetes.io/azure-pip-name: <public IP Name>
       name: azure-load-balancer
     spec:
       type: LoadBalancer
@@ -100,6 +101,9 @@ This article shows you how to create a static public IP address and assign it to
         app: azure-load-balancer
     ```
 
+    > [!NOTE]
+    > Adding the `service.beta.kubernetes.io/azure-pip-name` annotation ensures the most efficient LoadBalancer creation and is highly recommended to avoid potential throttling. 
+
 3. Set a public-facing DNS label to the service using the `service.beta.kubernetes.io/azure-dns-label-name` service annotation. This publishes a fully qualified domain name (FQDN) for your service using Azure's public DNS servers and top-level domain. The annotation value must be unique within the Azure location, so we recommend you use a sufficiently qualified label. Azure automatically appends a default suffix in the location you selected, such as `<location>.cloudapp.azure.com`, to the name you provide, creating the FQDN.
 
     > [!NOTE]
@@ -112,6 +116,7 @@ This article shows you how to create a static public IP address and assign it to
       annotations:
         service.beta.kubernetes.io/azure-load-balancer-resource-group: <node resource group>
         service.beta.kubernetes.io/azure-load-balancer-ipv4: <public IP address>
+        service.beta.kubernetes.io/azure-pip-name: <public IP Name>
         service.beta.kubernetes.io/azure-dns-label-name: <unique-service-label>
       name: azure-load-balancer
     spec:

articles/aks/static-ip.md

@@ -1,10 +1,14 @@
+items:
 - name: Azure
   tocHref: /azure/
   topicHref: /azure/index
   items:
   - name: App Service
     tocHref: /azure/app-service/
     topicHref: /azure/app-service/index
+  - name: App Service
+    tocHref: /azure/reliability/
+    topicHref: /azure/app-service/index
     items:
     - name: Web Apps
       tocHref: /azure/active-directory/fundamentals/