But, ultimately, those licensing rules may be under MS's control as well. Even if they aren't, it sounds like it has a significant impact on their service's design and usability, so it's in their interest to make a change somewhere.
Just merge them into a single collection and have my experience be dictated by that merged collection. With how entrenched they are with the Enterprise world, they should have foreseen this scenario and designed their family of products to facilitate this seamless merging of authorization rules across disparate accounts.
Because user stories aren't: "I want to access my Office365 work account" or "I want to access my personal Microsoft account".
They're: "I want to edit or download a file I have access to in the Microsoft cloud" or "I want to find a file I have access to".
Gawd.. You're microsoft, you can create a whole new security protocol. Don't have this half baked persona solution.
If you can't figure this out, it really reinforces the reason for every time we come across something in Azure where we're like wtf isn't this feature supported?