Microsoft Roadmap, messagecenter and blogs updates from 24-03-2026

Updated March 23, 2026: We have updated the timeline below. Thank you for your patience.

To help you manage metered consumption costs for Microsoft 365 Copilot Chat, we will introduce a new Message consumption usage report in the Microsoft 365 admin center. The new report will give you visibility into billed messages associated with your Microsoft 365 Copilot pay-as-you-go billing policies and includes total messages consumed, cumulative and daily time series, and messages per user, per billing policy, per agent, and per agent-user pair. The new report will roll out in preview. During the preview stage, the report will display a maximum of 30 days of message consumption history. Usage information from prior to May 3, 2025, will not be available in the report.

This message refers to Microsoft Copilot in a pay-as-you-go model. A Microsoft Copilot license is not required.

This message is associated with Microsoft 365 Roadmap ID 490738.

[When this will happen:]

Public Preview: Available now.

General Availability (Worldwide): We will begin rolling out in September 2026 (previously March) and expect to complete by end of September 2026 (previously end of March).

[How this will affect your organization:]

After you have set up pay-as-you-go billing for Microsoft 365 Copilot, either in the Microsoft 365 admin center or the Microsoft Power Platform admin center, and you have enabled agent usage in your organization, you will see a new report including metrics for messages consumed at the levels of tenant, users, agents, and agent-user. To help you mitigate overspending, you will see alerts when users have consumed more than 2000 billed messages.

This new report will be on by default and will be available in the Microsoft admin center at Reporting > Usage > Microsoft 365 Copilot > Message consumption:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify any admins that manage agents on the integrated apps page about this feature.

Learn more: Microsoft 365 reports in the admin center – Message consumption

Updated March 23, 2026: We have received customer feedback during Public Preview regarding the “Other” prompt category. To help avoid confusion for this category: 1) In the Impact tab within the Copilot Chat deep dive, there will be an updated calculation for the number of prompts submitted in the “Other” category; 2) In the Adoption tab under the “Adoption by app” table, the row for the active user counts corresponding to the “Other” category will be removed. These changes will start rolling out at the end of March 2026 and the Microsoft Learn documentation will contain updated details. Thank you for your patience.

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 486698.

Public Preview: We will begin rolling out in early September 2025 (previously mid-September) and will complete by late September 2025

General Availability (Worldwide): We will begin rolling June 2026 (previously late February) and expect to complete by end of June 2026 (previously end of February).

[How this will affect your organization:]

Users enabled to view Copilot dashboard will see these updates:

1. Adoption tab: Prompt categories will be available at Viva Insights > Microsoft Copilot Dashboard > Adoption > Adoption by app > Copilot Chat (work) dropdown:

2. Impact tab: Admins can go to Viva Insights > Microsoft Copilot Dashboard > Impact > Copilot chat card > Explore more button to access the prompt categories as metrics in the Copilot impact trend section and the Comparison between groups section:

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins and/or users about this change and update internal documentation.

Review and assess the impact for your organization. You might consider reviewing with your works council and updating your training and documentation as appropriate.

Learn more: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

Updated March 23, 2025: We have updated the timeline. Thank you for your patience. 

To help you manage agent adoption for Microsoft 365 Copilot Chat, we are introducing a new usage report in the Microsoft 365 admin center. The report provides visibility into how users in your organization are actively using agents in Microsoft 365 Copilot Chat and includes metrics such as: 

• Total number of active agent users and active agents 
• Usage breakdown per user, per agent, and per user-agent pair 
• Segmentation by license state (licensed vs. unlicensed Microsoft 365 Copilot users) 
• Segmentation by agent creator type (i.e. agents built by your organization, Microsoft, or Microsoft partners) 

The new report is rolling out in preview and will be available under Reporting > Usage > Microsoft 365 Copilot > Agent. During the preview stage, the report will display a maximum of 30 days of history. In addition, usage information from prior to August 19 2025 will not be available in the report. This report only includes declarative agents. Usage data for SharePoint agents and Custom engine agents will be available in a future update.

This message is associated with Microsoft 365 Roadmap ID 497999

[When this will happen:]

Public Preview (Worldwide): Available now.

General Availability (Worldwide): We will begin rolling out in early May 2026 (previously March) and expect to complete by mid-May 2026 (previously end of March).

[How this will affect your organization:]

[What you need to do to prepare:]

Updated March 23, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

Agent in Viva Engage communities are now available in Public Preview. Community admins can add agents to communities to help draft answers to questions without best or verified answers based on community content and add context to posts by answering follow up questions using the community’s conversations and SharePoint site and library.

We’re now adding the option for community admins to specify additional SharePoint sites outside the community as grounding sources. The agent will only use sites that community admins select, and it drafts answers from items that community members can view (Read).

We are also adding a new capability: tagging by community members. Tagging by community members enables Microsoft 365 copilot-licensed users to @-mention the community agent in the comments and replies of threads with follow up questions and requests to add context to posts. When tagged, the community agent will reply in the post. Tagging by community members will be enabled by default, but can be disabled by community admins in the agent settings.

[When this will happen:]

• Agents in communities Public Preview: available now
• SharePoint Grounding on Community site and library Public Preview (Worldwide): available now
• Grounding on SharePoint sites and libraries outside the community and tagging by community members Public Preview (worldwide): Rollout begins late March 2026 (previously mid-February) and should be completed by mid-April 2026 (previously mid-March).
• General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

• Who is affected: Viva Engage community admins and members with Microsoft 365 Copilot licenses; Global and Engage admins managing Viva Engage networks
• What will happen:
• During Public Preview:
• Admins can opt their network into the preview via the Engage admin center: Engage admin center > Tenant Settings > Enable Community Agent Public Preview.

Figure i. Add agent to community​

The agent will proactively draft answers to unanswered questions using past conversations.

By default, the agent posts answers automatically.

Admins can configure whether the agent posts answers automatically or only after approval and if tagging by community members is enabled.

Figure ii. Configure the agent’s capabilities and knowledge sources

[Grounding on SharePoint sites outside the community]

• Community admins can add SharePoint sites and libraries outside the community as additional grounding sources (for sites/libraries they administer).
• When an admin adds a site or library, they’ll be prompted to grant the community’s Microsoft 365 group Read access if it doesn’t already have permission.
• The agent only drafts answers using content that all community members can view (Read).
• By default, the agent uses the community’s SharePoint site and library. Any sites outside the community are optional and add to (not replace) the default grounding.

If Require review is enabled, admins and designated experts will be notified when the agent drafts an answer. They can approve, edit, or dismiss the response.

Figure iii. Community admins and experts can review agent suggestions​

If tagging by community members is enabled, then community members can @-mention the agent in messages.

Coming soon (General Availability):

The agent will only use content that all community members can access.

Admins must be owners of the SharePoint sites they wish to configure.

Admins can add additional SharePoint sites to expand the agent’s grounding knowledge.

The agent will be grounded by default on the community’s SharePoint site.

Community members can tag the community agent in community posts.

All Microsoft 365 Copilot licensed users will have access to the Community Agent by default.

The Community Agent Public Preview toggle will be retired.

• If participating in preview:
• Opt your network into the preview via the Engage admin center
• Communicate this change to helpdesk staff. 
• Update internal documentation that references Viva Engage Community Agent behavior or setup.
• No action is required at GA; the feature will be on by default.

Learn more: Set up and manage agents in Viva Engage communities | Microsoft Learn

[Compliance considerations:]

Updated March 23, 2026: We have updated the timeline. Thank you for your patience. 

We’re introducing more flexible and precise audience targeting in Viva Engage, starting with Storyline Announcements. This update allows leaders and their delegates to define a custom audience at the time of posting—without relying on pre-configured Leader Audiences. Audiences can include organizational attributes (such as reporting structure, country, department, job title), existing groups (Microsoft 365 Groups, DLs, SGs), or individual users by name. This flexibility enables more timely, targeted communication, helping leaders reach the right people with the right message. Notifications and delivery channels (such as Teams, email) will continue to follow existing Storyline Announcement behavior, ensuring a seamless experience for recipients.

This feature is ideal for leaders who want to tailor communications to specific departments, locations, or existing groups, enhancing relevance and engagement across the organization.

This message is associated with Microsoft 365 Roadmap ID 499895.

[When this will happen:]

• Public Preview (Worldwide): Begins mid-November 2025 and completes by mid-March 2026 (previously early February).
• General Availability (Worldwide): Begins late May 2026 (previously mid-March) and completes by end of June 2026 (previously mid-April).

[How this affects your organization:]

Who is affected: Leaders and delegates using Viva Engage Storyline Announcements in tenants enrolled in public preview.

What will happen:

• This capability is being introduced as part of the public preview for Viva Engage. During this phase, leaders and their delegates can actively experiment with flexible audience targeting for Storyline Announcements—defining a custom audience at the time of posting, rather than relying solely on pre‑configured Leader Audiences.
• Audiences can include organizational attributes (such as reporting structure, country, department, job title), existing groups (Microsoft 365 Groups, DLs, SGs), or individual users.
• Notifications and delivery channels (Teams, email, Viva Engage Inbox) remain unchanged for recipients.
• No dependency on IT or advance audience setup—leaders can act immediately when communication needs arise.
• Available only in public preview; functionality and targeting options may evolve before general availability.
• Admins should ensure organizational attributes in Entra ID or Organizational Data in Microsoft are accurate to support successful targeting.
• Available platforms: Desktop and web.
• Licensing requirements: This feature requires a premium license available through Viva or Communications and Communities (C&C). Availability may vary depending on your organization’s Microsoft 365 licensing agreement.

[What you can do to prepare:]

No admin action is required for rollout. To prepare, you may want to:

• Validate organizational attributes (reporting structure, country, department, role, job title) in Microsoft Entra ID or Organizational Data in Microsoft.
• Confirm leader and delegate assignments to ensure the right people can use Storyline Announcements and the new targeting control.

Learn more:

• Use your organizational data in Microsoft 365 and Microsoft Viva | Microsoft Viva | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated March 23, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption.

This message is associated with Roadmap ID 523213.

[When this will happen:]

• Public Preview: Rollout begins in late November 2025 and is and expected to complete by mid-January 2026
• General Availability: Rollout begins in mid-May 2026 (previously late April) and is and expected to complete by early June 2026 (previously early May).

[How this affects your organization:]

• Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices
• What will happen:
  • A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs
  • The wizard dynamically adjusts based on your organization’s security policies
  • Supports MFA setup, with emphasis on Microsoft Authenticator push notifications
  • This tool is optional and designed to improve BYOD Microsoft Teams adoption

[What you can do to prepare:]

• Review the admin documentation to understand the onboarding wizard’s capabilities and limitations
• Consider integrating the wizard into your new user onboarding workflows
• Communicate availability to helpdesk and frontline managers
• Update internal documentation if you support BYOD Microsoft Teams deployment
• Review documentation at the following link: Set up frontline Teams on personal devices

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated March 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing the Data Security Posture Agent, available in public preview December 24, 2025. This agent helps data security admins proactively discover sensitive data across your organization’s data estate and assess associated risks. By leveraging large language models (LLMs), it goes beyond traditional keyword-based analysis to understand the purpose and context of content, enabling more accurate risk identification and actionable insights.

This message is associated with Roadmap ID 542188.

[When this will happen:]

• Public Preview (Worldwide): Rollout begins mid-December 2025 and completes by late December 2026.
• General Availability (Worldwide): Rollout begins late May 2026 (previously mid-March) and completes by end of May 2026 (previously late March).

[How this affects your organization:]

Who is affected: Admins managing data security and compliance in Microsoft Purview.

What will happen:

• A new Data Security Posture Agent will be available in Microsoft Purview under the Explore Agent tab.



• The agent uses LLM-powered natural language discovery to:
  • Search documents, emails, and messages for sensitive data.
  • Assess risks based on context and intent, not just keywords.
• Provides:
  • GenAI-generated summaries.

  

  • LLM-assisted job completion tasks.
  • Actionable recommendations to improve security posture.
• Default setting: The feature requires admin setup; it is not enabled automatically.

[What you can do to prepare:]

• Set up the agent in Microsoft Purview > Explore Agent using the required admin roles.
• Review your organization’s data security policies and ensure admins have appropriate permissions.
• Communicate this change to your security and compliance teams.

Learn more: 

• Security Copilot Agents in Microsoft Purview overview (preview) | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

Updated March 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To help provide additional transparency about what content has been generated or altered by using AI in Microsoft 365, Microsoft is providing you with a policy setting that visually designates when content, such as video or audio content, is generated or altered by using AI. This policy setting controls your organization’s option to add a visual or audio watermark to video and audio content that your users generate or alter by using AI in Microsoft 365.

To turn on watermarks for video and audio content that your users generate or alter by using AI in Microsoft 365, you need to use the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy. This policy is available only in Cloud Policy service for Microsoft 365. 

Note: Watermarks are not turned on unless you set the policy to Enabled. Your organization is always responsible for following the Microsoft Enterprise AI Services Code of Conduct, including not generating or sharing deceptive AI content. 

This change is associated with Microsoft 365 Roadmap ID: 547831.

[When this will happen]

General Availability (Worldwide): We anticipate that this policy will be available in Cloud Policy by late March 2026 (previously mid-March).

[How this will affect your organization]

Users that generate or alter video and audio content by using AI in Microsoft 365

What will happen

If you set the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy to Enabled in Cloud Policy, a visual or audio watermark is added to video and audio content that is generated or altered by using AI in Microsoft 365. Here are two examples:

• A visual watermark is added to a video generated with Clipchamp.
• An audio watermark is added to an audio overview generated by Copilot from a Word document.

• This policy doesn’t affect images generated or altered by using AI in Microsoft 365.
• Instead, your users will be able to turn on watermarks for images by going to Settings & Privacy > Privacy at https://myaccount.microsoft.com. We anticipate this capability will be available in the second half of February 2026. 

[What you need to do to prepare]

Updated March 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re improving meet now channel meetings in Microsoft Teams by reducing automatic meeting updates in channel conversations. This change helps keep channels cleaner and focused on real user replies, while meeting details remain accessible when you open the meeting thread.

[When this will happen:]

• Targeted Release: Rolling out mid-March 2026, expected to complete by late March 2026 (previously early April).
• General Availability (Worldwide): Rolling out late March 2026 (previously early April), expected to complete by mid-April 2026.
• General Availability (GCC, GCCHigh, DoD): Rolling out late April 2026, expected to complete by mid-May 2026.

[How this affects your organization:]

Who is affected: All Microsoft Teams users participating in meet now channel meetings.

What will happen:

• Channel conversations will show fewer automatic meeting messages.
  • Only a single “Meeting started” message will appear when a Meet now meeting begins.
  • Other automatic updates (such as meeting end or recording updates) will appear inside the meeting thread, not as additional channel messages.
• Reply counts will reflect people’s replies, not automatic system messages.
• Meeting details, join options, and recaps remain available by opening the meeting thread.
• No admin configuration changes are required; the feature is enabled by default.

[What you can do to prepare:]

• No action is required. This update will roll out automatically.
• Optional: Communicate this change to helpdesk staff to reduce potential confusion.
• For more information on channel meetings, visit: Meetings in Teams.

No compliance considerations identified, review as appropriate for your organization.

Updated March 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re enhancing Microsoft 365 Copilot Chat by enabling users to draft, edit, and send Outlook email directly within Copilot Chat. When Microsoft 365 Copilot identifies an email‑writing intent, it will open an embedded Outlook compose form. This improvement reduces context switching and streamlines everyday communication workflows.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in early May 2026 (previously late March) and is expected to complete by early June 2026 (previously late April).

[How this will affect your organization]

Who is affected

• Users licensed for Microsoft 365 Copilot
• Users with Exchange Online mailboxes
• Users accessing Copilot Chat on desktop (“big screen”)

What will happen

• When users ask Copilot to draft an email, an embedded Outlook compose form will appear directly within Copilot Chat: 

  

• Users will be able to:
  • Edit the email content
  • Modify recipients
  • Send the email from within Copilot Chat
  • Open the draft in Outlook to continue editing
• The feature will be on by default for all eligible users.
• Availability:
  • Available: Copilot Chat desktop app
  • Not available: Copilot Chat mobile app or chat sidebar
• Existing Outlook and Exchange Online policies—including DLP—continue to apply.
• No admin configuration changes or new controls are introduced.

Note: Access to this feature requires an active Microsoft 365 Copilot license.

[What you can do to prepare]

No action is required.

You may choose to:

• Inform your helpdesk and end users about this new email‑drafting experience in Copilot Chat.
• Update internal documentation if you describe Copilot Chat workflows.
• Review which users in your organization are licensed for Microsoft 365 Copilot.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

• Data request success rate – Monitor the percentage of successful data requests made by canvas apps and get notified when the rate drops below your defined threshold.
• Data request latency – Monitor how long data requests take in your canvas apps and get notified when latency exceeds your defined threshold.