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

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

21-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!

Office 365 Roadmap Updated: 2026-11-21

Additions : 8
Updates : 10

More Details At: www.roadmapwatch.com


New FeaturesCurrent Status
Work IQ: ListenIn Development
Dynamics 365 Human Resources: Streamline the employee offboarding experienceIn Development
Dynamics 365 Human Resources: Ask HR – conversational HR self-service grounded in your own worker recordIn Development
Exchange: Enable High Volume Email (HVE) for External RecipientsIn Development
Dynamics 365 Finance: Collection Coordinator SkillIn Development
Dynamics 365 Commerce: Update e-commerce integration with Adyen and introduce ACH and Pay by Bank payment methodsIn Development
Dynamics 365 Finance: B2B electronic invoicing in SpainIn Development
Planner: Tab support for shared and private channels in Microsoft Teams in GCC, GCC-H and DoDIn Development
 
Updated FeaturesCurrent StatusUpdate Type
Microsoft Teams: Call quality feedback surveys for Teams Rooms on AndroidRolling OutStatus
Microsoft Teams: AI-powered notes for in-person meetings with Facilitator in Teams Rooms on AndroidRolling OutStatus
Microsoft Edge: v.158 – Import Google account data anytime from SettingsLaunchedStatus, Title
Microsoft Edge: v.158 – Automatically unsubscribe users from notifications sent by scam and malicious sitesLaunchedStatus, Title
Microsoft Edge: v.158 – Inline Switching for WorkspacesLaunchedStatus, Title
Microsoft Teams: Invite attendees to registerRolling OutStatus
Microsoft Teams: Chat for organizers and presenters in structured meetings and webinars on Teams Rooms on AndroidRolling OutStatus
Microsoft Teams: PowerPoint Live support for webinars and structured meetings on Teams Rooms on AndroidRolling OutStatus
Microsoft 365: [Education] Assign Study and Learn in Teams and LMS AssignmentsLaunchedStatus
Microsoft 365: [Education] Provide a Copilot starter prompt in Teams and LMS AssignmentsLaunchedStatus

Office 365 Roadmap Updated: 2026-11-21

Additions : 1
Updates : 1

More Details At: www.roadmapwatch.com


New FeaturesCurrent Status
Microsoft Teams: Set and manage meeting timers in Teams Rooms on WindowsIn Development
 
Updated FeaturesCurrent StatusUpdate Type
OneNote: Suggested Artifact Creation in Copilot NotebooksLaunchedStatus

Office 365 Roadmap Updated: 2026-11-21

Items from the MessageCenter in Microsoft 365

Power Apps – Feature retirement of Microsoft Dataverse for Teams: migrate before September 15, 2027
Category:Power Apps
Nummer:MC1515294
Status:planForChange
We are announcing the retirement of Microsoft Dataverse for Teams, the built-in subset of Dataverse capabilities in Microsoft Teams. Beginning with a regional rollout on November 15, 2026, customers will no longer be able to create new Dataverse for Teams environments. Existing Dataverse for Teams environments will continue to function until the start of a regional rollout on September 15, 2027. Please note that this change does not cancel your Microsoft 365 or Teams subscription, nor does it impact Microsoft Dataverse in Power Platform environments.

How does this affect me?
We have identified that your tenant has one or more Dataverse for Teams environments. To see them, open the Power Platform admin center and review environments of type Microsoft Teams. Retirement will take place following a scheduled regional rollout beginning on the dates mentioned below:

Milestone Date the regional rollout begins
New Dataverse for Teams environments can no longer be created November 15, 2026
Recoverable deletion of existing environments begins September 15, 2027
Permanent deletion of existing environments begins October 30, 2027

Apps, flows, agents, and data in Dataverse for Teams environments that have not been migrated prior to regional rollout beginning September 15, 2027, will be deleted. An administrator can recover a deleted environment prior to the regional rollout beginning October 30, 2027. After that date, the environment and its data are permanently deleted and cannot be recovered.

Apps and data already hosted in full Dataverse environments are not affected. You will receive in-product notifications and reminder Message center posts before each milestone.

What action do I need to take?
We recommend Power Platform and Microsoft Teams administrators:
  • Inventory your Dataverse for Teams environments and the apps, flows, agents, and data in each one.
  • Choose a path for each workload: upgrade the environment to full Dataverse without rebuilding existing apps, rebuild simpler workloads as SharePoint-backed apps, or retire solutions that are no longer needed.
  • Review available, unassigned Power Apps Premium licenses, which include Dataverse. Where sufficient appropriate licenses are available, migration can proceed without additional licensing cost.
  • Export or retain any data your organization needs for records retention, legal, or compliance purposes.
  • Complete migration and validation before September 15, 2027.
To learn more, please visit Important changes (deprecations) coming in Power Platform.
Power Apps – Information regarding the end of support for Power Apps Developer Plan and unmanaged developer environments
Category:Power Apps
Nummer:MC1515303
Status:planForChange
The free Power Apps Developer Plan is being retired. As this plan works only in unmanaged developer environments, these environments are also being retired. Beginning with a regional rollout starting November 15, 2026, users will no longer be able to sign up for the plan or create new unmanaged developer environments. Developer environments that are Managed Environments and use paid licenses will not be affected by this retirement.

How does this affect me?
We have identified that your tenant has one or more unmanaged developer environments that use the free Power Apps Developer Plan. These environments can be viewed in the Power Platform admin center by navigating to Manage > Environments. Once there, check for unmanaged developer environments labelled as Developer in the Type column.

Retirement of the Power Apps Developer Plan and unmanaged environments will take place following a scheduled regional rollout beginning on the dates mentioned below:

Milestone Date the regional rollout begins
Sign-ups and creation of new unmanaged developer environments stops November 15, 2026
Recoverable deletion of existing unmanaged developer environments begins December 15, 2026
Permanent deletion of existing unmanaged developer environments begins January 15, 2027

Apps, flows, solutions, and data in unmanaged developer environments that have not been migrated prior to the regional rollout beginning December 15, 2026, will be deleted. Administrators can recover a deleted environment prior to the regional rollout beginning January 15, 2027. After that date, the environment and its data are permanently deleted and cannot be recovered.

Developer environments that are Managed Environments, and all production and sandbox environments, are not affected by this retirement. Administrators and users will receive in-product notifications before each of the milestones.

What action do I need to take?
We recommend that Power Platform administrators and makers take the following actions:
  • Identify unmanaged developer environments in your tenant and the apps, flows, solutions, and data in each one.
  • Export any solutions and any data that needs to be kept.
  • Move workloads to a supported licensed destination: turn the developer environment into a Managed Environment and assign each maker an appropriate paid license or move the workload to another licensed development or sandbox environment.
  • Review available, unassigned Power Apps licenses. Where sufficient licenses are available, migration can proceed without additional licensing cost. Developers without a suitable license can use a free 90-day Power Apps trial as a temporary bridge.
  • Complete your migration prior to December 15, 2026.
To learn more, please visit Important changes (deprecations) coming in Power Platform.
(Updated) Clipchamp/ Copilot ‘Create a video’ experience is going to have an admin control available
Category:Microsoft Clipchamp
Nummer:MC1518034
Status:planForChange

Updated November 19, 2026: We have updated the content. Thank you for your patience. 

[What and Why:]

Microsoft Clipchamp is introducing an admin policy control for the Clipchamp AI video creation experience, also known as Clipchamp ‘Generate a video’ or ‘Create a video’ in Copilot Create. This control helps organizations manage which users can access the AI-powered video creation capability. This admin policy will roll-out with default access disabled. 

Note: As of 19 Nov 2026, the AI video creation feature has been updated to be only available from Clipchamp Home, and removed from Copilot Create & the Clipchamp Editor app.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

  • Users who have access to Clipchamp Create a video / Generate a video experiences.
  • Admins who manage Microsoft 365 app policies.

Platforms/Services:

  • Microsoft Clipchamp
  • Microsoft 365 admin center policy management

What will happen:

  • Admins will be able to use policy management to control access to Clipchamp AI video project creation.
  • If your organization wants to disable access, no further action required.
  • If your organization wishes to enable employee access to this feature, the organization admin will have to disable the ‘Turn off Clipchamp AI video project’ policy

[Action Required/Recommendations:]

No action is required if your organization would like to disable access to the Clipchamp Create a video / Generate a video feature. To enable access after rollout, admins can follow the steps in this support article How to enable or disable features in Clipchamp for users in your organization | Microsoft Support and disable the policy ‘Turn off Clipchamp AI video project’.

[Compliance considerations:]

QuestionAnswer
Does this change include an admin control?Yes. Admins can use policy management to control access to Clipchamp AI video project creation.
Does the change provide end users a new way of interacting with generative AI?No. This is not a new generative AI feature. The Create a video experience is an existing feature; this update adds admin control for managing user access.

—————————-For Processing Do Not Delete——————————

Do you need to update your Service description: No

Post Publish Date: 10/14/2026

Change type: Feature

Product marketing manager: [email protected]

Major Update: No

(Updated) Microsoft Copilot app: Updates to Home and navigation
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1535647
Status:stayInformed

Updated November 20, 2026: Copilot Workspaces will roll out to standard release in December 2026, and deferred release by January 2027. Thank you for your patience. Refer to MC1559638 for details on Copilot Workspaces.

[What and why]

In MC1479277 about updates to the Microsoft Copilot app, we introduced Home as the new starting point that brings Chat and Cowork together, so users can get chat assistance and delegate multi-step tasks in one view. This post builds on that announcement with worldwide rollout timing and the addition of Projects and Workspaces to the Home experience. 

[Rollout schedule]

  • Standard release begins late October 2026
  • Deferred release begins late November 2026

[Impact on your organization]

Who is affected

  • Users of the Microsoft Copilot app. Access to Cowork and Cowork-related capabilities depends on Microsoft 365 Copilot licensing and your organization’s usage-based billing configuration. 

Platforms and services

  • Microsoft Copilot web, desktop, and mobile app.

What will happen

Projects:

  • In addition to what was communicated in MC1479277, Projects provides a dedicated space in Home for organizing related chats, Cowork tasks, and everything they share: files, instructions, and outputs. From there they can create a new project, add files and context, and start chats or Cowork tasks inside it. Responses are grounded in the project’s context first, then in the user’s broader Microsoft 365 work context. Projects are accessible from the Home navigation pane.
  • Projects doesn’t store content itself, and files stay in OneDrive under the same permissions, sensitivity labels and retention policies you already use. Word, Excel and PowerPoint files that Copilot creates are saved to the user’s OneDrive.
  • Projects are available on Windows, Mac, & Web apps across tier 1 languages. It is coming soon to mobile apps.
  • 22322 1 - KbWorks - SharePoint and Teams Specialist
  • 22322 2 - KbWorks - SharePoint and Teams Specialist

Workspaces:

  • Users will see “Notebooks” become “Workspaces” in the left navigation of the Copilot app as Copilot Notebooks evolves into Copilot Workspaces. Workspaces give teams a shared space to bring together context, team members, and working files to work alongside Copilot on an ongoing workstream.
  • Existing notebooks will convert into “workspaces,” retaining all previously added or made content. Read FAQs on our Support Page.
  • This change will roll out to all users with access to Copilot Notebooks first in the Frontier program. Copilot Workspaces will rollout to standard release in December 2026, and deferred release by January 2027. Access to individual capabilities in Copilot Workspaces will vary by license.
  • 22322 3 - KbWorks - SharePoint and Teams Specialist

[Action required and recommendations]

  • Review which users are included in a spending policy that grants Cowork access and confirm your intended usage-based billing configuration.
(Updated) Microsoft Entra: Updated passkey registration experience in My Sign-ins
Category:Microsoft Entra
Nummer:MC1545694
Status:stayInformed

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

[What and why]

We’re updating the passkey registration experience in My Sign-ins for users registering a passkey in Microsoft Authenticator. Users will see an additional checkbox and updated link text, along with steps to guide users to open Microsoft Authenticator and select the + button to begin registration. If users can’t complete registration directly in Authenticator, the updated link text will help them find the WebAuthn registration flow.

[Rollout schedule]

  • General Availability (Worldwide): Beginning in early December 2026 (previously mid-November) and expected to complete by end of December 2026 (previously end-November 2027)

[Impact on your organization]

Who is affected

  • Users who are guided through My Sign-ins to register a passkey in Microsoft Authenticator

Platforms and services

  • Microsoft Entra My Sign-ins and Microsoft Authenticator

What will happen

  • Users will see an additional checkbox and updated link text during passkey registration.
  • Users will see steps to open Microsoft Authenticator and select the + button to begin registration:

22330 - KbWorks - SharePoint and Teams Specialist

  • If users can’t complete registration directly in Authenticator, the updated link text will help them find the WebAuthn registration flow.

[Action required and recommendations]

  • Inform users about the updated UI and update your internal user guidance to reflect these changes.

[Compliance considerations]

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

Power Platform – Information regarding the end of support for SharePoint temporary authentication URLs
Category:Power Platform
Nummer:MC1551122
Status:stayInformed
Starting April 1, 2027, SharePoint temporary authentication URLs will no longer be available. Power Apps and Automate functionality that relies on these URLs will break when they are retired.

How does this affect me?
Any Power Apps app or Power Automate cloud flow that relies upon the temporary authentication URLs will stop working.

What action do I need to take?
If you are using only native controls, actions, and connectors, and as long as you are not providing pre-authenticated URLs from SharePoint, then there is no action needed.

If you have authored a custom control, action, or connector with tempauth URLs, then you will need to ensure you have migrated to the new authentication. This may come up in a few ways such as:
  • SharePoint document-library thumbnails not loading
  • SharePoint-stored Images displayed through Image control not loading
  • For the Word Online (Business) connector, CreateWordFileWithContent currently returns a pre-authorized URL that can be used to download the generated document without additional authentication. After temporary authentication is removed, customers should no longer rely on this URL as an unauthenticated file-download mechanism.
After making the required changes, publish updated apps or save and publish updated flows, as applicable. Ensure the updated apps and flows are enabled and tested before the retirement date

For more information on this, visit Pre-authenticated (tempauth) URLs are retiring: move to Microsoft Entra ID tokens before April 1, 2027.
(Updated) Microsoft Copilot: Continue using models after reaching usage limits with Copilot Credits
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1557754
Status:planForChange

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

[What and Why:]

We’re introducing the option to continue using models in Copilot Chat and Office through usage-based billing (UBB) after reaching the usage limits included in a Microsoft 365 Copilot license. After reaching a limit, users can continue with Auto without consuming Copilot Credits or, if they have UBB enabled, can continue with the selected model by consuming Copilot Credits. New credit indicators in the UI help users understand when their work consumes Copilot Credits, while spending policies give administrators control over access and spending.

This capability was originally announced in MC1479276 and is rolling out alongside the models available only through usage-based billing announced in MC1519122.

Additionally, models offered in Chat and Word, Excel, and PowerPoint will now be visible in the model picker. Models that a user does not have access to will be greyed out and users will not be able to select them.

[Rollout Schedule:]

  • Frontier: Rolling out in early December 2026.
  • General availability: Planned for mid-December 2026 in the Worldwide production cloud.

[Impact on Your Organization:]

Who is affected: End users with a Microsoft 365 Copilot license. To use models with usage-based billing in Chat and Word, Excel and PowerPoint, users must also have access to available Copilot Credits through an applicable spending policy that includes the Models with usage-based billing in Chat and Office service.

Platforms/Services: Copilot Chat in the Microsoft Copilot app and Copilot in Word, Excel, and PowerPoint across web, desktop, and mobile.

What will happen:

  • When users reach an applicable model usage limit included in their license, they can continue with Auto without consuming Copilot Credits. Users that have UBB enabled can instead continue with the selected model using Copilot Credits.
  • The new Models with usage-based billing in Chat and Office service will be available in spending policies.
  • Access to models with usage-based billing requires the service to be included in an applicable spending policy, with credits available. Users without this access cannot use models with usage-based billing.
  • Existing spending policies with Auto-apply new services enabled automatically include newly supported services as they become available. Policies with this setting disabled require administrators to add the service.
  • A new credits icon helps users understand credit availability and whether their current experience consumes credits:
    • A filled icon indicates that usage is metered and consumes Copilot Credits.
    • An unfilled icon indicates that usage is not metered and does not consume Copilot Credits.
    • Hovering over the icon shows credit usage details and an option to open a pane with additional information.
  • Users can type and submit /cost as a prompt in Copilot to view details about their current session.
  • Users will see models offered in Chat and Word, Excel, and PowerPoint visible in the model picker. If the user does not have access to a model, it will be greyed out, and the user will not be able to select it.

22580 1 - KbWorks - SharePoint and Teams Specialist

Image of credit icon and usage details.

22580 2 - KbWorks - SharePoint and Teams Specialist

Image of banner allowing users to continue with credits if they have UBB enabled.

Action Required/Recommendations:

  1. Review existing spending policies. In the Microsoft 365 admin center, go to Copilot > Cost Management > Configuration and review the policies that apply to your users.  
  2. Confirm service access. To allow usage-based model access, ensure the applicable policy includes Models with usage-based billing in Chat and Office, has an appropriate billing method, and has credits available.
  3. Review policy scope, limits, and alerts. Policies can apply to all users or selected Microsoft Entra ID security groups. Confirm the intended audience and configure spending limits and notifications.  
  4. Prepare users and support teams. Explain the choice between Auto and credit-consuming model usage, the new credit indicators, and /cost.

Use these resources to configure and manage access:

[Compliance considerations:]

New way for end users to interact with generative AIYesEligible users can continue using a selected model after reaching an included usage limit by consuming Copilot Credits.
Administrative control, including Microsoft Entra ID group membershipYesAdministrators control access through service selection in spending policies. Policies support security-group targeting, spending limits, and alerts. [learn.microsoft.com]
(Updated) Continuous interpreter visibility with pop out video in Teams
Category:Microsoft Teams
Nummer:MC1559642
Status:stayInformed

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

[What and Why:]

Users who work with sign language interpreters in Microsoft Teams meetings will be able to pop out their paired interpreters’ video into a separate window. The window can be resized and moved anywhere on the screen, including to another monitor. Interpreters stay in view while users multitask, share content, or change meeting layouts. This is designed for Deaf and hard-of-hearing (D/HH) users, for whom losing sight of an interpreter means losing access to the conversation.

[Rollout Schedule:]

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

General Availability (Worldwide): We will begin rolling out on mid January 2027 and expect to complete by late January 2027.

[Impact on Your Organization:]

This applies to Teams desktop on Windows and Mac. After this rollout, users can:

  • Pop out their paired sign language interpreters’ video into a dedicated window that stays on top of other apps.
  • Resize the window and move it anywhere on their screen or to another monitor.
  • Keep interpreters in view while presenting, viewing shared content, using chat or captions, or with the main meeting window minimized.

The pop-out window only changes the user’s own view, and interpreters stay in the main meeting gallery for everyone else. The window isn’t visible to other participants when the user shares their screen.

[Action Required/Recommendations:]

You don’t need to do anything to prepare. Consider telling D/HH users and the interpreters who support them about this feature, and update your training and accessibility documentation as needed. To use the feature:

  1. In Teams Accessibility settings, turn on Sign language mode and select I am a Signer.
  2. Select Manage interpreters and add the people who interpret for you.
  3. Select View > Pop out interpreters during a meeting.
  4. Users open the pop-out window in each meeting. For faster access, they can pin the Pop out interpreters button to the meeting toolbar. There is no admin policy for this feature.

[Compliance considerations:]

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

Microsoft Copilot: GPT-6.2 Sol and Astra rolling out
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1560916
Status:stayInformed

What and Why

To give users more choice and flexibility when working with AI in Microsoft Copilot, we’re expanding the set of AI models available in Microsoft Copilot.

GPT-6.2 Astra is rolling out with usage-based billing (UBB) in general availability to Cowork and Microsoft Copilot Studio and in Frontier to Word, Excel, PowerPoint, and Chat.

GPT-6.2 Sol is rolling out with usage-based billing in general availability to Cowork and Copilot Studio. It is also rolling out in general availability as part of the Microsoft 365 Copilot user subscription license (USL) to Word, Excel, PowerPoint, and Chat. Limits apply to this model. They are designed to support broad day-to-day AI usage across organizations and are implemented in such a way that the vast majority of users are not expected to reach them. 

Rollout Schedule

General Availability:

  • GPT-6.2 Astra: Rolling out to Cowork and Copilot Studio with UBB.
  • GPT-6.2 Sol: Rolling out to Cowork and Copilot Studio with UBB and to Word, Excel, PowerPoint and Chat as part of the USL. 

Frontier: 

  • GPT-6.2 Astra: Rolling out to Word, Excel, PowerPoint and Chat.

Impact on Your Organization

Who is affected:

  • Cowork and Copilot Studio (GPT-6.2 Sol and GPT-6.2 Astra): Users assigned a user subscription license (USL) with usage-based billing (UBB) enabled.
  • Word, Excel, PowerPoint, and Chat (GPT-6.2 Sol): Users assigned a user subscription license (USL).
  • Word, Excel, PowerPoint, and Chat in Frontier (GPT-6.2 Astra): Users assign a user subscription license who is enrolled in Frontier and has usage-based billing (UBB) enabled.
  • Access to GPT-6.2 Astra across all surfaces requires the OpenAI subprocessor to be enabled. Learn more: OpenAI as a subprocessor in Microsoft Online Services | Microsoft Learn. As a reminder, this setting only controls whether OpenAI models operated by OpenAI (provided by OpenAI as a subprocessor) can be used. OpenAI models operated by Microsoft (Azure OpenAI) aren’t affected and remain available in Copilot regardless of this setting.

Platforms/Services:

    • Copilot Chat
    • Microsoft Word
    • Microsoft Excel
    • Microsoft PowerPoint
    • Copilot Cowork
    • Microsoft Copilot Studio

What will happen:

  • Users will be able to select GPT-6.2 Sol and GPT-6.2 Astra using the model selector from supported Microsoft Copilot experiences.
    • The models are enabled by default for eligible licensed users who meet the applicable configuration requirements.

Action Required / Recommendations

No action is required for organizations that want users to access these models.

Recommended actions:

  • Review whether the OpenAI subprocessor is enabled if you plan to make GPT-6.2 Astra broadly available to users. If disabled, this model will not be available.
  • Review your organization’s AI usage guidance and communicate model availability to end users.
  • Inform helpdesk and support teams that users may encounter usage-limit notifications.
  • Update internal user documentation and training materials, as appropriate.

Compliance Considerations

Consideration Explanation 
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? GPT-6.2 Sol and GPT-6.2 Astra are additional AI models that users can select within Microsoft Copilot experiences to generate responses based on content and context available to the user through Copilot. 
Does the change provide end users any new way of interacting with generative AI? Users gain access to new model choices, GPT-6.2 Sol and GPT-6.2 Astra, in supported Microsoft Copilot experiences. 
Does the change include an admin control and can it be controlled through Entra ID group membership? Access to GPT-6.2 Astra in Copilot depends on administrative configuration of the OpenAI subprocessor. 
Microsoft Teams mobile: Updated app bar and More menu on iOS and iPadOS
Category:Microsoft Teams
Nummer:MC1560919
Status:stayInformed

[What and Why:]

To align with Apple’s updated design guidance for tab bars in iOS and iPadOS 26, we’re updating the app bar and More menu in Microsoft Teams for iOS and iPadOS.

[Rollout Schedule:]

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

General Availability (GCC): We will begin rolling out on December 10, 2026 and expect to complete by December 16, 2026.

General Availability (GCC High): We will begin rolling out on December 10, 2026 and expect to complete by December 16, 2026.

[Impact on Your Organization:]

  • The app bar will show up to four apps plus More (previously up to five).
  • The More menu will become a list with two sections: Pinned, for the apps users pin, and All, for every other app, sorted by most recently used.
  • Nothing is removed. The first time the updated app bar loads, any app that no longer fits in the four slots, including apps pinned by an admin, moves automatically to the top of the Pinned section in its existing order.
  • Users can reorder apps on the app bar and in Pinned, pin or unpin apps from More, and uninstall apps and agents they no longer need.

This change applies to devices running iOS/iPadOS 26 or later. Devices on earlier versions will continue to see the current experience.

[Action Required/Recommendations:]

No action is required. If your organization pins apps through app setup policies, consider reviewing their order so the four most important apps appear first on mobile. You may also want to update internal help documentation and let your users know about the change.

[Compliance considerations:]

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

Copilot video creation in Clipchamp Video Hub is now live in Frontier Public
Category:Microsoft Clipchamp
Nummer:MC1560920
Status:planForChange

[What and Why:]

Copilot video creation is coming to the Clipchamp Video Hub. It turns documents, ideas and work content into videos that make complex information easier to understand and act on. Users start with a prompt, a document from OneDrive, or relevant work context, then preview the video in chat and refine it through conversation until they’re happy with it.

This is a usage-based billing (UBB) feature. Each video and subsequent refinements use Copilot Credits, billed through Copilot Credits usage-based billing in the Microsoft 365 admin center. To enable access, admins must enable Anthropic models and configure Copilot Credits spending policies for intended users.

Key features:

  • Create from a prompt. Describe the topic, audience, tone and length, or pick a starter prompt. 
  • Create in your language. Describe the video in your preferred language and make localized content for audiences worldwide. 
  • Base videos on your content. Add a Word document, PowerPoint presentation, images, video or PDF from OneDrive, or draw on relevant work context through Work IQ. 
  • Refine through conversation. Ask for changes like “Use a more formal tone”, “Make it shorter”, “Localize this into Japanese” or “Update the title.” 
  • Preview in chat. Watch each version without leaving the experience. 
  • Export and share. Save the finished video as an MP4. 

How to get started: 

Admins first turn on Copilot video creation in a spending policy that includes the right users, in Copilot > Cost management in the Microsoft 365 admin center.

Users can then:

  • Open Clipchamp Video Hub 
    • [CompanyName].sharepoint.com/_layouts/15/videohub.aspx?vhnav=video-agent-home
  • Go to Create video in the left menu
  • Describe the video, and add files if needed.
  • Preview the video, refine it.
  • Select Export to save it as an MP4.

[Rollout Schedule:]

Public Preview (Frontier public): available as of November 17, 2026.

General Availability (Worldwide): Expected February (timing subject to final confirmation).

[Impact on Your Organization:]

Users included in eligible spending policies can create and refine videos from work content in Clipchamp Video Hub. Video creation and refinements consume Copilot Credits and appear in Copilot cost management reporting. 

Governance:

  • Exported videos carry a “Made with AI” watermark, which admins can turn off. 
  • Videos only draw on work content the user already has access to.

Known limitations at preview:

  • Sensitivity labels: Videos created from documents with a sensitivity label above General can’t be downloaded yet but can be viewed.
  • Availability: Anthropic models must be enabled for your organization. If they’re turned off, video creation isn’t available.
  • Generation: Creating and changing videos can take some time. Requests may sometimes fail or time out, and preview or playback may not work as expected.
  • Editing: Changes happen through conversation, and videos export as MP4. Editing individual scenes or elements in Clipchamp isn’t supported yet.
  • Source material: WorkIQ, Web search, Word, PowerPoint, images (up to 3 per prompt), Videos (under 50mb) and PDF are supported. More file types and multiple sources will come in future releases.
  • Sessions: Keep the browser tab open while a video is being created. Only one session at a time is supported.

[Action Required/Recommendations:]

If you plan to enable this capability, confirm Anthropic models are enabled and update Copilot Credits spending policies to include Copilot video creation with Clipchamp for intended users.

Review internal readiness guidance for admins and support teams before broader enablement.

[Compliance considerations:]

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

Microsoft Copilot: In-app browsing will be enabled by default in the desktop app
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1560922
Status:planForChange

[What and why]

We are enabling in-app browsing by default in the Microsoft Copilot desktop app for Windows and Mac. As we announced in MC1474455, this feature allows users to open websites shared in Copilot chat directly within the desktop app, side by side with their Copilot conversation. Previously optional, this experience will be enabled by default, helping users access web content and Copilot responses in one place and reduce context switching.

[Rollout schedule]

  • General Availability (Worldwide): Rollout will begin in early January 2027 and is expected to complete by the end of January 2027.

[Impact on your organization]

Who is affected

  • Users of the Microsoft Copilot desktop app for Windows and Mac.

Platforms and services

  • Microsoft Copilot desktop app for Windows and Mac

What will happen

  • Websites shared in Copilot chat will open directly within the desktop app by default, side by side with the Copilot conversation.
  • Users can view web content and Copilot responses in one place, reducing context switching.

updated Copilot in-app browsing experience

[Action required and recommendations]

No action is required to enable in-app browsing. If your organization wants to disable or manage this experience:

  • Set the BrowsingEnabled policy to Off through your device management system to disable in-app browsing.
  • Configure the new in-app browsing policies as needed to manage security, privacy, access, authentication and network behavior, downloads, and permissions.

If no changes are made, in-app browsing will remain enabled by default.

[Learn more]

We will update this message with updated documentation.

[Compliance considerations]

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

Enhanced prompt categories for Microsoft 365 Copilot in Microsoft Copilot Dashboard and Agent 365 Business Analytics
Category:Microsoft Viva Microsoft Copilot (Microsoft 365)
Nummer:MC1560923
Status:stayInformed

[What and Why:]

Enhanced prompt categories for Microsoft 365 Copilot provide a detailed view into Copilot Chat usage by users with a Microsoft 365 Copilot license. Copilot Chat prompts are classified into 13 categories and 41 subcategories, which show how users apply Copilot Chat in their work. The enhanced categories replace the four legacy prompt categories in the Microsoft Copilot Dashboard: “Ask and find,” “Catch up,” “Draft and brainstorm” and “Other.”

With this update, leaders and adoption teams can:

  • See how users with a Microsoft 365 Copilot license use Copilot Chat across categories such as finding information, analyzing content, writing and creating content, summarizing content, and more.
  • Break down active users and prompts by category for groups, organizations and job functions, using your existing Copilot Dashboard and Agent 365 business analytics filters.

[Rollout Schedule:]

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

[Impact on Your Organization:]

The four legacy categories are being retired. “Ask and find,” “Catch up,” “Draft and brainstorm” and “Other” will be removed from the Copilot Dashboard and replaced by the enhanced categories.

Enhanced prompt categories apply to Copilot Chat usage by users with a Microsoft 365 Copilot license. Usage of Microsoft 365 Copilot Chat by users without a Microsoft 365 Copilot license isn’t included.

You’ll find the new categories in these places:

Microsoft Copilot Dashboard

  • Adoption tab: Shows the number and percentage of Copilot Chat users in each category.
  • Impact tab: Shows the number and percentage of prompts in each category.

Agent 365 Business Analytics

  • Use cases page: Treemap view of categories and subcategories, breakdown table by prompt category, heatmap by job function, organization, or group.

The dashboard uses the same prompt category names across tenants; no user input prompt text is shown.

Anyone who already has Copilot Dashboard or Agent 365 business analytics can view the enhanced prompt categories. There’s no separate setting to configure. This change is on by default.

[Action Required/Recommendations:]

We recommend that you update guidance and training materials that refer to the legacy categories. No admin action is required.

[Compliance considerations:]

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

Microsoft Teams: Tenant policy controls who can record and transcribe
Category:Microsoft Teams
Nummer:MC1560924
Status:planForChange

[What and Why:]

Teams administrators can use a policy to configure who may start recording and transcription. The policy supports two participant scopes: organizers and co-organizers, or organizers, co-organizers, and presenters. For each scope, administrators can specify whether meeting organizers can or cannot change the setting.

This provides a centrally managed default or enforced restriction for meetings organized by users assigned the policy, reducing the need for per-meeting configuration.

[Rollout Schedule:]

Targeted Release (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by mid-December 2026.

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

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

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

General Availability (DoD): We will begin rolling out in mid-February 2027 and expect to complete by early March 2027.

[Impact on Your Organization:]

A new Who can record and transcribe policy control will be available in the Recording & transcription section of the applicable Teams meeting policy in the Teams admin center.

The default value is Organizers, co-organizers, and presenters. Organizers can change, which preserves the current behavior.

Administrators can select one of the following four options in a single dropdown:

Who can record and transcribe – policy optionBehavior
Organizers and co-organizers. Organizers can changeDefaults to organizers and co-organizers. Organizers can also allow presenters through the existing meeting option.
Organizers and co-organizers. Organizers can’t changeLocks the policy value. Presenters and attendees cannot start recording or transcription.
Organizers, co-organizers, and presenters. Organizers can changeDefaults to organizers, co-organizers, and presenters. Organizers can restrict the roles through the existing meeting option.
Organizers, co-organizers, and presenters. Organizers can’t changeLocks the policy value. The organizer cannot change the role selection.

These configurations remain subject to existing recording and transcription availability controls and any sensitivity label that configures this option.

  • Enforcement: When organizer changes are blocked, Meeting options shows the policy value as read-only with a notice that it is locked by meeting policy. The effective role restriction is also enforced when a participant tries to start recording or transcription.
  • Sensitivity labels and templates: A sensitivity label that configures this option takes precedence over the meeting policy. A locked meeting policy takes precedence over a meeting template. An unlocked policy supplies a default.
  • Related meeting options: The existing Who can record and transcribe meeting option remains a Teams Premium or Microsoft 365 Copilot feature.

[Action Required/Recommendations:]

  • No action is required. If you do not configure the new policy, existing recording and transcription behavior remains unchanged.
  • If your organization needs to prevent presenters from starting recording or transcription, consider using the new Who can record and transcribe policy.
  • Review policy assignments, sensitivity labels, and meeting templates to confirm the effective behavior.
  • Notify meeting organizers and helpdesk teams of any changes and update internal guidance.

[Compliance considerations:]

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

Updates to Workforce Insights Agent (Frontier) for Admins in Microsoft 365 Copilot
Category:Microsoft Copilot (Microsoft 365)
Nummer:MC1560929
Status:stayInformed

[What and why]

We are adding new capabilities to Workforce Insights Agent (Frontier) in Microsoft 365 Copilot, enabling organizations to get grounded and contextually relevant responses in Copilot from their organizational data. The agent now provides administrators with an additional dedicated workspace to configure organizational definitions, data descriptions and business context. In the agent, admins can also validate how AI reason over those contexts in people and organizational queries and ask the agent to help diagnose gaps or issues where the responses are different than expected.

As the changes rolling out, configurations applied in Workforce Insights Agent will start to apply across some Copilot experiences, with the plan to extend availability across all Copilot experiences in the future. Review the Workforce Insights Agent roadmap and documentation for more details.

[Rollout schedule]

  • Public Preview (Frontier): Beginning in mid-November 2026, the new capabilities will become available to all Frontier tenants

[Impact on Your Organization]

Who is affected

  • Tenants: Tenants with Microsoft 365 Copilot licenses or the Microsoft 365 Copilot in Productivity Apps service plan, and enrolled in Frontier program, will see the agent available in the agent store
  • Administrator roles: Global, AI and Organizational Data Administrators will be needed for configurations

Platforms and services

  • Microsoft 365 Copilot, Workforce Insights Agent, Microsoft Entra ID, Microsoft 365 Organizational Data Service, and People Skills

What will happen

  • By default, licensed users can discover and install Workforce Insights Agent through Copilot or the Teams agent store, subject to admin policies. This does not grant access to configuration controls or data/expanded scope queries beyond users’ existing permissions.
  • AI administrators manage agent deployment and access, while Organizational Data Administrators can configure organizational context and validate results directly in the Workforce Insights Agent. We recommend assigning Organizational Data Administrator to individuals responsible for providing and maintaining data and organizational context, such as HR or People Analytics teams.
  • Workforce Insights Agent uses organizational data from Microsoft Entra ID by default. Organizations can use Microsoft 365 Organizational Data Service in Microsoft 365 Admin Center for additional attributes. Configuring context in the agent does not modify data in the underlying source system.
  • In Workforce Insights Agent, administrators can configure organizational context and attribute descriptions to help the agent and soon Copilot better understand how data should be interpreted or metrics should be calculated for your organization. Descriptions explain what each attribute represents, including relevant values, abbreviations, and guidance for its use. With this release, these capabilities apply fully to Workforce Insights Agent and to some types of queries in other Copilot experiences. Check out the Workforce Insights documentation and roadmap for more details and latest updates.

• AI Administrators and Organizational Data Administrators should review deployment scope and configuration for the intended audience.

[Action Required / Recommendations]

Before enabling or expanding use:

  • Review licensing and access: Ensure intended users have the required Microsoft 365 Copilot license, and the tenant has enrolled in Frontier program. Review default discovery and installation. Admins can install the agent for users, restrict access to users or groups, or remove or block it.
  • Prepare data and organizational context: Review Entra ID data quality, reporting relationships, organizational attributes, definitions, and terminology. Additional or replacement data can be provided through Microsoft 365 Organizational Data Service. Review permissions and data-handling requirements before uploading. Add organizational context from your existed business collateral to the agent and leverage the interactive tuning experience as appropriate.
  • Review configuration: Admin configurations will move from the Workforce Insights Admin web page to Workforce Insights Agent home page. Supported options include attribute descriptions, organizational context and visibility to all configurations such as attributes & access policies, data access and more.
  • Consider People Skills: Enable People Skills if skills-based queries are required and review its setup and governance requirements.
  • Review data access: Users can request expanded data scope from people with direct reports. Use the WorkforceInsights PowerShell module to control this access according to organizational policies.
  • Validate results: Have authorized users test representative prompts against known data and definitions, address discrepancies, and repeat validation after changes.

Learn more 

[Compliance considerations]

Workforce Insights Agent is not designed for behavioral monitoring, performance management or employment decisions. Administrators are responsible for local legal and business requirements, data protection obligations and Works Council guidelines. Configure available controls to align with these requirements and business practices.

Compliance considerationExplanation
Stores new customer dataUses organizational data from Microsoft Entra and optionally additional data uploaded through Microsoft 365 Organizational Data Service.
Alters processing of existing customer dataProcesses organizational data to generate workforce insights such as structure, roles, and composition.
Introduces AI/ML capabilities interacting with customer dataUses AI to analyze organizational and skills data and generate insights through natural language queries.
Admin control available (Entra groups)Admins can control access, restrict deployment, and manage availability using Microsoft 365 admin center and Entra group-based controls.
User can enable/disable featureUsers can install and pin the agent themselves unless restricted by administrative policies.
Low-latency alerts and metrics in Monitor
Category:Power Platform
Nummer:MC1560951
Status:stayInformed
We are announcing the ability to evaluate alert rules and review supported metrics for business-critical resources every hour in Monitor, helping admins identify potential issues sooner. This feature will enter public preview on November 23, 2026.

How does this affect me?
When creating or editing an alert rule for a supported app, flow, or agent, admins can set the Data review period to 1 hour. Monitor will evaluate the selected metric after new hourly data becomes available, and the alert can trigger when the configured threshold is crossed. Admins can also switch the metric chart to an hourly view to review activity from the previous 24 hours. These alerts follow an hourly evaluation schedule and are not real-time alerts.

The following products and metrics are supported in the Power Platform admin center experience of Monitor:
  • Canvas and code apps : Time to interactive, app open success rate, data request latency, and data request success rate
  • Model-driven apps : App open success rate
  • Cloud flows : Success rate
  • Copilot Studio agents : Agent session success rate
The following metrics are supported for Copilot Managed Runtime apps in the Microsoft 365 admin center experience of Monitor:
  • Time to interactive
  • App open success rate
  • Data request latency
  • Data request success rate
  • App session count
Low-latency alert rules apply to individual resources and metrics. Only one hourly rule can be configured for each resource and metric, and each tenant can configure up to 10 hourly rules in each supported admin experience. Hourly rules that are turned off continue to count toward this limit. For Power Platform resources, low-latency alerts use resource scope and require the resource to be in a Managed Environment.

What action do I need to take?
This message is for awareness, and no action is required.

If you choose to use this feature, consider configuring hourly alert rules for the business-critical resources where identifying an issue on the same day is most important.

For more information about this feature, please visit:
Power Platform Monitor – Route alert notifications to connector-backed destinations
Category:Power Platform
Nummer:MC1560957
Status:stayInformed
We are announcing the ability to route Power Platform Monitor alert notifications to Microsoft Teams, SMS, work item tracking systems, and other connector-backed destinations in Power Platform. This feature will reach public preview on November 20, 2026.

How does this affect me?
Tenant admins can use the new When an alert fires trigger in the Power Platform for Admins V2 connector to create a Power Automate cloud flow that runs when an opted-in Monitor alert fires. The flow can send alert details to any supported connector-backed destination. For example, it can:
  • Post an alert to a Microsoft Teams channel
  • Send an SMS notification
  • Create a work item
  • Perform several of these actions from the same alert
This enables your organization to receive and manage Monitor alerts using the tools and processes your teams already use.

During public preview, this capability supports custom alert rules created in the Power Platform admin center that uses a 24-hour data review period. Support for hourly, low-latency alert rules and environment admins is planned for a future release.

Existing email notifications will continue to function as they do today. Your organization will not experience any changes unless a tenant admin creates a cloud flow using the new trigger.

What action do I need to take?
This message is for awareness, and no action is required.

If you would like more information on this feature, please visit Route alert notifications to any connector-backed destination (preview).
Copilot Studio – Create Dataverse agent users with Microsoft Entra agent ‘s user account
Category:Microsoft Copilot (Power Platform)
Nummer:MC1560996
Status:stayInformed
We are announcing the ability to create Dataverse agent users with Microsoft Entra agent’s user account in Copilot Studio. This feature will reach general availability on December 8th, 2026.

How does this affect me?
This feature enables you to securely deploy agents to access and interact with Dataverse data by using enterprise-managed Microsoft Entra agent identities. It enables agents to be provisioned as Dataverse agent users with dedicated, least-privileged security roles based on their intended capabilities.

The feature ensures agents have only the access required to perform tasks autonomously or on behalf of users. By using identity-based role assignment and full auditing of agent-driven actions, you can enforce security and compliance policies across both human users and agents while maintaining traceability of data access and changes within Dataverse environments.

What action do I need to take?
This message is for awareness, and no action is required.

If you would like more information on this feature, please visit Create Entra agent users (preview).
Generate documents from the Agent node in workflows
Category:Microsoft Copilot (Power Platform)
Nummer:MC1561859
Status:stayInformed
We are announcing the ability to generate documents from the Agent node in workflows within Copilot Studio. This feature will reach general availability on December 3, 2026.

How does this affect me?
With this feature, the Agent node can now return files that the agent generates, such as PDF, Word, Excel, PowerPoint, and CSV, as workflow outputs.

Key functionality of this feature includes:
  • Ability to work with both inline agents and existing (published) agents.
  • Generated files appear as an ordered files output (name, content type, content) that’s available to downstream steps.
  • Ability to pass files to connectors, enabling emailing, saving to SharePoint/OneDrive, and attaching to records.
What action do I need to take?
This message is for awareness, and no action is required.
Run Python code as a workflow step
Category:Microsoft Copilot (Power Platform)
Nummer:MC1561862
Status:stayInformed
We are announcing the ability to use the Code node to run Python as a step in a workflow for logic that expressions and connectors cannot handle in Copilot Studio. This feature will reach general availability on December 1, 2026.

How does this affect me?
Makers can add Python steps to workflows for data transforms, file parsing and conversion (e.g. PDF to text, CSV, or XML), and calls to APIs that don’t have a connector. The code can be generated using natural language using AI, or Makers can write and edit the code by hand.

Code runs in a Microsoft-managed sandbox environment and consumes Copilot Credits. Code steps are unable to make outbound API calls.

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.