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

Author: Banani-Rath

.openpublishing.redirection.json

@@ -14000,11 +14000,6 @@
       "redirect_url": "/azure/blockchain/service/connect-vscode",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/blockchain/service/migration-guide.md",
-      "redirect_url": "/azure/blockchain/service/overview",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/blockchain/templates/ethereum-deployment.md",
       "redirect_url": "/azure/blockchain/templates/ethereum-poa-deployment",

.openpublishing.redirection.media-services.json

@@ -605,6 +605,11 @@
             "redirect_url": "transform-custom-preset-cli-how-to",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/media-services/video-indexer/observed-people-tracing.md",
+            "redirect_url": "azure/media-services/",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/media-services/latest/encode-custom-preset-rest-how-to.md",
             "redirect_url": "transform-custom-preset-rest-how-to",

articles/active-directory/devices/TOC.yml

@@ -49,7 +49,9 @@
     href: manage-stale-devices.md
   - name: Enable enterprise state roaming
     href: enterprise-state-roaming-enable.md
-  - name: Windows Azure VMs and Azure AD
+  - name: Azure Linux VMs and Azure AD
+    href: howto-vm-sign-in-azure-ad-linux.md
+  - name: Azure Windows VMs and Azure AD
     href: howto-vm-sign-in-azure-ad-windows.md
   - name: Virtual desktop infrastructure
     href: howto-device-identity-virtual-desktop-infrastructure.md

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -49,7 +49,8 @@ Most browser-based applications use session tokens instead of access and refresh
 
 ## Revoke access for a user in the hybrid environment
 
-For a hybrid environment with on-premises Active Directory synchronized with Azure Active Directory, Microsoft recommends IT admins to take the following actions. If you have an **Azure AD only environment**, you may skip the [On-premises Active Directory environment](https://docs.microsoft.com/azure/active-directory/enterprise-users/users-revoke-access#on-premises-active-directory-environment) section.
+For a hybrid environment with on-premises Active Directory synchronized with Azure Active Directory, Microsoft recommends IT admins to take the following actions. If you have an **Azure AD only environment**, skip to the [Azure Active Directory environment](https://docs.microsoft.com/azure/active-directory/enterprise-users/users-revoke-access#azure-active-directory-environment) section.
+
 
 ### On-premises Active Directory environment
 

articles/active-directory/enterprise-users/users-revoke-access.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: roles
 ms.topic: reference
-ms.date: 04/26/2021
+ms.date: 05/05/2021
 ms.author: rolyon
 ms.reviewer: vincesm
 ms.custom: it-pro, fasttrack-edit
@@ -62,6 +62,7 @@ This article lists the Azure AD built-in roles you can assign to allow managemen
 > | [Guest Inviter](#guest-inviter) | Can invite guest users independent of the 'members can invite guests' setting. | 95e79109-95c0-4d8e-aee3-d01accf2d47b |
 > | [Helpdesk Administrator](#helpdesk-administrator) | Can reset passwords for non-administrators and Helpdesk Administrators. | 729827e3-9c14-49f7-bb1b-9608f156bbb8 |
 > | [Hybrid Identity Administrator](#hybrid-identity-administrator) | Can manage AD to Azure AD cloud provisioning, Azure AD Connect, and federation settings. | 8ac3fc64-6eca-42ea-9e69-59f4c7b60eb2 |
+> | [Identity Governance Administrator](#identity-governance-administrator) | Manage access using Azure AD for identity governance scenarios. | 45d8d3c5-c802-45c6-b32a-1d70b5e1e86e |
 > | [Insights Administrator](#insights-administrator) | Has administrative access in the Microsoft 365 Insights app. | eb1f4a8d-243a-41f0-9fbd-c7cdf6c5ef7c |
 > | [Insights Business Leader](#insights-business-leader) | Can view and share dashboards and insights via the M365 Insights app. | 31e939ad-9672-4796-9c2e-873181342d2d |
 > | [Intune Administrator](#intune-administrator) | Can manage all aspects of the Intune product. | 3a2c62db-5318-420d-8d74-23affee5d9d5 |
@@ -1076,6 +1077,18 @@ Users in this role can create, manage and deploy provisioning configuration setu
 > | microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Microsoft 365 service requests |
 > | microsoft.office365.webPortal/allEntities/standard/read | Read basic properties on all resources in the Microsoft 365 admin center |
 
+## Identity Governance Administrator
+
+Users with this role can manage Azure AD identity governance configuration, including access packages, access reviews, catalogs and policies, ensuring access is approved and reviewed and guest users who no longer need access are removed.
+
+> [!div class="mx-tableFixed"]
+> | Actions | Description |
+> | --- | --- |
+> | microsoft.directory/accessReviews/allProperties/allTasks | Create and delete access reviews, and read and update all properties of access reviews in Azure AD |
+> | microsoft.directory/entitlementManagement/allProperties/allTasks | Create and delete resources, and read and update all properties in Azure AD entitlement management |
+> | microsoft.directory/groups/members/update | Update members of groups, excluding role-assignable groups |
+> | microsoft.directory/servicePrincipals/appRoleAssignedTo/update | Update service principal role assignments |
+
 ## Insights Administrator
 
 Users in this role can access the full set of administrative capabilities in the [M365 Insights application](https://go.microsoft.com/fwlink/?linkid=2129521). This role has the ability to read directory information, monitor service health, file support tickets, and access the Insights admin settings aspects.

articles/active-directory/roles/permissions-reference.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 12/10/2019
+ms.date: 05/10/2021
 ms.author: jeedes
 ---
 
@@ -158,6 +158,8 @@ After you've configured provisioning, use the following resources to monitor you
 
 * The Azure AD provisioning service currently operates under particular [IP ranges](../app-provisioning/use-scim-to-provision-users-and-groups.md#ip-ranges). If necessary, you can restrict other IP ranges and add these particular IP ranges to the allow list of your application. That technique will allow traffic flow from the Azure AD provisioning service to your application.
 
+* Self-hosted ServiceNow instances are not supported. 
+
 ## Additional resources
 
 * [Managing user account provisioning for enterprise apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)

articles/active-directory/saas-apps/servicenow-provisioning-tutorial.md

@@ -23,18 +23,22 @@ Keep your Azure Percept DK secure and up to date using over-the-air updates. In
 
 1. Go to the [Azure portal](https://portal.azure.com) and sign in with the Azure account you are using with Azure Percept.
 
-1. In the search bar at the top of the page, enter **Device Update for IoT Hub**.
+1. In the search bar at the top of the page, enter **Device Update for IoT Hubs**.
 
-1. Select **Device Update for IoT Hub** when it appears in the search bar.
+1. Select **Device Update for IoT Hubs** when it appears in the search bar.
 
-1. Click the **+Add** button in the upper-left portion of the page.
+1. Select the **+Add** button in the upper-left portion of the page.
 
 1. Select the **Azure Subscription** and **Resource Group** associated with your Azure Percept device and its IoT Hub.
 
 1. Specify a **Name** and **Location** for your Device Update Account.
 
+1. Check the box that says **Assign Device Update Administrator role.** 
+
 1. Review the details and select **Review + Create**.
 
+1. Select the **Create** button.
+
 1. Once deployment is complete, click **Go to resource**.
 
 ## Create a Device Update Instance

articles/azure-percept/how-to-set-up-over-the-air-updates.md

@@ -25,24 +25,24 @@ Follow this guide to learn how to update the OS and firmware of the carrier boar
 > [!NOTE]
 > If you have already imported the update, you can skip directly to **Create a device update group**.
 
-1. [Download the latest manifest file (.json)](https://go.microsoft.com/fwlink/?linkid=2155625) and [update file (.swu)](https://go.microsoft.com/fwlink/?linkid=2161538) for your Azure Percept device.
+1. Determine which [manifest and update package](./how-to-select-update-package.md) is appropriate for your dev kit.
 
 1. Navigate to the Azure IoT Hub that you are using for your Azure Percept device. On the left-hand menu panel, select **Device Updates** under **Automatic Device Management**.
 
 1. You will see several tabs across the top of the screen. Select the **Updates** tab.
 
 1. Select **+ Import New Update** below the **Ready to Deploy** header.
 
-1. Click on the boxes under **Select Import Manifest File** and **Select Update Files** to select your manifest file (.json) and update file (.swu).
+1. Select on the boxes under **Select Import Manifest File** and **Select Update Files** to select your manifest file (.json) and update file (.swu).
 
-1. Select the folder icon or text box under **Select a storage container** and select the appropriate storage account. If you’ve already created a storage container, you may re-use it. Otherwise, select **+ Container** to create a new storage container for OTA updates. Select the container you wish to use and click **Select**.
+1. Select the folder icon or text box under **Select a storage container** and select the appropriate storage account. If you’ve already created a storage container, you may reuse it. Otherwise, select **+ Container** to create a new storage container for OTA updates. Select the container you wish to use and click **Select**.
 
 1. Select **Submit** to start the import process. Due to the image size, the submission process may take up to 5 minutes.
 
     > [!NOTE]
     > You may be asked to add a Cross Origin Request (CORS) rule to access the selected storage container. Select **Add rule and retry** to proceed.
 
-1. When the import process begins, you will be redirected to the **Import History** tab of the **Device Updates** page. Click **Refresh** to monitor progress while the import process is completed. Depending on the size of the update, this may take a few minutes or longer (during peak times, the import service may to take up to 1 hour).
+1. When the import process begins, you will be redirected to the **Import History** tab of the **Device Updates** page. Click **Refresh** to monitor progress while the import process is completed. Depending on the size of the update, this may take a few minutes or longer (during peak times, the import service may take up to 1 hour).
 
 1. When the **Status** column indicates that the import has succeeded, select the **Ready to Deploy** tab and click **Refresh**. You should now see your imported update in the list.
 
@@ -58,15 +58,15 @@ Group Tag Requirements:
 - You can add any value to your tag except for "Uncategorized", which is a reserved value.
 - Tag value cannot exceed 255 characters.
 - Tag value can only contain these special characters: “.”,”-“,”_”,”~”.
-- Tag and group names are case sensitive.
+- Tag and group names are case-sensitive.
 - A device can only have one tag. Any subsequent tag added to the device will override the previous tag.
 - A device can only belong to one group.
 
 1. Add a Tag to your device(s):
 
 	1. From **IoT Edge** on the left navigation pane, find your Azure Percept DK and navigate to its **Device Twin**.
 
-	1. Add a new **Device Update for IoT Hub** tag value as shown below (```<CustomTagValue>``` refers to your tag value/name, e.g. AzurePerceptGroup1). Learn more about device twin [JSON document tags](../iot-hub/iot-hub-devguide-device-twins.md#device-twins).
+	1. Add a new **Device Update for IoT Hub** tag value as shown below (```<CustomTagValue>``` refers to your tag value/name, for example, AzurePerceptGroup1). Learn more about device twin [JSON document tags](../iot-hub/iot-hub-devguide-device-twins.md#device-twins).
 
         ```
         "tags": {

articles/azure-percept/how-to-update-over-the-air.md

@@ -1,28 +1,29 @@
 ---
-title: Update your Azure Percept DK over a USB connection
-description: Learn how to update the Azure Percept DK over a USB connection
+title: Update your Azure Percept DK over a USB-C cable connection
+description: Learn how to update the Azure Percept DK over a USB-C cable connection
 author: mimcco
 ms.author: mimcco
 ms.service: azure-percept
 ms.topic: how-to
 ms.date: 03/18/2021
-ms.custom: template-how-to #Required; leave this attribute/value as-is.
+ms.custom: template-how-to
 ---
 
-# How to update Azure Percept DK over a USB connection
+# How to update Azure Percept DK over a USB-C cable connection
 
-Although using over-the-air (OTA) updates is the best method of keeping your dev kit's operating system and firmware up to date, there are scenarios where updating (or "flashing") the dev kit over a USB connection is necessary:
-
-- An OTA update is not possible due to connectivity or other technical issues
-- The device needs to be reset back to its factory state
-
-This guide will show you how to successfully update your dev kit's operating system and firmware over a USB connection.
+This guide will show you how to successfully update your dev kit's operating system and firmware over a USB connection. Here is an overview of what you will be doing during this procedure.
+1. Download the update package to a host computer
+1. Run the command that transfers the update package to the dev kit
+1. Set the dev kit into "USB mode" (using SSH) so that it can be detected by the host computer and receive the update package
+1. Connect the dev kit to the host computer via the USB-C cable
+1. Wait for the update to complete
 
 > [!WARNING]
 > Updating your dev kit over USB will delete all existing data on the device, including AI models and containers.
 >
 > Follow all instructions in order. Skipping steps could put your dev kit in an unusable state.
 
+
 ## Prerequisites
 
 - An Azure Percept DK
@@ -32,14 +33,12 @@ This guide will show you how to successfully update your dev kit's operating sys
 
 ## Download software tools and update files
 
-1. [NXP UUU tool](https://github.com/NXPmicro/mfgtools/releases). Download the **Latest Release** uuu.exe file (for Windows) or the uuu file (for Linux) under the **Assets** tab.
-
-1. [7-Zip](https://www.7-zip.org/). This software will be used for extracting the raw image file from its XZ compressed file. Download and install the appropriate .exe file.
+1. [NXP UUU tool](https://github.com/NXPmicro/mfgtools/releases). Download the **Latest Release** uuu.exe file (for Windows) or the uuu file (for Linux) under the **Assets** tab. UUU is a tool created by NXP used to update software on NXP dev boards.
 
 1. [Download the update files](https://go.microsoft.com/fwlink/?linkid=2155734). They are all contained in a zip file that you will extract in the next section.
 
 1. Ensure all three build artifacts are present:
-    - Azure-Percept-DK-*<version number>*.raw.xz
+    - Azure-Percept-DK-*<version number>*.raw
     - fast-hab-fw.raw
     - emmc_full.txt
 
@@ -53,9 +52,11 @@ This guide will show you how to successfully update your dev kit's operating sys
 
 ## Update your device
 
-1. [SSH into your dev kit](./how-to-ssh-into-percept-dk.md).
+This procedure uses the dev kit's single USB-C port for updating.  If your computer has a USB-C port, you can disconnect the Azure Percept Vision device and use that cable.  If your computer only has a USB-A port, disconnect the Azure Percept Vision device from the dev kit’s USB-C port and connect a USB-C to USB-A cable (sold separately) to the dev kit and host computer.
+
+1. Open a Windows command prompt (Start > cmd) or a Linux terminal and **navigate to the folder where the update files and UUU tool are stored**. 
 
-1. Next, open a Windows command prompt (**Start** > **cmd**) or a Linux terminal and navigate to the folder where the update files and UUU tool are stored. Enter the following command in the command prompt or terminal to prepare your computer to receive a flashable device:
+1. Enter the following command in the command prompt or terminal.
 
     - Windows:
 
@@ -69,11 +70,13 @@ This guide will show you how to successfully update your dev kit's operating sys
         sudo ./uuu -b emmc_full.txt fast-hab-fw.raw Azure-Percept-DK-<version number>.raw
         ```
 
-1. Disconnect the Azure Percept Vision device from the carrier board's USB-C port.
+1. The command prompt window will display a message that say "**Waiting for Known USB Device to Appear...**" The UUU tool is now waiting for the dev kit to be detected by the host computer. It is now ok to proceed to the next steps.
+
+1. Connect the supplied USB-C cable to the dev kit's USB-C port and to the host computer's USB-C port. If your computer only has a USB-A port, connect a USB-C to USB-A cable (sold separately) to the dev kit and host computer.
 
-1. Connect the supplied USB-C cable to the carrier board's USB-C port and to the host computer's USB-C port. If your computer only has a USB-A port, connect a USB-C to USB-A cable (sold separately) to the carrier board and host computer.
+1. Connect to your dev kit via SSH. If you need help to SSH, [follow these instructions](./how-to-ssh-into-percept-dk.md).
 
-1. In the SSH client prompt, enter the following commands:
+1. In the SSH terminal, enter the following commands:
 
     1. Set the device to USB update mode:
 
@@ -92,7 +95,7 @@ This guide will show you how to successfully update your dev kit's operating sys
     > [!NOTE]
     > After updating, your device will be reset to factory settings and you will lose your Wi-Fi connection and SSH login.
 
-1. Once the update is complete, power off the carrier board. Unplug the USB cable from the PC.  
+1. Once the update is complete, power off the dev kit. Unplug the USB cable from the PC.  
 
 ## Next steps