Churning when loading tenants/subscriptions for multiple accounts

[bwateratmsft]

Possibly related to #1227, or at least a similar cause

When loading tenants/subs for several accounts--especially e.g. 3+ of them--the extension seems to start churning. I suspect that our subscription discovery is causing session changed events, which are restarting the discovery process.

I have seen users with 3 accounts whose subscriptions took several minutes to load (up to 15 minutes).

[bwateratmsft]

Might be an issue in the auth package too.

[bwateratmsft]

Possibly same as/related to #1250. The user I saw was also on Mac.

[ziesemer]

Seeing the same myself, and the "Azure Tools" extension pack in VS Code is effectively unusable for my primary account as such. I have not tried using this prior to today, so I don't know if I just came in at the worst possible time against a current bug, or if this has been an ongoing issue.

I have multiple tenants, and many subscriptions in my primary tenant - and I'm sure that is contributing to the issues here.

This is exactly why az login has a --tenant option.

Visual Studio, for 5+ years, has an a "Individual tenant filtering" feature, along with an option to deselect "Authenticate across all Azure Active Directories on sign-in": https://devblogs.microsoft.com/visualstudio/improving-the-authentication-experience-for-enterprises-leveraging-conditional-access-policies/#individual-tenant-filtering . A similar feature is much needed here.

Even if the "Azure: Sign in to Tenant (Directory)..." command would work. However, it seems to only allow a drop-down selection of tenants from accounts already logged-in to. I can't even get that far on my primary account to get this command to load.

I'm reading through other current and prior issues logged here., and hoping to find a way I can preconfigure a user or workspace-level setting to restrict my login to only a particular tenant.