Merge pull request #178868 from MicrosoftDocs/master

11/05 AM Publish

Author: huypub

articles/active-directory/enterprise-users/domains-verify-custom-subdomain.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: enterprise-users
 ms.workload: identity
 ms.topic: how-to
-ms.date: 10/28/2021
+ms.date: 11/05/2021
 ms.author: curtand
 ms.reviewer: sumitp
 
@@ -37,7 +37,7 @@ Because subdomains inherit the authentication type of the root domain by default
    New-MsolDomain -Name "child.mydomain.com" -Authentication Federated
    ```
 
-1. Use [Azure AD Graph Explorer](https://graphexplorer.azurewebsites.net) to GET the domain. Because the domain isn't a root domain, it inherits the root domain authentication type. Your command and results might look as follows, using your own tenant ID:
+1. Use the following example to GET the domain. Because the domain isn't a root domain, it inherits the root domain authentication type. Your command and results might look as follows, using your own tenant ID:
 
    ```http
    GET https://graph.windows.net/{tenant_id}/domains?api-version=1.6
@@ -61,7 +61,7 @@ Because subdomains inherit the authentication type of the root domain by default
      },
    ```
 
-### Use Azure AD Graph Explorer API to make this a root domain
+### Use Microsoft Graph API to make this a root domain
 
 Use the following command to promote the subdomain:
 
@@ -77,7 +77,7 @@ POST https://graph.windows.net/{tenant_id}/domains/child.mydomain.com/promote?ap
    Set-MsolDomainAuthentication -DomainName child.mydomain.com -Authentication Managed
    ```
 
-1. Verify via GET in Azure AD Graph Explorer that subdomain authentication type is now managed:
+1. Verify via GET in Microsoft Graph API that subdomain authentication type is now managed:
 
    ```http
    GET https://graph.windows.net/{{tenant_id} }/domains?api-version=1.6

articles/aks/http-proxy.md

@@ -21,6 +21,7 @@ Some more complex solutions may require creating a chain of trust to establish s
 ## Limitations and other details
 
 The following scenarios are **not** supported:
+- Monitoring addon
 - Different proxy configurations per node pool
 - Updating proxy settings post cluster creation
 - User/Password authentication

articles/automation/automation-security-overview.md

@@ -4,7 +4,7 @@ description: This article provides an overview of Azure Automation account authe
 keywords: automation security, secure automation; automation authentication
 services: automation
 ms.subservice: process-automation
-ms.date: 10/26/2021
+ms.date: 11/05/2021
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
@@ -33,6 +33,9 @@ A managed identity from Azure Active Directory (Azure AD) allows your runbook to
 
 Managed identities are the recommended way to authenticate in your runbooks, and is the default authentication method for your Automation account.
 
+> [!NOTE]
+> When you create an Automation account, the option to create a Run As account is no longer available. However, we continue to support a RunAs account for existing and new Automation accounts. You can [create a Run As account](create-run-as-account.md) in your Automation account from the Azure portal or by using PowerShell.
+
 Here are some of the benefits of using managed identities:
 
 - Using a managed identity instead of the Automation Run As account simplifies management. You don't have to renew the certificate used by a Run As account.
@@ -63,7 +66,7 @@ To create or renew a Run As account, permissions are needed at three levels:
 - Automation account
 
 > [!NOTE]
-> Azure Automation does not automatically create the Run As account. It has been replaced by using managed identities.
+> Azure Automation does not automatically create the Run As account, it has been replaced by using managed identities. However, we continue to support a RunAs account for existing and new Automation accounts. You can [create a Run As account](create-run-as-account.md) in your Automation account from the Azure portal or by using PowerShell.
 
 ### Subscription permissions
 

articles/availability-zones/az-region.md

@@ -29,7 +29,7 @@ Azure provides the most extensive global footprint of any cloud provider and is
 | East US | Norway East | | Korea Central |
 | East US 2 | UK South | | Southeast Asia |
 | South Central US | West Europe | | East Asia |
-| US Gov Virginia | Sweden* | | |
+| US Gov Virginia | Sweden | | |
 | West US 2 | | | |
 | West US 3 | | | |
 
@@ -208,4 +208,4 @@ You can access Azure availability zones by using your Azure subscription. To lea
 
 - [Building solutions for high availability using availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability)
 - [High availability with Azure services](/azure/architecture/framework/resiliency/overview)
-- [Design patterns for high availability](/azure/architecture/framework/resiliency/app-design)
+- [Design patterns for high availability](/azure/architecture/framework/resiliency/app-design)