MC1290827 - Create a line-of-business SharePoint Embedded app on SharePoint admin center

Message Center

Summary

Starting late June 2026, SharePoint admin center will offer a unified Apps page for creating and managing SharePoint Embedded apps without Global admin consent. Administrators can assign owners, configure billing, and manage apps centrally, streamlining app lifecycle and billing setup. No user action needed.

Last Updated

Jun 15, 2026

Published Apr 24, 2026

View version history

Service

SharePoint Online

Tag

Updated message
New feature
Admin impact

More information

Updated June 15, 2026: We have updated the timeline. Thank you for your patience. 

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 end of June 2026 (previously mid-May) and expect to complete by early July 2026 (previously late May).

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.

Version history

2 versions tracked

Updated 1 time since Apr 24, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Jun 15, 2026 · 04:57 PMLatest · v2

    Changed: Body, Tags, End date

  2. Apr 24, 2026 · 09:47 PMOriginal · v1

    Changed: Initial version