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

Updated November 11, 2025: Based on customer feedback we have decided not to proceed with this change. Thank you for your feedback.

Beginning mid-August 2025, the New Outlook for Mac will become the default experience for users in the Current Channel (version 16.100 and later). As part of this change, the admin preference key EnableNewOutlook—which previously allowed control over the default toggle state—will be retired. Users will no longer be able to switch back to Legacy Outlook starting with version 16.102 in mid-October 2025.

This update reflects our commitment to delivering a modern, performant, and reliable Outlook experience.

[When this will happen:]

• Legacy Outlook toggle admin perference i.e. EnableNewOutlook retired: Mid-August 2025 (version 16.100 and later)
• Users can no longer switch to legacy Outlook: Mid-October (version 16.102 and later)

[How this affects your organization:]

• The New Outlook for Mac will be the default experience for all users in the Current Channel.
• The EnableNewOutlook admin configuration key will no longer be honored in configuration profiles.

The New Outlook is built on Microsoft’s modern sync technology and offers:

• Improved performance and reliability
• Enhanced support for modern collaboration features
• A consistent cross-platform experience

It also supports key enterprise capabilities including:

• On-premises support
• Online Archive
• Shared Mailboxes and Calendars
• Delegation

Some features not yet available in New Outlook include:

• AppleScript
• Import/Export
• Public Folders

For the latest feature availability, please refer to the Microsoft 365 Roadmap.

[What you can do to prepare:]

• Notify users that New Outlook will become the default.
• Update training materials and internal documentation to reflect the new experience.
• For questions or support, users can go to Help > Contact Support in Outlook for Mac.
• For tenant-level questions or to tailor communications, please use your Message Center submission workflow or contact your Microsoft account team.

More information: End of support for legacy Outlook for Mac

Updated August 13, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

Coming soon for Microsoft Copilot in Teams: Intelligent meeting recap will be able to incorporate content shared on screen into the AI-based summary provided after the meeting, providing a richer and more comprehensive recap of the meeting. Intelligent meeting recap will capture details shown when a participant shares their screen, ensuring those unspoken insights become part of the meeting recap.

This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

This feature requires a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 490052.

[When this will happen:]

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

[How this will affect your organization:]

Copilot users will receive intelligent recap summaries that incorporate shared-screen content, preserving every detail and its context.

This feature will be available by default with no admin controls.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before 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.

Learn more: Intelligent recap for Teams calls, meetings, and events – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

Updated November 11, 2025: This capability has been cancelled for now. We recognize its importance and plan to reintroduce it as part of upcoming Copilot enhancements in PowerPoint at a later time. No admin action needed.

We’re introducing a new capability in Microsoft 365 Copilot for PowerPoint that allows users to reference Excel files when creating a slide. This enhancement helps users seamlessly reuse data from Excel to generate more informative and data-driven presentations.

This message is associated with Microsoft 365 Roadmap IDs 497537, 497538, and 497539.

When this will happen

General Availability (Worldwide): This capability has been cancelled for now.

How this will affect your organization

With this update, users can now reference an Excel file when selecting “New Slide with Copilot” from the PowerPoint ribbon or “Add a slide” from the Copilot button above the slide. This enables more efficient content creation by leveraging existing Excel data directly within PowerPoint.

Key details:

• Users can reference one Excel file at a time when creating a slide.
• The Excel file must be stored in OneDrive or SharePoint.
• Recommended file size for optimal performance is 24MB.
• Users can include a topic in their prompt to focus the slide content.
• Copilot can generate slides that include charts or tables based on the Excel data.
• This feature is available on web, Win32, and Mac platforms. There are no browser-specific limitations.

This feature is on by default and does not require admin configuration.

What you need to do to prepare

• This feature requires the Microsoft 365 Copilot add-on license. It is not included in standard Microsoft 365 SKUs (e.g., E3/E5).
• Available only to tenants with Microsoft 365 E3/E5 plus the Copilot license.
• There are no admin controls to enable, disable, or scope this feature.
• Users can reference a file by clicking the paperclip icon or typing a backslash to select a file.
• Only one file can be referenced per slide. The file must be an Excel format and stored in OneDrive and SharePoint.

No admin action is required for this feature to become available. We recommend informing your users so they can take advantage of this new capability.

Learn more: Reinvent productivity with Microsoft 365 Copilot

Compliance considerations

Updated November 11, 2025: This capability has been cancelled for now. We recognize its importance and plan to reintroduce it as part of upcoming Copilot enhancements in PowerPoint at a later time. No admin action needed.

Introduction

We’re introducing the ability to reference a PDF file when creating a slide using Copilot in PowerPoint. This enhancement enables users to extract and reuse content from cloud-stored PDFs, streamlining slide creation and improving productivity.

This feature is associated with Microsoft 365 Roadmap IDs 497536, 497540, and 497541. 

When this will happen

General Availability (Worldwide): This capability has been cancelled for now. 

How this will affect your organization

With this update, users can reference PDF files stored in OneDrive or SharePoint when using the “New Slide with Copilot” button in PowerPoint or the “Add a slide” option from the Copilot pane. Copilot will access the entire PDF file (text-based only) to generate slide content.

Key details:

• Supported files: Text-based PDFs stored in OneDrive or SharePoint. Password-protected or scanned/image-based PDFs are not supported.
• File size: Recommended maximum size is 24MB for optimal performance.
• Platform support: Available across PowerPoint for Windows, Mac, and Web.
• Prompting guidance: Users can click the paperclip icon or use the backslash (\) to reference a file. For large files, including the topic of interest in the prompt improves results.
• Licensing: Requires the Microsoft 365 Copilot add-on ($30/user/month). Not available with Copilot included in Microsoft 365 SKUs alone.
• Availability: This feature is available to tenants with Copilot enabled. There are no admin controls to enable or disable it.
• User control: Users can choose to keep or delete Copilot-generated slides.
• Telemetry: Usage of this feature is tracked.

This feature does not remove or alter any existing functionality. It is being added to the existing “New Slide with Copilot” experience.

What you need to do to prepare

• Inform your users about this new capability.
• Encourage them to explore how referencing PDFs can help them create slides more efficiently.
• No admin action is required for this update.

Learn more: Add a slide from a file with Copilot in PowerPoint

Compliance considerations

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

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

[Introduction]

We’re introducing enhanced Microsoft 365 Copilot connectors for people data to help organizations enrich Microsoft 365 people profiles with authoritative information from external systems. This update improves Copilot’s ability to deliver contextually relevant and personalized responses across Microsoft 365 experiences such as profile cards and people search.

Administrators can configure connectors to supported systems like BambooHR directly from the Copilot > Connectors > Gallery, under the Human resources & recruiting category. Additionally, customers and partners can build custom connectors via Microsoft Graph to ingest people-related data from other sources. These capabilities allow Copilot to ground its responses in richer, more accurate people data.

This message is associated with Microsoft 365 Roadmap ID 480736.

• Public Preview (Worldwide): Began mid-May 2025 and completes by mid-November 2025.
• General Availability (Worldwide): Begins mid-November 2025 and completes by mid-December 2025.
  • The BambooHR connector is available WW as of Friday the 14th of November.

Who is affected: Microsoft 365 administrators, developers building custom connectors, organizations using Microsoft 365 Copilot, people search, or profile cards.

What will happen:

• Administrators can configure connectors via Microsoft Admin Center under Copilot > Connectors > Gallery.
• BambooHR is available as a prebuilt connector.
• Developers can build custom connectors using Microsoft Graph.
• Enriched people profiles will be accessible in Microsoft 365 experiences and Copilot.
• Improved grounding for Copilot responses using external authoritative data.
• The feature is available for administrators to configure for all tenants once rolled out.

• Review the Microsoft Learn documentation for guidance on configuring or developing connectors.
• Monitor for updates between Public Preview and General Availability.
• Evaluate your organization’s data sources for people-related information.
• Communicate this change to IT and helpdesk teams.
• Update internal documentation if needed.
• Learn more about Copilot connectors compliance, privacy, and data usage.

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

[Introduction]

Browse your company’s approved logos, icons, and photos right inside PowerPoint—no need to search elsewhere. We’re introducing Brand Images in PowerPoint to help users easily access company-approved logos, icons, and photos directly within the app. This feature streamlines brand compliance and saves time by eliminating the need to search for assets externally.

This message is associated with Microsoft 365 Roadmap ID 509111.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: All users of PowerPoint in Microsoft 365 tenants with an Organization Assets Library (OAL) configured.

What will happen:

• Users will be able to browse and insert approved images directly from a centralized library in PowerPoint.
• The feature will be ON by default for all tenants. Admins must set up their SharePoint OAL for employees to use this feature effectively.
• Admins can manage which images are available, ensuring brand consistency and compliance.
• Reduces the risk of using outdated or unauthorized images.
• No impact to end-user workflow unless the OAL is not set up.

[What you can do to prepare:]

• Set up the OAL: Create an organization assets library | SharePoint in Microsoft 365 | Microsoft Learn
• Upload enterprise images: Add approved logos, pictures, and other image type assets to the designated SharePoint library.
• Create folders by asset type (e.g., logos, images) to enable type-based filtering. Note: Only top-level (L1) folders are supported; subfolders cannot be used for filtering.
• Add robust image metadata for better search: Apply descriptive tags and metadata to each image. For guidance, refer to: 
  • Find and manage images using enhanced image tagging | Microsoft 365 | Microsoft Learn
  • Overview of image tagging | Microsoft 365 | Microsoft Learn

[Compliance considerations:]

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

Updated November 11, 2025: We have updated the content and the images below. Thank you for your patience.

[Introduction]

Starting February 2026, we will introduce jailbreak and root detection for Entra credentials in the Microsoft Authenticator app on both iOS and Android platforms. This change enhances security by preventing Entra credentials from functioning on jailbroken/rooted devices. All existing Entra credentials on jailbroken or rooted devices will be wiped to protect your organization. This capability is secure by default and does not require any admin configuration or control.

[When this will happen] 

General Availability (Worldwide) rollout begins in February 2026 and is expected to complete in April 2026.

[How this affects your organization]

Who is affected: All users of Microsoft Authenticator on iOS and Android whose Entra credentials are registered on jailbroken or rooted device. This is going to be a continuous check.

What will happen:

• The feature is secure by default and enabled to all customers. There is no opt-out capability..
• Users on jailbroken or rooted devices will experience the following phased rollout. An estimated gap between 3 phases is ~ 1 month.
  • Phase 1 – Warning Mode: Users receive a warning that their device is jailbroken or rooted and will be blocked in the future (screenshots 1-4): 

  

  

  

  

  • Phase 2 – Blocking Mode: Users are blocked from registering Entra credentials or signing in via Authenticator (screenshots 5-8):

  

  

  

  

  • Phase 3 – Wipe Mode: Existing Entra credentials are wiped from jailbroken or rooted devices (screenshots 9-11):

  

  

  

• Users on non-Jailbroken or non-rooted devices will not be affected.

[What you can do to prepare]

• Notify users about this upcoming change. Users will see error messages or banners in the Authenticator app during warning or blocking phases. These screens are dismissible but indicate the device status.
• Communicate to helpdesk staff that Authenticator will become unusable for Entra accounts on jailbroken or rooted devices.
• Update internal documentation if you reference Authenticator usage.
• No admin action is required to enable or configure this feature.

Learn more: About Microsoft Authenticator | Microsoft Support

[Compliance considerations]

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

[Introduction]

The Loop app grace period is ending. This grace period was granted to organizations that participated in the Loop app Public Preview between March and November 2023, allowing all users—regardless of license—to create and manage Loop workspaces. To align with Microsoft 365 licensing requirements, this grace period will end in December 2025. After this change, only users with a qualifying Microsoft 365 plan will retain full workspace capabilities in the Loop app.

[When this will happen:]

This change will take effect in mid-December 2025.

[How this affects your organization:]

• Who is affected:
  • Organizations that participated in the Loop app Public Preview between March and November 2023.
  • Within those organizations, only users without a qualifying Microsoft 365 plan are affected by this change.
• What will happen:
  • Starting in mid-December 2025:
  • Users with a qualifying Microsoft 365 plan will continue to:
    • Create new Loop workspaces.
    • Add or remove members from Loop workspaces.
  • Users without a qualifying Microsoft 365 plan will:
    • No longer be able to create new Loop workspaces.
    • No longer be able to add or remove members from existing workspaces.
    • Continue to access and use previously created Loop components, pages, and workspaces.

[What you can do to prepare:]

• No action is required at this time. However, you may wish to:
• Review your organization’s Microsoft 365 licensing to ensure users who need to create or manage Loop workspaces have the appropriate plan.
• Communicate this change to your helpdesk or support staff.
• Update internal documentation if you provide guidance on Loop app usage.

Learn more: Loop access via Microsoft 365 subscriptions

[Compliance considerations:]

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

[Introduction]

As part of our ongoing efforts to simplify and modernize the Viva Connections experience, we will retire the Assignments and Courses adaptive card extensions (ACEs) for Education customers. ACEs are modular components built using the SharePoint Framework (SPFx) that allow developers to create rich, interactive dashboard cards in Viva Connections. These cards surface data and actions from Microsoft 365 services or custom sources, helping users engage with content directly from their dashboard. The equivalent SharePoint dashboard webparts will also be retired. This change is intended to streamline the experience and reduce redundancy across platforms.

[When this will happen:]

• New installations will be disabled on December 31, 2025.
• Existing components will reach end of support on June 30, 2026.

• Who is affected: Education tenants using Viva Connections and SharePoint dashboard webparts for Assignments and Courses.
• What will happen:
  • Users and admins will no longer be able to access Assignments and Courses ACE cards in Viva Connections.
  • Equivalent SharePoint dashboard webparts will also be inaccessible.
  • No reporting is available to identify which users are currently using these components.

• No admin action is required.
• Please notify your users about this change.
• Update any internal documentation that references these components.
• Share alternate capabilities with your users, if applicable.

Compliance considerations:

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

Viva Engage: Update storyline cover photos in Teams for iOS

We’re adding more customization to your Viva Engage storyline in Microsoft Teams. Soon, you’ll be able to update your storyline cover photo directly from the Teams iOS app. Storyline is a personal feed where users can share updates, insights, and experiences across their organization. This feature is already available on Teams for Android, Windows, Mac, and the web, and supports a consistent and personalized experience across platforms.

Screenshot 1: A user’s cover photo, with options to Take a photo or Upload a picture.

This message is associated with Roadmap ID 526783.

When this will happen:

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

How this affects your organization:

• Who is affected: All users of storyline from Viva Engage in Microsoft Teams.
• What will happen:
  • Users will be able to update their storyline cover photo directly from the Teams iOS app.
  • This feature is enabled by default and does not require admin configuration.
  • There is no change to existing admin policies or controls.

What you can do to prepare:

• Update any internal documentation that references storyline customization.
• No admin action is required to enable this feature.

Compliance considerations:

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

[Introduction:]

As part of the Microsoft Secure Future Initiative (SFI) and in alignment with the “Secure by Default” principle, we’re retiring the legacy IDCRL (Identity Client Run Time Library) authentication protocol in SharePoint Online and OneDrive for Business. This change helps strengthen your organization’s security posture by enforcing modern authentication standards—OpenID Connect and OAuth—which reduce exposure to outdated and vulnerable authentication methods.

[When this will happen:]

• Starting January 31, 2026: Legacy client authentication will be blocked by default. Organizations may temporarily re-enable it using PowerShell until April 30, 2026.
• Starting May 1, 2026: Legacy client authentication will be permanently blocked and cannot be re-enabled.

[How this affects your organization:]

Who is affected:

• Organizations using clients, scripts, or applications that rely on the legacy IDCRL authentication protocol to access SharePoint Online or OneDrive for Business.

• Legacy authentication calls using IDCRL will be blocked by default starting January 31, 2026.
• Temporary re-enablement is possible via PowerShell until April 30, 2026.
• After May 1, 2026, IDCRL authentication will be permanently retired and cannot be re-enabled.
• Applications using IDCRL will fail to authenticate unless updated to use modern protocols.

[What you can do to prepare:]

We recommend migrating from legacy authentication protocols to modern authentication as soon as possible. 

To prepare for this retirement:

• Migrate all clients, scripts, and applications to use OpenID Connect or OAuth protocols. 
• Review current configurations for IDCRL authentication.
• Notify IT admins, app owners, and security teams about the upcoming retirement.
• Update internal documentation to reflect the new authentication defaults.
• Use telemetry to identify usage of legacy authentication protocols and monitor migration progress.
• Use PowerShell to manage legacy authentication settings if needed:
  • Set AllowLegacyAuthProtocolsEnabledSetting and LegacyAuthProtocolsEnabled to TRUE to temporarily allow legacy authentication until April 30, 2026.
• Learn more:
  • Migrating from IDCRL authentication to modern authentication in SharePoint | Microsoft 365 Developer Blog | Microsoft Dev Blogs
  • Set-SPOTenant (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We’re updating how feedback policies are managed for in-app surveys in Microsoft Teams. Teams for Android and iOS will stop using Teams-specific feedback policies and instead adopt the Microsoft 365 Cloud Policy service. This change aligns survey feedback with other in-app feedback experiences, simplifying policy management across your organization.

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

Who is affected:

• All organizations using Microsoft Teams for Android and iOS.

What will happen:

• Teams-specific feedback policies will be retired for surveys.
• Surveys will now use the same Microsoft 365 Cloud Policy that governs other in-app feedback experiences (such as Give a compliment or Report a problem).
• The feature will be ON by default.
• There is no change to how users submit feedback; only policy management is unified.
• Existing Teams feedback policies will no longer apply after rollout.

• No admin action is required before rollout.
• Review your current Teams feedback policies.
• Update Microsoft 365 Cloud feedback policies to reflect your organization’s needs.
• Notify admins and helpdesk staff about this change.
• Update internal documentation if you reference Teams feedback policies.

Helpful resources:

• Manage feedback policies in Microsoft Teams
• Learn about Microsoft feedback for your organization
• Cloud Feedback Policy Service
• Overview of Cloud Policy service for Microsoft 365

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

[Introduction:]

We’re updating the Microsoft Teams jump list experience on Windows to streamline access to key actions directly from the desktop. These enhancements are designed to reduce clicks and improve user efficiency, based on feedback and alignment with other Microsoft 365 applications.

[When this will happen:]

General Availability:

• Worldwide: We will begin rolling out in mid-November 2025 and expect to complete by late November 2025.
• GCC, GCCH, and DoD: We will begin rolling out in late November 2025 and expect to complete in late November 2025.

[How this affects your organization:]

Who is affected: All users of the Microsoft Teams desktop app on Windows.

What will happen:

• Users will see upcoming and ongoing meetings directly in the Windows jump list.
• Users can join meetings without opening the full Teams app.
• New quick actions will be added to the jump list:
  • Schedule a meeting
  • Start a new chat
• The “Quit” option will be removed from the jump list and will only be accessible via the Teams system tray icon to prevent accidental exits.

Screenshot – New taskbar jump list view:

[What you can do to prepare:]

No action is required. These updates will be delivered automatically as part of the Teams desktop app release. You may wish to:

• Inform helpdesk staff of the updated jump list behavior.
• Update internal documentation if it references the “Quit” option in the jump list.

[Compliance considerations:]

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

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

Microsoft 365 Copilot is introducing support for connected agents, allowing one agent to query another for additional context or data. For example, the Researcher agent may request sales or inventory data from other enterprise software agents. This enhancement helps agents deliver more comprehensive and informed responses.

• Public Preview: We will begin rolling out in mid-November 2025 and expect to complete by late February 2026.

• Who is affected: Admins managing Microsoft 365 Copilot agents in the Microsoft 365 admin center. This applies to all licenses that include Microsoft 365 Copilot Chat, including both the free and paid versions.
• What will happen:
  • Agents will be able to query other agents for additional information
  • The Agents page in the Copilot hub will show which connected agents are configured
  • Admins can modify connected agents if allowed by the developer
  • Users must acquire both the primary and connected agents to use this functionality
  • Users will be able to enable or disable acquired agents per conversation
  • The first agent to support this feature is Researcher, starting Q4 2025
  • Up to 10 connected agents can be configured per agent:

Screenshot 1 – Early draft UI (experience subject to change closer to rollout): 

Screenshot 2 – A second view of early draft UI (experience subject to change closer to rollout): 

[What you can do to prepare:]

• Review the Agent inventory in the Copilot hub to view and manage connected agents
• Ensure users are allowed to acquire agents if you want them to use connected functionality
• Communicate this change to helpdesk staff
• Update internal documentation if you detail agent capabilities
• No changes to existing admin controls are required

Learn more: Manage Microsoft 365 Copilot Agents – Microsoft 365 admin | Microsoft Learn

• This security update includes improvements that were a part of update KB5067036 (released October 28, 2025).
• This update addresses security issues for your Windows operating system.
• This update addresses an issue that affects gaming handheld devices. These devices were unable to stay in low-power states, which caused faster battery drain.​​​​​​​
• This update addresses an issue on some handheld gaming devices where after signing in using the built-in Gamepad, the controller might not respond in apps for about five seconds.
• This update addresses an issue with enabling Storage Spaces Direct. It fails when creating a storage cluster.

• Windows 11, versions 25H2 and 24H2: KB5068861
• Windows 11, version 23H2: KB5068865
• Windows 11 Enterprise LTSC 2024: Hotpatch KB5068966
• Windows 10, versions 22H2 and 21H2: KB5068781
• Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5068791
• Windows 10 LTSB 2016 and Windows Server 2016: KB5068864
• Windows Server 2025: KB5068861
• Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5068966
• Windows Server 2022: KB5068787
• Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5068840
• Windows Server 2012 R2: Monthly Rollup: KB5068905
• Windows Server 2012: Monthly Rollup: KB5068907
• Windows Server 2008 R2 Service Pack 1: Monthly Rollup: KB5068904 / Security Only: KB5068908
• Windows Server 2008 SP2: Monthly Rollup: KB5068906 / Security Only: KB5068909

1. Navigate to the Windows Update settings page and select “Check for updates.”
2. Install the out-of-band (OOB) update (KB5071959) and reboot your device to complete installation.
3. Run the Windows 10 Consumer ESU enrollment wizard to enroll your device in the ESU program.
4. After you have successfully enrolled your device, navigate once more to the Windows Update settings page and select “Check for updates.”
5. Your device will now be offered the latest monthly security update. Install the update and reboot your device to complete installation.

Updated November 11, 2025: We are updating this post to serve as a reminder of this change. 

We are dedicated to providing our customers with the tools they need to achieve what matters, in their work and life. In order to focus on new benefits, we occasionally remove features and products.

In October 2026, Microsoft Publisher will reach its end of life. After that time, it will no longer be included in Microsoft 365 and existing on-premises suites will no longer be supported. Until then, support for Publisher will continue and users can expect the same experience as today.

As we look ahead to the retirement of Microsoft Publisher, we are exploring modern ways to achieve other common Publisher scenarios across applications like Microsoft Word, PowerPoint, and Designer. We will update as we have more to share.  

[When this will happen:]

October 13, 2026

[How this will affect your organization:]

You can continue to use Publisher with its current functionality until October 2026.

Support for the perpetual version of Publisher will end in October 2026, when Office LTSC 2021 reaches end of support. Microsoft 365 customers will not be able to access Publisher from that date forward.

[What you need to do to prepare:]

No action is required at this time. This notice is to allow you sufficient time to plan. We will share additional updates as the date approaches.