ℹ️ Requires a Professional or Team plan
Microsoft Azure DevOps is an alternative to GitHub, allowing you to store files in a Git repository in the cloud. This integration allows you to create new repositories and add members directly from Anchorpoint, so you don’t need to use the Azure web interface.
Every members needs to have an Azure DevOps account
All members need to be in the same Azure DevOps organization
If you have more than 5 members, make sure you subscribed to enough licenses on Azure DevOps
Open the Workspace Settings / Integrations and search for the Azure DevOps integration. Then click on Connect. Anchorpoint will open the web browser so you can log into Azure DevOps.
Follow the instructions in Anchorpoint.
Pick your organization
Login to Azure from Anchorpoint
Check OAuth policies
If the integration is active, you can create Git repositories directly from Anchorpoint. To do this, create a project in Anchorpoint and select the “Git Repository” option. Under Remote Settings, then select “New Azure DevOps Repository”. In the next step, add the members. These members will also be added to the project on Azure DevOps.
Your members will receive two emails. One from Azure DevOps and one from Anchorpoint. First, they need to open the Azure DevOps email, accept the invite and create an account on DevOps. Then they need to open Anchorpoint to access the project.
If you remove a project on Anchorpoint, it is not automatically removed from Azure DevOps. You have to remove it manually there.
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 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 https://dev.azure.com/YOUR-ORGANIZATION/_settings/members 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.
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 https://dev.azure.com/YOUR-ORGANIZATION/_settings/groups 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.
Azure DevOps 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 https://dev.azure.com/YOUR-ORGANIZATION/_settings/billing 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.
Azure DevOps 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.
Could not store credentials#
Git was unable to verify your credentials for Azure DevOps. To fix this, try one of these things:
A) Reauthenticate on Azure DevOps
Visit your Azure DevOps organization’s page at https://dev.azure.com/YOUR-ORGANIZATION
Log out of your account
Log back in to reauthenticate
B) Resolve Account Conflicts
It might be that you have two accounts using the same email address.
You can try to fix this or
Create a new account with a different email
C) Create unique credentials for your project on Azure DevOps
Go to your project page on Azure DevOps and click on “Repos” in the left sidebar.
Click the “Clone” button
Select “Generate Git Credentials”
Use the new credentials within Anchorpoint when joining the project
D) Do not use linked accounts (e.g. GitHub)
We have seen people experiencing issues when logging into Azure DevOps with a linked Microsoft account (e.g. GitHub, Skype, Office). If you have done this, create a new Microsoft account and log in with it. Also, make sure you sign in to your Azure DevOps organisation with the new account first.
If you have troubles with that, you can look at this solution