Microsoft Roadmap, messagecenter and blogs updates from 08-11-2025

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

08-November-2025 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: 2025-11-08

Additions : 2
Updates : 16

More Details At: www.roadmapwatch.com


New FeaturesCurrent Status
Microsoft Copilot (Microsoft 365): Streamlined Authentication process with OAuth for Connector AdminsIn Development
Microsoft Viva: Update storyline cover photos in Teams for iOS.In Development
 
Updated FeaturesCurrent StatusUpdate Type
Microsoft Copilot (Microsoft 365): Summarize files shared in Teams chat with CopilotLaunchedStatus
Microsoft Teams: Enhanced spell check with multi-language supportLaunchedStatus
Microsoft Viva: Viva Amplify – Distribute from SharePointLaunchedStatus
Outlook: Summarize email attachments with CopilotLaunchedStatus
Microsoft Copilot (Microsoft 365): The chat experience now offers better search refinement on CIQ menu Files tabLaunchedStatus
Outlook: Offline Support for Calendar – Create, Edit and Delete Event supportRolling OutStatus
Microsoft Teams: Default Teams Calling global policy to enable users to transcribe or record callsLaunchedStatus
Microsoft Copilot (Microsoft 365): Surveys Agent helps you build, run, and analyze surveysLaunchedStatus
Microsoft Copilot (Microsoft 365): Updated UI for the Copilot Chat Navigation Pane in TeamsLaunchedStatus
Microsoft Copilot (Microsoft 365): [Copilot Chat] Search based user RSVP statusLaunchedStatus
Microsoft Copilot (Microsoft 365): [Copilot Chat] Email attachment summarization (Modern Attachments)LaunchedStatus
Microsoft Copilot (Microsoft 365): Copilot Chat – Support for emails in ContextIQRolling OutStatus
Microsoft Teams: People count captured by Cloud IntelliFrame in the Pro Management portal reportsLaunchedStatus
Microsoft Teams: Permission and Privilege level of Apps and AgentsLaunchedStatus
Microsoft Teams: Agent & bot support for Entra authentication in group chatsRolling OutStatus
Microsoft Copilot (Microsoft 365): Floating Copilot icon in File Previewer for OneDriveRolling OutStatus

Items from the MessageCenter in Microsoft 365

Power Apps – Deprecation of Maker Copilot in canvas apps
Category:Power Apps
Nummer:MC1183604
Status:stayInformed
We are announcing the deprecation of the Edit your app with Copilot in Power Apps Studio (preview) in canvas apps. The deprecation will begin on January 6, 2026, and will remove the Maker Copilot chat sidecar (accessed by a Copilot button entry point in the header) from the Canvas App studio.

How does this affect me?
The Maker Copilot header button will be removed from the Canvas App studio. Makers will no longer be able to invoke Copilot from the header sidecar or via shortcut/URL.

App creation, editing, and publishing will continue to function normally. No existing apps will be impacted.

What do I need to do to prepare?
No action is required. This change is limited to the Maker Copilot chat sidecar entry point. Users can continue to use other Maker and publishing workflows without interruption and continue to create new apps conversationally using the Copilot in Table Designer, and Plan Designer.
Rate my call feedback experience update in Microsoft Teams
Category:Microsoft Teams
Nummer:MC1183608
Status:stayInformed

[Introduction]

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

user settings

[When this will happen:]

  • Targeted Release: Rollout begins mid-November 2025, completes by late November 2025
[How this affects your organization:]

Who is affected: Users of Microsoft Teams on Windows desktop, Mac, and Web clients

What will happen:

  • Users will see a new Rate My Call screen after calls and meetings
  • The new screen includes:
    • Thumbs up / thumbs down rating
    • Optional problem tokens
    • Optional free-text field for additional details
  • Feedback Rating values in Call Quality Dashboard (CQD) will change:
    • 5: Thumbs up / Good
    • 1: Thumbs down / Had issues
    • 0: Survey shown but not submitted
    • Null: Survey not shown
  • Problem tokens will still be recorded even if a rating (thumbs up or down) is not submitted
  • Admins may notice an increase in poor feedback metrics due to the new rating method; this does not reflect a decline in service quality
[What you can do to prepare:]

  • Communicate this change to helpdesk and support staff
  • Update internal documentation to reflect the new feedback format
  • Monitor PCR (Poor Call Rate) telemetry until it stabilizes, then set your own threshold

[Compliance considerations:]

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

[FAQ]

Q: Will a higher PCR mean calls are worse?
A: No. The new design captures more dissatisfied users by reporting a higher willingness to report poor calls. The increase is a measurement effect, not a quality regression.

Q: What is the new PCR target or threshold for your workstreams?
A: We cannot provide a fixed PCR threshold. Your action is to monitor your own PCR telemetry until it stabilizes (both volume and value relatively flat), then set your threshold. Stabilization may take weeks and once the data converges, you can then set your own.

Microsoft Teams: Join by code requires owner approval for private teams
Category:Microsoft Teams
Nummer:MC1183610
Status:stayInformed

[Introduction:]

To improve team governance and reduce the risk of unintended access, Microsoft Teams is updating the join by code experience for private teams. Going forward, team owners will need to approve join requests when users attempt to join a private team using a code. This change aligns the join by code experience with existing join by link behavior for private teams.

[When this will happen:]

  • Targeted Release: Rolling out in mid-November 2025 and expected to complete by late November 2025.
  • General Availability (Worldwide): Rolling out in early December 2025 and expected to complete by mid-December 2025.

[How this affects your organization:]

Who is affected: – All Microsoft Teams users in private teams using the join by code feature.

What will happen:

  • Team owners can continue to generate join codes under Team settings > Team code.
  • Users can enter a join code via the New items menu in the Chat or Channels app.
  • For private teams, users will no longer be added immediately upon entering a join code.
  • Instead, team owners will receive a join request they can approve or reject.
  • This change does not affect public teams—users can still join public teams automatically using a code.

[What you can do to prepare:]

  • Inform team owners, especially in environments where join by code is commonly used (such as schools or universities).
  • Encourage team owners to monitor and manage join requests for private teams.
  • Update internal documentation or training materials to reflect this change.
  • No admin action is required to enable this feature.

[Compliance considerations:]

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

Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF)
Category:Microsoft Teams
Nummer:MC1183611
Status:stayInformed

[Introduction]

To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation.

user settings

This message is associated with Microsoft 365 Roadmap ID 518218.

[When this will happen:]
  • Targeted Release: Rolling out early January 2026, expected to complete by mid-January 2026.
  • General Availability:  Rolling out early January 2026, expected to complete by mid-January 2026.

[How this affects your organization:]

  • Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations.
  • What will happen:
    • Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel.
    • A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones.
    • Once the external party is reached, users can merge them into the ongoing meeting.
    • No changes to existing administrator policies; feature is enabled by default.

[What you can do to prepare:]

  • No administrator action is required for this rollout.
  • If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability.
  • Before rollout, we will update this post with new documentation.

[Compliance considerations:]

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

Action Required to Enable Extended Security Update for local devices accessing Windows 365
Category:Windows
Nummer:MC1183612
Status:planForChange
Windows 10 devices accessing Windows 365 Enterprise Cloud PCs and Windows 365 Frontline (Dedicated) Cloud PCs are automatically entitled to Windows 10 Extended Security Updates (ESU) under certain conditions. IT administrators must use Microsoft Intune or another MDM provider to deploy a custom policy that helps verify whether a device is enrolled in the Windows 10 ESU subscription program.

Action is required in order for these devices to install the upcoming November 2025 Windows security update, which will be available on November 11, 2025. Learn more about this change at Enable Windows 10 Extended Security Updates (ESU) for clients accessing cloud and virtual machines.

When will this happen:
The upcoming November 2025 Windows security update will be available on November 11, 2025. It’s necessary to take action prior to this date, in order for devices to be eligible for this update.
 
Entitlement to ESU is available for qualifying devices any time, however, we advise taking action prior to November 11 in order to receive this month’s update and remain protected.

How this will affect your organization:
Windows 10 devices accessing Windows 365 Enterprise Cloud PCs and Windows 365 Frontline Cloud PCs in dedicated mode are automatically entitled to ESU for the duration of the ESU offer if the user has an active Windows 365 Enterprise license assigned or Windows 365 Frontline Cloud PC in dedicated mode provisioned, provided the following conditions are met:

  • IT administrators must deploy a custom policy that enables the EnableESUSubscriptionCheck flag. This policy helps verify whether a device is enrolled in the Windows 10 ESU subscription program. Microsoft Intune or another MDM provider can be used to deploy this custom policy. See the documentation To configure EnableESUSubscriptionCheck flag with Intune and the resources in the Additional Information section, below.
  • The local Windows 10 device is either Microsoft Entra joined or Microsoft Entra hybrid joined.
  • Users must sign in to their physical Windows 10 device using the same Microsoft Entra ID account they use for Windows 365 Cloud PCs at least once every 22 days to maintain eligibility for ESU updates on that device.

Please also note the following:

  • Physical devices that are only Microsoft Entra registered or on-premises Active Directory joined are not eligible for this Windows 365 ESU entitlement. 
  • Personal or BYOD devices that aren’t managed by the organization and are only Microsoft Entra registered will not qualify for this entitlement. These devices should be enrolled via the Consumer ESU program. An eligible user can activate up to 10 devices.

What you need to do to prepare:
Ensure that the Windows 10 devices across your organization meet the above requirements in order to continue to be protected under the ESU offering. We advise taking action prior to November 11 in order to remain protected. See the Additional information section for details and resources.

Additional information:
Power Automate – HTTP and Teams webhook trigger flows are moving to new URLs
Category:Power Platform
Nummer:MC1183710
Status:stayInformed
As of August 2025, Power Automate flows and Agent flows (Copilot Studio) with HTTP triggers or Teams Webhook triggers that have logic.azure.com in the URL moved to a new URL as a part of a critical infrastructure upgrade to improve execution speed and provide new features.

How does this affect me?
Users can see the new URL in the HTTP URL field of the flow’s trigger when loading the flow in the designer. Beginning November 30, 2025, the logic.azure.com URL will no longer work- meaning the flows will not trigger when invoked from external systems.

What action do I need to take?
To ensure that existing flows using HTTP or Teams Webhook triggers continue to work, complete the actions mentioned in this documentation by November 30, 2025. Prior to this date, both the old and new URLs will be supported. If no action is taken before this date to update flow triggers to the new URL, users will experience failures triggering these flows as the old URL will no longer work.
(Updated) Microsoft Viva Engage: New reply and reaction notifications in Microsoft Teams
Category:Microsoft Teams Microsoft Viva
Nummer:MC978923
Status:stayInformed

Updated November 6, 2025: We have paused rollout of this item. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience this may have caused and thank you for your patience.

Coming soon for Microsoft Viva Engage: Users will have a new way to engage with the Viva Engage app in Microsoft Teams through new notifications in the Teams Activity feed. This message applies to Teams for the web, Teams for Windows desktop, Teams for Mac desktop, and Teams for iOS/Android.

After this rollout, users with the Engage app installed can be notified in Teams for replies and reactions to their community posts. This new feature helps large organizations stay connected and informed of news, updates, and safety while in Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 474126.

[When this will happen:]

General Availability (Worldwide): Rollout is currently paused. We will communicate via Message center when we are ready to proceed. 

[How this will affect your organization:]

This feature will be available by default and the notifications will be on by default.

After this rollout, users can change notification settings in Teams for desktop or the web: Go to Activity on the left side of Teams, select the gear icon, and change settings in the Viva Engage section. In Teams for iOS/Android, users can turn notifications on or off for all apps from the notifications settings page. 

User documentation: Manage notifications in Microsoft Teams – Microsoft Support

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before or after the rollout.

Share this news with users at your organization and consider pinning Engage next to Chats and Teams. Ensure your corporate communications team is aware of this additional channel of reaching users across the organization.

You may want to update any relevant documentation.

Leave a Comment

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

Scroll to Top