Back to Changelog
Back to Changelog

July 6, 2022


Microsoft Teams Integration

Microsoft Teams Integration

📹 Microsoft Teams Integration

We are excited to announce our video conferencing integration with Microsoft Teams.

As we further our market leading position for enterprise readiness, organizations will now be able to collaborate over Teams for high bandwidth conversations as they tackle incidents.

  • Create a Teams bridge automatically whenever an incident starts
  • Automatically bookmark Teams bridge to incident channel for easy access
  • Edit/replace Teams bridge link (e.g. if an existing one is already in use)
  • Leverage workflows to dynamically create Teams bridge (e.g. only SEV0 and SEV1 require a call)

Our Teams integration sits alongside other video conferencing tools already supported such as Zoom, Google Meet, Slack Huddles, Webex, and more.

Docs for getting started:

🌝 New & Improved

  • 🆕 Specify notification channel whenever a workflow fails to run, found in Profile > Organization Settings
  • 🆕 Service dependencies inside of Rootly service catalog
  • 🆕 Alerts (e.g. PagerDuty) that Rootly pipes into Slack can now be customized with specific messaging and CTA buttons (e.g. create incident, link to alert, etc.), found in Workflow > Alerts
  • 🆕 Workflow triggers for custom fields (e.g. custom field updated, etc.)
  • 🆕 Action items can be exported to PDF
  • 🆕 Incident timestamps (acknowledged, detected, started, mitigated, resolved) can be used as a workflow condition (set or unset)
  • 💅 Paging responders in Slack modal now separates escalation policies and users instead of combining
  • 💅 UI polishes around workflows and tasks
  • 💅 Infrastructure enhancements that makes bulk emailing and inviting users to Rootly better
  • 💅 Migration from PagerDuty webhook v2 to v3, enables additional event types around signal changes to incident severity, responders, and all around better sync between the two
  • 💅 Alerts tab added to main navigation menu in Web platform and Pulses is now nested under configuration
  • 🐛 Fixed issue where some users were prompted to reintegrate PagerDuty
  • 🐛 Fixed issue where workflow conditions for action items could run into a race condition
  • 🐛 Fixed issue where elapsed time in Slack did not update
  • 🐛 Fixed issue where clicking on an related active incident in Web platform did not redirect you to active incident channel
Previous post
Previous post
You are viewing the latest post

👯‍♀️ On-Call Shadowing

🔌 Generic Webhook Alert Source

🔒 Lock Individual Workflows

🐦‍⬛ Round Robin Escalation Policies

🚨 Alert Sources

🔔 Configurable On-Call Shift Reminders

🪄 Dynamic Forms

🔐 Granular Role-Based Access Control Settings for On-Call

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on

🔦 Drop-down Search in Escalation Policy Builder

🦊 GitLab Integration

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command