Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into 20221228-validated-versions

Author: MikeRayMSFT

articles/active-directory/fundamentals/active-directory-data-storage-eu.md

@@ -79,7 +79,7 @@ Administrators can choose to enable or disable certain Azure AD features. If the
 
 * **Azure Active Directory Multi Tenant Collaboration** - With multi tenant collaboration scenarios enabled, customers can configure their tenant to collaborate with users from a different tenant. For example, a customer can invite users to their tenant in a B2B context. A customer can create a multi-tenant SaaS application that allows other third party tenants to provision the application in the third party tenant. Or, the customer can make two or more tenants affiliated with one another and act as a single tenant in certain scenarios, such as multi-tenant organization (MTO) formation, tenant to tenant sync, and shared e-mail domain sharing. Customer configuration and use of multi tenant collaboration may occur with tenants outside of the EU Data Residency and EU Data Boundary resulting in some customer data, such as user and device account data, usage data, and service configuration (application, policy, and group) stored and processed in the location of the collaborating tenant.
 * **Application Proxy** - Allows customers to access their on-premises web applications externally. Customers may choose advanced routing configurations that allow customer data to egress outside of the EU Data Residency and EU Data Boundary, including user account data, usage data, and application configuration data.
-* **Microsoft 365 Multi Geo** - Microsoft 365 Multi-Geo provides customers with the ability to expand their Microsoft 365 presence to multiple geographic regions/countries within a single existing Microsoft 365 tenant. Azure Active Directory will egress customer data to perform backup authentication to the locations configured by the customer. Types of customer data include user and device account data, branding data, and service configuration data (application, policy, and group).
+* **Microsoft 365 Multi Geo** - Microsoft 365 Multi-Geo provides customers with the ability to expand their Microsoft 365 presence to multiple geographic countries/regions within a single existing Microsoft 365 tenant. Azure Active Directory will egress customer data to perform backup authentication to the locations configured by the customer. Types of customer data include user and device account data, branding data, and service configuration data (application, policy, and group).
 
 ### Other EU Data Boundary online services
 

articles/aks/api-server-vnet-integration.md

@@ -12,8 +12,6 @@ ms.custom: references_regions
 
 An Azure Kubernetes Service (AKS) cluster configured with API Server VNet Integration (Preview) projects the API server endpoint directly into a delegated subnet in the VNet where AKS is deployed. API Server VNet Integartion enables network communication between the API server and the cluster nodes without requiring a private link or tunnel. The API server is available behind an Internal Load Balancer VIP in the delegated subnet, which the nodes are configured to utilize. By using API Server VNet Integration, you can ensure network traffic between your API server and your node pools remains on the private network only.
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## API server connectivity
 
 The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure subscription. A customer's cluster or node pool is in the customer's subscription. The server and the virtual machines that make up the cluster nodes can communicate with each other through the API server VIP and pod IPs that are projected into the delegated subnet.
@@ -31,33 +29,37 @@ API Server VNet Integration is available in all global Azure regions except the
 * Azure CLI with aks-preview extension 0.5.97 or later.
 * If using ARM or the REST API, the AKS API version must be 2022-04-02-preview or later.
 
-### Install the aks-preview CLI extension
+## Install the aks-preview Azure CLI extension
 
-```azurecli-interactive
-# Install the aks-preview extension
+[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
+
+To install the aks-preview extension, run the following command:
+
+```azurecli
 az extension add --name aks-preview
+```
+
+Run the following command to update to the latest version of the extension released:
 
-# Update the extension to make sure you have the latest version installed
+```azurecli
 az extension update --name aks-preview
 ```
 
-### Register the `EnableAPIServerVnetIntegrationPreview` preview feature
-
-To create an AKS cluster with API Server VNet Integration, you must enable the `EnableAPIServerVnetIntegrationPreview` feature flag on your subscription.
+## Register the 'EnableAPIServerVnetIntegrationPreview' feature flag
 
-Register the `EnableAPIServerVnetIntegrationPreview` feature flag by using the `az feature register` command, as shown in the following example:
+Register the `EnableAPIServerVnetIntegrationPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
 
 ```azurecli-interactive
 az feature register --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
 ```
 
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
+It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
 
 ```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/EnableAPIServerVnetIntegrationPreview')].{Name:name,State:properties.state}"
+az feature show --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
 ```
 
-When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
+When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
 
 ```azurecli-interactive
 az provider register --namespace Microsoft.ContainerService
@@ -227,11 +229,12 @@ az aks update -n <cluster-name> \
 For associated best practices, see [Best practices for network connectivity and security in AKS][operator-best-practices-network].
 
 <!-- LINKS - internal -->
-[az-provider-register]: /cli/azure/provider#az_provider_register
-[az-feature-register]: /cli/azure/feature#az_feature_register
-[az-feature-list]: /cli/azure/feature#az_feature_list
-[az-extension-add]: /cli/azure/extension#az_extension_add
-[az-extension-update]: /cli/azure/extension#az_extension_update
+[az-provider-register]: /cli/azure/provider#az-provider-register
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-list]: /cli/azure/feature#az-feature-list
+[az-feature-show]: /cli/azure/feature#az-feature-show
+[az-extension-add]: /cli/azure/extension#az-extension-add
+[az-extension-update]: /cli/azure/extension#az-extension-update
 [private-link-service]: ../private-link/private-link-service-overview.md#limitations
 [private-endpoint-service]: ../private-link/private-endpoint-overview.md
 [virtual-network-peering]: ../virtual-network/virtual-network-peering-overview.md

articles/aks/azure-cni-overlay.md

@@ -115,13 +115,13 @@ Register the `AzureOverlayPreview` feature flag by using the [az feature registe
 az feature register --namespace "Microsoft.ContainerService" --name "AzureOverlayPreview"
 ```
 
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature list][az-feature-list] command:
+It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
 
 ```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AzureOverlayPreview')].{Name:name,State:properties.state}"
+az feature show --namespace "Microsoft.ContainerService" --name "AzureOverlayPreview"
 ```
 
-When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
+When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
 
 ```azurecli-interactive
 az provider register --namespace Microsoft.ContainerService
@@ -157,4 +157,9 @@ The following steps create a new virtual network with a subnet for the cluster n
 
 ## Next steps
 
-To learn how to utilize AKS with your own Container Network Interface (CNI) plugin, see [Bring your own Container Network Interface (CNI) plugin](use-byo-cni.md).
+To learn how to utilize AKS with your own Container Network Interface (CNI) plugin, see [Bring your own Container Network Interface (CNI) plugin](use-byo-cni.md).
+
+<!-- LINKS - internal -->
+[az-provider-register]: /cli/azure/provider#az-provider-register
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-show]: /cli/azure/feature#az-feature-show

articles/aks/azure-cni-powered-by-cilium.md

@@ -19,8 +19,6 @@ By making use of eBPF programs loaded into the Linux kernel and a more efficient
 - Better observability of cluster traffic
 - Support for larger clusters (more nodes, pods, and services)
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## IP Address Management (IPAM) with Azure CNI Powered by Cilium
 
 Azure CNI Powered by Cilium can be deployed using two different methods for assigning pod IPs: 
@@ -55,33 +53,37 @@ Azure CNI powered by Cilium currently has the following limitations:
 * Azure CLI with aks-preview extension 0.5.109 or later.
 * If using ARM templates or the REST API, the AKS API version must be 2022-09-02-preview or later.
 
-### Install the aks-preview CLI extension
+## Install the aks-preview Azure CLI extension
 
-```azurecli-interactive
-# Install the aks-preview extension
+[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
+
+To install the aks-preview extension, run the following command:
+
+```azurecli
 az extension add --name aks-preview
+```
+
+Run the following command to update to the latest version of the extension released:
 
-# Update the extension to make sure you have the latest version installed
+```azurecli
 az extension update --name aks-preview
 ```
 
-### Register the `CiliumDataplanePreview` preview feature
-
-To create an AKS cluster with Azure CNI powered by Cilium, you must enable the `CiliumDataplanePreview` feature flag on your subscription.
+## Register the 'CiliumDataplanePreview' feature flag
 
-Register the `CiliumDataplanePreview` feature flag by using the `az feature register` command, as shown in the following example:
+Register the `CiliumDataplanePreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
 
 ```azurecli-interactive
 az feature register --namespace "Microsoft.ContainerService" --name "CiliumDataplanePreview"
 ```
 
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
+It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
 
 ```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/CiliumDataplanePreview')].{Name:name,State:properties.state}"
+az feature show --namespace "Microsoft.ContainerService" --name "CiliumDataplanePreview"
 ```
 
-When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
+When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
 
 ```azurecli-interactive
 az provider register --namespace Microsoft.ContainerService
@@ -174,3 +176,6 @@ Learn more about networking in AKS in the following articles:
 [aks-ingress-static-tls]: ingress-static-ip.md
 [aks-http-app-routing]: http-application-routing.md
 [aks-ingress-internal]: ingress-internal-ip.md
+[az-provider-register]: /cli/azure/provider#az-provider-register
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-show]: /cli/azure/feature#az-feature-show

articles/aks/configure-kube-proxy.md

@@ -20,40 +20,42 @@ author: phealy
 
 The AKS managed `kube-proxy` DaemonSet can also be disabled entirely if that is desired to support [bring-your-own CNI][aks-byo-cni].
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## Prerequisites
 
 * Azure CLI with aks-preview extension 0.5.105 or later.
 * If using ARM or the REST API, the AKS API version must be 2022-08-02-preview or later.
 
-### Install the aks-preview CLI extension
+## Install the aks-preview Azure CLI extension
 
-```azurecli-interactive
-# Install the aks-preview extension
+[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
+
+To install the aks-preview extension, run the following command:
+
+```azurecli
 az extension add --name aks-preview
+```
+
+Run the following command to update to the latest version of the extension released:
 
-# Update the extension to make sure you have the latest version installed
+```azurecli
 az extension update --name aks-preview
 ```
 
-### Register the `KubeProxyConfigurationPreview` preview feature
-
-To create an AKS cluster with custom `kube-proxy` configuration, you must enable the `KubeProxyConfigurationPreview` feature flag on your subscription.
+## Register the 'KubeProxyConfigurationPreview' feature flag
 
-Register the `KubeProxyConfigurationPreview` feature flag by using the `az feature register` command, as shown in the following example:
+Register the `KubeProxyConfigurationPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
 
 ```azurecli-interactive
 az feature register --namespace "Microsoft.ContainerService" --name "KubeProxyConfigurationPreview"
 ```
 
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
+It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
 
 ```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/KubeProxyConfigurationPreview')].{Name:name,State:properties.state}"
+az feature show --namespace "Microsoft.ContainerService" --name "KubeProxyConfigurationPreview"
 ```
 
-When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
+When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
 
 ```azurecli-interactive
 az provider register --namespace Microsoft.ContainerService
@@ -135,4 +137,7 @@ Learn more about Kubernetes services at the [Kubernetes services documentation][
 [aks-schema-kubeproxyconfig]: /azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#containerservicenetworkprofilekubeproxyconfig
 
 <!-- LINKS - Internal -->
-[aks-byo-cni]: use-byo-cni.md
+[aks-byo-cni]: use-byo-cni.md
+[az-provider-register]: /cli/azure/provider#az-provider-register
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-show]: /cli/azure/feature#az-feature-show

articles/aks/configure-kubenet-dual-stack.md

@@ -12,8 +12,6 @@ AKS clusters can now be deployed in a dual-stack (using both IPv4 and IPv6 addre
 
 This article shows you how to use dual-stack networking with an AKS cluster. For more information on network options and considerations, see [Network concepts for Kubernetes and AKS][aks-network-concepts].
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
 ## Limitations
 > [!NOTE]
 > Dual-stack kubenet networking is currently not available in sovereign clouds. This note will be removed when rollout is complete.
@@ -34,36 +32,40 @@ This article shows you how to use dual-stack networking with an AKS cluster. For
 * Azure CLI with the `aks-preview` extension 0.5.48 or newer.
 * If using Azure Resource Manager templates, schema version 2021-10-01 is required.
 
-### Register the `AKS-EnableDualStack` preview feature
+## Install the aks-preview Azure CLI extension
 
-To create an AKS dual-stack cluster, you must enable the `AKS-EnableDualStack` feature flag on your subscription.
+[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
 
-Register the `AKS-EnableDualStack` feature flag by using the `az feature register` command, as shown in the following example:
+To install the aks-preview extension, run the following command:
 
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
+```azurecli
+az extension add --name aks-preview
 ```
 
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
+Run the following command to update to the latest version of the extension released:
 
-```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AKS-EnableDualStack')].{Name:name,State:properties.state}"
+```azurecli
+az extension update --name aks-preview
 ```
 
-When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
+## Register the 'AKS-EnableDualStack' feature flag
+
+Register the `AKS-EnableDualStack` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
 
 ```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
+az feature register --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
 ```
 
-### Install the aks-preview CLI extension
+It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
 
 ```azurecli-interactive
-# Install the aks-preview extension
-az extension add --name aks-preview
+az feature show --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
+```
 
-# Update the extension to make sure you have the latest version installed
-az extension update --name aks-preview
+When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
+
+```azurecli-interactive
+az provider register --namespace Microsoft.ContainerService
 ```
 
 ## Overview of dual-stack networking in Kubernetes
@@ -400,4 +402,7 @@ curl -s "http://[${SERVICE_IP}]" | head -n5
 [express-route]: ../expressroute/expressroute-introduction.md
 [network-comparisons]: concepts-network.md#compare-network-models
 [custom-route-table]: ../virtual-network/manage-route-table.md
-[user-assigned managed identity]: use-managed-identity.md#bring-your-own-control-plane-mi
+[user-assigned managed identity]: use-managed-identity.md#bring-your-own-control-plane-mi
+[az-provider-register]: /cli/azure/provider#az-provider-register
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-show]: /cli/azure/feature#az-feature-show