Azure Information Protection
-
Enable co-authoring of Protected Documents
Currently, documents that are labelled can be co-authored in Office, but any document that is encrypted can only be opened by one person at a time. This prevents most of the business scenarios folks use today with two three or more folks editing a document at the same time. Instead - it forces businesses to email copies of a document around after setting AIP policies to allow folks to all edit it. A huge blocker for most of our customers.
65 votes -
Add PowerShell and/or Graph API support for AIP configuration
Add PowerShell (and/or Graph API) support for configuring AIP Policies and Labels. Configuring even 5-10 policies in the GUI is laborious and doesn't scale well to multiple tiers/environments.
18 votesWith the integration between AIP and Office Information Protection, Office 365 Management PowerShell will include the ability to manage labels for AIP.
This is expected to come out during the GA release of said integration before the middle of this year. -
Enable AIP in Office Mobile Clients
Integrate AIP functions into Office on iOS and Android
136 votes -
Office Web Apps Support AIP Policies
Surface the AIP policies within Office Web Apps
127 votes -
AIP Client for MacOS (for non-Office file formats)
Provide a Mac AIP client that is consistent with the current Windows AIP client, and is able to classify and protect documents from the desktop. For the AIP toolbar in Mac Office, use https://msip.uservoice.com/forums/600097-azure-information-protection/suggestions/19602337-integrate-aip-natively-into-office-for-mac.
95 votes -
Enable SPO to index protected files
Enable protected content to be optionally indexed and surfaced in results and engines like Delve
42 votes -
Administrative actions (SuperUser) are logged
All actions taken by administrators are logged for auditing and reporting purposes
31 votes
- Don't see your idea?