How to work with a mix of AIP P1 and P2 licenses

-
Just to get this out of the way: Yes, there are several ways to license AIP. You can get it through AIP license (Plan 1(P1)/Plan 2(P2)), Enterprise Mobility + Security license (E3/E5), the rather new Information and Compliance policy and also some Office 365 licenses. Just think of my references to P2 as the “upgraded basic” (P2/E5 etc.)



Many businesses have users with different needs and different types of licenses. When it comes to AIP, there are quite a few differences in functionality between the P1 and P2 licenses, and they are also quite differently priced. You may want to give a subset of your users the P2 license and worry about how you will do that without breaking the licensing terms.

Well, this is actually quite easy. You need to make sure that your global policy does not contain any options that would require the P2 license and create a scoped policy where you can add P2 functionality. For more information on how to create a scoped policy you can read my previous post on this: Creating a scoped policy



Comments

Post a Comment

Popular posts from this blog

Do not Forward and the protection of attachments

-
Image
Maybe I am the only one who has misunderstood this, but if not, this may be useful for you. I've been wrong about this for a while, and since it is not a feature we have used, I didn't really look into it until today. I always thought that using Do not Forward in a label would make sure attachments where given the same DNF rights.  Unfortunately I was shown the error of my ways by one of my customers today, when I answered (with some confidence) that, yes: Attachments get the same protection. He then replied that he was able to do all kinds of things with the attachment, and I started to look into it more closely. Microsoft has many great articles about protecting information, and this article is no exception. I guess you just have to read it carefully. They say:  “When the Do Not Forward option is applied to an email, the email is encrypted and recipients must be authenticated. Then, the recipients cannot forward it, print it, or copy from it . For example, in the Outlook cli
Read more

Using Do not Forward or Encrypt Only as the results of a Sensitivity Label

-
Image
Do not Forward and Encrypt Only can be found in Outlook by default for all who uses Office 365 E3 or equivalent/higher. And as many know, they can also be used in a Sensitivity label. But what are the consequenses of using these, instead of creating our own encryption settings within the label? This is what we will be looking at today.  As many know, we can use these two in Outlook, as long as we have the proper license. They are well hidden away under Options, and can look a little like this:    EO and DNF in Outlook.  I've covered these in earlier blogposts , but lets just quickly go through them again here: " Encrypt/Encrypt-Only " option makes sure the email is encrypted and recipients must be authenticated, but then they have all usage rights except Save As, Export and Full Control (Basically means no restriction except that they cannot remove the protection). When the Do Not Forward option is applied to an email, the email is encrypted and recipients must be au
Read more