Microsoft Teams actions

​

Step 1: Register an application in Microsoft Entra ID

1. Sign in to the Azure portal as an administrator (or a user who can register apps).
2. Open Microsoft Entra ID (Azure Active Directory).
3. Under Manage, select App registrations → New registration.
4. Enter a name (for example, “PipesHub Teams actions”), choose Accounts in any organizational directory and personal Microsoft accounts if you need the broadest sign-in audience (or a stricter option for your tenant), then register.
5. Copy the Application (client) ID for later.

​

Step 2: Add Microsoft Graph API permissions

1. In the app registration, open API permissions.
2. Click Add a permission → Microsoft Graph → Delegated permissions.
3. Add the permissions required by the Teams action (see the table below). Add each permission that appears in your product version; your administrator may consolidate or adjust these over time.
4. Click Add permissions.

​

Delegated permissions (reference)

​

Step 3: Grant admin consent (if required)

1. On API permissions, review Status for each permission.
2. If your tenant requires it, click Grant admin consent for [your organization] and confirm.

​

Step 4: Create a client secret

1. Open Certificates & secrets.
2. Under Client secrets, click New client secret, add a description and expiry, then Add.
3. Copy the secret value immediately; it is shown only once.

​

Step 5: Create the Microsoft Teams action in PipesHub

​

Case A — Organization does not have a Microsoft Teams instance yet

1. In the sidebar, open Workspace, then Actions.
2. On the catalog, find Microsoft Teams. With no org instance yet, the card is Not configured and the primary control is Setup.
3. Click Setup on the Microsoft Teams card (or open the card and start setup). The Action configuration drawer opens.

​

Case B — Organization already has at least one Microsoft Teams instance

1. In the sidebar, open Workspace, then Actions.
2. Find Microsoft Teams in the catalog. When an org instance already exists, clicking the card opens the Microsoft Teams type page (instances list) instead of launching setup immediately.
3. On the type page, click Add instance. The Action configuration drawer opens.

​

Complete configuration (both cases)

4. In the Action configuration drawer, set Instance name (for example, “Production Teams”).
5. Enter Client ID and Client secret from Entra (and Tenant ID if the form shows it—your directory GUID, domain, or common for the default multi-tenant and personal Microsoft account behavior, as described in the product UI).
6. Click Create to save the organization action instance.

​

Step 6: Copy the Redirect URI and register it in Azure

1. On the Microsoft Teams action page, find your new instance in the list.
2. Open Manage action configuration (the settings control on the instance row).
3. Under Redirect URI, copy the value (or use Copy). It matches your deployment host and this pattern: https://<your-pipeshub-host>/toolsets/oauth/callback/teams The path segment teams matches the Microsoft Teams action type. The value must match what you register in Entra exactly (scheme, host, path; no stray trailing slash unless your deployment includes one).
4. In the Entra app registration, open Authentication.
5. Under Platform configurations, add a Web platform if needed.
6. Under Redirect URIs, paste the exact Redirect URI from PipesHub.
7. For a web-based OAuth callback, you can enable Access tokens and ID tokens under Implicit grant and hybrid flows only if your organization’s security policy requires it; many confidential-client flows use the authorization code flow only.
8. Save the Authentication blade.

​

Step 7: Sign in and authorize