Microsoft Roadmap, messagecenter and blogs updates from 13-11-2026

Updated November 12, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

Microsoft Defender for Office 365 is introducing localization support for the default “Mark and notify” email template used in admin review and automated notification flows for user-reported messages.

This update ensures that users receive notification emails in their preferred language based on their Outlook settings, improving clarity and understanding of review outcomes. This helps improve engagement and supports stronger security practices.

This message is associated with Microsoft 365 Roadmap ID 557558.

[Rollout Schedule]

General Availability 

• Worldwide: Rollout begins in June 2026 and is expected to complete by end of September 2026 (previously late July).
• GCC, GCC High, DoD: Rollout begins in late November 2026 (previously mid-July) and is expected to complete by end of December 2026 (previously end of October).

[Impact on Your Organization]

Who is affected

• Organizations using Microsoft Defender for Office 365
• Admins and users participating in user-reported message workflows
• Applies only when the default notification template is used

Platforms/Services

• Microsoft Defender for Office 365
• Microsoft 365 Defender portal (web)
• Exchange Online

What will happen

• Default “Mark and notify” email templates will be localized.
• Notifications will be delivered in the user’s preferred language based on Outlook settings.
• Feature is enabled by default when auto-notification is turned on.
• Notifications will have consistent formatting and messaging across supported languages.
• No changes to message verdicts or classification logic.
• No changes to automated investigation behavior.
• No changes to custom notification templates configured by admins in the user reported settings page.
• Default ‘safe’ message template will also use softer, clearer wording while continuing to advise users to exercise caution:
  • This email doesn’t appear harmful. But you should always handle suspicious emails with caution.
  • The safe-message template will also advise users to:
    • Contact the sender through another channel to confirm the message’s validity.
    • Avoid links and attachments in unsolicited emails from unfamiliar senders.

Screenshot 1 – Before localization view: 

Screenshot 1 – Localized template view:

Screenshot 2 – Default safe message:

[Action Required/Recommendations]

No action is required.

You may consider the following:

• Inform users that notification emails may now appear in their preferred language.
• Review notification settings in Microsoft Defender: Settings > Email and collaboration > User reported settings.
• Update internal documentation or helpdesk guidance if this workflow is documented.

Learn more: Notify users about admin submitted messages to Microsoft – Use the Submissions page to submit suspected spam, phish, URLs, legitimate email getting blocked, and email attachments to Microsoft | Microsoft Defender for Office 365 | Microsoft Defender | Microsoft Learn

[Compliance considerations]

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

Updated November 12, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We are introducing a new Microsoft Teams Facilitator capability that proactively detects and resolves knowledge gaps during meetings. Facilitator can identify when participants ask questions or express uncertainty and retrieve and share relevant answers using web search in the meeting chat. This enhancement helps improve meeting productivity by reducing interruptions and enabling teams to stay focused on goals while accessing needed information. If a participant asks a factual question and no one responds, Facilitator can provide an answer directly in the meeting chat.

This message is associated with Microsoft 365 Roadmap ID 558341.

[Rollout Schedule]

• Targeted Release: Beginning early February 2027 (previously early December) and expected to complete mid-February 2027 (previously mid-December)
• General Availability (Worldwide): Beginning mid-February 2027 (previously mid-December) and expected to complete early March 2027 (previously mid-January)

[Impact on Your Organization]

Who is affected

• Users in Microsoft Teams meetings where Facilitator is enabled with Microsoft 365 Copilot (Premium)

Platforms/Services

• Microsoft Teams (meetings)
• Microsoft 365 Copilot

What will happen

• Facilitator will monitor meeting conversations in real time to detect implicit or explicit information needs.
• When a knowledge gap is identified, Facilitator performs a web search and posts a response in the meeting chat: 
• 
• Responses are infrequent in practice and typically occur less than once per meeting.
• Responses are limited to questions relevant to the meeting discussion based on agenda signals and conversational context.
• Facilitator must be manually added to the meeting and is not enabled by default.
• A user with a Microsoft 365 Copilot (Premium) license must enable Facilitator for the meeting. Other participants do not need to be licensed to receive responses.
• Admins can disable Facilitator at the tenant level. The feature depends on the Copilot web search setting. If web search is disabled, responses are not generated.
• Users can stop the behavior at any time by removing Facilitator from the meeting.
• The feature is supported in standard Teams meetings only and not supported in calls, webinars, or town halls.
• The experience is supported in meetings that include external or cross-tenant participants.

[Action Required/Recommendations]

No immediate action is required.

Recommended actions:

• Review your organization’s Copilot web search and Facilitator configuration settings to confirm alignment with your policies.
• Inform helpdesk and users about proactive Facilitator responses in meeting chats.
• Update internal documentation or training materials if you reference Teams meeting experiences.

[Compliance considerations]

Updated November 12, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why:]

Microsoft Teams is introducing enhancements for channel meetings to make it easier to schedule meetings in the right context and help teams discover relevant meetings across their channels.

Users will be able to create channel meetings directly from the Teams calendar and create and manage channel meetings from classic Outlook for Windows. Channel members will be able to more easily discover meetings associated with their channels, helping teams stay informed about upcoming discussions and participate in relevant conversations. Administrative assistants and delegates will also be able to schedule channel meetings on behalf of others while keeping meetings connected to the appropriate team and channel.

[Rollout Schedule:]

Public Preview (Worldwide): We will begin rolling out in mid-November 2026 (previously early November) and expect to complete by late November 2026.

General Availability (Worldwide): We will begin rolling out in late January 2027 (previously mid-December 2026) and expect to complete by late January 2027.

General Availability (GCC): We will begin rolling out in mid-December 2026 and expect to complete by late July 2027.

General Availability (GCC High): We will begin rolling out in mid-December 2026 and expect to complete by late August 2027.

General Availability (DoD): We will begin rolling out in mid-December 2026 and expect to complete by late September 2027.

[Impact on Your Organization:]

Users will have additional ways to create, manage, and discover channel meetings in Teams and classic Outlook for Windows. This can help meetings stay connected to the relevant team and channel context.

[Action Required/Recommendations:]

No admin action is required. You may want to inform users, meeting organizers, administrative assistants, and delegates about the enhanced channel meeting experience.

[Compliance considerations:]

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

[What and why]

We are updating scheduled prompts in Microsoft 365 Copilot to use native Copilot scheduling infrastructure instead of Power Platform. Users can continue scheduling one-time or recurring tasks using natural language, with Copilot executing tasks automatically and returning results to the associated conversation. The new experience operates independently of Power Platform, including where Power Automate is disabled, and processes and stores scheduled task data within the Microsoft 365 compliance boundary.

The existing Power Platform-based scheduled prompts experience will retire on December 31, 2026.

[Rollout schedule]

• Frontier/TAP: November 11, 2026
• Worldwide rollout: November 30 through December 31, 2026
• Retirement of Power Platform-based scheduled prompts: December 31, 2026

Rollout timing may change based on reliability and migration readiness.

[Impact on your organization]

Who is affected

• Users with a Microsoft 365 Copilot premium license who use scheduled tasks, subject to organizational controls

Platforms and services

• Microsoft 365 Copilot and Copilot Chat
• Tasks in the Microsoft 365 Copilot app
• Web and Windows desktop

What will happen

• Users can schedule one-time or recurring tasks that Copilot executes automatically, even when users are not present.
• Users can run, edit, pause, resume, or delete scheduled tasks, with limits of 10 active and 50 total schedules per user: 

• Tasks requiring user approval will pause until the user responds in the associated conversation.
• Users will manage Copilot Chat schedules from Tasks > Scheduled in the Microsoft 365 Copilot app.
• For 30 days after the Scheduled tab becomes available to a user, scheduled tasks will be accessible from both the existing shared-header More options (…) menu and Tasks > Scheduled. After this period, the existing menu entry will be removed.
• Responses from previously completed scheduled runs will remain available.
• Power Platform-based scheduled prompts will retire on December 31, 2026.

[Action required and recommendations]

We recommend that administrators:

• Notify users who rely on scheduled prompts about the transition.
• Advise affected users to recreate schedules that will not migrate automatically before December 31, 2026.
• Inform users that management of Copilot Chat scheduled tasks is moving to Tasks > Scheduled.
• Update internal documentation and helpdesk guidance.
• Review applicable Microsoft 365 Copilot controls and organizational policies.

No action is required to preserve responses from completed scheduled runs.

[Compliance considerations]

[What and why]

Microsoft 365 Copilot Workspaces (formerly Copilot Notebooks) is moving to an agentic chat experience. As part of this change, Researcher, Analyst, and Designer will no longer be available as standalone agent options within Copilot Workspaces.

Instead of selecting or switching between agents, users can describe what they need in plain language. Copilot will automatically apply the appropriate research, analysis, or design skills based on the request and the workspace content.

This change simplifies the user experience while preserving existing capabilities. Researcher, Analyst, and Designer will remain available as separate agents in the Microsoft 365 Copilot app for users who prefer working with a specific agent.

[Rollout schedule]

• Frontier preview: Rollout is planned to begin in December 2026. The completion date has not yet been determined.
• Rollout dates for general availability are still being finalized. We will provide additional information when available.

[Impact on your organization]

Who is affected

• Users of Microsoft 365 Copilot Workspaces who have access to the Frontier preview

Platforms and services

• Microsoft 365 Copilot Workspaces (formerly Copilot Notebooks)
• Microsoft 365 Copilot app

What will happen

• Standalone agent selection: Researcher, Analyst, and Designer will no longer appear as separate agent options within Copilot Workspaces.
• Agentic chat: Users can describe research, analysis, and design tasks in natural language. Copilot will automatically apply the appropriate skills based on the request and workspace content.
• No loss of capabilities: Research, analysis, and design capabilities will remain available within Copilot Workspaces.
• Simplified workflow: Users will no longer need to select or switch between agents when performing different tasks.
• Continued access to individual agents: Researcher, Analyst, and Designer will remain available as separate agents in the Microsoft 365 Copilot app.
• Default behavior: This change will apply automatically when it rolls out to your organization.

[Action required and recommendations]

No admin action is required. We recommend that you:

• Inform users that Researcher, Analyst, and Designer will no longer appear as separate agent options in Copilot Workspaces.
• Explain that users can describe their tasks directly in chat, and Copilot will apply the appropriate capabilities.
• Update internal training and support materials that instruct users to select specific agents within Copilot Workspaces.
• Direct users who prefer working with individual agents to Researcher, Analyst, and Designer in the Microsoft 365 Copilot app.
• Monitor Message center for additional rollout information.

[Compliance considerations]

This change introduces an agentic chat experience in Copilot Workspaces, allowing users to interact with research, analysis, and design capabilities through natural language rather than selecting individual agents.

Organizations should review this change as appropriate for their compliance requirements.

[What and why]

We are updating how the Who has access to the recording or transcript option appears for Microsoft Teams Events scheduling through the Events App including town halls and webinars. Currently, when AllowCloudRecording is set to false, this option does not appear for these events. After this change, the option will appear only when the applicable RecordingForTownhall or RecordingForWebinar setting in CsTeamsEventsPolicy is enabled.

[Rollout schedule]

• General Availability (Worldwide, GCC, GCC High, DoD): Beginning in early-November 2026 and expected to complete by mid-November 2026

[Impact on your organization]

Who is affected

• Microsoft Teams organizers of Events created via the Events App including town halls and webinars

Platforms and services

• Microsoft TeamsEvents created via the Events App including town halls and webinars

What will happen

The Who has access to the recording or transcript option will be based on the applicable RecordingForTownhall or RecordingForWebinar setting. It will no longer be based on the AllowCloudRecording setting.

[Action required and recommendations]

No action is required to enable this change.

We recommend updating your internal documentation to reflect this change.

[Compliance considerations]

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