Teams catalog app installs fail with InvalidUserId / Invalid Bot despite matching single-tenant bot registration

Question

Teams catalog app installs fail with InvalidUserId / Invalid Bot despite matching single-tenant bot registration

Nithish 20

We are integrating ManageEngine ServiceDesk Plus with Microsoft Teams using a custom organization app. Uploading the app package through Teams admin center succeeds and the app appears in the organization catalog. However, when a user selects Add from the catalog, installation fails for all accounts tested in the same tenant.

Teams displays:

Invalid Bot — Please make sure the bot is registered and Teams channel is enabled.

Captured installation failure

The browser Network capture shows:

POST https://teams.cloud.microsoft/api/apps/apac/beta/users/apps/entitlements
HTTP 400 Bad Request

Response:

{"errorCode":"InvalidUserId","message":"Incorrect bot configuration/registration, please check the bot settings."}

The failure was captured on 6 October 2026 at approximately 13:04:40–13:04:42 UTC. Request and server request IDs are available for a private support investigation.

Configuration already checked

The bot is registered in the legacy dev.botframework.com portal, where a Migrate option is visible.
Bot app type is Single Tenant, with the intended Microsoft App ID and App Tenant ID.
The corresponding Microsoft Entra app registration is active, uses the same client ID and tenant ID, and has supported account type “My organization only.”
The enterprise application/service principal exists. Sign-in is enabled and user assignment is not required.
The Microsoft Teams channel is enabled, shows Running, and is configured for Commercial cloud.
The Teams manifest uses the same Microsoft App ID in both bots[].botId and composeExtensions[].botId.
The actual failed entitlements request contains those same bot IDs, the expected manifest/catalog app IDs, and the same tenant ID. This was checked against the uploaded ZIP, rather than only the local source manifest.
Manifest version is 1.20 and app version is 1.0.0. The app includes a bot, bot-based message extension, and personal tabs; bot and message extension scopes include personal, team, and group chat.
The published custom app is available to Everyone in the organization, custom app installation is allowed, and the tested user's app setup policy allows custom app upload.
The bot has an HTTPS messaging endpoint configured for ServiceDesk Plus. We have not yet correlated application-side access logs with the failed install, so we cannot confirm whether Teams attempted a server-to-server call to that endpoint.

Questions

Which bot registration/identity validation can produce this specific InvalidUserId response during the entitlements installation POST when the visible IDs, tenant configuration, and Teams channel match?
Are there additional diagnostics to verify that a legacy Bot Framework registration is correctly provisioned/resolvable by Teams for a single-tenant bot?
If Microsoft-side tracing is required, which support route should receive the request IDs? Is migration necessary for this particular failure, and what evidence would establish that?

We are looking for the failed validation and a targeted fix. Package publication succeeds; user installation is the failing operation. Tenant/account identifiers, endpoint keys, authorization headers, and the raw HAR have been omitted from this public post.

0 comments

1 answer

Your answer

Answer 1

Hi @Nithish

You have already validated most of the expected configuration items. Based on the information provided I gathered,

Microsoft does not publicly document which specific backend validation returns the InvalidUserId error during the Teams entitlement/install workflow. Public information only indicates that it is associated with bot registration or configuration issues, so the exact failing check cannot be determined from client-side traces alone.
Beyond verifying the Bot ID, Entra app registration, tenant configuration, Teams channel configuration, and manifest values, I am not aware of a public diagnostic that specifically confirms whether the Teams entitlement service can successfully resolve the bot registration during installation.
The bot appears to be associated with a legacy Bot Framework registration experience, but I have not found documentation showing that a legacy registration or the presence of a Migrate option would cause this specific InvalidUserId failure. Microsoft-side tracing would likely be required to determine whether the Teams entitlement service is unable to resolve or validate the bot registration.

Given that the app publishes successfully and the failure occurs during user installation, I recommend opening a Microsoft Teams support case and providing the details. Microsoft support should be able to verify whether the Teams entitlement service can successfully resolve and validate the bot registration associated with the Bot ID.

Additionally, I reviewed the ServiceDesk Plus Integration with Microsoft Teams documentation and noticed that the documented setup flow creates and configures the bot through Teams Developer Portal, Microsoft Entra App Registration, and Azure configuration. The guide also instructs associating the Entra Application (Client) ID with the bot and Teams app.

Note: This information is provided as a convenience to you. This site is not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

One thing that stood out is that your description mentions a bot registration in dev.botframework.com with a Migrate option, while the ServiceDesk Plus documentation I reviewed does not appear to reference the legacy Bot Framework portal as part of the setup workflow.

Could you confirm whether your deployment was configured using the same process described in the ServiceDesk Plus integration guide, or was the bot originally created using a different/older Bot Framework registration method?