Source code
Azure DevOps
Connect an Azure DevOps organization so Dave can read code and open pull requests.
Azure DevOps asks for your organization name before sending you to Microsoft to approve Dave. Dave then adds its own service principal to your organization and works as that identity.
Connect
Section titled “Connect”-
Find your organization name — the segment after
dev.azure.com/in your URL. Forhttps://dev.azure.com/acme/MyProject, that isacme. On older accounts resolving asacme.visualstudio.com, it is the subdomain. Enter only the name. -
Confirm you are in Organization settings → Permissions → Project Collection Administrators. Dave needs those rights to add itself to the organization.
-
In Dave, go to Integrations → Add integration → Azure DevOps.
-
Enter the Organization, then choose Continue to Microsoft.
-
Sign in with the account that is a Project Collection Administrator and approve Dave.
An organization can be connected to only one Dave workspace at a time.
Permissions
Section titled “Permissions”Two identities are involved.
You, once, while connecting. Dave asks Microsoft for delegated access as you:
499b84ac-1321-427f-aa17-267ca6975798/user_impersonationopenidprofile499b84ac-1321-427f-aa17-267ca6975798 is the Azure DevOps API. Dave uses this access
only during setup, to list your projects and add its service principal to the
organization. You must be a Project Collection Administrator of the organization.
If your Microsoft Entra directory requires admin approval for new apps, an Entra
administrator has to approve Dave first.
Dave’s service principal, from then on. Approving Dave adds it to your Entra directory as an enterprise application. Dave then adds that service principal to your organization with:
Access level: BasicProject group: Contributors (on every project that exists at connect time)Dave works as this service principal for everything else: reading code, pushing branches, opening pull requests, and commenting on them.
Projects created after you connect are not included. To give Dave access to a new project, add its service principal to that project’s Contributors group under Project settings → Permissions, or disconnect and Connect again.
Manage the connection
Section titled “Manage the connection”In Azure DevOps, review or remove Dave’s service principal under Organization
settings → Users, at https://dev.azure.com/<org>/_settings/users. Change its
access level there, or choose Remove from organization. Per-project
access is under Project settings → Permissions → Contributors.
In Microsoft Entra, the Dave app is under the Azure portal at Microsoft Entra ID → Enterprise applications → Dave. Permissions shows the consent that was granted, and Properties → Delete removes the app from your directory.
Disconnect in Dave stops Dave from using the connection, but it does not remove anything on the Microsoft side. To fully revoke Dave:
-
In Azure DevOps, go to Organization settings → Users and remove Dave’s service principal from the organization.
-
In the Azure portal, go to Microsoft Entra ID → Enterprise applications → Dave → Properties, and choose Delete.
If Dave’s access level is lowered to Stakeholder, it can no longer read code. Set it back to Basic under Organization settings → Users.
Selecting repositories
Section titled “Selecting repositories”After connecting, choose which repositories Dave should work in. This narrows Dave’s attention; it does not change the service principal’s access in Azure DevOps.
Troubleshooting
Section titled “Troubleshooting”- “Dave could not add itself to your Azure DevOps organization.” The account that approved Dave is not a Project Collection Administrator. Connect again signed in as one.
- “Dave could not authenticate against your Microsoft Entra directory.” Consent was never completed or was revoked, for example by deleting the enterprise application. A Project Collection Administrator should Connect again.
- “Dave is no longer a member of this Azure DevOps organization.” Its service principal was removed from the organization. Connect again as a Project Collection Administrator so Dave can add itself back.
- “Dave’s access level … was lowered to Stakeholder.” Set it back to Basic under Organization settings → Users, then run the health check again.
- “This Azure DevOps organization is already connected to another Dave workspace.” Disconnect it there first.