Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into add-logic-app

Author: johnkemnetz

articles/active-directory/enterprise-users/groups-assign-sensitivity-labels.md

@@ -69,7 +69,7 @@ To apply published labels to groups, you must first enable the feature. These st
 1. Save the changes and apply the settings:
 
     ```powershell
-    Set-AzureADDirectorySetting -Id grpUnifiedSetting.Id -DirectorySetting $setting
+    Set-AzureADDirectorySetting -Id $grpUnifiedSetting.Id -DirectorySetting $setting
     ```
 
 You will also need to synchronize your sensitivity labels to Azure AD. For instructions, see [How to enable sensitivity labels for containers and synchronize labels](/microsoft-365/compliance/sensitivity-labels-teams-groups-sites#how-to-enable-sensitivity-labels-for-containers-and-synchronize-labels).

articles/active-directory/fundamentals/whats-new.md

@@ -95,7 +95,7 @@ The following new capabilities have been added to the claims transformations ava
 
 ---
 
-### Public preview - Flagged  
+### Public Preview – Flagged Sign-ins  
 
 **Type:** New feature  
 **Service category:** Reporting  

articles/active-directory/identity-protection/howto-identity-protection-configure-risk-policies.md

@@ -78,8 +78,12 @@ Before enabling remediation policies, organizations may want to [investigate](ho
    1. Under **Exclude**, select **Users and groups** and choose your organization's emergency access or break-glass accounts. 
    1. Select **Done**.
 1. Under **Cloud apps or actions** > **Include**, select **All cloud apps**.
-1. Under **Conditions** > **User risk**, set **Configure** to **Yes**. Under **Configure user risk levels needed for policy to be enforced** select **High**, then select **Done**.
-1. Under **Access controls** > **Grant**, select **Grant access**, **Require password change**, and select **Select**.
+1. Under **Conditions** > **User risk**, set **Configure** to **Yes**. 
+   1. Under **Configure user risk levels needed for policy to be enforced** select **High**.
+   1. Select **Done**.
+1. Under **Access controls** > **Grant**.
+   1. Select **Grant access**, **Require password change**.
+   1. Select **Select**.
 1. Confirm your settings, and set **Enable policy** to **On**.
 1. Select **Create** to create to enable your policy.
 
@@ -97,7 +101,9 @@ Before enabling remediation policies, organizations may want to [investigate](ho
 1. Under **Conditions** > **Sign-in risk**, set **Configure** to **Yes**. Under **Select the sign-in risk level this policy will apply to** 
    1. Select **High** and **Medium**.
    1. Select **Done**.
-1. Under **Access controls** > **Grant**, select **Grant access**, **Require multi-factor authentication**, and select **Select**.
+1. Under **Access controls** > **Grant**.
+   1. Select **Grant access**, **Require multi-factor authentication**.
+   1. Select **Select**.
 1. Confirm your settings and set **Enable policy** to **On**.
 1. Select **Create** to create to enable your policy.
 

articles/app-service/configure-connect-to-azure-storage.md

@@ -21,7 +21,7 @@ This guide shows how to mount Azure Storage Files as a network share in a Window
 
 ::: zone pivot="container-linux"
 
-This guide shows how to mount Azure Storage as a network share in a built-in Linux container or a custom Linux container in App Service. The benefits of custom-mounted storage include:
+This guide shows how to mount Azure Storage as a network share in a built-in Linux container or a custom Linux container in App Service. See the video [how to mount Azure Storage as a local share](https://www.youtube.com/watch?v=OJkvpWYr57Y). The benefits of custom-mounted storage include:
 
 ::: zone-end
 
@@ -94,6 +94,7 @@ The following features are supported for Linux containers:
 - FTP/FTPS access to custom-mounted storage is not supported (use [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/)).
 - Azure CLI, Azure PowerShell, and Azure SDK support is in preview.
 - Mapping `/` or `/home` to custom-mounted storage is not supported.
+- Don't map the custom storage mount to `/tmp` or its subdirectories as this may cause timeout during app startup.
 - Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
 - Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts. 
 
@@ -243,5 +244,6 @@ To validate that the Azure Storage is mounted successfully for the app:
 ::: zone pivot="container-linux"
 
 - [Configure a custom container](configure-custom-container.md?pivots=platform-linux).
+- [Video: How to mount Azure Storage as a local share](https://www.youtube.com/watch?v=OJkvpWYr57Y).
 
-::: zone-end
+::: zone-end

articles/applied-ai-services/form-recognizer/managed-identity-byos.md

@@ -24,6 +24,10 @@ Azure managed identity is a service principal that creates an Azure Active Direc
 Managed identity supports both privately and publicly accessible Azure blob storage accounts.  For storage accounts with public access, you can opt to use a shared access signature (SAS) to grant limited access.   In this article, you'll learn to enable a system-assigned managed identity for your Form Recognizer instance.
 
 ## Private storage account access
+> [!NOTE]
+>
+> Form Recognizer only supports system-assigned managed identities today. User-assigned managed identities is on the roadmap and will be enabled in the near future. 
+
 
  Private Azure storage account access and authentication is supported by [managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md). If you have an Azure storage account protected by a Virtual Network (VNet) or firewall or have enabled bring-your-own-storage (BYOS), Form Recognizer cannot directly access your storage account data; however, once a managed identity is enabled, the Form Recognizer service can access your storage account using an assigned managed identity credential.
 

articles/automation/automation-dsc-diagnostics.md

@@ -5,7 +5,7 @@ services: automation
 ms.service: automation
 ms.subservice: dsc
 author: mgoedtel
-ms.author: magoedte
+ms.author: v-ssudhir
 ms.date: 08/16/2021
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell

articles/automation/automation-dsc-onboarding.md

@@ -5,7 +5,7 @@ services: automation
 ms.service: automation
 ms.subservice: dsc
 author: mgoedtel
-ms.author: magoedte
+ms.author: v-ssudhir
 ms.topic: conceptual
 ms.date: 12/10/2019 
 ms.custom: devx-track-azurepowershell

articles/automation/automation-dsc-overview.md

@@ -6,7 +6,7 @@ services: automation
 ms.service: automation
 ms.subservice: dsc
 author: mgoedtel
-ms.author: magoedte
+ms.author: v-ssudhir
 ms.date: 08/17/2021
 ms.topic: conceptual
 manager: carmonm

articles/automation/automation-network-configuration.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Automation network configuration details
 description: This article provides details of network information required by Azure Automation State Configuration, Azure Automation Hybrid Runbook Worker, Update Management, and Change Tracking and Inventory
-ms.author: magoedte
+ms.author: v-ssudhir
 ms.topic: conceptual
 ms.date: 01/26/2021
 ---

articles/automation/how-to/private-link-security.md

@@ -2,7 +2,7 @@
 title: Use Azure Private Link to securely connect networks to Azure Automation
 description: Use Azure Private Link to securely connect networks to Azure Automation
 author: mgoedtel
-ms.author: magoedte
+ms.author: v-ssudhir
 ms.topic: conceptual
 ms.date: 12/11/2020
 ms.subservice: