Microsoft Roadmap, messagecenter and blogs updates from 12-09-2025

Updated September 11, 2025: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft PowerPoint: Users will be able to create presentations with Microsoft 365 Copilot in PowerPoint with your organization’s brand images in two ways:

• With an organizational asset library (OAL) in Microsoft SharePoint
• With a Templafy library (a third-party solution)

NOTE: You can choose either option, both options, or neither option. The current image default option in PowerPoint is Microsoft 365 images. If you take no action, your users will continue to have access to these Microsoft 365 images.

This message is associated with Microsoft 365 Roadmap ID 475055 and Microsoft 365 Roadmap ID 475064.

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

This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint for the web.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early June 2025 (previously March) and expect to complete by early July 2025 (previously late June).

[How this will affect your organization:]

Connecting your OAL to Microsoft 365 Copilot in PowerPoint:

After this rollout: As an admin, after you connect your OAL, hosted on SharePoint, to Microsoft 365 and Microsoft 365 Copilot, your users will be able to create presentations with your organization’s images. Users will have the option to use branded images from your OAL and/or Microsoft 365 images.

To use your OAL with Microsoft 365 Copilot, you will need to:

1. Create an organization assets library for your company’s brand assets
2. Run a Microsoft PowerShell command to connect your image OAL to Copilot.
3. Make sure the images in your asset library have robust metadata (keywords, title, and alt-text) so they are searchable

Connecting Templafy to Microsoft 365 Copilot in PowerPoint:

After this rollout: As an admin, please send a request to [email protected] to access this feature. After you connect your asset library hosted by Templafy to Microsoft 365 and Microsoft 365 Copilot, your users will be able to create presentations with your organization’s images.

Users will have the option to use branded images from your organization’s library in Templafy and/or Microsoft 365 images.

To use your brand images with Microsoft 365 Copilot, you will need to:

1. Have a Templafy account for your company’s brand assets
2. Enable Microsoft Graph Connector to establish the Copilot connection in your company’s Templafy account setting. Learn more: How to enable Microsoft Graph Connector for Templafy Image Library – Templafy Help center
3. Make sure the images in your asset library have robust metadata (keywords, title, and alt-text) so they are searchable

To use brand images in PowerPoint, users can select the Copilot icon in the top left of any slide and choose Create a new presentation:

On the next screen, users enter a prompt to ask Copilot to build the slide outline. After Copilot responds, users can scroll down to the Image settings. Users can pick if they want Copilot to use branded images from their organization’s library and/or Microsoft 365 images”.

The new features will be available by default for admins to configure for their users. With this rollout, Copilot will first use images from your organization library before using Microsoft 365 images as backup. Users have the option to use only on-brand images by turning on the image settings. However, if you do not wish for Copilot to use any Microsoft 365 images when creating a presentation, send an email to [email protected]. NOTE: Disabling all Microsoft 365 images will severely impact the Copilot output for creating presentations. We recommend considering this option only if you have more than 1,000 images with robust metadata in your image library.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more

• Keep your presentation on-brand with Copilot – Microsoft Support (will be updated before rollout begins)
• Connect organizational asset libraries to Copilot for an on-brand experience – SharePoint in Microsoft 365 | Microsoft Learn
• Create an organization assets library – SharePoint in Microsoft 365 | Microsoft Learn

Updated September 11, 2025: We have updated the timeline. Thank you for your patience.

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically set their work location to reflect the building they are working in. This feature is opt-in and requires you to take action to configure it.

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

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

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

[How this will affect your organization:]

This feature allows you to map Wi-Fi networks and devices to buildings, which allows your users to have their work location automatically configured when they connect. This is a major improvement over the current experience which relies on end-users to manually set their work location. When this feature is configured and enabled, Teams can automatically update the work location of users who connect their laptop to your organization’s Wi-Fi network or peripherals. The feature can leverage the mapping between your building names and your Wi-Fi networks to set the work location of your users to the right building. It can also leverage mappings to specific peripherals, such as monitors. Teams uses the same policy to enable or disable automatic updates of work location for Wi-Fi and peripherals. Learn more: New-CsTeamsWorkLocationDetectionPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Teams will not update the location of your users if they connect after their working hours (that they can configure in the Microsoft Outlook Calendar). Also, their work location will be cleared at the end of their working hours.

[What you need to do to prepare:]

Automatic update of work location is off by default, but it can greatly improve the experience of your users. We recommend turning it on and configuring it in your tenant.

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

Updated September 11, 2025: We have updated the timeline. Thank you for your patience.

What and Who

To enhance the security and integrity of Microsoft Teams meetings, we are introducing a new feature that validates Teams meeting join URLs. This update helps ensure that meeting links are not altered or rewritten by security products in ways that could render them unusable or flagged as malicious. This is applicable only when user Joins a meeting from Teams old calendar.

Rollout Schedule

• Worldwide: September 30, 2025
• GCC, GCC High, DoD: November 30, 2025

Impact on Your Organization

• Who is affected:
  • Organizations that use security solutions to inspect or rewrite URLs, as well as users who join Microsoft Teams meetings through the Teams platform, will be affected by this update.

What will happen:

• Users using New Calendar App:
  
  • For new calendar app in Teams, Meeting joins will not be blocked instead users will be redirected to a outlook safelinks provider and again redirected to the destination rewritten Join url
  • This feature is enabled by default and does not require admin configuration.
  • For more information on New calendar in app in Teams follow this link: https://support.microsoft.com/en-us/office/get-started-with-the-new-calendar-in-microsoft-teams-98f3b637-5da2-43e2-91b3-f312ab3e4dc5 

Old Teams Calendar App:

• Microsoft Teams will validate join URLs to ensure they have not been modified.
• If a join URL is rewritten or altered by a security product, it may be marked as malicious.
• Users will be prevented from joining meetings if URLs are not in their original format.
• This feature is enabled by default and does not require admin configuration.
• Microsoft’s advanced email security platform, including Safe Links (URL inspection/rewriting), will not be impacted by this update.
• Safe Links Behavior:
  • Does not rewrite the URLs behind the “Join Teams meeting” or “Join” buttons.
  • Only rewrites URLs within the meeting invitation body.
  • Any temporary rewriting (if applied) is removed by Exchange Online upon send/receive.
• Outlook Add-in Behavior
  • If meeting links are rewritten via Outlook add-ins during meeting creation, there is no impact.
• Potential impact:
  • This change may affect third-party security services that rewrite both the body URLs and the “Join” button URLs.
• Action required:
  • No action is needed for customers using Safe Links. There is no requirement to add Teams meeting URLs to the Safe Links “allowed list.”
  • For the customer using 3P solutions, they must ensure Teams join links are excluded from rewriting.
  • Compliance Considerations: No compliance considerations identified, review as appropriate for your organization.
• Workaround: Switch to New calendar to unblock users from joining the Meeting.

Platforms affected

• Only Microsoft Teams affected, other platforms like outlook web and win32, outlook mac remain unaffected.

Updated September 11, 2025: This release is intended solely for commercial cloud environments. Separate release timelines will be communicated for special clouds and on-premises segments in dedicated posts.

We’re introducing the new Microsoft Teams calendar experience, designed to unify and enhance productivity across Microsoft 365. This calendar integrates familiar features with innovations like Microsoft Copilot and Microsoft Places, enabling seamless collaboration from anywhere. It works consistently across Teams, the new Outlook for Windows, Outlook on the web, and Places. As part of this update, the legacy calendar experience will be deprecated, and the toggle to switch between old and new calendars will be removed.

When this will happen

• Public Preview: Early September 2025 – Mid September 2025
• Targeted Release: Early September 2025 – Mid-September 2025
• General Availability (Worldwide): Mid-September 2025 – End September 2025
• General Availability (Gallatin, GCC, GCC High, DoD, USSec): Mid-November 2025 – Late November 2025
• General Availability (USNat): Late November 2025 – Early December 2025

Once this update is deployed, users accessing the Calendar app in Microsoft Teams will see the new calendar experience by default. The toggle to switch between the old and new calendar will be removed, and only the new Microsoft 365 calendar will be available. This change may impact users accustomed to the legacy calendar interface.

No admin action is required. We recommend informing your users about the upcoming change and updating any internal documentation or training materials that reference the legacy calendar experience.

For more information about the new calendar experience, visit the Microsoft Teams documentation.

Compliance considerations

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

Updated September 11, 2025: We have updated the timeline. Thank you for your patience.

Introduction

You can now deploy, manage, and measure a frontline worker (FLW) pilot directly from Teams Admin Center. This new capability enables Teams administrators to define pilot users and owners, configure workloads, and monitor adoption—all in one place. It’s designed to help IT admins and business leaders streamline the rollout of Teams features tailored for frontline teams.

This message is associated with Microsoft 365 Roadmap ID 498226

When this will happen

Public Preview: Rolling out early November 2025; expected completion by mid-November 2025.

General Availability: Rolling out mid-November 2025; expected completion by late November 2025.

How this affects your organization

This feature provides a simplified experience for piloting Teams capabilities for frontline workers. Admins can:

• Select and configure workloads such as Chat, Channels, Shifts, Walkie Talkie, Viva Engage, and Tasks.
• Assign pilot users and owners.
• Share access to the Teams mobile app via QR code.
• Monitor adoption and usage insights directly in Teams Admin Center.

What you can do to prepare

To prepare for this rollout:

• Identify frontline worker pilot participants and the workloads you want to enable.
• Review your Teams Admin Center settings to ensure you have the necessary permissions.
• Plan communications with pilot users to support adoption.
• Learn more: [Link to be provided]

Compliance considerations

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

Updated September 11, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing Immersive Search, a new experience across Outlook for Web, Mac, iOS, Android, and the new Outlook for Windows. After performing a search, users will see an entry point to the Microsoft Copilot side pane, which presents a highly relevant, AI-generated summary based on their query. This summary includes content from emails, Teams messages, and documents—helping users quickly understand and act on their information.

This feature uses Microsoft 365 Copilot with an Outlook-specific experience and is available only to tenants with Copilot licenses.

This message is associated with Microsoft 365 Roadmap ID 498319.

When this will happen

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

How this will affect your organization

Once rolled out, users will see a new entry point to the Copilot side pane after executing a search in Outlook. This pane surfaces AI-generated summaries, improving productivity and reducing time spent navigating search results.

Copilot side pane in Outlook search results:

Key details:

• The Copilot side pane appears only after a user performs a search and selects the entry point on the search results page (SERP).
• Summaries include all content supported by Microsoft 365 Copilot, such as indexed emails, Teams messages, attachments, and shared files from OneDrive or SharePoint.
• This feature is on by default and does not require admin configuration.
• There are no changes to existing DLP, eDiscovery, or retention policies.
• Admins cannot control access to this feature via policy settings or Entra ID group membership.
• There is currently no setting in the Microsoft 365 admin center or Outlook user settings to manage or disable this experience.
• There is no way to monitor or audit usage of this feature through Microsoft Purview or Microsoft 365 audit logs.

What you can do to prepare

No action is required at this time. However, we recommend informing users about this new experience to reduce confusion and help desk inquiries.

You may also want to review your organization’s Copilot licensing and ensure users are aware of how to use the Copilot side pane effectively.

Compliance considerations

Updated August 22, 2025: After further review, this has been delayed to a later date. We apologize for any inconvenience.

Introduction

We’re enhancing the quarantine experience in Microsoft Defender and Exchange Online to improve visibility and control over items that have been temporarily deleted. With this update, users will be able to view and restore messages that were previously removed from the quarantine view but still exist in the system.

When this will happen

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

How this affects your organization

Users in both Microsoft Defender and Exchange Online quarantine portals will gain the ability to:

• View messages that were temporarily deleted from quarantine using the new Temporarily deleted filter under Release Status.
• Restore these messages back to the quarantine view using the new Restore temporarily deleted option.

Messages that have been permanently deleted will remain inaccessible. This feature is on by default and applies only to temporarily deleted items.

What you can do to prepare

• Inform users about the new filter and restore option to reduce confusion and potential help desk calls.
• Update internal documentation or training materials to reflect the new functionality.
• Monitor user feedback and usage to determine if additional guidance or support is needed.

No configuration changes are required to enable this feature.

Compliance considerations

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

[Introduction]

We’re streamlining how Microsoft Purview policies apply to unmanaged cloud apps accessed via the Edge browser. These updates reduce manual steps for admins and improve policy enforcement across browser environments, especially for organizations managing data sharing to Generative AI (GenAI) apps.

This change builds on the existing preview feature.

This message is associated with Microsoft 365 Roadmap ID 486368.

• Public preview is in progress.
• General availability: Rollout will begin in mid-October 2025 and is expected to complete by late October 2025.

[How this affects your organization:]

• Who is affected:
  • Admins managing Microsoft Purview collection and DLP policies targeting unmanaged GenAI apps in the browser.
  • Organizations using Microsoft Edge for Business and Edge configuration policies that activate Purview policies.
• What will happen:
  
  • Collection Policies
    
    • Previously: Required separate Edge configuration policy to apply protections with a browser blocking configuration.
    • Now: Collection policies apply directly in Edge without blocking configuration.
• DLP Policies
  • Previously: Admins manually created Edge configuration policies to block unsupported browsers.
  • Now: Edge configuration policies are automatically created and scoped to match DLP policies when DLP policies are created or updated.
• User experience:
  • Edge for Business: No impact.
  • Chrome with Purview extension: Browser usable; access to unmanaged GenAI apps is blocked.
  • Firefox and other browsers: Users are blocked from using the browser entirely.
• DLP Policy Modes:
  • Audit mode: Policy created but browser blocking is optional.
  • Block mode: Policy created and browser blocking is enforced.
• [What you can do to prepare:]
  • No action is required to enable these changes.
  • Inform your DLP and IT Admins of this update.
  • If you previously created Edge configuration policies scoped to all users and want to rely on automation:
    • Disable or delete the old Edge configuration policy.
    • Update your Purview DLP policy to trigger the automated behavior.
  • Learn more: Set up Microsoft Purview DLP policies in the Edge management service 

We’re introducing an enhanced organization chart experience in the Profile Card in Microsoft Teams for Windows Desktop, Mac, and Teams on the web. This update improves the user interface and navigation while maintaining the core browsing functionality. These changes are based on user feedback to streamline org chart exploration and reduce friction in navigating team structures.

This feature is associated with Microsoft 365 Roadmap ID: 500696.

Targeted Release: We will begin rolling out in late October 2025 and expect to complete in November 2025.

General Availability (Worldwide): We will begin rolling out in late November 2025 and expect to complete in December 2025.

Who is affected: All users of Microsoft Teams on Windows Desktop, Mac, and web platforms.

What will happen:

• The organization chart in the Profile Card will receive UI/UX enhancements to improve navigation and usability.
• The focused individual remains centered when the manager chain is collapsed, improving visual clarity.
• Fewer clicks are needed to view another person’s Profile Card from the current view, reducing navigation effort.
• New navigation buttons allow users to scroll through previously viewed individuals within the same Profile Card instance, streamlining org chart exploration.
• The feature is enabled by default and requires no configuration changes.

Screenshot 1 – Updated Profile Card with centered individual and collapsed manager chain:

Screenshot 2 – Expanded organization chart view:

What you can do to prepare

• No admin action is required at this time.
• We recommend informing users about the improved navigation experience to help them take full advantage of the update.
• Update internal documentation or training materials if they reference the Profile Card experience.

Learn more (to be updated closer to rollout): Profile cards in Microsoft 365 | Microsoft Support 

Compliance considerations

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

• September 2025 security update: The enhanced CSP policy is available to configure using Microsoft Intune or other mobile device management (MDM) tools. 
• October 2025: The GPO policy will be available for commercial use. The GPO will also support a locked down layout experience (bringing parity to current CSP policy). 

• Customize the Start layout for managed Windows devices 
• Configure Start Pins CSP