The Splunk>VictorOps for MS Teams Integration allows teams to work from MS Teams while leveraging the notification and coordination capabilities of VictorOps.
- MS Teams Account: May Require Organization Admin Permission to Integrate
- VictorOps Version Required: Getting Started, Essentials, or Enterprise.
First, install the app to your Teams organization instance.
NOTE: The user installing the app must have organization admin privileges in MS Teams for this step.
Next, add the app to a team to install the VictorOps bot. This can be done by any user.
NOTE: By selecting one channel in the team, the app installs to all channels in that team.
Once installed and added, the app needs to be configured for first-time use. Currently, the VictorOps for MS Teams app is set up for a single VictorOps organization to MS Teams organization relationship.
NOTE: Configuration is visible to any user but can only be completed by an organization administrator with a corresponding VictorOps account using the same email address. Member-level users who attempt to configure the app will immediately sees unauthorized message.
After adding, installing, and configuring the app, you will need to subscribe each channel to receive traffic from VictorOps.
NOTE: Subscribing to one channel does NOT subscribe to any other channels in that team.
How the App Works
VictorOps will route incident to the appropriate channel based on the mapping established in the configuration. After subscribing, users may acknowledge and resolve incidents in MS Teams.
The application handles both single- and multi-responder incidents.
Currently, a new card is generated with every incident event – creation, ack/resolve, adding responders and conference bridges.
Unsubscribing at the channel level does not remove the bot, and doesn’t impact other channels for that (or any other) team.
Deleting the app from the team level automatically unsubscribes all channels from that team, without affecting other teams’ subscriptions.
NOTE: Deleting from the org level does NOT unsubscribe currently due to a limitation in Teams. We’re currently working on figuring out a workaround.