Aug 20 2019
- last edited on
May 24 2021
We are deploying AIP with Unified Labels (UL). From what I read from an old post (few months ago), AIP scanner still only works with classic labels and not UL.
Is this the case? If it is, is there an ETA?
Is there any other alternative to automatically classify on-premises files that are on network shares?
Aug 24 2019 03:46 AM
@Pål Winther Thank you Pal for your quick reply on that! In fact, I also found that information in the latest blog from the AIP Blog where it also states that there are other nice features that are coming soon like the support for the following:
For people that wants to know more about that, you can read the blog post here:
Sep 10 2019 06:04 AM
@Chuck99 I have the same query and the article
states that this isn't a blocker 'As of today (August 2019), the Azure Information Protection scanner supports only labels from Azure Information Protection blade but this is not a blocker as the Azure Information Protection label metadata is identical to unified labels.'
Can anyone advise, does this mean we can scan on-prem sources using current AIP scanner which doesn't support UL? Presumably once its integrated, we can then migrate AIP labels to UL and carry on seamlessly or are there some pitfalls or alternative approach to consider?
Sep 11 2019 03:19 AM
@Chris JohnstonAs long as you have activated unified labeling your label configuration will be "synchronized" to the classic portal and can be published there as well. This means that needing to use the classic portal/classic client should not be a blocker for going for UL with sensitivity labels.