Application Configuration in Azure Portal for OAuth2 Account to use in Teams

Overview

The Snaps in the Microsoft Teams Snap Pack require an OAuth2 account to access the resources in Azure. For the OAuth2 account to authorize successfully, create, and configure an application corresponding to the account as shown in the workflow.

You must complete steps one to three in the Azure Portal and the remaining steps in the Snap account (SnapLogic®Platform).

Prerequisites

An Azure account with a free subscription to create the application.

Key Steps in the Workflow

Create an Application in the Azure Portal

  1. Log in to the Microsoft Azure Portal.

  2. Navigate to Azure services > Microsoft Entra ID.

  3. Navigate to Add > App registration.

  4. On the Register an application page, specify the name for registering the application and click Register. Learn more about creating an application at Quickstart: Register an app in the Microsoft identity platform - Microsoft identity platform.

To use an existing application, navigate to Portal Home > Azure Active Directory > App registrations > All applications. In the search box, specify the application name you want to use. Details on registered application is display in the search list.

Define Permissions

The Teams Online Snap Pack supports the following three types of accounts:

The permissions for the registered application are either Delegated or Application permissions based on the account types. Select Delegated permissions for OAuth2 User Accounts and Application permission for OAuth2 Application Accounts.

  1. On the left navigation panel, navigate to Manage, select API permissions > Add a permission.

  2. On the Request API permissions window, select Microsoft Graph > Delegated permissions for the OAuth2 User account and Application permissions for the OAuth2 Application Account.

  3. Select the required permissions from Files, Users, and Teams. Choose the minimum API permissions listed under Scopes and Permissions Required for Teams.

  4. Click Add Permissions. View all the permissions added under Configured permissions.

     

  5. Click Grant admin consent confirmation and select Yes.

  6. In the navigation panel, click Overview and select Add a Redirect URI. You will be redirected to the Platform configurations page.

     

    1. Under Platform configurations, click Add a platform.

      The Configure platforms window displays.

    2. Select Web and specify the Redirect URI in the following format: 
      https://<control-plane-name>.snaplogic.com/api/1/rest/admin/oauth2callback/<snap-pack-name>
      where the <control-plane-name> corresponds to the domain part of your SnapLogic URL—elastic (global control plane) or emea (EMEA control plane).
      For example:
      https://emea.snaplogic.com/api/1/rest/admin/oauth2callback/teams
      https://elastic.snaplogic.com/api/1/rest/admin/oauth2callback/teams

    3. Select Web and specify either of the following Redirect URIs based on the region your server is located:

    4. Click Configure. A popup message displays indicating that the application is successfully updated.

  7. On the Platform configurations page, click Save.

Locate the Application Credentials in the Azure Portal

To authorize your account in SnapLogic, you must have the following application credentials:

  • Application (Client) ID

  • Directory (Tenant) ID

  • Client secret value

  1. On the application page, navigate to Overview.

  2. Under Essentials, note the Application (client) ID and Directory (tenant) ID needed for the Snap account.

  3. In the navigation panel, select Manage > Certificates & secrets.

  4. On the Certificates & secrets page, click + New client secret.

  5. In the Add a client secret window, enter the Description, select an option for Expires from the dropdown list, and click Add. 

    The Client value and Secret ID are generated. This value and ID are required to configure the OAuth2 account.

You can copy the Client secret value only after it is generated. Note that this value is displayed only once, so ensure to copy it securely.

Scopes and Permissions Required for Teams API

Microsoft Teams exposes a few granular permissions that control the access that apps have to resources. When users sign into your app, they are required to consent to these permissions. 

Delegated permissions (work or school account only*)

Delegated permissions (work or school account only*)

Permission

Display String

Description

Admin Consent Required?

Channel.Create

Create channels

Create channels in any team, on behalf of the signed-in user.

 

Yes

ChannelMember.ReadWrite.All

Add and remove members from channels.

Add and remove members from channels, on behalf of the signed-in user. Also allows changing a member's role, for example from owner to non-owner.

Yes

ChannelMessage.Send

Send channel messages

Allows an app to send channel messages in Microsoft Teams, on behalf of the signed-in user.

 

No

ChannelSettings.ReadWrite.All

Read and write the names, descriptions, and settings of channels.

Read and write the names, descriptions, and settings of all channels, on behalf of the signed-in user.

No

ChannelSettings.ReadWrite.Group

Update the names, descriptions, and settings of this team’s channels.

Update this group's channel names, channel descriptions, and channel settings, without a signed-in user.

No