Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Frelease-notes%2Fnotification-center.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Frelease-notes%2Fnotification-center.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Notification Center

Jun 2026

Native Microsoft Teams connector

[![Microsoft Teams listed as a connector type in the Notification Center Connectors screen, alongside Slack, PagerDuty, ServiceNow, Generic HTTPS, and Email](/docs/assets/images/msteams-connectors-list-c4dd1ae30bc23b229e45b94f015fb3c4.png)](https://coralogix.com/docs/docs/assets/images/msteams-connectors-list-c4dd1ae30bc23b229e45b94f015fb3c4.png)

Route Coralogix alert and Case notifications to Microsoft Teams through a native connector, the replacement for the retired Office 365 incoming webhooks. A Teams administrator installs the Coralogix app in your tenant, then you pick a channel by link or by ID. Case lifecycle changes (assign, acknowledge, resolve, and close) reflect in the Teams message and on the Case timeline in near real time, with an option to keep updates in a single thread. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/destination-types/msteams/.md)**

Jun 2026

Dynamic field builder for connectors

[![Channel field in Query mode with All entities turned off and separate Cases and Alerts expressions](/docs/assets/images/dynamic-field-query-per-entity-7006304a5655df3fcada47382a89b3cb.webp)](https://coralogix.com/docs/docs/assets/images/dynamic-field-query-per-entity-7006304a5655df3fcada47382a89b3cb.webp)

Build dynamic connector routing without writing Tera. A builder mode on dynamic fields (Channel, Email addresses, Service key) lets you set conditions on alert or case priority, name, and labels, then route to the matching channel, recipients, or service. Conditions combine with AND within a row and OR across rows, with the first match applied, and a required fallback value covers anything that does not match. Define the routing once and reuse one connector across many routers, instead of creating a connector per team or channel. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/connectors/advanced-configuration/.md#use-the-dynamic-field-builder)**

Jun 2026

Service Catalog integration for ownership labels

[![GIF showing creation of router](/docs/assets/images/create-a-router-a3efd638b2071918404ba8b7e5506900.webp)](https://coralogix.com/docs/docs/assets/images/create-a-router-a3efd638b2071918404ba8b7e5506900.webp)

Set ownership labels by choosing a service from the APM Service Catalog instead of typing it as free text. Ownership labels decide which team is notified and which service an alert or Case belongs to, so picking a real catalog service (tagged **Catalog**) ties alerts and Cases to the correct APM entity and routes them to the right team. This avoids the typos and near-duplicate names that can leave a notification linked to the wrong service, or to none. Free text still works (tagged **Custom**) for services not yet in the catalog. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/routing/create-router/.md)**

Mar 2026

Cases entity type and condition templating

[![Cases and Alerts tabs in a router](/docs/assets/images/cases-alerts-tabs-e2067bb972eeba419db82311bc477e7d.webp)](https://coralogix.com/docs/docs/assets/images/cases-alerts-tabs-e2067bb972eeba419db82311bc477e7d.webp)

Cases as a notification entity type — Notification Center now supports Cases alongside Alerts as an entity type. Create routing rules that trigger on Case lifecycle events, use Ownership Tags for Case routing, and define Case-specific conditions and destinations. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/routing/define-routing-rule/.md)**

Condition templating for routing rules — Write advanced routing rule conditions using Tera templates. Includes support for alert name matching, label checks, regex patterns, case status and severity conditions, and entity-type routing. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/routing/condition-templating/.md)**

ServiceNow destination type — ServiceNow is now available as a Notification Center destination, enabling incident creation and management directly from Coralogix notifications. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/destination-types/introduction/.md)**

JSM (Jira Service Management) configuration via HTTPS — Configure Jira Service Management as a notification destination alongside OpsGenie. Includes JSM connector setup, Atlassian API endpoints, message presets, and a migration guide reflecting OpsGenie deprecation. **[Learn more](https://coralogix.com/docs/docs/user-guides/notification-center/destination-types/https/.md)**

notification.deliveries dataset update — The `notification.deliveries` dataset is now enabled by default at no cost. Alerts record delivery failures only, while Cases record both successful and failed deliveries.