11
Azure security recommendations has a feature which classifies database table columns with sensitivity based on the field names (so it's not super accurate).
https://docs.microsoft.com/en-us/azure/azure-sql/database/data-discovery-and-classification-overview#discover-classify-columns

Dynamics has "Asset classification" on sensitive fields:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/gdpr/gdpr-asset-classification-values

Currently the two things aren't linked - so Dynamics knows that fields are sensitive, but when we export that a data to another Microsoft source which also has the need for the same classification, it doesn't take the flag with it, so we have to manually re-flag the fields again once they're out of Dynamics.

It would be lovely if the classification was set on the metadata automatically based on the property setting in Dynamics.
Category: Data Management
STATUS DETAILS
Needs Votes