Merge pull request #206260 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 4f3ef384dcba · 2022-07-28T14:42:30.000-07:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/active-directory/saas-apps/8x8-provisioning-tutorial.md b/articles/active-directory/saas-apps/8x8-provisioning-tutorial.md
@@ -20,7 +20,7 @@ This tutorial describes the steps you need to perform in both 8x8 Admin Console
 ## Capabilities supported
 > [!div class="checklist"]
 > * Create users in 8x8
-> * Remove users in 8x8 when they do not require access anymore
+> * Deactivate users in 8x8 when they do not require access anymore
 > * Keep user attributes synchronized between Azure AD and 8x8
 > * [Single sign-on](./8x8virtualoffice-tutorial.md) to 8x8 (recommended)
 
@@ -48,17 +48,17 @@ This section guides you through the steps to configure 8x8 to support provisioni
 
 ### To configure a user provisioning access token in 8x8 Admin Console:
 
-1. Sign in to [Admin Console](https://admin.8x8.com). Select **Identity Management**.
+1. Sign in to [Admin Console](https://admin.8x8.com). Select **Identity and Security**.
 
-   ![Admin](./media/8x8-provisioning-tutorial/8x8-identity-management.png)
+   [ ![Screenshot showing the 8x8 Admin Console.](./media/8x8-provisioning-tutorial/8x8-identity-and-security.png) ](./media/8x8-provisioning-tutorial/8x8-identity-and-security.png#lightbox)
 
-2. Click the **Show user provisioning information** link to generate a token.
+2. In the **User Provisioning Integration (SCIM)** pane, click the toggle to enable and then click **Save**.
 
-   ![Show](./media/8x8-provisioning-tutorial/8x8-show-user-provisioning.png)
+   [ ![Screenshot showing the Identity and Security page of the Admin Console with a callout over the user provisioning integration slider.](./media/8x8-provisioning-tutorial/8x8-enable-user-provisioning.png) ](./media/8x8-provisioning-tutorial/8x8-enable-user-provisioning.png#lightbox)
 
 3. Copy the **8x8 URL** and **8x8 API Token** values. These values will be entered in the **Tenant URL** and **Secret Token** fields respectively in the Provisioning tab of your 8x8  application in the Azure portal.
 
-   ![Token](./media/8x8-provisioning-tutorial/8x8-copy-url-token.png)
+   [ ![Screenshot showing the Identity and Security page of the Admin Console with callout over token fields.](./media/8x8-provisioning-tutorial/8x8-copy-url-token.png) ](./media/8x8-provisioning-tutorial/8x8-copy-url-token.png#lightbox)
 
 ## Step 3. Add 8x8 from the Azure AD application gallery
 
@@ -82,19 +82,19 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
 
-	![Enterprise applications blade](./media/8x8-provisioning-tutorial/enterprise-applications.png)
+	![Screenshot showing the Enterprise applications blade](./media/8x8-provisioning-tutorial/enterprise-applications.png)
 
-	![All applications blade](./media/8x8-provisioning-tutorial/all-applications.png)
+	![Screenshot showing the All applications blade](./media/8x8-provisioning-tutorial/all-applications.png)
 
 2. In the applications list, select **8x8**.
 
-	![The 8x8 link in the Applications list](common/all-applications.png)
+	![Screenshot showing the 8x8 link in the Applications list](common/all-applications.png)
 
 3. Select the **Provisioning** tab. Click on **Get started**.
 
 	![Screenshot of the Manage options with the Provisioning option called out.](common/provisioning.png)
 
-   ![Get started blade](./media/8x8-provisioning-tutorial/get-started.png)
+   ![Screenshot showing the Get started blade](./media/8x8-provisioning-tutorial/get-started.png)
 
 4. Set the **Provisioning Mode** to **Automatic**.
 
@@ -106,7 +106,7 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 6. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
-	![Notification Email](common/provisioning-notification-email.png)
+	![Screenshot showing the Notification Email field.](common/provisioning-notification-email.png)
 
 7. Select **Save**.
 
@@ -160,4 +160,4 @@ Once you've configured provisioning, use the following resources to monitor your
 
 ## Next steps
 
-* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
diff --git a/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-copy-url-token.png b/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-copy-url-token.png
diff --git a/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-enable-user-provisioning.png b/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-enable-user-provisioning.png
diff --git a/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-identity-and-security.png b/articles/active-directory/saas-apps/media/8x8-provisioning-tutorial/8x8-identity-and-security.png
diff --git a/articles/app-service/configure-connect-to-azure-storage.md b/articles/app-service/configure-connect-to-azure-storage.md
@@ -213,12 +213,6 @@ Verify your storage is mounted by running the following command:
 az webapp config storage-account list --resource-group <resource-group> --name <app-name>
 ```
 
-Verify your configuration by running the following command:
-
-```azurecli
-az webapp config storage-account list --resource-group <resource-group> --name <app-name>
-```
-
 ---
 
 > [!NOTE]
diff --git a/articles/communication-services/concepts/email/email-authentication-best-practice.md b/articles/communication-services/concepts/email/email-authentication-best-practice.md
@@ -71,5 +71,5 @@ A DMARC policy record allows a domain to announce that their email uses authenti
 The following documents may be interesting to you:
 
 - Familiarize yourself with the [Email client library](../email/sdk-features.md)
-- How to send emails with custom verified domains?[Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
-- How to send emails with Azure Managed Domains?[Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- How to send emails with custom verified domains? [Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
+- How to send emails with Azure Managed Domains? [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
diff --git a/articles/communication-services/concepts/email/email-domain-and-sender-authentication.md b/articles/communication-services/concepts/email/email-domain-and-sender-authentication.md
@@ -53,5 +53,5 @@ Email Communication Service resources are designed to enable domain validation s
 The following documents may be interesting to you:
 
 - Familiarize yourself with the [Email client library](../email/sdk-features.md)
-- How to send emails with custom verified domains?[Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
-- How to send emails with Azure Managed Domains?[Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- How to send emails with custom verified domains? [Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
+- How to send emails with Azure Managed Domains? [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
diff --git a/articles/communication-services/concepts/email/email-overview.md b/articles/communication-services/concepts/email/email-overview.md
@@ -54,5 +54,5 @@ Key features include:
 The following documents may be interesting to you:
 
 - Familiarize yourself with the [Email client library](../email/sdk-features.md)
-- How to send emails with custom verified domains?[Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
-- How to send emails with Azure Managed Domains?[Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- How to send emails with custom verified domains? [Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
+- How to send emails with Azure Managed Domains? [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
diff --git a/articles/communication-services/concepts/email/prepare-email-communication-resource.md b/articles/communication-services/concepts/email/prepare-email-communication-resource.md
@@ -56,5 +56,5 @@ Your Azure Administrators will create a new resource of type “Email Communicat
 The following documents may be interesting to you:
 
 - Familiarize yourself with the [Email client library](../email/sdk-features.md)
-- How to send emails with custom verified domains?[Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
-- How to send emails with Azure Managed Domains?[Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- How to send emails with custom verified domains? [Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
+- How to send emails with Azure Managed Domains? [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
diff --git a/articles/communication-services/concepts/email/sdk-features.md b/articles/communication-services/concepts/email/sdk-features.md
@@ -51,6 +51,6 @@ Your Azure account has a set of limitation on the number of email messages that
 
 The following documents may be interesting to you:
 
-- How to send emails with custom verified domains?[Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
-- How to send emails with Azure Managed Domains?[Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- How to send emails with custom verified domains? [Add custom domains](../../quickstarts/email/add-custom-verified-domains.md)
+- How to send emails with Azure Managed Domains? [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
 - How to send emails with Azure Communication Service using Email client library? [How to send an Email?](../../quickstarts/email/send-email.md)
diff --git a/articles/container-apps/ingress.md b/articles/container-apps/ingress.md
@@ -47,7 +47,7 @@ The following settings are available when configuring ingress:
 
 | Property | Description | Values | Required |
 |---|---|---|---|
-| `external` | Your ingress IP and fully qualified domain name can either be visible externally to the internet, or internally within a VNET. |`true` for external visibility, `false` for internal visibility (default) | Yes |
+| `external` | The ingress IP and fully qualified domain name (FQDN) can either be accessible externally from the internet or a VNET, or internally within the app environment only. | `true` for external visibility from the internet or a VNET, `false` for internal visibility within app environment only (default) | Yes |
 | `targetPort` | The port your container listens to for incoming requests. | Set this value to the port number that your container uses. Your application ingress endpoint is always exposed on port `443`. | Yes |
 | `transport` | You can use either HTTP/1.1 or HTTP/2, or you can set it to automatically detect the transport type. | `http` for HTTP/1, `http2` for HTTP/2, `auto` to automatically detect the transport type (default) | No |
 | `allowInsecure` | Allows insecure traffic to your container app. | `false` (default), `true`<br><br>If set to `true`, HTTP requests to port 80 are not automatically redirected to port 443 using HTTPS, allowing insecure connections. | No |
diff --git a/articles/container-apps/samples.md b/articles/container-apps/samples.md
@@ -15,8 +15,9 @@ Refer to the following samples to learn how to use Azure Container Apps in diffe
 
 | Name | Description |
 |--|--|
-| [A/B Testing your ASP.NET Core apps using Azure Container Apps](https://github.com/Azure-Samples/dotNET-Frontend-AB-Testing-on-Azure-Container-Apps)<br /> | Shows how to use Azure App Configuration, ASP.NET Core Feature Flags, and Azure Container Apps revisions together to gradually release features or perform A/B tests. <br /> |
-| [gRPC with ASP.NET Core on Azure Container Apps](https://github.com/Azure-Samples/dotNET-Workers-with-gRPC-messaging-on-Azure-Container-Apps) | This repository contains a simple scenario built to demonstrate how ASP.NET Core 6.0 can be used to build a cloud-native application hosted in Azure Container Apps that uses gRPC request/response transmission from Worker microservices. The gRPC service simultaneously streams sensor data to a Blazor server frontend, so you can watch the data be charted in real-time. <br /> |
-| [Deploy an Orleans Cluster to Container Apps](https://github.com/Azure-Samples/Orleans-Cluster-on-Azure-Container-Apps) | An end-to-end sample and tutorial for getting a Microsoft Orleans cluster running on Azure Container Apps. Worker microservices rapidly transmit data to a back-end Orleans cluster for monitoring and storage, emulating thousands of physical devices in the field.<br /> |
+| [A/B Testing your ASP.NET Core apps using Azure Container Apps](https://github.com/Azure-Samples/dotNET-Frontend-AB-Testing-on-Azure-Container-Apps)<br /> | Shows how to use Azure App Configuration, ASP.NET Core Feature Flags, and Azure Container Apps revisions together to gradually release features or perform A/B tests. |
+| [gRPC with ASP.NET Core on Azure Container Apps](https://github.com/Azure-Samples/dotNET-Workers-with-gRPC-messaging-on-Azure-Container-Apps) | This repository contains a simple scenario built to demonstrate how ASP.NET Core 6.0 can be used to build a cloud-native application hosted in Azure Container Apps that uses gRPC request/response transmission from Worker microservices. The gRPC service simultaneously streams sensor data to a Blazor server frontend, so you can watch the data be charted in real-time. |
+| [Deploy an Orleans Cluster to Container Apps](https://github.com/Azure-Samples/Orleans-Cluster-on-Azure-Container-Apps) | An end-to-end sample and tutorial for getting a Microsoft Orleans cluster running on Azure Container Apps. Worker microservices rapidly transmit data to a back-end Orleans cluster for monitoring and storage, emulating thousands of physical devices in the field. |
+| [Deploy a shopping cart Orleans app to Container Apps](https://github.com/Azure-Samples/orleans-blazor-server-shopping-cart-on-container-apps) | An end-to-end example shopping cart app built in ASP.NET Core Blazor Server with Orleans deployed to Azure Container Apps. |
 | [ASP.NET Core front-end with two back-end APIs on Azure Container Apps](https://github.com/Azure-Samples/dotNET-FrontEnd-to-BackEnd-on-Azure-Container-Apps )<br /> | This sample demonstrates ASP.NET Core 6.0 can be used to build a cloud-native application hosted in Azure Container Apps. |
 | [ASP.NET Core front-end with two back-end APIs on Azure Container Apps (with Dapr)](https://github.com/Azure-Samples/dotNET-FrontEnd-to-BackEnd-with-DAPR-on-Azure-Container-Apps )<br /> | Demonstrates how ASP.NET Core 6.0 is used to build a cloud-native application hosted in Azure Container Apps using Dapr. |
diff --git a/articles/cost-management-billing/reservations/view-reservations.md b/articles/cost-management-billing/reservations/view-reservations.md
@@ -134,7 +134,7 @@ When you use the PowerShell script to assign the ownership role and it runs succ
 - Accept wildcard characters: False
 
 ## Tenant-level access
-[User Access Administrator](../../role-based-access-control/built-in-roles.md#user-access-administrator) rights are required before you can grant users or groups the Reservation Administrator and Reservation Reader roles at the tenant level.
+[User Access Administrator](../../role-based-access-control/built-in-roles.md#user-access-administrator) rights are required before you can grant users or groups the Reservation Administrator and Reservation Reader roles at the tenant level. In order to get User Access Administrator rights at the tenant level, follow [Elevate access](../../role-based-access-control/elevate-access-global-admin.md) steps.
 
 ## Add a Reservation Administrator role at the tenant level
 
diff --git a/articles/storage/common/storage-use-azcopy-troubleshoot.md b/articles/storage/common/storage-use-azcopy-troubleshoot.md
@@ -24,6 +24,8 @@ If the exit code is `1-error`, then examine the log file. Once you understand th
 
 If the exit code is `2-panic`, then check the log file exists. If the file doesn't exist, file a bug or reach out to support.
 
+If the exit code is any other non-zero exit code, it may be an exit code from the system. For example, OOMKilled.  Check your operating system documentation for special exit codes.
+
 ## 403 errors
 
 It's common to encounter 403 errors. Sometimes they're benign and don't result in failed transfer. For example, in AzCopy logs, you might see that a HEAD request received 403 errors. Those errors appear when AzCopy checks whether a resource is public. In most cases, you can ignore those instances.
diff --git a/articles/virtual-desktop/configure-device-redirections.md b/articles/virtual-desktop/configure-device-redirections.md
@@ -68,6 +68,9 @@ Set the following RDP property to configure COM port redirection:
 
 ### USB redirection
 
+>[!IMPORTANT]
+>To redirect a mass storage USB device connected to your local computer to the remote session host, you'll need to configure the **Drive/storage redirection** RDP property. Enabling the **USB redirection** RDP property by itself won't work. For more information, see [Local drive redirection](#local-drive-redirection).
+
 First, set the following RDP property to enable USB device redirection:
 
 - `usbdevicestoredirect:s:*` enables USB device redirection.
