Overview
A notification channel is the delivery pathway through which Turbo360 sends alerts and warnings generated by your monitoring configuration. When a monitor triggers (due to a budget breach, anomaly, application health issue, or any other configured condition) Turbo360 routes the notification to one or more channels you have set up.
Notification channels are configured globally under Settings and are shared across all modules. This means a single channel configuration can receive alerts from Cost Analyzer, Business Applications, Business Activity Monitoring, and Azure Documenter.
Business value
Relying solely on email for monitoring alerts creates gaps: messages can be missed, buried, or delayed. Notification channels let you route alerts to the tools your team already uses, ensuring the right people are notified through the right medium at the right time. This reduces mean time to respond (MTTR) and ensures monitoring events are actioned rather than overlooked.
Prerequisites
- A Turbo360 account with at least one module active
- Account Owner access, or a custom role with the Manage notification channels permission enabled
Required permissions
Notification channel management is restricted to the following:
- Account Owner: full access by default
- Custom role with Manage notification channels enabled: the Manage notification channels permission is available under Specify account permissions when creating a role in any module (Cost Analyzer, Business Applications, Business Activity Monitoring, or Azure Documenter). When enabled, it allows users to add, update, and remove notification channels globally, regardless of the module the role was created in or the group node it is scoped to.
To grant this permission to a user, navigate to User management > Roles, create or edit a custom role in any module, and enable Manage notification channels under Specify account permissions.
Note: The Manage notification channels toggle appears in the Specify account permissions section at the bottom of the role configuration panel. It is available regardless of which module the role is being created in.
Dependencies
- At least one monitor or alert rule must be configured to use a notification channel after setup
How it works
Notification channels are configured once in Settings and then selected when configuring monitors, alert rules, or escalation policies across any module. When a condition is met, Turbo360 evaluates the monitor's configuration and dispatches the notification payload to each assigned channel.
Each channel type handles delivery differently: some create work items, some send messages, some trigger external APIs. The channel configuration stores the connection details (such as webhook URLs, API keys, or SMTP credentials) so Turbo360 can authenticate and deliver the notification.
Steps
Use the following steps to add a notification channel. Navigate to Settings > Notification channels to get started.
- Navigate to Settings > Notification channels.
- Select Add notification channel. If no channels have been set up yet, select Configure instead. A panel opens listing all supported channel types.
- Select the channel type you want to configure from the list.
- Enter the required connection details for the selected channel.
- Select Save. The channel is now available for selection in monitor and alert rule configurations across all modules.
Configuration
Turbo360 supports 11 notification channel types. The table below summarises each channel and its common use cases.
| Channel | What it does | Common use cases |
|---|---|---|
| Azure Monitor | Logs an event to an Azure Log Analytics workspace | Feed events into existing log ingestion pipelines or third-party systems |
| Azure DevOps | Creates a work item in Azure DevOps | Log a work item when an application is unhealthy; assign cost optimization tasks |
| Jira | Creates a work item in Jira | Log a work item when an application is unhealthy; assign cost optimization tasks |
| Microsoft Teams | Sends a message to a Teams channel | Notify team members of monitoring alerts in real time |
| Opsgenie | Creates an incident or alert in Opsgenie | Trigger an alert when an application becomes unhealthy |
| PagerDuty | Sends an SMS notification | Alert on-call responders when an application is unhealthy or costs exceed thresholds |
| ServiceNow | Logs a ticket in ServiceNow | Log tickets for unhealthy applications, cost increases, or resource optimization tasks |
| Slack | Posts a message to a Slack channel | Notify teams of unhealthy applications or cost increases |
| SMTP | Sends an email via your mail server | Send email alerts for unhealthy applications or cost increases |
| Twilio | Sends an SMS via Twilio | Alert on-call users when an application is unhealthy |
| WebHook | Sends a payload to a custom endpoint | Trigger external APIs or integrations in response to a notification |
Each channel type requires its own set of connection credentials. Refer to the individual channel articles for configuration details.
Permission behavior
With Manage notification channels permission:
You can add, edit, and delete notification channels in Settings > Notification channels. Changes apply globally and affect all modules that reference the channel.
Note: In Settings > Notification channels, users with this permission see the full channel list along with options to Add notification channel, edit existing channels, and delete channels.
Without Manage notification channels permission:
The Settings > Notification channels section is not accessible. You can still select existing channels when configuring monitors or alert rules within your role's permitted scope, but you cannot create or modify channel configurations.
Example scenario
A DevOps team running Cost Analyzer and Business Applications wants critical alerts routed to their Teams channel and high-severity incidents logged in ServiceNow. The Account Owner configures both channels once under Settings > Notification channels. When setting up a budget alert in Cost Analyzer and an application health monitor in Business Applications, the team selects these channels from the notification channel list with no duplicate configuration required.
Limitations
- Notification channels are configured globally and cannot be scoped to a specific module, group, or child node. Any user with the Manage notification channels permission can manage all channels across the platform.
- Deleting a notification channel removes it from all monitors and alert rules that reference it. There is no automatic reassignment.
- Each channel supports validation during configuration. Upon successful validation, a test notification is sent for confirmation.
Troubleshooting
-
Notification channel option not visible in Settings.
Cause: The user does not have the Manage notification channels permission enabled on their role.
Fix: Ask an Account Owner to enable the Manage notification channels toggle under Specify account permissions when creating or editing the user's role in any module. -
Notifications not being delivered to the channel.
Cause: The connection credentials entered during channel setup (webhook URL, API key, SMTP credentials, etc.) may be incorrect or expired.
Fix: Navigate to Settings > Notification channels, edit the affected channel, and verify or re-enter the credentials. -
Channel was deleted and monitors stopped sending alerts.
Cause: Deleting a notification channel removes it from all monitors that referenced it.
Fix: Recreate the channel under Settings > Notification channels and reassign it to the affected monitors or alert rules. -
User can see channels in monitor configuration but cannot manage them in Settings.
Cause: The user's role permits them to configure monitors (read/manage at feature level) but does not include the Manage notification channels account permission.
Fix: This is expected behavior. To allow the user to manage channels, an Account Owner must enable Manage notification channels on their role in any module. -
Notifications received from one module but not another.
Cause: The notification channel may be assigned to monitors in one module but not configured in the monitors of the other module.
Fix: Review the monitor and alert rule configurations in the affected module and confirm the correct notification channel is selected.
FAQs
-
Can I use the same notification channel across multiple modules?
Yes. Notification channels are global and can be selected in any monitor, alert rule, or escalation policy across Cost Analyzer, Business Applications, Business Activity Monitoring, and Azure Documenter. -
Can a non-Owner user manage notification channels?
Yes, if they have been assigned a custom role with the Manage notification channels permission enabled under Specify account permissions. This permission grants global channel management access regardless of the module the role was created in or the role's scope. -
Does enabling Manage notification channels on a module-scoped role grant access to other modules?
The permission grants access to manage notification channels in Settings globally, but does not extend the user's module-level permissions beyond what their role already defines. -
Where do I assign a notification channel to a monitor?
Within each module's monitor or alert rule configuration. The channel list is populated from the channels configured in Settings > Notification channels.