Our technical writer, Carol Bailey, is letting you know what’s new and hot in the docs for February.
Dan (on behalf of the Information Protection team)
The Documentation for Azure Information Protection has been updated on the web and the latest content has a February 2017 (or later) date at the top of the article.
Wondered if you missed a doc update announcement for January? You didn’t. We had a lot of documentation pending for the February releases, and so we had very few docs republished in January. Because the February releases had a significant impact across the documentation, you’ll see a lot of articles with a February update date. For example, references to the Rights Management sharing application and the RMS Protection Tool throughout the documentation have been updated now that they are replaced by the Azure Information Protection client. However, documentation for this older application and tool will remain published as long as they remain in support.
Have feedback about the documentation for Azure Information Protection? We value customer feedback and try to incorporate it whenever possible. If you have feedback about our documentation, you can contact us by emailing AskIPTeam@Microsoft.com.
What’s new in the documentation for Azure Information Protection, February 2017
The following information lists the articles that have significant technical changes since the last update (December 2016).
What is Azure Information Protection?
– Updated for the latest changes, such as the new right-click options from Windows File Explorer, the latest “top 5 tips” video, and a link to the popular blog post Azure Information Protection: Ready, set, protect!
– Updated to remove many of the previously listed limitations from What can I do with the classification capabilities in Azure Information Protection? In addition, many of the previous FAQ entries on this page are now removed, in line with the service’s growing maturity.
– New entry in response to customer questions about when to use the “hold your own key” (HYOK) option: What’s the difference between BYOK and HYOK and when should I use them?
– Updated to replace all references to the Rights Management sharing application with the newly updated Azure Information Protection client, and to reflect UI changes in the Azure portal.
– Updated for a new section, Group membership caching, which explains how the Azure Rights Management service caches group membership for performance reasons. Two scenarios where you might need to take this into account is when you’re assigning usage rights to a group for a custom template, and when you use a group for the super user feature. A reference to group caching is therefore added to Create, configure, and publish a custom template and Configuring super users for Azure Rights Management and discovery services or data recovery.
– This article is also updated for the first tip about adding external users now that the latest PowerShell command supports external groups (currently, this was a limitation and external users only could be added). The help for the New-AadrmRightsDefinition cmdlet is also updated for this new support, and how to specify all users in another organization.
– Updated for the latest UI, with more prescriptive guidance when to use the HYOK (AD RMS) option in Hold your own key (HYOK) requirements and restrictions for AD RMS protection. That article also has a new additional limitation listed, for when users apply one type of protection to an email and then change their minds.
– Updated the How to interpret your Azure Rights Management usage logs section with information about operations that use the document tracking site, which includes clarifying which fields are blank for a revoke access action.
– Updated to clarify whether the listed admin tasks have an equivalent in the UI. This was a customer request that was also incorporated into each cmdlet help in the module.
– Updated the Windows registry settings table for the data collection value (DiagnosticState), which is supported with the newly released client (1.03102.0221) and corresponding RMS SDK 2.1. For more information about this latest SDK release, see the release notes and download it from the Microsoft Download Center.
– New landing page to hold resource links for the release history, admin guide, user guide, and relevant FAQs for the Azure Information Protection client.
– Updated for the 184.108.40.206 release in February.
– New guide to help administrators deploy and manage the Azure Information Protection client on an enterprise network. Because the target audience for this information is IT Professionals, it contains more detailed information than in the Azure Information Protection client user guide. For example, installation includes the different options that can be run from the command line and where to locate the setup log, how to configure the installation for users if they have Office 2010, the different file types supported and which ones are automatically skipped, and how to run PowerShell commands for the client.
– Updated end user instructions to support the main scenarios of install, classify and protect, track and revoke, and open protected files. In addition:
- For users who have an Office 365 subscription only to protect data and cannot label it: Protection-only mode for the Azure Information Protection client
- For users who are used to using the Rights Management sharing application: Tasks that you used to do with the RMS sharing application
– This landing page for the Rights Sharing application, the admin guide, and the user guide, have all been updated to include the end of support notification,
– New online help for the PowerShell cmdlets that install with the Azure Information Protection client. Before you use these cmdlets, make sure that you read and follow the prerequisites in the Azure Information Protection client admin guide. These prerequisites were previously documented in “about” files that shipped with the module for the RMS Protection Tool, but are now documented in the admin guide so that they can be more easily updated if needed.