Skip to content

Commit ceabdfc

Browse files
authored
Adding troubleshooting notes
1 parent 4551a0c commit ceabdfc

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,13 @@ In Microsoft Purview, you can register and scan various types of data sources, a
3131

3232
1. You can come back to **Scan Status** page by following the bread crumbs on the top left corner of the run history page.
3333

34+
## Scans no longer run
35+
36+
If your Microsoft Purview scan used to successfuly run, but are now failing, check these things:
37+
1. Have credentials to your resource changed or been rotated? If so, you'll need to update your scan to have the correct credentials.
38+
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.
39+
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.
40+
3441
## Next steps
3542

3643
* [Microsoft Purview supported data sources and file types](azure-purview-connector-overview.md)

0 commit comments

Comments
 (0)