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

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

Applies to: Teams for Windows desktop and Teams for Mac desktop 

[Introduction:]

All meeting participants joining from native apps on Windows and macOS will be able to request to start collaborative annotations when a screen or window is being shared. The annotations start only after the active sharer approves the request. This capability is available exclusively in the new Microsoft Teams experience on native Windows and macOS apps.

This release also introduces a meeting option in the Participation section, allowing organizers and co-organizers to choose who can start annotations. By default, “Everyone” can access the “Start Annotation” button, but organizers and co-organizers can limit it to just the “Active Sharer”, making the button visible only to the person currently sharing their screen or window.

Note: Users can view and annotate in Teams on the web but cannot initiate annotations. Anonymous users in the meeting will not be able to send a request.

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

Targeted Release: We will begin rolling out early May 2026 (previously mid-April) and expect to complete by mid-May 2026 (previously late April).

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-May 2026 (previously late March) and expect to complete by late May 2026 (previously late April).

[How this will affect your organization:]

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen, who can choose to accept or deny it.

Meeting Organizer Settings (Meeting Options)

A new “Who can start annotations?” option appears under the Participation section in Meeting Options. Organizers and co-organizers can select:

• Everyone (default) — All participants see the “Start Annotation” button
• Active Sharer — Only the person currently sharing sees the annotation button

After rollout, the default value of Everyone will apply to all newly created meetings. For meetings created before rollout, the setting will be Active Sharer to match the current behavior where only the active sharer can start annotations. Organizers and co-organizers must manually update existing meetings if they want to enable the new behavior for those meetings. 

Participant Annotation Request Flow 

When a participant who is not the active sharer wants to annotate, they click the “Start annotation” button in the meeting toolbar. A confirmation dialog appears, and once the participant clicks “Request”, a notification is sent to the presenter for approval.

1. Click the “Start annotation” button in the meeting toolbar to initiate an annotation request.



2. Confirm the request in the dialog box. Once approved, annotations start request will be sent to active sharer



3. Request sent notification confirms the request is pending and the presenter needs to approve it. 

Presenter Approval Experience

The active sharer (presenter) receives a notification at the top of their screen indicating that a viewer wants to start annotations. The presenter can choose to Deny or Allow the request.

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

• Notify your users about this change and how the annotation request/approval flow works 
• Update relevant documentation to reflect the new meeting option and participant behavior 
• Educate meeting organizers on the new “Who can start annotations?” meeting option under Participation 
• Communicate to end users that they can now request to start annotations during screen sharing sessions 

This change will be available by default. 

Additional Resources: 

• Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (will be updated before rollout)
• How to use Collaborative Annotations in a Microsoft Teams meeting (2022)
• Microsoft 365 Roadmap ID 89975

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

Copilot is making it easier to manage scheduling conflicts by automatically rescheduling 1:1 meetings and personal events. Within the meeting event form, users can indicate which events are more flexible and allow Copilot to reschedule them if conflicts arise. Users can also set preferences for when rescheduled events should occur. Copilot will detect double-bookings and automatically move these flexible events to a better time—saving users time and reducing manual coordination.

A Microsoft Copilot license is required to utilize this functionality.

[When this will happen:]

Targeted Release: Rollout begins mid-February 2026 (previously mid-November 2025) and expected to complete in May 2026 (previously end of February).

[How this affects your organization:]

Copilot users will gain the ability to automatically resolve scheduling conflicts for 1:1 meetings and personal events. This feature is especially useful for users with recurring 1:1 series that do not need to occur at a specific time each week, helping automatically reschedule those meetings if a conflict arises. The feature is available for Copilot-licensed users and can be enabled through the meeting form.

Main form with new toggle control for automatic rescheduling:

Users can specify their rescheduling preferences (if not set, Copilot will pick intelligent defaults):

This post will be updated with a link to the support article once published.

[What you can do to prepare:]

No admin action is required. However, you may want to:

• Inform users about this new capability and how to set their rescheduling preferences in the meeting form.
• Review any internal guidance on calendar management or Copilot usage to ensure alignment.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Yes – Calendar data is used to identify and reschedule events.
• Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? Yes – Copilot uses AI to analyze and reschedule events.
• Does the change provide end users any new way of interacting with generative AI? Yes – Users interact with Copilot to manage scheduling.

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

With this release, users can discover and add SharePoint agents directly within Microsoft Teams chats on Desktop and Mac. Agents can be added via the Add Agents and Bots option in the chat roster dropdown, which opens the in-context store for discovery and selection. This enables users to quickly bring SharePoint agents into conversations to support collaboration.

Additionally, SharePoint agents are available in the Teams Store under the Agents category, making them easier to find and deploy across Teams experiences.

This message is associated with Microsoft 365 Roadmap ID 515465.

[When this will happen]

• Targeted Release: Rolling out in mid-June 2026 (previously early May) and expected to complete in late June 2026 (previously mid-May).
• General Availability: Rolling out in late June 2026 (previously mid-May) and expected to complete by late July 2026 (previously end of May).

[How this affects your organization]

• Who is affected: All users of Microsoft Teams on Desktop and Mac.
• What will happen:
  • Users will be able to discover and add SharePoint agents from the in-context store in Teams chats.
  • SharePoint agents will be available in the Teams Store under the Agents category.
  • Agents can be added via the Add Agents and Bots option in the chat roster dropdown.
  • No admin action is required; the feature is enabled by default.
  • Existing policies are respected; no changes to admin controls are needed.

[What you can do to prepare]

• Ensure that intended users have E3 or E5 (with Teams) licensing, and one of the following options: 
  • Microsoft 365 Copilot license OR
  • Pay-as-you-go (PAYG) separately setup for SharePoint agents on MAC.

• Inform helpdesk staff in case users have questions about accessing or using SharePoint agents.
• Share this update with users to highlight new collaboration opportunities.
• Update internal documentation if you maintain guidance on Teams agents or bots.

Learn more: Share an agent from SharePoint in Teams | Microsoft Support

[Compliance considerations]

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

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

[Introduction]

We’re introducing a new co-branding capability that will allow organizations to display a branded footer at the bottom of the Chat screen in the Microsoft 365 Copilot app. This update will enable admins to add their organization’s logo to their users’ Microsoft 365 Copilot app, helping users confirm they are using their trusted, work-managed Copilot experience.

This feature will begin rolling out in early May 2026 (previously late March) and is expected to complete by end of May 2026 (previously late April).

This message is associated with Microsoft 365 Roadmap ID 555852.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using the Microsoft 365 Copilot app.

What will happen

• Admins will be able to upload a logo in the Microsoft 365 admin center to customize the footer in the Microsoft 365 Copilot app.
• The footer will display an “Approved by [Logo]” indicator to help users confirm they are in an organization-approved Copilot environment: 

  

• Only the logo from your organization’s theme configuration will be used; other theme elements will not be applied in this release.
• This feature will be off by default and will require admin configuration.
• There will be no user impact unless an admin enables the footer.

[What you can do to prepare]

No action will be required unless you want to enable the branded footer.

Admins who want to configure this feature should:

• Review and verify your organization’s theme configuration in the Microsoft 365 admin center.
• Upload the logo you want to display in the Microsoft 365 Copilot app footer once rollout begins.
• Use the existing theme management flow to apply co-branding once the feature is available.

For configuration guidance: Customize the theme for your organization | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

Microsoft is improving the custom license request experience for Microsoft 365 Copilot to help organizations better align Copilot license requests with their internal approval workflows. With this update, admins can create Copilot‑specific request policies and tailor guidance by user group, allowing more precise routing and clearer instructions for people requesting a license.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users who request Microsoft 365 Copilot licenses
• Admins who configure license request policies in the Microsoft 365 admin center

What will happen

• Admins will be able to create product‑specific custom license request policies for Microsoft 365 Copilot.
• Admins can scope policies by user group, such as security groups or Microsoft 365 groups.
• When someone requests a Copilot license, they will see:
  • Admin‑defined instructions.
  • A link to your organization’s internal approval workflow.
• License approvals will continue to occur outside Microsoft systems, using your existing internal processes.
• Existing custom license request behavior will remain unchanged unless an admin updates configuration.

[What you can do to prepare]

No action is required if you want to continue using your existing configuration.

If you choose to adopt the new capabilities, you can:

• Review your current custom license request policies in the Microsoft 365 admin center.
• Decide whether to apply product‑specific or group‑specific policies for Copilot.
• Confirm that internal approval links and instructions are accurate and accessible.
• Communicate these updates to your IT support or helpdesk teams.

Learn more: Manage self-service license requests in the Microsoft 365 admin center | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

• Generate configurations
• Validate setups
• Run simulations
• Surface diagnostics
• Explain the rationale behind recommendations

[Introduction]

Microsoft is taking steps to help keep customers safe as AI models become more advanced including plans to incorporate advanced AI models directly into our Security Development Lifecycle (SDL) to identify vulnerabilities and develop mitigations and updates. We are also sharing guidance through Microsoft Security Exposure Management on how customers can reduce their exposure as well as capabilities they can use to take action. You can learn more in our blog here: AI-powered defense for an AI-accelerated threat landscape 

[When this will happen:]

General Availability (Worldwide): We will begin rolling out on late April 2026 and expect to complete by late April 2026.

[How this will affect your organization:]

Customers should review the guidance captured in https://security.microsoft.com/securenow and take action to reduce their exposure in areas where autonomous AI‑driven attacks gain disproportionate advantage – patching, open-source software, customer source code, internet-facing assets, and baseline security hygiene. 

[What you need to do to prepare:]

Customers can review the guidance in Microsoft Security Exposure Management at https://security.microsoft.com/securenow and use the capabilities provided to take action.

[Introduction]

Update health builds on existing Cloud Update insights by adding clearer, more actionable diagnostics when an update does not complete successfully. Administrators see descriptive, easy‑to‑understand error messaging aligned with error codes, along with aggregated issue views across Cloud Update‑managed devices.

This message is associated with Microsoft 365 Roadmap ID 558249.

[When this will happen]

• Public Preview: Rollout beginning in April 2026 and is expected to complete by mid-May 2026.
• General Availability (Worldwide): Rollout will begin in late May 2026 and is expected to complete by late-May 2026.

[How this affects your organization]

Who is affected

• Microsoft 365 administrators managing Microsoft 365 Apps updates using Cloud Update
• Tenants with Cloud Update enabled in the Microsoft 365 Apps admin center

What will happen

• Admins will see aggregated views of update issues across Cloud Update–managed devices: 

  

• Update failures will surface descriptive error messages aligned with error codes: 

  

  Admins can drill into affected devices, review detailed issue information, and export device lists:

  

• Linked guidance is available to support troubleshooting and resolution.
• The feature is enabled by default for eligible tenants.
• There is no impact to users.
• No changes are made to existing update policies.

[What you can do to prepare]

• No action is required.
• To view Update health information, ensure Cloud Update is managing Microsoft 365 Apps updates for your devices.
• Review Update health in the Microsoft 365 Apps admin center.
• Review more information about upcoming changes to Cloud Update: New changes coming to Cloud Update

[Compliance considerations]

[Introduction]

Microsoft Teams is introducing enhanced recap sharing. Meeting organizers can grant access to meeting recordings, transcripts, AI-generated summaries, and notes when copying or sharing a recap link. This update improves how meeting content can be shared with people who were not part of the original meeting.

This message is associated with Microsoft 365 Roadmap ID 559606.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft Teams users who organize or attend meetings with recaps enabled.

What will happen:

• Meeting organizers can:
  • Grant access to the meeting recording, transcript, AI summary, and notes when copying or sharing a recap link.
  • Specify which people receive access at the time the recap link is shared.
• Meeting attendees who are not organizers can:
  • Copy or share recap links.
  • Recipients who were not in the meeting will be prompted to request access.
• The feature will be available by default.

To use this feature:

1. Select the Share menu in the top-right corner of the recap page or on the recap thumbnail in the meeting chat.

Screenshot 1: Recap page with Share menu highlighted:

>

Screenshot 2: Meeting chat with Share icon highlighted:



2. If the user is the meeting organizer: The user can specify people and copy or share the recap link while granting recap access to the specified people.

Screenshot 3: Share this recap options available to a meeting organizer:



If the user is not the organizer: The user can copy the recap link or share it by sending the link in a Teams chat. People who were not in the meeting will need to request access.

[What you can do to prepare:]

• No admin action is required.
• Inform users about the new sharing experience.
• Update internal documentation or helpdesk guidance if needed.

Learn more: Recap in Microsoft Teams | Microsoft Support (we will update the Share recap section before General Availability)

[Compliance considerations:]

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

[Introduction]

Meeting organizers in Microsoft Teams can now delete meeting‑generated content—including recordings, transcripts, AI summaries, and notes—directly from the meeting recap. This capability helps organizers manage meeting artifacts after the meeting. Shared files from the meeting are not deleted.

This message is associated with Microsoft 365 Roadmap ID 557170.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft Teams meeting organizers
• Tenants using meeting recap features

What will happen:

• A new Delete recap content option will appear in the More (…) menu on the meeting recap page.

Screenshot 1: Delete recap content option found under the More (…) menu:

>

Screenshot 2: Delete recap content confirmation:



• Meeting organizers can permanently delete:
  • Recordings
  • Transcripts
  • AI summary
  • Notes
• Shared files are not deleted and remain accessible in their original storage locations.
• Custom summary and Audio recap will not be deleted with Delete recap content in this release.
• Deleted meeting content cannot be restored.
• The feature is enabled by default and does not require admin configuration.

[What you can do to prepare:]

• Inform users about this new capability.
• Update internal documentation and helpdesk guidance.
• Review meeting governance and retention guidance.
• Monitor usage through Teams and SharePoint analytics.

[Compliance considerations:]

Meeting organizers can now permanently delete meeting-generated content, impacting how users manage and delete their data. Review as appropriate for your organization.

[Introduction]

To strengthen customer control over sensitive investigation data, Microsoft is extending Customer-managed key (CMK) protection to Microsoft Purview eDiscovery Direct Export. For tenants that have configured Data Encryption Policies (DEPs) using the Microsoft 365 Data-at-Rest Encryption Platform (MDEP), eDiscovery export packages will now be automatically encrypted using your organization’s CMK. This helps ensure exported investigation data remains protected under customer-controlled encryption policies throughout the export lifecycle, without changing the existing eDiscovery user experience.

This message is associated with Microsoft 365 Roadmap ID 557684.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft 365 tenants with Customer-managed keys enabled through Data Encryption Policies (DEPs), and request that Microsoft Support enable this feature for Purview eDiscovery Direct Export in their tenant
• Admins and investigators using Microsoft Purview eDiscovery Direct Export

What will happen:

• eDiscovery Direct Export packages for CMK‑enabled tenants will be encrypted at rest using tenant‑owned keys.
• Encryption is applied automatically based on existing DEP configuration.
• CMK configuration is dynamically validated through MDEP at export time.
• No change to the eDiscovery user experience.
• Only enabled for specific tenants by request to Microsoft Support 

[What you can do to prepare:]

To use CMK encryption for eDiscovery Direct Export, your organization must complete the following steps:

1. Configure Customer Key (self-service) Your Microsoft 365 administrator must have Customer Key enabled through the Microsoft 365 Data-at-Rest Encryption Platform (MDEP) with a DEP in PolicyAssigned status.
• This requires:
  • Two Azure subscriptions dedicated to Customer Key
  • Azure Key Vault(s) with RSA keys provisioned
  • A DEP created and assigned to your tenant
  • Follow the setup guidance here: Create two new Azure subscriptions | Microsoft Learn
2. Request feature enablement (contact Microsoft Support)
   • After Customer Key is configured, your organization must contact Microsoft Support to request that CMK for eDiscovery Direct Export be enabled for your tenant. This feature requires Microsoft-side service configuration that is not automatically applied. Work with your Microsoft Support contact or Customer Success Account Manager (CSAM) to complete enablement.

Important:

• If your tenant does not have CMK properly configured through MDEP at export time, direct export jobs will proceed without CMK encryption.
• No changes to the eDiscovery user experience are required — CMK encryption is applied transparently to export packages.
• Encryption scopes, storage accounts, and containers are managed automatically by the service; no additional storage configuration is needed.
• Exported data retention remains 14 days, unchanged by CMK.

Learn more: Export search results in eDiscovery | Microsoft Learn

[Compliance considerations:]

• Enhanced template discovery with views: Sellers can quickly filter templates, such as My templates, Team templates, or Approved templates, to find the best fit for each step.
• In-flow template creation and editing: Email templates can now be created or updated directly within the Sequence flow, making them instantly available and eliminating the need to switch contexts.

• Optimized storage: Reclaim capacity from inactive sandbox environments automatically, with no manual effort.
• Reduced governance overhead: You no longer need to manually identify and remove unused sandbox environments.
• Consistent lifecycle policy: Aligns sandbox environments with Developer and Default environment cleanup behavior already in place.
• Recoverable by default: Deleted environments can be restored for up to 7 days from PPAC.

• Automatic deletion of Power Platform environments
• Recover a deleted environment
• Sandbox environments

• Automatic deletion of Power Platform environments
• Recover a deleted environment

• Create multi‑branch research journeys across Dynamics 365 Sales data and Microsoft Fabric lakehouse data and analyze local files such as Excel and PDF.
• Start quickly with AI‑suggested, role‑optimized research topics, or ask your own questions using natural language.
• Use the AI cursor to start conversations, analyze findings, adjust visualizations, or add new data sources.
• View the reasoning behind research outcomes to understand how insights were derived.
• Save research workspaces, refresh them with new data, and regenerate blueprints or research findings as your business evolves.
• Define custom business functions with your own schemas, acronyms, and domain context to tailor analysis to your organization.

[Introduction]

We are introducing recipient groups for eSignature in Microsoft 365. Recipient groups allow a single recipient slot to be assigned to multiple people, where the first person to sign fulfills the signing requirement. This update helps make signature workflows more reliable by reducing delays when a specific signer is unavailable, without changing existing tenant policies.

This message is associated with Microsoft 365 Roadmap ID 560822.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users who create eSignature requests in Microsoft Word
• Microsoft 365 tenants that use eSignature for Microsoft 365

What will happen

• Users can assign up to 10 people to a single recipient slot: 

  

• The first person in the recipient group to sign fulfills the signing requirement for the group.
• Signature workflows are less likely to stall due to individual signer availability.
• The feature is enabled by default and respects existing tenant policies.

[What you can do to prepare]

• No action is required from admins.
• Consider informing users who rely on eSignature workflows about this improvement.

[Compliance considerations]

[Introduction]

Microsoft is introducing a Copilot account switcher in the Copilot side pane in the new Outlook for Windows. The account switcher shows the active Copilot‑enabled account and allows users to change the Copilot account used in the side pane in supported experiences.

This message is associated with Microsoft 365 Roadmap ID 559991.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users in Microsoft 365 tenants using the new Outlook for Windows
• Only users with multiple Copilot-enabled accounts configured in Outlook

What will happen

• Users will see a new account selector at the top of the Copilot side pane in supported experiences.
• The selector shows the currently active Copilot-enabled account.
• The account selector appears only when multiple Copilot-enabled accounts are available and the account context may be ambiguous (for example, certain Calendar experiences).
• Users will be able to switch Copilot accounts within the Copilot side pane without changing Outlook’s broader account context.
• If you are using Mail, you will not see the Copilot account switcher. 
• There is no impact for users with a single Copilot-enabled account.
• The feature is enabled by default and respects existing Copilot availability and licensing.
• The Copilot account switcher is available to users with Microsoft 365 Copilot (Premium) and Copilot Chat (Basic).
• This is a multi-account feature and requires at least two Copilot-enabled accounts, in any combination of Premium and/or Basic.

[What you can do to prepare]

No action is required.

To prepare for user questions, we recommend that administrators:

• Update internal documentation for Copilot usage in multi-account scenarios.
• Inform users who work across multiple accounts how to confirm or change the active Copilot account in the Copilot side pane.
• Update helpdesk guidance for users who have multiple Outlook accounts configured.

[Compliance considerations]

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

[Introduction]

We are introducing a unified Apps experience for SharePoint Embedded in the SharePoint admin center. This update simplifies app creation, and installation by centralizing the app lifecycle and reducing dependency on Global administrators. SharePoint Embedded administrators can manage apps, ownership, and billing from a single location, streamlining setup and ongoing administration.

With this experience, administrators can create and install SharePoint Embedded apps directly from the SharePoint admin center and then share the Microsoft Entra app ID and SharePoint Embedded app ID (also known as the container type ID) with developers for ongoing development and management.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Administrators responsible for managing SharePoint Embedded in the SharePoint admin center.
• Organizations using or planning to use SharePoint Embedded apps.

What will happen:

• A new Apps page will appear under SharePoint Embedded in the SharePoint admin center.
• Administrators can create and install SharePoint Embedded apps directly from the SharePoint admin center, without requiring Global admin consent.
• Administrators will have a centralized view to manage SharePoint Embedded apps, including:
• Installed apps: SharePoint Embedded apps currently installed in your organization, including apps developed internally or by external organizations.
• Owned apps: All SharePoint Embedded apps created by your organization, regardless of installation status.
• From this experience, administrators can:
• Create a new Microsoft Entra app or attach an existing Entra app during SharePoint Embedded app creation.
• Assign up to three owners to manage app settings and billing.
• Configure billing based on organizational deployment needs.
• When creating an app, administrators must select a billing type. This setting is permanent and cannot be changed after creation:
• User org: Billing is managed by the user organization. An admin in the user organization must configure pay‑as‑you‑go billing for SharePoint Embedded in the Microsoft 365 admin center.
• Owner org: Billing is managed by the app owner’s Microsoft 365 subscription.
• If Owner org billing is selected:
• Billing can be configured immediately by linking a subscription, or it can be set up later.
• Apps remain inactive until billing is configured.

[What you can do to prepare:]

• Ensure administrators responsible for SharePoint Embedded app management have the SharePoint Embedded Administrator role.
• If using Owner org billing, confirm that administrators have access to an appropriate billing subscription.
• Review internal guidance for developers on how to obtain the Microsoft Entra app ID and SharePoint Embedded app ID from admins.

No user action is required.

[Compliance considerations:]

The change introduces a new admin experience in the SharePoint admin center for creating and managing SharePoint Embedded apps.