Merge pull request #217718 from MicrosoftDocs/main

Publish to Live, Wednesday 4AM PST, 11/09

Author: PMEds28

.openpublishing.redirection.json

@@ -5960,12 +5960,12 @@
         },
         {
             "source_path_from_root": "/articles/best-practices-availability-paired-regions.md",
-            "redirect_url": "/azure/availability-zones/cross-region-replication-azure",
+            "redirect_url": "/azure/reliability/cross-region-replication-azure",
             "redirect_document_id": true
         },
         {
-            "source_path_from_root": "/articles/availability-zones/index.md",
-            "redirect_url": "/azure/availability-zones/az-overview",
+            "source_path_from_root": "/articles/partner-solutions/index.md",
+            "redirect_url": "/azure/partner-solutions/overview",
             "redirect_document_id": false
         },
         {
@@ -29301,12 +29301,12 @@
         },
         {
             "source_path_from_root": "/articles/app-service/environment/overview-zone-redundancy.md",
-            "redirect_url": "/azure/availability-zones/migrate-app-service-environment",
+            "redirect_url": "/azure/reliability/migrate-app-service-environment",
             "redirect_document_id": true
         },
         {
             "source_path_from_root": "/articles/app-service/how-to-zone-redundancy.md",
-            "redirect_url": "/azure/availability-zones/migrate-app-service",
+            "redirect_url": "/azure/reliability/migrate-app-service",
             "redirect_document_id": true
         },
         {
@@ -29354,6 +29354,121 @@
             "redirect_url": "/azure/developer/java/ee/jboss-on-azure",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/availability-zones/az-overview.md",
+            "redirect_url": "/azure/reliablity/availability-zones-overview.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/index.md",
+            "redirect_url": "/azure/reliablity/index.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/az-region.md",
+            "redirect_URL": "/azure/reliability/availability-zones-service-support",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/business-continuity-management-program.md",
+            "redirect_URL": "/azure/reliability/business-continuity-management-program",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/cross-region-replication-azure.md",
+            "redirect_URL": "/azure/reliability/cross-region-replication-azure",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/glossary.md",
+            "redirect_URL": "/azure/reliability/glossary",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-app-service-environment.md",
+            "redirect_URL": "/azure/reliability/migrate-app-service-environment",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-api-mgt.md",
+            "redirect_URL": "/azure/reliability/migrate-api-mgt",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-app-configuration.md",
+            "redirect_URL": "/azure/reliability/migrate-app-configuration-mgt",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-app-gateway-v2.md",
+            "redirect_URL": "/azure/reliability/migrate-app-gateway-v2",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-container-instances.md",
+            "redirect_URL": "/azure/reliability/migrate-container-instances",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-functions.md",
+            "redirect_URL": "/azure/reliability/migrate-functions",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-load-balancer.md",
+            "redirect_URL": "/azure/reliability/migrate-load-balancer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-monitor-log-analytics.md",
+            "redirect_URL": "/azure/reliability/migrate-monitor-log-analytics",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-workload-aks-mysql.md",
+            "redirect_URL": "/azure/reliability/migrate-workload-aks-mysql",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-search-service.md",
+            "redirect_URL": "/azure/reliability/migrate-search-service-balancer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-app-service.md",
+            "redirect_URL": "/azure/reliability/migrate-app-service",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-cache-redis.md",
+            "redirect_URL": "/azure/reliability/migrate-cache-redis",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-recovery-services-vault.md",
+            "redirect_URL": "/azure/reliability/migrate-recovery-services-vault",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-storage.md",
+            "redirect_URL": "/azure/reliability/migrate-storage",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/migrate-vm.md",
+            "redirect_URL": "/azure/reliability/migrate-vm",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/overview.md",
+            "redirect_URL": "/azure/reliability/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/availability-zones/region-types-service-categories-azure.md",
+            "redirect_URL": "/azure/reliability/availability-service-by-category",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/pytorch-enterprise/index.yml",
             "redirect_url": "/azure/databricks/machine-learning/train-model/pytorch",

.whatsnew/.application-management.json

@@ -17,7 +17,7 @@
     },
     "areas": [
         {
-            "name": ".",
+            "name": [ "."],
             "heading": "Azure Active Directory application management"
         }
     ]

articles/active-directory-domain-services/concepts-migration-benefits.md

@@ -56,7 +56,7 @@ To get started, see [Migrate Azure AD Domain Services from the Classic virtual n
 [azure-files]: ../storage/files/storage-files-identity-auth-active-directory-domain-service-enable.md
 [hd-insights]: ../hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md
 [avd]: ../virtual-desktop/overview.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [howto-migrate]: migrate-from-classic-vnet.md
 [attributes]: synchronization.md#attribute-synchronization-and-mapping-to-azure-ad-ds
 [managed-disks]: ../virtual-machines/managed-disks-overview.md

articles/active-directory-domain-services/overview.md

@@ -103,7 +103,7 @@ To get started, [create a managed domain using the Azure portal][tutorial-create
 [tutorial-create]: tutorial-create-instance.md
 [azure-ad-connect]: ../active-directory/hybrid/whatis-azure-ad-connect.md
 [password-hash-sync]: ../active-directory/hybrid/how-to-connect-password-hash-synchronization.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [forest-trusts]: concepts-resource-forest.md
 [administration-concepts]: administration-concepts.md
 [synchronization]: synchronization.md

articles/active-directory-domain-services/powershell-create-instance.md

@@ -395,7 +395,7 @@ To see the managed domain in action, you can [domain-join a Windows VM][windows-
 [New-AzVirtualNetwork]: /powershell/module/Az.Network/New-AzVirtualNetwork
 [Get-AzSubscription]: /powershell/module/Az.Accounts/Get-AzSubscription
 [cloud-shell]: ../cloud-shell/cloud-shell-windows-users.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [New-AzNetworkSecurityRuleConfig]: /powershell/module/az.network/new-aznetworksecurityruleconfig
 [New-AzNetworkSecurityGroup]: /powershell/module/az.network/new-aznetworksecuritygroup
 [Set-AzVirtualNetworkSubnetConfig]: /powershell/module/az.network/set-azvirtualnetworksubnetconfig

articles/active-directory-domain-services/template-create-instance.md

@@ -338,7 +338,7 @@ To see the managed domain in action, you can [domain-join a Windows VM][windows-
 [windows-join]: join-windows-vm.md
 [tutorial-ldaps]: tutorial-configure-ldaps.md
 [tutorial-phs]: tutorial-configure-password-hash-sync.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [portal-deploy]: ../azure-resource-manager/templates/deploy-portal.md
 [powershell-deploy]: ../azure-resource-manager/templates/deploy-powershell.md
 [scoped-sync]: scoped-synchronization.md

articles/active-directory-domain-services/tutorial-create-instance-advanced.md

@@ -263,7 +263,7 @@ To see this managed domain in action, create and join a virtual machine to the d
 [configure-sspr]: ../active-directory/authentication/tutorial-enable-sspr.md
 [password-hash-sync-process]: ../active-directory/hybrid/how-to-connect-password-hash-synchronization.md#password-hash-sync-process-for-azure-ad-domain-services
 [resource-forests]: concepts-resource-forest.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [concepts-sku]: administration-concepts.md#azure-ad-ds-skus
 
 <!-- EXTERNAL LINKS -->

articles/active-directory-domain-services/tutorial-create-instance.md

@@ -213,7 +213,7 @@ Before you domain-join VMs and deploy applications that use the managed domain,
 [tutorial-create-instance-advanced]: tutorial-create-instance-advanced.md
 [skus]: overview.md
 [resource-forests]: concepts-resource-forest.md
-[availability-zones]: ../availability-zones/az-overview.md
+[availability-zones]: ../reliability/availability-zones-overview.md
 [concepts-sku]: administration-concepts.md#azure-ad-ds-skus
 
 <!-- EXTERNAL LINKS -->

articles/active-directory/app-provisioning/known-issues.md

@@ -108,9 +108,9 @@ The following applications and directories aren't yet supported.
    - When a user is managed by Azure AD Connect, the source of authority is on-premises Azure AD. So, user attributes can't be changed in Azure AD. This preview doesn't change the source of authority for users managed by Azure AD Connect.
    - Attempting to use Azure AD Connect and the on-premises provisioning to provision groups or users into Active Directory Domain Services can lead to creation of a loop, where Azure AD Connect can overwrite a change that was made by the provisioning service in the cloud. Microsoft is working on a dedicated capability for group or user writeback. Upvote the UserVoice feedback on [this website](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789/) to track the status of the preview. Alternatively, you can use [Microsoft Identity Manager](/microsoft-identity-manager/microsoft-identity-manager-2016) for user or group writeback from Azure AD to Active Directory.
 
-#### Connectors other than SQL
+#### Connectors other than SQL and LDAP
 
-   The Azure AD ECMA Connector Host is officially supported for the generic SQL connector. While it's possible to use other connectors such as the web services connector or custom ECMA connectors, it's *not yet supported*.
+   The Azure AD ECMA Connector Host is officially supported for the generic SQL and LDAP connectors. While it's possible to use other connectors such as the web services connector or custom ECMA connectors, it's *not yet supported*.
 
 #### Azure AD
 

articles/active-directory/develop/scenario-web-app-call-api-overview.md

@@ -9,9 +9,9 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 07/14/2020
+ms.date: 11/4/2022
 ms.author: jmprieur
-ms.custom: aaddev
+ms.custom: aaddev, engagement-fy23
 #Customer intent: As an application developer, I want to know how to write a web app that authenticates users and calls web APIs by using the Microsoft identity platform.
 ---
 
@@ -29,20 +29,18 @@ You add authentication to your web app so that it can sign users in and call a w
 
 ![Web app that calls web APIs](./media/scenario-webapp/web-app.svg)
 
-Web apps that call web APIs are confidential client applications.
-That's why they register a secret (an application password or certificate) with Azure Active Directory (Azure AD). This secret is passed in during the call to Azure AD to get a token.
+Web apps that call web APIs are confidential client applications. That's why they register a secret (an application password or certificate) with Azure Active Directory (Azure AD). This secret is passed in during the call to Azure AD to get a token.
 
 ## Specifics
 
-> [!NOTE]
-> Adding sign-in to a web app is about protecting the web app itself. That protection is achieved by using *middleware* libraries, not the Microsoft Authentication Library (MSAL). The preceding scenario, [Web app that signs in users](scenario-web-app-sign-user-overview.md), covered that subject.
->
-> This scenario covers how to call web APIs from a web app. You must get access tokens for those web APIs. You use MSAL libraries to acquire these tokens.
+Adding sign-in to a web app is about protecting the web app itself. That protection is achieved by using *middleware* libraries, not the Microsoft Authentication Library (MSAL). The preceding scenario, [Web app that signs in users](scenario-web-app-sign-user-overview.md), covered that subject.
 
-Development for this scenario involves these specific tasks:
+This scenario covers how to call web APIs from a web app. You must get access tokens for those web APIs. You use MSAL libraries to acquire these tokens.
 
-- During [application registration](scenario-web-app-call-api-app-registration.md), you must provide a reply URI, secret, or certificate to be shared with Azure AD. If you deploy your app to several locations, you'll provide a reply URI for each location.
-- The [application configuration](scenario-web-app-call-api-app-configuration.md) must provide the client credentials that were shared with Azure AD during application registration.
+Development for this scenario involves;
+
+- Providing a reply URI, secret, or certificate to be shared with Azure AD during [application registration](scenario-web-app-call-api-app-registration.md). If you deploy your app to several locations, you'll provide a reply URI for each location.
+- Providing the client credentials in the [application configuration](scenario-web-app-call-api-app-configuration.md). These credentials were shared with Azure AD during application registration.
 
 ## Recommended reading