Attach emails to Azure DevOps work items directly from Outlook. Select one or more work items by ID, and the email is uploaded as an .eml attachment.
Works with the new Outlook (Windows, web, Mac) and classic Outlook desktop.
cd ADOIntegration
npm install
npm startThis starts a dev server on https://localhost:44366. You'll need the Office dev certs installed:
npx office-addin-dev-certs install- Open Outlook (new or web)
- Open any email → Get Add-ins → My add-ins → Add a custom add-in → Add from file...
- Select
ADOIntegration/manifest.xml
- Open an email you want to attach.
- Click "Attach to ADO" in the ribbon.
- On first use, configure your Azure DevOps org URL, project, and authentication (PAT or Entra ID).
- Enter a work item ID and click Add. Repeat for multiple work items.
- Click Attach — the email is uploaded as an
.emlfile to each selected work item.
Two methods supported, depending on your account type:
- Personal Access Token (PAT) — Required for personal Microsoft accounts. Generate a token at
https://dev.azure.com/{your-org}/_usersSettings/tokenswith Work Items: Read & Write scope. Paste it into the add-in settings. No Azure app registration needed. - Microsoft Entra ID (OAuth) — Available for work or school accounts only. Signs in via a popup using MSAL.js. Requires an Azure App Registration with the
Azure DevOps user_impersonationdelegated permission and a SPA redirect URI pointing to the add-in'staskpane.html.
Which should I use? If you log into Azure DevOps with a
@outlook.com,@hotmail.com, or@gmail.comaddress, use PAT. If you use a corporate/school email (@yourcompany.com), either method works.
- TypeScript, React, Fluent UI
- Office.js (Outlook Mail Read add-in)
- Azure DevOps REST API v7.1
- MSAL.js for Entra ID authentication
The original VSTO add-in for classic Outlook + TFS is in TFSIntegration/. It is no longer maintained — VSTO is not supported in the new Outlook.
See CHANGELOG.md for version history. | Privacy Policy | Terms of Use
