A unified data governance solution that helps manage, protect, and discover data across your organization
Hi Thiyagarajan Venkatasamy Ramamoorthy,
Thankyou for reaching microsoft Q&A!
What you’re seeing is expected behavior in Microsoft Purview. At present, subscription-level registration supports only a limited set of resource types for auto-discovery (such as Azure Storage, ADLS Gen1/Gen2, Azure SQL Database, Synapse Dedicated SQL, and Azure Data Explorer).
The broader list referenced in the documentation applies to individual resource-level registration, not subscription-level scans. This distinction can be unclear in the docs and is a known gap.
If you need to onboard additional resource types, the recommended approach is to register them individually in Purview.
Currently, there is no confirmed ETA or public roadmap update for expanding subscription-level support to additional resource types in Microsoft Purview. This limitation is by design at present.
For unsupported sources, the recommended approach is to continue using individual resource-level registration. You can also monitor the “What’s New” page for any future updates or enhancements
There isn’t a single document that explicitly states the limitation at the subscription level. However, Microsoft documentation clarifies that supported data sources apply primarily to individual resource-level registration, not subscription-level discovery.
You can refer here:
https://learn.microsoft.com/en-us/purview/data-map-data-sources
https://learn.microsoft.com/en-us/purview/data-map-scan-data-sources
Based on current documentation and behavior, subscription-level scanning supports only a limited set of resource types, while broader support is available when registering resources individually.
Please let us know if you’d like help with that, and we can guide you further.