Microsoft Roadmap, messagecenter and blogs updates from 14-07-2026

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

 What and Why

We’re introducing a new capability that allows users with a Microsoft 365 Copilot license to scope and control Copilot Chat responses by selecting specific content sources. This enhancement is designed to improve the relevance and accuracy of Copilot responses by limiting them to user-selected sources, aligning with customer feedback for more transparent and customizable AI interactions.

This message is associated with Microsoft 365 Roadmap ID 496596

Rollout Schedule

General Availability (Worldwide): Rollout will begin mid-July 2026 (previously mid-June) and is expected to complete by late July 2026 (previously end of June).

Impact on Your Organization

• Who is affected:
  • Users with a Microsoft 365 Copilot license.
• What will happen:
  • Users will see a new option to select content sources when using Copilot Chat.
  • Copilot responses will be scoped only to the selected sources, improving control and precision.
  • This feature will follow a standard rollout and is enabled by default.
  • There is no impact to admin settings or policies.
  • No changes to existing Copilot behavior unless users actively select sources.

Action Required/Recommendations

• No admin action is required.
• This feature does not impact admin controls or require configuration.
• We recommend:
  • Informing helpdesk staff of this new user-facing capability.
  • Updating internal documentation if you provide guidance on Copilot usage.

Compliance Considerations

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

Updated July 13, 2026: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience.

This MC post is associated with Roadmap ID 500872.

[Introduction:]

To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies.

This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app.

[When this will happen:]

• Public Preview: Begins in early December 2025 (previously late November 2025), completes by late December 2025.
• General Availability (Worldwide): Begins in early August 2026 (previously early July), completes by late August 2026 (previously late July).

[How this affects your organization:]

Who is affected:

Copilot Dashboard users with full company-level data access, including senior leaders (as identified in Entra ID), admin-assigned company-level users, delegates with company-level access, as well as global analysts and admins. 

Note: Group managers with data access limited to their own teams will not have access to this feature.

What will happen:

• Users will be able to export de-identified, row-level Copilot usage metrics from the dashboard.
• The dataset includes weekly, user-level metrics from the past six months.
• The export supports Copilot usage analysis across apps (such as Word, Excel, Teams), and includes two attributes: Organization, and Job function.
• Organizations can use the data to track usage patterns, generate insights to inform adoption strategies, optimize licensing, and measure ROI.
• The feature is enabled by default for eligible users.
• Admins can manage access via Viva Feature Access Management (VFAM) settings, under Module: Viva Insights; Feature: Copilot Metrics Export.
• No impact to user workflow unless accessed by eligible users.

Screenshot 1 – View of the new Microsoft Copilot dashboard: 

Screenshot 2 – Example of output: 

[What you can do to prepare:]

• Review the assignment of the Copilot dashboard users with full company-wide data access and adjust VFAM policies as needed.
• Communicate the upcoming feature to eligible users so they know what to expect.
• No admin setup is required to start using the export.
• Admins can disable the feature at the tenant or group level at any time using VFAM settings.

Learn more: 

Microsoft Viva Feature access management | Microsoft Learn

Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

[Compliance considerations:]

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

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

[Introduction]

We’re updating how entities inserted from Add Work Content under the + menu behave in Microsoft 365 Copilot and Copilot Chat. With this change, entity names (such as document titles, people names, or other referenced objects) will no longer be inserted as text within the input box, making it easier for users to craft clean prompts without needing to manually delete entity labels. This feature is available to both users with a Microsoft 365 Copilot license (Microsoft 365 Copilot users) and users without a Microsoft 365 Copilot license (Copilot Chat users), but the experience varies.

This message is associated with Microsoft 365 Roadmap ID 552592.

[When this will happen]

General Availability (Worldwide): Rollout begins in late May 2026 (previously mid-May) and completes mid-July 2026 (previously mid-June).

[How this will affect your organization]

Who is affected: All users with access to Microsoft 365 Copilot and Copilot Chat in commercial (non-government) clouds.

What will happen:

• When users insert entities through Add Work Content (+):
  • The entity pill will appear in context, but the entity name will no longer be inserted as text in the chat input box:

     

• This change creates a cleaner prompt-building experience by removing extraneous text.
• No admin controls are changing.
• This update is enabled by default for all tenants.

[What you can do to prepare]

No action is required.

Optional steps include:

• Informing helpdesk or training teams about the change.
• Updating internal documentation that references entity insertion behavior in Copilot or Copilot Chat.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat | Microsoft Support

[Compliance considerations]

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

Updated July 13, 2026: We have paused rollout of this feature at this time. We will provide an update via Message center when we are ready to proceed. We apologize for any inconvenience. 

[Introduction]

Consecutive Interpretation is a new interpretation mode available as an add‑on to the existing Interpreter agent in Microsoft Teams. It enables structured multilingual conversations in meetings by providing shared, meeting‑level interpretation when enabled by a Microsoft 365 Copilot licensed user.

This mode uses consecutive (turn‑by‑turn) interpretation, meaning participants speak one at a time and each speaker’s words are interpreted before the next speaker begins. This structured flow reduces overlap, improves interpretation accuracy, and helps everyone stay aligned in real time.

Consecutive Interpretation is ideal for back‑and‑forth, interactive discussions where participants need to respond, clarify, and build on each other’s input across languages, such as working sessions, negotiations, and cross‑functional collaboration.

This message is associated with Microsoft 365 Roadmap ID 557180.

[When this will happen]

• Targeted Release: Rollout begins in early May 2026 (previously early April) and is expected to complete by late May 2026 (previously mid-April).
• General Availability (Worldwide): We will provide an update via Message center when we are ready to proceed.

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using Microsoft Teams meetings where users are licensed with Microsoft 365 Copilot.

What will happen

• For tenants
  • The new Consecutive Interpretation mode extends the existing Interpreter agent to support structured, interactive multilingual meetings.
  • The existing Interpreter experience remains unchanged unless this new mode is enabled.
• For admins
• No new tenant‑level configuration is required.
• The feature is available to all users with a Microsoft 365 Copilot license.
• Existing compliance, privacy, and data‑handling policies for Interpreter continue to apply.
• For users
• When a Microsoft 365 Copilot licensed user enables the mode, interpretation becomes a shared meeting‑level experience rather than an individual setting.
• Participants speak consecutively, with each turn interpreted and delivered before the next participant begins.

[What you need to do to prepare]

• No action is required to maintain current behavior.
• Ensure any users who intend to use this mode have an active Microsoft 365 Copilot license.
• Consider providing guidance to users about when this mode is best suited (for example, working sessions, negotiations, or detailed multilingual collaboration).

[Compliance considerations]

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

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

[What and Why:]

Beginning in mid-June 2026, Microsoft 365 Copilot will be able to answer user questions using Power BI reports and semantic models for customers enrolled in Frontier. Copilot will ground responses in Power BI data, including scenarios where users share a specific report and scenarios where Copilot finds the right report automatically. The experience is built to work within existing security and permission models.

[Rollout Schedule:]

Data answering capabilities grounded in Power BI content will roll out across Frontier and Worldwide environments on the following schedule:

• Frontier Private: June 17, 2026 (applied to TAP, TAP Subset, and AIX00)
  
• Frontier Public (Entra): June 22, 2026
• Worldwide: Starting mid-August 2026, expected to complete by late August 2026

[Impact on Your Organization:]

• Who is affected: Organizations using Microsoft 365 Copilot and Power BI that are enrolled in Frontier
• Platforms/Services: Microsoft 365 Copilot, Power BI, Microsoft Fabric
• Licensing requirements:
  • Microsoft 365 Copilot (Premium) license is required to use this feature.
  • Use of Fabric content, including Power BI reports, will be subject to the usual Power BI licensing to view content in the service.
  • Users are not required to have access to Fabric Copilot. 
• What will happen:
  • Users can ask Copilot questions grounded in Power BI reports and semantic models.
  • Responses respect existing Power BI and Microsoft 365 permissions.
  • The feature is enabled by default. Admins can disable the feature through the Microsoft 365 admin center.
  • To generate responses, Microsoft 365 Copilot will search and retrieve data stored in Fabric, which means user query data from Microsoft 365 Copilot will be shared with Fabric. Fabric operates separately from Microsoft 365 Copilot and is subject to different commitments. Data processed in Fabric is subject to Fabric’s Product Terms. 

Screenshot: Before and after improvement in Copilot responses with Power BI data grounding:

• No action is required.
• Admins can disable the feature in the Microsoft 365 admin center. At the time of release, this control will be available on the Copilot settings page under the setting Fabric data in Microsoft 365 Copilot.  

[Compliance considerations:]

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

[What and Why]

This update introduces a simplified profile assignment and channel management experience for cloud update. Admins can now use groups to assign profiles and combine profile assignment with channel selection in a single step. This streamlines onboarding, makes it easier to move devices between update channels, and helps maintain consistent update management across the organization.

This message is associated with Microsoft 365 Roadmap ID 558250.

[Rollout Schedule]

• Public Preview (Worldwide): We will begin rolling out in early May 2026 and expect to complete by late June 2026.
• General Availability (Worldwide): We will begin rolling out in late June 2026 and expect to complete by late July 2026 (previously late June).

[Impact on Your Organization]

Who is affected: Admins managing Microsoft 365 Apps updates using Cloud Update in the Microsoft 365 Apps admin center.

Platforms / Services:

• Microsoft 365 Apps
• Microsoft 365 Apps admin center (Cloud Update)

What will happen:

• Admins can assign Cloud Update profiles using Microsoft Entra ID groups or built-in update channel groups.

Screenshot 1: Microsoft 365 Apps admin center home page showing available update profiles and access to profile management:



Screenshot 2: Profile details view showing device selection criteria using Microsoft Entra groups and built-in update channel groups:



• Profile assignment and update channel selection are combined into a single workflow.
• The Switch device update channel control in inventory is replaced by profile-based channel assignment.
• Existing Cloud Update profiles are automatically migrated with their associated built-in channel groups.
• Existing exclusions, rollout waves, pause controls, and rollback settings continue to apply.
• There is no impact to users.

[Action Required / Recommendations]

• No action is required to receive this public preview.
• Existing Cloud Update customers: profiles remain active and devices continue to be managed.
• New Cloud Update customers: profiles remain inactive until one or more groups are assigned.
• If you currently use the Switch device update channel control: add your group to the appropriate profile.
• Review and update any internal documentation related to Cloud Update.

Learn more:

New changes coming to cloud update – Microsoft 365 Apps | Microsoft Learn

[Compliance considerations]

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

[What and Why]

Microsoft Purview Data Loss Prevention (DLP) is introducing new capabilities to detect and act on classification failures such as timeout, throttling, and scan errors. This update helps administrators surface previously undetected failures and apply appropriate protection, improving visibility and strengthening compliance outcomes across Exchange Online.

This message is associated with Microsoft 365 Roadmap ID 561916.

[Rollout Schedule]

• Public Preview: Rollout begins in mid-July 2026 (previously mid-June) and is expected to complete by late July 2026 (previously early July).
• General Availability (Worldwide): Rollout begins in mid-August 2026 and is expected to complete by late August 2026.

[Impact on Your Organization]

Who is affected

• Admins managing Microsoft Purview DLP policies in Exchange Online

Platforms/Services:

• Exchange Online
• Microsoft Purview Data Loss Prevention

What will happen

• The feature is turned off by default and requires explicit tenant-level opt-in.
• There is no change to existing behavior or user experience unless you enable the feature.
• Existing DLP conditions will expand to detect additional classification failure scenarios after opt-in is enabled.
• New classification failure categories include:
  • timeout
  • throttling
  • other scan errors.
• A new condition called DocumentScanFailures allows targeting specific failure types and must be used with existing scan conditions.
• You may see an increase in DLP alerts and rule matches after enabling the feature. This reflects previously undetected classification failures and does not indicate new issues.

Updated condition behavior

• Document couldn’t be scanned will detect:
  • Text extraction failures
  • Classification failures such as timeout, throttling, and other scan errors after opt-in
• Document didn’t complete scanning will detect:
  • Partial text extraction
  • Partial classification failures where some classifiers succeed and others fail

New condition

• DocumentScanFailures enables detection of specific failure types including timeout, throttled, and other errors.
• Must be used with either Document couldn’t be scanned or Document didn’t complete scanning.
• Cannot be used as a standalone condition.

[Action Required and Recommendations]

To prepare for this update:

• Review existing DLP policies that use these conditions:
  • Document couldn’t be scanned
  • Document didn’t complete scanning
• Plan when to enable the tenant-level opt-in based on your readiness.
• Enable the feature using PowerShell:
  • Connect using Connect-IPPSSession.
  • Run the following commands:

$json = ‘{“Classification”:{“State”:1}}’

Set-PolicyConfig -DlpErrorHandlingConfig $json

• Allow up to one hour for the configuration to take effect.
• Configure rule priority to ensure proper evaluation:
  • Place content-based rules above scan failure rules.
  • Scan failure conditions only evaluate classifiers that have already run.

Example rule order:

• Detect credit card numbers
  • Condition: Content contains credit card number
  • Action: Block
• Detect account numbers
  • Condition: Content contains account number
  • Action: Block
• Detect exact data match
  • Condition: Content contains EDM sensitive information type
  • Action: Block
• Catch full scan timeout failures
  • Condition: Document couldn’t be scanned and DocumentScanFailures set to timeout
  • Action: Audit
• Catch partial scan throttling
  • Condition: Document didn’t complete scanning and DocumentScanFailures set to throttled
  • Action: Audit
• Catch other scan errors
  • Condition: Document couldn’t be scanned and DocumentScanFailures set to other
  • Action: Audit
• Monitor results using Activity Explorer and DLP alerts to understand classification failure patterns.
• Communicate this change to security and compliance teams.
• You can disable the opt-in setting to return to previous behavior if needed.

[Compliance considerations]

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

[What and why]

Outlook emails can now be added as references in Microsoft 365 Copilot Notebooks. This capability allows users to ground Microsoft 365 Copilot in email conversations, decisions, and context directly within their notebooks, alongside files and other content, to generate more relevant presentations, briefs, and summaries.

This capability extends existing Copilot grounding on organizational data into the Notebooks experience and is available in Copilot Notebooks across Microsoft 365.

This message is associated with Microsoft 365 Roadmap ID 564910.

[Rollout schedule]

• Public Preview: Rolling out early June 2026 through late June 2026.
• General Availability (Worldwide): Rolling out mid-July 2026 (previously early July) through late July 2026.

[Impact on your organization]

Who is affected

• Users with a Microsoft 365 Copilot (Premium) license who have access to Copilot Notebooks

Platforms and services

• Microsoft 365 Copilot
• Copilot Notebooks
• Outlook (email content as a reference source)
• Web experiences where Copilot Notebooks are available

What will happen

• Users can add Outlook emails as reference sources in Copilot Notebooks through the Add reference experience, , where an email option will appear.
• Copilot can use selected emails, together with files and other notebook sources, to generate responses.
• Users can add up to 300 total sources per notebook, including emails.
• Email content reflects its state at the time it is added and does not update with future replies or changes.
• In shared notebooks, email content is only available to users who were participants in the original email.
• Email attachments are not currently supported as grounding sources.
• The feature is enabled by default, with no admin control to disable it.
• Existing Microsoft 365 permissions are respected, and users only access content they already have permission to view.
• Existing compliance, governance, and Purview protections for Outlook data continue to apply.

[Action required or recommendations]

No action is required.

Consider the following recommendations:

• Inform users about the ability to add emails as notebook references.
• Update internal training or documentation for Copilot Notebooks if applicable.
• Review existing compliance and data governance policies to ensure alignment with expanded Copilot use of email content.

Learn more: Add references to your Microsoft 365 Copilot Notebook | Microsoft Support

[Compliance considerations]

• Default-deny allowlist: All certified connectors and actions are blocked unless explicitly added. New connectors are blocked by default until an administrator reviews and allows them. Business and non-business classifications have been removed for connectors and actions to improve clarity.
• Design-time and runtime enforcement: Makers now get immediate feedback while authoring an app, flow, or agent, not only at runtime when data is changing. Makers are blocked from adding restricted connectors or actions while authoring, and the platform performs a last-mile check at runtime.
• Govern AI tools: Admins can block an MCP server just like any other connector or action.
• Action-level control: Allow a connector while disabling specific risky, deprecated, or internal actions. Triggers, internal, and deprecated actions are clearly tagged.
• Automatic scaling: Because ACP is native to environment groups, the right policy follows each environment created through personal developer environments and routing, no environment-by-environment overhead is required.
• ACP-only mode: Optionally skip classic data policy evaluation entirely for a clean governance posture.

1. Review inventory. Use Power Platform inventory (preview) under Manage > Inventory to see connector and operation usage across apps, flows, and agents so you can anticipate impact before activating ACP.
2. Test on a single environment. Apply ACP under Security > Data and privacy in the Power Platform admin center. No Managed Environments are required for a single environment. The policy remains off until you activate it.
3. Build your allowlist. Starting from default-deny, add the certified connectors and actions your teams require. New connectors are blocked by default, so plan for ongoing allowlist reviews.
4. Scale with environment group. Applying ACP across an environment group requires Managed Environments. Configure on the group’s Rules tab.
5. Run hybrid with DLP. Keep existing DLP policies in place for custom connectors, HTTP connectors, and scenarios not yet at parity while you migrate to ACP.
6. Evaluate ACP-only mode. Test it in public preview to prepare for migration off of DLP policies.

Updated July 13, 2026: We have updated the content. Thank you for your patience. 

[What and Why:]

We are updating Viva Insights Copilot Analytics to remove the Viva Insights license requirement for managers to access team views. After this change, eligible managers and their delegates can access manager-scoped Copilot Analytics insights without requiring an assigned Viva Insights license or service plan.

This update reduces access barriers, supports broader Copilot adoption across organizations, and enables admins to more accurately define and manage the eligible manager population—while continuing to respect existing admin controls and manager settings.

Since additional users may be identified as group managers following this change, these newly identified GMs may receive onboarding communications from Microsoft; see MC1400831 – “Microsoft Viva Insights: New onboarding email for group managers in Copilot Analytics” for details.

[Rollout Schedule:]

General Availability (Worldwide, GCC):  We will begin rolling out in mid-July 2026 and expect to complete by late July 2026

During this period, the rollout will occur in two phases: the license requirement for managers will be removed first, followed by the requirement removal for individuals on a manager’s team.

[Impact on Your Organization:]

Who is affected:

• Administrators and leaders using Viva Insights Copilot Analytics
• Organizations with manager-scoped insights enabled
• Users permitted through Viva Insights VFAM controls
• Tenants with at least 50 Microsoft 365 Copilot (Premium) licenses or 50 Viva Insights licenses assigned

Platforms/Services:

• Viva Insights (web)
• Microsoft 365 Copilot Analytics

What will happen:

• The license requirement for managers to access team insights views will be removed (phase 1: removal of license requirement for managers; phase 2: removal of license requirement for individuals on managers’ teams).
• Eligible managers and delegates will gain access based on admin configuration, not license assignment.
• The feature will be enabled by default.
• Admins can manage access through the Manager settings page in Viva Insights.
• Existing admin controls and manager settings will continue to be respected.

[Action Required / Recommendations:]

No immediate action is required. We recommend that you:

• Review the update and assess impact on reporting, governance, and manager access policies.
• Verify access to manager-scoped team views in Viva Insights admin settings.
• Communicate the change to newly eligible managers.
• Engage your works council or employee representatives, if applicable.

Learn more: Configure manager settings | Microsoft Learn (will be updated prior to rollout)

[Compliance considerations:]

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

[What and Why]

Microsoft is introducing Copilot-enhanced topic assignment in Viva Glint to improve the accuracy, consistency, and reliability of employee feedback categorization. Copilot will help identify relevant topics in survey comments, enabling organizations to gain richer insights from employee feedback. Microsoft is also expanding the standard topic taxonomy with five new topics: Psychological Safety, Artificial Intelligence, Privacy & Data Use, Hybrid Work, and Ethics. This feature is controlled by the existing Viva feature access management (VFAM) toggle for Copilot in Viva Glint; there is no separate feature-level toggle for Copilot-enhanced topic assignment. 

This message is associated with Microsoft 365 Roadmap ID 553224.

[Rollout Schedule]

• General Availability (Worldwide): Beginning late July 2026; expected to complete by late July 2026

[Impact on Your Organization]

Who is affected:

• Organizations using Microsoft Viva Glint
• Microsoft 365 administrators
• Viva and Glint administrators
• Survey program managers, analysts, and leaders
• Users of ad-hoc and recurring surveys

Platforms/Services:

• Microsoft Viva Glint
• Microsoft Copilot in Viva Glint
• Employee feedback reporting and analytics

What will happen:

• Copilot will improve topic assignment for employee feedback comments.
• Five new standard topics will be added:
  • Psychological Safety
  • Artificial Intelligence
  • Privacy & Data Use
  • Hybrid Work
  • Ethics
• The existing Glint Copilot VFAM toggle controls feature availability.
• No separate toggle exists for Copilot-enhanced topic assignment.
• If the VFAM toggle is enabled, the feature becomes available to applicable users.
• If the VFAM toggle is disabled, there is no change to the current experience.
• The feature cannot be independently scoped to selected users.
• At launch, these enhancements will apply only to ad-hoc and recurring survey types. Support for always-on survey types will follow in a later release.

[Action Required / Recommendations]

• Review the current Glint Copilot VFAM toggle setting.
• Determine whether Copilot in Viva Glint aligns with organizational governance requirements.
• Coordinate with privacy, HR, legal, and governance stakeholders before enabling the feature.
• Inform survey administrators and analysts about the upcoming changes.
• Update internal documentation and support processes if applicable.
• Assess the impact of the new topics on reporting and analysis practices.

Learn more: Manage Viva Glint Copilot Access in Microsoft 365 Admin Center | Microsoft Learn

[Compliance Considerations]

[What and Why:]

Microsoft is expanding Copilot Notebooks to support Markdown (.md) files as notebook reference sources. This enhancement enables users to ground Copilot conversations in technical documentation, README files, runbooks, wikis, and AI-generated Markdown content without converting files to other formats. By broadening the types of content that can be used as notebook references, Microsoft is helping organizations make better use of existing knowledge repositories and improve the quality and relevance of Copilot-generated responses.

[Rollout Schedule:]

• General Availability (Worldwide): Beginning in mid-July 2026; expected to complete by late July 2026

[Impact on Your Organization:]

Who is affected:

• Users who have access to Copilot Notebooks.
• Teams that maintain knowledge assets in Markdown (.md) format.
• Organizations using Markdown-based documentation repositories such as technical runbooks, README files, and wiki exports.

Platforms/Services:

• Microsoft Copilot Notebooks
• Microsoft 365 Copilot
• Supported SharePoint and OneDrive locations

What will happen:

• Users will be able to add Markdown (.md) files as notebook reference sources.
• Copilot responses can use information contained within Markdown files as grounding content.
• Copilot can reference structural elements within Markdown documents.
• Existing Markdown-based documentation can be used without file conversion.
• Citations to source content continue to be available.
• The feature is enabled automatically.
• No admin configuration is required.
• Existing permissions and access controls continue to apply.

[Action Required/Recommendations:]

No action is required.

Recommended activities:

• Review internal guidance for users who maintain Markdown-based documentation.
• Communicate the update to Copilot Notebook users.
• Update adoption and training materials as appropriate.
• Validate documentation governance processes for Markdown repositories.

[Compliance Considerations:]

[What and Why]

We’re updating Outlook for iOS and Android so the Copilot button more clearly reflects when Copilot chat is available for users with multiple accounts connected to the app. The Copilot button will appear in multi-account views (unified message list and calendar) if at least one connected account supports Copilot chat. It will be hidden in single-account views where Copilot chat is not supported. This change does not affect Copilot eligibility, licensing, or feature availability; it is a UI update that better reflects existing support.

This change improves clarity and helps users better understand when Copilot is available. It does not change Copilot eligibility, licensing, or feature availability.

[Rollout Schedule]

• General Availability (Worldwide, GCC, GCC High, and DoD): Beginning in early July 2026 and expected to complete by late July 2026.

[Impact on Your Organization]

Who is affected

• Users of Outlook for iOS and Android with multiple accounts configured in the app
• Organizations with users licensed for Microsoft Copilot features in Outlook
• Platforms/Services
• Outlook for iOS
• Outlook for Android
• Microsoft Copilot

What will happen

• The Copilot button will appear in unified mail and calendar views when at least one connected account supports Copilot chat.
• The Copilot button will be hidden when users are viewing an individual account that does not support Copilot chat.
• Copilot support, licensing requirements, and feature availability are unchanged.
• No tenant-level configuration changes are required.
• The experience is enabled automatically as part of the rollout.

[Action Required/Recommendations]

No action is required.

Recommended actions:

• Inform help desk and support teams about this UI update.
• Update internal documentation or training materials that reference Copilot availability in Outlook mobile apps, if applicable.
• Communicate to users that this change improves visibility of existing Copilot availability and does not change licensing or feature entitlements.

[Compliance Considerations]

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

[What and why]

Passkeys will become the default authentication experience in Microsoft Entra on September 1, 2026. Telecom-based methods (SMS and voice) will transition to customer-configured providers through the Microsoft Security Store. 

The AI era demands stronger, phishing-resistant authentication. We are making passkeys the default authentication experience in Microsoft Entra to help customers securely adopt AI at scale.  

As part of this transition, SMS and voice will no longer be available as multifactor authentication methods starting February 1, 2027. SMS and voice do not offer sufficient levels of security in comparison to passkeys. Traditional authentication methods including passwords, SMS one-time passcodes, and voice-based verification remain vulnerable to phishing, interception, and social engineering attacks.

We strongly recommend moving away from telephony-based authentication methods to improve security and prevent identity attacks. Passkeys are included in all Microsoft Entra plans, so making this critical security change comes at no additional cost for you.  

While we recommend adopting passkeys for phishing-resistant authentication as quickly as possible, we also recognize that some customers may have business needs that make an immediate transition impractical. In such cases, customers may continue to use SMS and voice by selecting a telecom provider in the Microsoft Security Store. 

[Rollout schedule]

• September 1, 2026: 
  • Rollout begins. Changes may take time to reach all tenants and will be deployed gradually. 
  • Passkeys will be automatically enabled for users currently enabled for SMS or voice. 
  • Registration Campaign will be set to Microsoft-Managed targeting passkeys for all users in eligible tenants. 
  • Users will be prompted to register a passkey during MFA sign-in; users will be able to skip. 
• September 18th, 2026:
  • review the telecom providers and related information available through the Microsoft Security Store to evaluate which optiohn best meets your regional and compliance requirements.
• October 30, 2026:  
  • Customers who need to continue to use SMS or voice will be able to choose from a list of telecom providers available through the Microsoft Security Store. 
• February 1, 2027: 
  • Microsoft-provided SMS and voice authentication will be retired. 
  • Only customer-configured telecom providers will support SMS and voice going forward. 
  • Passkeys become the default, recommended authentication method. 

[Impact on your organization]

Who is affected

• All Microsoft Entra ID tenants enabled for SMS or voice authentication
• Users enabled for SMS or voice 

Platforms and services

• Microsoft Entra ID
• Multifactor authentication
• Microsoft Security Store

What will happen

• Passkeys will be automatically enabled for eligible users and Registration Campaign for passkeys will be set to Microsoft Managed state starting September 1, 2026. 
• Users will be prompted during MFA sign-in to register a passkey; users can skip the prompt. 
• Microsoft-provided SMS and voice will be retired on February 1, 2027.
• Organizations that still require telephony methods must configure a telecom provider in the Microsoft Security Store.
• Tenants that do not configure a provider and continue relying on Microsoft telephony will face SMS and voice authentication disruptions after retirement.

[Action required and recommendations]

Admins should take the following steps:

• Prepare for passkeys
  • Plan to transition users to passkeys and communicate upcoming registration prompts. 
• Decide if SMS or voice is still required
  • If SMS or voice is still needed, you must configure a customer-managed telecom provider. We recommend completing setup at least 4 weeks before the February 1 enforcement to allow sufficient time for testing and a cautious transition. 
• Set up a telecom provider before February 1, 2027
  • SMS and voice will only work after this date if a customer-configured telecom provider is enabled.  
• Use temporary opt-out if needed
  • A temporary opt-out will be available for the September 1, 2026 through February 1, 2027 changes. This allows you to delay passkey and Registration Campaign enablement while you complete transition activities, such as configuring customer-managed telecom providers or migrating to other authentication methods.
  • After February 1, 2027, passkey enablement will be enforced for all users in scope. 

Additional documentation and more information will be available on Microsoft Learn and the Tech Community.

For more information please visit: https://learn.microsoft.com/entra/identity/authentication/concept-sms-voice-retirement more:

• Deploy passkey adoption campaigns with the Conditional Access Optimization Agent | Microsoft Entra | Microsoft Learn
• Get started with phishing-resistant passwordless authentication deployment in Microsoft Entra ID | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• It’s Time to Hang Up on Phone Transports for Authentication | Microsoft Entra Blog
  
• Passkeys by default and retirement of Microsoft-provided SMS and voice authentication | Microsoft Entra | Microsoft Learn

[Compliance considerations]

Review as appropriate for your organization.