Allow for ad-hoc permissions/rights ('Custom Permissions') in Outlook 2016 when composing messages, just like you can now do with Custom Permissions in Word/Excel/Powerpoint/Windows Explorer.

Analysis to detect/alert/respond to anomalous data access

Users may uninstall AIP client to attempt to circumvent AIP policies or just because they find it annoying. If the default label could be applied to any documents in SharePoint or OneDrive could be applied even if AIP client is not present, it would alleviate this potential security end-run.

Typically, end-users will not have admin rights to uninstall applications, but some times it is inescapable, esp in a small business.

Need the possibility to have Policy Tips for DLP rules in multiple languages when created in Office 365 Security & Compliance (as you can do in Exchange Online Admin). The policy tip should match the language you have in Office. Now it's mixed with the static text in the Policy Tip and the custom text you have entered in the rule

The DNF template has restrictions on copy, print and export. Some customers would like to modify this template for example to allow print.

Maybe also a possibility to add a company wide scope of users to this dynamic rule like the request in
https://msip.uservoice.com/forums/600097-azure-information-protection/suggestions/19602400-dynamic-protection-templates

And the possibility for the sending user to add more users to the permission list with BCC and without BCC

for example if Sara@contoso.com send DNF to Anna@contoso.com and Lisa@adatum.com but wants Anna@contoso.com to be co-owner.

if Sara@contoso.com send DNF to Lisa@adatum.com but wants her team to be co-owner.

Integrate the possibility to use image-files (such as: gif, png or jpg) for labeling as footer, header or watermark. The would be a great feature for some customers, so it is possible to support the corporate identity with specific colours and embedded graphics.

Different people have different needs for the default label depending on their day to day job.( working in finance : default = confidential ; working in external communication default = unrestricted)

We liked that users can choose the better appropriate default label . If not possible apply default label to scoped policy (so to users groups).

Would like enhanced multi-language support for visibility markers within Office 365 documents that use Azure Information Protection.

Currently visibility markers only display in one language

Create a template that helps assist organizations to identify personal details within content and files. Suggestions would be to look at telephone number/post code/IP address/e-mail address/gender/NHS number etc.
If there could be auditing that shows where this data resides when identified and give central IT a means to track it, that would provide high value in remaining compliant and avoiding fines.

Microsoft has recently invested in Machine Learning technologies that can detect patterns and correlate different pieces of content. These are currently used for e-Discovery and other capabilities. Leveraging these capabilities to automatically classify content by correlating it with other pieces of protected content would provide more automatic classification, reduce false positives and lighten the load on administrators so they don't have to constantly update classification rules.

To be more visible, have the option to show the colour on the buttons all the time.

Make Outlook's recall feature functional on OME or IRM-enabled emails.

Products like ZIX are able to deliver a notification when someone reads the encrypted message they were sent.
Our Customer has requested this feature to be added in O365

Windows 10 Integration with sensitivity labels to classify and protect documents coming out of specific applications or saved to specific locations - making files classified and protected at creation based on the content and the context they have been created with

We use DLP on email to assist in our PCI compliance. As an online payments provider, we often provide dummy credit card information to help our customers set up their APIs (typically 4444 3333 2222 1111). Unfortunately, despite this not being a valid card number, it triggers Microsoft's built in "Credit Card" definition resulting in 100s of false positives per week. We need to have this hard coded as an exception to the "Credit Card" definition, or, better yet, allow definitions to be customised and/or excluded from via. the Admin portal.

Update the encryption to 256 from 128 on all Office endpoints

If we add disclaimer and having email conversation means, disclaimer is adding multiple times in the bottom of the email. It should add bottom of each email.