Back to latest version

MC887373 - Microsoft Purview: Message Encryption portal transitioning to the ".microsoft" domain by the end of 2024

Message Center

Metadata at Sep 10, 2024

Published

Sep 10, 2024

Service

Microsoft Purview

Tag

Major change
Feature update
User impact
Admin impact

Metadata changes

Title
Microsoft Purview: Minor encrypted message portal design updates, URL to remain the sameMicrosoft Purview: Message Encryption portal transitioning to the ".microsoft" domain by the end of 2024
Tags
Admin impact, Feature update, Updated message, User impactAdmin impact, Feature update, User impact

Body changes

removed textadded text

Updated October 23, 2024: The Microsoft Purview Message Encryption portal will undergo minor design updates to align with Purview branding. Organizations may need to update training and documentation accordingly.

Microsoft will be updating fonts, colors, controls, and more to align with Purview branding. These changes are designed to enhance the user experience without causing any disruptions.

We will be proceeding with the minor design updates on the portal (fonts, colors, controls and more). These changes are to align with Purview branding and should not disrupt users.

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out late October 2024 (previously mid-October) and expect to complete by late December 2024 (previously mid-December).

How this affects your organization:

Users will see minor design changes within the UI.

This isn't the final or complete list, but here are some prominent changes that users will notice:

1. Removed the bottom button bar.

2. Moved the emoji button to the formatting bar.

3. Relocated the toggle formatting option button to the top bar.

4. Updated the insert table control to allow size entry.


What you need to do to prepare:

You may consider updating training and documentation as appropriate.

---Summary of original message---

The Microsoft Purview Message Encryption portal provides access to encrypted messages sent from your organization's users to external recipients. The cloud.microsoft domain was provisioned in early 2023provisioned in early 2023 to provide a unified, trusted, and dedicated DNS domain space to host Microsoft’s first-party authenticated SaaS products and experiences. With this rollout, selected Microsoft products and scenarios will transition to a similar static.microsoft domain, in parallel with the previous domains. As part of this transition, the design of the portal (fonts, colors, controls, and more) will be adjusted to align with Purview branding and domain change.

Microsoft Purview Message Encryption portal (https://MessageEncryption.purview.static.microsoft)

A full list of products and scenarios already being delivered on the static.microsoft domain can be found at Unified cloud.microsoft domain for Microsoft 365 apps - Microsoft 365 Enterprise | Microsoft Learn.

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out mid-October 2024 and expect to complete by mid-December 2024.

How this will affect your organization:

Users that receive encrypted messages that have a link to open the mail in the encrypted message portal will be redirected to applications under static.microsoft domains gradually and automatically. No specific user action is required. Links to the previous domains are backwards compatible and will continue to be supported. Users may notice that the new application domains are lacking the .com extension, which is by design, because .microsoft is Microsoft’s own top-level domain. This exclusivity allows for additional security and protection against spoofing.

This change is on by default.

What you need to do to prepare:

  • Educate users to recognize and expect static.microsoft as a key domain for Microsoft cloud experiences. Users can learn more about the .microsoft domain in What is cloud.microsoft? - Microsoft Support
  • If your organizational websites, tools, or other materials reference the old URL outlook.office365.com/Encryption, those links will be automatically redirected. It would be good practice to update those assets and any documentation with screenshots to avoid user confusion.
  • Admins should ensure that connections to *.static.microsoft are not blocked from their clients and enterprise networks. This recommendation should require no action if you are following standard Microsoft network guidance on domains and service endpoints