This article lists Microsoft Teams integration error messages surfaced by the BoldDesk Teams app/bot, when each message appears, and the supported resolution steps. The error messages in this article reference configuration, authentication, and installation states across:
- Microsoft Teams (Team, Channel, user bot access)
- BoldDesk (Teams app installation, organisation mapping, domain)
- The BoldDesk Teams bot/service runtime (authentication values, connectivity)
This article does not define a single admin “enable/disable” toggle for all errors. Each error message is resolved by addressing the specific cause described in the How to resolve column.
Error Message Reference (Microsoft Teams)
Channel and Conversation Routing
| Error message |
When it displays |
How to resolve |
| Teams channel not found. Please contact your administrator to configure it. |
An organisation attempts to use Microsoft Teams, but the Microsoft Teams channel is not configured/mapped. |
Ask a BoldDesk administrator to configure the Microsoft Teams channel mapping in Admin, then retry the action. |
| This conversation cannot be continued because the associated Team/Channel is currently inactive. |
The configured Microsoft Teams Team/Channel for an organisation is inactive, blocking conversation. |
Re-activate the Team/Channel in Microsoft Teams, or reassign the Side Threads to an active channel. |
Trigger Input Validation
| Error message |
When it displays |
How to resolve |
| Invalid team ID |
IntegrationAppTeamId passed to the Microsoft Teams trigger is not a valid Team ID. |
Provide a valid, active Microsoft Teams Team identifier and retry. |
| Invalid team ID |
The Team ID passed to the Microsoft Teams trigger is empty, malformed, or does not resolve to a real Microsoft Teams Team. |
Provide a valid, active Microsoft Teams Team identifier and re-run the trigger. |
| Invalid BoldDesk domain |
A request supplies a host name that does not match the configured BoldDesk domain. |
Provide the correct BoldDesk domain (for example: https://example.bolddesk.com) and retry. |
| Invalid data |
Payload validation fails on the Microsoft Teams side (for example: missing action data, blank payload). |
Resend the message with required fields populated. If the wizard fails, use the manual command path. |
Authentication and Session
| Error message |
When it displays |
How to resolve |
| Login session expired |
The site used to log the user into BoldDesk has expired. |
Re-run the sign-in command from Teams to obtain a fresh login URL. |
| Invalid authentication token |
The authentication token sent by the caller cannot be validated. |
Sign the user in again through /bolddesk-sign-in to obtain a fresh token. |
| The BoldDesk Bot session has expired. Please sign in again. |
The operation fails because the BoldDesk session token has expired. |
Run /bolddesk-sign-in again to refresh BoldDesk credentials. |
| BoldDesk already authenticated |
The user attempts to sign in while a BoldDesk session is already active. |
Run /bolddesk-sign-out first, then sign in again with the intended account. |
| BoldDesk reauthentication failed. {0} |
Silent re-authentication of the bot session fails. |
Ask the user to run /bolddesk-sign-out, then /bolddesk-sign-in to re-link. |
Hi {0},
You are already logged in this account ({1}). |
A signed-in user re-runs sign-in to the same BoldDesk account. |
No action required. This message is informational. |
| *Authentication Required* Please sign in to BoldDesk using /bolddesk-sign-in to proceed with this action. |
Any command requiring authentication is invoked while the user is signed out. |
Run /bolddesk-sign-in, then retry the command. |
| Unable to save authentication details |
Persisting the OAuth code/token pair to the database fails. |
Check database connectivity/configuration, retry sign-in, and inspect audit logs if the issue persists. |
Bot/Service Runtime Configuration
| Error message |
When it displays |
How to resolve |
| Invalid authentication setting |
The bot detects misconfigured client ID / client secret / tenant values at runtime. |
Verify the Microsoft Teams authentication values in appsettings, then restart the bot service. |
Installation and Account Linking
| Error message |
When it displays |
How to resolve |
| Due to an internal issue, the app could not be installed. If the problem persists, please contact the administrator |
The install handshake fails or the BoldDesk API is unreachable. |
Retry the install. If repeated failures occur, contact the administrator. |
| To use this application, install the BoldDesk app in Microsoft Teams and connect your BoldDesk account to complete the setup. |
A user invokes a BoldDesk bot command without installing the BoldDesk Teams app. |
Install the BoldDesk app from Microsoft AppSource, then complete the sign-in steps. |
| Please install the Teams app on your BoldDesk account, then try again |
The Teams app is not installed inside the BoldDesk account. |
Install the Teams marketplace app inside BoldDesk, then retry the link. |
| Microsoft Teams app not found in your BoldDesk account |
Lookup for the Teams app inside BoldDesk returns null/unknown. |
Re-install the Teams marketplace app from the BoldDesk marketplace, then retry. |
| Unable to add integration |
The “add integration for Microsoft Teams” operation fails server-side. |
Confirm the Team is not already linked, refresh credentials, then retry Add. |
| Domain name required |
The user submits the Add Integration form without filling the domain field. |
Re-open the wizard, enter the BoldDesk domain (including scheme), then submit again. |
| This BoldDesk account is already linked with another Teams account |
The Team tenant ID is bound to one organisation but the request belongs to another. |
Use the matching BoldDesk tenant or unlink the previous tenant first. |
| The maximum number of Teams installs has been reached |
The organisation has reached the configured maximum number of active Teams installs. |
Remove an unused Teams install or contact the administrator to raise the limit. |
| Please uninstall the BoldDesk app from your Teams account, then try again |
The BoldDesk app must be uninstalled from Microsoft Teams before retrying the operation. |
Uninstall the BoldDesk app in Microsoft Teams, then retry after correcting any related configuration issues. |
Ticket and Content Operations
| Error message |
When it displays |
How to resolve |
| Ticket Updated Successfully. |
Displayed inside the adaptive card/task module after a ticket update completes. |
No action required. |
| Due to an internal issue, the app could not be loaded. If the problem persists, please contact the administrator. |
Task module initialization cannot reach a required service. |
Close the module and run the command again. Escalate to an administrator if it persists. |
| The ticket does not exist or you do not have permission to access it. |
The supplied Ticket ID does not exist, or the caller lacks permission. |
Confirm the Ticket ID and ensure the agent has access, then retry. |
| Ticket update has been failed. Please enter a valid content. |
The agent submits the task module form with an empty description. |
Provide a non-empty message and submit again. |
| Ticket is not updated due to an internal issue. If the problem persists, please contact the administrator. |
The underlying API call (reply/note/property update) fails unexpectedly. |
Retry. If it persists, contact the administrator. |
| <span><strong>Ticket (subject - {0}) failed to create</strong></span> |
Posted to the Microsoft Teams personal/bot thread when ticket creation fails. |
Review the cause of ticket creation failure, then retry. ({0} is replaced with the ticket subject.) |
Permissions and Access Denied
| Error message |
When it displays |
How to resolve |
| You are not allowed to perform this operation, please contact your administrator. |
Returned in the channel when the calling user lacks permission for the action. |
Contact an administrator to request the required permissions. |
| @{0} - Access Denied - You are not allowed to perform the ticket update operation, please contact your administrator. |
Posted in the channel as an attributed denial when a command fails due to missing permission. |
Contact an administrator to grant the missing permissions. |
| Access Denied - You are not allowed to perform the ticket update operation, please contact your administrator. |
A user in a group/meeting chat attempts a denied action. |
Contact an administrator to grant the missing permissions. |
Command Parsing
| Error message |
When it displays |
How to resolve |
| Sorry, I didn’t understand ‘{0}’. Type help to explore commands. |
The bot cannot recognize the slash command entered by the user. |
Type help to list valid commands. |
Notification Deactivation (Delivery Failures)
| Error message |
When it displays |
How to resolve |
| Microsoft Teams channel notification “{0}” deactivated |
Audit log entry/notification when a channel notification is disabled after repeated delivery failures. |
Verify the channel and bot configuration, then re-activate the notification from the Inactive tab of the Microsoft Teams app page. |
| Microsoft Teams notification for the user “{0}” deactivated |
Audit log entry when a user’s Teams notification is disabled after delivery failures. |
Ask the user to unblock the bot in Microsoft Teams, then re-authorize the personal bot from Personal Settings > Apps tab. |
Troubleshooting (when errors repeat)
If sign-in related errors persist
- Run
/bolddesk-sign-out and then /bolddesk-sign-in to force a clean re-link.
- If Unable to save authentication details persists, validate database connectivity/configuration and check audit logs.
If channel routing errors persist
- Confirm the mapped Microsoft Teams Team/Channel is active in Microsoft Teams.
- Re-check the Microsoft Teams channel mapping in BoldDesk Admin.
If installation errors persist
- Retry installation after confirming BoldDesk API availability.
- If maximum installs is reached, remove an unused install before retrying.
