Share via

lost access to devops organization

landon harris 0 Reputation points
2026-04-28T01:33:26.3266667+00:00

I have a vscode extension published through a devops organization that I no longer have access to because I created the organization with a university email. The email has been deactivated so I no longer have access to the organization and can't update the extension on the vscode marketplace.

Is there a way to connect that organization with my current microsoft azure account? I have access to the github account, phone number associated with the old account, etc. for validation if required.

Azure DevOps

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pravallika KV 14,235 Reputation points Microsoft External Staff Moderator
    2026-04-28T01:39:25.0166667+00:00

    Hi @Landon Harrison ,

    Thanks for reaching out to Microsoft Q&A.

    It sounds like your DevOps organization has become “orphaned” now that the university email (and its Entra ID account) is gone. Because VS Code extensions’ publishers live inside an Azure DevOps org, you’ll need to reclaim ownership of that org (or have Microsoft move the publisher).

    Here’s what you can try:

    1. Verify the backing Azure AD tenant
      • Sign into the Azure portal and use the “Directory + subscription” filter to switch to the tenant where you originally created the DevOps org.
      • Browse to https://dev.azure.com/‹your-org›. If you see an “Orphaned organization” banner or an Unauthorized page, you’re in the right place.
    2. Claim ownership of the orphaned org
      • Make sure you have or can get a Global Administrator account in that Azure AD tenant and that the Azure DevOps Administrator role is assigned.
      • On the DevOps sign-in or in Organization settings you should see a “Claim ownership” (or “Change owner”) link. Click it, justify your request, and point it at your current work or school account.
      • Once you’ve claimed ownership, add your new account (and at least one other admin) to the Project Collection Administrators group so you don’t get locked out again.
    3. Update your VS Code extension
      • With your new account in the Org Admin group, head to the VS Code Marketplace publisher page, update the extension, bump versions, etc.
    4. If you can’t claim ownership yourself
      • Check whether any other Global Admin in that old tenant can perform the claim. If the entire tenant is gone (or University IT refuses), you’ll need to open a support ticket with Microsoft DevOps/Product Marketplace. Provide:
      • The name of your DevOps org and Azure AD tenant
      • Proof of extension ownership (GitHub repo, phone number on file, etc.)
      • Ask them to transfer the VS Code extension publisher to a new DevOps org under your current Microsoft account.

    Hope this helps!

    If the resolution was helpful, kindly take a moment to click on User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know.

  2. Q&A Assist
    2026-04-28T01:33:39.7766667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    There is no supported way to directly connect or merge an existing Azure DevOps organization that was created with a deactivated university account into a different Microsoft account.

    For Azure DevOps organizations, ownership and access are tied to the identity that created or was later set as the organization owner. To manage or change the organization owner, the current owner (or a Project Collection Administrator) must still be able to sign in. If that identity is no longer accessible and there are no active Project Collection Administrators, the only supported recovery path is via Azure DevOps support in specific “orphaned organization” scenarios where the owner and all Project Collection Administrators are inactive in the connected Microsoft Entra tenant.

    Relevant supported actions:

    1. If the organization is (or was) connected to Microsoft Entra ID and the original owner account still exists in that tenant (even if the email mailbox is gone), an Azure DevOps or Microsoft Entra administrator may be able to:
      • Restore or enable the user in Microsoft Entra ID, then
      • Sign in and change the organization owner to a current account, as described in “Change organization owner”.
    2. If the organization’s owner and all members of the Project Collection Administrators group are inactive in the connected Microsoft Entra tenant, Azure DevOps Administrators can claim ownership of the organization using the “Resolve inactive organization owner” process.
    3. If neither of the above applies (for example, the organization was created with a standalone Microsoft account tied to a university email that no longer exists and is not backed by a Microsoft Entra tenant), there is no documented mechanism to prove ownership using phone number, GitHub account, or other signals and then rebind the organization to a new account. In that case, the extension and organization are effectively orphaned from a supportability standpoint.

    Given the constraints in the documentation, the only viable path is:

    • Determine whether the organization is backed by a Microsoft Entra tenant and whether an admin in that tenant can help restore the original owner identity long enough to transfer ownership; and
    • If the owner and all Project Collection Administrators are inactive in the tenant, follow the documented “Resolve inactive organization owner” route via Azure DevOps Administrators.

    If neither condition is met, there is no supported way in the documentation to regain access or connect that organization to a different Microsoft account.

    References:

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.