Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into 1874741b

Author: dagiro

.openpublishing.redirection.json

@@ -28511,6 +28511,11 @@
     {
       "source_path_from_root": "/articles/storage/storage-blob-storage-tiers.md",
       "redirect_url": "/azure/storage/blobs/storage-blob-storage-tiers",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/blobs/storage-blob-storage-tiers.md",
+      "redirect_url": "/azure/storage/blobs/access-tiers-overview",
       "redirect_document_id": true
     },
     {

articles/active-directory/conditional-access/howto-conditional-access-policy-admin-mfa.md

@@ -15,6 +15,7 @@ ms.reviewer: calebb, rogoya
 
 ms.collection: M365-identity-device-management
 ---
+
 # Conditional Access: Require MFA for administrators
 
 Accounts that are assigned administrative rights are targeted by attackers. Requiring multi-factor authentication (MFA) on those accounts is an easy way to reduce the risk of those accounts being compromised.
@@ -42,7 +43,7 @@ Organizations can choose to include or exclude roles as they see fit.
 
 Conditional Access policies are powerful tools, we recommend excluding the following accounts from your policy:
 
-- **Emergency access** or **break-glass** accounts to prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant take steps to recover access.
+- **Emergency access** or **break-glass** accounts to prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant to take steps to recover access.
    - More information can be found in the article, [Manage emergency access accounts in Azure AD](../roles/security-emergency-access.md).
 - **Service accounts** and **service principals**, such as the Azure AD Connect Sync Account. Service accounts are non-interactive accounts that are not tied to any particular user. They are normally used by back-end services allowing programmatic access to applications, but are also used to sign in to systems for administrative purposes. Service accounts like these should be excluded since MFA can't be completed programmatically. Calls made by service principals are not blocked by Conditional Access.
    - If your organization has these accounts in use in scripts or code, consider replacing them with [managed identities](../managed-identities-azure-resources/overview.md). As a temporary workaround, you can exclude these specific accounts from the baseline policy.
@@ -75,7 +76,7 @@ The following steps will help create a Conditional Access policy to require thos
       > [!WARNING]
       > Conditional Access policies support built-in roles. Conditional Access policies are not enforced for other role types including [administrative unit-scoped](../roles/admin-units-assign-roles.md) or [custom roles](../roles/custom-create.md).
 
-   1. Under **Exclude**, select **Users and groups** and choose your organization's emergency access or break-glass accounts. 
+   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**, and select **Done**.
 1. Under **Access controls** > **Grant**, select **Grant access**, **Require multi-factor authentication**, and select **Select**.

articles/active-directory/develop/reference-aadsts-error-codes.md

@@ -269,6 +269,7 @@ For example, if you received the error code "AADSTS50058" then do a search in [h
 | AADSTS90093 | GraphUserUnauthorized - Graph returned with a forbidden error code for the request. |
 | AADSTS90094 | AdminConsentRequired - Administrator consent is required. |
 | AADSTS900382 | Confidential Client is not supported in Cross Cloud request. |
+| AADSTS90095  | AdminConsentRequiredRequestAccess-  In the Admin Consent Workflow experience, an interrupt that appears when the user is told they need to ask the admin for consent.  |
 | AADSTS90099 | The application '{appId}' ({appName}) has not been authorized in the tenant '{tenant}'. Applications must be authorized to access the customer tenant before partner delegated administrators can use them. Provide pre-consent or execute the appropriate Partner Center API to authorize the application. |
 | AADSTS900971| No reply address provided.|
 | AADSTS90100 | InvalidRequestParameter - The parameter is empty or not valid. |

articles/active-directory/enterprise-users/groups-settings-cmdlets.md

@@ -28,6 +28,9 @@ Microsoft 365 groups settings are configured using a Settings object and a Setti
 
 The cmdlets are part of the Azure Active Directory PowerShell V2 module. For instructions how to download and install the module on your computer, see the article [Azure Active Directory PowerShell Version 2](/powershell/azure/active-directory/overview). You can install the version 2 release of the module from [the PowerShell gallery](https://www.powershellgallery.com/packages/AzureAD/).
 
+>[!Note]
+>With the settings in place to restrict the addition of guests to Microsoft 365 Groups, administrators will still add guest users to Microsoft 365 Groups. The setting will restrict non-admin users from adding guest users to Microsoft 365 groups.
+
 ## Install PowerShell cmdlets
 
 Be sure to uninstall any older version of the Azure Active Directory PowerShell for Graph Module for Windows PowerShell and install [Azure Active Directory PowerShell for Graph - Public Preview Release (later than 2.0.0.137)](https://www.powershellgallery.com/packages/AzureADPreview) before you run the PowerShell commands.

articles/automation/TOC.yml

@@ -166,15 +166,19 @@
               href: troubleshoot/collect-data-microsoft-azure-automation-case.md
         - name: Work with a Hybrid Runbook Worker
           items:
-            - name: Deploy Windows Hybrid Runbook Worker
+            - name: Deploy extension-based worker
+              href: extension-based-hybrid-runbook-worker-install.md
+            - name: Deploy agent-based Windows worker
               href: automation-windows-hrw-install.md
-            - name: Deploy Linux Hybrid Runbook Worker
+            - name: Deploy agent-based Linux worker
               href: automation-linux-hrw-install.md
             - name: Run runbooks on Hybrid Runbook Worker
               href: automation-hrw-run-runbooks.md
             - name: Use Azure Policy to enforce job execution
               href: enforce-job-execution-hybrid-worker.md
-            - name: Troubleshoot Hybrid Runbook Worker issues
+            - name: Troubleshoot extension-based worker issues
+              href: troubleshoot/extension-based-hybrid-runbook-worker.md
+            - name: Troubleshoot agent-based worker issues
               href: troubleshoot/hybrid-runbook-worker.md
         - name: Use source control integration
           href: source-control-integration.md

articles/automation/automation-connections.md

@@ -34,7 +34,7 @@ In most cases, you don't need to create a connection resource because it is crea
 
 ## PowerShell cmdlets to access connections
 
-The cmdlets in the following table create and manage Automation connections with PowerShell. They ship as part of the [Az modules](shared-resources/modules.md#az-modules).
+The cmdlets in the following table create and manage Automation connections with PowerShell. They ship as part of the Az modules.
 
 |Cmdlet|Description|
 |---|---|