Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/active-directory/app-provisioning/skip-out-of-scope-deletions.md

@@ -76,7 +76,7 @@ Copy the updated text from Step 3 into the "Request Body".
 
 Click on “Run Query”. 
 
-You should get the output as "Success – Status Code 204". 
+You should get the output as "Success – Status Code 204". If you receive an error you may need to check that your account has Read/Write permissions for ServicePrincipalEndpoint. You can find this permission by clicking on the *Modify permissions* tab in Graph Explorer.
 
    ![PUT response](./media/skip-out-of-scope-deletions/skip-06.png)
 

articles/active-directory/hybrid/how-to-connect-install-prerequisites.md

@@ -36,7 +36,6 @@ Before you install Azure AD Connect, there are a few things that you need.
 
 ### On-premises Active Directory
 * The Active Directory schema version and forest functional level must be Windows Server 2003 or later. The domain controllers can run any version as long as the schema version and forest-level requirements are met.
-* If you plan to use the feature *password writeback*, the domain controllers must be on Windows Server 2016 or later.
 * The domain controller used by Azure AD must be writable. Using a read-only domain controller (RODC) *isn't supported*, and Azure AD Connect doesn't follow any write redirects.
 * Using on-premises forests or domains by using "dotted" (name contains a period ".") NetBIOS names *isn't supported*.
 * We recommend that you [enable the Active Directory recycle bin](how-to-connect-sync-recycle-bin.md).

articles/aks/csi-storage-drivers.md

@@ -3,7 +3,7 @@ title: Enable Container Storage Interface (CSI) drivers on Azure Kubernetes Serv
 description: Learn how to enable the Container Storage Interface (CSI) drivers for Azure disks and Azure Files in an Azure Kubernetes Service (AKS) cluster.
 services: container-service
 ms.topic: article
-ms.date: 03/10/2022
+ms.date: 03/11/2022
 author: palma21
 
 ---
@@ -17,18 +17,12 @@ The CSI storage driver support on AKS allows you to natively use:
 - [*Azure Files*](azure-files-csi.md), which can be used to mount an SMB 3.0/3.1 share backed by an Azure Storage account to pods. With Azure Files, you can share data across multiple nodes and pods. Azure Files can use Azure Standard Storage backed by regular HDDs or Azure Premium Storage backed by high-performance SSDs.
 
 > [!IMPORTANT]
-> Starting in Kubernetes version 1.21, Kubernetes will use CSI drivers only and by default. These drivers are the future of storage support in Kubernetes.
+> Starting in Kubernetes version 1.21, AKS will use CSI drivers only and by default. CSI migration is also turned on starting from AKS 1.21, existing in-tree persistent volumes continue to function as they always have; however, behind the scenes Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers.
 > 
 > Please remove manual installed open source Azure Disk and Azure File CSI drivers before upgrading to AKS 1.21.
 > 
 > *In-tree drivers* refers to the current storage drivers that are part of the core Kubernetes code versus the new CSI drivers, which are plug-ins.
 
-## Limitations
-
-- This feature can only be set at cluster creation time.
-- The minimum Kubernetes minor version that supports CSI drivers is v1.17.
-- The default storage class will be the `managed-csi` storage class.
-
 ## Install CSI storage drivers on a new cluster with version < 1.21
 
 Create a new cluster that can use CSI storage drivers for Azure disks and Azure Files by using the following CLI commands. Use the `--aks-custom-headers` flag to set the `EnableAzureDiskFileCSIDriver` feature.
@@ -67,14 +61,9 @@ $ echo $(kubectl get CSINode <NODE NAME> -o jsonpath="{.spec.drivers[1].allocata
  - [Set up Azure File CSI driver on AKS cluster](https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/install-driver-on-aks.md)
 
 ## Migrating custom in-tree storage classes to CSI
-If you have created custom storage classes based on the in-tree storage drivers, these will need to be migrated when you have upgraded your cluster to 1.21.x.
-
-Whilst explicit migration to the CSI provider is not needed for your storage classes to still be valid, to be able to use CSI features (snapshotting etc.) you will need to carry out the migration.
-
-Migration of these storage classes will involve deleting the existing storage classes, and re-provisioning them with the provisioner set to **disk.csi.azure.com** if using Azure Disks, and **files.csi.azure.com** if using Azure Files.  
-
-Whilst this will update the mapping of the storage classes, the binding of the Persistent Volume to the CSI provisioner will only take place at provisioning time. This could be during a cordon & drain operation (cluster update) or by detaching and reattaching the Volume.
+If you have created in-tree driver storage classes, those storage classes will continue to work since CSI migration is turned on after upgrading your cluster to 1.21.x, while if you want to use CSI features (snapshotting etc.) you will need to carry out the migration.
 
+Migration of these storage classes will involve deleting the existing storage classes, and re-creating them with the provisioner set to **disk.csi.azure.com** if using Azure Disks, and **files.csi.azure.com** if using Azure Files.  
 
 ### Migrating Storage Class provisioner
 
@@ -86,12 +75,11 @@ As an example for Azure disks:
 kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
-  name: managed-premium-retain
+  name: custom-managed-premium
 provisioner: kubernetes.io/azure-disk
-reclaimPolicy: Retain
+reclaimPolicy: Delete
 parameters:
-  storageaccounttype: Premium_LRS
-  kind: Managed
+  storageAccountType: Premium_LRS
 ```
 
 #### CSI storage class definition
@@ -100,26 +88,30 @@ parameters:
 kind: StorageClass
 apiVersion: storage.k8s.io/v1
 metadata:
-  name: managed-premium-retain
+  name: custom-managed-premium
 provisioner: disk.csi.azure.com
-reclaimPolicy: Retain
+reclaimPolicy: Delete
 parameters:
-  storageaccounttype: Premium_LRS
-  kind: Managed
+  storageAccountType: Premium_LRS
 ```
 
 The CSI storage system supports the same features as the In-tree drivers, so the only change needed would be the provisioner.
 
-
-### Migrating in-tree disk persistent volumes
+## Migrating in-tree persistent volumes
 
 > [!IMPORTANT]
 > If your in-tree Persistent Volume reclaimPolicy is set to Delete you will need to change the Persistent Volume to Retain to persist your data.  This can be achieved via a [patch operation on the PV](https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/). For example:
 > ```console
 > $ kubectl patch pv pv-azuredisk --type merge --patch '{"spec": {"persistentVolumeReclaimPolicy": "Retain"}}'
 > ```
 
-If you have in-tree persistent volumes, get disk ID from `azureDisk.diskURI` and then follow this [guide][azure-disk-static-mount] to set up CSI driver persistent volumes
+### Migrating in-tree Azure Disk persistent volumes
+
+If you have in-tree Azure Disk persistent volumes, get `diskURI` from in-tree persistent volumes and then follow this [guide][azure-disk-static-mount] to set up CSI driver persistent volumes
+
+### Migrating in-tree Azure File persistent volumes
+
+If you have in-tree Azure File persistent volumes, get `secretName`, `shareName` from in-tree persistent volumes and then follow this [guide][azure-file-static-mount] to set up CSI driver persistent volumes
 
 ## Next steps
 
@@ -140,6 +132,7 @@ If you have in-tree persistent volumes, get disk ID from `azureDisk.diskURI` and
 <!-- LINKS - internal -->
 [azure-disk-volume]: azure-disk-volume.md
 [azure-disk-static-mount]: azure-disk-volume.md#mount-disk-as-volume
+[azure-file-static-mount]: azure-files-volume.md#mount-file-share-as-a-persistent-volume
 [azure-files-pvc]: azure-files-dynamic-pv.md
 [premium-storage]: ../virtual-machines/disks-types.md
 [az-disk-list]: /cli/azure/disk#az_disk_list

articles/app-service/environment/migrate.md

@@ -3,7 +3,7 @@ title: Migrate to App Service Environment v3 by using the migration feature
 description: Overview of the migration feature for migration to App Service Environment v3
 author: seligj95
 ms.topic: article
-ms.date: 2/10/2022
+ms.date: 3/14/2022
 ms.author: jordanselig
 ms.custom: references_regions
 ---
@@ -19,13 +19,22 @@ App Service can now automate migration of your App Service Environment v2 to an
 
 At this time, App Service Environment migrations to v3 using the migration feature support both [Internal Load Balancer (ILB)](create-ilb-ase.md) and [external (internet facing with public IP)](create-external-ase.md) App Service Environment v2 in the following regions:
 
-- West Central US
-- Canada Central
-- UK South
-- Germany West Central
-- East Asia
 - Australia East
+- Australia Central
 - Australia Southeast
+- Canada Central
+- Central India
+- East Asia
+- East US
+- East US 2
+- France Central
+- Germany West Central
+- Korea Central
+- Norway East
+- Switzerland North
+- UAE North
+- UK South
+- West Central US
 
 You can find the version of your App Service Environment by navigating to your App Service Environment in the [Azure portal](https://portal.azure.com) and selecting **Configuration** under **Settings** on the left-hand side. You can also use [Azure Resource Explorer](https://resources.azure.com/) and review the value of the `kind` property for your App Service Environment.
 

articles/azure-maps/media/power-bi-visual/pie-chart-layer.png

@@ -0,0 +1,69 @@
+---
+title: Add a pie chart layer to an Azure Maps Power BI visual
+titleSuffix: Microsoft Azure Maps
+description: In this article, you will learn how to use the pie chart layer in an Azure Maps Power BI visual.
+author: stevemunk
+ms.author: v-munksteve
+ms.date: 03/15/2022
+ms.topic: how-to
+ms.service: azure-maps
+services: azure-maps
+---
+
+# Add a pie chart layer
+
+In this article, you will learn how to add a pie chart layer to an Azure Maps Power BI visual.
+
+A pie chart is a visual representation of data in the form of a circular chart or *pie* where each slice represents an element of the dataset that is shown as a percentage of the whole. A list of numerical variables along with categorical (location) variables are required to represent data in the form of a pie chart.
+
+:::image type="content" source="./media/power-bi-visual/pie-chart-layer.png" alt-text="A Power B I visual showing the pie chart layer.":::
+
+> [!NOTE]
+> The data used in this article comes from the [Power BI Sales and Marketing Sample](/power-bi/create-reports/sample-datasets#download-original-sample-power-bi-files).
+
+## Prerequisites
+
+- [Get started with Azure Maps Power BI visual](./power-bi-visual-get-started.md).
+- Understand [layers in the Azure Maps Power BI visual](./power-bi-visual-understanding-layers.md).
+
+## Add the pie chart layer
+
+The pie chart layer is added automatically based on what fields in the **Visualizations** pane have values, these fields include location, size and legend.
+
+:::image type="content" source="./media/power-bi-visual/visualizations-settings-pie-chart.png" alt-text="A screenshot showing the fields required for the pie chart layer Power B I.":::
+
+The following steps will walk you through creating a pie chart layer.
+
+1. Select two location sources from the **Fields** pane, such as city/state, to add to the **Location** field.
+1. Select a numerical field from your table, such as sales, and add it to the **Size** field in the **Visualizations** pane. This field must contain the numerical values used in the pie chart.
+1. Select a data field from your table that can be used as the category that the numerical field applies to, such as *manufacturer*, and add it to the **Legend** field in the **Visualizations** pane. This will appear as the slices of the pie, the size of each slice is a percentage of the whole based on the value in the size field, such as the number of sales broken out by manufacturer.
+1. Next, in the **Format** tab of the **Visualizations** pane, switch the **Bubbles** toggle to **On**.
+
+The pie chart layer should now appear. Next you can adjust the Pie chart settings such as size and transparency.
+
+## Pie chart layer settings
+
+Pie Chart layer is an extension of the bubbles layer, so all settings are made in the **Bubbles** section. If a field is passed into the **Legend** bucket of the **Fields** pane, the pie charts will be populated and will be colored based on their categorization. The outline of the pie chart is white by default but can be changed to a new color. The following are the settings in the **Format** tab of the **Visualizations** pane that are available to a **Pie Chart layer**.
+
+:::image type="content" source="./media/power-bi-visual/visualizations-settings-bubbles.png" alt-text="A screenshot showing the pie chart settings that appear in the bubbles section when the format tab is selected in the visualization pane in power B I.":::
+
+| Setting               | Description                                                       |
+|-----------------------|-------------------------------------------------------------------|
+| Size                  | The size of each bubble.                                          |
+| Fill transparency     | Transparency of each pie chart.                                   |
+| Outline color         | Color that outlines the pie chart.                                |
+| Outline transparency  | Transparency of the outline.                                      |
+| Outline width         | Width of the outline in pixels.                                   |
+| Min zoom              | Minimum zoom level tiles are available.                           |
+| Max zoom              | Maximum zoom level tiles are available.                           |
+| Layer position        | Specifies the position of the layer relative to other map layers. |
+
+## Next steps
+
+Change how your data is displayed on the map:
+
+> [!div class="nextstepaction"]
+> [Add a bar chart layer](power-bi-visual-add-bar-chart-layer.md)
+
+> [!div class="nextstepaction"]
+> [Add a heat map layer](power-bi-visual-add-heat-map-layer.md)

articles/azure-maps/media/power-bi-visual/plus-sign.png

@@ -333,6 +333,8 @@ items:
       href: power-bi-visual-understanding-layers.md
     - name: Add a bubble layer
       href: power-bi-visual-add-bubble-layer.md
+    - name: Add a pie chart layer
+      href: power-bi-visual-add-pie-chart-layer.md
     - name: Add a bar chart layer
       href: power-bi-visual-add-bar-chart-layer.md
     - name: Add a heat map layer