See what the Microsoft Teams integration can do →
Overview
This article catalogs the error messages a subscriber may encounter when connecting to Microsoft Teams or sending messages from iPaaS.com to Microsoft Teams, with the cause of each error and how to resolve it. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. Each error carries a stable code you can search for on this page.
Some resolutions below refer to your Managed Integration Service Provider (MiSP) — the partner who set up and manages your iPaaS.com integration.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Add/Update Microsoft Teams Channel Message FROM iPaaS.com
Error Collection
Connecting to Microsoft Teams
These errors can occur while authorizing the Microsoft Teams connection in iPaaS.com. See Microsoft Teams Connections and Settings for the full connection walkthrough.
API URL not provided
MTMS-AUTH-1007 - Unable to complete OAuth process in ProcessAuthorization. API Url is not specified
Description: The API URL subscription setting is empty, so the authorization could not be completed.
Resolution: In the Microsoft Teams subscription settings, set the API URL to https://graph.microsoft.com, save, then re-authorize by clicking the Authenticate button in the subscription toolbar.
Authorization code missing
MTMS-AUTH-1004 - Unable to complete OAuth process in ProcessAuthorization. Code is not specified
Description: The authorization did not return an authorization code from Microsoft, so the connection could not be completed. This usually means the Microsoft sign-in was cancelled or did not finish.
Resolution: Re-authorize the connection: open the Microsoft Teams subscription, click the Authenticate button, and complete the Microsoft sign-in, allowing access when prompted. If the authorization keeps failing, your MiSP can review the connection.
Code verifier missing
MTMS-AUTH-1005 - Unable to complete OAuth process in ProcessAuthorization. Code_Verifier is not specified
Description: The authorization request was missing its security verifier, so the sign-in could not be completed.
Resolution: Re-authorize the connection using the Authenticate button and complete the Microsoft sign-in. If it keeps failing, your MiSP can review the connection.
Token exchange failed
MTMS-AUTH-1008 - Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token
Description: Microsoft did not return an access token when exchanging the temporary authorization code, so the connection could not be established. This can happen if the authorization expired or was interrupted.
Resolution: Re-authorize the connection: open the Microsoft Teams subscription, click the Authenticate button, and complete the Microsoft sign-in. If you are authorizing a different Microsoft account, first sign out of all Microsoft services at https://login.microsoftonline.com/logout.srf, then authenticate again. If it continues to fail, your MiSP can review the connection.
Client ID not configured
MTMS-AUTH-1001 - Unable to complete OAuth process in ProcessAuthorization. ClientId is not specified
Description: The OAuth Client ID for the Microsoft Teams integration is not present in the integration configuration, so the authorization could not be completed. This value is maintained by iPaaS.com and is not something you enter in your subscription.
Resolution: This is an iPaaS.com-managed setup value, not a subscription setting you can change. Report it to your MiSP, who manages the integration setup and can get the configuration corrected.
Client secret not configured
MTMS-AUTH-1002 - Unable to complete OAuth process in ProcessAuthorization. ClientSecret is not specified
Description: The OAuth Client Secret for the Microsoft Teams integration is not present in the integration configuration, so the authorization could not be completed. This value is maintained by iPaaS.com and is not something you enter in your subscription.
Resolution: This is an iPaaS.com-managed setup value, not a subscription setting you can change. Report it to your MiSP, who manages the integration setup and can get the configuration corrected.
Scope not configured
MTMS-AUTH-1003 - Unable to complete OAuth process in ProcessAuthorization. Scope is not specified
Description: The OAuth scope for the Microsoft Teams integration is not present in the integration configuration, so the authorization could not be completed. This value is maintained by iPaaS.com and is not something you enter in your subscription.
Resolution: This is an iPaaS.com-managed setup value, not a subscription setting you can change. Report it to your MiSP, who manages the integration setup and can get the configuration corrected.
Redirect URL not configured
MTMS-AUTH-1006 - Unable to complete OAuth process in ProcessAuthorization. Redirect Url is not specified
Description: The OAuth redirect URL for the Microsoft Teams integration is not present in the integration configuration, so the authorization could not be completed. This value is maintained by iPaaS.com and is not something you enter in your subscription.
Resolution: This is an iPaaS.com-managed setup value, not a subscription setting you can change. Report it to your MiSP, who manages the integration setup and can get the configuration corrected.
Add/Update Microsoft Teams Channel Message FROM iPaaS.com
Both a channel and a chat were provided
MTMS-VALD-1001 - Only one of either a chat ID or a channel ID must be specified.
Description: The message resolved both a channel and a chat as its destination. A message can be delivered to only one destination.
Resolution: Map either the channel field or the chat field, but not both, then retry the message.
No channel or chat was provided
MTMS-VALD-1002 - Could not transfer because neither a channel ID nor a chat ID was provided correctly through mappings.
Description: The message did not resolve a channel or a chat to deliver to.
Resolution: Confirm the message mappings so that either the channel field or the chat field is populated. For a channel, verify the channel name resolves to an existing channel in the configured team.
Message content is missing
MTMS-VALD-1003 - Could not transfer because content is null
Description: No content was produced for the message body. Content is built from the message text and its supporting detail; if those inputs are missing, no content is produced.
Resolution: Confirm the message has text and the supporting detail it needs so that content can be assembled.
Updating an existing message is not supported
MTMS-BIZL-1001 - Updating a previously posted message is not supported. Send a new message instead.
Description: A transfer attempted to update a message that was already posted. This collection creates new messages only; updating a previously posted message is not supported in this release.
Resolution: To send revised information, dispatch a new message rather than updating an existing one.
Microsoft Teams rejected the request
MTMS-EXTN-1001 - Error calling Microsoft Teams: {external response} (Http Code: {status}).
Description: Microsoft Teams returned an error while the message was being delivered. The logged message includes the response returned by Microsoft Teams and the HTTP status code. Common causes are an invalid or inaccessible channel or chat ID, insufficient permissions for the connected account, or Microsoft Teams throttling the request.
Resolution: Review the Microsoft Teams response and HTTP status code in the error log. Verify the Teams Group ID and the channel or chat the message targets, and confirm the connected account can post to that destination. If the response indicates a temporary condition, retry the message. If it persists, your MiSP can review the mapping and connection using the logged response and tracking GUID.