Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-check-access-update

Author: rolyon

.openpublishing.redirection.azure-monitor.json

@@ -510,6 +510,11 @@
             "source_path_from_root": "/articles/azure-monitor/logs/workspace-design-service-providers.md" ,
             "redirect_url": "/azure/azure-monitor/logs/workspace-design",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/containers/container-insights-transition-hybrid.md" ,
+            "redirect_url": "/azure/azure-monitor/containers/container-insights-onboard",
+            "redirect_document_id": false
         }
     ]
 }

.openpublishing.redirection.json

@@ -22348,6 +22348,11 @@
     "redirect_url":  "/azure/storage/common/customer-managed-keys-configure-key-vault",
     "redirect_document_id":  false
 },
+{
+    "source_path_from_root":  "/articles/storage/common/customer-managed-keys-configure-key-vault.md",
+    "redirect_url":  "/azure/storage/common/customer-managed-keys-configure-existing-account",
+    "redirect_document_id":  false
+},
 {
     "source_path_from_root":  "/articles/storage/common/encryption-customer-managed-keys.md",
     "redirect_url":  "/azure/storage/common/customer-managed-keys-overview",

articles/active-directory-b2c/configure-authentication-sample-react-spa-app.md

@@ -182,7 +182,7 @@ Your final configuration file should look like the following JSON:
 ```json
 {
     "credentials": {
-        "tenantName": "<your-tenant-name>",
+        "tenantName": "<your-tenant-name>.ommicrosoft.com",
         "clientID": "<your-webapi-application-ID>",
         "issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
     },

articles/active-directory-b2c/microsoft-graph-operations.md

@@ -60,8 +60,8 @@ Note, the [list](/graph/api/authentication-list-phonemethods) operation returns
 
 An email address that can be used by a [username sign-in account](sign-in-options.md#username-sign-in) to reset the password. For more information, see [Azure AD authentication methods API](/graph/api/resources/emailauthenticationmethod).
 
-- [Add](/graph/api/emailauthenticationmethod-post)
-- [List](/graph/api/emailauthenticationmethod-list)
+- [Add](/graph/api/authentication-post-emailmethods)
+- [List](/graph/api/authentication-list-emailmethods)
 - [Get](/graph/api/emailauthenticationmethod-get)
 - [Update](/graph/api/emailauthenticationmethod-update)
 - [Delete](/graph/api/emailauthenticationmethod-delete)

articles/active-directory/app-provisioning/on-premises-scim-provisioning.md

@@ -7,7 +7,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 07/05/2022
+ms.date: 08/25/2022
 ms.author: billmath
 ms.reviewer: arvinh
 ---
@@ -22,6 +22,7 @@ The Azure Active Directory (Azure AD) provisioning service supports a [SCIM 2.0]
 - An Azure AD tenant with Azure AD Premium P1 or Premium P2 (or EMS E3 or E5). [!INCLUDE [active-directory-p1-license.md](../../../includes/active-directory-p1-license.md)]
 - Administrator role for installing the agent. This task is a one-time effort and should be an Azure account that's either a hybrid administrator or a global administrator. 
 - Administrator role for configuring the application in the cloud (application administrator, cloud application administrator, global administrator, or a custom role with permissions).
+- A computer with at least 3 GB of RAM, to host a provisioning agent. The computer should have Windows Server 2016 or a later version of Windows Server, with connectivity to the target application, and with outbound connectivity to login.microsoftonline.com, other Microsoft Online Services and Azure domains. An example is a Windows Server 2016 virtual machine hosted in Azure IaaS or behind a proxy.
 
 ## Deploying Azure AD provisioning agent
 The Azure AD Provisioning agent can be deployed on the same server hosting a SCIM enabled application, or a seperate server, providing it has line of sight to the application's SCIM endpoint. A single agent also supports provision to multiple applications hosted locally on the same server or seperate hosts, again as long as each SCIM endpoint is reachable by the agent.  
@@ -49,6 +50,9 @@ Once the agent is installed, no further configuration is necesary on-prem, and a
  12.  Go to the **Provisioning** pane, and select **Start provisioning**.
  13.  Monitor using the [provisioning logs](../../active-directory/reports-monitoring/concept-provisioning-logs.md).
 
+The following video provides an overview of on-premises provisoning.
+> [!VIDEO https://www.youtube.com/embed/QdfdpaFolys]
+
 ## Additional requirements
 * Ensure your [SCIM](https://techcommunity.microsoft.com/t5/identity-standards-blog/provisioning-with-scim-getting-started/ba-p/880010) implementation meets the [Azure AD SCIM requirements](use-scim-to-provision-users-and-groups.md).
 

articles/active-directory/cloud-sync/concept-attributes.md

@@ -4,7 +4,7 @@ description: This article describes the Azure AD schema, the attributes that the
 services: active-directory
 documentationcenter: ''
 author: billmath
-manager: karenhoran
+manager: amycolannino
 editor: ''
 ms.service: active-directory
 ms.topic: conceptual
@@ -250,4 +250,4 @@ To view the schema and verify it, follow these steps.
 ## Next steps
 
 - [What is provisioning?](what-is-provisioning.md)
-- [What is Azure AD Connect cloud sync?](what-is-cloud-sync.md)
+- [What is Azure AD Connect cloud sync?](what-is-cloud-sync.md)

articles/active-directory/cloud-sync/concept-how-it-works.md

@@ -3,7 +3,7 @@ title: 'Azure AD Connect cloud sync deep dive - how it works'
 description: This topic provides deep dive information on how cloud sync works.
 services: active-directory
 author: billmath
-manager: karenhoran
+manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual

articles/active-directory/cloud-sync/how-to-accidental-deletes.md

@@ -3,7 +3,7 @@ title: 'Azure AD Connect cloud sync accidental deletes'
 description: This topic describes how to use the accidental delete feature to prevent deletions.
 services: active-directory
 author: billmath
-manager: karenhoran
+manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual

articles/active-directory/cloud-sync/how-to-attribute-mapping.md

@@ -3,7 +3,7 @@ title: 'Attribute mapping in Azure AD Connect cloud sync'
 description: This article describes how to use the cloud sync feature of Azure AD Connect to map attributes.
 services: active-directory
 author: billmath
-manager: karenhoran
+manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
@@ -156,4 +156,4 @@ To test your attribute mapping, you can use [on-demand provisioning](how-to-on-d
 - [What is Azure AD Connect cloud sync?](what-is-cloud-sync.md)
 - [Writing expressions for attribute mappings](reference-expressions.md)
 - [How to use expression builder with cloud sync](how-to-expression-builder.md)
-- [Attributes synchronized to Azure Active Directory](../hybrid/reference-connect-sync-attributes-synchronized.md?context=azure%2factive-directory%2fcloud-provisioning%2fcontext%2fcp-context/hybrid/reference-connect-sync-attributes-synchronized.md)
+- [Attributes synchronized to Azure Active Directory](../hybrid/reference-connect-sync-attributes-synchronized.md?context=azure%2factive-directory%2fcloud-provisioning%2fcontext%2fcp-context/hybrid/reference-connect-sync-attributes-synchronized.md)

articles/active-directory/cloud-sync/how-to-automatic-upgrade.md

@@ -4,7 +4,7 @@ description: This article describes the built-in automatic upgrade feature in th
 services: active-directory
 documentationcenter: ''
 author: billmath
-manager: karenhoran
+manager: amycolannino
 editor: ''
 ms.service: active-directory
 ms.topic: how-to