Unanswered

Change environment owner - orphaned environments

(0) Share

Report

Posted on by trash_panda

Hi,

we have noticed that we have several orphaned environments, whose creators (owners) have already left the company. The environments are still used - is there possibility to change the environment owner to someone else? Is there possibility to have maybe also a co-owners?

It would be nice also for another case - when I am creating an environment on someone's request and the person should be the real environment owner and admin, it would be cool to be able to make him the owner. (Our users don't have permissions to create environments themselves)

I am talking about sandbox and production environments also with Dataverse.

I can see only the possibility to add administrative privilege to someone. But this does not mark him as owner. How is the process or will the environment maker (possibly non-existing user) be assigned as environment owner forever? 🙂

Categories:

Governance & administering

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Jeff_Thorpe 6,085 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

The Power Platform Admin should be able to go into the security roles of the environment and add the new owners to the System Administrator Role.

Was this reply helpful? Yes No
RKushner 127 on at

Like (0)

Report
Copy link

Link copied!

There are several System Administrators, but the Environment still shows up as an Orphan (no owner) in the Center of Excellence.

Was this reply helpful? Yes No
jukka-niiranen 351 on at

Like (0)

Report
Copy link

Link copied!

Power Platform environments don't really have an owner. If you look at the environment object that the Power Platform for Admins connector returns, there is only information about "created by" and "modified by". So, any place that tries to show ownership info (like CoE Starter Kit) is only projecting it from the attributes available in the platform and "pretending" that there is an owner.

This is similar to how there isn't an owner for model-driven Power Apps either. Yeah, the Maker portal list of apps has the "owner" column since canvas apps have the ownership concept. Yet the model-driven apps are based on the XRM model where individual solution components like apps don't have an owner in their metadata. Canvas apps, flows and the other more recent elements introduced on Power Platform behave differently.

A "Power Platform environment" with Dataverse is essentially the same construct as what a Dynamics CRM Online instance was back in the days. Some of these environments will have therefore existed in the MS cloud for over a decade - without a specific owner. Maybe one day MS will enhance the built-in properties that can be defined for environments, although I haven't seen such a thing in the roadmap yet.

Was this reply helpful? Yes No
brandolph86 27 on at

Like (1)

Report
Copy link

Link copied!

The "Created By" is important, though, as Microsoft sends notifications on issues to that person.

Power Pages Web Authentication Key Renewal notification goes to the App Owner and is cc'd to the Created By on the environment. The App owner is no longer working on Power Apps and missed the email, and the environment creator is no longer with the company, so we missed it completely and our Power Pages site went down when it expired.

If I can change the Environment "Created By" or "owner", then those CC emails go to the right user or distribution list.

Is there a way to do this?

Thanks!

Was this reply helpful? Yes No