Unable to log into azure code repo, keep getting "403 - Uh-oh, you do not have access." error

Question

Hi,

I'm trying to login to my company's code repo, but keep getting a "403 - Uh-oh, you do not have access." error even after being added to the project. We are not sure why I cannot access it. I've tried an incognito window in my browser and it still does not work. Any help would be greatly appreciated!

Update: We've found my access level is stakeholder when it should be basic, how do we change the access level? Thanks!

Answer 1

The 403 - Uh-oh, you do not have access error typically indicates that your access level does not support access to the requested service or feature. Here are some steps you can take to troubleshoot this issue:

1. Verify Your Access Level: Ensure that your access level supports the service or feature you are trying to access. You can check your access level and subscription status.
2. Check Security Group Membership: Make sure that your membership within a security group supports access to the feature. If you were explicitly denied permission, that could also be the cause.
3. Refresh Permissions: If you were recently granted permission, your client might need a refresh to recognize the changes. Try refreshing or reevaluating your permissions.
4. Role Assignment: If you are trying to access a feature that is restricted to team administrators, ensure that you have been granted that role.
5. Preview Features: Check if you need to enable a preview feature that is required for access.

If you have gone through these steps and still cannot access the repository, consider contacting your project administrator or support for further assistance.

---

References:

• Common access and permission issues
• Work with GitHub

Answer 2

I’ve seen this a lot in Azure DevOps, and the 403 usually means you were added to the project, but not to the organization. DevOps requires both.

Here’s what normally fixes it:

Have an admin go to Organization Settings → Users and make sure your account is actually listed there.

If you aren’t in the organization user list, DevOps will block you with a 403 even if you were added to the repo or project.

After you’re added at the org level, refresh your browser or sign in again and the repo access should work immediately.

If your company uses AAD / Entra ID security groups, make sure the group is assigned at the organization level, not just the project.

That’s the usual root cause.