Every Power Pages site has an owner. Most of the time nobody thinks about who that is, until the person who built the site changes teams, goes on a long leave, or leaves the company. Then someone asks a simple question: who is responsible for this portal now?

If the answer is “the person who left,” you have a problem waiting to happen. Nobody is accountable for the site, and changes, access requests and fixes have no clear home.

Below, you’ll see how to pass a Power Pages site to a new person from the Power Platform admin center. You’ll also see why that is only half of a proper handover, because the data connected to the site keeps its original owner.

In this guide – When you should transfer a site – What you need before you start – The five steps to transfer ownership – Site ownership vs. Dataverse record ownership – Who should own a site – What to check afterward – FAQs

When Should You Transfer Site Ownership?

Think of a company that runs a customer portal on Power Pages. Customers log in to raise service requests, track their cases and download documents. The person who set up that portal has been its owner from day one.

When that person moves on, the portal keeps running, but the ownership record still points to them. A site with no active owner is harder to manage and harder to audit. Teams that rely on Microsoft Power Platform Solutions for customer-facing portals usually treat this as part of their standard offboarding checklist, right next to license removal and mailbox handling.

These are the most common triggers:

• An employee leaves the organization
• The site owner moves to a different role or department
• A contractor or implementation partner finishes a project and hands the portal back to your team
• A restructuring changes who is responsible for customer-facing systems

If any of these apply to you, it’s time to transfer.

What You Need Before You Start

Check these three things first. Skipping them is the most common reason a transfer fails or stalls.

1. Your own permissions. To run the transfer, you must be the site’s current owner, and your account must also have admin rights through one of these roles: System Administrator, Dynamics 365 administrator, or Power Platform administrator.
2. Admin center access. The whole task happens in the Power Platform admin center, so confirm that you can log in before you begin.
3. An eligible new owner. The person taking over needs an active Microsoft Entra account, and the user type must be Member. Guest accounts are not accepted.

Microsoft documents these role requirements in its Power Pages admin roles article, and it is worth a quick read if your tenant has custom role setups.

How to Transfer Ownership: Step by Step

The whole process takes only a few minutes.

Step 1: Find your site list. Log in to the Power Platform admin center and choose Manage in the left navigation, then Power Pages. Every site in your environments is listed there.

Step 2: Choose the site. Click the site you want to pass on. Its Site Details page shows the main settings, including who owns it today.

Step 3: Open the edit panel. On the Site Details page, click Edit. A side panel opens with the owner setting.

Step 4: Swap the owner. Clear the name in the Owner field, then type the new person’s name and pick them from the list that appears.

Step 5: Save and confirm. Click Save. A message asks you to confirm the change. Read it, then click Transfer.

When the transfer finishes, have the new owner open the site and make sure they can actually manage it.

A transfer has no undo button

If the site went to the wrong person, or the timing was off, you can’t simply reverse it. A different authorized admin has to run another transfer to restore the earlier owner. Check the name carefully before you confirm.

Site Ownership vs. Dataverse Record Ownership

This is the part many teams miss.

A site transfer only changes who is responsible for the site. The data in Dataverse is left alone. Accounts, Contacts, Cases and similar records keep their current owners. Treat site ownership and record ownership as two separate jobs.

If the person leaving also owned records, plan a second step. You can use the Reassign Records option in the admin center, or edit ownership straight in Dataverse. Once that is done, confirm the new record owners are correct, and look for permissions, related records or workflows that relied on the old owner.

Microsoft explains this in its documentation on updating a record owner and owning business unit.

Who Should Own a Power Pages Site?

Choosing the new owner is a decision, not just a form field. A few practical points help her

Pick someone who will still be there. The best owner is a person with a stable role who understands the site and can answer questions about it. Handing a site to someone who is already planning to move on only brings you back to the same problem in a few months.

Think about the day-to-day work. The new owner will spend time in the admin center, so they need the right admin role and some familiarity with the site. If the portal gets regular updates, give it to someone who is involved in that work, rather than a name chosen only for seniority.

Keep a record. Write down who owns each site, why, and who the backup is. A simple shared list is enough. When the owner changes, update it the same day.

Plan for the next handover. Add “transfer Power Pages ownership” and “reassign Dataverse records” to your offboarding checklist, so the task is not left to someone’s memory.

If you manage several portals across environments, a short governance review can save a lot of confusion. Our Power Platform Consulting Services cover exactly this kind of ownership, access and environment planning.

What to Check After the Transfer

A short review right after the handover saves a lot of trouble later.

• Look at the Site Details page and make sure the new owner’s name shows up.
• Have the new owner sign in and try managing the site themselves.
• See whether the previous owner can still get in. If they no longer need access, remove it.
• Go through Dataverse records on their own and reassign anything still tied to the old owner.

If your organization has a formal process for handovers, add these four checks to it so they happen every time.

Wrapping Up

Transferring a Power Pages site is a simple admin task. The only real trap is forgetting that site ownership and Dataverse record ownership are handled separately. Do both, run the post-transfer checks, and your portal will have clear ownership with no loose ends.

If you are planning a new portal, or need an existing one extended or cleaned up, our Power Platform Development Services team at Vaden Consultancy works with Power Pages, Dataverse and Dynamics 365 every day.

To talk through your requirements, write to us at connect@vadenconsultancy.com.