Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Azure CI/CD: Configuring Email Notifications in Azure DevOps

Posted on 01/09/202120/08/2026 Imoh Etuk By Imoh Etuk 1 Comment on Azure CI/CD: Configuring Email Notifications in Azure DevOps
  1. Home
  2. AWS/Azure/OpenShift
  3. Azure CI/CD: Configuring Email Notifications in Azure DevOps
header-picture-1

When building your first Azure CI/CD Pipeline on Azure DevOps, one of your responsibilities as the project administrator will be to manage notifications for a team, group, or organization so that can receive email notifications for each successful build or failure build pipeline. In his guide, we shall discuss “Azure CI/CD: Configuring Email Notifications in Azure DevOps”. In my previous articles, I described very extensively how you can build your first Azure CI/CD Pipeline in Azure DevOps using ASP.Net Core Application. Please see how to Integrate SonarCloud with Azure DevOps Pipeline

If you haven’t read it yet, click How to build your first CI/CD pipeline in Azure DevOps. Why do you need to read my previous article? The reason is to give you a first-step guide to how you can set up your Azure DevOps Account, starting from signing up for Azure DevOps as a new user, and creating your first Azure DevOps Organization to creating your first Azure DevOps Project, and running your Azure CI/CD Pipeline.

The steps mentioned are the first steps you need to get started with configuring email notifications for your project team for any build pipeline on Azure DevOps. So, there are two levels of notifications in Azure DevOps. They are:

  • Notifications at the organization level and;
  • Notification at the project level.

So if you disable email notifications for a particular project yet you still receive a build notification you need to also disable it at the organization level.

Here are some related guides: Import repo to Bitbucket Cloud: How to import your project from Bitbucket Server or Bitbucket Cloud to GitLab, and Azure DevOps and GitHub integration for Docker and Kubernetes deployment.

Why Do you need to Enable email Notifications for your build Pipeline Azure CI/CD?

Who receives an email notification when a build pipeline is successful or failed must be properly configured. Not properly configured can result in your inbox receiving too many or few emails which could prevent you from knowing at the early stage if your Azure CI/CD build pipeline is fine or not.

The reason why you need to configure the email and add new custom email subscriptions, its delivery settings, delivery preferences, and other factors is because notifications help you and your team stay informed about activity that occurs within your projects in Azure DevOps.

You can get notified when changes occur to the following items:

  • Build completes – Which reports the build is complete successfully
  • Pull request reviewers added or removed – Notifies the team when it is added or removed as a reviewer for a pull request reviewer
  • Pull request changes – Notifies the team when changes are made to a pull request
  • Run stage waiting for approval – Notifies the team when a run stage approval is pending on them.
  • Manual validation Pending – Notifies the team when a manual validation is pending on them.
  • Manual intervention pending – Notifies the team when a manual intervention is pending on the team
  • Deployment to an owned stage failed – Notifies the team when a deployment does not succeed and makes a stage that the team owns unhealthy
  • Deployment to an approved stage failed – Notifies the team when a deployment team approved does not succeed Azure CI/CD
  • Deployment completion failures – Notifies the team when a deployment team request does not succeed and run
  • Deployment approval pending – Notifies the team when an approval for a deployment is pending on the team.

Please see how to create a static pod in Kubernetes, and how to install, register and start GitLab Runner on Windows.

Enable email notifications at the organizational level Azure CI/CD?

The following steps explain this;

1: Sign in to your organization {https://dev.azure.com/{yourorganization}
2: Create a new organization or select organization settings if there is an existing organization as shown in the screenshot below.

Microsoft CI/CD
Azure DevOps Organization

3. Select Global notification and new subscription as shown below:

Azure Continuous Integration and Continuous Deployment

Customizing Email Notifications Based on Build Completion

4. Select a build completes option – In this option, you will configure the email notification for the whole project or a specific project by selecting the radio button. I configured mine for my specific project.

Under the Deliver to the dialog box, select Custom email. In the filtering section, you have the option to select the purpose for configuring the email notification, here I select Build reason Azure CI/CD. This will enable me and my team to be notified of any build that’s successful or fail.

Azure Continuous Delivery
Email notifications Preference

5. Click Finish to have it configured

Under the Azure DevOps organization settings, you can view the existing Subscribers. In the screenshots shown below, I am the only existing subscriber Azure CI/CD.

Azure DevOps Pipeline
Microsoft CI/CD

How to enable email notifications at the Project level?

1: Sign in to your organization (https://dev.azure.com/{yourorganization}).
2: Select organization ->project

Azure Continuous Integration and Continuous Deployment
Organization – project selection

3. Afterward, select Project settings -> Notifications ->New subscription

Azure Continuous Delivery
Project setting

4. Under the category tab, select Build -> select A build completes or A build fails depending on your preference

31.08.2021_05.53.42_REC

5. Click Next

6. Then, select Custom email address in the Deliver to dialog box

31.08.2021_05.56.02_REC

Here are some guides on Find work or find workers with Jobble: Who is a DevOps Engineer?, and Azure DevOps: Docker and Kubernetes Deployment with GitHub.

Customizing Notifications for Azure CI/CD Build Completion

7. Complete the following steps as shown in the screenshot below based on your preference. As you can here, I’m particularly configuring the notification for A build completes.

Azure CI/CD Hence, why that is specified as the description? Of course, I’m configuring it for my specific project and this specific project is for all the people added as team members for the project named demoproject.

Looking through the Filter section, I have added more clause such as status which and requested by.

31.08.2021_05.58.34_REC

8. Click Finish and you’re good to go.

Thus, you can turn off notifications for subscribers by simply switching between the toggling button as shown on the screenshot below.

Turning-off-Notification

View and edit all notification subscriptions

Hence, this view shows all notification subscriptions that you’ve created or that were created by an administrator.

Notification subscriptions let you control what you get notified about. In addition, subscribed notifications are indicated with the State as On Azure CI/CD.

View-and-edit-notification

That is it with configuring email notifications for your build pipeline or any other activities within your Azure DevOps organization and project.

I hope you found this article useful on “Azure CI/CD: Configuring Email Notifications in Azure DevOps”. Please feel free to leave a comment below.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
AWS/Azure/OpenShift, Version Control System Tags:Azure, Azure DevOps

Post navigation

Previous Post: How to deploy an Angular App to AWS S3
Next Post: How to install Microsoft SQL Server Management Studio

Related Posts

  • mgithub
    How to use Command-Line on Git Bash and GitHub Desktop to PUSH local code to GitHub Version Control System
  • ouath2final 1 e1786835965613
    How to implement Interactive Authentication using MSAL dotNET AWS/Azure/OpenShift
  • Azure DevOps Server
    How to Install Azure DevOps Server 2022 Automation
  • commit trong git 640
    How to uninstall Git from MacOS Mac
  • Gitfixed
    GitLab-runner is not recognized as an internal or external command, operable program, or batch file Version Control System
  • azure active director
    AD Connect Error: The Synchronisation service scheduler is currently synchronization and the configuration change cannot be made at this time AWS/Azure/OpenShift

More Related Articles

CreateanAWSact How to Set up an Amazon Web Services (AWS) Account AWS/Azure/OpenShift
banner Various ways to restart an AWS EC2 instance AWS/Azure/OpenShift
FEATUREIMAGE How to work with Azure Cognitive Service AWS/Azure/OpenShift
Microsoft 365 Developer Program instant Get your free Microsoft 365 E5 Sandbox today AWS/Azure/OpenShift
s3 How to Copy from a server to s3 and vice versa AWS/Azure/OpenShift
Azure Backup For AKS How to protect Azure Kubernetes Service (AKS) with Azure Backup AWS/Azure/OpenShift

Comment (1) on “Azure CI/CD: Configuring Email Notifications in Azure DevOps”

  1. Avatar photo Tim Grayden says:
    13/01/2023 at 7:52 PM

    Nice article!

    One thing I’ve noticed is that engineers can get too many email notifications, and start to filter them out after a while. There is a tool called CatLight that can help with that. It shows desktop notifications for Azure DevOps builds, releases, PRs and work items. It displays only the current state, so you’ll never see an outdated notification or alert. 

    It also has an investigation feature, so that the team can collaborate on fixing broken pipelines.

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

Top 30 Sysadmin blog

veeaam100

Veeam Vanguard

  • Force bitlocker encryption
    Force BitLocker Recovery mode: How to unlock BitLocker Protected Drive Network | Monitoring
  • banner
    Prevent Microsoft Edge from sending your Search data to Microsoft Windows
  • apache ubuntu 20 04
    How to Install Apache HTTP Server on Ubuntu 20.04 LTS Linux
  • GRADLE FEATURE
    How to install Gradle on Ubuntu Linux
  • Unveiling OOTBI Mini
    Unveiling OOTBI Mini and New Features for v1.7 from Object First Backup
  • zoom feature
    How to install Zoom video conference software on Linux System Linux
  • hero activedirectory
    How to find disabled Active Directory User accounts Windows Server
  • 785509289 780x439
    Integrate Pleasant Password Server with Active Directory Password Manager

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,745 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.