---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create a notification destination

# Create a notification destination in SRM {#ariaid-title1}

* Release version: Yokohama
* 
* Updated June 17, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Set up notification destinations to help keep teams informed about service reliability.

## Before you begin

Before creating notification destinations, set up the Microsoft Teams Graph spoke. When registering an application in the Microsoft Azure portal, grant the following Microsoft Teams Graph API permissions:

* `ChannelMessage.Send`
* `Group.ReadWrite.All**`

{#create-notification-destination__ul_o1k_ngy_vfc}For setup instructions, see [Set up the Microsoft Teams Graph spoke](https://www.servicenow.com/docs/access?context=set-up-msteams&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US).

Role required: srm_manager, srm_admin, or admin

## About this task

Create a notification destination to deliver messages to a specific Microsoft Teams channel. After you set up a notification destination, team members can attach it to error budget policies to receive messages about policy breaches.

## Procedure

1. Navigate to WorkspacesService Operations Workspace.
2. From the primary navigation, select Teams (![Teams icon]()).
3. On the Teams page, select the team you want to use the notification destination.
4. Select the SLO Notification destinations tab, select Create a destination, and then fill out the form.

   | Field | Description |
   | Channel URL | Deep link to the relevant Microsoft Teams channel. You can find deep links to channels in Microsoft Teams. They follow this general format: `https://teams.microsoft.com/l/channel/19%abcdef`. |
   | Destination name | Display name of the notification destination. Teams see this name when adding notification destinations to error budget policies. |
   |-|-|

   {#create-notification-destination__choicetable_q13_wwy_vfc}
5. **Optional:** Select Send test notification to verify your setup.  
   When successful, a message appears in the relevant Microsoft Teams channel. The message is titled `Test Notification` and includes the following text:

       This is a test notification from the Service Reliability Management (SRM) Team '<team-name>'.

6. Select Save.  
   The notification destination appears in the SLO Notification destinations tab. The table includes details about the Microsoft Teams channel and when the notification destination was last updated.

## What to do next

To use and learn more about notification destinations, visit the following pages:

* [Create SLOs, SLIs, and error budget policies](https://servicenow-prod.fluidtopics.net/PAyr1az_9UN3VPV1pJtwxA "Define service level objectives (SLOs), service level indicators (SLIs), and error budget policies to monitor service health. These tools help you and your teams track performance and take action when needed.")
* [Notifications for breached error budgets](https://servicenow-prod.fluidtopics.net/3LiEV19_7gR~c34bJWBnXw "Details about the notifications that teams receive for breached error budget policies.")
{#create-notification-destination__ul_ukt_w4h_wfc}

You can also edit and delete notification destinations from the SLO Notification destinations tab. Deleting a notification destination removes it from all error budget policies where it was previously used.

*[\>]: and then