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

Updated February 3, 2026: We have updated the timeline. Thank you for your patience. 

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

Copilot license requirements:

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

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

This message is associated with Microsoft 365 Roadmap ID 482198.

[When this will happen:]

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

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

General Availability (Worldwide, GCC): This is now available.

[How this will affect your organization:]

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

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

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

This change will be available by default.

[What you need to do to prepare:]

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

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

Updated February 3, 2026: We have updated the timeline. Thank you for your patience. 

Outlook mobile users can now prepare for their meetings using Copilot chat with a single tap. This feature is available on Android and iOS platforms and requires a Microsoft 365 Copilot license. It helps users quickly access relevant meeting information, making preparation more efficient and personalized.

This message is associated with Microsoft 365 Roadmap ID 516568.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in mid-February 2026 (previously early February) and is expected to complete by mid-February 2026 (previously end of January).

[How this affects your organization:]

• Who is affected: Users of Outlook mobile on Android and iOS who have a Microsoft 365 Copilot license.
• What will happen:
  • Eligible users will see a new Copilot chat option to prepare for meetings directly within Outlook mobile.
  • The feature will be ON by default for licensed users. To turn off Copilot in Outlook review Turn off Copilot in Microsoft 365 apps | Microsoft Support.
  • No admin configuration is required.
  • Existing policies and permissions are respected.

Screenshots 1-3 provide a view of the previous experience:

Screenshots 4-5 provide a view of the new experience – Selecting Prepare will take users to Copilot Chat, enabling users to ask follow-up questions:

[What you can do to prepare:]

• No admin action is required at this time.
• If desired, communicate this feature to helpdesk staff.
• Update internal documentation if you detail this feature.
• Ensure users have the appropriate Microsoft 365 Copilot license to access this feature.

[Compliance considerations:]

Updated February 3, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

To help users better prepare for upcoming meetings, Microsoft is enhancing the Up Next card experience in Microsoft 365. A new Prepare button will replace the Join button up to 5 minutes before a meeting starts, offering a one-tap way to access Copilot’s meeting preparation tools. This update supports improved productivity and readiness, aligning with feedback for more proactive meeting support.

Screenshot 1: Tap Prepare in Up Next.

Screenshot 2: Users can prepare with Copilot Chat.

[When this will happen:]

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins March 2026 (previously early February) and is expected to complete by end of March 2026 (previously late February).

[How this affects your organization:]

• Who is affected: Users with a Microsoft 365 Copilot Premium license.
• What will happen:
  • The Up Next card will display a Prepare button instead of Join until 5 minutes before a meeting.
  • This button provides quick access to Copilot’s meeting preparation features.
  • No changes to admin settings or policies are required.
  • The feature is enabled by default for eligible users.

[What you can do to prepare:]

• No admin action is required at this time.
• You may wish to:
  • Inform helpdesk and support teams of the upcoming change.
  • Share this support article with users: Prepare for your meeting with Copilot
  • Update internal documentation if you reference the Up Next card or meeting workflows.

[Compliance considerations:]

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

Updated February 2, 2026: In our January 13, 2026 update, we shared that broad availability of Anthropic as a subprocessor in the Researcher agent was expected by the end of January. Rollout is taking longer than anticipated as we complete additional validation. During this phased rollout, the Anthropic option in Researcher may not yet be visible in all tenants; the existing Researcher functionality remains unchanged. We will provide another update in this post when rollout to Researcher is complete. 
Use Claude with Researcher in Microsoft 365 Copilot

[Introduction:]

In September, Anthropic models became available in certain Copilot experiences through an opt-in setting, where use was subject to Anthropic’s commercial terms and data processing agreement. On January 7, 2026, Anthropic models will be enabled by default for many customers and now offered under the Microsoft Product Terms and Data Protection Addendum. To enable this change, Anthropic has been onboarded as a Microsoft subprocessor. This transition extends Microsoft’s contractual commitments and data protection standards to the use of Anthropic models in Copilot experiences.

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft 365 Copilot and Microsoft Copilot Studio.
• Microsoft 365 Copilot licensed customers participating in select Frontier features such as Word, Excel, PowerPoint, and Researcher agents, as well as Agent Mode in Excel.

Key changes

• Dec 8, 2025: New admin toggle for Anthropic models appears in the Microsoft 365 admin center (MAC). For most commerical cloud customers, it will be enabled ON by default (except customers in EU/EFTA and UK will be OFF by default). See “customer and region exclusions” section below for more details.
• January 7, 2026: Anthropic as a Microsoft subprocessor becomes enabled on your tenant; the legacy admin toggle to opt-in to Anthropic’s commercial terms and data processing agreement is deprecated.
  • If you previously opted in to the legacy Anthropic toggle, and you’re in an excluded region, you would need to opt in to the new subprocessor toggle.
• Admins can opt out in MAC now – no need to wait until January.

Some features are only available when Anthropic models are enabled. If you turn off this option, certain features may no longer be accessible.

Customer and region exclusions:

The following customers and regions will not have the toggle set to default on:

• Customer tenants in EU/EFTA and UK: The toggle will be set to default off. You will need to opt in to use Anthropic models as a subprocessor.
• Government clouds (GCC, GCC High, DoD) or sovereign clouds: Anthropic models are not yet available in government or sovereign clouds. No toggle will be present for those clouds.

What does it mean that Anthropic is now a Microsoft subprocessor?

As a subprocessor for Copilot experiences, Anthropic will operate under Microsoft’s direction and contractual safeguards. This includes coverage under the Microsoft Data Protection Addendum (DPA) and Product Terms. In addition, use of Anthropic models in Microsoft 365 Copilot falls under our Enterprise Data Protection as described here. Note that Anthropic models are currently excluded from EU Data Boundary and when applicable, in-country processing commitments. 

Learn more:

• Integrate and manage Anthropic’s AI models in Microsoft 365 Copilot
• Enterprise data protection in Microsoft 365 Copilot and Microsoft 365 Copilot Chat
• Use Claude with Researcher in Microsoft 365 Copilot
• Get started with Word, Excel, and PowerPoint Agents (Frontier) in Microsoft 365 Copilot
• Choose an external model as the primary AI model – Microsoft Copilot Studio

Updated February 3, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re adding a new setting in Microsoft Teams for Desktop and Web that lets users select what happens when they press Enter while composing a message. This update responds to customer feedback for more control and helps prevent accidental message sends. It also aligns Teams with behavior in other messaging apps, creating a familiar and predictable compose experience.

This message is associated with Microsoft 365 Roadmap ID 537279.

[When this will happen:]

• Targeted Release: Rollout will begin in late February 2026 (previously early February) and complete by end of February 2026 (previously mid-February).
• General Availability (Worldwide, GCC): Rollout will begin in late February 2026 (previously mid-February) and complete by end of February 2026 (previously late February).
• General Availability (GCCH, DoD): Rollout will begin in early March 2026 and complete by mid-March 2026.

[How this affects your organization:]

Who is affected: All users of Microsoft Teams for Desktop and Web.

What will happen:

• A new setting will appear under Settings > Chats and channels: “When writing a message, press Enter to…”



• Users can select:
  • Send the message (default for all users)
  • Start a new line (to send, press Ctrl + Enter or Cmd + Enter)
• Teams will show contextual hints near the compose box to remind users of the current behavior.



• Additional behavior:
  • Shift + Enter will always insert a new line.
  • Teams will show contextual hints near the compose box to remind users of the current behavior.
• Applies only to Desktop and Web.
• This setting is per-user and will roam across devices.
• There is no admin control, policy, or Graph API configuration.

[What you can do to prepare:]

No admin action is required.

• Notify your helpdesk that users will see a new setting affecting how messages are sent.
• Update any internal documentation that references Teams compose behavior.
• Share this explanation with users: “Teams now lets you select whether Enter sends your message or creates a new line. The default is ‘Press Enter to send.’ You can change this in Settings > Chats and channels.”

There are no changes to Data Loss Prevention (DLP), compliance boundaries, or message retention.

[Compliance considerations:]

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

Updated February 3, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft 365 Copilot in PowerPoint will soon support enterprise image libraries hosted on Adobe Experience Manager (AEM). This integration allows users to generate slides using branded images from your organization’s asset library, helping maintain brand consistency and streamline content creation.

This message is associated with Roadmap ID 516037, 516038, and 516039.

[When this will happen:]

General Availability (Worldwide): Rollout begins end of February 2026 (previously early February) and is expected to complete by end of April 2026 (previously end of March)

[How this affects your organization:]

Who is affected:

• Organizations using Adobe Experience Manager for brand asset management
• Admins and brand managers configuring enterprise image libraries
• PowerPoint users leveraging Microsoft 365 Copilot

What will happen:

• Admins can connect enterprise image libraries from AEM to Microsoft 365 Copilot in PowerPoint.
• Users will be able to generate slides using branded images from AEM.
• If no enterprise image library is connected, the branded image option will be disabled, and only Microsoft 365 images will be available.
• This feature is available by default for admins to configure; no opt-in required.

[What you can do to prepare:]

• Deploy AEM assets Microsoft 365 Copilot Connector by following the steps outlined in the article Deploy the Adobe Experience Manager Assets Microsoft 365 Copilot connector.
• Give your final consent on the Adobe Experience Manager Assets screen



• Ensure images in AEM include robust metadata (keywords, titles, alt-text) for better searchability.
• Communicate this change to your design and marketing teams.
• Update internal documentation if you detail image sourcing for PowerPoint.

Once setup is complete, users can select the New Slide with Copilot icon in the PowerPoint ribbon, enter a prompt, and choose their preferred image source—either Microsoft 365 images or their organization’s branded image library—via the Image Source menu.

Learn more:

• About Adobe Experience Manager Assets Microsoft 365 Copilot connector
• Keep your presentation on-brand with Copilot

[Compliance considerations:]

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

Updated February 3, 2026: Thank you for your feedback. We will be providing updated guidance via Message center shortly. You can safely disregard this message.

[Introduction]

We’re adding new output formats to the Researcher agent in Microsoft 365 Copilot to give users more flexibility in how they create, share, and use AI‑generated research reports. Based on customer feedback, users will now be able to export Researcher reports to additional formats and benefit from an updated experience for existing options.

This message is associated with Microsoft 365 Roadmap ID 546246.

[When this will happen]

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

[How this will affect your organization]

Who is affected: All users with access to the Researcher agent in Microsoft 365 Copilot.

What will happen:

Users will see new and updated export options, including:

• New output formats:
  • PowerPoint
  • PDF
  • Infographic
  • Audio overview
• Updated UX:
  • Improved export experience for existing Word and Pages formats

Additional details:

• These features are on by default; no admin configuration is required.
• There is no impact to existing workflows. Users can begin using the new formats as soon as they appear in their tenant.

[What you can do to prepare]

No action is required.

Admins may choose to:

• Inform users about the expanded export options in the Researcher agent.
• Update internal documentation if your organization references Researcher agent capabilities.

[Compliance considerations]

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

[Introduction]

We’re introducing the ability for users to copy tables created when using Chat in Microsoft 365 Copilot. This enhancement makes it easier for users to take AI‑generated structured content—such as comparison tables, checklists, and summaries—and reuse it directly in documents, emails, spreadsheets, and other Microsoft 365 apps. This feature is available for users with a Microsoft 365 Copilot license.

[When this will happen:]

General Availability (Worldwide): rollout will begin early March 2026 and complete by early March 2026.

[How this affects your organization:]

Who is affected:

Users with a Microsoft 365 Copilot license.

What will happen:

• Users will be able to copy tables generated in Chat.
• This feature is enabled by default for all users with a Microsoft 365 Copilot license.
• No existing admin policies or controls change.
• No impact to workflows beyond the new capability.

[What you can do to prepare:]

• No admin action is required.
• Update helpdesk or training materials as needed.

[Compliance considerations:]

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

[Introduction]

We are updating the Microsoft Teams app bar to create a cleaner and more focused experience. App names will be hidden by default, showing only app icons. This helps reduce visual noise and improves overall navigation clarity. Users can choose to show app names again in Settings.

[When this will happen]

General Availability (Worldwide): We will begin rolling out in late February 2026 and expect to complete by early March 2026.

[How this affects your organization]

Who is affected: All Microsoft Teams users in commercial (non-government) tenants.

What will happen:

• App names in the Teams app bar will be hidden by default.
• Users will see app icons only, providing a simplified vertical navigation experience.
• Users who prefer to show app names may update this setting individually:
  • Settings > Appearance > Show app names in the app bar
• No admin configuration changes are required.
• There is no impact to existing policies, permissions, or app availability.

Screenshot 1 – Before:

Screenshot 2 – After:

[What you can do to prepare]

• No action is required.
• If helpful, you may notify users or help desk staff about this visual update and how to re-enable app names.
• If your organization maintains internal documentation or screenshots of the Teams interface, consider updating them after rollout.

[Compliance considerations]

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

[Introduction]

We are expanding access to People Skills within Microsoft Teams. With this update, employees will be able to view skills directly on the Microsoft 365 profile card in Teams—making it easier to learn about colleagues, strengthen collaboration, and manage their own skills profile in the flow of work.

As a reminder, People Skills enables employees to build a skills profile based on a shared taxonomy, helping them showcase expertise and connect with others. Eligible Microsoft 365 Copilot, Viva, and Microsoft 365 E3/E5 users may also benefit from AI‑powered skill inferencing, which uses Microsoft Graph signals to automatically generate a personalized skills profile for each eligible employee and keep it up to date. People Skills data enhances Microsoft 365, Copilot, and Viva experiences by providing richer, contextual insights about people across the organization.

Learn more: People Skills | Microsoft Adoption

This message is associated with Microsoft 365 Roadmap ID 552588.

[When this will happen:]

• Targeted Release: We will begin rolling out early March 2026 and expect to complete by mid-March 2026.
• General Availability (Worldwide):We will begin rolling out March 2026 and expect to complete by April 2026

[How this affects your organization:]

Who is affected: 

• Users who have access to People Skills and can view the Microsoft 365 profile card in Teams

What will happen: 

Once this update is rolled out, all employees in tenants who have already set up People Skills will find a Skills section on the Microsoft 365 profile card in Teams. This makes it easier for users to:

• View colleagues’ skills in the profile card on Teams to better understand and connect with colleagues
• Access and manage their own skills profile from the new Skills component on the profile card in Teams

There is no change to existing People Skills admin controls, configuration settings, or data access permissions. People skills must be setup before the Skills component

is visible in M365 Profile Cards.

[What you can do to prepare:]

 If your organization uses People Skills today, no admin action is required. The experience will automatically appear on the profile card in Teams.
If you do not have People skills setup, please review your documentation to do so in admin center. Learn how to set up People Skills.

You may wish to:

• Inform users about this enhanced visibility of skills in Teams.
• Set up People Skills in admin center. Learn how to set up People Skills.

[Compliance considerations:]

• No changes have been made to how existing customer data (including documents, emails, and chats) is processed, stored, or accessed. This update does not introduce new AI/ML capabilities or modify inferencing behavior; it only expands where People Skills data is displayed.

We are reiterating the guidance for connector settings to ensure customers are using healthy configurations. The key problematic configurations we are seeing are:

1. When a tenant has an Inbound connector of type OnPremises and the connector does certificate-based authentication using a certificate with a subject/SAN for a domain that is NOT an Accepted Domain of the tenant.
2. When a tenant has an Inbound connector of type OnPremises and the connector does IP-based authentication, but the IP is used by other tenants.

These anti-patterns typically occur when you are using a 3rd party service to relay email through Exchange Online but could also occur if your organization has a single on-premises Exchange Server connecting to multiple Exchange Online tenants.

These configurations can cause incorrect mail flow because Exchange Online is a multi tenant service and relies on message attribution to determine which tenant an incoming message belongs to. When messages are received through an Inbound connector of type OnPremises, attribution is determined using the following priority order:

1. The domain on the TLS certificate presented by the sending server
2. The P1 MailFrom (envelope sender) domain
3. The P1 RcptTo (recipient) domain

[How this will affect your organization:]

We may perform internal changes, such as tenant moves, without notice, which can impact mail flow if a tenant has a bad connector configuration. This means a misconfigured connector that works today may unexpectedly stop working.

[What you need to do to prepare:]

If you have a single on-premises Exchange Server connecting to multiple Exchange Online tenants, your on-premises Exchange environment must use a unique client certificate to send to each unique Exchange Online tenant belonging to your organization. You must configure a unique Send Connector on-premises for each unique tenant in Exchange Online that you want to route on-premises traffic to: Send connectors in Exchange Server | Microsoft Learn. You should also prioritize configuring Inbound connectors of type OnPremises in Exchange Online to use certificate-based authentication, rather than IP based . For best performance, Exchange Online tenants Inbound connector’s should reference the unique client certificate dedicated for that connector path.

If you need to use a third-party add-on service to process email messages sent from your organization and then relay through Exchange Online, the third-party service must support a unique certificate for your organization, and the certificate domain (in Subject name or SAN) must be an accepted domain of your organization. In addition, you must update your Inbound connector of OnPremises type to use the unique certificate domain, via property TlsSenderCertificateName. An example of this scenario is your organization using a third-party CRM cloud service to send emails on behalf your organization to mailboxes of your company or other external users. To learn more, see Scenario: Integrate Exchange Online with an email add-on service.

[Introduction]

We’re introducing a new end-user moderation control in Viva Engage: Hide a user’s messages. This feature allows users to reduce visibility of messages from specific individuals, helping minimize unwanted or distracting interactions while preserving community engagement.

This message is associated with Roadmap ID 513276.

[When this will happen:]

General Availability (Worldwide): Rolling out late February 2026 and completing by late March 2026.

[How this affects your organization:]

Who is affected:

All Viva Engage users.

What will happen:

• The feature is on by default.
• Admins can turn this feature off in the Engage admin center.
• Users will have a new option to hide another user’s messages from:
  • Any message in Viva Engage

  

  • A user’s profile page

  

• When a user is hidden:
  • Their threadstarters will no longer appear in Home Feed or email digests.
  • In communities and other locations, their threadstarters will appear collapsed with a click‑to‑reveal option.
  • In all surfaces, comments appear collapsed with a click-to-reveal option.
• Some roles cannot be hidden, including:
  • Designated leaders (requires the Viva Communications & Communities or Viva Suite license)
  • Corporate communicators
  • Network/verified admins
  • Engage admins

[What you can do to prepare:]

No admin action is required.

We recommend:

• Informing users about this new moderation option.
• Updating internal documentation or guidance, as needed.
• Using the Engage admin center if you wish to disable the feature.

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

[Compliance considerations:]

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

[Introduction]

We are introducing a new Microsoft Purview Role-Based Access Control (RBAC) role—Purview Agent Deployment—and adding it to several existing Purview built‑in role groups. This update enables analysts who intend to work with Purview agents to also deploy them directly without requiring administrator involvement. This change improves onboarding efficiency and supports broader adoption of Purview’s AI‑powered agent capabilities.

[When this will happen:]

General Availability (Worldwide): Rollout begins late February 2026 and is expected to complete by mid‑March 2026.

[How this will affect your organization:]

Who is affected:
Admins and analysts who intend to use Microsoft Purview agents or manage Purview role groups.

What will happen:

• The new Purview Agent Deployment role will be added to these built‑in role groups:
  • Compliance Administrator
  • Data Security Management
  • Information Protection
  • Information Protection Analysts
  • Information Protection Investigators
  • Insider Risk Management
  • Insider Risk Management Analyst
  • Insider Risk Management Investigator
  • Purview Agent Management
• The Purview Agent Management role group will continue to include Purview Content Analyst role and maintain access to Posture agent capabilities.
• Users assigned to these role groups will be able to deploy, use, and manage Purview agents end‑to‑end, including:
  • Data Security Triage Agent (DLP)
  • Data Security Triage Agent (IRM)
  • Data Security Posture Agent (DSPM)
  • Future agents as released
• No default data access permissions are changed.
• No additional visibility into customer content is added.
• Organizations can optionally enforce separation of deployment vs. analysis roles using custom role groups.

[What you can do to prepare:]

• Analysts assigned to built‑in Purview role groups will automatically be able to deploy agents.
• If restricting agent deployment:
  • Create a custom role group without the Purview Agent Deployment role.
  • Assign analysts accordingly.
• Ensure custom groups include the Purview Agent Deployment role only where intended.
• Review and update internal RBAC documentation, training, and onboarding materials.

Learn more: Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview | Microsoft Learn

[Compliance considerations:]

[Introduction]

We will introduce a new indicator in Microsoft Teams channels that use the threads layout. As more teams begin using channels to organize their collaboration, we are seeing an increase in simultaneous meetings within the same channel. Today, Teams does not provide an efficient way for channel members to discover all ongoing meetings and choose the one they want to join. This new indicator will help fill that gap by making it easier for users to see active meetings at a glance and quickly join the meeting that best fits their needs.

The indicator will appear in the channel header and will expand to show active meetings, along with basic details and a Join button:

This update is associated with Microsoft 365 Roadmap ID 513272.

[When this will happen]

Targeted Release (Worldwide): We will begin rolling out in mid-February 2026 and expect to complete by late February 2026.

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

[How this affects your organization]

Who is affected:

• Users in Teams channels that use the threads layout
• All Microsoft 365 tenants, including Targeted Release

What will happen:

• A new ongoing meetings indicator will appear in the channel header.
• Users will be able to expand the indicator to view active meetings.
• Each meeting will show basic details and a Join button.
• The feature will be on by default; no admin configuration will be required.
• No changes will occur to existing meeting behaviors, policies, or controls.

[What you can do to prepare]

No admin action will be required. This feature will become available automatically for channels that use the threads layout.

You may optionally:

• Inform helpdesk or support staff of this change.
• Update internal Teams training materials as needed.

[Compliance considerations]

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

[Introduction]

Microsoft is retiring Teams Live Events and the Microsoft Graph APIs used to create them on June 30, 2026. Existing events scheduled before that date will continue to function through February 28, 2027. We encourage customers to migrate to Teams town halls, which offer an enhanced, end-to-end experience for large-scale events. This retirement supports Microsoft’s investment in Teams town halls, which provide an improved experience for digital and hybrid events and include comparable Graph APIs for programmatic creation, management, and integration.

[When this will happen]

• Teams Live Events and associated Microsoft Graph APIs will retire on June 30, 2026.
• Existing Teams Live Events will continue to function through February 28, 2027.
• Customers will no longer be able to schedule Teams Live Events past June 30, 2026, beginning February 3, 2026.
• Customers scheduling through Dynamics 365 will not be able to schedule events past June 30, 2026, beginning February 3, 2026.
• The isBroadcast property within the onlineMeetingGraph resource will remain available until June 30, 2026.

[How this affects your organization]

You are receiving this message because our reporting indicates your organization may be using or has access to Teams Live Events. 

Who is affected:

• Organizations using Teams Live Events.
• Organizations using Microsoft Graph APIs to create Teams Live Events.
• Organizations scheduling Teams Live Events through Viva Engage or Microsoft Dynamics 365.

What will happen:

• Teams Live Events and the associated Microsoft Graph APIs will no longer be available after retirement.
• Teams town hall is now the recommended option for large scale events.
• New scheduling of Teams Live Events will become limited as the retirement date approaches.
• Existing scheduled events will remain supported through the end of the service window.
• Workflows or applications that depend on the isBroadcast property will need to transition.
• Teams town halls and Teams meeting Graph APIs will serve as replacements for large-scale broadcast scenarios.
• Customers should migrate to Teams town halls or Teams meeting Graph APIs.

[What you can do to prepare]

No admin configuration changes are required. We recommend the following:

• Assess dependencies
• Identify where your organization uses Teams Live Events, including events scheduled through Viva Engage, Dynamics 365, or custom Graph-based solutions.
• Plan your transition
• Move large-scale broadcast and virtual event scenarios to Teams town halls or Teams meetings.
• Update or replace workflows that rely on the retiring Graph API functionality.
• Prepare users
• Inform event organizers and producers about the retirement and their transition path.
• Update internal training, documentation, and support materials.

Use these resources

• Plan for Teams town halls | Microsoft Teams | Microsoft Learn
• Get started with town hall in Microsoft Teams | Meetings | Microsoft Teams | Microsoft Support
• Retiring Teams live events: The next chapter for events at scale in Microsoft Teams | Microsoft Teams Blog
  
• Virtual events town hall API use cases | Microsoft Graph | Microsoft Learn
• Customer Hub events readiness sessions – recommended for Teams Live Events users transitioning to Teams town halls:
• What’s new in Microsoft Teams town halls and webinars
• Migrating from Teams Live Events to town halls
• Tips, tricks, and traps for town halls and webinars in Microsoft Teams

[Compliance considerations]

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

Introduction

Today, IT administrators can restrict whether an organizer can create a webinar using the AllowWebinars setting under Set-CsTeamsEventsPolicy. Webinars are events that require registration.

With the new Events scheduling experience launching in the Meet app, we are introducing a new policy, Registration, which will control whether organizers can schedule any event with registration. AllowWebinars will continue to control whether an organizer can create a webinar via the Teams Calendar App. 

Registration will default to Enabled.

When this will happen:

• Targeted Release: We will begin rollout early February 2026 and expect to complete by late February 2026.
• General Availability (Worldwide, GCC, GCCH, DoD): We will begin rollout mid-March 2026 and expect to complete by late March 2026.

How this affects your organization:

Who is affected:

• Teams administrators managing meeting and events policies
• Users who schedule events or webinars in the Teams Meet app or in the Teams Calendar app

What will happen:

• A new policy setting, Registration, will be added to Teams events policies.
• Registration = Enabled (default): Organizers can enable registration for any event.
• Registration = Disabled: Organizers cannot enable registration for any event and cannot create webinars.
• If AllowWebinars is Disabled but Registration is Enabled, organizers can schedule events with registration but cannot create webinars on the Teams Calendar app.
• No UI changes occur unless the admin updates policy.

What you can do to prepare:

• If you want all users to create events with registration, no action is required.
• To disable registration for all events, update the policy using PowerShell:

Set-CsTeamsEventsPolicy -Identity Global -Registration Disabled

• Communicate any changes to organizers or helpdesk staff.
• Update internal documentation as needed.
• Note: if you make changes to Registration prior to rollout, it will impact webinars as described above.

Learn more: Set-CsTeamsEventsPolicy (will be updated before rollout)

Compliance considerations:

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

[Introduction]

We’re retiring the isBroadcast property used to create Teams Live Events through Microsoft Graph. This change aligns with our investment in the Virtual Event APIs, which offer richer capabilities for Webinars and Town Halls, including improved registration, attendee management, presenter configuration, and reporting. These APIs provide more modern, flexible, and scalable options for organizations managing large virtual events.

[When this will happen]

• March 31, 2026: isBroadcast will be removed from the Microsoft Graph beta endpoint
• June 30, 2026: isBroadcast will be removed from the Microsoft Graph v1.0 endpoint

[How this affects your organization]

Who is affected: Organizations and developers who use the Microsoft Graph onlineMeeting resource with the isBroadcast property to create Teams Live Events programmatically.

What will happen:

• The isBroadcast property will no longer be available in Microsoft Graph after the dates listed above.
• Attempts to create Teams Live Events using isBroadcast will fail.
• Programmatic creation of new Teams Live Events through Microsoft Graph will no longer be supported.
• Developers should transition to the Virtual Event APIs, which support Webinar and Town Hall scenarios.
• Existing Teams Live Events scheduled before the retirement date will continue to function normally.

[What you can do to prepare]

If your apps, scripts, or workflows use isBroadcast, you should:

• Review updated API documentation and migration guidance.
• Migrate to the Virtual Event APIs:
  • virtualEventWebinar for Webinars
  • virtualEventTownhall for Town Halls
• Test updated workflows before the retirement dates.
• Update any internal documentation and notify app owners or developers who maintain integrations.
• If your organization does not programmatically create Teams Live Events using Microsoft Graph, no action is required.

Learn more: Choose the right Teams meeting type | Microsoft Graph | Microsoft Learn

[Compliance considerations]

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

Updated February 3, 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: Starting 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 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.