Recipients can't open encrypted emails - Wrong domain in URL

Josh Weigner 1 Reputation point
2025-02-21T15:51:26.6866667+00:00

We are experiencing issues with sending encrypted emails. Recipients can't open our encrypted emails, with the error "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." When looking at the URL, it contains the domain of the last person that the sender (our user) RECEIVED an encrypted email from. If they send the same message again, the recipient can open it. It seems that the domain in the URL is behind by one, which is why resending the same email to the same recipient works. Microsoft support hasn't been useful so far.

Example:

******@contoso.com receives an encrypted email from ******@abccompany.com

******@contoso.com sends an encrypted email to ******@xyzcompany.com

**@xyzcompany.com can't open the encrypted email. When we look at the URL of the encrypted email, we see: senderorganization{longstring}%26messageid%3D%{longstring}.prod.exchangelabs.com%253e%26cfmRecipient%3abccompany.onmicrosoft.com%26consumerEncryption%3

******@contoso.com resends the same encrypted email to ******@xyzcompany.com

**@xyzcompany.com can open the encrypted email. When we look at the URL of the encrypted email, we see: senderorganization{longstring}%26messageid%3D%{longstring}.prod.exchangelabs.com%253e%26cfmRecipient%3admin.xyzcompany.com%26consumerEncryption%3

Microsoft Purview
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,532 questions
{count} votes

2 answers

Sort by: Most helpful
  1. AnnuKumari-MSFT 34,456 Reputation points Microsoft Employee
    2025-02-26T06:18:06.82+00:00

    Hi Josh Weigner ,

    The team confirmed that the necessary adjustments to the sensitivity label were made to allow external users access to their encrypted emails. The issue is mitigated by editing the sensitivity label to include the external addresses or domains.

    Kindly check at your end and let me know if it's fixed or you are still facing the issue. Thankyou

    0 comments No comments

  2. Craig Manthei 0 Reputation points
    2025-04-22T17:01:52.9966667+00:00

    Good afternoon,

    We are running into the same issue. With us sending secure emails to 1000's of different domains, is the expectation that we are going to manually add all of those domains and external addresses to the sensitivity policy?


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.