Connect Azure DevOps to Rovo

Quickly retrieve your Azure DevOps repositories by connecting to Rovo.

Before you begin

• All of Azure DevOps’s plans are supported by Rovo.

• You must be the Azure DevOps Organization owner, or be a member of the Project Collection Administrators group to setup Rovo.

• Only repositories are available to Rovo.

• Rovo will always respect permissions. Users will only ever see tickets that they already have access to.

Enable Azure DevOps OAuth

1. Log into Azure DevOps, take note of your organization’s URL. For example, if your site is dev.azure.com/vitafleetengineering, you’ll need the vitafleetengineering later.

2. Select Organization settings at the bottom of the left navigation.

3. Select Settings > Policies in the left navigation.

4. Check that Third-party application access via OAuth is set to On.

Connecting to Azure DevOps

To get to the setup screen for Azure DevOps:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Settings > Rovo.

3. Under Activated sites, next to the site you want to connect, select More actions () and select Add connector.

4. Select Azure DevOps and press Next.

5. Enter a name for your Azure DevOps connection. This doesn’t need to match anything.

6. Enter the URL for your Azure DevOps site. If your full Azure DevOps URL is dev.azure.com/vitafleetengineering, you only need to enter vitafleetengineering.

7. Review the disclaimer.

8. Select Authorize Azure DevOps.

9. A new tab will open in Azure DevOps. Review and accept the permissions. Select Accept.

Next steps

After you’ve finished connecting Azure DevOps:

1. Repositories will start to show in Search incrementally over the next few hours.

2. Your team members will see Azure DevOps show up as a filter option in Search. If they haven’t connected to Azure DevOps from their Atlassian account, they may be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see content that they already have access to.

3. Depending on the number of repositories in Azure DevOps, it may take some time to be indexed and appear in Search.