Ask Secure Message a question. Answers come from this site's docs only. I will cite a page. I will not invent a product claim.
Purview is Microsoft’s compliance suite in their cloud. We are MX in, portal + code out, keys on your host.
Microsoft Purview is a compliance suite that runs in Microsoft’s cloud. Microsoft is retiring Office 365 Message Encryption in favor of Microsoft Purview Message Encryption. The new name does not move the keys or the message path onto your host. Purview still processes protected mail on Microsoft infrastructure.
Secure Message is a self-hosted email gateway. Point MX at it and relay outbound through it as a smart host. Matching outbound mail is held and opened in a one-time-code portal. Encryption keys live on the host you run. Mailboxes stay where they are.
This is email — not Purview, not TigerConnect, not a chat app. Recipients do not install a client, join a chat, or create an account. They open a link and enter a one-time code sent to the mailbox they already have.
The retirement of Office 365 Message Encryption is on the OME replacement page. This page is the split with Purview itself: their cloud, or your host.
Enterprise adds Autopilot, eDiscovery, and DLP. The inbound classifier is one Enterprise signal and stays off until you turn it on. Message content is not sent to a vendor model unless you opt into a hosted provider.
Rubix PDF Sign fills, signs and flattens PDFs on the workstation. No cloud account, no telemetry. It is a free download, and meant to pair with the gateway: sign locally, then send through Secure Message.
See the HIPAA email gateway page or pricing.