After reviewing the scenario, we can confirm that while the Salesforce source has been successfully scanned in Classic Microsoft Purview, automated data classification is currently not supported for Salesforce assets.
As per Microsoft Purview documentation, Purview supports extracting metadata from Salesforce (such as objects and fields), but it does not apply built-in or custom data classifications automatically during scans. This limitation is due to the semi-structured nature of the data and current feature constraints within the Classic Purview platform.
Additionally, when creating custom scan rule sets, Salesforce does not appear as a supported source type, which is expected behavior and aligns with current platform design.
Recommended Workarounds:
Manual Classification - After scanning, you may manually assign data classifications to Salesforce fields within the Purview Studio interface.
REST API or PowerShell - You can use the Purview REST APIs or PowerShell to apply classifications in bulk.
Unified Purview Experience - If automated classification is a critical requirement, we recommend evaluating the Microsoft Purview Unified Data Map, which continues to evolve and may offer broader source support in future updates.
For the latest updates, I recommend keeping an eye on the Azure updates page or the Microsoft Purview documentation: Azure Updates
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
For more details refer: https://learn.microsoft.com/en-us/purview/register-scan-salesforce
Hope this helps. Do let us know if you have any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.