Before you picture a new internal newsletter engine inside the admin center: this is a narrow channel. Right now it is mostly a delivery route for Microsoft's Copilot adoption campaigns. That is useful, but it is not a general-purpose announcement tool.
What actually shipped
Message Center post MC1189665, which Microsoft tied to the same roadmap ID, said email will be added as a delivery channel for Organizational Messages. Microsoft also said it helps organizations reach users through familiar communication channels, improving engagement and adoption.
The rollout dates moved more than once:
- Public preview: Rollout began in mid-November 2025 and is expected to complete by late January 2026.
- General availability: the updated Message Center post said GA begins in mid-May 2026 (previously late April).
- An earlier date: a copy of an earlier version kept by the M365 Admin archive site listed General Availability in late March 2026.
If you remember an earlier date, you're not imagining things. It slipped twice before it landed.
Microsoft Learn's current documentation describes email messages as a GA capability. Admins can send premade, templated messages by email alongside the existing Windows and Teams surfaces. The same notice also announces usage-based targeting. That is a separate feature, and it is covered further down.
Section summary: Email is now a GA delivery location for Organizational Messages in worldwide commercial tenants. It arrived after a preview that started in November 2025 and a GA date that moved twice.
The catch: templates only, and none are editable
This is the most important detail for anyone planning to use the feature. Microsoft Learn states that email functionality is currently limited to the eight provided pre-made templates. The email templates aren't customizable.
According to Microsoft's documentation, those eight templates are:
- Welcome to Copilot
- Welcome to Copilot Chat
- to 8. Six "Great Microsoft Copilot Journey" templates covering Copilot features and best practices for onboarding and adoption.
Not every source agrees on the count:
- ReconnAI's Copilot changelog reports 9 premade email templates available in 15 languages. It lists a third welcome template, "Welcome to Copilot Trial."
- LazyAdmin's preview write-up found that during the public preview, the available email templates are focused entirely on Copilot onboarding and adoption.
The safest assumption is that your tenant shows roughly eight or nine templates, all about Copilot, and none of them editable.
Compare that with the rest of Organizational Messages. On Windows and Teams surfaces, authors can add a logo and URL to premade messages or write fully custom messages. Email gets none of that. LazyAdmin summed it up: if you were hoping to use email as a general-purpose channel for admin communications, you will need to wait for more templates to arrive.
LazyAdmin also reported that the emails were sent from [email][email protected][/email] during its preview testing. That address comes from a third-party write-up, not Microsoft documentation. Still, it gives mail-flow and phishing-awareness teams something to watch for. Users trained to distrust unfamiliar senders may report a Copilot welcome email from that address as suspicious.
Section summary: The channel is real, but the content is fixed. It works for Copilot onboarding, not for "the parking garage is closed Friday."
How to send an email Organizational Message
Microsoft's documented process uses the existing wizard:
- Sign in to the Microsoft 365 admin center.
- Go to Show all > Reports > Organizational messages.
- Select Create a message.
- Choose an Objective. Options include Adoption, onboarding, Sustainability and Tech updates.
- At Location, pick email. Microsoft Learn says supported locations include Windows Spotlight, the taskbar, Notification Center, Microsoft Teams and email.
- Choose one of the premade email templates.
- Select recipients and set a schedule, then submit.
Prerequisites:
- Author role: whoever creates messages needs the Organizational Messages Writer Microsoft Entra role. Microsoft's FAQ explains how to assign it: go to Users > Active users, select the user, choose Manage roles, open Admin center access, select Show all by category, and find the role under Other.
- No approval for premade messages: Microsoft says premade messages need no approval before delivery. Only custom messages go through the Organizational Messages Approver workflow. Because every email message is a premade template, an approval queue doesn't apply to this channel.
- No Intune tenant policies: Microsoft Learn says tenant policies are needed only for Windows surfaces such as Spotlight, Notification Center and Taskbar. They aren't needed for Teams notifications or email. Requirements such as Windows 11 Enterprise 24H2/25H2 and the KB needed for the Taskbar experience apply to Windows delivery, not email.
Section summary: If you can already author Organizational Messages, sending an email takes a few clicks. No Intune configuration or approver review is needed.
Targeting, languages and limits
A few boundaries from Microsoft's documentation help set expectations:
- Targeting varies by location. Microsoft notes that targeting options depend on the chosen location. Windows channels support Entra groups plus advanced group-level aggregate targeting. Teams supports Entra groups only. The new "Usage" targeting (Inactive Copilot Users and Inactive Copilot Users in Teams) is documented for Windows Spotlight, Taskbar, Notification Center and Teams, and email is not on that list. Plan on Entra groups as your main way to target email recipients. Advanced targeting by department, location or company also requires Microsoft 365, Office 365 or Windows Enterprise E3/E5 licensing.
- Localization. Microsoft's FAQ lists 15 supported locales for Organizational Messages. Premade messages are created in all of them, and each recipient gets their first preferred language if it is supported.
- Government clouds are out. The FAQ says GCC and GCC-High environments aren't supported at this time.
- Delivery isn't instant. Microsoft says non-urgent messages take a few hours after scheduling before they can be delivered. Don't send one at 4:55 p.m. and expect inboxes to light up by 5:00.
Section summary: Use Entra groups, expect a delay of a few hours, and don't expect this in government tenants.
Measurement: no open-rate tracking
Microsoft Learn includes a note that matters for anyone reporting campaign results. Open tracking is being removed for Organizational Messages emails worldwide. New open-count metrics won't be available, but previously collected open-count data stays accessible.
The general Review activity dashboard still covers messages seen, clicks, dismisses and click-through rate, with charts and CSV export. Without open counts, though, measuring email performance comes down to clicks. If your Copilot adoption sponsor asks how many people opened the welcome email, the platform can't tell you anymore.
The tradeoff makes sense. Open-tracking pixels are unreliable because of client-side image blocking and privacy protections, and many organizations dislike them anyway. It does leave this channel with less reporting than the in-product surfaces have.
Analysis: who benefits, and who should wait
The case for using it is simple. The original feature reached people through Windows and Teams, so it missed anyone who ignores toasts, uses a non-Windows device or keeps Teams minimized. Email reaches users wherever they read mail. Microsoft frames the benefit as accelerates Microsoft 365 Copilot awareness, onboarding, and adoption through centralized campaign management. If you're running a Copilot rollout, a ready-made six-part "journey" series costs you nothing to write. That is a real saving for small IT teams without a communications department.
There is a skeptical reading too. A Microsoft-built email channel whose only content promotes Microsoft's flagship paid AI product fits a pattern: Copilot adoption tooling keeps showing up across the admin center. Admins should decide whether a Microsoft-written, unbranded, non-editable email matches their organization's tone. A bland vendor template can land worse than a short note from your own CIO.
Practical recommendations:
- Copilot rollout teams: pilot the welcome templates on a small Entra group, then check click-through in Review activity before sending more widely.
- Security teams: let your helpdesk and phishing-report triage know about the sender address, so users who report these emails get a quick answer.
- Everyone else: keep using your existing mail tools for general announcements. Organizational Messages email can't send your own content yet.
Bottom line: Email support adds a real channel to Organizational Messages, but for now it only carries Microsoft's Copilot templates. Use it for Copilot onboarding, and wait for editable templates before relying on it for anything else.