Occasional Contributor

Hi, I'm trying to find an answer to an issue that I am experiencing. If I send an Azure Information Protection email message to one of my clients, they receive an email with an attachment - 'message.rpmsg' and the subject indicating that they are the recipient of a protected message. If the client attempts to opens the file using an iOS device using Microsoft Outlook, the file cannot be opened or shared. If they attempt to open the attachment with the native email client, they get the option to share the file with the AIP Viewer app they've downloaded and once authenticated they're good to go (albeit a clunky process). If they client tries to open the attachment using their email app on their PC, say Outlook 2016, the file cannot be handled and the user is unable to open, even if they try and associate it with Outlook or the AIP viewer or the AIP client. I can't believe that such a great solution in principal, is so complex to use and I have therefore come to the conclusion that the solution has been implemented incorrectly. BTW, I am currently engaging with MS Support Services which, without sounding too disparaging, is tedious.


Can anyone put me on the right path?


BTW, I watched this video and it suggested that new functionality is coming to make this easier??


Many thanks.

3 Replies
best response confirmed by NEIL MARLOWE (Occasional Contributor)

Best thing you can do is to indeed configure what's shown in the video, the new V2 Office Message Encryption service. It makes it much easier on the receiving party to work with protected documents.


Here's the documentation:

Thanks Vasil, I'll give it a go.

Hi Vasil, That worked a treat and is now so much easier - thank you. I have a few questions around using the solution with external recipients if you can help? 1) If I send an email to (no attachments) with a protection policy applied that fred is not included in, I presume fred will not be able to open the email? 2) If I send an email to (with unprotected attachment) and use the Do Not Forward, I presume fred can open the email and the attached but presume the attachment is not protected and could be extracted / screen grabbed? 3) If I send an email to (with a mix of protected and unprotected attachments and use a separate protection policy for the email compared to the protected attachments, I guess the unprotected documents get the over-arching policy but do the originally protected attachments retain their previous policy, get a replacement policy or a composite policy? 4) If is not listed in a particular policy but I want to add him, does fred have to be added by an admin in the policy settings (i.e. add to Azure directory as contact) then applied to the policy before I can email fred (I know that this can be done using the AIP client using the Classify and Protect feature to add other recipients but I can't see how this can be applied using an email client or using a Word document if stored in Sharepoint)? Sorry - a lot of questions but these are the main scenarios that present themselves when implementing the solution. Your thoughts are gratefully received :-).