Azure DevOps#

Setting up a repository on Azure DevOps is not always smooth sailing. There are many issues that can occur due to the Microsoft accounts associated with it. We strongly recommend NOT using Microsoft accounts from other services (e.g. GitHub) when using Azure DevOps. In our experience, this has led to a lot of authentication errors when creating or joining a Git repository.

I don’t have access to the Azure DevOps repository#

First, check that you can access the repository (with your user account) on the Azure DevOps website. If that’s not possible, try this solution. Sometimes there are problems with multiple Microsoft accounts.

Another issue could be permissions. Go to “Organization Settings” / “Users” and change your team member from “Basic” to “Stakeholder” so that they can read and edit data in the repository.

I am getting an access denied error#

Make sure that you have enabled “Third-party application access via OAuth”. To do that go to your Organization, click on “Organization Settings” / “Policies” and enable “Third-party application access via OAuth”.

Member cannot create Azure DevOps projects from Anchorpoint#

If a member is unable to create Azure DevOps projects through Anchorpoint, you’ll need to check their group permissions. Navigate to and click on “Project Collection Administrators,” followed by the “Members” tab. If the member is not listed here, they won’t have the necessary permissions to create DevOps projects either in Anchorpoint or directly in Azure DevOps. To resolve this, add the member to the “Project Collection Administrators” group.

Free member limit reached#

When attempting to invite a new member to your Anchorpoint workspace or a specific project, you may encounter an error message stating, “Cannot add member to Azure DevOps. You need to set up billing to invite more members.” This indicates that you’ve reached the free member limit for your Azure DevOps organization. To resolve this, navigate to and click on “Set up billing” to extend your member limit.

By following these troubleshooting steps, you can resolve common issues related to Azure DevOps integration and ensure a smoother collaboration experience within your Anchorpoint workspace.

Network configuration#

At times, Azure DevOps may experience malfunctions when accessed through the IPv6 network protocol. To address this issue, Anchorpoint offers a solution that involves modifying your network configuration to ensure that only Azure DevOps utilizes the IPv4 protocol. We do this by making adjustments to the hosts configuration file.

Alternatively, you have the option to completely disable IPv6 on your system. Follow the steps outlined in this guide to disable IPv6.

Member does not receive an Azure DevOps invite#

If a member reports that they haven’t received an invitation to join your Azure DevOps workspace, the first step is to verify the email address you used for the invitation. Make sure it matches the one the member provided. Next, navigate to to check if the member is listed under the “Basic” Access Level. If the member is not visible, you can invite them by clicking on “Add Members.” Make sure to set their Access Level to “Basic” to ensure they have the appropriate permissions.

I cannot logout from Azure DevOps to login with a new account#

Due to Microsoft’s account linking, it’s sometimes hard to fully logout. Here is a forum entry that describes how to solve that issue.

401 - Uh oh, you do not have access#

If this happens to you, even if you think you are logged in with the correct account take a look at this forum entry .

Alternative login solutions