Microsoft Roadmap, messagecenter and blogs updates from 25-02-2026

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

 Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen.

This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.)

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

Targeted Release: We will begin rolling out mid-April 2026 (previously early March) and expect to complete by late April 2026 (previously late March).

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-May 2026 (previously late March) and expect to complete by late May 2026 (previously late April).

[How this will affect your organization:]

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen who can choose to accept or deny it:

If the request is accepted, the annotation session will start for everyone in the meeting:

Anonymous users in the meeting will not be able to send a request.

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

Learn more: Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (we will update this before rollout)

Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022)

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

Coming soon for Microsoft SharePoint: A new web part for FAQs, to help assist content owners keep their content fresh and relevant. Powered by Microsoft 365 Copilot, this new web part can help content owner easily curate FAQ by working with agents and connected grounding data.

Copilot license requirements:

• Reading: All readers can view FAQ web part content without a Copilot license.
• Creating & Editing: A Copilot license is necessary for creating and editing content using Copilot features.

This feature requires a SharePoint license and a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 482198.

[When this will happen:]

Public Preview (Worldwide): We will begin rolling out early August 2025 and expect to complete by late August 2025.

Public Preview (GCC): We will begin rolling out late September 2025 and expect to complete by mid-October 2025.

General Availability (Worldwide, GCC): We will begin rolling out May 2026.

[How this will affect your organization:]

After this rollout, authors can add the web part for FAQs directly to pages or news posts during editing:

By selecting one or more grounding source files, AI will automatically generate FAQ content, reducing the time and effort needed for manual creation of FAQs. The web part currently supports FAQ types such as Event, Product, and Policy, with the option for authors to provide additional descriptions to guide more targeted content generation.

FAQs created using the web part can be indexed for search and shared via email, making it easier to distribute consistent, up-to-date information to your organization.

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Before rollout, we will update this post with new documentation.

Updated February 24, 2026: We have updated the timeline. Thank you for your patience.

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically set their work location to reflect the building they are working in. This makes it easier for users to coordinate work with their coworkers and connect in person.

This feature is opt-in and requires you to take action to configure it. After you turn it on, end-users remain in control and can choose whether to share their work location with their coworkers.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

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

[How this will affect your organization:]

This feature allows you to map Wi-Fi networks and devices to buildings, which allows your users to have their work location automatically updated when they connect. This is a major improvement over the current experience which relies on end-users to manually set their work location. When this feature is configured and enabled, Teams can automatically update the work location of users who connect their laptop to your organization’s Wi-Fi network or peripherals. The feature can leverage the mapping between your building names and your Wi-Fi networks to set the work location of your users to the right building. It can also leverage mappings to specific peripherals, such as monitors. Teams uses the same policy to enable or disable automatic updates of work location for Wi-Fi and peripherals. Learn more: New-CsTeamsWorkLocationDetectionPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Teams will not update the location of your users if they connect after their working hours (that they can configure in the Microsoft Outlook Calendar). Also, their work location will be cleared at the end of their working hours.

[What you need to do to prepare:]

Automatic update of work location is off by default, but it can greatly improve the experience of your users. We recommend turning it on and configuring it in your tenant.

Before rollout, we will update this post with new documentation.

Updated February 24, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

Starting end of February 2026, we will introduce jailbreak and root detection for Entra credentials in the Microsoft Authenticator app on both iOS and Android platforms. This change enhances security by preventing Entra credentials from functioning on jailbroken/rooted devices. All existing Entra credentials on jailbroken or rooted devices will be wiped to protect your organization. This capability is secure by default and does not require any admin configuration or control.

[When this will happen] 

General Availability (Worldwide Android) rollout begins in end of February 2026 and is expected to complete in mid-year 2026 (previously April).

General Availability (Worldwide iOS) rollout begins in April 2026 (previously March) and is expected to complete in mid-year 2026 (previously April).

[How this affects your organization]

Who is affected: All users of Microsoft Authenticator on iOS and Android whose Entra credentials are registered on jailbroken or rooted device. This is going to be a continuous check.

What will happen:

• The feature is secure by default and enabled to all customers. There is no opt-out capability..
• Users on jailbroken or rooted devices will experience the following phased rollout. An estimated gap between 3 phases is ~ 1 month.
  • Phase 1 – Warning Mode: Users receive a warning that their device is jailbroken or rooted and will be blocked in the future (screenshots 1-4): 

  

  

  

  

  • Phase 2 – Blocking Mode: Users are blocked from registering Entra credentials or signing in via Authenticator (screenshots 5-8):

  

  

  

  

  • Phase 3 – Wipe Mode: Existing Entra credentials are wiped from jailbroken or rooted devices (screenshots 9-11):

  

  

  

• Users on non-Jailbroken or non-rooted devices will not be affected.

[What you can do to prepare]

• Notify users about this upcoming change. Users will see error messages or banners in the Authenticator app during warning or blocking phases. These screens are dismissible but indicate the device status.
• Communicate to helpdesk staff that Authenticator will become unusable for Entra accounts on jailbroken or rooted devices.
• Update internal documentation if you reference Authenticator usage.
• No admin action is required to enable or configure this feature.

Learn more: About Microsoft Authenticator | Microsoft Support

[Compliance considerations]

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

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

[Introduction:]

We’re introducing a visual refresh of the Access Request and Access Denied page experience across Microsoft 365, redesigned to help users quickly request access to content such as documents, SharePoint sites, or Teams meeting recordings. This update features modern Fluent illustrations, animations, and clearer messaging to make it easier to understand and resolve access issues for a more seamless collaboration experience.

This message is associated with Roadmap ID 553214.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in March 2026 (previously February) and expect to complete March 2026 (previously early February).

[How this will affect your organization:]

Who is affected: All users requesting access to content stored on OneDrive and SharePoint.

• Users will see a redesigned Access Request page when attempting to access restricted content: 



• The page will feature updated Fluent visuals and animations.
• Messaging will be clearer to help users understand the status of their request:



• No changes to admin policies or access controls.
• The update will be enabled by default.

[What you need to do to prepare:]

No action is required to enable this update; it will be applied automatically.

However, to ensure a smooth experience for your users, we recommend the following:

• Communicate this change to helpdesk and support staff so they can assist users who may have questions about the new visuals or messaging.
• Update internal documentation if you reference the Access Request or Access Denied experience in training materials or support guides.
• Review any custom workflows or access request processes to ensure they align with the updated experience.
• Monitor user feedback after rollout to identify any confusion or support needs related to the new design.

[Compliance considerations:] 

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

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft 365 Copilot in PowerPoint will soon support enterprise image libraries hosted on Adobe Experience Manager (AEM). This integration allows users to generate slides using branded images from your organization’s asset library, helping maintain brand consistency and streamline content creation.

This message is associated with Roadmap ID 516037, 516038, and 516039.

[When this will happen:]

General Availability (Worldwide): Rollout begins end of March 2026 (previously end of February) and is expected to complete by end of April 2026 (previously end of March)

[How this affects your organization:]

Who is affected:

• Organizations using Adobe Experience Manager for brand asset management
• Admins and brand managers configuring enterprise image libraries
• PowerPoint users leveraging Microsoft 365 Copilot

What will happen:

• Admins can connect enterprise image libraries from AEM to Microsoft 365 Copilot in PowerPoint.
• Users will be able to generate slides using branded images from AEM.
• If no enterprise image library is connected, the branded image option will be disabled, and only Microsoft 365 images will be available.
• This feature is available by default for admins to configure; no opt-in required.

[What you can do to prepare:]

• Deploy AEM assets Microsoft 365 Copilot Connector by following the steps outlined in the article Deploy the Adobe Experience Manager Assets Microsoft 365 Copilot connector.
• Give your final consent on the Adobe Experience Manager Assets screen



• Ensure images in AEM include robust metadata (keywords, titles, alt-text) for better searchability.
• Communicate this change to your design and marketing teams.
• Update internal documentation if you detail image sourcing for PowerPoint.

Once setup is complete, users can select the New Slide with Copilot icon in the PowerPoint ribbon, enter a prompt, and choose their preferred image source—either Microsoft 365 images or their organization’s branded image library—via the Image Source menu.

Learn more:

• About Adobe Experience Manager Assets Microsoft 365 Copilot connector
• Keep your presentation on-brand with Copilot

[Compliance considerations:]

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

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Teams meeting Notes, powered by Loop, are now available for instant calls and meetings, like those started from Meet now and calls started from chat. Meeting notes are Loop components in Teams meetings and chats that allow users to collaboratively build agendas, capture notes, and create action items. Once added, they stay in sync and can be shared and edited in the Loop app in your web browser.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 541831.

[When this will happen:]

• Targeted Release: We will begin rollout early April 2026 (previously mid-March) and expect to complete mid-April 2026 (previously late March).
• General Availability (Worldwide): We will begin rollout mid-April 2026 (previously early April) and expect to complete mid-May 2026 (previously late April).
• General Availability (GCC): We will begin rollout mid-May 2026 (previously late April) and expect to complete late May 2026.
• General Availability (GCC High): We will begin rollout early June 2026 (previously late May) and expect to complete mid-June 2026 (previously mid-June).
• General Availability (DoD): We will begin rollout mid-July 2026 (previously early June) and expect to complete late July 2026 (previously early July).

[How this affects your organization:]

Who is affected:

• All users who participate in instant meetings in Microsoft Teams.
• Admins managing Teams, SharePoint sharing defaults, or Loop settings.

What will happen:

• Users can add meeting notes using the Notes button in meeting controls.
• Notes appear in a right-side pane with an option to open in the browser.



• Notes are Loop components and stay in sync across Teams and the Loop app.
• Users can co-create agendas, take notes, and assign tasks.
• Tasks sync with Planner and To Do and send email notifications.
• After the meeting, notes are accessible in the Recap tab → Notes.



• Note: The new meeting notes file will generate a Company Shareable Link (CSL) unless your organization has set People Specific Link (PSL) as the default. If PSL is the default, only users included on the original meeting invite will be able to access the notes. Users who were forwarded the meeting or nudged into it will need to request access to the notes.
• This feature is enabled by default.
• Known limitation: Meeting notes are not available for Teams calls.

[What you can do to prepare:]

No admin action is required.

• Review your organization’s SharePoint sharing defaults.
• Notify users or helpdesk staff about this change.
• Update internal documentation as needed.
• Manage this feature via PowerShell if necessary:
  Set-SPOTenant -IsCollabMeetingNotesFluidEnabled (boolean)

Learn more: Settings management for Loop functionality in Teams

[Compliance considerations:]

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

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

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

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

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

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

[When this will happen]

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

[How this will affect your organization]

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

What will happen

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

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

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

[What you need to do to prepare]

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a new capability in Microsoft Purview eDiscovery (Premium) that allows eDiscovery users to add a statistical sample of search results to a review set. This enhancement helps organizations validate search results earlier in the investigation process, improving confidence in data relevance before committing all results to review.

With this update, reviewers can include a representative subset of items based on configurable sampling criteria, enabling faster early‑stage assessment while reducing review volume. 

This message is associated with Microsoft 365 Roadmap ID 516578.

[When this will happen]

General Availability (Worldwide): Rollout will begin in mid-March 2026 (previously late February) and is expected to complete by late March 2026 (previously late February).

General Availability (GCC, GCCH, and DoD): Rollout will begin in mid-March 2026 (previously early March) and is expected to complete by late March 2026.

[How this affects your organization]

Who is affected: Administrators and eDiscovery (Premium) users who manage or review search results and review sets in Microsoft Purview.

What will happen:

• This change does not impact any other Microsoft Purview or Microsoft 365 services.
• Users will see new sampling options after search statistics have been generated for a search.
• Users can choose to add all search results to a review set or add a sample of results based on configurable statistical inputs.
• When sampling is selected, reviewers can specify:
  • Confidence level
  • Confidence interval
  • Percentage‑based sampling options
• This capability integrates with existing eDiscovery workflows.
• No changes are made to permissions, access controls, or review set behaviors.
• No features are being removed or replaced.
• The feature will be available by default when it reaches your tenant.

[What you can do to prepare]

No prerequisites are required, and no action is needed to prepare for this change. The capability will become available automatically.

If helpful, you may consider:

• Reviewing internal eDiscovery workflows.
• Updating training or documentation to reflect how sampling can support early validation of search results.

Learn more about eDiscovery: Learn about eDiscovery solutions | Microsoft Learn

Learn more about adding search results to review set: Add search results to a review set in eDiscovery | Microsoft Learn

[Compliance considerations]

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

Updated February 24, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

We’re introducing context preservation behavior in Microsoft Teams that restores recent conversation and view state when users return after a brief period.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It’s associated with Roadmap ID 557184.

When this will happen:

Targeted Release: Rollout begins early April 2026 and is expected to complete by mid-April 2026. 

General Availability (Worldwide): Rollout begins mid-April 2026 (previously mid-March) and is expected to complete by late April 2026 (previously late March)

How this affects your organization:

Who is affected:

• All Microsoft Teams users

What will happen:

• When users leave a chat, channel, or Quick View and return within 30 minutes,
  • Their previously selected tab is restored
  • Any opened side panel is restored
  • The layout is restored
  • In Quick View, the previously selected message is restored
• This supports short interruptions and quick context switching, allowing users to resume work without resetting their workspace
• When users return after more than 30 minutes:
  • The conversation or view opens in the default layout 
  • Prior context is not restored
• The feature is enabled by default
• There are no new admin controls or configuration options

What you can do to prepare:

No action is required

Compliance considerations:

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

• The tools are already available to help you to proactively inventory, monitor, and apply updated certificates to your Windows Server devices.
• June 2026: The 2011 Secure Boot certificate authorities (CAs) begin expiring.

1. Inventory and prepare your environment.  
2. Monitor and check your devices for Secure Boot status.  
3. Apply any needed OEM firmware updates before updating certificates.  
4. Plan and pilot Secure Boot certificate deployments.  
5. Troubleshoot issues. 

• Get started today with the recommended approach in Windows Server Secure Boot playbook for certificates expiring in 2026.
• Prepare your servers for Secure Boot certificate updates.
• Join the online event Secure Boot certificate updates explained – Microsoft Technical Takeoff on March 9, 2026. 
• To manage Secure Boot certificate updates on Windows client, see Secure Boot playbook for certificates expiring in 2026. 
• For the latest information, bookmark https://aka.ms/GetSecureBoot as your landing page for resources to help you with Windows Secure Boot certificate updates.

[Introduction]

We’re introducing two new remediation actions as part of the Email table in Advanced Hunting that help security operations (SecOps) teams respond more quickly during investigations:

• Attachment block action
• Top-level URL domain block action

These actions let SecOps teams move directly from detection to mitigation within the same workflow, reducing response time and operational friction when addressing malicious campaigns.

These actions will be available through Take action if the query returns all the required columns.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2026 and expect to complete by the end of March 2026.

[How this affects your organization:]

Who is affected:

• Security operations teams and administrators using Advanced Hunting in Microsoft Defender for Office 365
• This feature is available to customers with Microsoft Defender for Office 365 Plan 2 or Microsoft 365 E5 licenses.

What will happen:

• Security teams can block malicious email attachments directly from Advanced Hunting results.
• Security teams can block top-level URL domains associated with phishing or malicious campaigns.
• Remediation actions are available in the Advanced Hunting “Take action” wizard.
• The feature is enabled by default; no configuration changes are required.
• There is no impact to user workflows unless a security action is taken.

Note:

• Attachment entries in the Tenant Allow/Block List are supported only if the query results include the Attachment column by joining with the EmailAttachmentInfo table on NetworkMessageId.
• Submit to Microsoft may be unavailable if required columns are missing. To resolve this issue, select Show empty columns before you select Take actions.

What you can do to prepare:

• No action is required.
• Review security investigation and response procedures to include the new remediation options.
• Inform SecOps teams of the updated Advanced Hunting capabilities.

Learn more: Take action on advanced hunting query results in Microsoft Defender XDR – Microsoft Defender XDR | Microsoft Learn (documentation will be updated before rollout)

Compliance considerations:

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

• The Emoji 16.0 release introduces a small, thoughtfully curated set of new emojis, one from each major category. Each emoji carries timeless symbolism and practical versatility. These new emojis now appear in the emoji panel.
• A built‑in network speed test is now available from the taskbar. You can open it from the Wi‑Fi or Cellular Quick Settings, or by right-clicking the network icon in the system tray. The speed test opens in the default browser and measures Ethernet, Wi‑Fi, and cellular connections.
• You can now control pan and tilt for supported cameras in the Settings app. The controls appear under Settings > Bluetooth & devices > Cameras, in the “Basic settings” section for your selected camera.
• Windows now brings System Monitor (Sysmon) functionality natively to Windows. Sysmon helps you capture system events for threat detection, and you can use custom configuration files to filter the events you want to monitor. Windows writes captured events to Windows Event Log, which allows security tools and other applications to use them.

• Windows 11, version 26H1: KB5077239
• Windows 11, versions 25H2 and 24H2: KB5077241