Illustration of a website ownership transfer, showing user profiles, security controls, and an activity log.
For years, the website owner of a Power Pages site was effectively stuck with it, a bit like the person who once signed for the office coffee machine lease. Microsoft's own admin-roles page put it plainly: the website owner is the user who created the Power Pages website, and while you can update website management roles, ownership remains with the creator and can't be transferred or changed. Roadmap item 577825, "Power Pages: Administration and governance – Enable self-service site ownership transfer," changes that. It is now marked as launched.

Here's what changed, who can actually use it, the steps to follow, and the catches to know about before you hand a production site to someone new.

Illustration of a website ownership transfer, showing user profiles, security controls, and an activity log. What Microsoft shipped​

The roadmap entry lists the feature as launched and enabled automatically for admins, makers and marketers. Public preview and general availability are both dated September 2026, in the Worldwide (Standard Multi-Tenant) cloud. The related Message Center post, MC1454011, lists Power Platform as the primary service, low admin and user impact, and a release start of 15 September 2026. Microsoft calls it an awareness-only update with no action required.

The roadmap describes more than a change to the owner field. There are four parts:

  • Self-service transfer: Existing site owners and global administrators can assign ownership to another valid user within the tenant without requiring manual intervention from support.
  • Audit history: Every ownership transfer is recorded in an auditable history, including the previous owner, new owner, initiating user, and timestamp.
  • Notifications and compliance logging: Notifications go to the previous owner, the new owner, and administrators, and the changes get logged into Compliance Center.
  • Ownerless-site detection: Power Pages also identifies sites that no longer have a valid owner and surfaces this information on Power Advisor, so administrators can take corrective action to ensure that every production site has a designated accountable owner.

Microsoft's Power Platform blog announcement says the same thing in plainer terms. Transfer activities capture the previous owner, the new owner, who initiated the transfer, and when it occurred, and relevant stakeholders (old owners, new owners, and relevant system administrators) are notified by email.

Section summary: This is a governance feature with four parts: transfer, audit, notification and orphan detection. It isn't just a new button.

"Self-service" doesn't mean any owner can do it​

The roadmap text says "existing site owners and global administrators." The Microsoft Learn procedure page, "Transfer ownership of a Power Pages site," is stricter. Before you start, you need all of the following:

  1. You're the website app owner and you hold one of these roles:
    • System administrator
    • Dynamics 365 administrator
    • Power Platform administrator
  2. You can access the Power Platform admin center.
  3. The new owner is an enabled Microsoft Entra user with the Member user type. Guest accounts don't qualify.

That list doesn't include Global Administrator. Don't assume a tenant Global Admin can finish the transfer unless they also meet the documented requirements.

The Learn page adds one more condition. Sites on the Power Platform managed identity model don't need web app ownership before you start a transfer. For other sites, if the transfer option is missing, check whether you're an owner of the site's Microsoft Entra app registration. Microsoft's older admin documentation explains how to add yourself: the app is called Portals-<<website name>>, and you select Owners under Manage, then Add owners.

How to transfer a Power Pages site, step by step​

According to Microsoft Learn, the whole procedure runs in the Power Platform admin center:

  1. Sign in to the Power Platform admin center.
  2. In the left pane, select Manage, then Power Pages.
  3. Select the site you want to update.
  4. On the Site Details page, select Edit.
  5. In the Owner field, remove the current owner and search for the new one.
  6. Select the new owner, then select Save.
  7. Read the confirmation message and select Transfer.

Success looks like this: the selected user becomes the site's primary owner. Microsoft tells admins to check that the new owner can actually access and manage the site. Don't treat the saved change as the finish line.

Troubleshooting and common pitfalls​

Symptom or riskLikely cause and fix
The transfer option doesn't appearYou may not own the site's Entra app registration (this doesn't apply to managed-identity sites). Add yourself as an app owner, or have an eligible admin do it.
You can't select the intended recipientThe person must be an enabled Entra Member user. Guests and disabled accounts don't qualify.
You picked the wrong personThere's no undo. An authorized administrator has to run another transfer back to the right user.
The former owner loses accessMicrosoft warns this can happen depending on the site's permissions and configuration. Grant access separately if they still need it.
Business records still show the old ownerInogic says site transfer does not change ownership of Dataverse records such as Accounts, Contacts, and Cases, so reassign these separately.

One practical tip: check that the recipient is eligible before an offboarding starts. If the outgoing owner's account is disabled first, the handover can turn into the support ticket this feature is meant to replace.

Section summary: Check eligibility first, transfer once, confirm afterwards, and remember that ownership of Dataverse records and other access are handled separately.

Finding the audit trail in Microsoft Purview​

The roadmap only says changes are logged to "Compliance Center." Microsoft's Learn page "View Power Pages activity logs in Microsoft Purview" gives the detail. Its activity table lists Transfer site ownership under the operation name OwnershipTransferred, described as the site's ownership moving to another user. That means auditors can search for one specific operation instead of scrolling through every website record update.

To search it:

  • Auditing has to be configured and turned on for the Power Platform production environments you want to monitor.
  • You need the Audit Logs or View-Only Audit Logs role in Microsoft Purview.
  • In the Purview portal, go to Solutions > Audit. Filter by date range and enter the operation name, or use keyword search.
  • Developers can also pull the same logs through the Office 365 Management API.

The same table has neighbouring events you may want in a governance dashboard, including SiteDeleted, SiteVisibilityUpdated, WAFDisabled and ConvertedToProduction. Put them together and you can see who owns a site and what they did with it.

Power Advisor: catching orphans before they cause problems​

Power Advisor already flags Power Pages problems. When Microsoft brought Power Pages recommendations to Power Advisor in 2024, the checks covered trial sites close to expiring, sites with no traffic in 30 days, and production sites without CDN or WAF. An ownerless-site signal fits in that list.

Be realistic about what's documented so far. The roadmap says Power Advisor will show sites without a valid owner. None of the documentation reviewed here describes where that recommendation appears, how to filter it, or which remediation button it offers. Microsoft's release-plan page also carries its usual warning that some functionality may not have shipped and timelines can change. If you don't see the signal in your tenant yet, it isn't necessarily misconfigured.

Analysis: why this matters​

The following is editorial analysis based on general industry experience, not Microsoft statements.

Orphaned assets are a common low-key governance failure in low-code platforms. An external portal built by a contractor or a departed project lead can keep serving customers for years with no accountable owner. The blog post makes the same point: the site itself often continues serving customers, partners, employees, citizens or other users for years. An unowned public-facing site is a real security and compliance problem.

The feature also has limits:

  • Narrow eligibility. Requiring an admin role means "self-service" really means self-service for admins. Owners who are only makers will still have to ask IT.
  • No rollback. A one-way transfer with only a manual reversal makes mistakes costly, so a second person should check the recipient for production sites.
  • Doc mismatch. The roadmap mentions "global administrators," but the procedure page lists a different set of roles. Go by the procedure page.

Bottom line: Add Power Pages ownership transfer to your offboarding and reorganization checklists. Set up a Purview alert or saved search on OwnershipTransferred, and watch Power Advisor for the ownerless-site signal as it reaches tenants. If you've been dealing with orphaned sites through support tickets, this is a real improvement.

 

References

  1. Power Pages: Administration and governance - Enable self-service site ownership transfer Microsoft 365 Roadmap 2026-10-22T23:45:49.708272Z
  2. Transfer Power Pages Site Ownership: Step-by-Step Guide inogic.com
  3. Enable self-service site ownership transfer | Microsoft Learn learn.microsoft.com