Currently, Microsoft Partners access Dynamics 365 and other Power Apps administrative and development features through the Partner Centre > Customer > Service Management area. This allows Partner Developers to make changes in Dynamics or PowerApps as "Delegated Admin", equivalent to a global administrator, so that the client organisation does not need to buy additional licences for Microsoft partner developers not in their company.
On the whole this process works well, as it means that it is much easier to audit who is making changes to systems and the client company does not need to worry about managing these accounts. This is Microsoft's recommended practice for carrying out development work with a Microsoft Partner.

But when invited to a Teams team, shared planner, or having folders in SharePoint shared to the developer, for the purposes of project management and communication, suddenly the process above Completely breaks for the Power Platform. Through troubleshooting, we discovered that because the developer is added to the tenant as a Guest User - the Power Apps admin portal and Dynamics 365 will preference the permissions of the guest user (which is none) over the delegated admin granted by the Partner Centre. All Power Platform services become inacessible. Other services such as Exchange, M365, SharePoint and Teams admin centres honour the administrator permissions, but Power Platform will not load any environments and does not recognise the account as a global administrator. The only workaround is to remove the user from the guest users, which also removes access to the Team or other shared resources. This means Partner developers now need to choose between being able to effectively communicate with the client company team, or actually being able to do work on the Power Platform.

I reported this issue to Microsoft via support and the dev team has responded that the login process is working as designed, despite other services like SharePoint and Exchange having completely different behaviour.
The suggested work around was to use multiple accounts and buy more licences for these accounts, or to buy and assign licences to the guest user account, shifting the burden for this behaviour inconsistency onto Microsoft customers, which I do not find to be an acceptable solution. The whole idea of the partner centre is so that I do not need a seperate identity in every single clients tenant, and so that when there are multiple developers, engaging Microsoft assistance in development requirements does not place an additional financial burden on the customer. Support suggested I raise this as an idea to get it changed so that the power platform login for partners is not horribly crippled by Guest User access.

So here is my idea: Please change the Login Process for Power Platform to honour Partner Centre Administrative permissions above guest user permissions so I can actually login as a partner when i exist as a guest user, bringing the behaviour into line with all other Microsoft services.
Needs Votes