Help
Email Service Desk turns email to your Microsoft 365 support mailbox into Azure DevOps work items, and sends your team's replies from the work item as that mailbox. Each connected mailbox is a desk.
Get started
- Install the extension in your Azure DevOps organization from the Visual Studio Marketplace.
- Connect once. Open Project settings → Email desk and select Connect. Work items are created with that Microsoft sign-in, so emails become work items even when nobody is signed in. One connection covers the whole organization.
- Add a desk. Select New desk, give it a name, enter the Mailbox (a shared or user mailbox in your Microsoft 365, such as support@yourcompany.com), pick the Work item type and Area path, and select Connect mailbox.
- Allow access to the mailbox, once (next section).
Only project administrators can add or change desks; everyone else in the project can see them and their activity. It works with Azure DevOps Services organizations connected to Microsoft Entra ID; if yours isn't, the Email desk page says so.
Allow access to the mailbox
A Microsoft 365 administrator of the mailbox's organization (Global Administrator or Privileged Role Administrator) allows the app Email Service Desk Mail to read and send email, one time per Azure DevOps organization. After you select Connect mailbox, the panel shows Allow access to <mailbox>:
- Allow access — if you are that administrator: Microsoft's consent screen opens. Accept it, and sign in when asked; that sign-in confirms you are an administrator of that organization.
- Copy link for your admin — if you are not: send them the link (it works for a week). The desk connects by itself once they allow it; you can close the panel.
Once the desk is connected, new emails in the mailbox become work items within about a minute. Emails that were already in the mailbox stay as they are. Nothing in the mailbox is moved, marked read or deleted.
What access the app needs, and why
The app reads new mail in each desk mailbox (Mail.ReadWrite) and sends replies and automatic emails as that mailbox (Mail.Send). These are application permissions, so a desk keeps working when the person who set it up is away or leaves. Microsoft grants them for the whole tenant; the app opens only the mailboxes connected as desks, and only mail that arrives after the desk is added.
Limit the app to the desk mailboxes
Your Exchange administrator can scope the app to the desk mailboxes with
RBAC for Applications in
Exchange Online. Do it after the first desk is connected. In Exchange Online PowerShell
(Connect-ExchangeOnline), with the app's Object ID from Microsoft Entra admin center →
Enterprise applications → Email Service Desk Mail:
$id = "<Object ID>"
New-ServicePrincipal -AppId 828f7570-3099-43c3-9798-0f6336e794bf -ObjectId $id -DisplayName "Email Service Desk Mail"
Set-Mailbox -Identity support@yourcompany.com -CustomAttribute15 "EmailServiceDesk"
New-ManagementScope -Name "Email Service Desk mailboxes" -RecipientRestrictionFilter "CustomAttribute15 -eq 'EmailServiceDesk'"
New-ManagementRoleAssignment -App $id -Role "Application Mail.ReadWrite" -CustomResourceScope "Email Service Desk mailboxes"
New-ManagementRoleAssignment -App $id -Role "Application Mail.Send" -CustomResourceScope "Email Service Desk mailboxes"
Test-ServicePrincipalAuthorization -Identity $id -Resource support@yourcompany.com
- Run
Set-Mailboxfor every desk mailbox. If custom attribute 15 is already in use, pick another one in both lines. - The last line should show InScope: True for a desk mailbox and False for any other.
- If Exchange answers that you first need to run
Enable-OrganizationCustomization, run it, then try again later: Microsoft can take a few hours to allow the scope commands after it. - Then remove the tenant-wide grant, which would otherwise still apply: Enterprise applications → Email Service Desk Mail → Permissions → Admin consent, and revoke the two Microsoft Graph permissions (Mail.ReadWrite, Mail.Send). The desks keep working on the scoped roles.
- For a new desk later, tag its mailbox with
Set-Mailboxbefore you add the desk, so it connects without asking for consent again.
Desk settings
Open a desk from the list. Each desk has four tabs; select Save after a change.
| Tab | What you set |
|---|---|
| Defaults | The new work items' Work item type, Area path, Iteration path, Assigned to, Tags (separated by commas) and Priority |
| Senders | Anyone who emails the mailbox, or Only these senders and domains (name@company.com or @company.com) |
| Emails | Desk name; Send the requester a confirmation when a request arrives; Email the requester when the work item moves to the closing states you tick. Subjects and messages can use {id}, {title}, {first name} and {desk name} |
| Activity | Every email the desk received and sent in the last 30 days, and its result |
A project can have several desks, one per mailbox: the mailbox decides where an email goes. A mailbox can belong to one desk only.
When an email arrives
- A new email becomes a work item with the desk's defaults: the subject is the title, the message the description, and attachments are attached (up to 10 MB each and 14 MB per email; larger files are left out and the work item says so).
- The Requester group on the work item form shows who wrote in.
- An answer to an email from the desk is added to the same work item as a comment, with only the new text. An answer after the resolved email reopens the work item.
- Auto-replies, bounces, bulk mail and mail loops never create work items. With a sender list, mail from anyone else doesn't either, but people already on a conversation can always answer it. All of these show in Activity with the reason.
- If a work item can't be created (for example the desk's area path was deleted), the email waits. Fix the desk and save it: waiting emails are filed then.
Reply by email
Open the work item's Email tab. The conversation is listed newest first, with the reply box on top: check To, add people on Cc, Attach files (10 MB together at most) and select Send. The email goes out from the desk mailbox with its Microsoft 365 display name, threaded with the requester's email, and a copy stays in the mailbox's Sent Items.
On a work item that didn't come from email, the Email tab lets you email someone from it: pick the desk in From. Their replies come back to this work item. Save a new work item before emailing from it.
Discussion comments on the work item stay with the team. Only what you send from the Email tab, and the automatic emails, reach the requester. A desk sends at most 500 emails a day.
If something's wrong
| The desk says | What to do |
|---|---|
| Waiting for access | A Microsoft 365 administrator hasn't allowed access yet. Select Allow access, or copy the link for your admin. |
| Access taken back | The app's access to the mailbox was removed. Select Reconnect, or send the link to your admin. |
| Mailbox can't be found | The mailbox was removed or renamed. Delete the desk and add one for the new address. |
| Sign-in expired | Select Reconnect on the Email desk page. Emails are kept and become work items once you reconnect. |
| This area path was deleted | Pick another area path on the Defaults tab and save. Waiting emails are filed then. |
Your data
What the extension reads, stores and for how long: Privacy. To stop it reading a mailbox, delete the desk; to remove its mail access completely, remove the Email Service Desk Mail enterprise application in Microsoft Entra.
Contact
Questions or problems: crosstowntech.com/support. We reply by email.