Merge pull request #214121 from whhender/patch-40

Boosting policy messaging

Author: prmerger-automator[bot]

articles/purview/concept-best-practices-scanning.md

@@ -18,6 +18,9 @@ Running a *scan* invokes the process to ingest metadata from the registered data
 
 The curation process applies automated classification labels on the schema attributes based on the scan rule set configured. Sensitivity labels are applied if your Microsoft Purview account is connected to the Microsoft Purview compliance portal.
 
+> [!IMPORTANT]
+> If you have any [Azure Policies](../governance/policy/overview.md) preventing **updates to Storage accounts**, this will cause errors for Microsoft Purview's scanning process. Follow the [Microsoft Purview exception tag guide](create-azure-purview-portal-faq.md) to create an exception for Microsoft Purview accounts. 
+
 ## Why do you need best practices to manage data sources?
 
 Best practices enable you to:

articles/purview/create-microsoft-purview-portal-faq.md

@@ -5,14 +5,16 @@ author: nayenama
 ms.author: nayenama
 ms.service: purview
 ms.topic: how-to
-ms.date: 08/26/2021
+ms.date: 10/10/2022
 ---
 
 # Create an exception to deploy Microsoft Purview
 
-Many subscriptions have [Azure Policies](../governance/policy/overview.md) in place that restrict the creation of some resources. This is to maintain subscription security and cleanliness. However, Microsoft Purview accounts deploy two other Azure resources when they're created: an Azure Storage account, and optionally an Event Hubs namespace. When you [create Microsoft Purview Account](create-catalog-portal.md), these resources will be deployed. They'll be managed by Azure, so you don't need to maintain them, but you'll need to deploy them. Existing policies may block this deployment, and you may receive an error when attempting to create a Microsoft Purview account.
+Many subscriptions have [Azure Policies](../governance/policy/overview.md) in place that restrict the creation or update of some resources. This is to maintain subscription security and cleanliness. However, Microsoft Purview accounts deploy two other Azure resources when they're created: an Azure Storage account, and optionally an Event Hubs namespace. When you [create Microsoft Purview Account](create-catalog-portal.md), these resources will be deployed. They'll be managed by Azure, so you don't need to maintain them, but you'll need to deploy them. Existing policies may block this deployment, and you may receive an error when attempting to create a Microsoft Purview account.
 
-To maintain your policies in your subscription, but still allow the creation of these managed resources, you can create an exception.
+Microsoft Purview also regularly updates its Azure Storage account after creation, so any policies blocking updates to this storage account will cause errors during scanning.
+
+To maintain your policies in your subscription, but still allow the creation and updates to these managed resources, you can create an exception.
 
 ## Create an Azure policy exception for Microsoft Purview
 

articles/purview/create-microsoft-purview-portal.md

@@ -3,7 +3,7 @@ title: 'Quickstart: Create a Microsoft Purview (formerly Azure Purview) account'
 description: This Quickstart describes how to create a Microsoft Purview (formerly Azure Purview) account and configure permissions to begin using it.
 author: nayenama
 ms.author: nayenama
-ms.date: 06/20/2022
+ms.date: 10/11/2022
 ms.topic: quickstart
 ms.service: purview
 ms.custom: mode-ui
@@ -20,6 +20,9 @@ For more information about the governance capabilities of Microsoft Purview, for
 
 ## Create an account
 
+> [!IMPORTANT]
+> If you have any [Azure Policies](../governance/policy/overview.md) preventing creation of **Storage accounts** or **Event Hub namespaces**, or preventing **updates to Storage accounts** first follow the [Microsoft Purview exception tag guide](create-azure-purview-portal-faq.md) to create an exception for Microsoft Purview accounts. Otherwise you will not be able to deploy Microsoft Purview.
+
 1. Search for **Microsoft Purview** in the [Azure portal](https://portal.azure.com).
 
     :::image type="content" source="media/create-catalog-portal/purview-accounts-page.png" alt-text="Screenshot showing the purview accounts page in the Azure portal":::

articles/purview/how-to-monitor-scan-runs.md

@@ -31,6 +31,13 @@ In Microsoft Purview, you can register and scan various types of data sources, a
 
 1. You can come back to **Scan Status** page by following the bread crumbs on the top left corner of the run history page.
 
+## Scans no longer run
+
+If your Microsoft Purview scan used to successfully run, but are now failing, check these things:
+1. Have credentials to your resource changed or been rotated? If so, you'll need to update your scan to have the correct credentials.
+1. Is an [Azure Policy](../governance/policy/overview.md) preventing **updates to Storage accounts**? If so follow the [Microsoft Purview exception tag guide](create-azure-purview-portal-faq.md) to create an exception for Microsoft Purview accounts.
+1. Are you using a self-hosted integration runtime? Check that it's up to date with the latest software and that it's connected to your network.
+
 ## Next steps
 
 * [Microsoft Purview supported data sources and file types](azure-purview-connector-overview.md)

articles/purview/troubleshoot-connections.md

@@ -81,6 +81,13 @@ To verify this, do the following steps:
 
 If you don't see your Microsoft Purview managed identity listed, then follow the steps in [Create and manage credentials for scans](manage-credentials.md) to add it.
 
+## Scans no longer run
+
+If your Microsoft Purview scan used to successfully run, but are now failing, check these things:
+1. Have credentials to your resource changed or been rotated? If so, you'll need to update your scan to have the correct credentials.
+1. Is an [Azure Policy](../governance/policy/overview.md) preventing **updates to Storage accounts**? If so follow the [Microsoft Purview exception tag guide](create-azure-purview-portal-faq.md) to create an exception for Microsoft Purview accounts.
+1. Are you using a self-hosted integration runtime? Check that it's up to date with the latest software and that it's connected to your network.
+
 ## Next steps
 
 - [Browse the Microsoft Purview Data catalog](how-to-browse-catalog.md)