Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Connect Azure DevOps to Rovo

Mike Zdanio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 24, 2026

Has anyone been able to successfully connect Azure DevOps to Rovo following these instructions?

https://support.atlassian.com/organization-administration/docs/connect-azure-devops-to-rovo/

 

I am the owner of a brand new Azure Organization, but every time I try to connect, I get the following error. OAuth is enabled in the Azure org.

 Screenshot 2026-05-15 090454.png

I have a ticket open with Atlassian, but wondering if anyone has seen similar errors and have been able to resolve them.

Thanks! 

1 answer

0 votes
VENKATESWARLU KURUVA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 24, 2026

Hey Mike,

That error is super common with fresh Azure DevOps orgs — it's almost never actually about OAuth being disabled. Here's what usually fixes it:

Most likely culprits:

Third-party OAuth needs to be ON at the org level — not just the project level. Go to Azure DevOps → Organization Settings → Policies → make sure "Third-party application access via OAuth" is enabled. This trips up most people.

You need to authorize the Atlassian app in Azure AD too — if your Azure org uses Azure AD (Entra ID), an admin needs to grant consent for the Atlassian enterprise app. Check Azure Portal → Enterprise Applications → look for the Atlassian/Rovo app and grant admin consent.

Browser/cookie issue — try in an incognito window. Sometimes stale auth tokens from the Azure login flow cause this exact error.

Timing — brand new Azure orgs sometimes take a few hours for OAuth policies to fully propagate. If you just enabled it, give it 30-60 minutes and retry.

Quick checklist:

1.Azure DevOps → Org Settings → Policies → Third-party OAuth = ON

2. Azure AD → Enterprise Apps → Atlassian app → Admin consent granted

3. You're an org owner/admin on both sides (Atlassian + Azure)

4. Try incognito browser

If all that checks out and it still fails, your support ticket is the right move — there's a known edge case with certain Azure AD tenant configurations that needs backend help from Atlassian.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events