Azure Information Protection Documentation Update for December 2017

Hi everybody


Welcome to the very first post on our new Azure Information Protection technical blog!  Going forward, this is where we will post a summary of monthly updates to our documentation.


My name is Carol Bailey and I'm a technical writer for Azure Information Protection.  My goal is to help you deploy your classification, labeling, and protection solutions by providing you with relevant and accurate online information. But I don't do this alone. I work with a terrific engineering team, a very knowledgeable support team, and a growing community of smart and helpful people like you.  As we move into a new year, I'm very proud of everything we've achieved so far and looking forward to 2018!


Reminders: Follow us on Twitter (Microsoft Mobility @MSFTMobility) and join our peer community at www.yammer.com/AskIPTeam. 

The Documentation for Azure Information Protection has been updated on the web and the latest content has a December 2017 (or later) date at the top of the article. 


Yes, we're in the holiday season and there are no documentation updates for new releases this month. However, we do have some important changes in support statements, a new section that highlights the new capabilities for Office 365 Message Encryption, and some clarifications for when you configure a label for protection.


We listen to your feedback and try to incorporate it whenever possible. Let me know if you have feedback about the documentation and I encourage you to head over to our Yammer site to see what others are discussing.  In the meantime, we wish you happy holidays and look forward to helping you deploy and manage Azure Information Protection in 2018.


What’s new in the documentation for Azure Information Protection, December 2017


What is Azure Information Protection?

- New section, Additional integration for email, that illustrates the new capabilities for Office 365 Message Encryption and how it can be used with an Azure Information Protection label.


BYOK pricing and restrictions

- Updated the recommendation and guidance to use a dedicated key vault and subscription. While we continue to recommend a separate key vault for your Azure Information Protection tenant key, it might make sense to share a subscription. Read the updated guidance for more information.


Configuring usage rights for Azure Rights Management

- For the Rights included in permissions levels section, updated footnote 3 to say that Export is also not included when you configure a label for permissions and choose Co-Author in the Azure portal.


How to configure the policy settings for Azure Information Protection

- Updated with the important note that the recently added policy setting in the Azure portal, Display the Information Protection bar in Office apps, is in preview and requires the preview version of the Azure Information Protection client. When this setting is off, it has no effect if you have a GA version of the Azure Information Protection client.


How to configure a label for Rights Management protection

- A couple of clarifications for when you configure a label for protection:

  • If you choose Enter details to manually specify a domain name, do not put domain names from social providers that support personal email accounts. For example, do not enter gmail.com, hotmail.com, or outlook.com. Instead, use the domain email  option to specify all uses in an organization.
  • The Select a predefined template option does not display if you are editing a label that previously used the Set permissions option.

Tasks that you used to do with the Azure classic portal

- Updated the introduction note for the new retirement date of the Azure classic portal (Jan 8), and added the important information that customers who have a subscription for Office 365 US Government (Government Community Cloud) currently cannot use the Azure portal and instead, must use PowerShell to manage their templates.


RMS client deployment notes

- Removed Windows Server 2008 and Windows Vista from the Which operating systems support the RMS client? section.  These operating systems are out of main stream support but as a concession to AD RMS customers, remained supported for AD RMS only.  That's no longer the case and client support for AD RMS is now the same as client support for Azure Information Protection.  The comparison table for Comparing Azure Information Protection and AD RMS is therefore also updated to show no difference for the minimum operating system.


Azure Information Protection client: Version release history and support policy

- Updated the support lifecycle statement to say that each general availability (GA) version of the Azure Information Protection client is supported for up to six months after the release of the subsequent GA version.


Admin Guide: Install the Azure Information Protection client for users

- A new prerequisite for Windows 7 computers, that's needed to classify and protect PDF files: Visual C++ Redistributable for Visual Studio 2015 (32-bit version).



Not applicable

Hi Carol, great update! I took the time to review some very good articles. Thanks for sharing...and Happy Holidays!!! :)


Hi Pepo - thanks for the feedback and happy holidays to you as well. Yes, these quieter days offer an ideal opportunity to catch up on some reading!


Hello Carol.

Just discovered this section and your post, being guided from the Yammer group. In collaboration with Microsoft team, I'd be using the AIP SDK for project delivery for a client. So this post is very helpful indeed. However, the developers guide link on the site here still gives a 404 error.


Is there any updates on the SDK also, since Nov 2017?


Hello, Pinaki


Thanks for the heads-up about the broken link - I've asked for this to be fixed.


I write the docs for admins, and they change on a fairly regular basis - in comparison to the developer docs that get updated when there's a new release of the SDKs.  I'll ask and see what I can find out for you.


Hello, again Pinaki

I've had it confirmed that there are no new SDK docs published since November.