I have a customer looking to start a testing AIP. Currently they have Office 365 E3 licenses for their users and thus will be using Azure Information Protection for Office 365.
I'd like to know if it's best to start with Unified labelling and the Azure Information Protection unified labelling client or if we need to stick to using the AIP portal and the standard AIP client.
Also, this link states that Azure Information Protection for Office 365 supports protection but not classification and labelling. I was under the impression that a label had to be applied to a document before protection can be applied. Am I misunderstanding this?
It's really difficult to see what is possible in the documentation when just using Azure Information Protection for Office 365.
@Dan Snape Hi. The Office 365 E3 licenses only cover built-in protection and built-in labeling in Office clients, not the AIP plugin. Since built-in labeling hasn't shipped in Office for Windows yet (expected for later this Summer) this mean that on Windows clients this license only allows you to apply protection.
Which brings me to your second question: protection functionality has been in Office for over a decade. You can select the File/Info/Protect menu to apply either a rights policy template or a manual protection policy (or Do Not Forward, for emails) directly from Office. In addition to this being a significantly less elegant experience than applying labels which in turn apply protection, this of course misses the other benefits of labeling: content markings, automatic classifications and recommendations, default labels, etc. But in the absence of labeling, protection is still an effective method to reduce data leakage and exposure.
Once Office ships a naive labeling experience on Windows, these users will be able to use labels instead (they can already do that on Mac, iOS and Android).
If the customer also acquires AIP (P1 or P2 licenses, included in EMS E3 and E5 respectively) then they can indeed use the AIP plugin to apply labels (both classic and Unified Labeling).
Setting licensing aside, in most cases we recommend clients deploying now to use the classic client, since the Unified Labeling client still lacks some functionality available in the classic client. But next month we will ship a new version of the Unified Labeling client which should close this gap and at that point we will recommend most customers to start using the Unified Labeling client (and to those that have already deployed, to upgrade).