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.
You host the gateway. Community filters inbound mail on that host. Professional holds matching outbound mail for a one-time-code portal. Keys stay on your host. This is email — not Purview, not TigerConnect, not a chat app.
Secure Message sits in front of the mail you already run. Point MX at the gateway and relay outbound through it as a smart host. Mailboxes stay where they are. 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.
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. That split is on the OME replacement page.
Encryption at rest under your keys, audit logs, and the whole path on infrastructure you own. The recipient portal is Professional. We describe it as built to HIPAA safeguards, not as a certification.
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 how it works or pricing.