Microsoft Roadmap, messagecenter and blogs updates from 08-05-2026

Updated May 7, 2026: We have updated the timeline. Thank you for your patience. 

We’re introducing a new Account Manager experience in Outlook for Windows. This feature helps users better manage their Microsoft accounts by providing quick access to account details, displaying their profile picture, and enabling account switching (if permitted by your organization). This update aligns the experience with classic Outlook and enhances user productivity.

This message is associated with Microsoft 365 Roadmap ID 497546

When this will happen:

General Availability (Worldwide): Rollout will begin in mid-March 2026 (previously early March) and is expected to complete by mid-May 2026 (previously late March).
Targeted Release: Rollout will begin in early February 2026 (previously early December 2025) and is expected to complete by late February 2026 (previously late December 2025).

How this affects your organization:

Once the rollout is complete, users will see the new Account Manager in the title bar of Outlook for Windows. Key capabilities include:

• Displaying the user’s profile picture, automatically synced from their Microsoft account.
• Providing access to the Microsoft account page, consistent with the experience in classic Outlook.
• Allowing users to add and manage accounts, if permitted by your organization’s policies.

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

What you can do to prepare:

No admin action is required. You may wish to inform your helpdesk and users about the new experience to reduce potential confusion.

Compliance considerations:

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

Updated May 7, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

General Availability (Worldwide): We will begin rolling out in mid-July 2026 (previously late April) and expect to complete by end of July 2026 (previously mid-May).

[What’s changing?]

Who is affected:

• Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
• Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.

What will happen:

• The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
• Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
• Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
• Conversation history will persist during meetings for Copilot without transcription.
• Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.

If adopting the new defaults:

• Review TeamsMeetingPolicy for transcription dependencies.
• Update internal documentation and training.
• Communicate to users how to enable transcription when needed.

Optional admin steps to retain current behavior:

• Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell.
• TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated.
• PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies:

  get-csteamsmeetingpolicy | ? {
    $_.Identity -ne "Tag:AllOn" -and
    $_.Identity -ne "Tag:AllOff" -and
    $_.Identity -ne "Tag:Default" -and
    $_.Identity -ne "Tag:Kiosk" -and
    $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and
    $_.Identity -ne "Tag:RestrictedAnonymousNoRecording"
  } | % {
    $_.Identity;
    set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript
  }
      

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

Updated May 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To help organizations streamline approval workflows and improve governance, users who request a Microsoft 365 Copilot license will be able to submit a business justification with their request. Admins will see this justification during review, enabling faster and more informed decisions while reducing manual follow-ups.

This message is associated with Microsoft 365 Roadmap ID 547731.

[When this will happen]

General Availability (Worldwide): Rollout will begin end of May 2026 (previously late April) and is expected to complete by end of May 2026 (previously late April).

[How this affects your organization]

Who is affected:

• Users who request Microsoft 365 Copilot licenses
• Admins who review, approve, or manage Copilot license requests

What will happen:

• Users requesting a Copilot license will see a new field to provide a business justification.
• Admins will see the justification as part of the review experience.
• The feature will be on by default with no tenant configuration required.
• Existing license request workflows will continue to function as they do today.
• There will be no impact to the user experience unless they request a Copilot license.
• No changes to admin policies, settings, or reporting.

Screenshot 1 – A license request will be created when the user clicks Request License:

Screenshot 2 – On the next screen, there is an option to provide a business justification for the request; this step is optional:

Screenshot 3 – View of the dropdown menu with business justification options:

[What you can do to prepare]

No action is required.

Optional steps:

• Notify helpdesk or approvers about the new justification field.
• Review or update internal documentation as needed.
• If you track license request metadata, ensure your internal workflows and tools account for the justification field.

[Compliance considerations]

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

Updated May 7, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We are retiring SharePoint One‑Time Passcode (SPO OTP) authentication in OneDrive and SharePoint starting July 2026. Beginning in May 2026, new external sharing invitations and authentication will start using Microsoft Entra B2B instead of SPO OTP. This transition simplifies external collaboration, aligns authentication with Microsoft identity standards, and enables consistent guest lifecycle management, governance, and Conditional Access coverage across Microsoft 365.

[When this will happen]

• May & June 2026: Invitation and authentication for new external sharing transitions to Microsoft Entra B2B. Users who previously authenticated via SPO OTP will continue to have access to specific people links even without a B2B guest account yet.
• July 2026: Retirement of SPO OTP authentication begins. External users without a guest account get access denied on previously shared specific people links. To restore access, a guest account must be created in Entra B2B, or an allowed user must share/re-share at least one file/folder/site.
• Retirement is expected to complete by August 31, 2026.

[How this affects your organization]

Who is affected

• All Microsoft 365 tenants (commercial, government, sovereign).
• All external users who access OneDrive or SharePoint files, folders, or sites.

What will happen

• The EnableAzureADB2BIntegration setting will no longer control external sharing behavior beginning May 2026.
• SPO OTP authentication will retire beginning July 2026.
• The option to disable Entra B2B integration will be removed.

Impact on external users

• External users who already have an Entra B2B guest account in your directory:
  • No change in behavior.
• External users without a B2B guest account:
  • Specific people links shared after changes rolled out to your tenant:
    • A guest account will be automatically created via the Entra B2B Invitation Manager.
    • Authentication will use Entra B2B (email OTP available if enabled).
  • Specific people links shared before changes rolled out to your tenant:
    • SPO OTP authentication continues until July 2026.
    • After July 2026, these users will receive access denied until a matching B2B guest account exists.

Restoring access after retirement

• Admins can manually create a guest account for the external user at any time.
• Alternatively, an internal user with permissions needs to share or re-share at least one file, folder, or site, which will automatically create the guest account and restore access to all previously shared content.

[What you need to do to prepare]

No admin action is required. However, to ensure a smooth transition:

• Inform users that some external collaborators may see access denied beginning July 2026 for older links authenticated via SPO OTP.
• If your organization relies on email OTP authentication via Entra, ensure it is not disabled in Entra External ID settings. See Email OTP for B2B guests.
• Review external sharing policies and conditional access settings for guests in SharePoint and Entra admin centers.
• Optionally, identify external collaborators without guest accounts via external sharing reports. Proactively create guest accounts to retain access.
• Update internal documentation.

Learn more:

• Add and manage B2B collaboration users in the Microsoft Entra admin center | External ID | Microsoft Entra | Microsoft Learn
• Email one-time passcode authentication for B2B guest users | External ID | Microsoft Entra | Microsoft Learn
• Frequently Asked Questions: Improvements to external sharing in OneDrive & SharePoint | SharePoint in Microsoft 365 | Microsoft Learn
• Overview: B2B collaboration with external guests for your workforce | External ID | Microsoft Entra | Microsoft Learn
• Quickstart: Add a guest user and send an invitation | External ID | Microsoft Entra | Microsoft Learn
• SharePoint and OneDrive integration with Microsoft Entra B2B | SharePoint in Microsoft 365 | Microsoft Learn

[Compliance considerations]

Updated May 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing Catch up in Microsoft Teams mobile. This new, consolidated view helps users triage conversations that need their attention across chats, meeting chats, and followed channels or threads. The experience uses a mobile-optimized card layout with swipe actions to help users stay organized and act quickly on important messages.

This message is associated with Microsoft 365 Roadmap ID 558108.

[When this will happen]

• Targeted Release: Rolling out in early April 2026; expected completion in early April 2026.
• General Availability (Worldwide): Rolling out in early May 2026; expected completion in late June 2026 (previously early May).

[How this affects your organization]

Who is affected

• All users accessing Microsoft Teams on mobile clients.

What will happen

• Users will see a new Catch up experience summarizing:
  • @mentions
  • Replies in followed channels/threads
  • Chats and meeting chats where actions may be required
• A new card‑based view will appear in Teams mobile: 

  

• Users can swipe cards to take quick actions and triage messages:

   

• No admin configuration changes are required.
• The feature is enabled by default for all tenants.

[What you can do to prepare]

No admin action is required at this time.

If your organization provides guidance or training for Teams usage, you may want to:

• Inform users about the new Catch up mobile view and how it supports triage.
• Update internal helpdesk or user‑support documentation if it references existing Teams mobile views.

[Compliance considerations]

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

Updated May 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing a refreshed chat‑first design in the Microsoft 365 Copilot mobile app. This update modernizes the interface and streamlines navigation to make it faster and easier for users to start, continue, and manage chats. The improved experience is based on customer feedback and aligns the mobile app more closely with the broader Copilot visual design. The updated design will release first on iOS, followed shortly by Android.

[When this will happen]

• Public Preview: Rolling out in mid-May 2026 (previously late April) and expected to complete in late June 2026.
• General Availability (Worldwide, GCC, GCCH, and DoD): Rolling out in mid-May 2026 (previously late April) and expected to complete in late August 2026.

[How this affects your organization]

Who is affected

• All users of the Microsoft 365 Copilot mobile app on iOS and Android across Worldwide, GCC, GCC High, and DoD clouds
• This feature is available to both users with a Microsoft 365 Copilot license (Microsoft 365 Copilot users) and users without a Microsoft 365 Copilot license (Copilot Chat users), but the experience varies.

What will happen

The Microsoft 365 Copilot mobile app will update automatically with a new chat‑first design. Key changes include:

• Updated, modern visual design language
• Simplified chat input that supports text formatting
• Updated chat response layout for easier viewing, copying, reopening, and accessing citations
• Refreshed visual experience for voice interactions
• Streamlined navigation, including:
  • Unified profile and settings entry point
  • Chat search moved into the navigation menu
  • Create and Notebooks relocated to the overflow menu
  • Chat settings consolidated into app settings
• The new UI will be on by default for all users.
• No existing workflows are removed or altered.
• No admin configuration changes or policy updates are required.

Screenshot 1 – Redesigned navigation bar:

Screenshot 2 – Redesigned chat input:

[What you can do to prepare]

No admin action is required.

You may choose to:

• Inform helpdesk or support teams of the updated interface.
• Share internal readiness materials to help users understand the new layout.
• Review new Microsoft Learn documentation once published after rollout.

[Compliance considerations]

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

[Introduction]

We are improving how users discover Microsoft 365 Copilot capabilities in the file previewer of OneDrive and SharePoint. Ready to use Copilot actions will appear directly in the file preview experience, alongside the Copilot button. When users preview supported files, suggested prompts will help them complete common tasks such as summarizing documents, generating FAQ, and extracting key information without writing their own prompts.

[When this will happen]

General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete the rollout by early May 2026.

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using OneDrive for Business
• Users who have access to Microsoft 365 Copilot
• Administrators managing OneDrive and Copilot experiences

What will happen

• Users will see suggested Copilot actions when previewing supported files in OneDrive:

   

• Suggested actions may include summarizing content, generating FAQ, and identifying key points.
• The feature will be enabled by default for eligible users. Suggestions will disappear after a timeout or after a user interacts with a file.
• Existing Copilot, OneDrive, SharePoint, and Microsoft Purview policies will continue to apply.
• There will be no change to file permissions, sharing behavior, or data residency. Copilot will continue to respect existing access controls and Microsoft Purview policies.

[What you can do to prepare]

• No admin action is required.
• Consider notifying users that Copilot suggestions will appear in OneDrive file previews to support awareness and adoption.
• If Copilot is disabled or restricted in your tenant, those settings continue to apply.

[Compliance considerations]

• Translating user intent into structured workflow logic
• Automatically configuring actions, triggers, and other components
• Reducing the need for manual setup and technical configuration
• Accelerating time from concept to implementation

• Enable manual recording for non-voice engagements through settings.
• Specify which roles can start, stop, review, or download recordings using existing security roles.
• Disable individual capabilities at any time by turning off the relevant settings or removing role permissions.
• Manually link recordings to cases or conversations when sessions don’t originate from voice calls, ensuring recordings are attached to the correct entity.

Updated May 7, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re introducing support for Black Forest Labs Flux.2 Flex image generation model in PowerPoint with Microsoft 365 Copilot. This model is optimized for high‑quality visual output with improved text and layout rendering, helping users generate more polished and presentation-ready images. This update expands flexibility by allowing users to select their preferred image generation model based on their needs.

[When this will happen:]

• General Availability (Worldwide): Rollout began late April 2026 and is expected to complete by early May 2026.

[How this affects your organization:]

Who is affected:

• Users with access to Microsoft 365 Copilot in PowerPoint
• Organizations with image generation enabled in PowerPoint
• A Microsoft 365 Copilot (Premium) license is required to use this feature.

What will happen:

• Users will find Flux.2 Flex as an additional option in the image model picker in PowerPoint.

Screenshot 1: Open the Copilot pane in PowerPoint. The model picker appears at the top with Auto selected by default. Select it to view available models:

 

Screenshot 2:  Reasoning models appear first. Scroll to the Image models section and expand it to view options: 



• The model is not enabled by default and must be explicitly selected by users.
• Existing image generation settings and admin configurations are respected.
• Users must have a valid Microsoft 365 Copilot subscription.
• There are no changes to existing workflows unless users choose the new model.

[What you can do to prepare:]

No action is required if image generation is already enabled in your organization.

• Review your current image generation settings in Microsoft 365 if you want to control access.
• Inform your helpdesk and support teams that a new model option will appear in PowerPoint.
• Update internal documentation or training materials if you reference image generation features.

[Compliance considerations:]

• Flux.2 Flex is a third‑party model hosted within Microsoft‑controlled Azure infrastructure.
• User prompts are processed only when the model is explicitly selected.
• Customer data is processed in accordance with Microsoft’s existing enterprise data protection commitments.
• Customer data is not shared with or processed outside of Microsoft’s controlled environment.
• There is no change to existing compliance, security, or data governance controls.

[Introduction]

We are enhancing Power BI reporting capabilities in Viva Insights by allowing administrators to enable additional attributes—including reserved attributes and organization-specific custom attributes—as report filters. This update enables organizations to derive deeper insights aligned to their business structure and needs.

This message is associated with Microsoft 365 Roadmap ID 559995.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late May 2026 and is expected to complete by early June 2026.

[How this affects your organization:]

Who is affected:

• Viva Insights Global administrators and Insights administrators
• Users with access to Viva Insights Power BI reports
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• The configuration experience is available to admins by default in the Viva Insights web app.
• Admins can enable additional attributes as filters in Power BI reports via the Viva Insights web app.

Screenshot 1: Example of the Attribute filter settings page in Viva Insights where admins can enable filters for Power BI reports:

• Supported filters include reserved attributes (provided by Microsoft) and custom attributes configured by your organization.

Screenshot 2: Example of Viva Insights reports displaying newly enabled filters available to users after admin configuration:



• Once enabled:
  • These filters become available to report viewers in Power BI
  • Users can personalize reports based on business-specific dimensions

[What you can do to prepare:]

• No immediate action is required.
• Review your current Viva Insights attribute configuration.
• Identify which custom or reserved attributes would add value as report filters.
• Plan internal governance for filter usage.
• Communicate this capability to report users once enabled.
• Update internal documentation or reporting guidance.

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

[Compliance considerations:]

[Introduction]

Microsoft is upgrading the backend service that powers Teams meeting templates to improve security and reliability. As part of this change, meeting templates will require supported versions of Microsoft Teams and Outlook clients. Meeting templates functionality and user experience remain unchanged.

Meeting templates is a Teams Premium feature and requires the appropriate license to be enabled for users.

[When this will happen:]

• Worldwide, GCC, GCCH and DoD: Support for meeting templates feature in older versions will stop by June 30, 2026. 

[How this affects your organization:]

Who is affected:

• Meeting organizers who create Teams meetings using meeting templates
• This includes webinars and town halls that rely on meeting templates

What will happen:

• Users on unsupported versions of Microsoft Teams or new Outlook for Windows may experience issues when accessing or applying meeting templates
• Meeting templates functionality remains unchanged for supported clients
• This change is enforced automatically; no admin configuration is required

[What you can do to prepare:]

To ensure a smooth transition, please confirm users are on the minimum supported versions listed below:

• Microsoft Teams (Windows): 26015.1706.4351.4392 or later
• Microsoft Teams (Mac): 26015.1706.4351.4392 or later
• Outlook (classic) with Teams add-in: Teams version 26015.1706.4351.4392 or later (no separate Outlook update required)
• New Outlook for Windows: 20260320002.20 or later

Recommended actions:

• Verify users are running supported versions before the applicable deadline.
• Communicate this change to helpdesk and support teams.
• Encourage users to restart Teams and Outlook applications to ensure updates are applied.

Update guidance:

• Review how Teams updates automatically and how to manually check for updates: Update Microsoft Teams | Microsoft Support
• Learn how updates are managed in the new Outlook for Windows: Manage updates in new Outlook for Windows | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We are introducing separate admin controls for Viva Engage Communities and Storylines in Microsoft Teams. These controls provide more granular management by allowing administrators to independently enable or disable each experience within Teams, while existing controls in the Viva Engage admin center remain unchanged. By default, both Communities and Storylines will be enabled in Teams unless configured otherwise.

[When this will happen:]

• General Availability (Worldwide): Individual controls will be available by May 18, 2026

[How this affects your organization:]

Who is affected:

• All users licensed for Microsoft Teams and Viva Engage
• Administrators managing Teams messaging policies

What will happen:

• Two new independent controls will be available in the Teams admin center:
  • Communities
  • Storylines

Screenshot: Viva Engage Controls in Teams Admin Center:



• Admins can configure these controls through Teams messaging policies.
• Default state:
  • Communities in Teams: On
  • Storylines in Teams: On
• If Communities is turned off in Teams, it is hidden in Teams but remains available in Viva Engage.
• If Storylines is turned off in Teams, it is hidden in Teams but remains available in Viva Engage.
• If Storylines is disabled in Viva Engage, it is disabled in both Viva Engage and Teams.
• If Viva Engage experiences in Teams was previously turned off, Storylines will remain off and Communities will be enabled by default after this update.
• Changes may take up to 24 hours to propagate.

[What you can do to prepare:]

Action required:

• Review and configure your preferred settings before Communities reach General Availability in June. If no action is taken, Communities and Storylines will remain enabled by default in Teams.

Recommended steps:

• Review current Teams messaging policies
• Decide whether Communities and Storylines should be enabled or disabled
• Update settings as needed

To disable Communities in Teams:

1. Go to Teams admin center
2. Select Settings & policies
3. Choose Global (Org-wide default) or custom policy
4. Open Messaging settings
5. Set Communities to Off
6. Save changes

To disable Storylines in Teams:

1. Go to Teams admin center
2. Select Settings & policies
3. Choose Global (Org-wide default) or custom policy
4. Open Messaging settings
5. Set Storylines to Off
6. Save changes

Learn more: Manage Viva Engage experiences in Microsoft Teams – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

[Introduction]

We’re introducing integration of the Microsoft Purview SDK into the Microsoft Agent Framework SDK to help organizations build secure, enterprise-ready AI agents. This integration enables developers to apply Microsoft Purview compliance and data protection capabilities directly within agent runtimes. It extends existing security and governance controls to custom-built AI agents across Microsoft 365 workloads.

This message is associated with Microsoft 365 Roadmap ID 534609.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations building or planning to build AI agents using the Microsoft Agent Framework SDK
• Admins and developers responsible for security, compliance, and governance of custom AI agents
• Tenants with Microsoft Purview licenses that enable SDK usage

What will happen

• Developers can embed Microsoft Purview SDK controls directly into AI agent runtimes built with the Agent Framework SDK.
• AI agents can respect existing Microsoft Purview compliance configurations, such as data protection and policy enforcement, when accessing organizational data.
• There is no change to user experiences in Microsoft 365 services.
• The integration is not enabled automatically; it requires developer implementation within custom agents.
• Existing Microsoft Purview policies and configurations remain unchanged unless explicitly used by the agent.

[What you can do to prepare]

No immediate admin action is required if your organization is not developing AI agents.

If your organization builds AI agents:

• Share this update with your development and security teams.
• Review Microsoft Purview SDK documentation to understand supported compliance capabilities.
• Validate how existing Purview policies should be applied within agent workflows.

Learn more: Building Secure, Enterprise-Ready AI Agents with Purview SDK and Agent Framework | Microsoft Security Community Blog

[Compliance considerations]

[Introduction]

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

[When this will happen]

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

[How this affects your organization]

Who is affected

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

What will happen

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

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

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

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

[What you can do to prepare]

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

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

[Compliance considerations]

[Introduction]

The new Outlook for Windows now allows users to store S/MIME encryption certificates directly within Contacts. This capability enables users to save recipients’ public certificates and use them to send S/MIME encrypted emails, improving secure communication and continuity when transitioning from classic Outlook for Windows (Win32). Certificates previously stored in Contacts in classic Outlook will automatically be available in new Outlook.

This message is associated with Microsoft 365 Roadmap ID 518288.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users of new Outlook for Windows
• Organizations that use S/MIME encryption

What will happen:

• Users can store recipients’ S/MIME public certificates directly in Contacts.

Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:



• Stored certificates can be used to encrypt outgoing email to those recipients.
• Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.
• Feature is available by default; no admin configuration required.
• No impact to users who are not using new Outlook for Windows.

[What you can do to prepare:]

• No admin action is required to enable this feature.
• If your organization uses S/MIME:
  • Instruct users to add or import S/MIME public certificates into Contacts.
  • Communicate how to select S/MIME encryption when composing emails. Learn more: Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support.
• Update internal documentation for users transitioning from classic Outlook.
• Inform helpdesk teams of this improved certificate handling experience.

[Compliance considerations:]

Updated May 7, 2026: We have updated the timeline. Thank you for your patience.

Coming soon: Users will be able to automatically see their automapped calendars when toggling from classic Microsoft Outlook to new Outlook for Windows. This message applies to classic Outlook for Windows desktop and new Outlook for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 415168.

[When this will happen:]

General Availability: We will begin rolling out end of May 2026 (previously May) and expect to complete by end of June 2026 (previously end of May).  

[How this will affect your organization:]

Before this rollout, users were not able to see their automapped calendars when toggling from classic Outlook to new Outlook.

To access an automapped calendars, users can go to Microsoft Outlook > Calendar icon on left of screen > My Calendars > Automapped calendar.

This feature is on by default.

[What you need to do to prepare:]

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

Learn more

• The section called Use the shared calendar from the shared mailbox in Open and use a shared mailbox in Outlook – Microsoft Support
• Definition of automapping: Remove automapping for a shared mailbox – Outlook | Microsoft Learn

#newoutlookforwindows