Microsoft Teams OAuth2 API Credentials

Fields

Field	Type	Required	Notes
Client ID `clientId`	string	Yes	The Application (client) ID from your Azure AD app registration.
Client Secret `clientSecret`	password	Yes	The client secret from your Azure AD app registration.
Tenant ID `tenantId`	string	No	The Azure AD tenant ID.
Scope `scope`	string	No	OAuth2 scopes to request.
Authorization URL `authorizationUrl`	string	No	The Microsoft Identity Platform authorization endpoint.
Access Token URL `accessTokenUrl`	string	No	The Microsoft Identity Platform token endpoint.
Microsoft Graph API Base URL `graphApiBaseUrl`	string	No	The Microsoft Graph API base URL.
Access Token `accessToken`	password	No	OAuth2 access token. Required for API calls.
Refresh Token `refreshToken`	password	No	OAuth2 refresh token. Required for automatic token renewal. Leave blank only if the token never expires.
Token Expiry (Unix timestamp) `expiresAt`	string	No	Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

In Microsoft Teams OAuth2 API, create the credential this connection needs — the values listed in the table above. These are issued from your own Microsoft Teams OAuth2 API account, usually under its developer, API or integrations settings.
In BusyBot, open Credentials → Add credential and choose Microsoft Teams OAuth2 API.
Paste each value into the matching field and save.
Add the Microsoft Teams Trigger node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Secret values are encrypted at rest with AES-256-GCM and are never shown again after saving.
Grant the minimum scopes or permissions the operations you actually use require.
Rotate the credential periodically, and immediately if it may have been exposed.
Credentials are scoped to your account — a workflow cannot use another account's.