Azure DevOps is a live integration, and it is the one provider whose single connection covers both halves of a team's delivery system: Boards (work items, sprints, backlogs) and Repos (pull requests, commits, pipeline runs).
Link your Azure DevOps account
- Open Connected Apps and choose Azure DevOps.
- Sign in with your Microsoft work account (Microsoft Entra ID) and accept the requested access. Everview acts as you, with your permissions — nothing more.
- Everview lists the Azure DevOps organizations in your directory and creates a first team from your first project's default team automatically. Work items and sprints sync right away; pull requests, commits, and build history follow.
Two sign-in notes:
- Depending on your company's policy, an admin may need to approve Everview the first time anyone connects. Everview shows the approval link to send them; after they approve once, everyone can connect.
- Sign-in with a personal Microsoft account isn't accepted, so organizations tied to personal accounts can't be connected — Microsoft's documentation covers moving an organization into a directory.
Choose what a team tracks
- Open Teams from the Organization Menu, then create or open a team.
- Set the Team name, then choose your connected Azure DevOps account under Organization.
- Under Data Source in Azure DevOps, pick the Organization, the Project, and the Team — the same slice a board shows in Azure DevOps: that team's backlog and its sprints.
- Click Create Team to save.
Everview reads the project's process configuration (Agile, Scrum, Basic, CMMI, or a custom process) to learn its work item types and estimate field — there is nothing to map by hand.
If your organization isn't listed
Azure DevOps organizations live in a specific Microsoft directory. If you use one as a guest of another company's directory — common for consultants and partner teams — connect it with "Add organizations from another directory" in Connected Apps: you sign in once more with the account that backs that organization.
What to do about it
Once connected, set the team's workflow preferences — default work item type, capacity, and member allocation — in Set Team Capacity and Workflow Preferences. Everview writes back only when you act: creating and editing work items, moving them between sprints, changing states, comments, links, and sprint create/complete all round-trip to Azure DevOps with your permissions. Disconnecting from Connected Apps removes the event subscriptions Everview created and stops syncing — your Azure DevOps data itself is never touched.