Spike.sh
DashboardWebsiteHUB
Spike.sh
Spike.sh
  • Introduction
  • What is Spike.sh?
  • Incidents
    • What is an incident?
    • Incident lifecycle
    • Incident statuses
    • How to change incident status?
    • Acknowledge timeout
    • Grouping incidents
    • Priority and Severity
    • Mute alerts
    • Reassign incidents
    • Sharing incidents
    • Why does message parsing fail?
    • Rate limiting on duplicate incidents
  • Alerts
    • Phone
    • SMS
    • Mobile app alerts
    • E-mail
    • Slack
    • Microsoft Teams
    • WhatsApp
    • Telegram
    • Pushover
    • Discord
    • Alert rules
    • Title Remapper
    • Personal alerts management
      • During office hours
      • Out of office
      • Resolved incident alerts
      • Deep work & Cooldown modes
  • Services
    • Introduction to services on Spike
  • Escalations
    • Introduction to escalations
    • How to create an escalation policy?
    • Repeat escalations
    • Archive escalation policy
  • Collaboration
    • Task management integrations
      • JIRA Cloud
      • JIRA server (self-hosted)
      • ClickUp
      • Linear
      • Shortcut
    • Helpdesk integrations
      • Zendesk
      • Freshdesk
      • Supportpal
    • War rooms
  • On-call schedules
    • Introduction to On-call schedules
    • Create On-call schedule
    • Introduction to Slots in schedules
    • Introduction to Layers in on-call schedules
    • Override an on-call
    • Add on-call schedule to your calendar
    • Notifications for on-call shifts
    • Change on-call rotation day
  • Playbooks
    • Introduction to Playbooks
    • Actions in Playbooks
    • Automating your Playbooks
    • Run Playbooks manually
  • Status Pages
    • Create Status page
    • Style your status page
    • Incidents on status page
    • Create Planned Maintenance on status page
    • Edit Planned Maintenance
    • Add custom domain to status page
    • Manage your subscribers
    • Embed status page notifications on your website
    • Live status widget
  • Uptime
    • Create Uptime monitor
    • Link uptime to Status Page
  • Integrations guidelines
    • Create integration and service on our dashboard
    • Setup integrations
    • Archive an integration
    • Integrating with Webhooks
    • Integrate Spike with Email
    • Integrate Spike with AWS
    • Integrate Spike with Google Cloud
    • Integrate Spike with Sematext
    • Integrate Spike with Healthchecks
    • Integrate Spike with Pingdom
    • Integrate Spike.sh with Sentry
    • Integrate Spike with Apex ping
    • Integrate Spike with Uptime Robot
    • Integrate Spike with Twilio
    • Integrate Spike with Microsoft Azure
    • Integrate Spike with Honeybadger
    • Integrate Spike with Rollbar
    • Integrate Spike with Travis CI
    • Integrate Spike with Heroku
    • Integrate Spike with Datadog
    • Integrate Spike with Axiom
    • Integrate Spike with Needle.sh
    • Integrate Spike with Cronitor
    • Integrate Spike with Bugsnag
    • Integrate Spike with Grafana
    • Integrate Spike with Prometheus
    • Integrate Spike with Instana
    • Integrate Spike with Zapier
    • Integrate Spike with Librato
    • Integrate Spike with Checkly
    • Integrate Spike with AppSignal
    • Integrate Spike with New Relic
    • Integrate Spike with Site24x7
    • Integrate Spike with Stackify
    • Integrate Spike with Scout-apm
    • Integrate Spike with Oh-Dear
    • Integrate Spike with Nixstats
    • Integrate Spike with Server Density
    • Integrate Spike with Raygun
    • Integrate Spike with Lightstep
    • Integrate Spike with Runscope
    • Integrate Spike with Honeycomb
    • Integrate Spike with Graylog
    • Integrate Spike with Checkmk
    • Integrate Spike with Hyperping
    • Integrate Spike with Epsagon
    • Integrate Spike with Uptime
    • Integrate Spike with Splunk
    • Integrate Spike with Sumo Logic
    • Integrate Spike with Thousand Eyes
    • Integrate Spike with Loggly
    • Integrate Spike with Elastic Cloud
    • Integrate Spike with App Optics
    • Integrate Spike with NodePing
    • Integrate Spike with Scalyr
    • Integrate Spike with Moogsoft
    • Integrate Spike with AppDynamics
    • Integrate Spike with Dynatrace
    • Integrate Spike with CopperEgg
    • Integrate Spike with Coralogix
    • Integrate Spike with ElastAlert
    • Integrate Spike with LogDNA
    • Integrate Spike with Zebrium
    • Integrate Spike with LibreNMS
    • Integrate Spike with Uptime Kuma
    • Integrate Spike with Logentries
    • Integrate Spike with Logz
    • Integrate Spike with Ghost Inspector
    • Integrate Spike with Hetrix Tools
    • Integrate Spike with LogRocket
    • Integrate Spike with StatusCake
    • Integrate Spike with Sysdig
    • Integrate Spike with Wavefront
    • Integrate Spike with Buildkite
    • Integrate Spike with Semaphore
    • Integrate Spike with Better Uptime
    • Integrate Spike with Hexowatch
    • Integrate Spike with PM2
    • Integrate Spike with Cloudflare
    • Integrate Spike with Zabbix
    • Integrate Spike with Tenderly
    • Integrate Spike with Xitoring
    • Integrate Spike with Crowdstrike
    • Integrate Spike with GitHub Workflows
    • Integrate Spike with Solarwinds Orion
    • Integrate Spike with Airbrake.io
    • Updown.io
  • Administration
    • Roles and access
    • SSO
    • Enforce login
    • Our notification numbers
    • Contact the support team
    • Adding team members
    • Check if team is getting alerts
    • Removing team members
  • Additional resources
    • Create a badge
Powered by GitBook
On this page
  • Getting Started with the Spike App on Microsoft Teams
  • Available Commands
  • Setting Up Incident Alerts with the Spike App
  • Direct Messages (DMs)
  • Connecting multiple groups on Teams
  • Get Teams alerts from Spike.sh using Incoming Webhook (to be deprecated)
  • How to set up Teams?

Was this helpful?

Edit on GitHub
  1. Alerts

Microsoft Teams

Get alerts on your Microsoft Teams from Spike.sh

PreviousSlackNextWhatsApp

Last updated 6 months ago

Was this helpful?

Our Microsoft Teams app simplifies incident management by delivering alerts directly to your Teams channels and enabling you to take immediate actions. Below is a quick overview of the available features:

  1. Receive Incident Alerts: Get real-time incident alerts directly in your Teams channels

  2. Create Incidents from Teams: Seamlessly create new incidents directly from within Microsoft Teams and keep your workflow uninterrupted.

  3. Manage Incidents: Easily acknowledge, resolve, or escalate incidents.

  4. On-call Notifications: Receive direct messages for the start and end of your on-call shifts, invitations to join a war-room, and notifications when you're mentioned in a comment on Spike.sh.

  5. On-Call Shift Information: Quickly check who is currently on-call and get details about your current and upcoming on-call shift timings.

directly or search for "Spike.sh" in the Teams Apps section on the sidebar. If you need assistance with installation due to permission restrictions, please contact your Teams admin.

If you're unable to install the app, you can still receive alerts by using the Incoming Webhook connectors. Scroll down for detailed setup instructions.

Getting Started with the Spike App on Microsoft Teams

After installing the app, you'll receive a message with instructions on how to connect your Spike account. For full functionality, we recommend using both the connect and connect-org commands.

  • The connect command links your personal Spike account with Teams, enabling direct messages for on-call shift notifications and when you are mentioned in a comment.

  • The connect-org command links your organization’s Spike account with Teams. This will enable your org to receive actionable incident alerts in channels.

For the best experience, we suggest running both commands.

Available Commands

  • New incident:

    • /create-new-incident - Create a new incident from Teams

  • Am I on-call?:

    • /oncall-me - Check if you are on-call and when your shift ends.

  • Who is on-call?:

    • /oncall-now - See who is currently on-call.

  • Disconnect:

    • /disconnect - Disconnects your Spike account from Teams. Note: This will only disconnect your personal account. Incident alerts will continue to be available in channels.

Setting Up Incident Alerts with the Spike App

Once your account is connected, you can easily add any of your Teams channels to an escalation policy. To do this, select "Teams" in the escalation policy, and your available channels will automatically appear on the right-hand side.

Any team member can take action on an incident directly from Teams. We recommend creating a dedicated channel for responders to receive and manage alerts. If an incident is acknowledged or resolved via the Spike dashboard, phone call, email, or any other medium, the latest incident will be automatically reflected in the Teams channel, along with the suppressed and repeated counts.

Direct Messages (DMs)

After running the connect command, you can use the oncall-me and oncall-now commands to get information about your on-call schedules directly in Teams. You will also receive direct messages from Spike.sh for important notifications, such as:

  1. Invites to War rooms

  2. Mentions in comments

  3. The ability to create new incidents directly from Teams

  4. Your on-call shift alerts

Connecting multiple groups on Teams

Since our bot can only be connected to one group at a time, you'll need to disconnect the current group and then reconnect to the new one.

You can easily connect the Spike bot to multiple groups of channels in Microsoft Teams. Follow these steps:

  1. Go to the desired group in Microsoft Teams and type @Spike.sh connect-org to establish the connection.

  2. Next, visit your escalations page, and you'll see the newly connected channels listed in the dropdown menu.

There is no limit on how many groups can be connected.


Get Teams alerts from Spike.sh using Incoming Webhook (to be deprecated)

Microsoft will deprecate all new webhook connectors on 15th September. On Spike, we will deprecate the incoming webhook support on 26th November 2024.

The alert messages on Microsoft Teams (referred to as Teams from here on) comes with gists for you and your team to quickly learn about the incident.

How to set up Teams?

Step 1 - Setup incoming webhook

Go to the Apps section in your teams account and install the Incoming Webhook app (created by Microsoft).

Select a channel of your choice and click setup connector

Step 2 - Paste the URL on Spike.sh

Make sure to paste the exact URL from above. Any changes in the URL might result in missing alerts

Once integrated, we will send a sample alert to your configured Teams channel

A friendly name will help you identify this integration while creating escalation policies. Like below -

You can create multiple Teams integrations with different incoming webhooks configured on Teams.

Name your connector and upload our Spike.sh logo so as to easily identify alerts coming from us.

Head over to Spike.sh dashboard and visit and create a Teams integration by giving a friendly name along with the URL you copied from step 1.

You can download our logo here.
settings > organisation > alerts
Install our Teams app
How incident alerts look on Teams
How incident alerts look on Teams
How incident alerts look on Teams
Install the Incoming Webhook app
Submit the form and then copy the unique URL
Using Teams in Escalation policies