Microsoft Roadmap, messagecenter and blogs updates from 10-03-2026

Updated March 9, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

We’re enhancing offline functionality in the new Microsoft Outlook for Windows. This update (Microsoft 365 Roadmap ID 496371) enables users to add file attachments while composing emails offline, improving productivity for those working without an internet connection.

When this will happen

• Targeted Release (Worldwide): Rollout begins in late October 2025 and is expected to complete by late March 2026 (previously late November 2025).
• General Availability (Worldwide): Rollout begins in early April 2026 (previously early January) and is expected to complete by late April 2026 (previously early February).
• General Availability (GCC): Rollout begins in early May 2026 (previously mid-February) and is expected to complete by late May 2026 (previously late February).

How this affects your organization

Users with offline mode enabled in the new Outlook for Windows will be able to attach files to draft emails while offline. These emails, including attachments, will be sent automatically once the device reconnects to the internet.

This feature will be on or off by default based on your current configuration of the OWAMailboxPolicy-OfflineEnabledWin policy. No changes will be made to existing configurations.

What you can do to prepare

To enable this functionality, ensure the following settings are configured in the new Outlook under Settings > General > Offline:

• Enable offline email, calendar, and people
• Include file attachments

Admins can manage this feature using the OWAMailboxPolicy-OfflineEnabledWin mailbox policy. Learn more at Set-OwaMailboxPolicy.

Caption i. Offline editing can be enabled or disabled in Settings > General > Offline

Compliance considerations

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

Updated March 9, 2026: We have updated the content. Thank you for your patience.

Introduction

The Outlook Mobile team is updating the release for Data Loss Prevention (DLP) Policy Tips & Override for Outlook Mobile. A number of improvements have been made to the initial scope of this rollout, along with some unforeseen challenges that will be listed in detail.

This message is associated with Microsoft 365 Roadmap ID 496146.

When this will happen

Production Build App Store Release for Android and iOS: We are targeting April 6th to submit to the app store, and on average it can take up to a week for Apple and Google to then distribute that build via the App Stores.

How this affects your organization

The following updates have been made to this DLP rollout for Outlook Mobile:

1. [added] Custom oversharing dialog support
2. [added] Custom policy information
3. [added] Policy tip evaluation performance improvements
4. [added] Attachment scanning
5. [added] Intune control for Android and iOS to turn Data Leak Prevention on or off (default is set to OFF)
6. [temporarily removed] External recipient rule validation

Due to unique challenges with external recipient rule validation we are removing External Recipient rule validation from this release pending changes to the implementation.

After feedback we have added an Intune control that is defaulted to OFF to give your organization the opportunity for validation and user training prior to enabling DLP on Android and iOS. Documentation links for “DLP on Android and iOS” and “Intune controls for DLP in Mobile” will be provided in an update soon.

What you can do to prepare

Please prepare to validate your organization’s rules in a test environment prior to enabling Data Leak Prevention on Mobile, and where possible provide training for users which can greatly improve their success and overall experience with policy tips and rules.

[Introduction]

We’re improving external collaboration in Microsoft Teams by enabling file attachments and Loop sharing in 1:1, group and meeting chats with external users. This update improves the collaboration experience for Files and Loop and add a new control for IT admins. Specifically, Files and Loop components will be shared automatically with external participants in the chat and won’t require any action by the sender by default. Additionally, Entra B2B Guests in your organization will be able to attach and share files from their home tenant’s OneDrive or SharePoint. 

This change applies to Teams for Windows desktop, Mac desktop, and web and is associated with Roadmap ID 492625.

Screenshot 1: Files are automatically provisioned.

Screenshot 2: Files shared have an external label and always open on Web.

[When this will happen:]

• Targeted Release: Rollout begins late October 2025; expected to complete by mid-November 2025
• General Availability (Worldwide): Rollout begins mid-January 2026

[How this affects your organization:]

Who is affected:

All Microsoft Teams users in your organization who participate in 1:1, group, or meeting chats with external users, including guest and Teams for Free users.

What will happen:

With this update:

• Unless the user chooses to share File and Loop by pasting links, external users in chat will be automatically provisioned to allow frictionless collaboration.
• You can disable automatic provisioning and have the user change permissions manually by using policy controls.
• If disabled, users will have to manually provision the file to users in the chat.
• Guest users will be able to upload files from their home tenant’s OneDrive and SharePoint.
• Files shared by external users will continue to display an External tag for clarity.
• Loop components will now be rendered inside external chats in Teams.
• Recipients will access File and Loop components as B2B guests within the resource tenant. If they are not already added as guests, they will need to give consent and might need to complete MFA, depending on your company’s B2B policy, before viewing the chat content.

• No action is required to enable the feature—it will be automatically available as the rollout progresses.
• To disable the automatic provisioning behavior for files and loops set the AutoShareFilesInExternalChats attribute of TeamsMessagingPolicy to Disabled. Learn more: Set-CsTeamsMessagingPolicy documentation.
• To provide seamless Loop access experience for external users, we recommend turning on Entra B2B Guest Access. Refer to: Microsoft Entra B2B integration for SharePoint & OneDrive – SharePoint in Microsoft 365 | Microsoft Learn.
• For configuration guidance, refer to: Set-CsTeamsFilesPolicy documentation (documentation will be updated before rollout).

Compliance considerations

Updated March 9, 2026: We have updated the timeline. Thank you for your patience. 

Microsoft is introducing a new capability in Teams that enables Channel Agent to orchestrate tasks with select third-party Model Context Protocol (MCP) servers, including GitHub, Asana, and Atlassian (JIRA). This integration supports collaborative workflows that reflect real human teamwork, allowing agents to transparently reason through tasks and gather information across tools. This change helps reduce manual switching between apps and improves task completion efficiency—all within the familiar Teams environment.

A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 515466.

• Targeted Release (Worldwide): Begins in mid-November 2025 and is expected to complete by end of July 2026 (previously late January).

Who is affected: Microsoft 365 tenants using Teams and Channel Agent integrations.

What will happen:

• Channel Agent will be able to collaborate with Model Context Protocol (MCP) servers like GitHub, Asana, and Jira.
• Users can ask Channel Agent questions and receive coordinated responses across tools:

          Screenshot 1

Screenshot 2



• The feature will be available in preview and requires admin enablement.
• A Microsoft 365 Copilot license is required.
• There is no impact unless enabled by tenant admins.

What you can do to prepare

• Enable Channel Agent usage in Teams for your tenant.
• Allow apps that integrate with Model Context Protocol (MCP) servers such as GitHub, Asana, or Jira.
• Ensure users who need access have a Microsoft 365 Copilot license.
• Review internal documentation and update helpdesk guidance as needed.

Compliance considerations

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

Updated March 9, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction:]

Microsoft Edge for Business will soon support summarization and contextual grounding with Microsoft 365 Copilot Chat. This enhancement enables users to ask Copilot questions about multiple open browser tabs, Microsoft 365 documents (such as Word, Excel, PowerPoint), and YouTube videos directly from the Edge side pane.

This message is associated with Microsoft 365 Roadmap ID 496364, 499423, and 499424.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in mid-February (previously mid-March).

[How this affects your organization:]

Who is affected: Users signed in to Microsoft Edge for Business with their Entra ID and who have access to Microsoft 365 Copilot.

What will happen:

• Users will be able to ask Copilot questions about open browser tabs, Microsoft 365 documents, and YouTube videos.
• The feature will be off by default.
• If Copilot is restricted from accessing page content via Data Loss Prevention (DLP) or the EdgeEntraCopilotPageContext policy, it will be suppressed to maintain DLP integrity.
• Existing DLP and policy configurations will be respected.

[What you can do to prepare:]

• This rollout will happen automatically by the specified date; no admin action is required before rollout.
• Ensure users who need this capability have access to Microsoft 365 Copilot.
• Ensure your tenant is configured to support Microsoft 365 Copilot and that eligible users meet all licensing prerequisites, including Entra ID sign-in and applicable Microsoft 365 service plans.
• Review your current DLP and Edge policy configurations to determine potential impact.
• Notify users about this upcoming capability.
• Update internal documentation if needed.

Learn more:

• Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn
  
• Microsoft Edge – Policies | Microsoft Edge | Microsoft Learn
  

[Compliance considerations:]

Updated March 9, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

As AI agents become deeply embedded in enterprise ecosystems, they are evolving beyond simple tools or workflows into an autonomous digital workforce. These agents can interpret user intent, access and manipulate enterprise data, execute actions on behalf of users, and even make real-time decisions. In many ways, they operate like human insiders only with machine-speed data processing capabilities.

To govern and protect these agents effectively, organizations require visibility into their activities, contextual understanding of their actions, and the ability to flag or block risky behavior. Now, Insider Risk Management can be extended to detect and remediate potentially risky agent activities.

Features:

• Copilot Studio & Azure AI Foundry Integration: Detect potentially risky activities of agents hosted on Copilot Studio, Azure AI Foundry, and Agent 365 platforms
• Risky AI Usage Policies: Define and enforce policies specific to AI agents accessing sensitive data or performing high-risk actions.
• IRM for Agent Users: Extend IRM in Purview to govern agent-driven workflows and protect organizational data.

This message is associated with Microsoft 365 Roadmap ID 516032.

[When this will happen:]

• Public Preview: We will begin rolling out early December 2025 and expect to complete by mid-January 2026.
• General Availability (Worldwide): We will begin rolling out early May 2026 (previously late March) and expect to complete by late May 2026 (previously late April).

[How this affects your organization:]

On the Overview page in the Insider Risk Management solution, you will be able to access the overall risk profile of agents deployed in your organization.

The Risky Agents policy will be automatically deployed for all agents hosted on Copilot Studio and Azure AI Foundry across your organization. Alerts from this policy will be generated when an agent’s activity exceeds the thresholds configured in this automatically deployed Risky Agents policy. These alerts can be found under Agents > Alerts on the left pane.

[What you can do to prepare:]

• Review the public facing documentation to learn more about this exciting new offering: Learn about Insider Risk Management policy templates | Microsoft Learn
• Review the new Insider Risk Management interface in the Microsoft Purview portal, which now includes separate sections for Users and Agents.
• Review and tune the Risky Agents policy based on your organization’s requirements.
• If you don’t wish to track agent activities, you can delete the automatically deployed Risky Agents policy. 

Learn more:

• Help dynamically mitigate risks with Adaptive Protection | Microsoft Learn
• Create and manage Insider Risk Management policies | Microsoft Learn
• Learn about Insider Risk Management policy templates | Microsoft Learn

Updated March 9, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Copilot in PowerPoint lets you create, edit, and refine presentations through natural conversation, directly in your presentation. You can start a new presentation or build on an existing one, asking Copilot to generate slides, update content, improve layouts, and polish design—while preserving formatting, structure, and branding. Available to Microsoft 365 users.

For Microsoft 365 Copilot-licensed users, Copilot can also connects to your brand kit so you can apply branded templates, insert brand‑approved images, and check for brand compliance.

Screenshot – Entry point for Edit with Copilot in PowerPoint

This message is associated with Roadmap IDs 548520 and 548646.

[When this will happen:]
General Availability (Worldwide): Rollout will begin mid-February 2026 and complete by mid-March 2026.

[How this will affect your organization:]

Who is affected:
Users in your organization who use the PowerPoint web application and have Microsoft 365 Copilot licenses.

What will happen:

• Users will gain access to Copilot editing capability in Microsoft 365 Copilot for PowerPoint for the web.
• Users can interact with Copilot Chat to edit and refine presentation content.
• Formatting, structure, and branding will be preserved.
• Users can use Enterprise assets to further enhance the presentation.
• Edit with Copilot is available to all eligible users by default; no action is needed by Admins.
• Note: Copilot editing capability is part of Copilot Chat within PowerPoint for the web and is not a standalone feature.

[What you need to do to prepare:]
No action is required.

• Communicate availability of Copilot editing capability to helpdesk staff and users.
• Encourage users to explore the feature to improve presentation workflows.
• Review and update internal documentation if you provide guidance on PowerPoint for the web or Copilot usage.

[Compliance considerations:]

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

Updated March 9, 2026: We have updated the content. Thank you for your patience. 

Introduction

To reduce notification noise and improve signal quality, Microsoft will disable Teams Meeting Recording (TMR) expiration notification emails. Customer feedback indicates these emails generate high volume with minimal engagement. Only the email notifications are being removed; recording expiration and deletion behavior remains unchanged.

When this will happen

June 1, 2026

How this affects your organization

Who is affected:

• All Microsoft 365 tenants
• Users who receive Teams meeting recording expiration emails

What will happen:

• Users will no longer receive email notifications when a Teams meeting recording expires.
• Recording expiration and deletion policies remain unchanged.
• No admin action or policy updates are required.
• This change is enabled by default.

What you can do to prepare

• No action is required.
• Optionally notify users and helpdesk teams of this change.
• Update internal documentation if it references expiration emails.

Compliance considerations

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

1. Open the offline profile editor in your canvas app or model-driven app.
2. Select the Filter option for an entity.
3. Under Related rows or Custom filter, choose Edit FetchXML or View FetchXML to open the editor.

[Introduction]

Microsoft Agent 365 will become Generally Available (GA) on May 1, 2026. This milestone reflects extensive customer feedback and validation through the Frontier early-access program, where participating organizations have helped improve product quality, readiness, and overall experiences. GA enables broader adoption of Agent 365 while allowing Frontier participants to continue shaping future innovations.

[When this will happen:]

• General availability: May 1, 2026
• Frontier program: Continues without interruption

[How this affects your organization:]

Who is affected:

• Customer tenants currently enrolled in the Agent 365 Frontier program
• Administrators planning or evaluating Agent 365 deployment.

What will happen:

• Agent 365 will be Generally Available starting May 1, 2026.
• Customers already participating in Frontier will retain their access and continue to receive early-access features.
• Frontier will remain the channel for piloting new capabilities and providing feedback before features reach GA.
• Trial and paid options for Agent 365 will be introduced, with transition guidance shared prior to GA.

[What you can do to prepare:]

• No immediate action is required for customers currently participating in Frontier.
• Learn about today’s announcements https://aka.ms/AIBuiltforWork
• Review Agent 365 deployment guidance and technical documentation to prepare for GA rollout: Getting Started with Microsoft Agent 365
• Plan internal readiness activities (for example, admin training or helpdesk awareness) ahead of May 1, 2026.
• Watch for upcoming communications detailing trial availability, licensing, and paid options

[Introduction]

We’re enhancing Microsoft 365 Copilot Chat by enabling users to draft, edit, and send Outlook email directly within Copilot Chat. When Microsoft 365 Copilot identifies an email‑writing intent, it will open an embedded Outlook compose form. This improvement reduces context switching and streamlines everyday communication workflows.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in early March 2026 and is expected to complete by early April 2026.

[How this will affect your organization]

Who is affected

• Users licensed for Microsoft 365 Copilot
• Users with Exchange Online mailboxes
• Users accessing Copilot Chat on desktop (“big screen”)

What will happen

• When users ask Copilot to draft an email, an embedded Outlook compose form will appear directly within Copilot Chat: 

  

• Users will be able to:
  • Edit the email content
  • Modify recipients
  • Send the email from within Copilot Chat
  • Open the draft in Outlook to continue editing
• The feature will be on by default for all eligible users.
• Availability:
  • Available: Copilot Chat desktop app
  • Not available: Copilot Chat mobile app or chat sidebar
• Existing Outlook and Exchange Online policies—including DLP—continue to apply.
• No admin configuration changes or new controls are introduced.

Note: Access to this feature requires an active Microsoft 365 Copilot license.

[What you can do to prepare]

No action is required.

You may choose to:

• Inform your helpdesk and end users about this new email‑drafting experience in Copilot Chat.
• Update internal documentation if you describe Copilot Chat workflows.
• Review which users in your organization are licensed for Microsoft 365 Copilot.

[Compliance considerations]

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

• SLA violations: Receive notifications when work items in a queue breach their defined service level agreements.

• Devices will start receiving hotpatch updates by default with the May 2026 Windows security update. 
• The tenant setting to opt out of hotpatch updates is scheduled to go live on April 1, 2026. 

• Hotpatch updates 
• Hotpatch for Windows client now available 
• Hotpatching now available for 64-bit Arm architecture 
• Hotpatch for client: Frequently asked questions 
• Transforming security and compliance at Microsoft 
• Hotpatch efficiency unlocked: Smaller update size 
• Inside hotpatch updates for Windows (YouTube video) 
• Hotpatching 101: Enable virtualization-based security (VBS) (YouTube video) 

The In development for Microsoft Intune page in our documentation has been updated.

[How this will affect your organization:]

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You will start seeing these changes in the next month or in a subsequent release.

[What you need to do to prepare:]

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

[Introduction]

We’re expanding model choice in Microsoft 365 Copilot with the addition of Anthropic Claude Sonnet for users with a Microsoft 365 Copilot license. Claude Sonnet is available in Copilot Chat in Frontier, alongside the latest OpenAI models, giving users the flexibility to choose the model best suited for their tasks. This expansion reflects our commitment to delivering the latest AI innovation for work—while maintaining the security, compliance, and privacy standards customers expect from Microsoft.

[When this will happen:]

• Frontier availability: Claude Sonnet is available now in Frontier.
• General availability (web/desktop/macOS/mobile): Rolling out gradually; expected completion late March 2026.

[How this affects your organization:]

Who is affected:

• Users with a Microsoft 365 Copilot license

Who is not affected:

• Tenants in EU/EFTA and the UK
• Government clouds (GCC, GCC High, DoD)
• Sovereign clouds For these tenants, Anthropic models are not available

For these tenants, Anthropic models are not available and no model option will be shown.

What will happen:

• Microsoft 365 Copilot licensed users will be able to select Claude Sonnet as an option in the model selector within Copilot Chat.
• In regions where Anthropic is configured as a subprocessor and is set to Off by default, admins can choose to opt in to make Anthropic models available for their organization.
• Enterprise Data Protection for Microsoft 365 Copilot continues to apply, with no changes to existing protections.
• Anthropic operates as a Microsoft subprocessor under the Microsoft Data Protection Addendum and Product Terms.
• Anthropic models are currently excluded from EU Data Boundary and in‑country processing commitments.

[What you can do to prepare:]

• No action is required. However, it’s recommended that you review internal guidance and communicate to users that availability.
• If your tenant is in a region where Anthropic is Off by default, review the subprocessor setting and opt in if you want Anthropic models available to users. Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft Learn
• Learn more about Anthropic as a Microsoft subprocessor: Anthropic as a subprocessor for Microsoft Online Services

[Introduction]

We’re introducing new policy configuration options in Microsoft Purview Data Loss Prevention (DLP) to help organizations enhance data security across inline network traffic and Edge for Business browser. These updates provide administrators with more granular controls for discovering and protecting sensitive data in unmanaged cloud apps, and additional options for defining enforcement conditions and user notifications.

This message is associated with Microsoft 365 Roadmap ID 557976.

[When this will happen:]

• Public Preview: Rollout will begin late March 2026 and is expected to complete by late April 2026.
• General Availability (Worldwide): Rollout will begin late April 2026 and is expected to complete by late May 2026.

[How this affects your organization:]

Who is affected:

• Administrators managing Microsoft Purview collection policies and DLP policies
• Organizations using Purview network data security or Purview browser data security in Edge for Business
• Users accessing unmanaged cloud apps through network traffic or Edge for Business (when policies are configured)

What will happen:

• Administrators can scope Purview collection policies for unmanaged cloud apps based on the presence of sensitivity labels.
• Administrators can use “URL contains text” as a condition or exception in Purview DLP policies.
• Administrators can configure email notifications to alert users when activities are blocked.
• Features are available by default once rolled out but require admin configuration to take effect.
• Existing policies are respected and not changed automatically.

[What you can do to prepare:]

No action is required before rollout.

• Review the new options in the Microsoft Purview portal.
• Update existing policies if additional control is desired.
• Inform other data security administrators of these updates.
• Decide whether to enable end-user email notifications.

Learn more:

• Microsoft Purview collection policies | Microsoft Learn
• Microsoft Purview data loss prevention | Microsoft Learn
• Microsoft Purview network data security | Microsoft Learn
• Microsoft Purview browser data security in Microsoft Edge for Business | Microsoft Learn

[Compliance considerations:]

This update enhances existing compliance and DLP capabilities by adding new configuration options. Review internal compliance requirements to determine whether policy updates are appropriate.

[Introduction]

Security Store is now integrated into Microsoft Purview Data Loss Prevention (DLP), providing administrators with a streamlined, in-product experience to discover, purchase, and enable a curated set of partner integrations. This change simplifies how organizations extend Purview capabilities—especially network data security—by managing partner integrations directly from the Purview portal.

This message is associated with Microsoft 365 Roadmap ID 557977.

[When this will happen:]

• General availability (Worldwide): Rollout will begin in late March 2026 and is expected to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators managing Microsoft Purview DLP
• Data security and compliance administrators

What will happen:

• Once rolled out, you can access the Security Store from the Data Loss Prevent solution in Purview.



• Admins can discover, purchase, and enable supported partner integrations.
• The feature is available by default once it reaches your tenant.
• There is no impact to users unless an integration is enabled.
• Existing Purview DLP policies are not changed.

[What you can do to prepare:]

No action is required.

• Inform data security administrators about the new capability.
• Review available integrations once the Security Store appears.

Learn more:

• Discover, buy, and deploy security solutions and agents
• Learn about Microsoft Purview Network Data Security

[Compliance considerations:]

[Introduction]

Copilot highlights in Viva Glint provides AI‑generated, structured summaries of employee survey results directly within supported Glint reports. The feature appears as a collapsible card at the top of the report and surfaces key insights—including strengths, opportunities, team‑level differences, and trends—to help managers and leaders move from data to action faster. Copilot highlights will be automatically available for users who have access to Copilot in Viva Glint, with no additional configuration required.

This message is associated with Microsoft 365 Roadmap ID 558111.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in early April 2026 and is expected to complete by late April 2026.

[How this affects your organization]

Who is affected

• Organizations using Viva Glint
• Admins who manage Copilot in Viva Glint access in the Microsoft 365 admin center
• Users with Glint roles that include dashboard and reports access when Copilot in Viva Glint is enabled
• Users must have a license for Viva Glint, Microsoft Viva Suite, or Microsoft Viva Workplace Analytics and Employee Feedback to access Copilot highlights.
• A Microsoft 365 Copilot license is not required to use Copilot in Viva Glint or Copilot highlights.

What will happen

• Copilot highlights will appear automatically as a collapsible card at the top of Team Summary and Executive Summary reports.
• There will be no separate toggle to configure; the feature will be enabled automatically when Copilot in Viva Glint is turned on.
• Summaries may include up to three structured sections:
  • Overview and key outcomes: Response rate, key outcome trend, top strengths
  • Team scores: Team breakdowns, increases/decreases, high/low scoring teams
  • Top opportunities: Score, benchmark comparison, risk classification
• Multilingual summaries will be generated in each user’s configured Viva Glint dashboard language.
• Interpretation rules will surface only notable findings based on respondent group size.
• No new data sources will be introduced; summaries will use existing report data.
• Existing access policies, data permissions, and confidentiality thresholds will remain unchanged.
• No changes will be made to dashboard access, user permissions, or privacy protections.

[What you can do to prepare]

• Verify Copilot access settings:
  • Go to admin.microsoft.com → Settings → Viva → Viva Glint → Manage settings for Microsoft Copilot in Viva Glint.
  • Confirm Copilot in Viva Glint is turned on at the tenant level.
  • If needed, adjust access policies to limit Copilot visibility to specific users or groups.
• Inform report viewers: Let managers and leaders know that AI‑generated summaries will appear at the top of supported reports. Users can collapse the card if they prefer to review data directly.
• No additional configuration is required: Copilot highlights will be automatically available when Copilot in Viva Glint is enabled.
• Learn more: Manage Viva Glint Copilot access in the Microsoft 365 admin center | Viva Glint | Microsoft Viva | Microsoft Learn

[Compliance considerations]

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

[Introduction]

Outlook for iOS and Android is adding support for recommended and automatically applied sensitivity labels when you compose an email on your mobile device. With this release, we are extending Recommended Labels to Outlook mobile (iOS and Android), providing the same labeling experience users already have in Outlook on the desktop and web. For recommended labels, you’ll see a prompt to review and apply the suggested label. For automatic labels, they will be applied without needing any action from you. This ensures alignment with your organization’s Microsoft Purview Information Protection labeling policies when sensitive information is detected.

This message is associated with Microsoft 365 Roadmap IDs 557253 and 557254.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users who compose email in Outlook for iOS and Android
• Organizations with automatic or recommended sensitivity labeling policies configured in Microsoft Purview Information Protection

What will happen

• This update extends Recommended Labels to Outlook mobile (iOS and Android), enabling recommended label prompts when sensitive information is detected.
• Users see recommended sensitivity labels when Microsoft Purview identifies sensitive information during email composition.
• Users are prompted to review and apply recommended labels.
• Automatic labels are applied without user action when required by policy.
• The feature is on by default for organizations with existing Purview sensitivity labeling policies.
• No changes are made to Purview policy configuration, scopes, or publishing.
• Outlook desktop and Outlook on the web are not affected; this update adds support for Outlook mobile only.

Figures 1–3. Examples of users being prompted to review and apply recommended sensitivity labels in Outlook mobile.

[What you can do to prepare]

No action is required if your organization already uses automatic or recommended sensitivity labeling policies in Microsoft Purview Information Protection. Outlook mobile support is added automatically.

Admins may choose to:

• Review existing labeling policies in the Microsoft Purview portal to confirm correct scoping and label publishing.
• Ensure sensitivity labels are published to users who rely on Outlook mobile.
• Communicate this change to helpdesk or support teams.
• Review Microsoft Learn documentation for minimum supported Outlook mobile versions: Sensitivity label capabilities in Outlook – Minimum versions for sensitivity labels in Office apps | Microsoft Purview | Microsoft Learn

[Compliance considerations]

[Introduction]

We’re introducing Microsoft Entra passkeys on Windows to enable phishing-resistant sign-in to Entra-protected resources. This update allows users to create device‑bound passkeys stored in the Windows Hello container and authenticate using Windows Hello methods (face, fingerprint, or PIN). It also expands passwordless authentication to Windows devices that aren’t Entra‑joined or registered, helping organizations strengthen security and reduce reliance on passwords.

[When this will happen]

• Public preview: Rolling out from mid-March 2026 through late April 2026
• General Availability
  • Worldwide: Mid‑March 2026 to mid‑April 2026
  • GCC: Mid-April 2026 to mid-May 2026
  • GCC High: Mid-April 2026 to mid-May2026
  • DoD: Mid-April 2026 to Mid-May 2026

[How this affects your organization]

Who is affected

• Organizations using Microsoft Entra ID whose users sign in from Windows devices, including corporate‑managed, personal, and shared PCs.

What will happen

• There is no impact to your organization unless you opt in.
• Microsoft Entra passkeys on Windows will be available as a phishing‑resistant, passwordless sign‑in option for Entra‑protected cloud resources.
• Users will authenticate with Windows Hello (face, fingerprint, or PIN).
• Users can use passkeys on Windows devices that are not Entra‑joined or registered, enabling use on personal, shared, and unmanaged PCs.
• Users can sign-in to multiple Entra accounts on the same Windows device, with each account registering its own passkey.
• Passkeys on Windows are device‑bound and do not sync across devices; each device requires separate registration per Entra account.
• Windows Hello for Business remains recommended for managed, Entra‑joined or registered devices; passkeys supplement unmanaged device scenarios and do not support device sign‑in.
• Existing Conditional Access and authentication strength policies continue to apply with no required configuration changes unless you choose to enable passkeys.
• Users can’t register a passkey on Windows if a Windows Hello for Business credential already exists for the same account and container. This block may not apply once the user exceeds 50 total credentials across passkeys (FIDO2), Windows Hello for Business, and Mac Platform Credentials.  

[What you can do to prepare]

If you want to enable Entra passkeys on Windows during public preview:

• Enable the Passkeys (FIDO2) authentication method in Authentication Methods policies.
• Create a passkey profile and configure:
  • Attestation enforcement: Disabled
  • Key restrictions: Enabled
  • Allowed AAGUIDs (required during preview):
    • Windows Hello Hardware Authenticator: 08987058-cadc-4b81-b6e1-30de50dcbe96
    • Windows Hello VBS Hardware Authenticator: 9ddd1817-af5a-4672-a2b9-3e3dd95000a9
    • Windows Hello Software Authenticator: 6028b017-b1d4-4c02-b4b3-afcdafc96bb2
    • Note: During Public Preview, you must explicitly add these Windows Hello AAGUIDs to the allowed list.
• Assign the passkey profile to appropriate groups.
• Validate Conditional Access and authentication strengths policies to ensure they support passkey authentication.
• Communicate with pilot users about supported scenarios and enrollment steps.
• Update internal documentation if your organization tracks approved authentication methods.

If you do not plan to participate in the public preview, no action is required.

Learn more: How to enable passkey (FIDO2) profiles in Microsoft Entra ID (preview) | Authentication | Microsoft Entra ID | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We are adding AI citations analytics to SharePoint to help site owners understand how their SharePoint documents, news posts, and pages are referenced by Microsoft Copilot and other AI agents. These insights will help organizations track content value, identify high‑impact information, and understand how AI‑powered workflows use SharePoint content. Users must have the appropriate Microsoft Copilot licenses to use the AI features that may generate citations.

This message is associated with Microsoft 365 Roadmap ID 480725.

[When this will happen]

General Availability (Worldwide): Rollout will begin in mid‑April 2026 and will complete by mid-May 2026.

[How this affects your organization]

Who is affected:

• SharePoint Online site owners, content authors, and admins.
• Users who have Microsoft Copilot licenses for the experiences that may generate citations.

What will happen:

The following updates will appear in SharePoint:

• SharePoint Popular content in Site Usage will display documents, news posts, and pages ranked by how often they are cited by Copilot or AI agents.
• SharePoint page analytics will include a new Total citations card showing the number of times a page or news post is referenced in Copilot or agent responses.
• SharePoint file statistics will include a new AI citations metric displayed alongside existing metrics such as views and viewers.
• A new AI citations analytics page will appear under Site Usage. It will provide:
  • The number of users who consume site content through Copilot and AI agents.
  • The total number of citations for the site.
  • The most frequently cited documents, news posts, and pages.

Supported agents include Microsoft 365 Copilot, Copilot in Word, Excel, PowerPoint, Teams, Loop, Planner, SharePoint Knowledge Agent, and SharePoint custom agents.

This feature will be on by default and will not require admin action to enable.

Screenshot 1 – AI citations aggregated across site content in the Site analytics view: 

Screenshot 2 – AI citations shown for an individual SharePoint page or news post in Page analytics:

[What you can do to prepare]

No admin action is required before the rollout.

You may want to:

• Inform site owners and content authors about the new analytics.
• Review your SharePoint usage and analytics processes to understand how the new AI citation metrics may support governance, content lifecycle planning, and content strategy.
• Update internal documentation or training materials.
• Provide guidance to users on Copilot licensing requirements if your organization centrally manages those licenses.

[Compliance considerations]

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

Updated March 9, 2026: We have updated the timeline. Thank you for your patience.

Microsoft Purview Communication Compliance is improving the capabilities and customization of policy alerts.

This message is associated with Microsoft 365 Roadmap ID 181825.

[When this will happen:]

Public Preview: We will begin rolling out October 2026 (previously late July 2025) and expect to complete by end of October 2026 (previously mid-Aug 2025).

General Availability (Worldwide): We will announce this timeline in a future update.

[How this will affect your organization:]

Communication Compliance is improving the capabilities and customization of policy alerts. Admins will be able to customize the alert frequency per policy as well as adjust the email alerts frequency and recipients within the policy creation wizard by navigating to the new alerts page.

This new feature is available by default.

[What you need to do to prepare:]

Microsoft Purview Communication Compliance provides the tools to help organizations detect business conduct and regulatory compliance violations (e.g. SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy.

You can access the Communication Compliance solution in the Microsoft Purview compliance portal. 

Learn more: 

• Learn about communication compliance 

• Create and manage communication compliance alert policies | Microsoft Learn