Microsoft Roadmap, messagecenter and blogs updates from 02-10-2025

Updated October 1, 2025: We have updated the timeline. Thank you for your patience. 

Introduction

We’re introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes—helping organizations better understand adoption patterns and tailor support strategies.

This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan).

This message is associated with Microsoft 365 Roadmap ID 499899.

When this will happen

Public Preview: We will begin rolling out at the end of October 2025 and expect to complete by end of November 2025.

General availability (Worldwide): We will begin rolling out at the end of November 2025 and expect to complete by end of December 2025.

How this affects your organization

Users with access to the Microsoft Copilot dashboard will see new analytics cards and visualizations focused on Microsoft 365 Copilot Chat adoption for unlicensed users. These insights will appear in the dashboard’s adoption tab and include:

• Usage trends over time: Track active users and adoption growth.
• Adoption by group: Compare usage across departments or roles.
• Usage intensity and retention: Understand recurring usage and engagement levels.
• App-level breakdowns: Identify which apps and entry points drive adoption.
• Filtering and drilldown: Segment data by organizational attributes to tailor change management strategies.

This feature will be on by default for existing dashboard users. No additional administrator action is required to enable it.

What you can do to prepare

Review the impact of this feature on your organization’s reporting and privacy practices. You may also want to update internal training and documentation to reflect the new insights available.

Starting in September 2025:

• A new administrator control will be available for Global administrators, Viva Insights administrators, and AI administrators to turn off this feature at the tenant level. To disable this feature, use Viva Feature Access Management (VFAM) in Microsoft admin center or PowerShell.
• These same roles will also be able to exclude specific users or groups from being included in aggregated insights using the updated exclusion list feature.

Administrators should read the communication regarding the detailed scope and availability of this exclusion feature here (Roadmap ID: 500161).

Administrators should review any existing exclusions, assess their impact, and take appropriate action to exclude or include additional users or groups as needed.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn
• Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn
• Copilot for all: Introducing Microsoft 365 Copilot Chat | Microsoft Blog
• Manage settings for the Microsoft Copilot Dashboard and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn
• Microsoft 365 Copilot overview | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

Compliance considerations

• The initial default setting for this feature is Off.
• However, depending on the tenant region, the default was changed to On between August 25 and September 15, 2025, as part of a feature roll-out communicated on September 1, 2025. The feature became available for use starting September 10, 2025.
• We understand that some customers may not have been aware of this update. We are committed to improving the clarity of such communications going forward.

1. Navigate to Power Platform admin center (new admin center)
2. Go to Manage > Tenant settings
3. Find Name: Hosted browser in computer use
4. Toggle On/Off and Save

Updated October 1, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing Benchmarks in the Microsoft Copilot dashboard (in Viva Insights). This new feature enables organizations to compare Copilot usage internally across cohorts and externally against similar companies. These insights help identify adoption trends and opportunities to improve Copilot engagement.

This message is associated with Microsoft 365 Roadmap ID: 495464.

• Targeted Release (Worldwide): We will begin rolling out in mid-October 2025 (previously late September) and expect to complete by late October 2025 (previously early October).
• General Availability (Worldwide): We will begin rolling out in late October 2025 (previously mid-October) and expect to complete by late November 2025 (previously late October).

Once available, the Copilot dashboard will include:

• External benchmarks to compare your percentage of active Copilot users with:
  • Top 10% and Top 25% of companies like yours
  • Top 10% and Top 25% overall benchmarks
• Internal benchmarks to compare cohorts within your company based on manager types, regions, and job functions:
  • Percentage of active Copilot users
  • Adoption by app
  • Returning user percentage

External benchmarks are calculated using randomized mathematical models to ensure privacy. Each benchmark group includes at least 20 companies and is not derived from any single company’s actual data.

• Review which users have access to the Microsoft Copilot dashboard and adjust permissions as needed.
• Assess the impact of benchmark visibility on your organization’s Copilot adoption strategy.
• Update training materials and documentation to reflect the new dashboard capabilities.
• Learn more about providing access to Microsoft Copilot dashboard: Manage settings for the Microsoft Copilot dashboard and Viva Insights web app – Viva Insights | Microsoft Viva | Microsoft Learn

Expected with Intune’s January (2601) release, all guided scenarios, except Windows 365 Boot, will be removed from the Intune admin center.

[How this will affect your organization:]

Admins will no longer have access to the guided scenario wizards in the Intune admin center. However, any Intune objects previously created by these wizards, such as policies and apps, will remain and can continue to be managed as usual.

[What you need to do to prepare:]

No action is required, only awareness. This change will not impact existing configurations or require admin intervention.

For alternative solutions and step-by-step guidance, refer to the following resources:

• Microsoft Intune product and capabilities documentation | Microsoft Learn
• Intune prescriptive guides
• Intune administration guides: https://setup.cloud.microsoft/intune
• Securing apps for mobile | Android
• Securing apps for mobile | iOS
• Configuring Intune and Configuration Manager to co-manage devices
• Manage and secure devices for Windows
• Microsoft Copilot in Intune | Microsoft Learn

Windows 11, version 25H2 is now being offered to eligible devices via feature updates. For customers enrolled in hotpatch quality update policies, when the upgrade is taken can affect whether devices continue to receive hotpatch updates during the current hotpatch cycle. Devices that upgrade during a designated baseline release period (such as October) will remain eligible for hotpatching. Devices that upgrade during a non-baseline month (such as November) will temporarily stop receiving hotpatch updates and, until the next baseline release in January 2026, will instead receive standard security updates that require a restart.

[When will this happen:]

The Windows 11, version 25H2 upgrade will be offered starting September 30, 2025, with October 2025 designated as the baseline month for hotpatch eligibility. Organizations should plan their upgrade timing accordingly to maintain hotpatch continuity.

[How this will affect your organization:]

If you are using hotpatch-enabled quality updates in your tenant and a device upgrades to Windows 11, version 25H2 outside of a baseline month, it will temporarily receive standard (non-hotpatch) updates until the next baseline month.

[What you need to do to prepare:]

To ensure devices continue to receive hotpatch updates, please review the following:

• Review your feature update release schedule to ensure devices are positioned to update during baseline months. Look for the release date for your devices in your feature update policy as well as your feature update deferral settings in your Update Rings policies in Windows Autopatch.
• Review the hotpatch servicing cadence and upgrade timing implications. Refer to the Hotpatch FAQ for technical guidance.

[Introduction]

This is a reminder based on our previous communication (MC1117814) regarding the Viva Engage email sender domain update. Please ensure your email configurations are updated, as we plan to roll out the new email domains for your tenant starting Monday, October 6, 2025.

[When this will happen:]

• Rollout begins: Monday, October 6, 2025
• Expected completion: Tuesday, October 7, 2025
• Applies to U.S. and EU tenants currently receiving messages from @yammer.com and @eu.yammer.com.

[How this will affect your organization:]

All emails from Viva Engage will now come from a new domain instead of yammer.com or eu.yammer.com The exact sender domain depends on the data residency for your Viva Engage network:

• US geo: from @yammer.com to @engage.mail.microsoft
• EU geo: from EU​.yammer.com to @eu.engage.mail.microsoft

In addition to the domain change, Viva Engage email addresses will now include a tenant-specific prefix to help differentiate your organization’s environment such as test and production tenants. For example, fabrikam.onmicrosoft.com will result in a “fabrikam” prefix. Continuing with this example, sender addresses may include:

• [email protected] – for digest emails, leader identification, community expert identification, delegate notifications and others.
• [email protected] – for community posts, storyline updates, and other user activity notifications.
• [email protected] – for leadership announcements and other broad communications.

For networks in the EU geo, you should change the sender domain in the examples above to [email protected], etc.

These changes affect all Viva Engage emails, including notifications, announcements, and digests.

[What you need to do to prepare:]

Admins should review these configurations before and during rollout:

• Email Transport / Mail Flow Rules: Update any rules referencing @yammer.com (or EU.yammer.com) to also include @engage.mail.microsoft (and EU.engage.mail.microsoft) so encryption, forwarding, or redirection rules keep working.
• Security Filters: Add the new domains to spam filters or allowlists if they were previously trusted. 
• Outlook Inbox Rules: Notify users to update personal rules that filter by domain (e.g., moving Yammer emails to a folder). Otherwise, Engage emails may land directly in their inbox.
• Safe Senders / Allow Lists: Add the new domains to org-level and user safe sender lists to prevent misclassification as junk.

Please communicate these changes in advance so users know how their rules or filters may be affected. If you don’t use custom rules, no changes are needed; the switch will occur automatically.

Learn more: Viva Engage Email Sender Domain Update

[Compliance considerations:]

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

[Introduction]

This message is associated with Microsoft 365 Roadmap ID 503102.

[When this will happen:]

[How this affects your organization:]

• Who is affected: Admins managing apps and agents in Microsoft Teams Admin Center.
• What will happen:
  • Admins will find additional security and compliance attributes—SOC 2, ISO 27001, GDPR—for apps that are not Microsoft 365 certified or publisher attested.
  • This data will appear in: Teams Admin Center > Teams apps > Manage apps > App details > Security and Compliance tab.
  • Data is sourced from Microsoft Defender for Cloud Apps (MDA).
  • No changes to app enablement/blocking behavior.
  • No impact to user experience.
  • Feature is enabled by default.

[What you can do to prepare:]

• No action is required. This feature will be available automatically in the Teams Admin Center.
• If desired, you may:
  • Review app details in the Security and Compliance tab to inform internal app governance.
  • Communicate this update to helpdesk or security teams.
  • Update internal documentation if you track app compliance attributes.

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

[Compliance considerations:]

We’re introducing multilingual support for Copilot in Viva Glint, enabling users to interact with Copilot in their preferred language. This enhancement removes a key adoption barrier for non-English users and promotes equitable access to AI-powered insights across global organizations.

When this will happen:

General Availability (Worldwide): Rollout will begin in early November 2025 and is expected to complete by late November 2025.

How this affects your organization:

Who is affected:

• Viva Glint customers using Copilot
• Users in non-English locales

What will happen:

• Users can submit prompts in their native language; Copilot will respond in the same language:



• Mixed-language prompts are supported.
• Copilot summaries in the comments panel will match the user’s dashboard language.
• Static UI content (such as starter prompts, prompt guides) will be localized.
• Feature will be enabled by default for all Viva Glint Copilot users.

What you can do to prepare:

• Update internal documentation if you reference Copilot behavior.
• Communicate this change to helpdesk and support teams to prepare for multilingual usage scenarios.

Learn more: 

• Viva Glint supported languages | Viva Glint | Microsoft Viva | Microsoft Learn

Compliance considerations:

We’re introducing a new content explorer experience for cases in Insider Risk Management, now available in public preview. This update enhances the classic content explorer with advanced filtering, grouping options, document preview, column customization, and time zone selection—making it easier for investigators to review case content efficiently. This new experience will apply to all newly created cases in Insider Risk Management.

• Public Preview (Worldwide): Rollout will begin in early October 2025 and is expected to complete by early November 2025.

Who is affected: All Insider Risk Management customers using Microsoft Purview. Admins and investigators managing Insider Risk cases.

What will happen:

• All new cases created after rollout will use the new content explorer experience.
• Existing cases will continue to use the classic content explorer.
• The new experience includes:
  • Advanced filtering and grouping options.
  • Document preview within the explorer.
  • Customizable columns.
  • Time zone selection for better context.
• No changes to existing policies or configurations.
• The feature is enabled by default for new cases.

• No action is required. This feature will be rolled out automatically.
• Learn more: Review data with the Insider Risk Management content explorer

[Compliance considerations:]

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

[Introduction]

Microsoft is retiring the themes feature in user settings for Viva Engage. This change removes the ability for users to personalize their Viva Engage interface with custom themes. While usage of themes is low across Viva Engage tenants, this decision was made due to accessibility limitations in the current themes implementation, which conflict with future feature improvements. The retirement now helps pave the way for a new admin-led branding capability that is in development. This new feature will allow organizations to centrally configure visual elements such as logos, brand colors, and names. It is not yet available and will be communicated separately when ready.

Screenshot 1: Themes will no longer appear in Viva Engage settings

[When this will happen:]

This change will be rolled out early November 2025 and completes mid-November 2025.

[How this affects your organization:]

Who is affected: All Viva Engage users accessing the service via web, desktop apps, Microsoft Teams, or Outlook.

What will happen:

• Users will no longer be able to set personal themes in Viva Engage.
• Existing user-defined themes will be removed, and users will see the default Viva Engage theme.
• This change does not affect mobile apps.

What you can do to prepare:

• No admin action is required. However, we recommend the following:
• Notify your users about the upcoming change to avoid confusion.
• Update internal documentation that references user-set themes in Viva Engage.

Compliance considerations:

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

Microsoft Teams is introducing a new feature in the Teams Admin Center that enables IT administrators to streamline app and agent evaluations using trust-based filters. This enhancement allows filtering by industry-standard security and compliance attributes such as SOC 2, ISO 27001, HIPAA, GDPR, and more—helping organizations make faster, more informed decisions about trusted apps. 

This message is associated with Roadmap ID 503100.

[When this will happen:]

General Availability (Worldwide): Rollout will begin mid-October 2025 and is expected to complete by the end of October 2025.

Who is affected: Admins managing apps and agents in Microsoft Teams Admin Center.

What will happen:

Today, IT administrators can view security and compliance information for apps and agents by navigating to Teams apps > Manage apps > App details page > Security and Compliance tab. This includes data for Microsoft 365 certified and publisher-attested apps.

With this update:

• A new column titled Security and compliance info will be added to the Manage apps list view.
• Admins can filter apps by specific compliance attributes (e.g., SOC 2, ISO 27001, HIPAA, GDPR) to quickly identify trusted apps aligned with organizational standards.
• An enhanced tile on the Manage apps page will highlight Microsoft 365 certified apps that have submitted supporting evidence documents.
• These improvements simplify the app review process and support broader and faster adoption of secure apps.
• The feature will be available automatically and does not change app enablement/blocking behavior.

No action is required.

You may choose to:

• Familiarize yourself with the new filtering options in Teams Admin Center.
• Communicate this enhancement to relevant IT staff.
• Update internal documentation if app review workflows are documented.

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

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

We’re introducing a new productivity feature in Microsoft Teams: Open Channels in a New Window. This enhancement allows users to detach any channel from the main Teams client and view it in a separate window—supporting better multitasking and focus, especially in high-traffic or cross-functional collaboration scenarios.

General Availability (Worldwide): Rollout will begin in late October 2025 and is expected to complete by late November 2025.

• Who is affected: All users of Microsoft Teams desktop client (Windows and macOS).
• What will happen:
  • Users will find a new option to Pop out channel from the channel menu.

  • Screenshot 1: Entry point from left rail

    

    Screenshot 2: entry point from channel header

    

  • The channel will open in a separate window, allowing simultaneous viewing of multiple channels.
  • There are no changes to existing Teams functionality or policies.
  • Feature will be enabled by default for all tenants.

• No admin action is required.
• You may choose to:
  • Inform helpdesk and support staff of the new multitasking capability.
  • Update internal training or documentation if you provide Teams usage guidance.

[Compliance considerations:]

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

[Introduction:]

We’re introducing version history in Microsoft 365 Copilot Pages to help users confidently refine their work. This feature allows users to view and restore previous versions of a page—whether changes were made manually, through Copilot, or collaboratively. This update supports transparency and control in content creation, aligning with customer feedback.

[When this will happen:]

• Public Preview (Worldwide): Begins early October 2025 and completes by late October 2025.
• General Availability (Worldwide): Begins late October 2025 and completes by late October 2025.

[How this affects your organization:]

Who is affected: Users with Entra ID (work or school) accounts who have access to Microsoft 365 Copilot Pages and underlying SharePoint or OneDrive storage. 

Note: A Microsoft 365 Copilot license is not required to use version history in Copilot Pages.

What will happen:

• Users will be able to view and restore previous versions of Copilot pages:

 

• Version history will include changes made manually, via Copilot, or by collaborators.
• The feature will be enabled by default.
• No admin configuration is required.

Admin controls and licensing:

• IT admins cannot disable version history for Copilot Pages.
• Admins can manage how many versions are stored using existing versioning settings in the underlying SharePoint or OneDrive library.
• Copilot Pages are configured to save up to 50 versions per file.
• There are no Copilot Page-specific versioning controls today.
• Version history is available to users with SharePoint or OneDrive storage—even if they do not have a Microsoft 365 Copilot license.
• Copilot Pages are not currently available to personal Microsoft accounts (such as Microsoft 365 Personal or Family).

[What you can do to prepare:]

No action is required at this time.

You may choose to:

• Communicate this change to helpdesk staff.
• Update internal documentation if you reference Copilot Pages functionality.
• Review training materials to ensure users are aware of the version history feature.
• Review your SharePoint or OneDrive versioning settings if you want to adjust how many versions are retained.

Learn more: 

• [to be updated for WW General Availability rollout phase in late Oct. 2025] – How Microsoft 365 Copilot Pages works | Microsoft Support
• Summary of governance, lifecycle, and compliance capabilities for Loop | Microsoft 365 | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

To improve detection accuracy across EU identifiers, we’re updating the definitions of five Microsoft built-in out-of-box bundled (OOB) Sensitive Information Types (SITs). These bundled SITs include EU passport number, EU national identification number, EU social security number or equivalent identification, EU tax identification number, and EU driver’s license number. Bundled SITs contain definitions for multiple EU nations within a single SIT. With this update, we’ve aligned the accuracy of bundled SITs with their standalone counterparts by enhancing supporting keywords and function processors.

[When this will happen:]

General Availability (Worldwide): Rollout began in mid-September 2025 and is expected to complete by mid-October 2025.

[How this affects your organization:]

Who is affected: Admins managing Microsoft Purview policies that use the specified bundled EU identifier SITs.

What will happen:

• Definitions for the five bundled EU OOB SITs will be updated.
• Enhanced keyword and function processor logic improves detection accuracy.
• No changes to standalone SITs.
• Existing policies using these SITs will automatically benefit from improved detection.

No admin action is required to enable the update.

[What you can do to prepare:]

No action is required. However, you may choose to:

• Review existing DLP or Information Protection policies that use these SITs.
• Communicate the update to your compliance or security teams.
• Update internal documentation if you reference these SITs.

Learn more: Learn about sensitive information types | Microsoft Purview | Microsoft Learn

[Compliance considerations:]

[Introduction]

To support broader collaboration scenarios, Microsoft 365 Copilot Chat will now allow users with access to shared mailboxes to ground their conversations in the content of those mailboxes. This update reflects customer feedback requesting more inclusive access to Copilot capabilities across mailbox types.

To use this feature, users must have a Microsoft 365 Copilot license and read access to the shared mailbox.

This update is available across multiple platforms, including Android, Desktop, Developer, iOS, Linux, Mac, Teams, Surface Devices, and Web.

This message is associated with Microsoft 365 Roadmap ID 488797.

[When this will happen:]

• General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late September 2025.

[How this affects your organization:]

Who is affected: Users with access to shared mailboxes in Microsoft 365.

What will happen:

• Users will be able to ground Copilot Chat conversations in shared mailbox content:

 

• The feature will be ON by default for eligible tenants.
• Existing mailbox permissions will determine access; no changes to permission models are required.
• There is no impact to end-user workflow unless Copilot Chat is actively used.

• Communicate this change to shared mailbox owners and users.
• Ensure users understand that anyone with access to a shared mailbox will be able to use Copilot Chat to analyze its email content.
• Update internal documentation if you detail Copilot Chat capabilities.
• No configuration changes are required unless you wish to restrict Copilot Chat access via existing mailbox permissions.

Learn more: Use Copilot in shared mailboxes and delegate mailboxes | Microsoft Support

[Introduction:]

We’re introducing support for Microsoft 365 Copilot in delegated mailboxes. This update enables users with delegate access to use M365 Copilot to reason over emails in those mailboxes, improving productivity and collaboration in shared scenarios. To use this feature, users must have a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 416062.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late September 2025.

[How this affects your organization:]

Who is affected: Users with delegate access to another user’s mailbox in Microsoft 365.

What will happen:

• Users with delegate mailbox access will be able to use Microsoft 365 Copilot to interact with and reason over emails in delegated mailboxes:

 

• The feature will be available on Android, Desktop, Developer, iOS, Linux, Mac, and Web platforms.
• No changes to existing delegate permissions are required.
• The feature will be ON by default for eligible users.
• Admin policies governing mailbox access remain unchanged.

• Ensure users providing delegate access are aware that delegates will be able to use Copilot to reason over emails in the delegated mailbox.
• Communicate this change to helpdesk and support staff.
• Update internal documentation if you detail Copilot capabilities or delegate access.
• No configuration changes are required unless you wish to restrict delegate access to Copilot features.

Learn more: Use Copilot in shared mailboxes and delegate mailboxes | Microsoft Support

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

• Live Conversation View: Monitor all active conversations by channel (chat, voice, records) in a dedicated and organized view.
• Direct actions: Take immediate actions like assign, transfer, monitor, force close, or notify, individually or in bulk.
• Real-Time Sentiment & KPIs: Track sentiment, talk/hold/wrap times, and key metrics to spot and act on at-risk conversations.
• Flexible Filters & Saved Views: Filter by agent, queue, channel, or sentiment; save and share views for team coordination.
• Bulk Management: Handle high-volume scenarios efficiently with multi-record actions.
• Customizable & Extensible: Add custom attributes and expand dashboard features to meet specific business needs.
• Auto Refresh: Keeps data up to date without manual reloads for continuous visibility.

• End-to-End Lifecycle Management: Move visual customizations from development to production without manual rework.
• User-Friendly Interface: A built-in UX allows report authors to easily download, promote, and manage report versions.
• Offline Versioning: Download and store report versions for audit, rollback, and historical tracking.
• Governance & Control: Role-based access ensures only authorized users can manage visual updates.

• Focused Time window filter: Default view now shows data from the past 2 hours (instead of full-day or 24-hour range).
• Business unit level filter: Enables comparison across business units and allows users to isolate metrics for a specific business unit.
• Agent Report Enhancement: Includes visibility into idle agents in real time.

• Set open and close dates for event registration to match your planning timeline.
• Attendees can only register during the defined window.
• When the registration period ends, the registration form is automatically disabled.
• Works seamlessly with reminders and communications, so attendees know when to register.

• Increase automation: Reduce the need for human intervention in intent promotion.
• Improve accuracy and trust: Make sure that only high-confidence, low-risk intents are promoted automatically by using robust validation mechanisms to prevent erroneous promotions.
• Enhance administrator control and flexibility: Allow administrators to configure self-promotion settings at various levels and provide override mechanisms.

• Facebook Ads
• Google Ads
• LinkedIn
• Secure FTP (SFTP)
• Snapchat

• Admins define hierarchy views for their teams. The feature currently supports single-table hierarchies, with support for multiple-table complex hierarchies coming later in the year.
• Customize what data appears on each tile, along with the size, color, and picture or icon. You can show up to seven fields on each tile.
• Define hierarchies by using relationships in your data. You can use single-table (self-referencing) relationships, cross-table relationships, or the Dataverse Connections table for flexible relationships between any two records.

• Zoom in and out and expand and collapse branches so you can efficiently work with customers of all sizes.
• Switch between vertical and horizontal display modes to optimize the view based on the shape of the hierarchy.
• Select a tile to open the details form in a side pane, so you can make updates, add meeting notes, and make other edits without leaving the hierarchy view.

• Display live events for a configured web application in a responsive grid layout
• Search events by name or description
• View detailed information about each event
• Embed the Customer Insights-Journeys registration form

• Automatically get inline field suggestions by copying relevant text or images to your clipboard.
• Paste using the smart paste icon or the keyboard shortcut (Ctrl+V or Cmd+V) when no field is selected and allow AI to analyze the form and clipboard content to suggest field values.
• Choose to accept or ignore suggestions and continue editing the form as needed.
• Paste directly into specific fields as usual by selecting the field first.

• Review your feature update release schedule to ensure devices are positioned to update during baseline months. Look for the release date for your devices in your feature update policy as well as your feature update deferral settings in your Update Rings policies in Windows Autopatch
• Review the hotpatch servicing cadence and upgrade timing implications. Refer to the Hotpatch FAQ for technical guidance.

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting October 1st, 2025 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel

• Wi-Fi 7 support for enterprise access points
• Microsoft Purview to help reduce data breaches and stay current with regulations, certifications, and reporting
• Integrated tools and AI-powered insights in Microsoft Defender
• Windows ML to deploy production experiences
• Windows 365 Frontline—now available for Government Community Cloud (GCC) and GCC High (GCCH)
• Health check for proactive troubleshooting across Windows 365 and Azure Virtual Desktop environments
• Additional improvements released in September

• Windows IT Pro Blog
• Microsoft Intune Blog
• Microsoft Security Blog 
• Windows 11 update history
• Windows Server update history 

• Entities, such as cases and accounts, and their application tabs.
• Focus to the last session or app tab that users viewed.
• After the user’s presence reloads, the browser restores conversations such as calls and chats.

Updated October 1, 2025: We have updated the content documentation link. 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 and 503105.

When this will happen:

We will begin rolling out this feature late September 2025 and expect to complete by mid-November 2025.

1. Phase 1 – Default Tenant Unification

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

We will begin rolling out this feature at the end of October 2025. 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 agent or app availability differences across both admin centers, a wizard in the Teams admin center will help identify affected agents and apps and guide through resolving discrepancies.
• 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.

This message is associated with Microsoft 365 Roadmap ID 503105.

3. Phase 3 – Automatic Unification

Tenants that haven’t transitioned as part of Phase 1 & Phase 2, will be automatically moved to unified app agent management. We will update this post with a timeline and more details later.

How this will affect your organization

Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified agent app management, you will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize.

• You’ll gain a consolidated view of agent and Microsoft 365 app availability across both Microsoft 365 and Teams admin centers.
• Changes made in either admin center to the agent and app availability will automatically apply across all supported hosts.
• Organization-wide defaults for both admin centers will be in sync and govern app availability across Teams, Outlook, and the Microsoft 365 copilot app.

 What you need to do to prepare

To ensure a smooth transition, review your tenant-level and individual agent/app settings (app allow/block & user availability) in both the Microsoft 365 Admin Center and the Teams Admin Center. If different departments within your organization manage these settings, we suggest coordinating efforts to complete the review collaboratively.

This update will be rolled out automatically by the stated date, and no immediate action is required. However, it’s a good time to update any internal documentation related to agent and app management policies. 

Learn more: Unified agent and app availability management across Microsoft 365 and Teams Admin Centers – Microsoft Teams | Microsoft Learn 

Updated October 1, 2025: As previously announced in the October 31st, 2024, post, we will be retiring the Utility.SendEmail API on October 31st, 2025. 

As a reminder, you are able to identify usage of the API via the Purview audit logs in the admin center

1.  As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center.
2. Open Audit to search for activities.
3.  Select a date range to run the audit search for (recommend running it for at least 90 days)
4. Put the following text, “SendEmailApiInvoked” into the “Activities – operation names” textbox and click search.
5. The request will be queued, and results will be available once processed.
6. Click on the results and review each of the items.

Use the UserAgent and ApplicationDisplayName to help identify the caller.

[NOTE:] If the ApplicationDisplayName = “Workflow” then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows.

From custom code the API can be referenced via REST as (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it would be “Utility.SendEmail” with more information on the original implementation at Utility.SendEmail method for CSOM.

[When this will happen:]

October 31, 2025

[How this will affect your organization:]

Any components, custom code, or Power Automate connections that utilize the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement date and will no longer send any email requests from that date.

[What you need to do to prepare:]

Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API.

The following are recommended or alternative approaches:

1. Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages
2. Customizations through Power Automate may also utilize the Outlook connector and utilize “Send an email” within the Actions. Overview of using Outlook and Power Automate 

Learn more:

1. Retirement of the SharePoint SendEmail API
2. Automate creating, sending, and processing messages
3. Overview of using Outlook and Power Automate
4. Learn about the Microsoft Purview portal | Microsoft Learn

Updated October 1, 2025: Today we announced multiple updates to our Microsoft 365 subscription lineup for individuals. Multiple account access allows individuals with these subscriptions to access Microsoft 365 Copilot value while at work through the Microsoft 365 apps.

As mentioned previously, enterprise data protection continues to apply for files accessed with the user’s organizational identity, regardless of which account grants Copilot access. Learn more about what this means for your organization.

If you wish to restrict multiple account access to Copilot, you can use the “Multiple account access to Copilot for work documents” Cloud Policy.

For more information, refer to documentation.

Multiple account access to Copilot in Microsoft 365 desktop and mobile apps will be available soon.

[When will this happen]

General availability (Worldwide): We will begin rolling out in early March 2025 and expect to complete by early July 2025 (previously mid-June).

Cloud Policy to manage use will be available by late January 2025.

[How this will affect your organization]

As an M365 service, Copilot can be used across signed in accounts in clients that allow you to sign in with multiple accounts. This lets users use their Copilot value on any document to which they have permission. Note that Copilot data protection is always based on the identity used to access the file. This ensures enterprise data protection for files in your organization, regardless of which account grants Copilot access. The setting for web grounding in Copilot is also based on the identity used to access the file. If you disabled web grounding in Copilot, users will not be able to use web grounding even when using Copilot access from another account. This feature will be available starting in March 2025, at which point, users signed into accounts with external Copilot licenses will be able to use Copilot on their work and school documents in Word, Excel, PowerPoint, Outlook and OneNote desktop and mobile apps.

[What you need to do to prepare]

If you wish to restrict multiple account access to Copilot, you can use the “Multiple account access to Copilot for work documents” Cloud Policy.  This policy setting is expected to be available in Cloud Policy by the end of January 2025

[Additional information]

For more information, see Multiple account access to Copilot for work and school documents.