My work account is a guest/member of an old Entra tenant created with an msn account

Steve Reschke 0 Reputation points
2026-07-02T14:22:24.5633333+00:00

My work account is a guest/member of an old Entra tenant. Visual Studio attempts to authenticate against that tenant and receives AADSTS50076. I cannot leave the tenant because authentication to that tenant is broken, and the original personal account is no longer accepted because the tenant now requires a work or school account. I need either the guest membership removed or the tenant's authentication repaired.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Julie Huynh 1,530 Reputation points Independent Advisor
    2026-07-03T10:14:44.85+00:00

    Dear @Steve Reschke,

    Good day! Welcome to Microsoft Q&A forum!

    Based on your description, I understand that your work account is associated with an old Microsoft Entra tenant that was originally created using a personal account. Visual Studio is attempting to authenticate against that tenant and encountering the AADSTS50076 error. You can no longer access the tenant using either your work account or the original personal account, which prevents you from leaving the tenant or managing the account association. You're seeking assistance with removing the guest/member relationship or restoring access to the tenant so the issue can be resolved.

    To help determine the correct resolution path, could you please confirm whether your account is a Guest user or an Owner/Administrator of the old tenant?

    • If your account is a Guest user, I recommend contacting the IT administrator or support team responsible for that tenant. Guest accounts can only be managed by administrators within the tenant, and they would be in the best position to review your membership and remove the account if needed.
    • If you are the owner or administrator of the tenant, and you're unable to access the tenant because authentication is no longer working, I recommend creating a support ticket. The support team can review the tenant access issue and advise on the available recovery options.

    Once I know your role in the tenant, I'll be better able to guide you toward the most appropriate next steps. I appreciate your patience and look forward to your update.

    If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-07-02T14:22:39.0233333+00:00

    The situation matches a broken guest relationship with a Microsoft Entra B2B collaboration tenant and an app (Visual Studio) trying to authenticate against the wrong or unusable tenant.

    From the available guidance, there are only two viable paths:

    1. Have an admin in the old tenant remove or fix the guest account
      The tenant that owns the directory where the work account is a guest must perform the cleanup:
      • A tenant admin signs in to the Microsoft Entra admin center for that old tenant.
      • Go to Identity → Users → All users.
      • Locate the affected work account (it will appear as a guest user).
      • Either:
        • Delete the guest user from the tenant, or
        • Open Authentication methods for that user and select Require re‑register MFA to repair a stuck MFA profile (this is the same pattern used when a guest/personal account’s MFA is broken).
      Once the guest account is deleted, Visual Studio will no longer be able to authenticate that work account against the old tenant. If MFA is simply stuck and is reset, sign‑in should succeed and the user can then leave the organization via the My Account portal.
    2. Filter out the problematic tenant in Visual Studio so it stops using it
      Visual Studio can be configured to ignore specific tenants:
      • In Visual Studio, open File → Account Settings… → Account options.
      • Either:
        • Clear Authenticate across all Azure Active Directories to only use the default tenant for the work account, or
        • Click Apply filter, then in Filter account deselect the old tenant so it is filtered out.
      After filtering out that tenant, Visual Studio will stop attempting to authenticate against it and will only use the remaining tenants associated with the work account.

    If the user can still sign in to the old tenant via any account, they can also manage organizations directly from the My Account portal and leave that organization there, but this requires at least one successful sign‑in to that tenant.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.