Can't connect to DevOps.

(2) Share

Report

Posted on by JoBox

112

Hi All,

My customer invited me to their LCS and DevOps for some customization.
However, I can't connect to their DevOps in Visual Studio.

The message shows:
TF30063: You are not authorized to access dev.azure.com/xxxxxxxx

Can someone share which permissions my account needs to be added to?

Many thanks.

I have the same question (0)

All responses (14)

Answers (1)

Suggested answer

Komi Siabi 13,093 Most Valuable Professional on at

Like (1)

Report

Hello,

You should try to access dev.azure.com/xxxxxxxx on the web. If all work well, then the issue should be from Visual studio. So, the question would be , what version of VS are you connecting from?

I found some article were the error you got it caused by VS and not access on dev.azure.

https://developercommunity.visualstudio.com/t/vs30063-you-are-not-authorized-to-access-httpsdeva-2/1532255

https://stackoverflow.com/questions/55317539/tf30063you-are-not-authorized-to-access-dev-azure-com-but-i-can-connect

Was this reply helpful? Yes No
Layan Jwei 8,097 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

I feel this is a bug in visual studio, it always happens with me where i need to repeat the steps more than once sometimes

Right click on the link where you showed us a red arrow, then click disconnect. Then click on manage connections and sign to devOps again by putting ur email and password then click connect

Was this reply helpful? Yes No
Layan Jwei 8,097 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Is your issue fixed? if yes, then please verify the answers that helped

Was this reply helpful? Yes No
Suggested answer

Bill Ngo 372 on at

Like (0)

Report

Hi Jobox,

Your customer needs to grant your priviledge as Basic, otherwise you can't connect to their DevOps in Visual Studio.

Was this reply helpful? Yes No
Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

Just note that the access level (such as Basic) means a license, not a security privilege. You need both a license and permissions.

Personally, I would follow Komi's advice and try it through the portal first, because that can tell you more than just "can't connect". For example, maybe you'll be able to connect but you won't see repositories, which will give a better idea what to look at.

Was this reply helpful? Yes No
Verified answer

JoBox 112 on at

Like (2)

Report

Komi Siabi & Layan Jwei, thanks for your information.

After reviewing these information, I solved the DevOps connection issue by following these three steps:

Step1: Remove/Disconnect the existing incorrect DevOps connection.

Step2: Re-enter my credentials (Files\Account Settings...).

Step3: Restarting Visual Studio and connecting to Azure DevOps again.

Was this reply helpful? Yes No
Komi Siabi 13,093 Most Valuable Professional on at

Like (0)

Report

Congrats JoBox,

Please, mark the answer(s) that helped.

Was this reply helpful? Yes No
Bill Ngo 372 on at

Like (0)

Report

Hi Martin,

Cc JoBox, Komi

If you not grant your priviledge as Basic, maybe you can connect DevOps to VS but I am sure you could not Get Latest Version of source codes from the Source Control Explore. And offcourse you cannot deploy your codes to DevOps too.

Please consider!!!

Was this reply helpful? Yes No
Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

It's not true. The Basic license allows you to use version control repositories. You likely mean the Stakeholder license, which doesn't have access to code (and therefore stakeholders don't see repositories in the web portal nor can use them in any other way)

And permissions are another thing. For example, even you have a license that allows you to commit code to a repository (or delete test plans or anything else), it doesn't mean that project administrators give you permissions to do so.

Was this reply helpful? Yes No
JoBox 112 on at

Like (0)

Report

Hi,

My customer has granted me "VS Enterprise subscription" privileges.
was able to connect to DevOps and get the latest version of the source control from Source Control Explorer.

Was this reply helpful? Yes No