Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,568 questions
Recipients receiving an error when attempting to open an encrypted emails.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 82%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Steve Mauer
0
Reputation points
We have recently started applying encryption to emails using sensitivity labels created in Purview. We have multiple users who started reporting that recipients can not open any of their encrypted emails. The error received is "Sorry, we can't display your message right now. Something went wrong and your encrypted message couldn't be opened. Please try again by following the instructions in the original email message in 5 minutes." Examining the URL from these emails receiving the error, the URL contains a domain in it that is not the recipients domain. When this issue is happening the sender is able to send working secure emails from OWA and the mobile app, just not from the Outlook desktop app. We have had it pop up on multiple users at random times after we pushed out the labels. The only known fix we have is to rebuild the senders windows profile. Wondering if anyone else has experienced this and has been able to find a resolution?
Microsoft Purview
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 18%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGG%3C/text%3E%3C/svg%3E)
Ganesh Gurram 6,780 Reputation points Microsoft External Staff Moderator2025-05-09T17:02:29.0833333+00:00 The error message
"Sorry, we can't display your message right now. Something went wrong and your encrypted message couldn't be opened"typically occurs when the Outlook desktop client fails to authenticate or access the required services to decrypt the message.Potential Causes and Recommended Actions:
Creating new windows profile - Delete the affected user's Windows profile (or Outlook profile), and then recreate it. This forces the system to download a fresh set of user configurations, including Microsoft Purview policies and encryption settings.
Reference: Microsoft Docs – Encrypted message errorConditional Access Policies - Conditional Access (CA) policies might be blocking access to Microsoft Information Protection endpoints. Review any CA policies to ensure services like Microsoft Azure Information Protection or Microsoft Information Protection are not inadvertently blocked.
Reference: More info on CA and sensitivity labelsSensitivity Label Restrictions - If the applied sensitivity label is scoped to internal recipients only, external users may not be able to access the message. Review label encryption settings in the Microsoft Purview compliance portal to confirm that intended access is permitted. Reference: Configure encryption for sensitivity labels
Multi-Factor Authentication (MFA) - MFA requirements can affect external recipients if they are unable to complete the challenge. Outlook Web App and mobile clients often succeed in these cases because decryption is handled in the cloud.
Reference: External recipient can't open encrypted emailFor more details refer to this similar thread: https://answers.microsoft.com/en-us/outlook_com/forum/all/encrypted-message-sorry-we-cant-display-your/606285fb-98aa-414a-97c0-ac5602165621
I hope this information helps.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
-
Ganesh Gurram 6,780 Reputation points Microsoft External Staff Moderator
2025-05-12T08:25:34.04+00:00 We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
-
Steve Mauer 0 Reputation points
2025-05-12T20:17:51.3033333+00:00 Hello,
I have not found a resolution yet.
-
Ganesh Gurram 6,780 Reputation points Microsoft External Staff Moderator
2025-05-12T22:00:59.16+00:00 @Steve Mauer - Thanks for the update.
According to this MS documentation: https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/office-message-encryption/cannot-display-message
This problem occurs because the MIME types that are associated with the default Outlook Web App policy changed so that the text/html MIME type was removed or changed.
Solution:
To resolve this problem, reset the MIME types that are associated with the default Outlook Web App policy to the default values. To do this, follow these steps:
- Connect to Exchange Online by using remote PowerShell. For more information about how to do this, see Connect to Exchange Online Using Remote PowerShell.
- Run the following commands:
$owapolicy = Get-OwaMailboxPolicySet-OwaMailboxPolicy -AllowedMimeTypes @{remove = "text/html"} -BlockedMimeTypes @{remove = "text/html"} -ForceSaveMimeTypes @{add = "text/html"} -Identity $owapolicy.IdentityNote - It may take as long as 30 minutes for the changes to take effect.
For more details refer: Outlook Web App Mailbox Policy Procedures.
I hope this information helps.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
-
Steve Mauer 0 Reputation points
2025-05-13T14:36:35.9933333+00:00 Hello,
That looks like it is just for OWA, our problem is with the desktop app. I did give it a try anyway though, it did not make any changes
-
Ganesh Gurram 6,780 Reputation points Microsoft External Staff Moderator
2025-05-13T18:59:17.2766667+00:00 Thanks for the update. Since the issue is specifically affecting the Outlook desktop app and not resolved by the previous steps, another likely cause is related to the permissions configured in the sensitivity label used for encryption.
Please check if the sensitivity label applied to the email includes permissions for external users. Update the label permissions to explicitly allow access to the intended external recipients.
Sign in to comment
Sign in to answer