Microsoft has rolled out the December update for Azure Information Protection to all its users. It contains all the improvements of previous builds and two new collaboration features.
AIC users can now share protected Office documents to a group of people, as well as a specific organization. The functionality uses corporate email addresses (eg. [email protected]) and means users don’t need individual names to share.
Azure Information Protection December Update Features
However, this build also brings several features you may have missed in the preview. Here’s a short summary of everything new:
- “Scoped Policies so you can make labels available to users based on group membership
- Scopes are optional, you don’t have to define a set or group for a policy. If not set, the policy has global scope for everyone in the tenant.
- Policies are ordered by administrators. This order defines which scopes are considered higher than others. Policies are combined into an effective policy, which is given to the client.
- A new, unified Windows client that combines the RMS Sharing app features into the Azure Information Protection client
- Scopes are optional, you don’t have to define a set or group for a policy. If not set, the policy has global scope for everyone in the tenant.
- Policies are ordered by administrators. This order defines which scopes are considered higher than others. Policies are combined into an effective policy, which is given to the client.
- An updated viewer for protected files, including protected PDFs downloaded from SharePoint
- Manual (right-click) labeling and protection for non-Office files
- Bulk classification and labeling for data at rest using PowerShell”
- Query for a files Label and Protection attributes
- Set a Label and/or Protection for documents stored locally or on file servers and network shares that are accessible through SMB/CIFS (e.g. \\server\finance\)”
These features should be available immediately for all users. Microsoft has extensive documentation on them, and you can download the new client here. For more information about the changes, visit the TechNet blog.