Applies to: Azure Rights Management, Office 365
After you have deployed and configured Azure Rights Management (Azure RMS) for your organization, provide help and guidance for users, administrators, and your help desk:
Let users know how and when to protect documents and emails that contain sensitive information. Whenever possible, provide this information for their existing work flows so that they can incorporate the additional steps to an already-familiar process rather than introducing completely new processes . Be sure to let them know the benefits (and the risks) that are specific to your business, as well as providing guidance for when they should protect files and emails. If you have configured custom templates, provide instructions about which one to select if the template name and description is not sufficient for them to choose the correct one.
Some applications automatically apply information protection, by using policies and settings that administrators configure. For these applications, you might need to provide instructions for other administrators who manage these applications and services. For more information, see How applications support Azure Rights Management and Configuring applications for Azure Rights Management.
Help desk information:
One of the most useful tools for the help desk is the RMS Analyzer. Help desk operators can run it with the Azure RMS administrator option, and they can ask users to run it with the Azure RMS user option. This tool can not only help identify problems, but also fix problems that it finds, and if still not fixed, record trace logs.
If there are legitimate requests to have full rights access to protected documents, for example a request by the legal department or a manager after an employee has left the organization, make sure the help desk has processes to request this by using the Azure RMS super user feature.
In addition, these are some of the typical problems that users might report:
Sign in help:
Users might be prompted for credentials when Azure RMS needs to authenticate a user and cannot use cached credentials. This will be the user’s work or school account and password that is associated with your Office 365 tenant or Azure Active Directory tenant. It will not be a Microsoft account (formerly Microsoft Live ID) or their personal email account, because these are not currently supported by Azure RMS. Provide users and your help desk with instructions about which account to use when users are prompted for credentials when they use these applications with Azure RMS.
Problems protecting or consuming content:
Make sure that users have the appropriate instructions for the applications that they use, and are using applications and devices that are supported by Azure RMS. For more information about supported applications and devices, see Requirements for Azure Rights Management.
If users see an error when trying to protect or consume content, ask them to run the RMS Analyzer as an Azure RMS user.
If users report that they can open protected content but don't have the rights that they need, ask them to run the RMS Analyzer as an Azure RMS user and download and view the templates. This will confirm that they have successfully downloaded the templates and what rights the templates provide. The problem might be that the user is not in the correct group that's configured for the template, or that the template needs reconfiguring for the user.
Use the following sections for application-specific information to help users protect sensitive documents and emails.
Using information protection with the Rights Management sharing application
The Rights Management (RMS) sharing application is required for users to protect and consume protected content if they use Office 2010, but also recommended for all computers and mobile devices that support Azure RMS.
In addition to making it easier for users to protect important documents, the RMS sharing application lets users track the documents that they have protected, and if necessary, revoke access to them.
For instructions to use this application for Windows computers, see the Rights Management sharing application user guide.
For mobile devices, see the FAQ for Microsoft Rights Management Sharing Application for Mobile Platforms.
For a high-level example scenario with screenshots, see Users safely share attachments with mobile users.
Using information protection with Office 365, Office 2016, or Office 2013
If you are using Azure RMS and have not installed the Rights Management sharing application, users will not see the Share Protected button on the ribbon or Protect in-place from File Explorer that makes it easier for them to protect files. For these users, they must follow instructions similar to these.
To find application-specific help and instructions for using information protection with these applications, search for IRM and the application name and version.
To protect a document in Word 2013
Within Microsoft Word, create a new document.
From the File menu, click Info, click Protect Document, click Restrict Access, and then choose a template to quickly apply the appropriate usage rights, or select Restrict Access and select the usage rights yourself.
If this is the first time that you have used Rights Management, you will contact the Azure Rights Management service and will be prompted for credentials to configure the Office IRM client.
Save the document.
When others open the document, they are first authenticated. If they are not authorized to open the document, the document does not open. If they are authorized to open the document, it opens with the restricted usage rights that were specified for that user. For example, a usage right of View-only does not allow the user to edit or save the document, even if it is first copied to another location. The usage rights are displayed at the top of the document by using a restriction banner. The banner might display the permissions that are applied to the document, or it might provide a link to display them.
To protect an email message using Outlook 2013 and Exchange Online
Within Outlook, create a new mail message addressed to a recipient within your organization.
From the OPTIONS tab, click Permission, and then select an option. For example: Do Not Forward, <Company Name> - Confidential or <Company Name> - Confidential View Only.
Send the message.
Similarly to viewing a protected document, when the recipients receive the email message, they are first authenticated. If they are authorized to see the email message, it opens with the restricted usage rights that were specified for that user. For example, if you selected Do Not Forward, the Forward button on the ribbon is not available.
To protect an email message using the Outlook Web App
Within the Outlook Web App, create a new mail message addressed to a recipient within your organization.
Click …, click set permission, and then select an option. For example: Do Not Forward, Do Not Reply All, <Company Name> - Confidential or <Company Name> - Confidential View Only.
Send the message.
Similarly to viewing a protected document, when the recipients receive the email message, they are first authenticated. If they are authorized to see the email message, it opens with the restricted usage rights that were specified for that user. For example, if you selected Do Not Reply All, the REPLY ALL option in the message window is not available.