Microsoft Roadmap, messagecenter and blogs updates from 21-04-2026

Updated April 20, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

Connectivity changes between cmdlets and Microsoft 365 services like SharePoint and Exchange now require a new parameter for improved security and modern authentication. Starting April 30, 2026, Admins must use Exchange Online PowerShell v3.9.0 or later and include the -EnableSearchOnlySession parameter when running Connect-IPPSession to execute Data Lifecycle Management cmdlets.

When this will happen:

Enforcement begins April 30, 2026.

How this affects your organization:

• Who is affected: Admins using Data Lifecycle Management cmdlets in Security & Compliance PowerShell.
• What will happen:
  • You must use Exchange Online PowerShell v3.9.0 or later.
  • You must include the -EnableSearchOnlySession parameter when running Connect-IPPSession.
  • This applies to the following cmdlets:
    • New-RetentionCompliancePolicy
    • Set-RetentionCompliancePolicy
    • New-RetentionComplianceRule
    • Set-RetentionComplianceRule
    • New-ComplianceTag
    • Set-ComplianceTag
    • Remove-ComplianceTag
    • New-ComplianceRetentionEvent
    • Set- ComplianceRetentionEvent
    • Remove- ComplianceRetentionEvent
    • New-ComplianceRetentionEventType
    • Set-ComplianceRetentionEventType
    • Remove- ComplianceRetentionEventType
  • No impact for users accessing Data Lifecycle Management through the Purview portal.
  • Cmdlets remain incompatible with Certificate-Based Authentication (CBA).

What you can do to prepare:

• Update scripts and workflows to include the -EnableSearchOnlySession parameter.
• Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later.
• For more information, visit: Learn about Data Lifecycle Management solutions in Microsoft Purview.

Compliance considerations:

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

Updated April 20, 2026: We are updating this post as a reminder. Thank you for your patience. 

[Introduction]

Microsoft is retiring SharePoint Designer 2013, which follows the Microsoft Fixed Lifecycle Policy and will reach end of support on July 14, 2026. This retirement aligns with our commitment to modernize workflow automation and customization experiences using supported tools such as Power Automate.

[When this will happen]

End of support begins in mid-July 2026, with retirement enforcement occurring between mid-July and late July 2026 across all Microsoft 365 environments (Worldwide, GCC, GCC High, and DoD).

[How this affects your organization]

Who is affected: Organizations that use SharePoint Designer 2013 for SharePoint workflows or site customizations.

What will happen:

• Microsoft will no longer provide support, security updates, or fixes for SharePoint Designer 2013.
• No extensions or exceptions will be offered beyond the retirement date.
• Workflows built with SharePoint Designer 2013 will require migration to supported alternatives such as Power Automate.
• The SharePoint Migration Tool (SPMT) can migrate supported workflow actions to Power Automate.

[What you can do to prepare]

We recommend the following actions before July 14, 2026:

• Review existing SharePoint Designer 2013 workflows and customizations.
• Plan and complete migration to supported technologies.
• Update internal documentation, helpdesk knowledge bases, and user communications.
• Use the SharePoint Migration Tool (SPMT) 4.1 to assess and migrate supported workflow actions to Power Automate.
• Note: The SharePoint Migration Tool lets you migrate SharePoint Designer 2013 workflows to Power Automate.
• Review SharePoint Designer 2013 lifecycle details and workflow migration guidance as part of your planning.

No extension options will be available after the retirement date.

Learn more:

• Guidance: Migrate from classic workflows to Power Automate flows in SharePoint | Microsoft Learn
• Microsoft Fixed Lifecycle Policy | Microsoft Learn
• SharePoint Designer 2010 and 2013 workflow migrations to Power Automate | Microsoft Learn
• SharePoint Designer 2013 Lifecycle | Microsoft Learn

[Compliance considerations]

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

Updated April 20, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Consecutive Interpretation is a new interpretation mode available as an add‑on to the existing Interpreter agent in Microsoft Teams. It enables structured multilingual conversations in meetings by providing shared, meeting‑level interpretation when enabled by a Microsoft 365 Copilot licensed user.

This mode uses consecutive (turn‑by‑turn) interpretation, meaning participants speak one at a time and each speaker’s words are interpreted before the next speaker begins. This structured flow reduces overlap, improves interpretation accuracy, and helps everyone stay aligned in real time.

Consecutive Interpretation is ideal for back‑and‑forth, interactive discussions where participants need to respond, clarify, and build on each other’s input across languages, such as working sessions, negotiations, and cross‑functional collaboration.

This message is associated with Microsoft 365 Roadmap ID 557180.

[When this will happen]

• Targeted Release: Rollout begins in early May 2026 (previously early April) and is expected to complete by late May 2026 (previously mid-April).
• General Availability (Worldwide): Rollout begins in late June 2026 (previously late May) and is expected to complete by mid-July 2026 (previously mid-June).

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using Microsoft Teams meetings where users are licensed with Microsoft 365 Copilot.

What will happen

• For tenants
  • The new Consecutive Interpretation mode extends the existing Interpreter agent to support structured, interactive multilingual meetings.
  • The existing Interpreter experience remains unchanged unless this new mode is enabled.
• For admins
• No new tenant‑level configuration is required.
• The feature is available to all users with a Microsoft 365 Copilot license.
• Existing compliance, privacy, and data‑handling policies for Interpreter continue to apply.
• For users
• When a Microsoft 365 Copilot licensed user enables the mode, interpretation becomes a shared meeting‑level experience rather than an individual setting.
• Participants speak consecutively, with each turn interpreted and delivered before the next participant begins.

[What you need to do to prepare]

• No action is required to maintain current behavior.
• Ensure any users who intend to use this mode have an active Microsoft 365 Copilot license.
• Consider providing guidance to users about when this mode is best suited (for example, working sessions, negotiations, or detailed multilingual collaboration).

[Compliance considerations]

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

Updated April 20, 2026: We are updating this post as a reminder. Thank you for your patience. 

Introduction

As announced earlier in MC616550 (June 2023), InfoPath Forms Service in SharePoint Online is being retired and will be removed from existing tenants after July 14, 2026. To support this transition and reduce future migration effort, Microsoft will prevent the publication of InfoPath forms in SharePoint Online for all tenants ahead of the service’s retirement.

When this will happen:

• After May 18, 2026: Publishing new InfoPath forms or publishing updates to existing forms will be blocked
• July 14, 2026: InfoPath Forms Service will be fully retired

How this affects your organization:

Who is affected:

• All SharePoint Online tenants
• InfoPath designers, publishers, and site owners
• IT administrators managing SharePoint Online

What will happen:

• After May 18, 2026, new InfoPath forms cannot be published
• Modifications to existing InfoPath forms cannot be published
• Existing published forms will remain available and usable
• There is no option to extend InfoPath Forms Service beyond retirement

What you can do to prepare:

To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can:

• Identify all InfoPath Forms usage in the tenant, per site collection and site.
• Evaluate the recency and volume of usage of InfoPath Forms.
• Understand lists, libraries, and content types that use InfoPath.

We recommend communicating to the impacted site owners and teams inside your organization now, so they are aware of the coming change.

For scenarios where InfoPath or InfoPath Forms Services are currently being used, we recommend migrating to Power Apps, Power Automate, or Microsoft Forms. Please ensure that you allow adequate time for migration of any use of InfoPath or InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog.

Note: Please plan the migration appropriately as there will not be an option to extend InfoPath Forms Services beyond the InfoPath retirement date of July 14, 2026.

Compliance considerations:

This update disables the ability to publish or republish InfoPath forms in SharePoint Online as part of a planned service retirement; it does not change how existing customer data is stored, processed, or governed.

Updated April 20, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Purview Information Protection admins can now exclude modern Microsoft 365 groups and scope sensitivity label policies to dynamic and non-mail enabled security groups. These capabilities give admins more flexibility, expanding policy targeting beyond individual users and mail-enabled groups. 

This message is associated with Microsoft 365 Roadmap ID 558685.

[When this will happen:]

• Public Preview: We will begin rolling out late April 2026 and expect to complete by mid-May 2026.
• General Availability: We will begin rolling out late May 2026 (previously mid-June) and expect to complete by early June 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• Information Protection admins managing sensitivity label publishing policies

What will happen:

• Admins can exclude modern Microsoft 365 groups from label publishing policies
• Admins can include non-mail-enabled security groups, including dynamic security groups
• Existing policies and configurations remain unchanged
• No user impact unless admins update policy scope

[What you can do to prepare:]

• No action is required
• Optionally review and update label publishing policies to take advantage of expanded scoping

Learn more: Create and publish sensitivity labels | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

[Introduction]

We’re introducing new license management capabilities for Microsoft Teams Events in the Teams admin center (TAC). This update provides admins with a centralized experience to discover, assign, and manage Attendee Capacity Pack licenses for event organizers from a single location. This experience aligns with existing Teams add-on license management patterns and helps admins proactively manage licensing needs for upcoming events.

[When this will happen]

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

[How this affects your organization]

Who is affected:

• Admins managing Microsoft Teams Events licensing in the Teams admin center
• Organizations that have purchased at least one Attendee Capacity Pack license

What will happen:

• Admins can discover Teams Events Attendee Capacity Pack licenses in a dedicated add-on licensing experience in TAC.
• Admins can assign, reassign, or revoke Attendee Capacity Pack licenses for event organizers.

Screenshot: Teams admin center > Teams Events: Attendee Capacity Pack license management experience:

>

• License assignment status will be visible at both the user and tenant levels.
• Admins removing a license will receive impact warnings if the organizer has upcoming events that may be affected.
• Admins can view upcoming events that could be impacted prior to removing a license.
• This feature is available by default when eligible licenses are present.
• No policy changes are required.
• There is no impact to user workflows.

[What you can do to prepare]

• No action is required before rollout.
• Review your current Teams Events licensing configuration.
• Update internal documentation and training materials as needed.
• Communicate this change to your helpdesk and event organizers.

Learn more about managing Attendee Capacity Pack licenses in TAC: Manage Attendee Capacity Pack licenses | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re updating the API endpoints used by Microsoft 365 Copilot to align with Microsoft’s ongoing transition to the cloud.microsoft domain. This change improves service reliability and security by ensuring Copilot-connected workloads use modernized Microsoft 365 network endpoints.

This update is part of a previously announced Microsoft domain unification initiative across Microsoft 365 services. This update does not introduce changes to the Microsoft 365 Copilot user interface and will not impact user experience, provided your environment follows published Microsoft 365 and Copilot network configuration requirements.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout will begin in late April 2026 and is expected to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators managing network configurations for Microsoft 365 and Microsoft 365 Copilot
• Organizations using custom firewall, proxy, or endpoint filtering configurations within their tenant environment that restrict or interfere with WebSocket (WSS) connections

What will happen:

• APIs used by Microsoft 365 Copilot will transition from the legacy office.com domain to the cloud.microsoft domain.
• This change occurs at the service infrastructure level and is not visible to users.
• No changes to the Microsoft 365 Copilot user interface or workflows are expected.
• The change is enabled by default and cannot be disabled
• If your organization has followed previously published Microsoft 365 and Microsoft 365 Copilot network connectivity requirements:
  • No action is required
  • No service impact is expected
• Organizations that restrict access to the cloud.microsoft domain or restrict WSS connectivity may experience Microsoft 365 Copilot performance or reliability issues

[What you can do to prepare:]

• Confirm that traffic to *.cloud.microsoft is included in your Microsoft 365 endpoint allow list.
• Verify that WSS connections to *.cloud.microsoft destinations are not blocked or interfered with.
• Exempt traffic to *.cloud.microsoft from intrusive network actions such as:
  • TLS decryption
  • Packet inspection
  • Network-level DLP
• Review Microsoft 365 network connectivity guidance:
  • Microsoft 365 endpoints
  • Microsoft 365 Copilot connectivity requirements
• Communicate this change to your networking and helpdesk teams.
• Run the Microsoft 365 Copilot Network Connectivity Test: Microsoft 365 Copilot Network Connectivity Test.

[Compliance considerations:]

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

Updated April 20, 2026: We are updating this post as a reminder. Thank you for your patience. 

Industry trends and feedback from our customers and partners make it clear that today’s businesses demand an intelligent, integrated forms experience that spans devices which InfoPath does not provide. As announced earlier, InfoPath Client 2013 will reach the end of its extended support period on July 14, 2026 (link), and to keep an aligned experience across Microsoft products, InfoPath Forms Service will be retired from SharePoint Online. We’re sending this message to bring it to your early attention to minimize the potential impact on your organization. 

[Key Points:]

• Major: Retirement
• Timeline: After May 18, 2026: Publishing new InfoPath forms or publishing updates to existing forms will be blocked and from July 14, 2026, Microsoft will remove InfoPath Forms Services for existing tenants.
• Action: Review and assess impact

[How this will affect your organization:]

• After May 18, 2026, publishing new InfoPath forms or publishing updates to existing forms will be blocked. Existing published forms will remain available and usable till July 14, 2026
• After July 14, 2026, users will no longer be able to use InfoPath forms in SharePoint Online. 

[What you need to do to prepare:]

To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can:

• Identify all InfoPath Forms usage in the tenant, per site collection and site.
• Evaluate the recency and volume of usage of InfoPath Forms.
• Understand lists, libraries and content types that use InfoPath.

We recommend communicating to the impacted site owners/teams inside your organization now, so they are aware of the coming change.

For scenarios where InfoPath or InfoPath Forms services are currently being used, we recommend migrating to Power Apps, Power Automate or Forms. Please ensure that you allow adequate time for migration of any use of InfoPath/InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog. 

Please plan appropriately as there will not be an option to extend InfoPath Form Services beyond the InfoPath retirement date of July 14, 2026.

Updated April 20, 2026: We have updated the timeline. Thank you for your patience. 

 Coming soon to Microsoft Purview | Data Loss Prevention: When an admin wants to enable user email notifications, policy tips also need to be enabled and vice versa. After this rollout, notifications and policy tips will be decoupled, and admins can configure the following rules to enable:

1. Only a user email notification
2. Only a policy tip
3. A user email notification and a policy tip
4. No policy tips or user email notifications

After this rollout, policy tips and user email notifications will align with the behavior currently available with Microsoft Exchange.

This message is associated with Microsoft 365 Roadmap ID 394279.

[When this will happen:]

Public Preview: We will begin rolling out mid-April 2026 (previously February 20) and expect to complete by late April 2026 (previously late February).

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

[How this will affect your organization:]

After rollout, to configure policy tips and user email notifications, you can use PowerShell or Purview | Data Loss Prevention.

In PowerShell

After rollout, use the new parameter called -NotifyUserType with the cmdlets New-DlpComplianceRule and Set-DlpComplianceRule.

Use New-DlpComplianceRule to create a new rule. Use Set-DlpComplianceRule to update an existing rule.

• Default value: NotSet
• To enable a policy tip: PolicyTip
• To enable a user email notification: Email
• To enable a user email notification and a policy tip: Email,PolicyTip

Example 1: New-DlpComplianceRule -Name "PT rule" -Policy "Policy Name" -ContentContainsSensitiveInformation @{Name="India Unique Identification (Aadhaar) Number"} -NotifyUserType PolicyTip -NotifyUser SiteAdmin,LastModifier,Owner

Example 2: Set-DlpComplianceRule -Identity "Rule Name" -NotifyUserType Email

To check that the value is set correctly, check the following and check the parameter value for NotifyUserType:

Get-DlpComplianceRule -Identity "Rule Name" | fl

In Data Loss Prevention (DLP)

Before rollout:

After rollout:

DLP examples

Rule 1: Configured to only trigger a user email notification:

Rule 2: Configured to only trigger a policy tip:

Rule 3: Configured to trigger a user email notification and a policy tip:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to update any relevant documentation as appropriate.

Updated April 20, 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 May 2026 (previously end of May) and expect to complete by end of May 2026 (previously end of June).  

[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

Updated December 5, 2025: We have paused GA release for this feature. Thank you for your patience.

Extend your sensitivity labels to specific or all subscriptions within Azure Storage, Azure SQL, Azure Cosmos DB, Azure Data Explorer, Azure Database for MySQL, Azure Database for PostgreSQL, Azure Databricks Unity Catalog, Azure SQL Managed Instance, Azure Synapse Analytics, Snowflake, Dataverse, and SQL Server via auto-labeling policy. Clearly define labeling conditions for data sources beyond M365 without fear of it interfering with existing M365 files configurations. 

This message is associated with Microsoft 365 Roadmap ID 429876.

[When this will happen:]

Public Preview: We will begin rolling out early July 2025 and expect to complete by late July 2025.

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

[How this will affect your organization:]

You can create new auto-labeling policies for non-m365 workloads Server that allow you to specify specific data assets or ALL assets to be automatically labeled when the out-of-the-box sensitive information types are detected in a column or asset. After the auto-labeling policy is turned on, wait 15 minutes, and then rescan the scoped data assets. The assets will be labeled automatically.

This change will be available by default for admins to configure.

After the rollout, these capabilities will no longer be available:

• The ability to extend labeling to assets in the Microsoft Purview Data Map (opt in)
  • Instead, you can select where to extend these assets in an auto-labeling policy
• Schematized data assets as an applicable label scope
  • You can select any label with the scope Files & other data assets for labeling in non-Microsoft 365 workloads
• Auto-labeling for schematized data assets in label definition
  • If you have configured Auto-labeling for schematized data assets in the label definition, you will need to reconfigure those conditions in an auto-labeling policy.

Tip: After you apply labeling to data assets, you can use protection policies to add access control settings associated with the label.

You will be able to select non-m365 workloads in the auto-labeling policy:

[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.

• Sensitivity Labels in the Microsoft Purview Data Map FAQ
• Learn about Microsoft Purview billing models | Microsoft Learn
• Data sources that connect to Microsoft Purview Data Map | Microsoft Learn