Update Principal owner of a SharePoint Embedded user-owned container through SPAC and PowerShell

SharePoint Embedded will allow admins to update the principal owner of user-owned containers via the SharePoint Admin Center or PowerShell starting late September 2025. This helps manage ownership during user or team changes, requires no opt-in on SPAC, and needs PowerShell updates. No compliance issues noted.

Introduction

To improve administrative control and support organizational transitions, SharePoint Embedded now allows administrators to update the principal owner of user-owned containers directly through the SharePoint Admin Center (SPAC) or via SharePoint PowerShell cmdlets. This update addresses common scenarios such as user departures or team restructuring.

When this will happen:

General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late October 2025.

How this affects your organization:

  • Who is affected: SharePoint administrators managing user-owned containers in SharePoint Embedded.
  • What will happen:
    • Admins will be able to update the principal owner of user-owned containers via SPAC or PowerShell.
    • This capability is limited to user-owned containers only.
    • The update helps maintain continuity and access control when users leave or teams change.
    • No changes will be made to existing containers unless action is taken by an admin.
    • The feature will be available by default on SPAC; no opt-in required.
    • The feature will not be readily available by default on PowerShell. The admin has to update it to the latest version. 

What you can do to prepare:

  • Review user-owned containers that may need ownership updates.
  • Use SPAC to select a container and update the principal owner via the General tab.
  • Alternatively, use the updated SharePoint PowerShell cmdlets to perform the same action. Ensure your SharePoint PowerShell module is updated to the latest version.
  • Communicate this change to helpdesk or support teams.
  • Update internal documentation if ownership management is referenced.

Compliance considerations:

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

Message ID: MC1152315


Comments are closed.


I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.

%d bloggers like this: