Microsoft 365 Action Segments Target Inactive Copilot Users

Microsoft 365 Organizational Messages now supports Action Segments, a usage-based targeting option that lets IT administrators direct in-product prompts at people based on recent Copilot activity rather than static Entra ID group membership. Microsoft lists the feature under Roadmap ID 503563, with general availability beginning in May 2026 for worldwide standard multi-tenant tenants.
The change is aimed squarely at Copilot adoption campaigns. Instead of building and maintaining a group for users who may need a reminder, admins can select Microsoft-defined behavioral segments when creating an organizational message. Microsoft’s release notes describe the capability as usage-based targeting, while the admin documentation calls the predefined audiences Action Segments.

What the initial segments cover​

Per Microsoft Learn, the generally available release starts with two Copilot-oriented segments:

• Inactive Copilot users: licensed Microsoft 365 Copilot users who have not used Copilot in the previous 28 days.
• Inactive Copilot users in Teams: licensed Microsoft 365 Copilot users who have not used Copilot in Teams in the previous 30 days.

That is a narrow first implementation, but it removes a common administrative chore: translating product-use data into membership rules or manually curated campaign lists. The targeting is dynamic, so a user’s eligibility should change as their behavior changes.
Messages can be delivered through the existing Organizational Messages surfaces: Windows Spotlight, the Windows taskbar, Notification Center, and Microsoft Teams notifications. The feature does not turn into a general-purpose user surveillance or messaging system; it works within the Organizational Messages service and its supported in-product channels.

Requirements and caveats​

Microsoft’s Organizational Messages documentation says message authors need the Organizational Messages Writer role. Customized messages and advanced targeting are restricted to tenants holding at least one qualifying E3 or E5 license across Microsoft 365, Office 365, or Windows Enterprise.
For Windows delivery, recipients need Windows 11 Enterprise and Microsoft Entra ID-joined devices. Microsoft Entra hybrid-joined devices are not supported for Organizational Messages. Admins must also configure the relevant tenant and Windows policy settings before messages can be delivered.
Microsoft notes that non-urgent messages are not necessarily immediate. After scheduling, delivery eligibility can take several hours, and Windows’ pull-based delivery model can mean 24 hours or more before a message appears on an endpoint. That makes a small pilot more sensible than assuming a campaign will reach everyone at a fixed time.
Action Segments first appeared in public preview in December 2025, and Microsoft’s June 2026 Copilot release notes marked usage-based targeting generally available. The roadmap entry was last updated on July 13, 2026, but does not announce additional segment types beyond the initial Copilot inactivity audiences.
For admins already using Organizational Messages, the practical next step is to test one of the inactive-Copilot segments against a low-noise adoption prompt and verify delivery, policy coverage, and engagement reporting before expanding the campaign.

---

References​

1. Primary source: Microsoft 365 Roadmap
   Published: 2026-07-13T23:07:14.8221961Z
   
   

   Microsoft 365 Roadmap | Microsoft 365

   The Microsoft 365 Roadmap lists updates that are currently planned for applicable subscribers. Check here for more information on the status of new features and updates.

   www.microsoft.com
2. Official source: learn.microsoft.com
   
   

   Organizational messages in Microsoft 365 - Microsoft 365 admin | Microsoft Learn

   Learn how to create and manage organizational messages in the Microsoft 365 admin center. Drive adoption and configure delivery to Windows and Teams.

   learn.microsoft.com