Skip to main content

Netskope Help

Microsoft Teams Plugin for Ticket Orchestrator

This document explains how to configure your Microsoft Teams integration with the Ticket Orchestrator module of the Netskope Cloud Exchange platform.


To complete this configuration, you need:

  • A Netskope Tenant (or multiple, for example, production and development/test instances)

  • A Netskope Cloud Exchange tenant with the Ticket Orchestrator module already configured.

  • A Microsoft Teams account.

  1. Create an Incoming Webhook URL.

  2. Configure the Microsoft Teams plugin.

  3. Configure Ticket Orchestrator Business Rules for Microsoft Teams.

  4. Configure Ticket Orchestrator Queues for Microsoft Teams.

  5. Validate the Microsoft Teams Plugin.

Click play to watch a video.


If you already have a team and channel created, jump to step 3.

  1. To get an Incoming webhook URL, log in to your Microsoft Teams account and then click on Teams in the left panel. Click Create Team and then From scratch to create a basic team.

  2. Click Public, enter a Team Name, and click Create. After creating a team, the option to add team members can be skipped.

  3. Click on Add channel by clicking the menu image3.png icon besides the team. Enter the name of your channel for Channel Name and click Create App.

  4. Click Apps in the left panel,. Click Add to Team, enter a Channel Name, and then click Set up a connector.

  5. To set up a webhook, provide a name, and click Create.

  6. Click Copy to get the newly generated webhook URL. This will be used when configuring the Microsoft Teams plugin.

  1. In Cloud Exchange, go to Settings > Plugins.

  2. Search for and select the Microsoft Teams plugin box to open the plugin creation page (make sure Ticket Orchestrator is enabled. If not, go to Settings > General and enable the Ticket Orchestrator module).

  3. Enter a Configuration Name and click Next.

  4. Enter the Webhook URL from your Microsoft Teams account.

  5. Click Save.

  1. Go to Ticket Orchestrator and click Business Rules.

  2. Click Create new rule.

  3. Enter an appropriate Rule Name and build the appropriate filter query condition on field(s) for the business rule. You can also type the query manually by clicking Filter Query.

  4. Click Save.

  5. To create Mute Rule(s) and/or Deduplication Rule(s) for this business rule, click on the Business Rule you created.

  6. Click on the round “+” icon to create a new Mute Rule/Deduplication Rule.

  7. Enter a Rule Name, build the appropriate condition, and then click Save.

  8. Similarly, Deduplication Rule(s) can be created.

  9. To test the newly created business rule, click the refresh image15.png icon, enter a time period (in days), and click Fetch. This shows the number of alerts that are eligible for incident/ticket creation.

  1. Go to Ticket Orchestrator and click Queues.

  2. Click Add Queue Configuration.

  3. Select your previously created Business Rule from the dropdown.

  4. Select the plugin Configuration from the dropdown for which the queue is being configured.

  5. Select the Queues from the dropdown. For the Microsoft teams plugin, it should be a Notification queue.

  6. Add/Map appropriate values between alerts and notification in the Map Field section. Alert’s attributes can be accessed via “$” in the custom message field. Click on the Add button to add more field mappings.

  7. Click Save.

  8. Based on the business rule(s), Notifications for incoming alerts will be sent automatically to the configured channel. To create notifications for historical alerts, click the refresh image15.png icon on the configured queue, enter the Time period (in days), and click Fetch. This shows the number of alerts that are eligible for sending notifications. Click on the Sync button to send the notification(s).


In order to validate the workflow, you must have Netskope Alerts.

  1. Go to Ticket Orchestrator and click Alerts.

  2. To view the message(s) sent to Teams, go to your configured channel.

  3. If notifications are not being sent to Teams, you can look at the audit logs in Cloud Exchange. In Cloud Exchange, click Logging to look through the logs for errors.