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

het nieuws van Microsoft message center roadmap en blogs - KbWorks - SharePoint and Teams Specialist

15-November-2026 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.

This entire post was automated via Microsoft Flow
have fun reading!

Items from the MessageCenter in Microsoft 365

(Updated) Microsoft 365 Copilot: Copilot Pages and Notebooks Creation in OneDrive
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1449182
Status:planForChange

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

[What and why]

We’re changing where newly created Copilot Pages are stored. Going forward, Copilot Pages created in Copilot Chat, the Microsoft 365 Copilot app, and new Copilot Notebooks will be stored in OneDrive for Business instead of their current location.

This change enables organizations to manage newly created Copilot Pages using existing OneDrive for Business governance, compliance, data protection, retention, and lifecycle management capabilities.

[Rollout schedule]

  • General Availability (Worldwide): Beginning in mid-October 2026 (previously mid-August) and expected to complete by late November 2026 (previously late September)
  • General Availability (GCC, GCC High, and DoD): Beginning in mid-November 2026 (previously mid-September) and expected to complete by mid-December 2026 (previously early December)

[Impact on your organization]

Who is affected

Users who create Copilot Pages in:

  • Copilot Chat
  • Microsoft 365 Copilot app
  • Copilot Notebooks

Microsoft 365 administrators responsible for governance, compliance, retention, and content management

Platforms and services

  • Microsoft 365 Copilot
  • Copilot Chat
  • Copilot Notebooks
  • OneDrive for Business
  • Microsoft Purview compliance solutions

What will happen

After rollout:

  • Newly created Copilot Pages will be stored in users’ OneDrive for Business.
  • New Copilot Pages will appear alongside other OneDrive files, such as Word, Excel, and PowerPoint documents.
  • New Copilot Notebooks and artifacts created within them will appear alongside other OneDrive files, such as Word, Excel, and PowerPoint documents.
  • Existing OneDrive governance, compliance, data protection, retention, lifecycle management, reporting, and investigation capabilities will apply to newly created Copilot Pages.

In addition to all existing governance and management capabilities, the following additional OneDrive for Business capabilities will apply to newly created Copilot Pages:

Compliance and legal

  • Standard file path-based eDiscovery
  • Retention labels with record locking
  • Information Barriers
  • Compliance Boundaries

Data protection

  • Data Loss Prevention (DLP) policies and mitigation workflows
  • Third-party governance solutions that support OneDrive content

Lifecycle management

  • Retention and lifecycle policies
  • Existing departed-user workflows for OneDrive content

Monitoring and oversight

  • OneDrive storage reporting
  • Administrative investigations of content stored in OneDrive

Unaffected files

  • Existing Copilot Pages will remain in their current location and will not be migrated as part of this change.
  • Existing Copilot Notebooks will continue to store all newly created pages in SharePoint Embedded. Only Copilot Notebooks created after this change will store pages in OneDrive. 
  • Loop workspaces are not affected and will continue to use their current storage location.

IT Admin controls

  • If your organization has set Create and view Copilot Pages and Copilot Notebooks to Disabled, that setting will continue to be honored after this change.
  • This admin control is planned for future retirement. Microsoft will provide additional communication and transition guidance before the setting is retired.

[Action required and recommendations]

No action is required for the rollout.

We recommend that administrators:

  • Review existing DLP, retention, and compliance policies that apply to OneDrive for Business.
  • Verify that any third-party governance or eDiscovery solutions are configured to monitor OneDrive content as appropriate.
  • Update internal documentation and governance guidance for AI-generated content.
  • Communicate to users that newly created Copilot Pages will be stored in their OneDrive for Business.

[Compliance considerations]

QuestionAnswer
Does this change alter where customer data is stored?Yes. Newly created Copilot Pages will be stored in OneDrive for Business instead of their previous storage location.
Does this change affect compliance and governance capabilities?Yes. Newly created Copilot Pages will be subject to OneDrive for Business compliance capabilities, including eDiscovery, retention labels with record locking, Information Barriers, and Compliance Boundaries.
Does this change affect data protection controls?Yes. Existing OneDrive for Business data protection controls, including Data Loss Prevention (DLP) policies and supported third-party governance solutions, can be applied to newly created Copilot Pages.
Does this change affect lifecycle management and retention processes?Yes. Existing OneDrive for Business retention policies, lifecycle management capabilities, and departed-user workflows will apply to newly created Copilot Pages.
Does this change affect how administrators monitor or investigate content?Yes. Administrators will be able to use standard OneDrive for Business reporting, monitoring, and investigation capabilities for newly created Copilot Pages.
(Updated) Microsoft Purview: Adaptive scopes add lifecycle status evaluation controls for recipients and site owners
Category:Microsoft Purview
Nummer:MC1450128
Status:stayInformed

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

[What and why]

Microsoft Purview is introducing lifecycle status evaluation controls for adaptive scopes. This update gives administrators explicit control over whether active, inactive, and soft-deleted recipients and site owners are included in adaptive scope membership.

With this change, newly created adaptive scopes will evaluate only active recipients and site owners by default. Administrators can configure adaptive scopes to include inactive and/or soft-deleted recipients and site owners when needed.

This update also adds support for ISO 8601 duration values for selected date attributes in the adaptive scope advanced query builder.

This message is associated with Microsoft 365 Roadmap ID 568785.

[Rollout schedule]

  • Public Preview: Beginning in December 2026 (previously mid-September) and expected to complete in December 2026 (previously early October)
  • General Availability (Worldwide): Beginning in April 2027 (previously mid-October 2026) and expected to complete in April 2027 (previously mid-November 2026)

[Impact on your organization]

Who is affected

  • Microsoft Purview administrators who create or manage adaptive scopes.
  • Organizations that use adaptive scopes for Microsoft Purview policy targeting.

Platforms and services

  • Microsoft Purview
  • Adaptive Scopes

What will happen

Existing adaptive scopes will continue to function as they do today and will not be automatically modified as part of this rollout.

For newly created adaptive scopes:

  • Active recipients and site owners will be evaluated by default.
  • Inactive and soft-deleted recipients or site owners will not be included unless explicitly configured by an administrator.

21547 - KbWorks - SharePoint and Teams Specialist

Administrators will also have the option to update existing adaptive scopes to use explicit lifecycle status evaluation criteria for recipients and site owners.

Additionally, adaptive scopes will support ISO 8601 duration values for certain date-based attributes in the advanced query builder.

[Action required and recommendations]

No action is required before rollout.

We recommend that administrators:

  • Review current adaptive scope configurations and governance requirements.
  • Determine whether inactive or soft-deleted recipients and site owners should be included in future adaptive scope definitions.
  • Update adaptive scope creation processes and documentation, if applicable, to account for the new lifecycle status settings.

Learn more

[Compliance considerations]

No compliance considerations have been identified.

Release Planner Retirement: D365, Power Platform, and Dataverse Move to AI at Work
Category:Dynamics 365 Apps Power Apps Microsoft Power Automate Microsoft Dataverse Power Platform
Nummer:MC1461529
Status:planForChange
Release Planner is now retired. To stay informed about upcoming capabilities and prepare your organization for feature rollout and adoption, use the resources shared below. To view product availability for Dynamics 365, Power Platform and Copilot Studio, visit the new Learn page at https://aka.ms/d365-product-availability.


Starting this fall, Dynamics 365, Power Platform, and Dataverse roadmap content is joining the AI at Work roadmap, giving customers a single destination to discover upcoming capabilities, track rollout progress, and plan adoption across Microsoft’s business applications, productivity, and AI portfolio.

As part of this transition, Release Planner will retire on November 15, 2026. Microsoft is also retiring the twice-yearly release wave communication model in favor of continuous roadmap disclosure and change communications. New capabilities will be published to the AI at Work roadmap as they become committed and ready to share, providing a more current and comprehensive view of upcoming innovation.

When this will happen
  • September 2026: New Dynamics 365, Power Platform, and Dataverse roadmap items begin publishing directly to the AI at Work roadmap.
  • Fall 2026: Existing roadmap items with Public Preview or General Availability dates on or after June 1, 2026 transition from Release Planner to the AI at Work roadmap.
  • By November 15, 2026: Release Planner retires. The AI at Work roadmap becomes Microsoft’s primary destination for public roadmap information.
How this affects your organization

If your organization uses Release Planner, Release Plans on Microsoft Learn, or release wave announcements for roadmap planning, you will need to transition to the AI at Work roadmap.

Key changes include:

  • Release Planner will retire on November 15, 2026.
  • New Release Plans will no longer be published on Microsoft Learn beginning in September 2026. Existing Release Plans will remain available for historical reference.
  • The September 2026 Release Wave 2 announcement will not occur because release wave communications are being retired.
  • Roadmap information will be published continuously rather than grouped into twice-yearly release wave announcements.
  • Roadmap content will be available through filtering, CSV export, RSS subscriptions, and the Release Communications MCP Server pulls roadmap information directly into your own AI tools and workflows.
  • Personalized saved views from My Release Plans will not migrate to the AI at Work roadmap.
What is not changing

This transition changes how Microsoft communicates roadmap information. It does not change how products are built, released, or deployed.

The following remain unchanged:

  • Product release schedules
  • Deployment and rollout processes
  • Upgrade planning and support lifecycles
  • Preview and testing programs
  • Message Center notifications, which remain the authoritative source for tenant-specific communications
  • Microsoft Learn as the home for product documentation and implementation guidance
What you can do to prepare
  • In September, begin using the AI at Work roadmap as your primary destination for roadmap planning.
  • Review internal processes, documentation, bookmarks, and communications that currently reference Release Planner, Release Plans, or release wave announcements.
  • Configure roadmap filters, RSS subscriptions, and CSV exports to support your organization’s planning processes.
  • Evaluate the Release Communications MCP Server if your organization integrates roadmap data into planning workflows or AI tools.
  • Continue using Message Center for tenant-specific change notifications and deployment communications.
Additional information

The AI at Work roadmap provides a single destination for roadmap information across Microsoft business applications, productivity experiences, Copilot, agents, and AI solutions. Organizations are encouraged to familiarize themselves with the roadmap’s filtering, export, RSS, and MCP capabilities before September 2026 publishing begins.

(Updated) Microsoft Teams: Video sharing from OneDrive in Teams events
Category:Microsoft Teams
Nummer:MC1506734
Status:planForChange

Updated November 13, 2026: We have updated the content. If you are a tenant in a GCCH or DoD environment, you can safely ignore this message as you are not impacted. Thank you for your patience. 

[What and why]

Microsoft Teams will soon support sharing video directly from OneDrive during Teams events that are optimized for scale (previously called town halls). Organizers and producers using Manage what attendees see can load videos from OneDrive and present them on stage without screen sharing a local media player or embedding videos in PowerPoint. This improvement provides smoother, higher-quality video playback for attendees and simplifies event production through built-in video playback controls.

[Rollout schedule]

  • Targeted Release (Worldwide): Rollout will begin in mid-November 2026 (previously early November) and end in early December 2026.
  • General Availability (Worldwide, GCC): Rollout will begin in early December 2026 and is expected to complete by early December 2026.

[Impact on your organization]

Who is affected

  • Teams event organizers and producers using events configured with Manage what attendees see.

Platforms and services

  • Microsoft Teams
  • OneDrive
  • Teams events

What will happen

  • Organizers and producers will be able to select and share videos stored in OneDrive directly within Teams events configured with Manage what attendees see and will have access to built-in controls to start and pause video playback during events.
  • Videos can be presented on stage without screen sharing a local media player or embedding videos into a PowerPoint presentation.
  • Attendees will experience smoother and higher-quality video playback.

[Action required and recommendations]

No action is required. We recommend that you:

  • Inform Teams event organizers and producers that they can share videos directly from OneDrive in Teams events configured with Manage what attendees see.
  • Ensure that organizers and producers store videos in OneDrive with the appropriate permissions before using them in events.
  • Review and update internal event production guidance that recommends screen sharing locally played videos or embedding videos in PowerPoint.

[Learn more]

We will update this post with new documentation.

[Compliance considerations]

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

(Updated) Microsoft Purview | Information Protection: Sensitivity labels for Microsoft Entra security groups
Category:Microsoft 365 suite Microsoft Purview
Nummer:MC1508238
Status:stayInformed

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

[What and why]

Microsoft Purview is introducing sensitivity labels for Microsoft Entra cloud security groups. This capability extends label-based protection currently available for Microsoft 365 groups and SharePoint sites to cloud security groups.

With this change, organizations can apply published Microsoft Purview sensitivity labels directly to security groups and automatically enforce membership and guest access policies when groups are created or labeled. This helps administrators apply governance policies consistently across group types, reduce the risk of oversharing, and support controlled self-service group creation.

This message is associated with Microsoft 365 Roadmap ID 568217.

[Rollout schedule]

  • General Availability (Worldwide): Beginning in mid-January 2027 (previously mid-November 2026) and expected to complete in mid-January 2027 (previously late November 2026)

[Impact on your organization]

Who is affected

  • Microsoft Entra administrators
  • Microsoft Purview administrators
  • Organizations that use or plan to use sensitivity labels to govern access to Microsoft Entra security groups

Platforms and services

  • Microsoft Purview
  • Microsoft Entra ID
  • Microsoft Entra admin center
  • Azure portal
  • Microsoft Graph
  • PowerShell

What will happen

  • Administrators will be able to apply published Microsoft Purview sensitivity labels to cloud security groups during group creation or after a group has been created.
  • Labels can be assigned through the Microsoft Entra admin center, Azure portal, PowerShell, or Microsoft Graph.
  • Existing sensitivity label functionality for Microsoft 365 groups will remain unchanged.
  • Once a sensitivity label is applied to a security group, the label cannot currently be changed or removed. Support for changing assigned labels will be introduced in a future update.
  • Sensitivity labels can be used to enforce organizational membership and guest access policies for security groups.

[Action required and recommendations]

No action is required to receive this change.

  • To use sensitivity labels with Microsoft Entra security groups after rollout:
  • Confirm that your organization has eligible licensing, such as Microsoft 365 E3 or Microsoft 365 E5, which includes Microsoft Entra ID P1.
  • In the Microsoft Purview portal, publish the sensitivity labels you want to use with the Groups & Sites scope enabled.
  • Allow up to 24 hours for labels to synchronize and become available in Microsoft Entra ID.
  • Enable sensitivity label support for cloud security groups in your tenant settings.
  • If sensitivity labels are already enabled for Microsoft 365 groups, note that cloud security groups require a separate configuration setting and must be enabled independently.

Consider reviewing your existing sensitivity label policies and governance processes before enabling this feature, particularly because assigned labels cannot currently be changed or removed from security groups.

Learn more

[Compliance considerations]

QuestionAnswer
Does the change modify or add to Purview-related capabilities?Yes. This update extends Microsoft Purview sensitivity labels to Microsoft Entra security groups, adding a new governance and protection capability for this group type.
Does the change include an admin control?Yes. Administrators must enable sensitivity label support for cloud security groups and manage label publication and assignment through Microsoft Purview and Microsoft Entra administrative controls.
Does the change alter how admins manage or demonstrate compliance activities?Yes. Administrators can use sensitivity labels on cloud security groups to apply and enforce access governance policies, expanding the scope of compliance controls available within Microsoft Purview.
Dynamics 365 Field Service – Preserve actual booking End Time when completion is recorded later
Category:Dynamics 365 Apps
Nummer:MC1552365
Status:stayInformed
We are announcing the ability to Preserve actual booking End Time when completion is recorded later in Dynamics 365 Field Service. This feature will reach public preview on November 22, 2026.

How does this affect me?
This feature allows Field Service administrators to choose whether completion by the booked resource automatically changes the booking End Time. Admins complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred.

Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update.
  • With the setting set to Yes, which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Duration.
  • With the setting set to No, Field Service preserves End Time and Duration when the booked resource completes the booking unless the completion request explicitly supplies a different End Time.
  • Completion by another user or an integration continues to preserve End Time for either setting value.
  • When the setting is No and the booked resource completes the booking, Field Service uses the retained or supplied End Time as the effective Completed booking timestamp. This keeps timestamp-derived booking journals and automatic time entries aligned with the recorded work end. Dataverse audit fields continue to show when the completion was submitted.
The setting applies to future completion transitions and does not rewrite historical bookings. It does not change the booking-status lifecycle, invoice generation, or the existing Work Order Completed On calculation, which continues to use the latest eligible booking End Time.

What action do I need to take?
This message is for awareness, and no action is required.
Microsoft 365 Copilot: Page context for open tabs in the Copilot desktop app built-in browser
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1552386
Status:stayInformed

[What and why]

Copilot in the desktop app will be able to use content from open webpage tabs in the app’s built-in browser as page context. Users will be able to ask questions or request summaries for a single tab or across multiple tabs, which helps with multi-tab workflows. Page context will be scoped to the current conversation and will apply only when the built-in browser is enabled. 

Availability is limited to the Microsoft Copilot desktop app.

[Rollout schedule]

  • General availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete the rollout in late November 2026.

[Impact on your organization]

Who is affected

  • Users of the Copilot desktop app in organizations where the built-in browser is enabled
  • Admins who manage the Copilot desktop app and its built-in browser

Platforms and services

  • Copilot desktop app (built-in browser)
  • Microsoft 365 Copilot

What will happen

  • When the built-in browser is enabled, Copilot will be able to use content from open webpage tabs in that browser to answer questions and provide summaries: 

22488 1 - KbWorks - SharePoint and Teams Specialist

  • Users will be able to ask about a single tab or across multiple tabs: 

22488 2 - KbWorks - SharePoint and Teams Specialist

  • Page context will be limited to the current conversation.
  • If the built-in browser is disabled, this feature will not be active and will have no impact.

[Action required and recommendations]

No action is required. We recommend that you:

  • Confirm whether the Copilot desktop app built-in browser is enabled for your organization.
  • Review the governance settings for in-app browsing and page context use.
  • Validate the expected behavior with pilot users.
  • Tell users and helpdesk staff that page context is limited to the current conversation.

[Compliance considerations]

QuestionAnswer
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with customer data?Yes. Copilot uses content from open webpage tabs in the built-in browser as context for answers and summaries.
Does the change give users a new way of interacting with generative AI?Yes. Users can ask questions or request summaries for one tab or across multiple tabs.
Retired: Microsoft Defender for Identity classic alerts (Remote code execution attempt and pass-the-hash)
Category:Microsoft Defender XDR
Nummer:MC1552387
Status:planForChange

[What and Why:]

Microsoft Defender for Identity (MDI) is retiring two classic alerts at the end of November 2026: Remote code execution attempt (RCE) and Suspected identity theft (pass-the-hash). This update aligns detection workflows with current Microsoft Defender XDR and endpoint monitoring capabilities.

[Rollout Schedule:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late November 2026 and expect to complete by late November 2026.

[Impact on Your Organization:]

Who is affected:

– Security teams using classic MDI alert workflows for RCE and pass-the-hash scenarios.

Platforms/Services:

– Microsoft Defender for Identity

– Microsoft Defender XDR services

What will happen:

– The two classic alerts will no longer be available after rollout completes.

– RCE activity can continue to be monitored with a custom detection rule in Advanced Hunting.

– Pass-the-hash monitoring should continue through Microsoft Defender for Endpoint on onboarded devices.

[Action Required/Recommendations:]

Before the end of November 2026:

– Create an Advanced Hunting custom detection rule for RCE scenarios using the published query.

– Confirm pass-the-hash detection coverage through Defender for Endpoint on onboarded devices.

– Review guidance: MDI classic alerts documentation.

– Use the published query: RCE custom detection query.

[Compliance considerations:]

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

Microsoft 365 Copilot: Workforce Intelligence plugin available in Copilot Cowork
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1552389
Status:stayInformed

[What and why]

We’re adding the Workforce Intelligence plugin to Microsoft Copilot Cowork and other supported plugin surfaces for tenants enrolled in Frontier. The plugin helps leaders and managers use natural language to explore their organization’s structure, workforce composition, and skills, making it easier to prepare for organizational discussions and identify team-level learning opportunities.

[Rollout schedule]

  • Public Preview (Frontier Worldwide): Starting November 16, 2026

[Impact on your organization]

Who is affected

  • Users with a Microsoft 365 Copilot license and access to Copilot Cowork in organizations where an admin has opted into the Frontier program, configured Workforce Insights, and made the plugin available

Note: Skills insights also require appropriate People Skills licensing and admin enablement.

Platforms and services

  • Microsoft 365 Copilot
  • Microsoft Copilot Cowork
  • Workforce Insights agent
  • Workforce Intelligence plugin
  • People Skills

What will happen

  • Explore organizational structure: Leaders and managers can ask questions about headcount, roles, functions, reporting relationships, direct reports, management layers, and locations.
  • Understand skills and learning opportunities: Users can explore collective strengths, identify opportunities for team-level learning and knowledge sharing, and assess the completeness of skills records.
  • Prepare summaries and dashboards: Users can organize workforce findings into summaries or dashboards for leadership discussions.
  • Access the plugin: Users can find the Workforce Intelligence plugin in Copilot Cowork by selecting + > Customize and searching for the plugin. Once the plugin is available and enabled, Cowork automatically selects the appropriate skill based on the conversation, so users don’t need to select a skill before asking a question.
  • Existing data permissions remain unchanged: Installing the plugin does not grant additional access to workforce data. Responses depend on user permissions, connected data sources, data freshness, and admin-configured governance labels and access policies.
  • Admin configuration remains separate: Admins continue to configure organizational terminology, business context, and attribute descriptions in the Workforce Insights agent. These definitions do not modify workforce records or grant additional access.
  • Intended use and limitations: The plugin supports organizational discussions and team-level learning. It is not designed for monitoring employee behavior, managing performance, ranking employees or managers, or making employment decisions. It does not provide historical trends, forecasting, or attrition analysis.
  • Dashboard sharing: Creating a dashboard does not automatically share, publish, or schedule it for refresh.

Example prompt:

“Help me review my organization for our next leadership discussion. Focus on team sizes, management layers, locations, and opportunities for team-level learning.”

[Action required and recommendations]

To prepare for this feature, admins should:

  • Verify prerequisites: Confirm that intended users have Microsoft 365 Copilot licenses and Cowork access, your organization has opted into the Frontier program, and Workforce Insights is configured.
  • Enable skills insights (optional): Verify appropriate People Skills licensing and enablement. 
  • Make the plugin available: Determine which leaders and managers should have access to the plugin and make it available to them. You can also optionally deploy it automatically to the intended users.
  • Review data governance: Verify access policies and governance labels to ensure users can access only permitted workforce data.
  • Configure organizational context: Define company-specific terminology and attribute descriptions in the Workforce Insights agent to help ensure responses reflect your organization’s definitions.
  • Communicate with users: Explain the plugin’s intended uses and limitations. Remind users that AI-generated responses may be inaccurate or incomplete and should be reviewed before sharing.

Learn more

[Compliance considerations]

The Workforce Intelligence plugin introduces AI-powered workforce insights through Copilot Cowork while respecting existing data access permissions and organizational governance policies.

  • The plugin uses organizational and skills data that users are authorized to access.
  • Installing the plugin does not grant additional access to workforce data or change existing access policies.
  • Admins control plugin availability and configure organizational context through Workforce Insights.
  • AI-generated workforce insights should be reviewed before sharing and should not be used for employee performance evaluation or employment decisions.
Microsoft Teams: Manage call groups on Mobile
Category:Microsoft Teams
Nummer:MC1552390
Status:stayInformed

[What and Why:]

Call groups let colleagues answer calls on a user’s behalf, but changing one today means going to the desktop. When availability changes, for example when a backup contact is out or a new teammate needs to cover, users often notice while they are away from their desks and cannot update their call group from the phone where they take their calls.

We’re introducing the ability to create and manage a call group directly from Microsoft Teams on Mobile. Users can add or remove members, configure how the group should ring, and choose to forward or simultaneously ring incoming calls to their call group. This makes it easier for on the go users to manage how their calls are handled without needing to reach desktop.

From Settings, users can open Calling and select Manage call group to view their current call group or create a new one.

Once the call group is set up, users can forward their calls to the group or ring the group at the same time as their own devices, using the call handling options in Calling settings.

[Rollout Schedule:]

General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid December 2026.

[Impact on Your Organization:]

Once available, eligible users will see Manage call group in the Calling settings of Teams on Mobile.

Users will be able to:

  • View their current call group and its members.
  • Create a call group if they don’t have one.
  • Add or remove members.
  • Choose how the group rings: Everyone at once or In the order below.
  • Reorder members when the ring order matters.
  • Forward calls to the call group or have the group ring alongside their own devices.

Changes made on Mobile apply to the same call group settings that users manage on desktop. Mobile adds a new way to manage them and does not introduce a separate call group.

This feature is available to users with a Teams Phone license and uses the existing calling policy that controls call groups. If call groups are turned off for a user in their calling policy, they won’t be able to use the feature on Mobile.

[Action Required/Recommendations:]

No admin action is required before rollout.

Manage call groups on Mobile uses the same controls as the desktop experience.

We recommend that you:

  • Review the calling policy assigned to the users who should be able to manage call groups, and confirm that call groups are allowed.
  • Confirm that those users have a Teams Phone license.
  • Inform your users, particularly those who rely on call groups for backup coverage and often work away from their desk uses Mobile.

[Compliance considerations:]

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

Microsoft Teams: Copilot in the Queues app on Mobile
Category:Microsoft Teams Microsoft Copilot (Microsoft 365)
Nummer:MC1552391
Status:stayInformed

[What and Why:]

After a customer call, calling reps or supervisor leads often need to know what was discussed. They might be following up on a missed call, picking up a conversation a colleague handled, or checking how a call went. Getting those details usually means going through the call itself, which takes time, especially on Mobile.

We’re introducing Copilot in the Queues app on Microsoft Teams Mobile. From shared call history, calling reps and supervisor leads can ask Copilot questions about a past call and quickly surface relevant information and insights from the conversation. This helps them get up to speed and take the next step without having to review the entire call.

[Rollout Schedule:]

General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid December 2026.

Targeted Release (Worldwide): We will begin rolling out on late November 2026 and expect to complete by early December 2026.

[Impact on Your Organization:]

Once available, eligible users will be able to use Copilot on calls in shared call history in the Queues app on Mobile.

Users will be able to:

  • Open Copilot from a recorded call in shared call history.
  • Ask questions about the call and get relevant information and insights from the conversation.
  • Understand a customer conversation and decide on a follow-up without reviewing the full call.

Copilot is available for recorded call queue calls, as it is on desktop.

 Users need a Teams Premium license to use the Queues app and a Microsoft 365 Copilot license to use Copilot.

This feature does not change how call recordings are created, stored, or accessed. Copilot in the Queues app is already available on desktop, and Mobile brings the same capability to the phone.

[Action Required/Recommendations:]

No admin action is required before rollout.

We recommend that you:

  • Confirm that automatic recording is turned on for the call queues where you want users to use Copilot.
  • Review Microsoft 365 Copilot and Teams Premium license assignments for the users who will use the feature.

[Compliance considerations:]

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

Microsoft Teams: Automatic recording indicator for call queue calls on Mobile
Category:Microsoft Teams
Nummer:MC1552392
Status:stayInformed

[What and Why:]

When an organization automatically records its call queue calls, calling reps need to know at a glance that the call is being recorded and that this is controlled by the organization.

For call queue calls that are automatically recorded by the organization, Microsoft Teams on Mobile will clearly indicate that recording and transcription have started automatically and cannot be stopped. This gives calling reps a clear and accurate picture of the call and provides a consistent experience across desktop and Mobile. 

[Rollout Schedule:]

General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid-December 2026.

[Impact on Your Organization:]

Once available, calling reps who answer call queue calls that are automatically recorded by your organization will see the updated message in the recording banner in Teams on Mobile.

What will change:

  • The banner will state that recording started automatically and cannot be stopped.
  • The previous wording, which implied the user had started the recording, will no longer appear on these calls.

This change updates only the banner text. It applies to call queue calls that your organization records automatically. Other calls and recordings started manually by users are not affected. Existing consent text, the privacy link, and the AI notice in the banner stay the same.

This feature does not change how recordings are started, stored, or accessed. Automatic recording for call queues is already available on desktop and is configured by admins in Teams admin center. Mobile now shows the same recording state.

[Action Required/Recommendations:]

No admin action is required before rollout. We recommend informing your calling reps about the updated banner, particularly those who answer queue calls on their mobile devices, so they know automatic recording is controlled by the organization and cannot be stopped by the rep.

[Compliance considerations:]

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

Microsoft Viva Engage: Retirement of Teams town hall event creation
Category:Microsoft Viva
Nummer:MC1552394
Status:planForChange

[What and why]

We are retiring the option to create Microsoft Teams town hall events from Viva Engage. Starting December 7, 2026, users will no longer be able to create new Teams town hall events from Engage. Organizers should use the new Events experience in Viva Engage or Microsoft Teams to create events.

[Rollout schedule]

  • December 7, 2026: Users will no longer be able to create Teams town hall events from Viva Engage. Previously scheduled events will run as planned.

[Impact on your organization]

Who is affected

  • Event organizers who create Teams town hall events from Viva Engage.
  • Communications teams responsible for organizing events.

Platforms and services

  • Microsoft Viva Engage
  • Microsoft Teams

What will happen

  • Users will no longer be able to create new Teams town hall events from Viva Engage. Previously scheduled events will continue to run as planned.
  • Organizers will need to use the new Events experience to create events:
    • In Viva Engage: Create town hall, community town hall, or AMA events using Engage events.
    • In Microsoft Teams: Create town hall events directly in Teams.

[Action required and recommendations]

We recommend that you:

  • Inform event organizers and communications teams about this change before December 7, 2026.
  • Create new and upcoming events using the new Events experience in Viva Engage or Microsoft Teams.
  • Update internal documentation, training materials, and guidance that reference creating Teams town hall events from Viva Engage.

[Learn more]

Microsoft SharePoint: Resources web part and Announcements capabilities expand to all sites
Category:SharePoint Online
Nummer:MC1552397
Status:stayInformed

[What and why]

We are expanding the Resources web part and Announcements capabilities to all SharePoint sites, making it easier for organizations to share important links and updates with employees. Site owners will have more flexibility to curate relevant resources and communicate important information.

[Rollout schedule]

  • General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to complete by late November 2026.
  • General Availability (GCC, DoD): Rollout will begin in mid-December 2026 and is expected to complete by late December 2026.

[Impact on your organization]

Who is affected

  • SharePoint site owners and users.

Platforms and services

  • Microsoft SharePoint

What will happen

  • Resources web part: Site owners can curate important links on any SharePoint site and use audience targeting to display relevant resources to specific groups of users.

resources web part

  • Announcements: Site owners can create announcements on any SharePoint site, not just home sites. Announcements created on organizational news sites will trigger notifications.

announcements web part

[Action required and recommendations]

No admin action is required. These capabilities will roll out automatically to all customers.

[Learn more]

[Compliance considerations]

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

Copilot Studio – Credit visibility in run view & monitor in workflows
Category:Microsoft Copilot (Power Platform)
Nummer:MC1552503
Status:stayInformed
We are announcing Copilot Credit visibility in run view and monitors in workflows in Copilot Studio. This feature reached general availability on November 11, 2026.

How does this affect me?
Makers will now be able to see how many Copilot Credits each workflow run consumes directly from the workflow designer. This allows makers to predict and control the cost of automation before scaling it to production, and to quickly identify which steps are driving consumption.

This feature brings the following improvements:
  • Run Details: A credits pill shows the estimated credits per run and per step.
  • Monitor tab: You can now view credits used across runs to understand and predict costs.
  • Capacity awareness: A warning banner will appear when credit limits are approaching or have been reached, and test runs will be blocked when credits are exhausted.
What action do I need to take?
This message is for awareness, and no action is required.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

Get The Paul Take

My no-fluff read on Microsoft 365, Teams, SharePoint and Copilot. Real lessons from real rollouts, and what I would actually do. Once every two weeks.

No spam. Unsubscribe anytime.