Merge branch 'main' of https://github.com/microsoftdocs/azure-docs-pr into ade-misc

Author: msmbaldwin

articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md

@@ -272,4 +272,4 @@ Follow these links to learn more about Node.js applications on Azure App Service
 * [Using Node.js Modules with Azure applications](/training/modules/create-nodejs-project-dependencies/)
 * [Azure App Service Web Apps: Node.js](/archive/blogs/silverlining/windows-azure-websites-node-js)
 * [Node.js Developer Center](../nodejs-use-node-modules-azure-apps.md)
-* [Exploring the Super Secret Kudu Debug Console](https://azure.microsoft.com/documentation/videos/super-secret-kudu-debug-console-for-azure-web-sites/)
+* [Exploring the Super Secret Kudu Debug Console](https://www.youtube.com/watch?v=-VjqyvA2XjM)

articles/app-service/environment/how-to-upgrade-preference.md

@@ -4,7 +4,7 @@ description: Configure the upgrade preference for the Azure App Service Environm
 author: madsd
 ms.topic: tutorial
 ms.custom: devx-track-azurecli
-ms.date: 06/25/2024
+ms.date: 11/05/2024
 zone_pivot_groups: app-service-cli-portal
 ---
 
@@ -34,10 +34,14 @@ In smaller regions, Early and Late upgrade preferences might be very close to ea
 
 Manual upgrade preference gives you the option to receive a notification when an upgrade is available. The availability is also visible in the Azure portal. After the upgrade is available, you'll have 15 days to start the upgrade process. If you don't start the upgrade within the 15 days, the upgrade is processed with the remaining automatic upgrades in the region.
 
+> [!IMPORTANT]
+> In rare cases, you might see an upgrade is available in the **Configuration** page for your App Service Environment, but you don't receive a **Service Health** notification (if you [configure notifications](#configure-notifications)). If you don't receive a Service Health notification, this available upgrade isn't required and the 15-day time limit doesn't apply. This is a known bug that we are working to fix.
+> 
+
 Upgrades normally don't affect the availability of your apps. The upgrade adds extra instances to ensure that the same capacity is available during upgrade. Patched and restarted instances are added back in rotation, and when you have workloads sensitive to restarts you should plan to start the maintenance during non-business hours. The full upgrade process normally finishes within 18 hours, but could take longer. Once the upgrade is started the upgrade runs until it's complete and isn't paused during standard business hours.
 
 > [!NOTE]
-> In rare cases the upgrade availability might be impacted by a security hotfix superseding the planned upgrade, or a regression found in the planned upgrade before it has been applied to your instance. In these rare cases, the available upgrade will be removed and will transition to automatic upgrade.
+> In rare cases, the upgrade availability might be impacted by a security hotfix superseding the planned upgrade, or a regression found in the planned upgrade before it has been applied to your instance. In these rare cases, the available upgrade will be removed and will transition to automatic upgrade.
 > 
 
 ## Configure notifications

articles/app-service/overview-authentication-authorization.md

@@ -172,9 +172,7 @@ When a request fulfills all these conditions, App Service authentication automat
 
 When using Azure App Service with authentication behind Azure Front Door or other reverse proxies, a few additional things have to be taken into consideration.
 
-- Disable caching for the authentication workflow.
-
-    See [Disable cache for auth workflow](../static-web-apps/front-door-manual.md#disable-cache-for-auth-workflow) to learn more on how to configure rules in Azure Front Door to disable caching for authentication and authorization-related pages.
+- Disable [Front Door caching](../frontdoor/front-door-caching.md) for the authentication workflow.
 
 - Use the Front Door endpoint for redirects.
 

articles/application-gateway/ssl-certificate-management.md

@@ -66,6 +66,14 @@ There are two primary scenarios when deleting a certificate from portal:
 | Port | The port associated with the listener gets updated to reflect the new state. | 
 | Frontend IP | The frontend IP of the gateway gets updated to reflect the new state. | 
 
+### Deletion of a listener with an SSL certificate
+
+When a listener with an associated SSL certificate is deleted, the SSL certificate itself is not deleted. The certificate will remain in the application gateway configuration and can be assigned to another listener. 
+
+### Deletion of a key vault certificate
+
+When deleting a certificate from key vault that is associated to an application gateway, the certificate must be deleted first on application gateway, then on key vault. 
+
 ### Bulk update
 The bulk operation feature is helpful for large gateways having multiple SSL certificates for separate listeners. Similar to individual certificate management, this option also allows you to change the type from "Uploaded" to "Key Vault" or vice-versa (if required). This utility is also helpful in recovering a gateway when facing misconfigurations for multiple certificate objects simultaneously.
 
@@ -84,7 +92,9 @@ To use the Bulk update option,
 1. You can't delete a certificate object if its associated listener is a redirection target for another listener. Any attempt to do so will return the following error. You can either remove the redirection or delete the dependent listener first to resolve this problem. 
 `The listener associated with this certificate is configured as the redirection target for another listener. You will need to either remove this redirection or delete the redirected listener first to allow deletion of this certificate.`
 
-1. The Application Gateway requires at least one active Listener and Rule combination. You thus cannot delete the certificate of a HTTPS listener, if no other active listener exists. This is also true if there are only HTTPS listeners on your gateway, and all of them are referencing the same certificate. Such operations are prevented because deletion of a certificate leads to deletion of all dependent sub resources. 
+1. The Application Gateway requires at least one active Listener and Rule combination. You thus cannot delete the certificate of an HTTPS listener, if no other active listener exists. This is also true if there are only HTTPS listeners on your gateway, and all of them are referencing the same certificate. Such operations are prevented because deletion of a certificate leads to deletion of all dependent sub resources. 
+
+1. If a certificate is deleted in key vault but the reference to the certificate in Application Gateway is not deleted, any update to the Application Gateway will cause it to appear in a failed state. To fix this, you must delete all the certificates without an associated listener one by one.
 
 
 ## Next steps

articles/azure-resource-manager/management/move-support-resources.md

@@ -806,7 +806,12 @@ Before starting your move operation, review the [checklist](./move-resource-grou
 > [!div class="mx-tableFixed"]
 > | Resource type | Resource group | Subscription | Region move |
 > | ------------- | ----------- | ---------- | ----------- |
-> | databaseaccounts | **Yes** | No | No |
+> | databaseaccounts | **Yes** | Partial | No |
+
+Moves between subscriptions are supported for APIs that use the RU architecture (Microsoft.DocumentDB/databaseAccounts), but not for those based on the vCore architecture, such as:
+
+- MongoDB vCore (Microsoft.DocumentDB/mongoClusters)
+- Azure Managed Instance for Apache Cassandra (Microsoft.DocumentDB/cassandraClusters)
 
 ## Microsoft.DomainRegistration
 

articles/communication-services/quickstarts/ui-library/get-started-calling-with-chat.md

@@ -1,7 +1,7 @@
 ---
 title: Add calling and chat functionality
 titleSuffix: An Azure Communication Services how-to guide
-description: Add calling and chat functionality using the Azure Communication Services UI Library.
+description: Add calling and chat functionality by using the Azure Communication Services UI Library.
 author: pavelprystinka
 
 ms.author: pprystinka
@@ -12,12 +12,12 @@ ms.date: 10/28/2024
 ms.custom: template-how-to
 zone_pivot_groups: acs-plat-ios-android
 
-#Customer intent: As a developer, I want to add calling and chat functionality to my App.
+#Customer intent: As a developer, I want to add calling and chat functionality to my app.
 ---
 
-# Integrate Calling and Chat UI Libraries
+# Integrate calling and chat by using the UI Library
 
-## Set up the feature
+In this article, you learn how to integrate calling and chat functionality in your Android or iOS app by using the Azure Communication Services UI Library.
 
 ::: zone pivot="platform-android"
 [!INCLUDE [Integrate Calling with Chat in the Android UI Library](./includes/get-started-calling-with-chat/android.md)]
@@ -27,20 +27,18 @@ zone_pivot_groups: acs-plat-ios-android
 [!INCLUDE [Integrate Calling with Chat in the iOS UI Library](./includes/get-started-calling-with-chat/ios.md)]
 ::: zone-end
 
-
 ## Run the code
 
-To build and run your app on the device.
+Run the code to build and run your app on the device.
 
 ### More features
 
-The list of [use cases](../../concepts/ui-library/ui-library-use-cases.md?branch=main&pivots=platform-mobile) has detailed information about more features.
+The [list of use cases](../../concepts/ui-library/ui-library-use-cases.md?branch=main&pivots=platform-mobile) has detailed information about more features.
 
 ## Add notifications to your mobile app
 
 Azure Communication Services integrates with [Azure Event Grid](../../../event-grid/overview.md) and [Azure Notification Hubs](../../../notification-hubs/notification-hubs-push-notification-overview.md), so you can [add push notifications](../../concepts/notifications.md) to your apps in Azure. You can use push notifications to send information from your application to users' mobile devices. A push notification can show a dialog, play a sound, or display an incoming call UI.
 
-
-## Next steps
+## Related content
 
 - [Learn more about the UI Library](../../concepts/ui-library/ui-library-overview.md)

articles/communication-services/quickstarts/ui-library/includes/get-started-calling-with-chat/android.md

@@ -13,41 +13,37 @@ ms.service: azure-communication-services
 - A deployed [Azure Communication Services resource](../../../create-communication-resource.md).
 - An Azure Communication Services [access token](../../../identity/quick-create-identity.md).
 
-## A complete sample
+## Get a complete sample
 
-You can get a [complete sample project](https://github.com/Azure-Samples/communication-services-calling-ui-with-chat-android) from the GitHub.
+You can get a [complete sample project](https://github.com/Azure-Samples/communication-services-calling-ui-with-chat-android) from GitHub.
 
-   :::image type="content" source="../../media/call-chat-android-experience.gif" alt-text="animation to showcase the experience on Android using call and chat in the same app.":::
+:::image type="content" source="../../media/call-chat-android-experience.gif" alt-text="Animation to showcase the experience on Android using call and chat in the same app.":::
 
 ## Set up the project
 
-Complete the following sections to set up the quickstart project.
-
-### Create a new Android project
-
 In Android Studio, create a new project:
 
-1. In the **File** menu, select **New** > **New Project**.
+1. On the **File** menu, select **New** > **New Project**.
 
 1. In **New Project**, select the **Empty Activity** project template.
 
    :::image type="content" source="../../media/composite-android-new-project.png" alt-text="Screenshot that shows the New Project dialog in Android Studio with Empty Activity selected.":::
 
 1. Select **Next**.
 
-1. In **Empty Activity**, name the project **UILibraryQuickStart**. For language, select **Java/Kotlin**. For the minimum SDK, select **API 26: Android 8.0 (Oreo)** or later.
+1. In **Empty Activity**, name the project **UILibraryQuickStart**. For language, select **Java** or **Kotlin**. For the minimum SDK, select **API 26: Android 8.0 (Oreo)** or later.
 
 1. Select **Finish**.
 
-   :::image type="content" source="../../media/composite-android-new-project-finish.png" alt-text="Screenshot that shows new project options and the Finish button selected.":::
+   :::image type="content" source="../../media/composite-android-new-project-finish.png" alt-text="Screenshot that shows new project options and the Finish button.":::
 
 ## Install the packages
 
 Complete the following sections to install the required application packages.
 
 ### Add a dependency
 
-In your app-level *UILibraryQuickStart/app/build.gradle* file (in the app folder), add the following dependency:
+In your app-level *UILibraryQuickStart/app/build.gradle* file, add the following dependency:
 
 ```groovy
 dependencies {
@@ -57,7 +53,8 @@ dependencies {
     ...
 }
 ```
-Add META-INF exclusion to the *UILibraryQuickStart/app/build.gradle* `android` section
+
+Add a `META-INF` exclusion to the *UILibraryQuickStart/app/build.gradle* `android` section:
 
 ```groovy
 packaging {
@@ -67,9 +64,9 @@ packaging {
 
 ### Add Maven repositories
 
-Two Maven repositories are required to integrate the library:
+You need two Maven repositories to integrate the library:
 
-- MavenCentral
+- The `mavenCentral` repository
 - The Azure package repository
 
     ```groovy
@@ -83,15 +80,13 @@ Two Maven repositories are required to integrate the library:
     }
     ```
 
+## Connect to the Teams meeting with calling and chat
 
-## Connect to the Teams Meeting with Calling and Chat
+You use `CallComposite` to connect to the call. After a user is admitted to the call, `CallComposite` notifies you by changing the status to `connected`. Then the user can be connected to the chat thread.
 
-- First we will use CallComposite to connect to the call
-- Once user is admitted to the call, CallComposite will notify us by changing status to `connected`
-- Then user can be connected to the chat thread
-- When user clicks `Chat button`, a custom button added to the CallComposite, CallComposite will be minimized and Chat is displayed
+When the user selects the **Chat** button, a custom button is added to `CallComposite`. `CallComposite` is minimized, and **Chat** appears in Teams.
 
-## Add button and chat container view to Activity_main.xml
+## Add a button and chat container view to Activity_main.xml
 
 In the *app/src/main/res/layout/activity_main.xml* layout file, add the following code to create a button to start the composite:
 
@@ -134,27 +129,27 @@ In the *app/src/main/res/layout/activity_main.xml* layout file, add the followin
 </androidx.constraintlayout.widget.ConstraintLayout>
 ```
 
-## Download a Chat Icon
+## Download a Chat icon
 
-- Download an icon from [here](https://github.com/microsoft/fluentui-system-icons/blob/master/android/library/src/main/res/drawable/ic_fluent_chat_24_regular.xml).
-- Save it to the *UILibraryQuickStart/app/src/main/res/drawable*
-- Open it and change `android:fillColor` to the `@color/white`
+1. Download an icon from the [GitHub repository](https://github.com/microsoft/fluentui-system-icons/blob/master/android/library/src/main/res/drawable/ic_fluent_chat_24_regular.xml).
+1. Save the icon to *UILibraryQuickStart/app/src/main/res/drawable*.
+1. Open the icon and change `android:fillColor` to `@color/white`.
 
-## Initialize the composites
+## Initialize the composite
 
-To initialize the Call composite:
+To initialize the call composite, go to `MainActivity` and update connection settings:
 
-- Go to `MainActivity` and update connection settings:
-    - Replace `TEAM_MEETING_LINK` with the Teams meeting link.
-    - Replace `ACS_ENDPOINT` with your ACS resource's endpoint.
-    - Replace `DISPLAY_NAME` with your name.
-    - Replace `USER_ID` with ACS user ID.
-    - Replace `USER_ACCESS_TOKEN` with your token.
+- Replace `TEAM_MEETING_LINK` with the Teams meeting link.
+- Replace `ACS_ENDPOINT` with your Azure Communication Services resource's endpoint.
+- Replace `DISPLAY_NAME` with your name.
+- Replace `USER_ID` with your Azure Communication Services user ID.
+- Replace `USER_ACCESS_TOKEN` with your token.
 
-### Get a Teams meeting chat thread for a Communication Services user
-The Teams meeting details can be retrieved using Graph APIs, detailed in [Graph documentation]()(/graph/api/onlinemeeting-createorget). The Communication Services Calling SDK accepts a full Teams meeting link or a meeting ID. They're returned as part of the `onlineMeeting` resource, accessible under the [joinWebUrl](/graph/api/resources/onlineMeeting) property
+### Get a Teams meeting chat thread for an Azure Communication Services user
 
-With the Graph APIs, you can also obtain the threadID. The response has a chatInfo object that contains the threadID.
+You can retrieve Teams meeting details by using Graph APIs, as described in the [Graph documentation](/graph/api/onlinemeeting-createorget). The Azure Communication Services Calling SDK accepts a full Teams meeting link or a meeting ID. They're returned as part of the `onlineMeeting` resource, which is accessible under the [joinWebUrl](/graph/api/resources/onlineMeeting) property.
+
+With the Graph APIs, you can also obtain the `threadID` value. The response has a `chatInfo` object that contains the `threadID` value.
 
 #### [Kotlin](#tab/kotlin)
 
@@ -234,8 +229,8 @@ class MainActivity : AppCompatActivity() {
             .build()
 
         callComposite.addOnCallStateChangedEventHandler { callState ->
-            // When user is admitted to the the Teams meeting, call state becoms connected.
-            // Only users admitted to the meeting, can connect the meeting's chat thread.
+            // When a user is admitted to the Teams meeting, the call state becomes connected.
+            // Only users admitted to the meeting can connect to the meeting's chat thread.
             if (callState.code == CallCompositeCallStateCode.CONNECTED) {
                 connectChat()
             }
@@ -367,8 +362,8 @@ public class MainActivity extends AppCompatActivity {
                 .build();
 
         callComposite.addOnCallStateChangedEventHandler(callState -> {
-                    // When user is admitted to the the Teams meeting, call state becoms connected.
-                    // Only users admitted to the meeting, can connect the meeting's chat thread.
+                    // When a user is admitted to the Teams meeting, the call state becomes connected.
+                    // Only users admitted to the meeting can connect to the meeting's chat thread.
                     if (callState.getCode() == CallCompositeCallStateCode.CONNECTED) {
                         connectChat();
                     }
@@ -419,4 +414,3 @@ public class MainActivity extends AppCompatActivity {
     }
 }
 ```
-