> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Azure DevOps
> Keep incidents and their follow-ups tracked in Azure DevOps, without anyone updating them by hand.
Connect Azure DevOps to create work items in the project your team already plans in: one for each incident, and one for each follow-up you export. We keep them updated as the work progresses, and sync changes back.
## Connecting Azure DevOps
Sign in as an Azure DevOps user with access to the relevant projects, then go to [Settings → Integrations](https://app.incident.io/~/settings/integrations), find Azure DevOps, and click **Connect**.
Click **Sign in with Microsoft** and complete the authorization flow.
Use a personal account under a shared "service" email. Azure service accounts behave differently in the API, so we don't support them for authentication.
Then add a [service hook](#service-hooks) so changes in Azure DevOps reach us.
## Exporting follow-ups
Export [follow-ups](/post-incident/follow-ups) as Azure DevOps work items, from the dashboard or from Slack and Microsoft Teams. Use an [export template](/integrations/auto-export-follow-ups) to send them automatically based on incident attributes.
The title always comes from the follow-up, and can't be set in a template. The work item's title syncs back as the follow-up title instead.
Changes in Azure DevOps update the linked follow-up:
* Title, description, and tags, which become follow-up labels
* The assignee, which becomes the follow-up owner
* Completion, which completes the follow-up and records when it happened
A work item counts as complete once it has a completed date. Which field that is depends on your process template: **Completed Date** on Scrum, **Resolved Date** on Agile, or **Closed Date** on Basic. We use whichever is set.
## Incident tickets
Set up [incident tickets](/integrations/incident-tickets) to create and maintain a work item for each incident, with its title, description and state driven by a template. Templates default to the **Issue** work item type.
Comments added to the work item sync back into incident.io.
## Service hooks
A service hook lets changes in Azure DevOps reach incident.io. Without one, nothing syncs back for follow-ups or incident tickets.
1. Go to your project, select **Project settings**, and then select **Service hooks**.
2. Select **Create subscription**.
3. Select **Web Hooks** and then click **Next**.
4. Change the trigger to **Work item updated** and then click **Next**.
5. Copy the service hook details from the dashboard into the service hook config.
6. Click **Test**, and check the dashboard shows a success.
7. Click **Finish** in Azure DevOps to complete the setup.
