February 19, 2020 Azure DevOps Services authentication update

Microsoft has announced that Azure DevOps Services will no longer accept Alternate Credentials authentication beginning on March 2, 2020.

What is changing?

Azure DevOps Services is no longer supporting Alternate Credentials authentication for integrations. Aha! customers will now be required to create and enter a personal access token as part of an integration with Azure DevOps Services.

Who is affected?

Aha! customers who have integrations with Azure DevOps Services and use Alternate Credentials to authenticate their accounts. If you are already using a personal access token to authenticate with Azure DevOps, you do not need to update your integration.

Note: Integrations with Azure DevOps Server, which is the on-premises version, are not affected at this time.

When is this change happening?

Microsoft will begin disabling Alternate Credentials for all Azure DevOps organizations on March 2, 2020.

How do I update my integration?

First, you will need to create a personal access token within Azure DevOps Services.

Then navigate to Settings ⚙️ Workspace Integrations back in Aha! and select your Azure DevOps Services integration. Select Configure Account and enter the personal access token in the password field.

Note: If your Azure DevOps integration is active and working without a username, then the integration is already using a personal access token.

If you are using integration templates, you can update the template with a personal access token and it will automatically apply to all integrations based on that template. Any other integrations created with that template in the future will also include your personal access token.