Prerequisites
In order to configure the integration, you will need the following:
- One of the following roles in Microsoft Entra: Global Administrator, Privileged Role
Administrator, User Administrator, Privileged Authentication Administrator, License
Administrator - Your Microsoft Teams Directory (tenant) ID
- A Entra user to act as the service account for the integration
Create the Risk Cloud Teams User in Entra
- In Entra ID, navigate to Users
- Click Create new user
- Select Create new user
- Create a new user with a name and email that will identify it as a Risk Cloud integration
- Disable Per-user MFA
- Assign any necessary Group memberships and Licenses your organization requires to
interact with the Teams channels and members that Risk Cloud will send notifications
to
Create the Risk Cloud Teams Application in Entra
- In Entra ID, navigate to App registrations
- Click New Registration
- Enter a name that will identify the application as your Risk Cloud integration
- For “Who can use this application or access this API?” select “Accounts in this organizational directory only”
- Click Register
- Copy the Directory (tenant) ID which will be used later in Risk Cloud
- Select API Permissions
-
Add the following permissions
- ChannelMessage.Send
- Chat.Create
- ChatMessage.Send
- Group.Read.All
- offline_access
- Team.ReadBasic.All
- TeamMember.Read.All
- TeamsUserConfiguration.Read.All
- User.Read
- User.ReadBasic.All
- Click Authentication
- Set “Allow public client flows” to No
Connect your Teams Integration to Risk Cloud
2. Find the Microsoft Teams integration card. After Logicgate's Product Support team enable Microsoft Teams integration for your organization, you should see the Enabled status. Click the setting gear on the top-right of the card. Then click Configure.
6. Once the integration is enabled, you can confirm that your Teams Integration is connected by navigating to Build Tab > Job in Risk Cloud. Select any Job Trigger, then confirm if Send Teams Message appears as one of the Operation options.
7. If you don't see Send Teams Message, please reach out to your Azure / Microsoft Admin to troubleshoot by checking that the steps in the Create the Risk Cloud Teams User in Entra and Create The Risk Cloud Teams Application in Entra sections of this article were followed.
Especially, make sure Microsoft Graph permissions are granted for Risk Cloud Application.
8. If you see Send Teams Message, then you can follow this article to continue creating a Job with Teams!
Legacy Authentication Flow
Starting 1/20/2025, we have updated the Microsoft Teams integration to OAuth 2.0 to enhance security, improve user experience, and align with modern authentication standards.
- If your organization HAS NOT set up the Microsoft Teams Integration on Risk Cloud, please follow the steps below.
- If your organization HAS ALREADY set up the integration, you can continue using the Legacy Authentication Flow and Job Operations previously configured using Teams Integration. However, we strongly encourage you to switch to the updated authentication method. You should contact your CSM for migration guidance. We will no longer enhance the legacy authentication method using the "Allow Public Client Flows" setup.