The Microsoft Teams activities use the Microsoft identity platform to establish an authenticated connection between UiPath and your Microsoft Teams application via the Microsoft Scope activity. This connection enables a Robot to call the Microsoft Graph API to read and write resources on your behalf.

To establish your authenticated connection, you first register your Microsoft Teams application in your Azure Active Directory (using your personal, work, and/or school Microsoft Office 365 account). When registering your application, you assign the Microsoft Graph API permissions that specify the resources a Robot can access on your behalf.

After registering your Microsoft Teams application, Azure Active Directory assigns a unique application (client) ID that you enter in the Microsoft Teams Scope activity. The ApplicationID is used to collect the necessary information about your registered app to initiate authentication.

📘

How do I register my app and assign permission?

To learn more about registering your application and assigning permission, see the Setup guide. This guide provides step-by-step instructions to configure your Microsoft Teams application for automation.

How it works

The following steps and message sequence diagram is an example how the activity works from design time (i.e., the activity dependencies and input/output properties) to run time.

1. Complete the Setup steps.
2. Add the Microsoft Teams Scope activity to your project.
3. Enter values for the Authentication, Input, and Unattended (if applicable) properties.

Unattended vs. Attended Automation

The Microsoft Teams Scope activity has three different authentication flows (AuthenticationTypes) that you can choose from when adding the activity to your project. Your selection is dependent on the type of automation mode you plan to run (unattended or attended) and your application authentication requirements (consult with your administrator if you're unsure which authentication requirements apply to your application).

❗️

Important

Unattended automation does not support multi-factor authentication. If you're application requires multi-factor authentication, you can only run attended automation using the InteractiveToken authentication type.

Interactive Token

The InteractiveToken authentication type can be used for attended automation and when multi-factor authentication (MFA) is required. This is the default option and what we use in our examples. If you're interested in "playing around" with the activity package, this option is easy to configure and works well for personal accounts (using the default redirect URI noted in step 7 of the Register your application section of the Setup guide).

When the Microsoft Teams Scope activity is run for the first time using this authentication type, you are prompted to authorize access to the resources (you granted permissions to when registering your app) via a consent dialogue box.

If you select this option, the Username, Password, and Tenant properties should be left empty.

This authentication type follows the OAuth 2.0 authorization code flow.

Integrated Windows Authentication

The IntegratedWindowsAuthentication authentication type can be used for both attended and unattended automation. This option can apply to Windows hosted applications running on computers joined to a Windows domain or Azure Active Directory.

You should only select this option if your registered application is configured to support Integrated Windows Authentication (additional information can be found on <a href="https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Integrated-Windows-Authentication" target=_"blank">GitHub).

If you select this option, the Username, Password, and Tenant properties should be left empty.

Username and Password

The UsernameAndPassword authentication type can be used for both attended (when mutli-factor authentication is not required) and unattended automation.

Though it's not recommended by Microsoft, you can use this authentication type in public client applications. Using this authentication type imposes constraints on your application. For instance, apps using this flow won't be able to sign in a user who needs to perform multi-factor authentication (conditional access). It won't enable your application to benefit from single sign-on either. Authentication with username/password goes against the principles of modern authentication and is only provided for legacy reasons (additional information can be found on GitHub).

If you select this option, the Username and Password properties are required and the Tenant property is optional for single-tenant applications (required for multi-tenant applications).

📘

Note

The ApplicationID property is required when selecting the UsernameAndPassword AuthenticationType. You can register your Microsoft Office 365 Application using your personal, work, and/or school account.

Properties

The values for the following properties are specified when adding this activity to your project in UiPath Studio.

Common

DisplayName

The display name of the activity.

---

Authentication

ApplicationID

The unique application (client) ID assigned by the Azure Active Directory when you registered your app during Setup.

AuthenticationType

The type of authentication required for your registered application.

Tenant

The unique directory (tenant) ID assigned by the Azure Active Directory when you registered your app during Setup.

---

Interactive Token

OAuthApplication

Indicates the application (client) to be used.

---

Username and Password (Unattended)

These properties apply when you run unattended automation only. When specifying values for these properties, be sure the AuthenticationType property is set to UsernameAndPassword. For more information, see the Username and Password section above.

Password

The password of your Microsoft Office 365 account.

SecurePassword

The password of your Microsoft Office 365 account.

Username

The username of your Microsoft Office 365 account.