Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into clear-system-data-sensor

Author: yoninalmsft

.openpublishing.publish.config.json

@@ -164,6 +164,12 @@
       "branch": "dev",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "functions-quickstart-templates-v1",
+      "url": "https://github.com/Azure/azure-functions-templates",
+      "branch": "v1.x",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-functions-samples-java",
       "url": "https://github.com/Azure-Samples/azure-functions-samples-java",

.openpublishing.redirection.json

@@ -130,6 +130,11 @@
             "redirect_url": "/azure/aks/monitor-aks",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/aks/workload-identity-migration-sidecar.md",
+            "redirect_url": "/azure/aks/workload-identity-migrate-from-pod-identity",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/api-management/zone-redundancy.md",
             "redirect_url": "/azure/availability-zones/migrate-api-mgt",
@@ -800,12 +805,12 @@
         },
         {
             "source_path_from_root": "/articles/aks/dapr-troubleshooting.md",
-            "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+            "redirect_url": "/troubleshoot/azure/azure-kubernetes/troubleshoot-dapr-extension-installation-errors",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/aks/csi-secrets-store-troubleshooting.md",
-            "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+            "redirect_url": "/troubleshoot/azure/azure-kubernetes/troubleshoot-key-vault-csi-secrets-store-csi-driver",
             "redirect_document_id": false
         },
         {
@@ -5955,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
         },
         {
@@ -29296,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
         },
         {
@@ -29349,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",

articles/active-directory-b2c/aad-sspr-technical-profile.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 06/23/2020
+ms.date: 11/08/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -26,8 +26,6 @@ This technical profile:
 - Uses the Azure AD SSPR service to generate and send a code to an email address, and then verifies the code.
 - Validates an email address via a verification code.
 
-[!INCLUDE [b2c-public-preview-feature](../../includes/active-directory-b2c-public-preview.md)]
-
 ## Protocol
 
 The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C:

articles/active-directory-b2c/custom-policy-developer-notes.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 06/27/2022
+ms.date: 11/08/2022
 ms.custom: project-no-code
 ms.author: kengaderdus
 ms.subservice: B2C
@@ -22,7 +22,9 @@ Azure Active Directory B2C [user flows and custom policies](user-flow-overview.m
 ## Terms for features in public preview
 
 - We encourage you to use public preview features for evaluation purposes only.
+
 - [Service level agreements (SLAs)](https://azure.microsoft.com/support/legal/sla/active-directory-b2c) don't apply to public preview features.
+
 - Support requests for public preview features can be submitted through regular support channels.
 
 ## User flows
@@ -156,7 +158,7 @@ The following table summarizes the Security Assertion Markup Language (SAML) app
 | ------- | :--: | ----- |
 | [MFA using time-based one-time password (TOTP) with authenticator apps](multi-factor-authentication.md#verification-methods) | GA |  Users can use any authenticator app that supports TOTP verification, such as the [Microsoft Authenticator app](https://www.microsoft.com/security/mobile-authenticator-app).|
 | [Phone factor authentication](phone-factor-technical-profile.md) | GA |  |
-| [Azure AD MFA authentication](multi-factor-auth-technical-profile.md) | Preview |  |
+| [Azure AD MFA authentication](multi-factor-auth-technical-profile.md) | GA |  |
 | [One-time password](one-time-password-technical-profile.md) | GA |  |
 | [Azure Active Directory](active-directory-technical-profile.md) as local directory | GA |  |
 | [Predicate validations](predicates.md) | GA | For example, password complexity. |

articles/active-directory-b2c/multi-factor-auth-technical-profile.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 12/09/2021
+ms.date: 11/08/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -18,7 +18,6 @@ ms.subservice: B2C
 
 Azure Active Directory B2C (Azure AD B2C) provides support for verifying a phone number by using a verification code, or verifying a Time-based One-time Password (TOTP) code.
 
-[!INCLUDE [b2c-public-preview-feature](../../includes/active-directory-b2c-public-preview.md)]
 
 ## Protocol
 

articles/active-directory-b2c/self-asserted-technical-profile.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 02/17/2022
+ms.date: 11/07/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -50,8 +50,6 @@ In a self-asserted technical profile, you can use the **InputClaims** and **Inpu
 
 ## Display claims
 
-The display claims feature is currently in **preview**.
-
 The **DisplayClaims** element contains a list of claims to be presented on the screen for collecting data from the user. To prepopulate the values of display claims, use the input claims that were previously described. The element may also contain a default value.
 
 The order of the claims in **DisplayClaims** specifies the order in which Azure AD B2C renders the claims on the screen. To force the user to provide a value for a specific claim, set the **Required** attribute of the **DisplayClaim** element to `true`.
@@ -133,7 +131,7 @@ Use output claims when:
 - **Claims are output by output claims transformation**.
 - **Setting a default value in an output claim** without collecting data from the user or returning the data from the validation technical profile. The `LocalAccountSignUpWithLogonEmail` self-asserted technical profile sets the **executed-SelfAsserted-Input** claim to `true`.
 - **A validation technical profile returns the output claims** - Your technical profile may call a validation technical profile that returns some claims. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. For example, when signing in with a local account, the self-asserted technical profile named `SelfAsserted-LocalAccountSignin-Email` calls the validation technical profile named `login-NonInteractive`. This technical profile validates the user credentials and also returns the user profile. Such as 'userPrincipalName', 'displayName', 'givenName' and 'surName'.
-- **A display control returns the output claims** - Your technical profile may have a reference to a [display control](display-controls.md). The display control returns some claims, such as the verified email address. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. The display control feature is currently in **preview**.
+- **A display control returns the output claims** - Your technical profile may have a reference to a [display control](display-controls.md). The display control returns some claims, such as the verified email address. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. 
 
 The following example demonstrates the use of a self-asserted technical profile that uses both display claims and output claims.
 

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