E-mail owners, add owners, transfer flows and apps – and the messages you may see

How the governance actions work, what they need, and what each error means.

E-mail the owners (Teams, groups & sites)

Select inactive teams, groups or sites → E-mail owners. One e-mail per workspace goes to all its active owners from the mailbox you enter (a shared mailbox such as it-team@contoso.com works well). Use the placeholders {name}, {url}, {type}, {lastActivity}, {days} and {owners}; the preview shows the first e-mail. Workspaces without an active owner are skipped – add an owner first.

Add owners

Select teams or groups → Add owners → enter one or more people. They are added as owners and members (team owners must be members). People who don't exist or are disabled are refused before anything changes.

Orphaned flows and apps

Select them → Assign new owner:

Power Apps: Transfer ownership makes the person the owner (the previous owner keeps edit rights), or Add as co-owner.
Flows: the person is added as an owner – a flow's creator can't be changed. The new owner should open the flow and fix connections that used the old account.

Every action is listed under Actions log with its result.

Messages

Message	Fix
The app may not read usage reports – add … Reports.Read.All	Add the Graph application permission `Reports.Read.All`, grant consent, run again. Owners are still checked meanwhile.
The usage reports hide user, group and site names	Clear Display concealed user, group, and site names – see set up.
… Add the Microsoft Graph application permission Mail.Send	Add `Mail.Send` (application), grant consent. The sender must be a mailbox in the tenant.
… Group.ReadWrite.All	Needed to add owners.
Power Platform refused the app (403). Register the app registration as a Power Platform management application	Run `pac admin application register --application-id <client ID>` once.
No user … in this tenant / … is disabled	Check the address; the new owner must be an enabled user.

Was this article helpful?

Updated 2026-10-26