I may be leaving the company I am with soon, and I'd prefer to be able to change ownership of the application to another developer. They have "Can Edit", but I'd just be more comfortable doing so.
The current forum recommendation is to contact support.
A UI change to the portal to allow the change of ownership, similar to Microsoft Flow's ability to add multiple owners, would be a great option.
You can use the PowerApps for Admins connector and use the Set App Owner Operations to change the owner. https://docs.microsoft.com/en-us/connectors/powerappsforadmins/
Multiple owners or group will be good and the ability for the owner to share with other owners instead of tenant level admin will be good for big organisation like us as tenant admin will not cope with the valume of apps spawn anticipated when we officially roll out O365.
Can we have have the option to grant owner permission to a SharePoint group? That way we only manage the permission in 1 source if the powerapps datasource is store in SharePoint. That will definately help with staff offboarding process.
Are there any instructions on actually using this feature?
Wait a minute... how do you do this through the UI? The link provided talks about a connector... all we simply want to do is click somewhere in PowerApps, select a new owner (preferably multiple owners!!!), and then click OK.
How does a connector help in this scenario?
The original request specifically states "A UI change to the portal to allow the change of ownership, similar to Microsoft Flow's ability to add multiple owners, would be a great option." Yes I know you can set a "co-owner" through the UI, but unfortunately, co-owners "...can use, edit, share app but not delete or change owner."
If no UI change has been done, how can this be marked as "Completed"?!
(And if we get told again that "sorry, you have to create a new post and be explicit about what you want", even though this post explicitly states that a UI change was requested, it proves that this whole forum process for requesting the bleeding obvious is not working)
Shocker! Microsoft releases a feature that doesn't meet the actual request. PowerShell it is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.