Dec 05 2017
08:26 AM
- last edited on
May 24 2021
02:01 PM
by
TechCommunityAP
Dec 05 2017
08:26 AM
- last edited on
May 24 2021
02:01 PM
by
TechCommunityAP
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.
Dec 05 2017 11:42 AM
SolutionBest 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: https://support.office.com/en-us/article/Set-up-new-Office-365-Message-Encryption-capabilities-built...
Dec 08 2017 04:36 AM
Dec 05 2017 11:42 AM
SolutionBest 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: https://support.office.com/en-us/article/Set-up-new-Office-365-Message-Encryption-capabilities-built...