Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Notifications in Azure DevOps keep you and your team informed about project activity, including changes to work items, code reviews, pull requests, source control files, and builds. When an event occurs in Azure DevOps, the event content is compared with every subscription of that event type. A notification is generated for every subscription/event match that meets the filter conditions. Notifications are delivered through email or service hook, based on the delivery properties defined in the subscription.
For more information, see the list of supported event types and learn more about email delivery options.
Notification types
There are four types of notifications that you can manage in Azure DevOps. The following table lists the types and the permissions or role required to manage each notification.
| Notification type | Role required to manage |
|---|---|
| Personal notifications | User |
| Team notifications | Team Administrator, or member of the Project Administrators group or Project Collection Administrators group |
| Project notifications | Member of the Project Administrators group or Project Collection Administrators group |
| Global notifications | Member of the Project Collection Administrators group |
Personal notifications
There are several ways you can manage your personal notifications:
- View your notifications
- Set alerts only for yourself
- View and edit all subscriptions
- Add a custom subscription
- Unsubscribe or opt out of a team or project subscription
For more information, see Manage your personal notifications.
Team and project-level notifications
For team and project-level notifications, you can create a subscription for the following categories and templates:
| Category | Templates |
|---|---|
| Build | Build completes, Build fails, Status changes for legacy XAML build controller or agent, Quality changes for legacy XAML build |
| Code (Git) | Commit pushed, Comment added to pull request, Pull request created or updated, Pull request in review by my team updated |
| Code (TFVC) | Code checked in, Code checked in with policy override, Changes to code review, File in specific path checked in, File with specific extension checked in |
| Pipelines | Run stage waiting for approval, Run stage waiting for manual validation |
| Work | Work item created, Work item changed, Work item deleted, Work item restored, Work item moved from this team project |
| Artifacts | Package changed |
| Extension management | Extension modified |
| Release | Deployment approval pending, Deployment completes, Release creation request fails, Manual intervention for deployment pending |
Note
You can also create a custom notification subscription for pull requests created or updated in a draft state. For more information, see Custom notification subscription for draft pull requests.
For more information, see Manage team, group, and global notifications.
Global notifications
Global notifications apply to all projects defined for an organization or collection.
Subscriptions
A notification subscription is associated with a supported event type. The subscription includes a set of filters that are used to match events. For example, a subscription for a work item created event might include a filter that matches only the work item type, Bug. Or, a subscription for a pull request created event might include a filter for a specific repository and branch.
Default email subscriptions
Many useful email subscriptions are predefined and automatically enabled in the system. These resources and are referred to as default subscriptions. Default subscriptions provide out-of-box (OOB) support for the most common notification scenarios. For more information, see the list of available default subscriptions.
An organization or team administrator can choose which of the default subscriptions to make available to their users. For more information, see Manage notifications for a team, project, or organization.
Individual users can choose to opt out of any default subscription while other team members remain subscribed. For more information, see Manage your personal notifications.
The Default subscriptions section in Azure DevOps lists all default global subscriptions available. The globe icon 
indicates a default or OOB subscription. For more information, see Default and supported notifications.
Members of the Project Collection Administrators group have permission to enable/disable any default subscription in this view. Any member of the Project Collection Valid Users group has permission to view the details of the default subscription. The view and enable options are available in the More options menu (...) associated with each individual subscription.
Custom email subscriptions
Organization or team administrators can create Custom email subscriptions that apply to all members of the organization or team. For more information, see Manage notifications for a team, project, or organization. To learn more about querying with group clauses, see Define a work item query.
Users can also create custom subscriptions, which apply only to them. For more information, see Manage your personal notifications.
Custom service hook subscriptions
Use service hooks subscriptions to integrate with third-party services. When an Azure DevOps event matches a service hook subscription, the third-party service receives a notification. For example, when an Azure DevOps build completes, a notification goes to a Slack channel with links back to the build artifact in Azure DevOps. For more information, see Integrate with third party services.
Subscribers
The Subscribers section begins with an empty identity search box. Enter any group, team, or individual to view the list of subscriptions associated with the specified identity.
You can find all notification subscriptions for the specified identity in this view. Management options are available from the More options menu (...) associated with each subscription. The globe icon
indicates a default or OOB subscription.
Statistics
The Statistics section shows the most active notification subscriptions and the top event initiators (group, team, or individual). The statistics are for the current day only and the values reset at 00:00 UTC. One benefit of viewing the statistics is the ability to identify unintended high-volume subscriptions or event initiators.
Settings
Manage global-level Settings, such as delivery preferences. The Settings section allows organization-level management by any member of the Project Collection Administrators group. All teams and groups inherit the Default delivery option setting, which isn't explicitly set at the team or group level.
For more information, see Manage team, group, and global notifications.
Permissions for notifications
There are no UI permissions associated with managing email notifications or alerts. Instead, you can manage access by using the TFSSecurity command line tool.
- By default, members of the project level Contributors group can subscribe to alerts for themselves.
- Members of the Project Collection Administrators group, or users who have Edit collection-level information permission, can set alerts for others or for a team, within that collection.
- Members of the Project Administrators group, or users who have Edit project-level information permissions can set alerts in that project for others or for a team.
Preferred email address
By default, the preferred contact email address for your organization profile receives notifications. This email address is usually the same address you use to sign into Azure DevOps. You can manage this email address from your organization preferences profile page.
If you're enrolled in the Microsoft Entra profile information preview, your profile information is pulled directly from Microsoft Entra and can't be edited. For more information, see Set your preferences.
Note
Your preferred contact email address applies to all your organizations and can't be changed on a per-organization basis.