But have each tuple listed still be isolated from the other, only domains listed together in a single list could share a cookie container.
If I decide I want, say, an Azure Portal container then I cannot have login.microsoftonline.com assigned to a different container -and- configured to automatically open in that container.
If I do that, I need to have a combined Azure + Office 365 + anything-I-need-to-authenticate-to-Azure-AD-for container.
It’s a good solution but with its lack of flexibility I find it’s too far in the direction of security versus convenience.
Maybe another way to think of it is like a one-to-many join. A domain would not "belong" to a single container, but have tags to associate with 1+ containers.
Could you explain how this could be beneficial to the user?