Track & Revoke is back for the AIP Unifed Labeling Client

-

For those of you who have been asking for a Track & Revoke feature after migrating your labels to Sensitivity labels, Microsoft has some great news. When the feature was removed, Microsoft told us that it wasn't actually used by many, but still there seemed to be a lot of attention around this when it disappeared. 

So how do we get this working? Well, Microsoft says that once we have upgraded to version 2.9.109.0 any documents not yet registered for tracking are registered the next time they're opened on a machine with the AIP unified labeling client installed.  

 

When the documents are registered we can use PowerShell to track document access and revoke this access if needed. It was always a cool feature, and I for one missed this. We can also use the new Revoke access option on the Sensitivity menu. 

The 2.9.109.0 UL client is still in Public Preview, but if you want to get started right away, you can download it here: Download AIP Clients

The version number is not listed there, but select the UL client that is marked Preview and you should see the version number in the bottom left corner: 

  

 Is this something you have been waiting for? For more info read Microsoft's documentation here: Track & Revoke Admin

 

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