@Daniel Russell I hope you are doing well,
Purview scans sometimes hang when:
- The size of the data exceeds internal estimation limits
- There are nested or malformed file paths
- Service is under load or experiencing backend issues (which might not show as an error)
Try:
Splitting the scan into smaller, more focused jobs (e.g., scanning folders individually).
Temporarily disabling classification and just running a scan, to isolate the bottleneck.
- Setting scanLevel=File instead of File+Classification.
5. Restart Scan via PowerShell or CLI
If the UI retry fails:
# Azure CLI Example
az purview scan run --name myScanName --data-source-name myDataSource --resource-group myRG --account-name myPurviewAccount
😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!