Forum Discussion
Sign in to Azure DevOps
The https://dev.azure.com URL redirects to the landing page for the Azure DevOps product. I used to promote this as an URL to use to login to the product.
Since this year the page is missing the "Already have an account? Sing in to Azure DevOps" link.
As far as I can see there is no way to login to Azure DevOps trough this interface now.
There is the usual "sing in" in the top right, which will redirect you to the azure portal (or at least for me it does).
How are we supposed to login to Azure DevOps?
Old login:
- The expected flow for logging in to Azure DevOps is by visiting the organization directly: https://dev.azure.com/<organization>.
In case you're looking for a way to log in first and see the organizations you have access to later, you can try logging in to https://aex.dev.azure.com/. This gives you an overview of all the organizations you have access to as well as options to leave organizations or create new ones.
16 Replies
Thanks for posting this. After reading through the discussion, the community provided a clear solution that addresses the exact problem you're facing.
The Core Issue
As you noted, going to https://dev.azure.com no longer shows a straightforward "Sign in" link. Instead, it redirects to a product landing page, and clicking "Sign in" in the top right takes you to the Azure portal – not what you want.
The Solution (From the Accepted Reply)
The community's solution, provided by user Rick and marked as accepted, is straightforward:
- Visit your organization directly: https://dev.azure.com/<your-organization-name>
- If you just want to see all organizations you have access to (without knowing the specific org name), use: https://aex.dev.azure.com/
The aex.dev.azure.com URL gives you an overview of all organizations you can access, plus options to leave organizations or create new ones. One community member also recommended https://msportals.io/ as a helpful reference for Azure landing page issues.
Community Frustration (Valid Points)
Several commenters expressed frustration with this design – and rightfully so. One user said: "This is not user friendly at all, having to go through a forum just to know how to sign in to DevOps." Another added: "I should be able to just type in https://dev.azure.com/ and get to where I need to go."
These are fair criticisms. Microsoft's current authentication flow is confusing, and forcing users to remember organization-specific URLs or discover aex.dev.azure.com through community forums is not ideal.
Quick Summary
What you want to do URL to use Access a specific Azure DevOps organization https://dev.azure.com/<org-name> See all organizations you have access to https://aex.dev.azure.com/ Product landing page (no direct login) https://dev.azure.com (avoid) How EaseCloud Can Help
If your team is spending too much time wrestling with Azure authentication, access management, or DevOps pipeline setup instead of actually building products, EaseCloud can help streamline your cloud and DevOps workflows:
- DevOps Consulting – Optimize your CI/CD pipelines and access patterns
- Cloud Strategy & Assessment – Evaluate whether your current Azure setup is working efficiently
- Azure Managed Services – Let us handle the operational overhead so your team stays productive
Thanks for posting this. After reading through the discussion, the community provided a clear solution that addresses the exact problem you're facing.
The Core Issue
As you noted, going to https://dev.azure.com no longer shows a straightforward "Sign in" link. Instead, it redirects to a product landing page, and clicking "Sign in" in the top right takes you to the Azure portal – not what you want.
The Solution (From the Accepted Reply)
The community's solution, provided by user Rick and marked as accepted, is straightforward:
- Visit your organization directly: https://dev.azure.com/<your-organization-name>
- If you just want to see all organizations you have access to (without knowing the specific org name), use: https://aex.dev.azure.com/
The aex.dev.azure.com URL gives you an overview of all organizations you can access, plus options to leave organizations or create new ones. One community member also recommended https://msportals.io/ as a helpful reference for Azure landing page issues.
Community Frustration (Valid Points)
Several commenters expressed frustration with this design – and rightfully so. One user said: "This is not user friendly at all, having to go through a forum just to know how to sign in to DevOps." Another added: "I should be able to just type in dev.azure.com and get to where I need to go."
These are fair criticisms. Microsoft's current authentication flow is confusing, and forcing users to remember organization-specific URLs or discover aex.dev.azure.com through community forums is not ideal.
Quick Summary
What you want to do URL to use Access a specific Azure DevOps organization https://dev.azure.com/<org-name> See all organizations you have access to https://aex.dev.azure.com/ Product landing page (no direct login) https://dev.azure.com (avoid) How EaseCloud Can Help
If your team is spending too much time wrestling with Azure authentication, access management, or DevOps pipeline setup instead of actually building products, EaseCloud can help streamline your cloud and DevOps workflows:
- DevOps Consulting – Optimize your CI/CD pipelines and access patterns
- Cloud Strategy & Assessment – Evaluate whether your current Azure setup is working efficiently
- Azure Managed Services – Let us handle the operational overhead so your team stays productive
You are what is wrong with is community
This is not user friendly at all, having to go through a forum just to know how to sign in to DevOps
I do not understand what kind of drugs the Azure people are on. Not only do you have to go through a forum to log into devops, you also have to try 14 different OTP tokens and 4 microsoft authenticator logins only to be stuck in the authentication loop of doom. I would really like to tell my teammates on teams that I will be running late because MS is being dumb, but my phone browser says it's not a supported platform and the teams app tells me "this is not possible yet" when I log in.
It must be that 80% of microsoft product users use them because of inertia. There is no other possible explanation for why you would be putting up with so much pain.
- rickvdbosch
Microsoft
The expected flow for logging in to Azure DevOps is by visiting the organization directly: https://dev.azure.com/<organization>.
In case you're looking for a way to log in first and see the organizations you have access to later, you can try logging in to https://aex.dev.azure.com/. This gives you an overview of all the organizations you have access to as well as options to leave organizations or create new ones....but why?
When I try to login with dev.azure.com I'm redirected to the azure portal, that -- AFAICS does not offer any link to devops. In other words: the landing page for devops does not lead to devops. Is this the intended path? Or am I missing something here?
I hate this. I should be able to just type in dev.azure.com and get to where I need to go. The fact that this currently after login is redirecting me to portal.azure.com (another resource entirely) is bad. It's too confusing all around. I should be able to go to dev.azure.com, login and see a list of the organizations available to me. Having to use the organization in the url is just plain annoying.
- Thanks Rick , also a good starting point for URL landingpage issues is: https://msportals.io/
they report: https://aex.dev.azure.com/me
