How do I transition from 1:1 mapping of authentication and authorization to simpler options?

I have never taken the following suggestion for fear of not knowing what would happen next. I don't know what would happen next, because I have multiple Microsoft accounts and access multiple SharePoints:

In a nutshell - How is this functionality supposed to work and what problem does it solve?  More specific concerns are below with additional questions which may be more helpful to any of you potentially answering this question.  Thanks in advance!


Usually, a Microsoft account is going to 1:1 with SharePoint sites, and there are never SharePoint sites which would require access by more than one of my Microsoft accounts.
Sometimes a Microsoft account is going to map 1:many where 1 Microsoft account maps to more than one SharePoint
Seldom 2 Microsoft accounts might need access to the same SharePoint.

For Example, I am an employee of Consult-o-rama, and the account referred to is Microsoft here in the dialog above is a login called Consult-o-Rama in my Consult-o-Rama vault dedicated to all things Consult-o-Rama.

Further, the SharePoint referred to here, is a SharePoint of a company which was a joint venture 30 years ago and with whom we have a close relationship. They have their own AD, but Microsoft federation is such that we are allowed to log into their sites separately using our same login as guests. Likewise, we can switch orgs in Teams and use their separate teams with the same credentials, as guests. 

My Consult-o-Rama login credential, which is a Microsoft account, is stored in 1password as a Login with URLs for all the sites I would use it for in the Consult-o-Rama vault. I also have a client vault which we can call Client 1.  Client 1 has dedicated logins for only Client 1.  But in my Consult-o-Rama vault, my Consult-o-Rama credential will have sites of both Consult-o-Rama resources, and only the SharePoint URL for the Client 1. 

With me so far?

Other background:

• I have 4-7 vaults depending on how many clients I have.  consult-o-rama, client 1, Client 2, Personal, and then Client <#> for however many clients I need to have them for, I sometimes have vaults for additional purposes.
• I use separate browser identities and have the 1password addon in the browser filtering only on the relevant vaults per browser identity (so in the Client 1 Edge profile, I have it filtering only for Consult-o-Rama and Client #1)
• The login credential record "Consult-o-Rama' is one of 5-10 microsoft account.  I log into at least that many SharePoints.  Some of the microsoft accounts are all in Consult-o-Rama. Client #2 and others will have other Microsoft Accounts.
• None of my login credential records are named Microsoft or SharePoint.

How can I best use the functionality I'm being prompted to use without doing the following?

• Creating duplicate records of login credentials.
• Being clear about mapping identities and being able to label "Microsoft" in this example instead as "Consult o Rama', and "SharePoint" instead as "consult-o-rama" SharePoint.  So that in the future I can map  1 to many and many to 1 logically and without confusion?

And if none of that is clear - How is this functionality actually supposed to work?

Thanks!