Terminology for Azure Information Protection
Confused by a word, phrase, or acronym that's related to Microsoft Azure Information Protection? Find the definition here for terms and abbreviations that are either specific to Azure Information Protection or have a specific meaning when used in the context of this service.
Word, phrase, or acronym
|AADRM||The name of the first PowerShell module for the protection service (Azure Rights Management), which was derived from the unofficial abbreviation for Azure Rights Management when it was previously named (Windows) Azure Active Directory Rights Management. This PowerShell module is now replaced with the AIPService module.|
|activate||To enable the protection service (Azure Rights Management) so that an organization can protect their documents and email. This action also enables IRM features in Exchange Online and SharePoint Online.|
|Active Directory Rights Management Services||Frequently abbreviated to AD RMS.
A Windows Server role that provides rights management protection by using encryption and policy to help secure documents, files, and email.
|AD RMS||See Active Directory Rights Management Services.|
|AIPService||The current name of the PowerShell module for the protection service, which replaces with the older, AADRM module.|
|AzureInformationProtection||The name of the PowerShell module for the Azure Information Protection client (classic) and the Azure Information Protection unified labeling client.|
|Azure Information Protection||A cloud-based service that uses labels to classify and protect documents and emails. Azure Rights Management provides the protection by using encryption, identity, and authorization policies.|
|Azure Information Protection client (classic)||Sometimes abbreviated to classic client.
The original client side of Azure Information Protection that lets users, administrators, and services use the labels and settings from your Azure Information Protection policy. Now being replaced with the Azure Information Protection unified labeling client.
|Azure Information Protection label||An item that always applies a classification value to documents and emails, and can also protect them. When a label is applied, the label information is stored in the metadata for applications and services to read and optionally, act on it.|
|Azure Information Protection policy||Administrator-defined configuration for clients and services that use Azure Information Protection labels and policy settings.|
|Azure Information Protection scanner||A service that runs on Windows Server and lets you discover, classify, and protect documents on local folders, network shares, and SharePoint Server sites and libraries.|
|Azure Information Protection unified labeling client||Sometimes abbreviated to unified labeling client.
The client for Windows computers that lets users, administrators, and services use the sensitivity labels and label policy settings from the Office 365 Security & Compliance Center, the Microsoft 365 security center, and the Microsoft 365 compliance center. Replaces the Azure Information Protection client (classic).
|Azure RMS||See Azure Rights Management.|
|Azure Information Protection viewer||An app that runs on Windows computers and mobile devices, to display protected files.|
|Azure Rights Management||Frequently abbreviated to Azure RMS.
An Azure service used by Azure Information Protection that uses encryption and policy to help secure documents, files, and email. Also known as Azure Rights Management service. Previous names have included:
- Windows Azure Active Directory Rights Management: Frequently abbreviated to Windows Azure AD Rights Management Service.
- RMS Online: The original, proposed name, which you might sometimes see in error messages and log file entries.
|default template||A protection template that is automatically created for you when you obtain a subscription for Azure Information Protection, so that you can immediately start protecting documents and emails that contain sensitive information.|
|BYOK||See bring your own key.|
|bring your own key||Frequently abbreviated to BYOK.
A configuration and topology option chosen by an organization that wants to generate and manage their own tenant key for Azure Information Protection.
|built-in labeling||An Office 365 app or service capability to support sensitivity labels without the requirement to install an additional labeling client. Also known as native labeling.|
|content key||A unique key that is created by RMS-enlightened applications for each document or email that is protected by using Rights Management and that helps to limit the risk of information disclosure.|
|consume||In the context of protection only: To open a document or email to read or use it when that content has been protected by a rights management service. For a document, consuming includes editing and adding new content to a protected document. For an email message, consuming includes replying to a protected message.
In the context of labeling (with or without protection): To read and potentially act on the label information stored in the metadata of files and emails.
|deactivate||To disable the Rights Management service so that the organization can no longer use Azure Information Protection.|
|departmental template||A protection template that you create and that is configured to be visible for selected users rather than all users in your organization. Also known as a scoped template.|
|enlightened applications||Applications that natively support Rights Management, which includes Office applications, such as Word and Excel. Independent software vendors (ISVs) and developers can also write applications that natively support Rights Management.|
|enterprise rights management||An industry-standard, generic term that is often used to describe products and solutions that help organizations protect sensitive or valuable information by using a combination of encryption and policy authorization tools. Azure Information Protection is an example of an enterprise rights management (ERM) solution.|
|ERM||See enterprise rights management.|
|generic protection||A level of protection that encrypts any file type and prevents unauthorized people from opening the file. After the file is opened, the file is now unencrypted and usable in an application that doesn’t natively support Rights Management.|
|HYOK||See hold your own key.|
|hold your own key||Frequently abbreviated to HYOK.
A configuration and topology option for an organization that wants to generate and store their own key on-premises, typically for regulatory or compliance reasons.
|key object||In the context of the tenant key, an entity that contains metadata that is required by the Azure Rights Management service for cryptographic operations.|
|label||See Azure Information Protection label.|
|information protection||Sometimes abbreviated to IP.
An industry-standard, generic term that refers to protecting data and files from unauthorized access, even after the data and files leave the organizational boundaries by using email or document sharing. Microsoft Azure Information Protection is an example of an information protection (IP) solution.
|Information Rights Management||Frequently abbreviated to IRM.
A term used in conjunction with Office services, such as Exchange Server, Word, and SharePoint Online, to describe the ability to support the Microsoft Rights Management services.
|IRM||See Information Rights Management.|
|Office Message Encryption||Frequently abbreviated to OME.
The new Office 365 Message Encryption capabilities have native integration with the Azure Rights Management service to provide the same email protection for internal and external users, automatic refresh of templates, and support for the bring your own key (BYOK) scenario. The previous OME implementation was designed for external recipients only, required a mail flow rule, and did not support BYOK.
|Microsoft Information Protection||Sometimes abbreviated to MIP.
A framework for products and integrated capabilities that use the same labeling store ("unified labels") and help you protect your organization's sensitive information.
|MIP||See Microsoft Information Protection|
|MSDRM||Sometimes seen as references for the RMS client 1.0, which is replaced with the newer client, MSIPC. This older client supports applications that are developed with the RMS SDK 1.0 and supports Office 2010 and Office 2007, Exchange 2010 and Exchange 2013, and SharePoint 2010 and SharePoint 2007.|
|MSIPC||Sometimes seen as references for the RMS client 2.0, which replaced the older RMS client, MSDRM. This later client supports applications that are developed with the RMS SDK 2.0 and supports Office 365 ProPlus, Office 2019, Office 2016, Office 2013, SharePoint 2013, and the Azure Information Protection client.|
|native protection||A level of protection available in all enlightened applications that prevents unauthorized people from opening a file and that can also enforce more stringent policies, such as read-only, and do not print. In addition, this protection stays with the file, even when the file is forwarded to other people or saved in a public location that others can access.|
|.pfile||The file name extension that is appended to all files that a rights management service generically protects.|
|permissions level||A logical grouping of usage rights that make it easier for end-users and administrators to choose configuration options that are role-based. For example, Reviewer and Co-Author.|
|protect||Apply rights management controls to files or email messages by using encryption, identity, and access control policies to help secure your data.|
|protection template||Also known as a rights policy template, Rights Management template, and RMS template.
A group of protection settings that are managed by an administrator and that include the defined usage rights for authorized users, and access controls for expiry and offline access.
|publish||To protect a file in order to safeguard it from unauthorized access and use. Also used as a term in conjunction with protection templates and the Azure Information Protection policy, to make these items available for use by clients and services.|
|Rights Management connector||An outbound proxy relay that you can deploy for on-premises services such as Exchange Server and SharePoint, to protect data by using the Azure Rights Management service.|
|Rights Management issuer||The account that protected a document or email.|
|Rights Management owner||The account that retains full control of a protected document or email by being automatically granted the Rights Management Full Control usage right and is exempt from any expiry date or offline setting.|
|Rights Management services||The generic term that applies to both the cloud version of Rights Management (Azure Rights Management) and the on-premises version of Rights Management (AD RMS).|
|Rights Management sharing application||Now replaced by the Azure Information Protection client.|
|RMS||See Rights Management services.|
|RMS connector||See Rights Management connector.|
|RMS for individuals||A free subscription for a user to use Rights Management when their organization does not have a subscription to Office 365 or Azure Active Directory.|
|RMS sharing app||See Rights Management sharing application.|
|RMS template||See protection template.|
|protection-only mode||An operational mode for the Azure Information Protection client when there is no Azure Information Protection policy to apply labels. In this mode, classification labels are not displayed but users can still apply Rights Management protection.|
|scanner||See Azure Information Protection scanner.|
|super user||A group of highly trusted administrators who can decrypt and access files that the organization has protected by using a rights management service. Typically, this level of access is required for legal eDiscovery and by auditing teams.|
|tenant key||Also known as the server licensor certificate (SLC) key.
The key that is unique to an organization and ultimately secures all Rights Management cryptographic functions that chain to this tenant key.
|unified label||Also known as unified sensitivity label.
A label that can be applied by apps, clients, and services that support the Microsoft Information Protection framework, to apply classification and optionally, protection. In Office apps and services, unified labels are implemented as sensitivity labels.
|unprotect||Remove protection controls from files or email messages, which used encryption, identity, usage rights, and access control policies to help secure your data.|
|use license||A per-document certificate that is granted to a user who opens a file or email message that has been protected by a rights management service. This certificate contains that user’s rights for the file or email message and the encryption key that was used to encrypt the content, as well as additional access restrictions defined in the document’s policy.|