Microsoft Roadmap, messagecenter and blogs updates from 13-11-2025

Updated November 12, 2025: We are postponing the GA release for this feature at this time. We apologize for any inconvenience.

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

Copilot license requirements:

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

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

This message is associated with Microsoft 365 Roadmap ID 482198.

[When this will happen:]

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

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

General Availability (Worldwide, GCC): We will update via Message center when we are ready to proceed.

[How this will affect your organization:]

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

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

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

This change will be available by default.

[What you need to do to prepare:]

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

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

Updated November 12, 2025: We have updated the timeline. Thank you for your patience.

This feature will empower administrators to manage the availability of trusted Microsoft Teams apps based on rules, for enhanced security. Admins will be able to manage Microsoft 365 certified apps in the Teams admin center through a new control in Org-wide settings. You can further customize the availability of these apps based on permissions accessed and publisher names. The system automatically checks the Microsoft 365 certified apps that meet all the conditions you specify and makes those apps available.  

This message is associated with Microsoft 365 Roadmap ID 485712.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-January 2026 (previously early December 2025) and expect to complete by early February 2026 (previously mid-December 2025).

[How this will affect your organization:]

Before this rollout, you cannot manage at bulk the availability of Microsoft 365 certified apps. They are only controlled by third-party app tenant settings.

After this rollout, you can manage Microsoft 365 certified apps availability from org-wide settings in the Teams admin center at Manage apps > Actions > Org-wide app settings > Microsoft 365 certified apps. 

You can configure additional criteria from the Customize availability option:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before or after the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. This new control will be disabled by default.

Learn more: Manage org-wide app settings in Manage your apps in the Microsoft Teams admin center – Microsoft Teams | Microsoft Learn (will be updated before rollout)

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

[Introduction]

Multi-Geo In-Region Routing (IRR) enables customers to control the routing of inbound emails. Using IRR, customers can set the geo-region that inbound mail should be routed to for specific Accepted Domains.

This message is associated with Microsoft 365 Roadmap ID 410245.

[When this will happen:]

Public Preview: We will begin rolling out in early October 2025 and expect to complete by end of October 2025.

General Availability (Worldwide): We expect to begin rolling out in early October 2025 (previously early December) and expect to complete by late December 2025.

[How this will affect your organization:]

In-Region Routing (IRR) is disabled by default. If you do not plan to use this feature, no action is required.

For domains where you choose to enable IRR, the feature allows you to route inbound emails to accepted domains associated with specific geo-regions. When these domains are aligned with users located in the same geo-region, emails are fully processed and stored within the recipient’s region. 

If your organization uses Microsoft Purview capabilities such as Data Loss Prevention (DLP), retention policies, or eDiscovery, you may need to review and adjust those policies to ensure they align with the new regional routing behavior.

[What you need to do to prepare:]

• Ensure that admins have the necessary permissions to manage accepted domains and access to either Exchange Online PowerShell or to the Microsoft 365 admin center.
• Review your domain configurations and identify users located in secondary geo-regions.
• Prepare to configure accepted domains with the new geo-region property.
• Review the licensing terms, as Multi-Geo licenses will be indefinitely required to use In-Region Routing:
  • https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide#licensing
  • https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide#getting-started 
• Review the documentation for configuring the feature: Configure Multi-Geo In-Region Routing (In Preview) – Microsoft 365 Enterprise | Microsoft Learn”

We value your feedback and want to hear from you if you have any questions or concerns. Please comment or contact us through the M365 Admin Center if you need any assistance.

[Compliance considerations:]

• Does the change alter how existing user data is processed, stored, or accessed? – Yes. Emails are stored in-region based on domain configuration.
• Does the change modify, interrupt, or disable any Purview capabilities? – Maybe. Depends on how DLP or retention policies are scoped by region.
• Does the change alter how admins can monitor, report on, or demonstrate compliance activities? – Maybe. Regional routing may affect reporting granularity.

Updated November 12, 2025: We have updated the content and the timeline. Thank you for your patience.

[Introduction:]

Prevent screen capture is a Microsoft Teams Premium feature that helps protect sensitive meeting content by blocking screenshots and recordings across supported platforms. When enabled by the meeting organizer, this feature restricts screen capture using native device tools and most third-party apps. It enhances meeting confidentiality and is especially useful for high-security discussions. Desktop Windows and Mobile Android are supported platforms. All other platforms are unsupported. Attendees on unsupported platforms will join in audio-only mode. Organizers and co-organizers can enable this feature via Meeting Options. It is not governed by meeting policy.

This message is associated with Microsoft 365 Roadmap ID 490561.

[When this will happen:]

Targeted Release: We begin rolling out in mid-September 2025 and expect to complete by late September 2025.

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

[How this affects your organization:]

When enabled, platform-specific behavior includes:

• Windows desktop: Screenshots show a black rectangle around the meeting window, including pop-outs.
• Android (phones and tablets): Screenshots and recordings are blocked. Users see a message indicating screen capture is restricted. Applies to key views such as stage, chat, participant list, notes, banners, Copilot panels, and more.
• All other platforms: Audio only mode.

This feature is off by default and must be manually enabled per meeting.

Screenshot – Meeting options with Prevent screen capture (default off). To enable it, please turn on the toggle: 

[What you can do to prepare:]

• Inform meeting organizers and security/compliance teams about the availability and purpose of this feature.
• Review and update internal guidance for Teams Premium usage.
• Ensure mobile devices are Intune-enrolled to support screen capture prevention.
• Familiarize organizers with enabling the feature via Meeting Options.

[Compliance considerations:]

Updated November 12, 2025: We have updated the timeline. Thank you for your patience. 

[Introduction]

To streamline the process of drafting emails from Copilot prompts, we’re introducing an Edit in Outlook button. When a user’s prompt indicates a strong intent to draft an email (such as “Draft an email to my team thanking them for their hard work on Project K”), the button will appear. Clicking it will open Outlook with a pre-populated draft email, including subject and body fields.

This feature is available to all users licensed with Microsoft 365 Copilot, with no need for additional licenses or add-ons.

It works across a broad range of platforms, including Windows Desktop, Mobile, Mac, Web, Teams and Surface Devices, and Linux.

This message is associated with Microsoft 365 Roadmap ID 494510.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late October 2025 and is expected to complete by late November 2025 (previously mid-November).

[How this affects your organization:]

Who is affected: This feature is available to all users licensed with Microsoft 365 Copilot, with no need for additional licenses or add-ons.

What will happen:

• Users will see an Edit in Outlook button when Copilot detects email drafting intent:

 

• Clicking the button opens Outlook with a draft email pre-filled with subject and body.
• No changes to existing admin policies or configurations.
• Feature is enabled by default.
• No additional licensing or add-on is required.
• Supported platforms include:
  • Desktop
  • Developer
  • Linux
  • Mac
  • Teams and Surface Devices
  • Web

[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 detail this feature.

Learn more: What’s new in Microsoft 365 Copilot | September 2025 | Microsoft Community Hub

[Compliance considerations:]

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

Updated November 12, 2025: We have updated the timeline. Thank you for your patience.

[Introduction:]

To improve clarity and control over Frontier feature access, Microsoft is updating the Frontier Admin Control in the Microsoft Admin Center. Starting November 13, 2025, administrators will no longer be able to assign access using groups. This change aligns with feedback to simplify access management and ensure transparency in user-level assignments.

[When this will happen:]

• Change takes effect: November 13, 2025
• Transition period: November 6–13, 2025 (no changes to user assignments allowed during this time)

[How this affects your organization:]

Who is affected:

• Admins managing Frontier access in Microsoft 365 tenants.

What will happen:

• Group-based assignments for Frontier access will be removed.
• Admins will only be able to assign access to individual users.
• From November 6–13, changes to user assignments will be temporarily disabled to support migration.
• Existing group assignments will be converted to individual user entries based on group membership as of November 6.
• Group-based management may return in the future, but is not currently supported.

[What you can do to prepare:]

• Review current Frontier access assignments and identify any group-based configurations.
• Transition group-based assignments to individual users before November 13 to avoid disruption.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect the new assignment method.
• For more information, visit: Frontier program – Microsoft Adoption

[Compliance considerations:]

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

Updated November 12, 2025: We have updated the content. Thank you for your patience.

[Introduction:]

We are expanding Microsoft Purview Data Loss Prevention (DLP) to support Microsoft 365 Copilot, helping organizations safeguard prompts that contain sensitive data. This real-time control helps mitigate data leakage and oversharing risks by preventing Microsoft 365 Copilot—including pre-built agents—from returning a response or using sensitive data for grounding in Microsoft 365 or the web.

This message is associated with Microsoft 365 Roadmap ID 515945.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft tenants with access to Microsoft 365 Copilot (free and paid), including E1, E3, and E5 license holders.
• Admins managing Microsoft Purview DLP policies for Microsoft 365 Copilot.

What will happen:

• Admins can configure DLP policies in the Microsoft Purview portal to restrict Copilot from processing prompts containing selected sensitive information types (SITs), including default and custom SITs.
• Prompts containing sensitive data will not receive Copilot responses and will not be used for external web search or internal Microsoft Graph grounding.
• By default, a DLP for Copilot policy to safeguard prompts are available in simulation mode. Admins can configure this default policy from the Purview portal or the Microsoft Admin Center. You can learn more about the Microsoft Admin Center experience in Message Center post MC1182689.
  

  Screenshot 1

  

  Screenshot 2

   

  Important: At this time, DLP for Copilot policies do not support enforcement based on sensitive information types (SITs). Hence, no users will be impacted under SIT-based conditions. Admins need to create a new policy to enforce DLP for Copilot prompt based on SIT.

[What you can do to prepare:]

• This feature will be available automatically by the specified date with no admin action required.
• Admins can opt-in to use the feature by setting up a new policy. Review your current configuration to assess the impact on your organization.
• To edit or view a DLP for Microsoft 365 Copilot policy, an admin account needs to be a member of a required role group. Data Security AI admins are also able to edit a DLP for Microsoft 365 Copilot policy.
• You may want to notify your users or admins about this change and update your relevant documentation.

Learn more: 

• Learn about data loss prevention | Microsoft Purview | Microsoft Learn
• Learn about the Microsoft 365 Copilot location | Microsoft Purview | Microsoft Learn

Updated November 12, 2025: We are postponing the GA release for this feature at this time. We apologize for any inconvenience.

[Introduction]

We’re introducing AI-powered enhancements to the SharePoint FAQ web part to help content owners keep FAQs accurate and fresh with less effort. These updates are based on customer feedback and aim to improve content reliability and reduce manual upkeep. Key improvements include AI-suggested updates, seamless import of existing FAQs, and the ability to ground answers in SharePoint Pages.

This message is associated with Roadmap ID 482198.

• Public Preview (Worldwide, GCC): Rollout begins in late November 2025 and completes by early January 2026 (previously early December 2025).
• General Availability (Worldwide, GCC): We will update via Message center when we are ready to proceed.

Who is affected: Content authors using the SharePoint FAQ web part with a Microsoft 365 Copilot license.

What will happen:

The following enhancements will be available to improve FAQ management and content accuracy:

• On-demand AI-suggested FAQ updates: Authors can manually trigger a freshness check. AI will analyze grounding files and viewer-submitted questions to identify outdated or inaccurate FAQ entries and suggest revisions.
Screenshot 1: FAQ authors can trigger an on-demand update check whenever new AI-generated update suggestions are available.

Screenshot 2: FAQ authors can review and approve AI suggestions to keep the content accurate and up to date.



• Seamless import of existing FAQs: Authors can copy and paste curated FAQ content directly into the SharePoint FAQ web part, enabling quick integration of existing knowledge assets.

Screenshot 3: FAQ authors can easily import Q&A pairs by simply pasting content.



• SharePoint Page as grounding source: FAQ answers can be grounded in SharePoint content, including the current page or other selected pages, improving response reliability and contextual relevance.

Screenshot 4: FAQ authors can use the current page or existing pages as reference sources.

[What you can do to prepare:]

• No admin action required: The feature will be enabled by default for eligible users.
• Notify content authors and site owners about the new capabilities.
• Update internal documentation or training materials as needed.
• Review the updated FAQ web part documentation when available (expected late November).

Use a FAQ web part in SharePoint (documentation will be updated in late November)

[Compliance considerations:]

Updated November 12, 2025: We have updated the content. Thank you for your patience. 

[Introduction]

We’ve added a new Copilot button that gives users a quick and visible entry point to Copilot directly within the file previewer in OneDrive and SharePoint. This button appears near the bottom-right corner of the file previewer (instead of in the command bar) and surfaces contextual prompts for Copilot-supported file types. It also provides access to the Copilot chat. This feature will be available to users with a paid Copilot license.

This message is associated with Roadmap ID 513432.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-November 2025 and expect to complete by December 2025.

[How this affects your organization:]

Who is affected:

• Users who preview files in OneDrive or SharePoint.

What will happen:

• A new Copilot button will appear in the bottom-right corner of the file previewer.

• This button provides access to Copilot chat and contextual prompts based on the file type.
• The previous Copilot command in the command bar will be removed.
• No changes to admin policies or settings are required.
• This feature is enabled for users with the paid Copilot license add-on.

[What you can do to prepare:]

• No action is required at this time.
• Communicate this change to helpdesk or support staff.
• Update internal documentation to reflect the new location of the Copilot button.

[Compliance considerations:]

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

Updated November 12, 2025: We have added a documentation link. Thank you for your patience.

[Introduction]

We’re improving the panel which shows your Activity in other accounts and orgs in Microsoft Teams to streamline how users triage and respond to cross‑tenant activity. This update reduces the need to switch tenants, helping users stay in context and collaborate more efficiently across organizations.

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

[When this will happen:]

• Targeted Release: Begins rolling out November 16, 2025; expected to complete by November 20, 2025.
• General Availability (Worldwide): Begins rolling out late January 2026; expected to complete by late February 2026.
• General Availability (GCC, GCC High): Begins rolling out early February 2026; expected to complete by late February 2026.
• General Availability (DoD): Begins rolling out mid-February 2026; expected to complete by mid-March 2026.

[How this affects your organization:]

• Who is affected: All Microsoft Teams users with multi‑tenant, multi‑account configurations.
• What will happen:
  • Users gain an improved centralized panel for viewing cross‑organization and cross-account activity notifications, eliminating the need to manually switch organizations or accounts to check notification and activity details. This improves responsiveness and reduces context switching.
  • The entry point for the panel that shows Activity in other accounts and orgs will move from the top-right corner to the bottom-left sidebar in Teams. The entry point icon will appear only when you have more than one account or tenant available to you. 

  

  • The entry point icon will display a count of total missed cross‑org and cross‑account activity notifications.
  • Selecting the icon will open a panel which will show missed activity notifications across all orgs and accounts, grouped by each tenant. If there is no missed activity in a tenant, it will not appear in the panel.
  • Selecting an activity inside the panel opens it in a child window, preserving the context in the main window.
  • Users can pin up to 3 tenants to the sidebar to stay updated. Pinned tenants remain in the sidebar even if there is no missed activity.
  • Selecting a pinned tenant shows a panel with missed activity notifications from that tenant only. Notifications from pinned tenants do not appear in the main panel for activity in other accounts and orgs.

  

  • The feature is enabled by default for tenants where multi‑tenant or multi-accounts are supported and available.
  • No admin configuration is required, the updated panel respects existing tenant and account policies.

Review our new documentation here: Activity in other accounts and orgs – Microsoft Teams | Microsoft Learn.

[What you can do to prepare:]

• Communicate this change to users, including the new location of the Activity in other accounts and orgs panel and the ability to pin tenants to the sidebar.
• Monitor adoption and gather feedback for future iterations.
• No admin action is required for rollout.

Known issue: Cross-cloud notifications do not appear in the Activity in other accounts and orgs panel at this time. This capability is actively being worked on and is expected to be available by the end of November 2025.

[Compliance considerations:]

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

[Introduction]

Microsoft has paused new customer onboarding for calendar sync between Google Workspace and Microsoft Teams. We will update this message and our help documentation when we have more information.

[When this will happen:]

Effective immediately.

[How this affects your organization:]

• Who is affected: Organizations that have not yet completed calendar sync setup between Google Workspace and Microsoft Teams.
• What will happen:
  • Existing calendar sync setups will continue to function and be supported.
  • Organizations that have not interacted with the sync setup in the last 30 days will be unable to initiate new sync configurations.
  • New onboarding for calendar sync is paused until further notice.

[What you can do to prepare:]

• No action is required at this time.
• Learn more: Set up calendar syncing between Google Workspace and Microsoft Teams for your business

[Compliance considerations:]

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

[Introduction]

To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption.

This message is associated with Roadmap ID 523213.

[When this will happen:]

• Public Preview: Rollout begins in late November and is and expected to complete by mid-January
• General Availability: Rollout begins in late January and is and expected to complete by end of January 2026

[How this affects your organization:]

• Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices
• What will happen:
  • A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs
  • The wizard dynamically adjusts based on your organization’s security policies
  • Supports MFA setup, with emphasis on Microsoft Authenticator push notifications
  • This tool is optional and designed to improve BYOD Microsoft Teams adoption

[What you can do to prepare:]

• Review the admin documentation to understand the onboarding wizard’s capabilities and limitations
• Consider integrating the wizard into your new user onboarding workflows
• Communicate availability to helpdesk and frontline managers
• Update internal documentation if you support BYOD Microsoft Teams deployment

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

[Compliance considerations:]

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

[Introduction]

This message is a follow-up notice to retire the legacy CDN domain publiccdn.sharepointonline.com. After this rollout completes, content referenced via the legacy domain will no longer be accessible, and users will receive 404 errors when trying to access resources hosted on the legacy domain.

[When this will happen:]

[How this affects your organization:]

• Organizations using SharePoint Online with applications, scripts, or configurations that hardcode the legacy CDN domain.
• Developers using SharePoint Framework (SPFx) with hardcoded cdnBasePath values.
• Admins who have configured domain-based allow lists in their network settings.

What will happen:

• The legacy domain publiccdn.sharepointonline.com will be retired.
• Any content referenced via the legacy domain will return 404 errors.
• The same resources remain available through the new CDN domain public-cdn.sharepointonline.com.
• The legacy domain previously served as an automatic hosting endpoint for SharePoint resources.
• The 404 error does not indicate data loss—only the access path is affected.
• Hardcoded references to the legacy domain will fail once the domain is retired.

[What you can do to prepare:]

• Review your applications, scripts, and configurations for any hardcoded references to publiccdn.sharepointonline.com.
• Update affected components to use supported and dynamic endpoints to ensure continued functionality.
• For SPFx applications:
  • If using an external CDN, it’s fine to update the cdnBasePath.
  • If relying on automatic hosting through the Microsoft 365 Public CDN, do not hardcode cdnBasePath—leave it unchanged, shown in the code snippet box below. For more details, refer to Update your solution project for the CDN URLs.

{
  "cdnBasePath": "<!-- PATH TO CDN -->"
}

• Ensure public-cdn.sharepointonline.com is included in your domain-based allow lists.
• Validate your updates before March 31, 2026 to prevent potential service disruptions.
• Monitor network traffic and optionally block requests to the legacy domain to confirm that content hosted through the CDN continues to function properly.
• Learn more: Overview of the SharePoint Framework

[Compliance considerations]

This update introduces new remediation actions in Microsoft Defender for O365 that can be triggered directly from the Advanced Hunting interface. These actions—previously only available in Threat Explorer—include “Submit to Microsoft” and “Initiate automated investigation.” This enhancement enables security teams to respond to threats more efficiently and programmatically using custom queries, aligning with customer feedback to streamline incident response workflows.

General Availability (Worldwide): We began rolling out this feature on November 10, 2025.

Who is affected:

• Admins and Security Analysts using Microsoft Defender XDR and Advanced Hunting.

What will happen:

• New actions will be available directly from Advanced Hunting results:
  • Submit to Microsoft
  • Add entries to Tenant allow/block list
  • Initiate automated investigation
• These actions are enabled automatically and available by default; they cannot be removed from the user interface.
• Existing admin policies are respected; no policy changes are required.
• Threat Explorer will continue to be available; both interfaces will coexist.

• Review and update existing hunting queries and playbooks to incorporate new actions.
• Communicate the change to SOC teams and relevant stakeholders.
• Provide training or documentation as needed.
• If you want to scope access to these actions, use role-based access control (RBAC) in Microsoft Defender XDR.
  • Click path: Microsoft 365 Defender portal > Settings > Permissions > Roles

Learn more: Take action on advanced hunting query results in Microsoft Defender XDR – Microsoft Defender XDR | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

To improve discoverability and simplify configuration, we’re updating the Microsoft 365 admin center to consolidate people-related settings. As part of this update, controls for Name Pronunciation and Pronouns will be relocated to the People settings section under Org Settings. This change helps administrators manage user profile settings more efficiently.

General availability (Worldwide): This change will begin rolling out in late November 2025 and will complete by mid-December 2025.

Who is affected:
Admins managing user profile settings in the Microsoft 365 admin center.

What will happen:

• Name Pronunciation and Pronoun settings will no longer be editable in their previous location.
• These controls will now be accessible under People settings in Org Settings.
• No new controls are introduced, and existing feature behavior remains unchanged.
• The update is applied automatically; no opt-in or toggle is required.

No action is required to enable this change. However, we recommend:

• Informing help desk and support teams of the new settings location.
• Updating internal documentation or admin training materials.

• Learn about the People settings: Manage people data and related experinces from the microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn
• Learn about Name pronunciation controls: Manage name pronunciation settings for an organization by using the Microsoft Graph API – Microsoft Graph | Microsoft Learn
• Learn about Pronouns controls: Turn pronouns on or off for your organization in the Microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn

Copilot is making it easier to manage scheduling conflicts by automatically rescheduling 1:1 meetings and personal events. Within the meeting event form, users can indicate which events are more flexible and allow Copilot to reschedule them if conflicts arise. Users can also set preferences for when rescheduled events should occur. Copilot will detect double-bookings and automatically move these flexible events to a better time—saving users time and reducing manual coordination.

A Microsoft Copilot license is required to utilize this functionality.

[When this will happen:]

Targeted Release: Rollout begins mid-November 2025 and expected to complete by late November 2025.

[How this affects your organization:]

Copilot users will gain the ability to automatically resolve scheduling conflicts for 1:1 meetings and personal events. This feature is especially useful for users with recurring 1:1 series that do not need to occur at a specific time each week, helping automatically reschedule those meetings if a conflict arises. The feature is available for Copilot-licensed users and can be enabled through the meeting form.

Main form with new toggle control for automatic rescheduling:

Users can specify their rescheduling preferences (if not set, Copilot will pick intelligent defaults):

This post will be updated with a link to the support article once published.

[What you can do to prepare:]

No admin action is required. However, you may want to:

• Inform users about this new capability and how to set their rescheduling preferences in the meeting form.
• Review any internal guidance on calendar management or Copilot usage to ensure alignment.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Yes – Calendar data is used to identify and reschedule events.
• Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? Yes – Copilot uses AI to analyze and reschedule events.
• Does the change provide end users any new way of interacting with generative AI? Yes – Users interact with Copilot to manage scheduling.

[Introduction]

We are updating the user interface (UI) for Copilot Chat in Outlook for Android so that the button is separate from the mail compose, event compose, and add a contact button. This feature will be available for users with a M365 Copilot license.

General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in early December 2025 and is expected to complete in early December 2025.

Who is affected:

• Users who have a Copilot license and use Outlook on Android.

What will happen:

• Users will see a distinct Copilot Chat button, separate from mail and event compose buttons.

Screenshot 1: Mail view



Screenshot 2: Calendar view



• This update improves clarity and ease of access to Copilot Chat.
• No changes to functionality or permissions.
• The feature is enabled by default for eligible users.

• No admin action is required.
• You may wish to:
  • Inform helpdesk staff of the UI change to reduce potential confusion.
  • Update internal training or documentation if it references the previous button layout.

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

• Control over which content is approved for deployment to which devices 
• Automation of a safe rollout process 
• Faster security with hotpatching 
• Pausing or expediting monthly quality updates or drivers 
• Simplified update compliance reporting 
• Policy management and reporting through the Microsoft Intune admin center 

1. Go to the Microsoft Intune admin center. 
2. In the left pane, select Tenant administration and then navigate to Windows Autopatch > Autopatch groups. 
3. Create a Windows Autopatch group and assign devices, automating a few things: 
4. Distribute devices for gradual rollout into a set of Microsoft Entra groups. 
5. Configure a safe rollout schedule using update rings. 
6. (Optional) Configure content approval using feature and driver update policies. 
7. (Optional) Configure update settings for Microsoft 365 Apps and Microsoft Edge. 
8. Enroll devices to receive hotpatch updates, getting them secure faster. 
9. That’s it! Just monitor the reports to ensure that you’re hitting your update compliance targets. 

• Read the announcement at Windows Autopatch for the US government: How to get started. 
• Double-check that your devices meet the prerequisites for Windows Autopatch. 
• Configure role-based access control to manage access to your organization’s resources. 
• Configure your network.