Azure devops login

Azure devops login DEFAULT

DevOps has paved the way for faster and more agile software development processes by unifying teams, processes, and technologies to create an ever-evolving software development lifecycle (SDLC). This has led to more robust and efficient SDLCs, now capable of handling any user request, market demand, or technological issue.

A range of tools is available in the market to facilitate DevOps, such as CI/CD tools, version control systems, artifact repositories, IaC tools, and monitoring tools. With the increased demand for cloud-based technologies, DevOps tools have also transitioned to cloud offerings. These cloud offerings can be used by teams spread across the world with nearly unlimited scalability and efficiency.

In this article, we will explore such a cloud-based DevOps service offered by Microsoft called Azure DevOps.

(Explore our DevOps Guide, a series of articles & tutorials.)

Azure Devops 5 Services

What is Azure DevOps?

Azure DevOps is a service offered by Microsoft based on the Azure cloud computing platform that provides a complete set of tools to manage software development projects. It consists of:

  • Five key services
  • An extensive marketplace that contains extensions to further extend the Azure DevOps platform and integrate with third-party services

Azure DevOps core services

Core Azure DevOps services include:

  1. Azure Boards
  2. Azure Pipeline
  3. Azure Repos
  4. Azure Test Plans
  5. Azure Artifacts

Azure DevOps comes in two variants:

  • The cloud-based Azure DevOps service
  • The Azure DevOps Server

The Azure DevOps Server, previously known as the Team Foundation Server (TFS), is a DevOps server solution that is targeted for on-premise deployments. It consists of all the tools available in the cloud-based Azure DevOps service to power any DevOps pipeline.

This also server offers a free variant called Azure DevOps Server Express, aimed at individual developers and small teams of up to five team members. Itcan be installed in any environment.

Azure guarantees 99.9% availability for all the paid DevOps services including paid user-based extensions. Moreover, it provides 99.9% availability to execute load testing and build and deploy operations in paid Azure Test Plans (Load Testing Service) and Azure Pipelines.

Azure DevOps: Pricing

The cost will be one of the primary concerns when considering any DevOps solution.

The cloud-based Azure DevOps services come as both free and paid options. Additionally, the service offerings are provided in two varieties as individual services and complete service bundles.

Azure DevOps Comparing Services & Pricing

In addition to the above, there are special pricing options for open-source projects and Visual Studio subscribers to get free access to the Azure DevOps services depending on the subscription level.

(Visit the Azure DevOps pricing page for details & up-to-date pricing.)

Azure DevOps: Registration

Registering for Azure DevOps is a simple and straightforward process that requires only a Microsoft account. Simply visit this page and click on “Start for free.”

When registering, you will need to provide some additional information such as organization name, project name, version control type (repo), etc.

  • Organization refers to the Azure DevOps account name. The organization can contain multiple projects.
  • Projects allow users to separate projects, control access, and split the code, tests, and pipelines to keep them within the assigned projects. A project can be either public or private, with Git or Team Foundation server as the version controlling system. Additionally, projects can be configured with a work item process like Agile or Scrum that will be used in Azure Boards to manage the project.

Once the registration is complete, you will gain a dedicated organization URL in the following notation:

https://<organization name>

Users can manage all their projects and use the DevOps services by visiting this URL.

Azure DevOps Services

Azure DevOps consists of five services—which we’ll explore in this section. All these services can be grouped under individual projects so that users can have proper isolation between different projects using different technologies and catering to different needs.

Project summary view:

Azure DevOps Project summary view

Azure Boards

The Boards service in Azure DevOps is the management hub of the project.

Boards can be used to plan, track, and collaborate between team members. With Azure, the Boards team can create Work items, Kanban boards, backlogs, dashboards, and custom reports to track all aspects of the project.

You can also customize boards to suit the exact workflow requirements and gain meaningful insights through built-in reporting and monitoring tools. Additionally, Azure Boards comes with first-party integrations with services like Microsoft Teams and Slack, which enables efficient ChatOps.

Azure Repos

The Azure Repos are code repositories that enable users to manage their codebases. These are private and cloud-based repositories that support both Git and TFVC version control systems.

Azure DevOps Repos

Azure Repos can support projects of any scale, from individual hobby projects to enterprise developments. They also consist of the following features:

  • Support for any Git client (IDE, Text Editor, CLI)
  • Semantic code search
  • Collaboration tools to interact with other team members
  • Direct integration with CI/CD tools
  • Branch Policies to enforce code quality standards

Platform-agnostic services like Azure allows repo users to use any IDE or tool they are familiar with to interact with the Azure Repos in any operating system.

Azure Pipelines

Pipelines are the CI/CD tool that facilitates automated building, testing, and deployment. Azure Pipelines supports any programming language or platform which enables users to create pipelines that support Windows, Linux, and macOS using cloud-hosted agents.

Azure DevOps Pipeline

These pipelines are easily extensible through the extensions available in the marketplace. Besides, they support advanced workflows that can be used to facilitate:

  • Multi-phase builds
  • Test integrations
  • Custom reporting functions

On top of that, Azure Pipelines provide native container support, enabling them to push containers to container registries from the pipeline directly. The pipelines offer flexibility to deploy to multiple environments from Kubernetes clusters to serverless functions and even deploy to other cloud providers such as AWS or GCP.

Azure Test Plans

Test Plans is the Azure DevOps service that allows users to integrate a cloud-based testing platform to manage all the testing requirements such as:

  • Planned manual testing
  • User acceptance testing (UAT)
  • Exploratory testing
  • Gathering feedback from stakeholders

Azure Test Plans allow users to create test plans and execute test cases within a pipeline. This can be combined with Azure Boards to create a test that can be executed from the Kanban boards and plan and author tests collaboratively.

Test Plans support creating UAT plans for user acceptance testing and assign users from the DevOps platforms. It also supports the Test and Feedback browser extension to easily enable exploratory testing for interested parties without utilizing third-party tools. Furthermore, Test Plans enable users to test on any platform while having end-to-end traceability and powerful data gathering tools to diagnose any remedy identified issues.

It is the only service in Azure DevOps with no free tier due to its rich toolset that is only accessible for commercial users.

Azure Artifacts

This is the artifact library service by Azure DevOps that can be used to create, store, and share packages (development artifacts). Azure Artifacts enable users to integrate fully featured package management functionality to CI/CD pipelines.

Moreover, Azure Artifacts enable users to manage all package types like npm, Maven, etc., and keep them organized in a central library scoped only to the specific project.

Azure offers cloud-based DevOps services

Azure DevOps is one of the leading cloud-based DevOps services that offer a robust and feature-rich toolset to create and manage a complete DevOps process. It enables users to:

  1. Cater to any DevOps need regardless of the programming language, technology, or the targeted platform.
  2. Deploy anywhere from containers to third-party clouds.

Azure DevOps facilitates all these with unparalleled scalability and availability without the hassle of maintaining specific software to carry out separate DevOps tasks.

Related reading

These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

See an error or have a suggestion? Please let us know by emailing [email protected]


How to use Zendesk- Azure DevOps Integration App?

In order to use the DevOps integration app Zendesk - Azure DevOps app on Zendesk respectively user need to create the Azure DevOps personal access token and Zendesk API access token in order to use the integration app.

Follow below article steps to create the new Azure DevOps personal access token

How to create Azure DevOps authentication token

Follow below article steps to get the Zendesk API access token

How to generate Zendesk API token key

Follow below article steps to install the Zendesk Azure DevOps app

Zendesk - Azure DevOps Integration app Installation guide

Follow below steps on how to use the Zendesk - Azure DevOps integration app

1. Login to your Zendesk account with your login credentials

2 Create a new ticket in Zendesk or go to any existing ticket.

3. You will see the Zendesk - Azure DevOps Integration app on the right side of your ticket.

4. In the Zendesk - Azure DevOps integration app there are certain options we are providing.

a. Create New Work Item

    b. Link Work Item.

    c. Notify Linked Work Items.

    d. Work Item Log

    e. Configure App

    f. Unlink Work Item.

About Zendesk - Azure DevOps Integration App:

Zendesk - Azure DevOps Integration App simple integration between Zendesk and Azure DevOps. Suppor agents using this app can Create, link, notify Azure DevOps work items. You can Collaborate your support team and developers at one place.

Zendesk-Azure DevOps app allows the support agents to create Azure DevOps work items from Zendesk apps form. Zendesk-Azure DevOps app also allows support agents to link existing Zendesk tickets to an existing Azure DevOps work items. In addition, Zendesk-Azure DevOps app allows support agents to help notify the Azure DevOps team, by sending comments from Zendesk support. 

We also support customization based on customer request and tailored to your needs! We bring Azure DevOps closer to your business requirements!

The Zendesk-Azure DevOps app provides couple of options like Create Work Item, Link Work Item, Notify, Work Item Log & Configure App

Create Work Item

    The Create Work Item lets the user to create new work item # in Azure DevOps from Zendesk, support agent can select type of work item he/she want to create like Bug, Epic, Feature, Task, User Story etc. Based on the work item type selection he will see all the Azure DevOps fields. The User can make the selection and click on Create button which would create work item in Azure DevOps and then display the corresponding Azure DevOps work item Id in the App.   

Link Work Item:  

    Using this button in Zendesk-DevOps app support agent can link an existing Azure DevOps Workitem # to current Zendesk ticket. Zendesk-Azure DevOps app allows the user to create or link multiple work items to one Zendesk ticket. 


    Notify button in Zendesk-Azure DevOps app allows the support agent to notify all the linked Azure DevOps work items to current Zendesk ticket these will show up as comments in Azure DevOps. 

Work Item Log:

    In the Zendesk-Azure DevOps app Work Item log modal shows you couple of details of work item history including the comments history to current Zendesk ticket.  

Configure App

    This will help to map certain fields between Zendesk and Azure DevOps.

The Zendesk - Azure DevOps Integration app is limited to few Projects in free version.

  1. Attack on titan gas
  2. Samsung self clean instructions
  3. Project zomboid multiplayer
  4. Audi a6 usa price
  5. Ucla health medical group

Sign in with a personal access token (PAT)

Sign in with a Personal Access Token (PAT), Azure DevOps CLI

Azure DevOps

Use a Personal Access Token (PAT) with Azure DevOps CLI







>= azure-devops-2020


[!INCLUDE temp]

You can sign in using an Azure DevOps personal access token (PAT). To create a PAT, see Use personal access tokens.

To use a PAT with the Azure DevOps CLI, use one of these options:

User prompted to use az devops login

You're prompted to enter a PAT after you run the command:

$az devops login --organization Token:

If you have already signed in with interactively or if you're using a user name and password, you're not required to provide a token because the commands now support sign-in through . However, you can't sign in as the service principal via . In that scenario, a PAT is required.

When you're successfully signed in, this command also can set your default organization to Contoso, provided no default organization is configured.

Pipe PAT on StdIn to az devops login

From a variable

This option is useful in pipelines in which can be replaced by or another pipeline variable:

echo"######"| az devops login --organization

From a file

cat my_pat_token.txt | az devops login --organization

Use the AZURE_DEVOPS_EXT_PAT environment variable

To gain access in a non-interactive manner for automation scenarios, you can use environment variables or fetch a PAT from a file.

If or haven't been used, all commands will try to sign in using a PAT stored in the environment variable.

To use a PAT, set the environment variable at the process level.


# set environment variable for current process$env:AZURE_DEVOPS_EXT_PAT='xxxxxxxxxx'
macOS and Linux
export AZURE_DEVOPS_EXT_PAT=xxxxxxxxxx

Replace xxxxxxxxxx with your PAT.


Azure DevOps (VSTS) setup

Below is a step-by-step guide on how to connect your Microsoft Azure DevOps to Flow.

Before you get started

Before you get started, please make sure that your system is supported. You are supported if:

  • You use git repos (TFVC repos are not supported and are not expected to be supported)

In this article

Permission requirements

To use all integration services such as repos, pull requests, tickets and webhooks, two conditions must be met. First, please review the personal access token scopes outlined below. And second, the service account needs to be a Project Collection Administrator at the organizational level. 

If webhooks are not needed, the permission required to establish a connection and import repos is View instance-level information at the user level, and the user needs to be added to the reader group at the project level.

Azure DevOps configuration

  1.  In order to connect your Azure DevOps account, you will need to first create a new integration. Starting on your Flow home page, go to the top navigation bar and click Settings. Using the left navigation under Integrations, click Integrations.
  2. Click the Add Integration button in the top right hand corner of your integrations screen.

  3. On the following page click Azure DevOps

  4.  On this page you will need to input the following information:

    • Email - Email associated with the service account.

    Tip: This field is case sensitive. Use the exact email format seen in your Azure user profile.

    • Personal Access Token (see below)
    • Base URL -{yourorganization} 

    Tip: Even if your base URL in Azure Devops uses the domain, you will need to use the domain in the "Base URL" field in Flow for the connection to be successful.

Creating a personal access token

To create a personal access token in Azure DevOps follow the instructions below. 

  1.  Locate Personal access tokens under your user settings.
  2. On the Personal access token page click New Token.

  3. Fill in the following information for your new personal access token:

    • Name
    • Organization 
    • Expiration date
    • Scopes - Below find the minimum scopes required to connect your account.
      • Code: Read
      • Build: Read
      • Graph: Read
      • Identity: Read
      • Project and Team: Read
      • Work Items: Read
  4. Click Save.

Finalizing the connection

Now that you have created a personal access token you can complete your integration setup in Flow.

  1. Copy your access token and paste it into the Flow Personal Access Token field. 
  2. Click Test connection.

  3. If the connection was successful you will see the following message:

    If you receive an “Authorization denied” error when trying to connect your Azure DevOps account verify access token and try again.

    If you receive “An error has occurred” error verify that the email and base URL are correct and try again. 

  4. Once you have successfully connected to your Azure DevOps account, click Next.

  5. On the next screen you will be selecting the services you want turned on for this integration. If you would like to import pull request and ticket data in addition to repo data, then leave all services on. You can turn services “on” and “off” at any time. Click Next.

    Note: Azure DevOps Work Items are generally mapped to Tickets in Flow.

  6. Name your integration so you can identify the account you connected with. Click Create.

  7. You have successfully created a new Azure Devops integration.

  8. You can begin to import your repos by going to your repo import page. Click the repo import page link. To learn more about managing your new Integration settings, see Manage integrations.


If you are unable to get your integration setup or connected, please see the following guidance: 

  1. If your Integration does not test successfully:

Upon receipt the following error message when testing your integration connection, please review the following information. 

  • Check to make sure your email address is the same case and spelling as seen in your Azure Profile. The email field is case sensitive.

  1. If you’re unable to enable Webhooks
    If your projects appear in your Webhooks tab, but nothing happens when you click enable next to a repo, this could indicate that your Azure user permissions are not sufficient. In order to enable webhooks, you must be a Project Collection Administrator. 

back to top

If you need help, please email [email protected] for 24/7 assistance.


Devops login azure

Sign up, sign in to Azure DevOps

Azure DevOps Services

Learn how to sign up for Azure DevOps for free. Also, sign in with a Microsoft or GitHub account, create an organization or project, and invite your teammates.

Sign up for Azure DevOps to upload and share code in free, unlimited private Git repositories.

Then, connect to your favorite development tool like Eclipse, Xcode, Visual Studio, IntelliJ, or Android Studio to work on apps anytime, anywhere.

Sign up with a personal Microsoft account

  1. Select the sign-up link for Azure DevOps.

  2. Enter your email address, phone number, or Skype ID for your Microsoft account. If you're a Visual Studio subscriber and you get Azure DevOps as a benefit, use the Microsoft account associated with your subscription. Select Next.

    Sign in with your Microsoft account

    If you don't have a Microsoft account, choose Create one. To learn more, see create a Microsoft account.

  3. Enter your password and select Sign in.

    Enter your password and sign in

  4. To get started with Azure DevOps, select Continue.

    Choose Continue to sign up for Azure DevOps

An organization is created based on the account you used to sign in. Sign in to your organization at any time, ().

You can rename and delete your organization, or change the organization location. To learn more, see the following articles:

If you signed in with an existing Microsoft account, your next step is to Create a project. If you signed in with a newly created Microsoft account, then your project is automatically created and named after your account name. To learn more about managing projects, see Manage projects.

Sign up with a GitHub account


If your GitHub email address is associated with an Azure AD-backed organization in Azure DevOps, you can't sign in with your GitHub account, rather you must sign in with your Azure AD account.

  1. Select the sign-up link for Azure DevOps, Start free with GitHub. If you're already part of an Azure DevOps organization, select Sign in to Azure DevOps.

    Sign up for Azure DevOps

  2. Select Sign in with GitHub.

    Select Sign in with GitHub

    If you have an account in session already, select Use another account. You're taken to GitHub sign-in where you can enter your GitHub user name or email address.

  3. Enter your GitHub account credentials, and then select Sign in.

    Enter GitHub credentials

  4. Select Authorize Microsoft corporation.

    Authorize Microsoft

  5. To get started with Azure DevOps, select Continue.

    Choose Continue to sign up for Azure DevOps

An organization is created based on the account you used to sign in. Sign in to your organization at any time, ().

You can rename and delete your organization, or change the organization location. To learn more, see Manage organizations.

Enable GitHub invitations

Creating a new Azure DevOps organization with your GitHub username turns on the Invite GitHub users policy by default. For existing organizations, your administrator can turn on this capability via Organization settings > Policies tab.

Once the setting is changed, sign out of Azure DevOps, and then from a fresh browser session, sign back in to the organization or with your GitHub credentials. You're now recognized as a GitHub user and the GitHub invitation experience is available to you.

Invite GitHub users policy

For more information about GitHub authentication, see FAQs.

Create a project

If you signed up for Azure DevOps with a newly created Microsoft account (MSA), your project is automatically created and named based on your sign-in.

If you signed up for Azure DevOps with an existing MSA or GitHub identity, you're automatically prompted to create a project. You can create either a public or private project. To learn more about public projects, see What is a public project?.

  1. Enter information into the form provided, which includes a project name, description, visibility selection, initial source control type, and work item process.

    Create project form ready for completion

    See choosing the right version control for your project and choose a process for guidance.

  2. When your project is complete, the welcome page appears.

    Project creation confirmation dialog, new nav

Invite team members

Give team members access to your organization by adding their email addresses or GitHub usernames to your organization. For GitHub user invitations, ensure you've enabled the policy, Invite GitHub users in Organization settings > Policies tab.

  1. Sign in to your organization ().

  2. Select Organization settingsOrganization settings.

    Open Organization settings

  3. Select Users > Add new users.

    Select Add users

  4. Enter the following information:

    • Users: Enter the email addresses (Microsoft accounts) or GitHub usernames for the users. You can add several email addresses by separating them with a semicolon (;). An email address appears in red when it's accepted.
    • Access level: Leave the access level as Basic for users who will contribute to the code base. To learn more, see About access levels.
    • Add to project: Select the project you want to add them to.
    • DevOps Groups: Leave as Project Contributors, the default security group for users who will contribute to your project. To learn more, see Default permissions and access assignments.
  5. When you're done, select Add to complete your invitation.

For more information about managing users and organization access, see Add organization users for Azure DevOps.

Choose your content version

This content supports a platform/version selector. Select from the Content version selector dropdown, located above the table of contents, to access the content that's specific to your version. The table of contents and content page refresh to show only that content specific to the selected version.

Documentation version selector

Next steps

Oque é o Azure DevOps - Guia para Iniciantes

Azure DevOps

GitKraken allows you to connect to Azure DevOps (formerly VSTS), which will help you find repos on Azure DevOps when cloning.


  • Create repositories on Azure DevOps account including .gitignore and license
  • Automatically generate an SSH key pair and copy it to Azure DevOps
  • Clone from Azure DevOps repo list
  • Identify Azure DevOps repos with remote avatars on graph
  • Add remotes for Azure DevOps repos
  • Create and view Pull Requests

Azure DevOps Authentication

To authenticate with Azure DevOps, navigate to the upper right corner to access

Or alternatively if you are in the view, click on under Customize.

From the Authentication window, enter your Host Domain then click the

This opens a web browser where you next log in with your Azure DevOps credentials and generate an access token.

Copy your token to the clipboard as this is the only time you will see this token. Paste the token into GitKraken and click on .

Generating an SSH Key for Azure DevOps

GitKraken uses your local SSH Config from SSH Defaults to fetch and push unless you set up a Azure DevOps-specific SSH key, or enable your local SSH Agent.

Once your Azure DevOps account has been connected to GitKraken, you may easily generate an SSH key and add it to your Azure DevOps account from .

Click the magic button and add the key to your Azure DevOps account.

OAuth integration with Azure DevOps

GitKraken's integration with Azure DevOps provides handy information about your repositories.

First, you may search through your existing repositories when cloning:

Next, GitKraken presents a list of forks of the current repository when adding remotes:

Of course, you still have the option of manually entering repo URLs.

Connecting to multiple Azure DevOps accounts

GitKraken connects to one Azure DevOps account at a time. However, with GitKraken Pro's multiple profile support, you can easily switch between profiles that each have their own associated Azure DevOps accounts.

Training resources

Share these resources with your team to explain why collaborating with GitKraken is easier, and to get everyone up and running with Azure DevOps and GitKraken quickly.


Similar news:

Aha! Roadmaps | Integrate with Azure DevOps (integrations 2.0)

Successful products do not happen by accident. They are often the result of seamless collaboration between product and development teams. Developers need strategic context for their work. Product managers need progress updates to inform their roadmap.

But all too often, product managers have to use developer tools just to provide context and track updates — then manually update their own product plans elsewhere. They spend their days in multiple tools, trying to be the glue that brings strategic vision and successful go-to-markets together.

The integration between Aha! Roadmaps and Azure DevOps keeps product and development teams in their tools of choice — without sacrificing context or collaboration. Real-time, two-way updates mean that strategic and progress updates flow back and forth immediately. And you can customize the integration to match your team's workflow and terminology.

Features board with highlight on the integrations field and the Azure Devops integration

In this article, we will walk through how to configure and customize an integration with Azure DevOps Services or Server.

Click any of the following links to skip ahead:


Integration type

Aha! level

Required user permissions:

Required user permissions:
Use integration

Associated record types

  • Initiatives

  • Releases / Schedules

  • Epics

  • Features / Activities

  • Requirements


How to think about your integration

Aha! provides a two-way integration with Azure DevOps Services and Azure DevOps Server. This allows product teams to send their planned work from Aha! to their development team working in Azure DevOps.

Before configuring any integration for the first time, it is important to fully understand how to think about integrating Aha! with your development tool. Aha! should come first in the process —build out or import your records in Aha!, then send them to Azure DevOps. You can customize the ways that fields map to each other and sync record dependencies between the two tools, and even customize whether you want integrated records to update automatically, or only after your review.

Services or Server? The main difference between the two tools is this:

  • Azure DevOps Services (formerly known as Visual Studio Team Services, or VSTS) is a cloud-based solution that is available through a web browser or IDE client.

  • Azure DevOps Server (formerly known as Team Foundation Server, or TFS) is an on-premises offering.

This integration supports sending the following Aha! record types to Azure DevOps:

  • Initiatives

  • Releases / Schedules

  • Epics

  • Features / Activities

  • Requirements

The above Aha! record types can be mapped to any work item type in Azure DevOps, including both standard and sub-task types.


Configure your integration

To set up an integration with Azure DevOps, you need to be a workspace owner in Aha! for the workspace you wish to integrate. You will also need to have an Azure DevOps account that has proper access to create/edit records in the project you plan to integrate.

  1. Navigate to Settings ⚙️ → Workspace and press the + icon next to Integrations on the left side navigation bar. Depending on if you are integrating to the cloud or on-premise, select either Azure DevOps Services or Azure DevOps Server from the integrations 2.0 grouping.

  2. This will launch the integration configuration wizard. The first step is to name your integration and optionally select a template if you have already created one. Click Save and continue.

  3. Next, you will be prompted to authenticate with valid Azure DevOps Services or Azure DevOps Server credentials.

    For Azure DevOps Services:

    • You will need to create a personal access token within Azure DevOps Services.

    Note: The screenshot from the Azure DevOps knowledge base article has Custom defined selected. For Aha! purposes,you will need Project and team (read) and Work items (full) scopes.

    • Back in Aha! Roadmaps, you need to enter the subdomain of your Azure DevOps Services account. This will be the "mycompany" part of the access URL.

    Note: Your Azure DevOps Services URL will be in one of two formats: or

    Next, enter the personal access token that was created.

    For Azure DevOps Server:

    • You will need to enter the server URL for your Azure DevOps Server account. Be sure to enter the entire server URL, including the collection part of the path with no trailing slash. For example, the following URL would be a valid entry:

    Next, enter the username and password that you use to login to your Azure DevOps Server account. If you are using a personal access token, enter that as the password. The username field should be ignored.

  4. After authenticating, you will be prompted to choose a project and an area. Both of these lists are based on what your user has available to them in Azure DevOps.

  5. Next comes record mappings. This step allows you to configure how Aha! records are mapped to your Azure DevOps records. The default mappings are based on what is most widely used across our customers. However, you are free to remove the default mappings and add your own to map records together based on what makes sense for your team and how you work.

    Azure Devops integration configuration on the Mappings step
  6. Within record mappings, you have the option to also specify your field mappings. This is an advanced option within the configuration that allows you to customize how each field within the record is mapped between Aha! and Azure DevOps — as well as what relationship links exist for those records.

    Note: If you have configured required fields in Azure DevOps, we recommend setting the Required flag on those fields in the custom layout associated with your Aha! workspace. This will ensure that any required fields are populated when records are created on the Aha! record creation form.

    The relationship links are important to understand because they allow records created in your development system to be automatically imported into Aha! in certain use cases.

  7. While not every user will need to customize their field mapping, you do need to define the way statuses are mapped. Within the field mapping section for each Aha! record, there is a line for Status with a gear ⚙️ icon at the far right. Click the gear ⚙️ icon to open up the status mapping window.

    Azure devops integration with status mapping configuration modal open
  8. When mapping statuses, you will be presented with your Aha! status workflow for the record type on the left and your integrated system status workflow on the right. Matching values will map automatically. You can then manually rearrange statuses to your preferred mappings as needed. Drag and drop statuses on top of each other to create groupings, or drag them into different orders to rearrange. Click Done when you are ready to move on.

    In the above screenshot, you can see that multiple statuses have been grouped together where the Aha! Roadmaps status of Under consideration has mapped to the Azure statuses of Doing, Done, and To Do.

  9. With your records, optional field mappings, and statuses defined, you can click Save and continue to move onto the last step in the workflow. The Enable step allows you to specify how updates from Aha! are sent to your development system. To start with, you should choose to Approve outgoing changes. We recommend this option until the team is familiar with how the integration works, at which point you can choose to send changes automatically. The approval step allows teams that are new to the integration to validate what is being sent to their development system, which can help prevent unintentional changes from going through.

    Note: If a feature's parent release is not linked with Aha! Roadmaps, or if releases are not mapped with the development system at all, then the feature will be imported into the first parking lot release. This is by design, since the parking lots are repositories for unscheduled work.


Set up webhooks for two-way sync

All sections of your integration configuration have been set. However, if you set any mappings to sync from Azure DevOps to Aha!, you will need to set up webhooks in Azure DevOps so that Aha! can receive updates. Each integration you add will require two webhooks to be added to Azure DevOps — one for creating items, and one for updating them — regardless of whether the project already has an Aha! webhook configured.

Work item created webhook

  1. In Aha!, copy the webhook URL from the Enable step of the integration configuration.

  2. In your Azure DevOps account, go to the project you want to integrate.

  3. Click the Project settings button in the bottom left and select the Service hooks page.

  4. Add a new service hook by clicking the + Create subscription button.

  5. Scroll to the option for the Web Hooks service and click Next.

  6. Under Trigger on this type of event, choose the Work item created trigger from the dropdown menu. To reduce unnecessary webhooks, add filters for the specific area, item type, or tags that you plan to integrate with Aha! Click Next.

  7. On the Action page, under Settings, paste the webhook URL from Aha! into the URL field. You can leave the option fields unchanged and click Finish to create the subscription.

Work item updated webhook

  1. In Aha!, copy the webhook URL from the Enable step of the integration configuration.

  2. In your Azure DevOps account, go to the project you want to integrate.

  3. Click the Project settings button in the bottom left and select the Service hooks page.

  4. Add a new service hook by clicking the + Create subscription button.

  5. Scroll to the option for the Web Hooks service and click Next.

  6. Under Trigger on this type of event, choose the Work item updated trigger from the dropdown menu.

    1. To reduce unnecessary webhooks, add filters for the specific area, item type, or tags that you plan to integrate with Aha! Roadmaps.

    2. Make sure that Links are added or removed is not checked.

    3. Click Next.

  7. On the Action page, under Settings, paste the webhook URL from Aha! into the URL field. You can leave the option fields unchanged and click Finish to create the subscription.


Add additional security (Azure DevOps Server)

2.0 integrations with on-premises tools have the option to include a client certificate for added integration security.

To set a client certificate, open your Azure DevOps Server integration settings and click the More options icon in the upper right, then click Set client certificate. From here, enter the private key and certificate — we recommend creating a private key and client certificate specifically for this purpose — and click Save to save your changes.

If you use an integration template to manage multiple integrations in the same workspace, set the client certificate in your integration template. That way, you only need to set the client certificate once.

Note: This feature will only provide additional security when the server that Aha! is communicating with validates the certificate. This is usually only possible with customer-configured on-premises integrations. Client certificate authentication is in addition to the standard username and password/token authentication and is not a replacement.


Test your integration

Congratulations! You're ready to test your new integration. To do this, send a feature to Azure DevOps by following these steps:

  1. Navigate to Features → Board.

  2. Open one of your features in Aha!, scroll to the Integrations field, and select Send to Azure DevOps Services or Send to Azure DevOps Server. You should see a link to the created Azure DevOps record appear on the Aha! feature after a few seconds. This will let you easily click into Azure DevOps to verify that everything was sent through correctly.

Note: You also have the ability of manually bulk sending a subset of features to Azure DevOps.


Manage your integration

If you have multiple Azure DevOps integrations that you need to manage, use the Manage integrations report, located in:

  • Settings ⚙️ → Account → Integrations for account-level integrations.

  • Settings ⚙️ → Workspace → Integrations for workspace-level integrations.

If you run into difficulties with your Azure DevOps integration, you can find answers to common problems in the Azure DevOps section of the knowledge base.

Otherwise, if you run into any trouble with the integration process, please reach out to our Customer Success team. They are all product experts, and respond very quickly.


Note: On September 10, 2018, Microsoft renamed Visual Studio Team Services (VSTS) to Azure DevOps Services. As part of this change, the URL convention changed from to Microsoft supports redirection from URLs, so there are no broken links with existing accounts. Additionally, the next version of Team Foundation Server (TFS) will be called Azure DevOps Server. Please reference this announcement from Microsoft for further detail.


4484 4485 4486 4487 4488