Merge branch 'master' into release-ga-functions-v4

Author: v-alje

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/api-management/api-management-using-with-internal-vnet.md

@@ -148,7 +148,6 @@ To access these API Management service endpoints, you can create a virtual machi
 
 You can then access all the service endpoints from the virtual machine you created.
 
-If you use a custom DNS server in a VNET, you can also create DNS A-records and access these endpoints from anywhere in your VNET.
 
 ### Access on custom domain names
 

articles/application-gateway/multiple-site-overview.md

@@ -29,7 +29,7 @@ Similarly, you can host multiple subdomains of the same parent domain on the sam
 While using multi-site listeners, to ensure that the client traffic is routed to the accurate backend, it is important to have the request routing rules be present in the correct order.
 For example, if you have 2 listeners with associated Host name as `*.contoso.com` and `shop.contoso.com` respectively, the listener with the `shop.contoso.com` Host name would have to be processed before the listener with `*.contoso.com`. If the listener with `*.contoso.com` is processed first, then no client traffic would be received by the more specific `shop.contoso.com` listener.
 
-This ordering can be established by providing a 'Priority' field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. In case the incoming client traffic matches with multiple listeners, the request routing rule with highest priority will be used for serving the request.
+This ordering can be established by providing a 'Priority' field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. In case the incoming client traffic matches with multiple listeners, the request routing rule with highest priority will be used for serving the request. Each request routing rule needs to have a unique priority value.
 
 The priority field only impacts the order of evaluation of a request routing rule, this will not change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
 

articles/applied-ai-services/form-recognizer/overview.md

@@ -18,7 +18,7 @@ ms.custom: ignite-fall-2021
 <!-- markdownlint-disable MD024 -->
 # What is Azure Form Recognizer?
 
-Azure Form Recognizer is an [Azure Applied AI Service](../../applied-ai-services/index.yml) cloud service that uses machine learning models to extract and analyze form fields, text, and tables from your documents. Form Recognizer analyzes your forms and documents, extracts text and data, maps field relationships as key-value pairs, and returns a structured JSON output. You quickly get accurate results that are tailored to your specific content without excessive manual intervention or extensive data science expertise. Use Form Recognizer to automate your data processing in applications and workflows, enhance data-driven strategies, and enrich document search capabilities.
+Azure Form Recognizer is a cloud-based [Azure Applied AI Service](../../applied-ai-services/index.yml) that uses machine learning models to extract and analyze form fields, text, and tables from your documents. Form Recognizer analyzes your forms and documents, extracts text and data, maps field relationships as key-value pairs, and returns a structured JSON output. You quickly get accurate results that are tailored to your specific content without excessive manual intervention or extensive data science expertise. Use Form Recognizer to automate your data processing in applications and workflows, enhance data-driven strategies, and enrich document search capabilities.
 
 Form Recognizer easily identifies, extracts, and analyzes the following document data:
 

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/TOC.yml

@@ -1,7 +1,9 @@
 - name: Azure Resiliency
   items:
   - name: Azure Resiliency feature page
-    href: https://azure.microsoft.com/features/resiliency
+    href: https://azure.microsoft.com/features/
+  - name: Resiliency in Azure
+    href: overview.md   
   - name: Design resilient applications for Azure
     href: /azure/architecture/framework/resiliency/app-design
 - name: Availability Zones fundamentals
@@ -97,21 +99,26 @@
       items:
       - name: Create an Azure Active Directory Domain Services instance
         href: ../active-directory-domain-services/tutorial-create-instance.md
-  - name: Azure Orbital Documentation
-    items:
-    - name: What is Azure Orbital?
-      href: ../networking/azure-orbital-overview.md
+
 - name: Disaster Recovery
-  items:
+  items:  
+  - name: Business continuity management in Azure
+    href: business-continuity-management-program.md
+  - name: Cross-region replication in Azure
+    href: cross-region-replication-azure.md
   - name: Use Azure Site Recovery
     href: ../site-recovery/index.yml
-- name: Azure Backup
-  items:
   - name: Use Azure Backup
     href: ../backup/index.yml
+  - name: Microsoft Azure Well-Architected Framework
+    href: /azure/architecture/framework/  
 - name: Resources
   items:
   - name: Azure Roadmap
     href: https://azure.microsoft.com/roadmap/
   - name: Azure Regions
     href: https://azure.microsoft.com/regions/
+- name: Azure Orbital Documentation
+  items:
+  - name: What is Azure Orbital?
+    href: ../networking/azure-orbital-overview.md

articles/availability-zones/az-overview.md

@@ -5,7 +5,7 @@ author: prsandhu
 ms.service: azure
 ms.topic: conceptual
 ms.date: 10/01/2021
-ms.author: prsandhu
+ms.author: rarco
 ms.reviewer: cynthn
 ms.custom: references_regions
 ---
@@ -48,8 +48,8 @@ Azure provides the most extensive global footprint of any cloud provider and is
 | Central US | North Europe | | Japan East |
 | East US | Norway East | | Korea Central |
 | East US 2 | UK South | | Southeast Asia |
-| South Central US | West Europe |  | East Asia* |
-| US Gov Virginia | Sweden* | | |
+| South Central US | West Europe |  | East Asia |
+| US Gov Virginia | Sweden | | |
 | West US 2 | | | |
 | West US 3 | | | |
 

articles/availability-zones/az-region.md

@@ -5,7 +5,7 @@ author: prsandhu
 ms.service: azure
 ms.topic: conceptual
 ms.date: 10/01/2021
-ms.author: prsandhu
+ms.author: rarco
 ms.reviewer: cynthn
 ms.custom: references_regions
 ---
@@ -28,8 +28,8 @@ Azure provides the most extensive global footprint of any cloud provider and is
 | Central US | North Europe | | Japan East |
 | East US | Norway East | | Korea Central |
 | East US 2 | UK South | | Southeast Asia |
-| South Central US | West Europe | | East Asia* |
-| US Gov Virginia | Sweden* | | |
+| South Central US | West Europe | | East Asia |
+| 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)