Registering Azure Active Directory (AAD) Application for Teams Chat Connectors using Export API

Article: 100055529
Last Published: 2023-04-04
Ratings: 1 0
Product(s): Veritas Alta SaaS Protection

Description

This article will provide directions on registering an Azure Active Directory (AAD) Application for Teams Chat Connectors using Export API.

For the Teams chat connectors to authenticate, it is required to create an Azure Active Directory application. This application needs to have a specific set of permissions if the Teams chat connector is configured to use Microsoft Teams Export API.

Instructions to create an Azure AD Application

NOTE: The hostnames used in the screenshots are lab machines for demonstration purpose. 

Log into Azure AD and select the 'Azure Active Directory blade', then click ' App registrations ', followed by ' New registration '.

  • Configure the application as follows:
  • Name: Veritas Alta™ SaaS Protection – Teams Export API
  • Support account types: Accounts in this organizational directory only
  • Redirect URI:  Change to Public client/native. The value should be urn:ietf:wg:oauth:2.0:oob
  • Click the 'Register' button.

  • Once registration process completes, it will automatically open the newly created application.
  • Now we need to add permissions.  Choose the API permissions button on the left, choose +Add a permission button and then on the right side, choose ‘Microsoft Graph’.
  • Select the Application Permissions button.

  • Select and add the following application permissions:

Directory.Read.All   

Chat.Read.All   

ChatMember.Read.All   

ChannelMessage.Read.All  

ChannelMember.Read.All   

TeamMember.Read.All   

 

  • Click the Grant Admin consent for... button to save the permissions. The result for permissions is as follows: 

The last step is to create a secret key.  

  • Click on Certificates & secrets
  • Click New client secret
  • Enter the Description as:  VASP Teams chat OAuth App Key
  • Choose 24 Months for Expires
  • Click Add

  • Take note of the VALUE key and save it. We do not need the Secret ID string. 

  • Lastly, we need to make a note of the following: 
    • Application (client) ID
    • Directory (tenant) ID 

  • These two ID's and the secret key will be used to configure the Teams chat connector which uses Microsoft Teams Export API.

Was this content helpful?