![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Microsoft 365 and Office | Excel | For business | Windows
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 97%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKT%3C/text%3E%3C/svg%3E)
Hi,
Thank you for taking the time to raise this concern.
The current documentation can understandably be confusing because some Microsoft Learn articles continue to describe Excel integration scenarios, while Azure DevOps Office Integration 2019 is also identified as a legacy and unsupported component.
Based on Microsoft's publicly available documentation, there is currently no announced long-term roadmap, replacement timeline, or open-source plan for Azure DevOps Office Integration 2019.
The current documentation suggests the following:
1/ Azure DevOps Office Integration 2019 is a legacy component.
Microsoft documentation states that the Office integration add-in is no longer supported, may not function correctly with newer Office or browser versions, and does not receive ongoing updates or fixes.
2/ Excel integration remains available today, but its future availability has not been publicly committed.
Current documentation continues to reference Excel-based work item management scenarios for Azure DevOps Services and Azure DevOps Server. However, because the underlying Office Integration add-in is classified as legacy and unsupported, it should be viewed as a compatibility feature rather than an actively developed investment.
3/ Microsoft's recommended direction appears to be web-based and API-based workflows.
Documentation increasingly points customers toward:
- Web portal bulk editing of work items
- CSV import/export capabilities
- Azure DevOps REST APIs for automation and integration scenarios.
4/ There is no public indication that the Office Integration add-in will be open-sourced.
Microsoft has open-sourced the Azure DevOps Open in Excel extension (microsoft/vsts-open-in-excel) on GitHub. However, that project is only the portal extension used to launch Excel and still depends on the separate Azure DevOps Office Integration client. At this time, there does not appear to be any public commitment to release the source code for the underlying Office Integration add-in if it is eventually retired.
For reference:
- GitHub - microsoft/vsts-open-in-excel: Open in Excel extension for Azure DevOps
- Connect Azure Boards to Excel (legacy) - Azure Boards
- Excel and Azure Boards FAQs - Azure Boards
- Azure DevOps Open in Excel - Visual Studio Marketplace
This link is shared by community members for your convenience. It points to a third-party site that is not managed or verified by Microsoft. I can’t guarantee the quality, safety, or suitability of any content or software found there. Please review carefully and make sure you understand any potential risks before using it.
Because many organizations still rely on Excel-connected work item management, additional clarity from Microsoft would be very valuable, particularly regarding:
- Whether Excel integration will continue to be included in future Azure DevOps Server releases.
- Whether a supported replacement for Excel-based work item editing is planned.
- Whether the Office Integration add-in will remain available for customers with existing dependencies.
- Whether Microsoft would consider open-sourcing the Office Integration client if it reaches end-of-life.
In the meantime, organizations that depend on Excel integration may want to evaluate alternative approaches such as CSV import/export, Azure DevOps web-based bulk editing, REST API integrations, or other modern workflow solutions to reduce reliance on a legacy component.
I hope this information helps clarify what is currently known from the publicly available documentation. If further updates or clarification become available from the Microsoft product team, they would be valuable for customers who continue to rely on Excel-based work item management.
Thank you for your understanding, and have a wonderful day ahead.
If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.