Microsoft Teams (combined)

Introduction

Integrate Microsoft Teams (Teams) with OX to receive real-time security alerts, incident updates, and workflow notifications directly in MS Teams channels.

This integration streamlines incident management, reduces response time, enhances team collaboration, and enables you to:

• Send a Teams message about an issue

• Add a Teams message to a workflow

Connection methods

For general information about connection methods, see Connection methods.

To connect Teams to OX, use one of the following two connection methods:

• Identity provider: OX sends notifications using your individual Microsoft user identity. You connect by authenticating to Microsoft directly from OX.

• Bot identity provider: Sends Teams notifications from a unified "OX Security" app identity instead of individual user accounts. This method centralizes deployment via Teams policies and provides direct links from notifications to OX issues and workflows.

Permission scopes

OX requests the Microsoft Graph and OpenID Connect permissions for the Microsoft Teams integration. OX declared these permissions when it registered its application in Azure. Microsoft grants the permissions when you connect and complete the Microsoft consent flow.

Permissions (A-Z)	Description
Channel.ReadBasic.All	Reads basic channel properties (name, description, type). Allows OX to select a channel when sending notifications. OX lists channels inside the selected team to populate the UI so messages are sent to the correct channel.
ChannelMessage.Send	Sends messages to team channels (both standard and private). Required to permit OX to send security alerts and notifications to your selected Teams channels.
Chat.Create	Creates new 1:1 or group chats for private notifications when no existing conversation exists.
Chat.ReadWrite	Reads and sends messages in chats where the app participates, including 1:1 and group notifications.
offline_access	Maintains persistent connection to Teams without requiring users to repeatedly sign in. Enables OX to automatically renew expired access tokens so notifications and integrations continue working uninterrupted.
openid	Enables Microsoft sign-in and single sign-on (SSO) so users can authenticate and connect their Teams environment to OX using their work account credentials.
Team.ReadBasic.All	Reads team and channel names and IDs for channel notification configuration. Requires admin consent.
User.Read	Reads signed-in user profile (name, email, ID) to identify connected user and list joined teams
User.Read.All	Reads basic profile information for all organization users to enable notification recipient selection and 1:1 chat resolution. Requires admin consent.

Prerequisites

Connection method	OX	Microsoft Teams
Identity provider	Permission to configure connectors	Microsoft Teams account (Optional) Administrative access to Microsoft Azure Admin Center Permissions to manage enterprise applications in Azure
Bot identity provider	Permission to configure connectors	Microsoft Teams account Microsoft Teams admin with permission to manage apps and policies in the Teams Admin Center

Connect with Identity Provider

1. Verify that the prerequisites are in place.

2. In the OX app, go to Connectors > Dev Alerts > Microsoft Teams and select IDENTITY PROVIDER.

   
3. Select CONNECT. The Microsoft Teams connector is configured.

4. When prompted, you will be asked to approve access to organization resources. For the list of permissions, see the section Permission Scopes.

5. Select Accept.

Connect with the Bot Identity Provider

Step 1: Connect to OX [OX]

1. Verify that the prerequisites are in place.

2. In OX, go to Settings > Connectors > Dev Alerts > Microsoft Teams and select BOT IDENTITY PROVIDER.

   
3. In Configure your Microsoft Teams credentials, select CONNECT.

4. When prompted, you will be asked to approve access to organization resources. For the list of permissions, see the section Permission scopes.

5. Complete the Microsoft consent flow, then return to OX and confirm that the connector shows Connected.

Step 2: Publish the OX Security app to your Teams tenant [Microsoft]

1. Verify that the prerequisites are in place.

2. Go to the Teams Admin Center.

3. Go to Teams apps > Manage apps. Search for OX Security and open the app from the Azure Marketplace.

   
4. If your policies require it, set the app to Allowed for your organization.

5. Go to Teams apps > Setup policies.

6. Create a new app setup policy or edit an existing one. For example, edit the default policy Global (Org-wide default).

   
7. In Add installed apps, select the OX Security Alerts app.

   
8. Select Add. This installs the app for all users covered by the policy.

Verify OX permissions in Microsoft Entra Admin Center

After connecting, you can view and verify the permissions granted to OX.

1. Go to the Microsoft Entra Admin Center, log in, and select Applications > Enterprise Applications.

   
2. From the right pane, select OXSecurity. The Permissions page displays the current permissions which you can modify, if needed.

   

Send a Teams message about an issue

1. In the OX app, go to Active Issues and select the issue.

   

   You can also select the Teams icon from the bottom of the screen.

2. Right-click the 3 dots and select Send message to Teams.

3. In Send message to Teams, add recipients and a comment, then select SEND.

   

Add a Teams messages to a workflow

You can configure workflows to automatically send Teams notifications when specific conditions are met.

1. In the OX, go to Workflows and select the relevant workflow.

2. Find the workflow step where you want to add the Teams notification and select +

3. Select Action > Teams.

   
4. In Active Settings, complete the details in the table.

   

Item	Description
Recipients	Required
Fallback recipients	Required
Add your own comment	Optional, but good practice.
Apply to	Select one of the triggers: Updated Issues, New or Updated Issues, New, Updated or Existing Issues, or Periodic

1. Select ADD. The new Teams action appears in the workflow and triggers on the selected action.