What’s happening here is that Azure DevOps ties organization ownership to the exact identity record in Azure AD/Microsoft Account, not just the alias. When you switched your primary email and then back again, the identity mapping may have become inconsistent, which explains why you can still access Azure Admin but get errors in DevOps.
The first step I recommend is to clear cached credentials and try signing in with the original primary email address that is listed as the organization owner. If that doesn’t work, check whether your DevOps organization is linked to an Azure AD tenant (Entra ID). Even if you don’t think it is, many organizations are automatically connected, and ownership is validated against that directory. If the owner identity is mismatched, you may need to re‑add yourself as an administrator from another valid owner account.
If you are the only listed owner and cannot sign in, the most reliable path forward is to open a support ticket with Azure DevOps Support. Provide them with your organization URL and proof of ownership, they can reassign the owner identity to your current primary email. In the meantime, you can also try adding your new email as an alternate organization administrator if you still have partial access.
I hope the response provided some helpful insight. If it clarified the issue for you, please consider marking it as Accept Answer so others with the same issue can find the solution.
Jason.