Integrate existing M365 sensitivity labels with Apricot sensitivity tags
Would like to see integration between Apricot sensitivity tags and M365 sensitivity labels for sites & groups to allow more organizations to take full advantage of Apricot.
The current Apricot sensitivity tags only exist within Apricot and are not the same, nor do they integrate/sync or play well with M365 sensitivity labels, even if you set both to the same choices. This prevents organizations that need to use M365 sensitivity labels from using many features of Apricot since the sensitivity labels cannot be completely turned off and even if they could, Apricot does not even read the existing M365 labels so it limits use of Apricot for even basic visibility/reporting as far as sensitivity.
Some organizations need to use M365 sensitivity labels for consistency across Teams, Communication Sites and other workloads which are not covered by Apricot. The M365 labels are integrated into the site/team provisioning screens and can enforce that users must select the sensitivity at the time they create the team/site (instead of after the fact) and users are already trained and familiar with this process (same as it's predecessor, site classifications). Turning on sensitivity tags in Apricot will ask them a second time and can also cause potential issues/mismatches/incorrect settings. M365 labels also give users ability to be able to change the label if their needs change, without requiring IT intervention, which is not an option with Apricot sensitivity tags.
Rob Devereaux commented
Would love to see this capability added to the app/product. We are using Labels now and to have the ability to add it to provisioning templates as well as the Teams/Groups/Sites in the management app would make the tool more valuable.
Any plans in the roadmap for ShareGate to display/support/prevent conflict with M365 sensitivity labels versus classic AAD classification (legacy method)? M365 sensitivity labels still don't even display in the ShareGate UI for viewing. The Sharegate "sensitivity tags" are not the same thing and only exist within ShareGate and using these interferes with the native sensitivity labels which are policy driven. Similar feedback from others has been closed in error as launched due to confusion between sensitivity "tags" in sharegate and the actual m365 labels.