Azure Information Protection (AIP) is the new name, and new features for Azure Rights Management. Azure Information Protection allows a company to create a series of labels to apply to documents and to have those documents tags and labelled. For example a watermark or header is easy to set in the Azure Information Protection management blade in portal.azure.com.
In fact its so easy to turn on I did just that. The actual work and business consulting with Azure Information Protection is the why and business reasons for using it rather than the technical steps to enable it.
So once I enabled it and the client installed I found that I had a banner toolbar in Office applications as shown:
Clicking any of the labels will perform the default function of the product. These can be modified in the Azure Portal as shown:
The above two graphics show one example label (Confidential) that has had a sub label added (called NBConsult UK). The larger image above shows the details for this “NBConsult UK” label. In the properties blade for the label you can see I have turned on a template from RMS.
Once the changes are made and saved, you can publish the changes. Clients will pick up these changes on restarting the client application.
And then started my issues and the steps to troubleshoot this. First I got the following prompt twice:
And so I was finding my documents did not get the RMS based labels applied.
Reasons why this might be the case can be checked using the RMS tool in the Office application. So I tried to protect the document manually via File > Info tab:
This worked – I had the rights to use the template in the application – just AIP could not apply the template via the AIP tool.
To fix this I ran the Azure Information Protection (AIP) diagnostics tool. To get this click the AIP lock icon and choose Help and Feedback from the menu:
From this a popup appears:
And from this choose Run diagnostics:
Let the tool complete. I got the following errors before the application failed (crashed) and then did not complete again if left it again
To get around this issue, as the reset option to fix the AIP application in the diagnostics tool was not available due to the application crash, I followed the steps in http://social.technet.microsoft.com/wiki/contents/articles/19251.ad-rms-troubleshooting-reset-the-client-msipc.aspx to bootstrap the client manually. If the AIP diag client completes, fix the listed issue or choose Reset in the client.
Once I had deleted the files and related registry keys mentioned in the above website I could restart any Office application. The RMS certs, keys and settings where downloaded to the client again and the AIP client was able to protect a document where as before it was not: