Showing posts from September, 2018

Microsoft Information Protection (MIP). Yet another abbreviation you need to know about?

If you are following the news from Ignite, you might have heard the abbreviation MIP. Forget AIP. The big news is MIP someone said to me. Sounds a little dramatic right? Is AIP really dead? Well, to calm down everyone who has invested time and effort into AIP: MIP is not taking over for AIP, it is rather a new umbrella that includes AIP and a lot of other security solutions. It can be seen as a new step in the evolution of Microsoft’s overall information protection strategy.

Creating a scoped Policy and linking it to a label.

In my previous posts I have mentioned scoped policies a few times. The policy that is included from the start and that will be available for everyone default is the Global Policy . Sometimes that will be all you need, but there are situations where protecting content for groups of people, like the HR department for instance, will be required.

The AIP Scanner, licensing, usage and more.

Previously I have promised that I would write a post about the AIP scanner, how it is installed and more, but the good installation guides from Microsoft rendered this kind of unnecessary.

Some updates of the previous blogposts

Trying to keep up with cloud solutions is not at all like back in the day when we got a new server version every few years. Updates are happening all the time, and some of the things I wrote earlier has now been changed so much that I will say something about the updates here. 

Error messages when applying labels with the Azure Information Protection client.

This post describes some of the issues I have had/seen with the AIP Client and Office. Usually everything works well, and you can just start using the labels, but when things go wrong, it is not alway easy to see why.