Overview

Perform operations on MS Teams via the Workflow Automator.

Description

Orchestration apps let you automate repeatable tasks and actions that span across a diverse set of systems and applications using workflows. The list of actions supported for this app include:

Team Management

1. Create Team

2. Update Team

3. Get Team

4. Archive Team

5. Unarchive Team

6. Add Member To Team

7. Remove Member From Team

 Channel Management

1. Create Channel

2. Get Channel

3. Get Channel By Name

4. Delete Channel

5. Add Member To Channel

6. Remove Member From Channel

      Chat Management

1. Post Message

Prerequisites

To install and authenticate the app you need to provide the following input:  

• Config Name

• The config name is the unique identifier for the account credentials added to the app.

•  Client ID

• Navigate to “Azure Active Directory”

• Go to App Registrations (if you don’t have an existing App, create a new app registration)

• Then open your App 

• Copy “Application (client) ID”

• Key (Secret Key)

• Navigate to Azure Active Directory

• Go to App Registrations 

• Then click “Certificates & secrets” on the left panel

• Click on “New client secret” 

• Copy the Secret Key given as “Value”.

• Active Directory Domain

• Navigate to  Azure Active Directory 

• Go to Overview

• Copy Primary Domain / Tenant Id.

Steps to assign permissions

1. Navigate to Azure Active Directory

2. Go to App Registrations

3. Select your app 

4. Go to API Permissions

5. Click on “Add Permissions” 

6. Click on “Microsoft Graph” 

7. Click on  “Application Permissions”

8. Assign the following permissions to your app:

i.  Group.Read.All

ii. Group.ReadWrite.All

iii. TeamMember.ReadWrite.All

iv. ChannelMember.ReadWrite.All

9. Make sure you "Grant admin consent" for all the permissions you assign.

Usecases

Now that you've successfully installed the Microsoft Teams orchestration app, please have a look at the sample use case below to show how the app can be used efficiently. 

• Sample Use Case- MS Teams Notification for High Priority Incident

Limitations limitations in the Microsoft Teams API

The Microsoft Teams API has specific limitations in how message content is rendered. The following behaviors may affect how formatted text appears when content is posted to Microsoft Teams.

• HTML tags are not preserved - Microsoft Teams does not retain certain HTML tags, such as <u>. As a result, HTML-based formatting may be removed during rendering.

• Leading spaces and tabs are removed - Leading spaces or tab characters at the beginning of a line are stripped when the content is rendered in Microsoft Teams.

• Underlined text is not supported - Any underlined text in the ticket description is removed, as Microsoft Teams does not support HTML underline formatting.

• Font color and highlight color are not supported - Custom font colors or background highlight colors applied in the source content do not appear in Microsoft Teams.
  Teams supports only standard Markdown and a limited set of formatting styles.

• Extra line breaks render as literal <br /> tags - Multiple consecutive line breaks in the content may appear as literal <br /> tags in Microsoft Teams.
  This occurs because the Teams API does not interpret or collapse consecutive <br> elements in incoming text.

Supported Formatting

The following formatting elements continue to function as expected in Microsoft Teams:

• Bullet points

• Bold and italic text

• No additional HTML tags (such as <div>) are inserted

• No text truncation observed, including content exceeding 2,000 words

All observed formatting differences are due to current limitations in Microsoft Teams’ message rendering behavior and API capabilities. These behaviors are expected and are not caused by issues in our implementation.