We want to spend time on the most important things right? Are you also annoyed by the number of emails generated by Azure DevOps? See how I fixed the email overdose using an Outlook rule.

E-mail headers

To remove all emails would be nice, but we won’t see any mentions. To know how to recognize a mention email I opened a mention email. I found the headers by clicking the three dots in the Outlook web version. And then Open the ‘View’ dropdown and select ‘View message details’.

Outlook web View message details
Outlook web - View > View message details

We see that some headers indicate that the message trigger contained ‘Mention’. This is essential information for our next steps. Here below the headers I found in the email message.

1
2
3
4
5
6
X-VSS-Scope: organisation/project/Repository
X-VSS-Event-Type: ms.vss-mentions.identity-mention-event
X-VSS-Subscription-ID: ms.vss-mentions.identity-mention-subscription
X-VSS-Event-Initiator: Mart de Graaf
X-VSS-Event-Initiator-Ascii: Mart de Graaf
X-VSS-Event-Trigger: Mention

Outlook Rules

I am not praising the Outlook client, I want to talk about the Rules feature of Outlook. The rules are found in the classic Outlook by pressing ‘File’ and then clicking the big ‘Manage Rules & Alerts’ button. Let’s create a rule to delete and mark all those emails as read.

The first step is to define conditions. We know Azure DevOps emails from azuredevops@microsoft.com. For my case, I wanted to scope emails to a certain organization, which can be done by filtering specific words in the message header.

Rule conditions
Rule conditions


The emails should be deleted, but also be marked as read. Nothing is more annoying than a number after your delete folder, right?

Rule actions
Rule actions


We still would like to receive the Mention emails. So we need to make an exception for them. As said earlier this can be done by filtering the message header for specific words.

Rule exceptions
Rule exceptions


Full Outlook Rule

The only thing you have to edit in my example is the organisationName.

1
2
3
4
5
from azuredevops@microsoft.com
 and with VSS-Scope: organisationName
delete it
 and mark it as read
except if the message header contains 'X-VSS-Event-Trigger: Mention' or 'X-VSS-Subscription-ID: ms.vss-mentions.identity-mention-subscription'

:megaphone: Have any suggestions, I would love to hear them!

Conclusion and discussion

Help yourself keep control of your inbox. I think you should work from the board and business wishes, and not from your inbox.