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

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

We’re introducing My Team audiences and expanded targeting capabilities in Viva Engage to help leaders communicate with the employees in their organization and tailor messages to relevant teams, departments, locations, or groups. My Team provides a ready-to-use, automatically maintained audience based on the organizational hierarchy, so leaders can reach the employees who report up to them, including both direct and indirect reports. This audience helps unlock and improve leadership experiences across Viva Engage, making Storyline Announcements, audience analytics, Leadership Corner, and feed and digest distribution more relevant with less setup.

Leaders and delegates can use My Team as-is, review its membership, or further customize and save it as a reusable audience across leader communication experiences. For Storyline Announcements, they can also define recipients at the time of publish, choosing My Team, a saved audience, or a custom audience built using organizational attributes such as department, job title, or country; existing groups like M365 Groups, distribution lists, or security groups; and individual users by name. Together, My Team and flexible targeting make leader communications more relevant, scalable, and easier to manage – with a dynamic default audience and precise targeting for relevant employee groups.

This message is associated with Microsoft 365 Roadmap ID 499895.

[When this will happen:]

• Public Preview (Worldwide): Begins mid-November 2025 and completes by mid-March 2026 (previously early February).
• General Availability (Worldwide): Begins mid-August 2026.

[How this affects your organization:]

Who is affected: Leaders and delegates using Viva Engage Storyline Announcements in tenants enrolled in public preview.

What will happen:

• This capability is being introduced as part of the public preview for Viva Engage. During this phase, leaders and their delegates can actively experiment with flexible audience targeting for Storyline Announcements—defining a custom audience at the time of posting, rather than relying solely on pre‑configured Leader Audiences.
• Audiences can include organizational attributes (such as reporting structure, country, department, job title), existing groups (Microsoft 365 Groups, DLs, SGs), or individual users.
• Notifications and delivery channels (Teams, email, Viva Engage Inbox) remain unchanged for recipients.
• No dependency on IT or advance audience setup—leaders can act immediately when communication needs arise.
• Available only in public preview; functionality and targeting options may evolve before general availability.
• Admins should ensure organizational attributes in Entra ID or Organizational Data in Microsoft are accurate to support successful targeting.
• Available platforms: Desktop and web.
• Licensing requirements: This feature requires a premium license available through Viva or Communications and Communities (C&C). Availability may vary depending on your organization’s Microsoft 365 licensing agreement.

[What you can do to prepare:]

No admin action is required for rollout. To prepare, you may want to:

• Validate organizational attributes (reporting structure, country, department, role, job title) in Microsoft Entra ID or Organizational Data in Microsoft.
• Confirm leader and delegate assignments to ensure the right people can use Storyline Announcements and the new targeting control.

Learn more:

• Use your organizational data in Microsoft 365 and Microsoft Viva | Microsoft Viva | Microsoft Learn

[Compliance considerations:]

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

Updated June 24, 2026: We have decided not to move forward with this change at this time. We apologize for any inconvenience. 

[Introduction]

We are introducing a new handoff experience that allows users to take content created in Copilot Pages and seamlessly continue authoring as a SharePoint news post. This update helps users move from ideation to publishing more efficiently.

[When this will happen:]

General Availability (Worldwide, GCC): We have decided not to move forward with this change at this time.

[How this affects your organization]

Who is affected:

• Users who create content in Copilot Pages and publish SharePoint News
• Organizations using Microsoft 365 Copilot with SharePoint Online

What will happen:

• Users can move content from Copilot Pages directly into a SharePoint News post.
• A new SharePoint option will appear under the Create button in Copilot Pages:

  

• Selecting SharePoint opens the content in SharePoint News for continued editing and publishing.
• The feature is enabled by default.
• Existing SharePoint permissions, policies, and governance controls are respected.
• There is no disruption to existing SharePoint News workflows.

[What you can do to prepare]

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

[Introduction]

We’re expanding Microsoft Purview Data Loss Prevention (DLP) controls for Microsoft 365 Copilot and Copilot Chat to help organizations reduce the risk of untrusted or externally sourced content influencing AI‑generated responses. This new capability allows admins to exclude emails from external senders from being used as grounding data during Copilot prompt processing. When enabled, Copilot continues to generate responses using trusted internal Microsoft 365 data sources, subject to existing licensing and policy controls.

This message is associated with Microsoft 365 Roadmap ID 561552.

[When this will happen]

• Public preview: We will begin rolling out in early June 2026 and expect to complete by late June 2026.
• General availability (Worldwide): We will begin rolling out in late January 2027 (previously late July) and expect to complete by late February 2027 (previously late August).

[How this affects your organization]

Who is affected

• Organizations using Microsoft 365 Copilot (Premium) or Copilot Chat
• Admins managing AI governance, security, and data protection using Microsoft Purview

What will happen

• A new DLP policy control will be available for Microsoft 365 Copilot and Copilot Chat.
• When enabled by an admin:
• Emails sent from external or untrusted domains are excluded from being:
  • Referenced
  • Summarized
  • Used as grounding data by Copilot
• Copilot continues to generate responses using trusted internal Microsoft 365 data sources (for example, SharePoint, OneDrive, and internal Exchange content), subject to existing licensing and policy.

This change does not:

• Affect email delivery, retention, eDiscovery, or user access
• Change existing Copilot interaction behavior unless the policy is explicitly configured

Default state:

• Off by default.
• There is no change unless an admin enables this control in Microsoft Purview.

Screenshot 1. Select Microsoft 365 Copilot and Copilot Chat as the DLP policy location: 

Screenshot 2. New DLP setting to restrict processing of external email content: 

[What you can do to prepare]

No action is required if you do not plan to use this capability.

If you want to enable the feature:

• Create or update a DLP policy for Microsoft 365 Copilot in the Microsoft Purview portal.
• Review existing DLP configurations to understand potential Copilot impact.
• Ensure your admin account has the required DLP and Purview roles.
• Inform IT, security, and helpdesk teams about the new control.
• Update internal documentation related to AI governance and Copilot usage.

Learn more:

• Learn about data loss prevention | Microsoft Purview | Microsoft Learn
• Learn about using Microsoft Purview Data Loss Prevention to protect interactions with Microsoft 365 Copilot and Copilot Chat | Microsoft Purview | Microsoft Learn
• Permissions – Create and deploy data loss prevention policies | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Updated May 22, 2026: We have paused rollout of this feature at this time. We will communicate via Message center when we are ready to proceed. Thank you for your patience.

[Introduction]

We’re introducing the ability to create workflows that schedule prompts in Agent Builder in Microsoft 365 Copilot. This new capability allows users to schedule prompts that run automatically on a defined cadence, such as hourly, daily, or weekly. Based on customer feedback requesting more automation and proactive insights, workflows help users reduce manual prompting and automate routine tasks using their Copilot agents.

[When this will happen]

• General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

[How this affects your organization]

Who is affected

• Users who create and manage agents using Agent Builder in Microsoft 365 Copilot (Premium)

What will happen

• Users will be able to create scheduled workflows for agents.
• Scheduled workflows include:
  • Prompt text
  • Triggers and recurrence patterns
  • Date, time, and time zone settings
• Supported recurrence patterns:
  • Hourly
  • Daily
  • Weekly
  • Monthly
  • Yearly

• Workflows are configured per user and run only for the user who created them.
• Workflows are not shared when an agent is shared with others.
• Scheduled workflows will not run for draft or unpublished agents.
• Users can view, edit, preview, and delete workflows within Agent Builder.
• This feature is enabled by default and respects existing tenant and Copilot policies.

Screenshot of Agent Builder showing a “Project Horizon” agent configuration screen. The instructions panel is visible in the center, while a dropdown menu in the top-right corner is expanded with options including “Create a workflow for this agent” and “Manage workflows.” A purple arrow highlights the option to create a new workflow.

Screenshot of Agent Builder showing a “Project Horizon” agent configuration screen. A modal titled “Create a workflow to prompt your agent” is centered, with a text field labeled “Prompt” and scheduling options set to run weekly on Friday at 1:30 PM. A purple arrow highlights where to enter the prompt. 

[What you can do to prepare]

• No admin action is required to enable this feature.
• Consider informing users who build Copilot agents about the availability of workflows.
• Update internal documentation or training materials if you support Copilot agent creation.
• For privacy or compliance requests, continue using the existing Data Subject Request (DSR) processes.

Learn more: Dsr Compliance – Delete Flow | Dsr Compliance | Power Platform API | Microsoft Learn

[Compliance considerations]

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

[What and Why]

Microsoft Teams will introduce a new in-meeting toggle that allows licensed meeting organizers and presenters to turn Meeting AI (including Copilot, Facilitator, and meeting recap) on or off during a live meeting. This change builds on existing Meeting AI behavior and provides real-time flexibility to control when AI is active.

Licensed organizers and presenters can capture insights when discussions are valuable and turn off AI when conversations shift to sensitive topics. The toggle respects existing tenant policies and compliance controls.

This message is associated with Microsoft 365 Roadmap ID 558286.

• Targeted Release: We will begin rolling out early July 2026 (previously early June) and expect to complete by mid-July 2026 (previously mid-June).
• General Availability (Worldwide): We will begin rolling out mid-July 2026 (previously mid-June) and expect to complete by end-of-July 2026 (previously late June).

Who is affected

• All Microsoft 365 tenants with Meeting AI (Copilot and/or Facilitator) enabled by policy and in Meeting Options
• Licensed organizers and presenters in Teams Meetings

• Microsoft Teams (Desktop, Web, and Mobile)
• Microsoft 365 Copilot (Meeting AI, Facilitator, recap)

• A new Meeting AI toggle will appear in the Teams meeting toolbar: 

  

• Licensed organizers and presenters can turn Meeting AI on or off during meetings: 

  

• Toggles are shown only when Meeting AI is allowed by policy.
• An AI status indicator will show participants whether Meeting AI is active.

Existing tenant policies and meeting options are respected:

• If Meeting AI is disabled by policy, the toggles will not appear.

When Meeting AI is turned off:

• Copilot, Facilitator responses, and Notes will no longer be generated.
• Previously generated artifacts remain available and governed by retention policies.
• If AI is used without transcription, speech-to-text data stops and Recap is not generated.

Important: Transcription Dependency

• When AI is used with transcription, they remain coupled:
• Turning on Meeting AI automatically turns on transcription and generates a recap.
• Starting transcription automatically enables Meeting AI and recap.
• To prevent Meeting AI usage, transcription and Meeting AI must remain off.

• Meeting options configured before meetings
• Recording, transcription, and sensitivity labels behavior
• Retention and compliance policies
• Licensing requirements for Copilot and Meeting AI

No action is required for this rollout.

Recommended actions:

• Update internal training and documentation to explain:
• Where the Meeting AI toggle appears
• Who can use the toggle (licensed organizers and presenters)
• Communicate to end users:
• Starting transcription automatically enables Meeting AI and recap
• Meetings that must avoid AI should not use transcription
• Prepare helpdesk teams to support user questions about:
• Controlling Meeting AI during meetings
• Understanding transcription-related behavior

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

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

[What and Why]

Microsoft Teams is updating the location and naming of the room optimization experience, previously called “add shared display,” to a context dependent “optimize for room” option. This change improves usability and helps users more easily configure Teams for shared and in-room meeting scenarios. The updated experience automatically optimizes audio, video, and display behavior to support more effective hybrid collaboration.

This message is associated with Microsoft 365 Roadmap ID 564912. 

[Rollout Schedule]

• General Availability (Worldwide): Begins in early August 2026 (previously mid-July) and expected to complete by late August 2026 (previously late July).

[Impact on Your Organization]

Who is affected

• Users who run Microsoft Teams meetings on laptops connected to shared or room-based equipment, such as conference rooms or bring your own device meeting setups.

Platforms/Services

• Microsoft Teams desktop

What will happen

• The “add shared display” option is renamed to “optimize for room.”
• The option is moved to a context dependent location in the Teams interface.
• When enabled, Teams will optimize the meeting experience for room scenarios.
• Connected room peripherals, such as AV devices associated with a room, will be automatically selected instead of laptop audio and video devices.
• If an external display is connected, shared display mode will activate and split Teams into two windows.
• Voice isolation will be disabled so in room participants can be heard clearly.
• Voice recognition will be enabled if allowed by policy.
• A room node will appear in the meeting roster to represent in room participants.
• The feature is user initiated and is not enabled by default.

[Action Required or Recommendations]

No admin action is required.

Recommended actions:

• Inform users of the updated “optimize for room” terminology and where to find it.
• Update internal documentation that references “add shared display.”
• Communicate the change to support and helpdesk teams.
• Encourage users to adopt the feature for improved hybrid meeting experiences.

[Compliance considerations]

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

[What and Why:]

Microsoft is introducing a new tenant-level setting to support the transition from ODBC (Open Database Connectivity) to ADBC (Arrow Database Connectivity) in Power Query. This change is part of Microsoft’s ongoing investment in improving data connectivity performance, reliability, and scalability. ADBC aligns with modern data access standards and helps deliver faster, more efficient data operations across your organization.

[Rollout Schedule:]

General Availability (Worldwide): Rollout begins late June 2026 and is expected to complete by late December 2026

[Impact on Your Organization:]

Who is affected:

• Admins managing Power Query settings and data connectivity within the tenant
• Users leveraging ODBC-based connections in Power Query (e.g., Excel, Power BI)

Platforms/Services:

• Power Query (across Excel, Power BI, and other integrated Microsoft data experiences)

What will happen:

• A new tenant setting for ODBC-to-ADBC transition will be visible in your tenant.
• The setting is disabled by default at rollout.
• Microsoft plans to enable this setting by default at a later date.
• There is no immediate impact to users or existing workflows while the setting remains disabled.
• Future enablement may transition eligible connections from ODBC to ADBC.

[Action Required / Recommendations:]

No immediate action is required. We recommend that you:

• Review the new tenant setting once it becomes available.
• Evaluate existing ODBC-based data connections.
• Test ADBC compatibility in non-production environments.
• Communicate upcoming changes to data and analytics teams.

Learn more: Transition to ADBC in Power Query

[Compliance considerations:]

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

[What and why]

We have resolved a long-standing issue where notebooks could not be deleted due to policy conflicts in environments with configured data lifecycle and retention policies in Microsoft Purview. This fix has been validated through our safe deployment process and restores expected deletion behavior while maintaining compliance integrity.

This improvement supports enterprise-ready AI by ensuring Copilot notebooks function reliably in compliant environments and enables continued investment in notebook recovery capabilities, including upcoming Recycle Bin functionality. Deployment is progressing across supported commercial environments.

[Rollout schedule]

• General Availability (Worldwide): We will begin rolling out in late June 2026 and expect to complete by early July 2026.
• General Availability (GCC and GCC High): We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.

[Impact on your organization]

Who is affected

• Organizations using Microsoft 365 Copilot notebooks with configured data lifecycle and retention policies in Microsoft Purview
• Admins managing compliance policies in Microsoft Purview

Platforms and services

• Microsoft 365 Copilot
• Copilot notebooks
• SharePoint Embedded storage

What will happen

• Users will be able to delete notebooks as expected.
• Compliance policies will no longer block deletion actions incorrectly.
• Existing retention and lifecycle policies will continue to be enforced.
• No changes to admin configurations are required for the fix to take effect.

[Action required or recommendations]

No action is required.

Recommended actions:

• Review any previously excluded storage locations and re-enable them if appropriate for compliance coverage.
• Inform helpdesk teams that notebook deletion issues have been resolved.
• Continue using SharePoint Embedded recovery capabilities to restore deleted containers until Notebook Recycle Bin functionality becomes available.
• Watch for a future Message center post with timelines for Notebook Recycle Bin availability.

[Compliance considerations]

[What and Why]

We are expanding Microsoft Teams Phone capabilities to mobile devices by enabling users to manage and use multiple assigned phone numbers directly within the Teams mobile app. Users will see and manage their assigned phone lines in the Calls app on Teams mobile, allowing them to choose the appropriate number when placing or returning calls. This update provides a more consistent calling experience across devices and helps users who manage multiple roles or regions stay productive without switching devices or workflows.

This message is associated with Microsoft 365 Roadmap ID 565131.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected:

• Organizations using Teams Phone
• Users who are assigned multiple phone numbers in Teams Phone

Platforms/Services

• Microsoft Teams
• Teams mobile (iOS and Android)

What will happen

• Users will be able to select which phone line to use when placing calls from the dial pad: 

  

• Calls can be returned using a selected phone line directly from call history: 

  

• A unified call history will be available, with the ability to filter by phone line.
• Calling across multiple phone lines will be supported within Teams mobile.
• This capability extends existing Teams Phone multi-line functionality to mobile devices.
• The feature will be available to users who are already configured with multiple phone numbers in Teams Phone.

[Action Required or Recommendations]

No action is required.

After rollout, admins may choose to:

• Review which users require multiple phone numbers.
• Assign and manage phone numbers in the Teams admin center.
• Ensure each assigned number has a valid emergency address configured.
• Confirm compliance with regional telecommunications requirements.

Learn more: (To be updated closer to rollout.) Use the dial pad to make a call in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

[What and Why]

Microsoft Defender for Cloud Apps is enhancing its threat protection capabilities by migrating legacy detection policies to a new dynamic detection model. This update improves detection accuracy, reduces false positives, and enables faster response to evolving threats by using research-driven detections maintained by Microsoft security experts.

As part of this change, the legacy alert “Activity performed by terminated user” is being replaced by a detection built on the new dynamic detection model. This updated detection is designed to more precisely identify risky activity associated with users who have left the organization while continuously adapting to changes in the threat landscape.

This change also introduces a shift from static detection logic to continuously updated detection logic, which may evolve over time to improve signal quality and accuracy.

[Rollout Schedule]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late June 2026 and expect to complete by early July 2026.

[Impact on your organization]

Who is affected

• Organizations using Microsoft Defender for Cloud Apps threat protection capabilities
• Security operations center and IT security teams

Platforms and services

• Microsoft Defender for Cloud Apps, part of Microsoft Defender XDR

What will happen

• The legacy alert “Activity performed by terminated user” will be replaced by a detection built on the new dynamic detection model, titled “Activity by a deprovisioned user (preview).” The suffix will be removed next month.
• The updated detection will:
  • Be enabled by default
  • Be automatically maintained and updated by Microsoft
  • Continuously evolve to improve detection accuracy and adapt to emerging threats
• Detection behavior, alert patterns, or alert volume may change over time as the model adapts.
• No manual configuration is required.
• During rollout:
  • Disabled legacy policies may remain temporarily visible, and 
  • Legacy policies will be removed after migration completes as part of the retirement of the legacy detection model.

Screenshot 1:

Screenshot 2:

[Action Required/Recommendations]

No action is required.

Recommended steps:

• Notify SOC and helpdesk teams about this change.
• Update internal documentation that references the legacy alert “Activity performed by terminated user.” and the new alert “Activity by a deprovisioned user (preview)”.
• Review and validate any alert-based automation, workflows, or incident response processes after rollout.
• Monitor alerts after rollout to understand updated detection behavior and tuning needs.

Learn more: (To be updated closer to rollout.) Create Defender for Cloud Apps anomaly detection policies | Microsoft Defender for Cloud Apps | Microsoft Learn

[Compliance considerations]

[What and Why]

We are improving the Speed dial experience in Microsoft Teams mobile (iOS and Android) to help users reach important contacts faster and more reliably. This update introduces a simpler and more personalized interface for managing contacts and ensures consistency across devices, supporting productivity for users who need quick access to calling features while on the go.

[Rollout Schedule]

General Availability (Worldwide): We began rolling out in mid-June 2026 and expect to complete by late June 2026.

[Impact on Your Organization]

Who is affected

• Users in your organization who use Teams Phone and access calling features on Teams mobile

Platforms/Services

• Microsoft Teams mobile (iOS and Android)
• Teams Phone

What will happen

• Users will see a redesigned Speed dial interface in the Calls app on mobile:

   

• Users can add, edit, and remove contacts directly within the Speed dial interface:

   

• Speed dial lists will sync across devices, ensuring consistency between mobile and other Teams clients.
• The feature is enabled by default for eligible users.
• There are no changes to admin configuration or policies.

[Action Required/Recommendations]

No action is required. This update will roll out automatically to eligible users.

Recommended actions:

• Inform users, especially frontline workers and support teams, about the updated Speed dial experience.
• Update internal documentation if it references Teams mobile calling workflows.
• Prepare helpdesk teams to answer user questions about the updated interface.

Learn more: Manage your contacts with the People App in Teams | Microsoft Support

[Compliance considerations]

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

[What and Why:]

We are introducing configurable alerts in the Microsoft Teams admin center to notify administrators when a new Teams desktop client version begins rolling out in their tenant. This capability helps IT teams stay informed and quickly respond to version-related issues during rollout, improving operational visibility and client health management.

[Rollout Schedule:]

General Availability (Worldwide): Beginning in late June 2026 and expect to complete by late June 2026

[Impact on Your Organization:]

Who is affected: Admins managing Microsoft Teams deployments in the Teams admin center.

Platforms/Services: 

• Microsoft Teams desktop client
• Microsoft Teams admin center

What will happen:

• A new alert rule named “Teams client update rollout” will be available in the Teams admin center.
• The alert is disabled by default and requires admin configuration.
• When enabled, admins will receive notifications when a new Teams desktop client version begins rollout in their tenant.
• Alerts can be configured based on:
  • Update ring (for example, Targeted or Standard release)
  • Platform selection (such as Windows or macOS)
• Alerts can be delivered via:
  • A Microsoft Teams channel
  • A webhook URL for integration with external systems
• The alert rule is evaluated daily, and notifications are sent if conditions are met.
• No impact to users unless admins enable and configure the alert.

[Action Required/Recommendations:]

Actions are required for admins who want to use the feature.

To enable alerts:

1. Go to the Microsoft Teams admin center.
2. Navigate to Notifications and alerts > Rules.
3. Select Teams client update rollout alert rule.
4. Configure:
   • Ring and platform conditions
   • Notification destination (Teams channel or webhook URL)
5. Set the rule status to Active.
6. Select Save.

The following table describes the available configuration options:

Field	Description
Conditions	Choose the Ring to specify which ring the alert monitors for a new client version release. Choose the Platform to specify which platforms you want to monitor for a new client version release.
Scope	This rule is evaluated daily, and an alert is sent if the selected conditions are met.
Actions	Choose if you want to send alerts to a specific Teams channel or to a webhook URL.
Status	Choose if the rule is active and alerts should be sent.

Recommendations:

• Evaluate whether proactive monitoring of client rollouts aligns with your update management processes.
• Configure alerts for critical update rings first (for example, early release rings).
• Notify your helpdesk or support teams about this capability to improve incident response readiness.
• Update internal documentation if you track Teams client version rollouts.

Learn more: Alerts for new Teams desktop client releases – Microsoft Teams | Microsoft Learn

[Compliance considerations:]

[What and Why]

Microsoft is introducing explicit grounding integration in Excel Agent, allowing users to upload and process files directly to ground AI responses in their data. This improves productivity by enabling more accurate analysis of large datasets, combining information across multiple files, and supporting a broader range of file types within Excel. By grounding AI in user-provided content, Excel Agent helps deliver more relevant, context-aware insights.

[Rollout Schedule]

• General Availability (Worldwide): Rolling out from late April 2026 through late June 2026.

[Impact on Your Organization]

Who is affected

• Users with access to Excel Agent in Microsoft 365 tenants

Platforms/Services

• Excel Agent (Microsoft 365 apps)

What will happen

• Users will be able to upload files directly within Excel Agent:

   

• Excel Agent will use uploaded files for explicit grounding to improve AI-generated results.
• Users can analyze large datasets and combine insights across multiple files.
• A broader range of file types will be supported.
• The feature will be available within the existing Excel Agent workflow.
• The feature will be enabled by default where Excel Agent is available.
• No changes to existing admin policies are required.

[Action Required/Recommendations]

• No action is required.
• Consider notifying users about this enhancement to help them take advantage of grounded AI capabilities in Excel Agent.
• Update internal documentation or training materials if you reference Excel Agent or Copilot capabilities.

[Compliance considerations]

• June 24, 2026 – Secure Boot certificates start expiring, beginning with Microsoft Corporation KEK CA 2011 certificate.
• July 1 – Windows Server Secure Boot AMA
• July 8 – Secure Boot Office Hours for virtualized environments
• July 15 – OEM Secure Boot Office Hours

1. Keep your devices up to date with the latest Windows updates.
2. Check that the latest firmware version is installed. You can visit your OEM’s support page or use their official support channels. 
3. Continue with your phased rollout. Gradual deployment of certificates, boot managers, and updated OEM firmware, along with validation, remains the most reliable approach. 
4. Use the tools available to you. Whether built into Windows, such as the Windows Security app, or designed for IT-managed environments, these tools help you monitor progress and make informed decisions.

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

• Displaying intuitive and actionable error messaging to support troubleshooting when needed and provide clear next steps.
• Providing the ability for supervisors to retry failed evaluations directly from the evaluation grid view.

Updated June 24, 2026: We have added Phase 4 for unified app and agent installation management. Thank you for your patience.  

What it is

Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you’ll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient.

This message is associated with Microsoft 365 Roadmap ID 393931, 485712 and 503105.

When this will happen:

We will begin rolling out this feature late September 2025 and expect to complete by August 2026 (previously end of June).

1. Phase 1 – Default Tenant Unification of App/Agent Availability

We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931.

2.Phase 2 – Modified Tenants Unification of App/Agent Availability

This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers.

• For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. We will begin rolling out this feature in early November 2025.
  
  • This message is associated with Microsoft 365 Roadmap ID 485712 & 503105.