Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022
Important
The Azure DevOps Office integration add-in is no longer supported and might not function with current versions of Office or browsers. Microsoft doesn't provide updates or fixes for this add-in. For bulk work item operations, use the CSV import/export functionality, which is the recommended and supported approach.
Note
This article covers the legacy Azure DevOps Office integration add-in. For new bulk workflows, use CSV import/export or bulk modify work items in the web portal. The following steps are for teams that still rely on Excel-based workflows.
To support legacy work tracking workflows, you can use Microsoft Excel to add or update work items. You can either work in online mode (connected to Azure Boards or Azure DevOps Server) or in offline mode (against a local copy of the document).
Tip
You can use AI to help with this task later in this article, or see Enable AI assistance with Azure DevOps MCP Server to get started.
Supported Office clients and Azure DevOps versions
The following table shows Office client support by Azure DevOps/Visual Studio version.
macOS isn't supported. Even if you installed Visual Studio for Mac, connection to Azure DevOps from Excel or any other Office client isn't supported.
| Azure DevOps/Visual Studio version | Excel | Project integration | PowerPoint Storyboarding | Notes |
|---|---|---|---|---|
| Azure DevOps Services Azure DevOps Server 2020 Visual Studio 2022 Visual Studio 2019 Azure DevOps Office Integration 2019 |
✅ Supported | ❌ Not supported | ❌ Not supported | Project integration and TFSFieldMapping are deprecated. Linking from inside PowerPoint is deprecated, but you can still add a Storyboard link from within a work item. |
| Visual Studio 2017 (legacy) | ✅ Supported | ✅ Supported | ✅ Supported | Legacy support only. |
Prerequisites
| Category | Requirements |
|---|---|
| Software | - Microsoft Excel 2016 or later, including Microsoft 365 versions. - Visual Studio or the free Azure DevOps Office Integration 2019. - The Azure DevOps Office Integration plug-in (installed with Visual Studio or with Azure DevOps Office Integration 2019). |
| Download Azure DevOps Office Integration 2019 | - Go to Visual Studio Downloads. - Scroll to All Downloads. - Expand Other Tools, Frameworks, and Redistributables. - Find Azure DevOps Office Integration 2019 and select Download. - If you can't locate the download or don't have access, sign in with a Microsoft account or contact your administrator. |
| Permissions | - Project member access to connect to an Azure Boards project. |
| Project | - An Azure Boards project. If you don't have one, see Create a project. |
For information about compatibility requirements, see Azure DevOps client compatibility.
Limitations and known issues
The Azure DevOps Office integration add-in predates modern Microsoft 365 authentication, and Microsoft no longer actively maintains it. Expect these limitations:
- Modern authentication: Conditional Access, multifactor authentication (MFA), and device compliance policies can block sign-in. If interactive sign-in fails, sign in to your Office client with the same account you use for Azure DevOps before you open the worksheet.
- Personal access tokens (PATs): Some scenarios prompt for a PAT instead of interactive sign-in. PATs are long-lived credentials, so avoid them when possible. Use Microsoft Entra tokens where supported. If you must use a PAT, see Use personal access tokens.
- Microsoft 365 (web) and macOS: The add-in works only in desktop Office on Windows. Excel for the web and Office for Mac don't support this add-in.
- Hosted agents and automation: The add-in supports interactive use only. It doesn't support unattended or pipeline-based scenarios. Use the Azure DevOps REST API instead.
- Large datasets: Publishing or refreshing thousands of work items in one worksheet can time out. Split work across worksheets or use CSV import/export.
For supported alternatives, see Bulk modify work items in the web portal and Bulk import or update work items using CSV files.
Publish and refresh work items
When you work in Excel, you edit a local copy of work item data.
Use these actions to stay synchronized:
- Refresh downloads the latest values from Azure Boards into your worksheet.
- Publish uploads your worksheet changes to Azure Boards.
At first, your worksheet and Azure Boards match. Over time, other users or processes can change the same work items. To avoid conflicts and stale edits, use this rhythm:
- Refresh when you open the file.
- Make a small set of edits.
- Publish changes.
- Refresh again, especially during longer sessions.
Repeat this cycle throughout your session.
Azure DevOps and Excel
The following diagram shows the two-way sync between Excel and Azure DevOps:
- Excel publishes local edits to Azure DevOps.
- Excel refreshes to pull server-side updates.
For the full Excel workflow, see Bulk add work items with Excel.
Connect an Azure DevOps project to Excel
To add or modify work items in Excel, first connect your worksheet to an Azure DevOps project.
Note
- This section shows Excel steps for Azure Boards. PowerPoint uses a similar connection flow.
- In Azure DevOps Services, the portal automatically selects the Team Project Collection. In Azure DevOps Server, select the collection before you select the project.
Choose one connection path:
- Web portal
- Excel client (cloud)
- Excel client (on-premises)
- Visual Studio/Team Explorer
Your worksheet connects as either an Input list (manual list) or a Query list (saved query results).
- From the web portal
- From an Office client (cloud)
- From an Office client (on-premises)
- From Visual Studio
This connection method requires the Azure DevOps Open in Excel Marketplace extension and Visual Studio 2017 or later.
In your browser, confirm the correct project is selected, and then go to Boards > Queries > All.
Select the query you want to open in Excel.
On the Results tab, select the
actions icon, and then select Open in Excel.
Tip
You can use multiple worksheets within an Excel workbook to work with different input or query lists. You can only connect to one project per workbook.
If you move your Azure DevOps project to a different project collection in the same Azure DevOps Server instance, your documents reconnect automatically. If the project moves to a different Azure DevOps Server instance, you must manually reconnect your documents to the new server.
Work offline and reconnect to Azure Boards
You can work offline in Excel to add or update work items, then reconnect and sync later.
Note
If the project moves to a different Azure DevOps organization or Azure DevOps Server instance, reconfigure the document connection. For steps, see Connect Azure DevOps project to Excel.
Disconnect a document file from the network
Before you disconnect, prepare your worksheet:
Open the document you want to edit offline.
Get the latest updates. In Excel, on the Team ribbon, in the Work Items group, select Refresh.
Add all columns you plan to edit. You can't add columns after you disconnect.
Disconnect your computer from the network, or save the work item list file and copy it to another computer.
Office might show a connection error after you disconnect.
Modify or update the work item list as needed.
While offline, you can't create most link types between work items. Parent-child links in an Excel tree list are the exception.
Reconnect a file to Azure Boards
When you're back online, resync your file:
Reconnect your computer to the network, or copy the file to a computer that is connected to Azure Boards.
If you changed the file offline, in Excel, on the Team ribbon, in the Work Items group, select Publish.
If you didn't make offline changes, select Refresh instead.
Resolve any validation errors or conflicts.
Marketplace extensions
These Marketplace extensions support Azure DevOps and Microsoft 365 integration scenarios:
-
Opens query results or selected work items in Excel from the web portal for bulk editing and analysis.
- Publisher: Microsoft DevLabs
- Requirements: Microsoft Excel and either Visual Studio or the Azure DevOps Office Integration client
- Compatibility: Azure DevOps Services and Azure DevOps Server
-
Sends Azure DevOps service hook notifications (for example, build, code push, and work item events) to a Microsoft 365 group inbox.
- Publisher: Microsoft
- Scope: Azure DevOps Services
Note
The Marketplace page states this extension is preinstalled with Visual Studio Team Services/Azure DevOps Services.
Use AI to work with work items without Excel
If you configure the Azure DevOps MCP Server, you can describe common work item tasks in natural language, avoiding the legacy Excel add-in for many scenarios.
Replace placeholder values before you run a prompt: <ProjectName>, <AreaPath>, <IterationPath>, and <UserName>.
| Task | Example prompt |
|---|---|
| Add work items in bulk | Create 10 User Stories in project <ProjectName> under area path <AreaPath> in iteration <IterationPath> |
| Import a hierarchy | Create an Epic "Checkout revamp" in project <ProjectName> with 3 Features and 2 User Stories under each Feature |
| Update field values | Set Iteration Path to <IterationPath> for all active Tasks assigned to <UserName> in project <ProjectName> |
| Reassign work | Reassign all active User Stories in area path <AreaPath> from <UserName> to <UserName> |
| Move items to a sprint | Move all uncommitted User Stories in project <ProjectName> from iteration <IterationPath> to iteration <IterationPath> |
| Add tags in bulk | Add tag "release-2026" to all User Stories in iteration <IterationPath> in project <ProjectName> |
| Query work items | Show all active unassigned Bugs in project <ProjectName> |
| Export a snapshot | List all resolved Bugs in project <ProjectName> from the last 30 days with Title, Assigned To, and Closed Date |
| Refresh values in bulk | Set Priority to 2 for all active Bugs in area path <AreaPath> in project <ProjectName> |
| Change work item type | Change all Issues tagged "convert-to-bug" to Bug in project <ProjectName> |
Note
If you're using Visual Studio Code, agent mode is especially helpful for complex work item operations.