Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into vnet-peer-spn

Author: asudbring

articles/azure-monitor/app/convert-classic-resource.md

@@ -28,6 +28,11 @@ Workspace-based resources:
 >
 > * Diagnostic settings export might increase costs. For more information, see [Diagnostic settings-based export](export-telemetry.md#diagnostic-settings-based-export).
 
+> [!WARNING]
+> Continuous Export within Classic Application Insights will be shut down on May 15th, 2024. After this date, your Continuous Export configurations will no longer be available.
+> 
+> Beginning April 29th, 2024, and ending May 1st, 2024, Continuous Export will undergo maintenance in preparation for shut down. During this time, Continuous Export will be unavailable. Any data which would have been exported during this time will be exported at the conclusion of the maintenance window on 1 May 2024. Depending on the amount of data you're exporting, it may take up to 72 hours to fully recover.
+
 ## New capabilities
 
 Workspace-based Application Insights resources allow you to take advantage of the latest capabilities of Azure Monitor and Log Analytics:

articles/azure-monitor/cost-usage.md

@@ -155,7 +155,14 @@ To explore the data in more detail, click on the icon in the upper-right corner
 :::image type="content" source="logs/media/manage-cost-storage/logs.png" lightbox="logs/media/manage-cost-storage/logs.png" alt-text="Screenshot of log query with Usage table in Log Analytics.":::
 
 ### Application insights
-To learn about your usage trends for your classic Application Insights resource, select **Usage and Estimated Costs** from the **Applications** menu in the Azure portal. 
+
+#### Workspace-based resources
+
+To learn about usage on your workspace-based resources, see [Data volume trends for workspace-based resources](logs/analyze-usage.md#data-volume-trends-for-workspace-based-resources).
+
+#### Classic resources
+
+To learn about usage on retired classic Application Insights resources, select **Usage and Estimated Costs** from the **Applications** menu in the Azure portal. 
 
 :::image type="content" source="media/usage-estimated-costs/app-insights-usage.png" lightbox="media/usage-estimated-costs/app-insights-usage.png" alt-text="Screenshot of usage and estimated costs for Application Insights in Azure portal.":::
 

articles/data-catalog/.openpublishing.redirection.data-catalog.json

@@ -29,6 +29,11 @@
         "source_path_from_root": "/articles/data-catalog/data-catalog-common-scenarios.md",
         "redirect_url": "/azure/data-catalog/overview",
         "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/data-catalog/data-catalog-migration-to-azure-purview.md",
+        "redirect_url": "/azure/data-catalog/data-catalog-migration-to-microsoft-purview",
+        "redirect_document_id": false
       }
 ]
 }

articles/data-catalog/TOC.yml

@@ -18,7 +18,7 @@
 - name: How-to guides
   items:
   - name: Migrate to Microsoft Purview
-    href: data-catalog-migration-to-azure-purview.md
+    href: data-catalog-migration-to-microsoft-purview.md
   - name: Register data sources
     href: data-catalog-how-to-register.md
   - name: Discover data sources

articles/data-catalog/data-catalog-migration-to-azure-purview.md renamed to articles/data-catalog/data-catalog-migration-to-microsoft-purview.md

@@ -3,42 +3,44 @@ title: Migrate from Azure Data Catalog to Microsoft Purview
 description: Steps to migrate from Azure Data Catalog to Microsoft's unified data governance service--Microsoft Purview.
 ms.service: data-catalog
 ms.topic: how-to 
-ms.date: 12/13/2023
+ms.date: 04/24/2024
 ms.custom: template-how-to
 #Customer intent: As an Azure Data Catalog user, I want to know why and how to migrate to Microsoft Purview so that I can use the best tools to manage my data.
 ---
 
 # Migrate from Azure Data Catalog to Microsoft Purview
 
-Microsoft launched a unified data governance service to help manage and govern your on-premises, multicloud, and software-as-a-service (SaaS) data. Microsoft Purview creates a map of your data landscape with automated data discovery, sensitive data classification, and end-to-end data lineage. Microsoft Purview data governance solutions enable data curators to manage and secure their data estate and empowers data consumers to find valuable, trustworthy data. 
+Microsoft launched a unified data governance service to help manage and govern your on-premises, multicloud, and software-as-a-service (SaaS) data. Microsoft Purview creates a map of your data landscape with automated data discovery, sensitive data classification, and end-to-end data lineage. Microsoft Purview data governance solutions enable data curators to manage and secure their data estate and empowers data consumers to find valuable, trustworthy data.
 
-The document shows you how to do the migration from Azure Data Catalog to Microsoft Purview. 
+The document shows you how to do the migration from Azure Data Catalog to Microsoft Purview.
 
 ## Recommended approach
 
 To migrate from Azure Data Catalog to Microsoft Purview, we recommend the following approach:
 
-:heavy_check_mark: Step 1: [Assess readiness](#assess-readiness)
+:heavy_check_mark: Step 1: [Assess readiness.](#assess-readiness)
 
-:heavy_check_mark: Step 2: [Prepare to migrate](#prepare-to-migrate)
+:heavy_check_mark: Step 2: [Prepare to migrate.](#prepare-to-migrate)
 
-:heavy_check_mark: Step 3: [Migrate to Microsoft Purview](#migrate-to-microsoft-purview)
+:heavy_check_mark: Step 3: [Migrate to Microsoft Purview.](#migrate-to-microsoft-purview)
 
-:heavy_check_mark: Step 4: [Cutover from Azure Data Catalog to Microsoft Purview](#cutover-from-azure-data-catalog-to-microsoft-purview)
+:heavy_check_mark: Step 4: [Cutover from Azure Data Catalog to Microsoft Purview.](#cutover-from-azure-data-catalog-to-microsoft-purview)
 
 > [!NOTE]
 > Azure Data Catalog and Microsoft Purview are different services, so there is no in-place upgrade experience. Intentional migration effort required.
 
 ## Assess readiness
 
-Look at [Microsoft Purview](https://azure.microsoft.com/services/purview/) and understand key differences of Azure Data Catalog and Microsoft Purview.
+Look at [Microsoft Purview](/purview/purview) and understand key differences of Azure Data Catalog and Microsoft Purview.
+
+[Microsoft Purview's Data Catalog](/purview/what-is-data-catalog) is the next iteration of the current Azure Data Catalog experience.
 
 ||Azure Data Catalog  |Microsoft Purview |
 |---------|---------|---------|
 |**Pricing**    |[User based model](https://azure.microsoft.com/pricing/details/data-catalog/)      |[Pay-as-you-go model](https://azure.microsoft.com/pricing/details/azure-purview/)       |
-|**Platform**    |[Data catalog](overview.md)     |[Unified governance platform for data discoverability, classification, lineage, and governance.](../purview/overview.md)        |
-|**Data sources supported** | [Data Catalog supported sources](data-catalog-dsr.md)| [Microsoft Purview supported sources](../purview/microsoft-purview-connector-overview.md)|
-|**Extensibility** |N/A  |[Extensible on Apache Atlas](../purview/tutorial-purview-tools.md)|
+|**Platform**    |[Data catalog](overview.md)     |[Unified governance platform for data discoverability, classification, lineage, and governance.](/purview/purview)        |
+|**Data sources supported** | [Data Catalog supported sources](data-catalog-dsr.md)| [Microsoft Purview supported sources](/purview/microsoft-purview-connector-overview)|
+|**Extensibility** |N/A  |[Extensible on Apache Atlas](/purview/tutorial-atlas-2-2-apis)|
 |**SDK/PowerShell support** |N/A |[Supports REST APIs](/rest/api/purview/) |
 
 ## Prepare to migrate
@@ -50,38 +52,39 @@ If your organization already has Microsoft Purview accounts, follow the [existin
 
 1. Review the article for the [Free version of Microsoft Purview governance solutions](/purview/free-version-get-started) to get started with the Microsoft Purview trial. You can try some of the new features in the free version with [Azure data sources you already have access to](/purview/live-view).
 1. Review the [Microsoft Purview governance solutions](/purview/governance-solutions-overview) for information about all the solutions available when you [upgrade to the enterprise version of Microsoft Purview governance solutions](/purview/upgrade).
-1. Determine the impact that a migration will have on your business. 
+1. Determine the impact that a migration will have on your business.
     For example: how will Azure Data catalog be used until the transition is complete?
-1. Create a migration plan using the [Microsoft Purview deployment checklist.](../purview/tutorial-azure-purview-checklist.md)
+1. Create a migration plan using the [data governance quick start](/purview/data-catalog-get-started) and the [Microsoft Purview data governance tutorial](/purview/section2-scan-your-assets).
 
 ### Existing Microsoft Purview customer guide
 
 1. Identify data sources that you'll migrate.
     Take this opportunity to identify logical and business connections between your data sources and assets. Microsoft Purview will allow you to create a map of your data landscape that reflects how your data is used and discovered in your organization.
-1. Review [Microsoft Purview best practices for deployment and architecture](../purview/deployment-best-practices.md) to develop a deployment strategy for Microsoft Purview.
-1. Determine the impact that a migration will have on your business. 
+1. Review [Microsoft Purview best practices for data catalog](/purview/data-catalog-best-practices) to develop a deployment strategy for your Microsoft Purview Data Catalog.
+1. Determine the impact that a migration will have on your business.
     For example: how will Azure Data catalog be used until the transition is complete?
-1. Create a migration plan using the [Microsoft Purview deployment checklist.](../purview/tutorial-azure-purview-checklist.md)
 
 ## Migrate to Microsoft Purview
 
-[Create a Microsoft Purview account](../purview/create-catalog-portal.md), [create collections](../purview/create-catalog-portal.md) in your data map, set up [permissions for your users](../purview/catalog-permissions.md), and onboard your data sources.
-    
-We suggest you review the Microsoft Purview best practices documentation before deploying your Microsoft Purview account, so you can deploy the best environment for your data landscape.
+We suggest you review the Microsoft Purview best practices documentation before deploying Microsoft Purview, so you can deploy the best environment for your data landscape.
 Here's a selection of articles that might help you get started:
-- [Microsoft Purview deployment checklist](../purview/tutorial-azure-purview-checklist.md)
-- [Microsoft Purview security best practices](../purview/concept-best-practices-security.md)
-- [Accounts architecture best practices](../purview/concept-best-practices-accounts.md)
-- [Collections architectures best practices](../purview/concept-best-practices-collections.md)
-- [Create a collection](../purview/quickstart-create-collection.md)
-- [Import Azure sources to Microsoft Purview at scale](../purview/tutorial-data-sources-readiness.md)
-- [Tutorial: Onboard an on-premises SQL Server instance](../purview/tutorial-register-scan-on-premises-sql-server.md)
+
+- [Use the Microsoft Purview portal](/purview/purview-portal)
+- [Data governance quick start](/purview/data-catalog-get-started)
+- [Microsoft Purview data governance tutorial](/purview/section2-scan-your-assets)
+- [Data catalog best practices](/purview/data-catalog-best-practices)
+- [Manage domains and collections](/purview/how-to-create-and-manage-domains-collections)
+- [Live view](/purview/live-view)
+- [Supported sources](/purview/microsoft-purview-connector-overview)
+- [Import Azure sources to Microsoft Purview at scale](/purview/tutorial-data-sources-readiness)
+- [Microsoft Purview data governance permissions](/purview/roles-permissions)
 
 ## Cutover from Azure Data Catalog to Microsoft Purview
 
 After the business has begun to use Microsoft Purview, cutover from Azure Data Catalog by deleting the Azure Data Catalog.  
 
 ## Next steps
-- Learn how [Microsoft Purview's data insights](../purview/concept-insights.md) can provide you with up-to-date information on your data landscape.
-- Learn how [Microsoft Purview integrations with Azure security products](../purview/how-to-integrate-with-azure-security-products.md) to bring even more security to your data landscape.
-- Discover how [sensitivity labels in Microsoft Purview](../purview/create-sensitivity-label.md) help detect and protect your sensitive information.
+
+- Learn how [Microsoft Purview's data estate health insights](/purview/data-estate-health) can provide you with up-to-date information on your data landscape.
+- Learn how [Microsoft Purview integrations with Azure security products](/purview/how-to-integrate-with-azure-security-products) to bring even more security to your data landscape.
+- Discover how [sensitivity labels in Microsoft Purview](/purview/create-sensitivity-label) help detect and protect your sensitive information.

articles/data-catalog/includes/catalog-to-purview-migration-flag.md

@@ -10,6 +10,6 @@ ms.author: whhender
 >
 > New Azure Data Catalog accounts can no longer be created.
 >
-> For data catalog features, please use the [Microsoft Purview](../../purview/overview.md) service, which offers unified data governance for your entire data estate.
+> For data catalog features, please use the [Microsoft Purview](/purview/free-version) service, which offers unified data governance for your entire data estate.
 >
 > If you're already using Azure Data Catalog, you'll need to [create a migration plan for your organization to move to Microsoft Purview](../data-catalog-migration-to-azure-purview.md) by May 15, 2024.

articles/storage/blobs/data-lake-storage-access-control.md

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: azure-data-lake-storage
 ms.topic: conceptual
-ms.date: 08/30/2023
+ms.date: 04/24/2024
 ms.author: normesta
 ms.reviewer: jamesbak
 ms.devlang: python
@@ -102,13 +102,31 @@ This table shows a column that represents each level of a fictitious directory h
 | Read Data.txt            |   `--X`   |   `--X`    |  `--X`      | `R--`          |
 | Append to Data.txt       |   `--X`   |   `--X`    |  `--X`      | `RW-`          |
 | Delete Data.txt          |   `--X`   |   `--X`    |  `-WX`      | `---`          |
+| Delete /Oregon/          |   `-WX`   |   `RWX`    |  `RWX`      | `RWX`          |
+| Delete /Oregon/Portland/ |   `--X`   |   `-WX`    |  `RWX`      | `RWX`          |
 | Create Data.txt          |   `--X`   |   `--X`    |  `-WX`      | `---`          |
 | List /                   |   `R-X`   |   `---`    |  `---`      | `---`          |
 | List /Oregon/           |   `--X`   |   `R-X`    |  `---`      | `---`          |
 | List /Oregon/Portland/  |   `--X`   |   `--X`    |  `R-X`      | `---`          |
 
+### Deleting files and directories
+
+As shown in the previous table, write permissions on the file are not required to delete it as long as the previous two conditions are true. However, to delete a directory and all of its contents, the parent directory must have Write + Execute permissions. The directory to be deleted, and every directory within it, requires Read + Write + Execute permissions.
+
+> [!NOTE]
+> The root directory "/" can never be deleted.
+
+### Which permissions are required to recursively delete a directory and its contents?
+
+- The caller has 'super-user' permissions,
+
+Or
+
+- The parent directory must have Write + Execute permissions.
+- The directory to be deleted, and every directory within it, requires Read + Write + Execute permissions.
+
 > [!NOTE]
-> Write permissions on the file are not required to delete it, so long as the previous two conditions are true.
+> You do not need Write permissions to delete files in directories. Also, the root directory "/" can never be deleted.
 
 ## Users and identities
 

articles/virtual-wan/media/monitor-virtual-wan-reference/hub-metrics.png

@@ -28,34 +28,7 @@ The following metric is available for virtual hub router within a virtual hub:
 
 > [!NOTE]
 > As of March 28, 2024, the backend functionality for the Routing Infrastructure Units and Spoke VM Utilization metrics are still rolling out. As a result, even if you see these metrics displayed in Portal, the actual values of these metrics might appear as 0. The backend functionality of these metrics is aimed to finish rolling out within the next several weeks, which will ensure the proper values are emitted. 
->
-
-#### PowerShell steps
-
-To query, use the following example PowerShell commands. The necessary fields are explained below the example.
-
-**Step 1:**
-
-```azurepowershell-interactive
-$MetricInformation = Get-AzMetric -ResourceId "/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/VirtualHubs/<VirtualHubName>" -MetricName "VirtualHubDataProcessed" -TimeGrain 00:05:00 -StartTime 2022-2-20T01:00:00Z -EndTime 2022-2-20T01:30:00Z -AggregationType Sum
-```
-
-**Step 2:**
-
-```azurepowershell-interactive
-$MetricInformation.Data
-```
-
-* **Resource ID** - Your virtual hub's Resource ID can be found on the Azure portal. Navigate to the virtual hub page within vWAN and select **JSON View** under Essentials.  
-
-* **Metric Name** - Refers to the name of the metric you're querying, which in this case is called 'VirtualHubDataProcessed'. This metric shows all the data that the virtual hub router has processed in the selected time period of the hub.  
-
-* **Time Grain** - Refers to the frequency at which you want to see the aggregation. In the current command, you'll see a selected aggregated unit per 5 mins. You can select – 5M/15M/30M/1H/6H/12H and 1D.
-
-* **Start Time and End Time** - This time is based on UTC. Ensure that you're entering UTC values when inputting these parameters. If these parameters aren't used, the past one hour's worth of data is shown by default.  
-
-* **Sum Aggregation Type** - The **sum** aggregation type shows you the total number of bytes that traversed the virtual hub router during a selected time period. For example, if you set the Time granularity to 5 minutes, each data point will correspond to the number of bytes sent in that 5 minute interval. To convert this to Gbps, you can divide this number by 37500000000. Based on the virtual hub's [capacity](hub-settings.md#capacity), the hub router can support between 3 Gbps and 50 Gbps. The **Max** and **Min** aggregation types aren't meaningful at this time. 
- 
+> 
 
 ### <a name="s2s-metrics"></a>Site-to-site VPN gateway metrics