Microsoft has quietly turned on a new channel that lets administrators push Copilot onboarding messages directly into employee inboxes, expanding the Organizational Messages tool beyond Windows surfaces and Teams pop-overs. The feature reached general availability between mid-May and mid-June 2026, but the rollout comes with a critical constraint: only eight pre-built, non-customizable templates are available to start, all tied to Copilot and Copilot Chat. That narrow scope is both a safeguard and a signal — organizations that fire off tenant-wide campaigns without a plan risk teaching users to ignore official mail.

What Actually Changed

Organizational Messages in the Microsoft 365 admin center started as an in-product notification system. Messages appeared on the Windows lock screen (Spotlight), in the taskbar, inside the Notification Center, or as Teams pop-overs. They were designed to nudge users about features, training, or service updates without competing with the email deluge.

Now the tool gains email delivery alongside those existing surfaces. The process lives under Reports > Organizational messages in the admin center. An authorized writer picks an objective — currently limited to adoption, onboarding, sustainability, or tech updates — but when email is the location, the template catalog shrinks to exactly eight options:

  • Two welcome messages: “Welcome to Copilot” and “Welcome to Copilot Chat”
  • Six messages from the “Great M365 Copilot Journey,” each highlighting a feature or best practice

None of the email templates are customizable beyond adding a logo and a URL. You cannot rewrite the headline, body copy, or calls to action. For organizations that need different wording to match internal terminology, staged rollouts, or data-handling policies, that’s a hard boundary.

Targeting is where administrators regain some control. Recipients can be selected through Microsoft Entra groups or — if the tenant has the required E3/E5 or Windows Enterprise licenses — advanced group-level aggregates: company, department, location, and usage. The usage option is particularly relevant:

  • Inactive Copilot users: anyone with a license who hasn’t used Copilot in the last 28 days
  • Inactive Copilot users in Teams: same idea but scoped to Teams activity over 30 days

Technical requirements are lighter for email and Teams than for Windows surfaces. You don’t need Intune device configuration policies or specific firewall endpoints to deliver an email; those only apply to Spotlight, taskbar, and Notification Center. That means a global admin or Organizational Messages Writer can start an email campaign quickly — perhaps too quickly. The approval workflow is also bypassed for pre-made templates, so no second set of eyes is mandatory before the message heads to thousands of mailboxes.

What It Means for You

For IT and Microsoft 365 admins

The email channel looks like a low-friction way to boost Copilot adoption, but it’s deceptively high-stakes. Unlike a taskbar tip that vanishes when dismissed, an email sits in the inbox indefinitely, searchable and forwardable. If employees perceive it as marketing noise — or, worse, a phishing test — they’ll mentally file all future “from the company” automated mail into the same ignore bin.

That makes cross-team alignment essential before campaign one. Internal communications teams should review the message’s appearance and timing. Security teams need to know the sender address and exact subject lines so they can update awareness materials. Help desks must be ready for “Is this real?” tickets.

The reporting dashboard shows total messages seen (impressions), total clicks, and click-through rate, with CSV export for deeper analysis. Those are vanity metrics if taken alone. A click might mean curiosity, confusion, or a reflexive attempt to verify legitimacy. The real question is whether the campaign closed a measurable gap: fewer support requests about Copilot basics, higher feature utilization, or smoother onboarding.

For end users

Employees will see emails from their own organization, not from Microsoft, pushing Copilot tips. The from-address and reply-to will depend on the tenant’s configuration. Without prior warning, those messages could look suspicious. Once users learn to expect them, the next danger is habituation — if the content feels generic or mistimed, they’ll stop reading.

For security and compliance teams

A new, centralized email source adds another variable to phishing defense. Employees are trained to pause on unexpected links, even from internal senders. Organizational Messages campaigns should therefore be announced in advance, limited to defined audiences, and never sent during active security incidents. If a campaign triggers phishing reports, treat that as valuable feedback about how the message was perceived — not just a false positive.

How We Got Here

Microsoft introduced Organizational Messages as a way to inject official communications inside the products people already use. The feature first appeared with Windows 11 Enterprise surfaces (Spotlight, taskbar, notifications) and later expanded to Teams pop-overs. The obvious gap was email — the channel where most employees still receive critical operational mail.

The push for Copilot adoption accelerated the timeline. Microsoft has been building out the “Great M365 Copilot Journey,” a sequence of template messages designed to guide users from first discovery to regular use. Email made sense as a delivery surface because it’s persistent and scannable, unlike fleeting notifications.

General availability was announced through the Microsoft 365 admin center message center (MC1189665) and rolled out broadly by late June 2026. The documentation on learn.microsoft.com now reflects the email option, along with usage-based targeting and the pre-made template library.

What to Do Now

1. Decide if email is even necessary. Before touching the admin center, write down the communication problem you’re trying to solve. If existing Teams posts, manager-led training, or service-desk content already covers Copilot onboarding, adding email may create noise without benefit.

2. Start small. Pick one audience — for example, a department that just got Copilot licenses but hasn’t used them. Using the “inactive Copilot users” targeting is a good way to reach people who might genuinely need a nudge. Avoid sending to the entire tenant just because you can.

3. Preview the template in your context. The fixed wording might not match your organization’s exact stage. If you’re in a staged rollout, the welcome message could arrive before someone has access, causing confusion. If that’s likely, prepare a separate, short email or Teams announcement that explains why the Copilot message is arriving and what to do with it.

4. Brief your defenders. Send the exact subject lines, sender address, and example screenshots to your security team and help desk. Ask them to update any phishing-awareness materials. If possible, schedule the campaign for a quiet period and monitor the phishing report rate as an early signal of trust.

5. Set up the campaign correctly. In the Microsoft 365 admin center:

  • Go to Reports > Organizational messages.
  • Select Create a message.
  • For Objective, choose Adoption.
  • For Location, choose Email.
  • Pick one of the eight Copilot templates.
  • Add your logo and an internal URL (e.g., your Copilot support page).
  • Under Recipients, select an Entra group or use advanced targeting (e.g., Usage: Inactive Copilot users).
  • Set a start date, end date, and frequency. Because email can’t be “dismissed” like a notification, avoid high-frequency repeats — once per user per phase is often enough.
  • Review and schedule. No approver needed for pre-made templates.

6. Measure what matters. After the campaign, pull the CSV report and look at click-through rate and impressions. Then compare against pre-campaign baselines: Did Copilot adoption tick up in that group? Did help-desk ticket volume for “how to use Copilot” drop? If not, the campaign may not be worth repeating.

7. Plan to stop. Once a target group has received the relevant message, don’t let the campaign linger. Set a firm end date. Over-messaging turns adoption efforts into background hum that employees train themselves to ignore.

Outlook

The email channel will almost certainly broaden. Microsoft’s documentation already mentions “pre-made” templates as distinct from “create your own” custom messages, and the admin center includes a full custom-message workflow — gated behind advanced licensing for now. Once custom email becomes available, the governance questions get sharper: who can write a broadcast to all employees, what subjects are permitted, and how do you prevent “urgent” from being abused.

For now, the eight Copilot templates act as a low-risk on-ramp. Use them to prove that targeted, well-governed email can genuinely help employees adopt Copilot. If the pilot shows real improvement — not just click numbers — you’ll have a solid case for expanding responsibly. If it doesn’t, you’ll have saved your organization the cost of yet another ignored inbox channel.