Share via

Generic Error When Uploading Custom App to a Specific Team in Microsoft Teams

Andrus Shirnavana 145 Reputation points
2025-09-25T12:06:12.3966667+00:00

I’m encountering an issue when attempting to upload a custom app to a specific team in Microsoft Teams. The app package is a valid .zip file created via the Teams Developer Portal, and it uploads successfully to other tenants or teams without any problems. However, when I try to add it to this particular team, either through the Teams client or the Admin Center, I get a generic error message: “The app cannot be added to the Teams. Try again and if issue persists contact MS custom support.” I’ve verified that the app permission policies are set to allow custom apps in the Teams Admin Center, and there are no apparent restrictions on the team itself.

The app manifest is correctly formatted, and I’ve tested it in preview mode, where it functions as expected.

My Manifest Json

{

"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.13/MicrosoftTeams.schema.json",

"manifestVersion": "1.13",

"version": "1.0.0",

"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", // Replace with your Azure AD App ID (GUID)

"packageName": "com.example.myapp",

"developer": {

"name": "Example Developer",

"websiteUrl": "https://www.example.com",

"privacyUrl": "https://www.example.com/privacy",

"termsOfUseUrl": "https://www.example.com/termsofuse"

},

"name": {

"short": "My Custom App",

"full": "My Custom App for Teams"

},

"description": {

"short": "A custom app for team collaboration",

"full": "This app provides a custom tab for team collaboration and messaging in Microsoft Teams."

},

"accentColor": "#60A18E",

"icons": {

"color": "color.png", // 192x192 PNG in app package

"outline": "outline.png" // 32x32 PNG in app package

},

"configurableTabs": [

{

  "configurationUrl": "https://myapp.example.com/config", // HTTPS endpoint for tab config

  "canUpdateConfiguration": true,

  "scopes": ["team", "groupchat"]

}

],

"permissions": [

"identity",

"messageTeamMembers"

],

"validDomains": [

"myapp.example.com" // Must match configurationUrl domain

],

"webApplicationInfo": {

"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", // Same Azure AD App ID as above

"resource": "api://myapp.example.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" // API resource URI

},

"authorization": {

"permissions": {

  "resourceSpecific": [

    {

      "name": "TeamSettings.ReadWrite.Group",

      "type": "Application"

    },

    {

      "name": "ChannelMessage.Send",

      "type": "Delegated"

    }

  ]

}

}

}

Microsoft 365 and Office | Development | Other
0 comments

Answer accepted by question author

Anonymous
2025-09-25T13:46:48.3266667+00:00

Hi Andrus Shirnavana

Thank you for posting your question in the Microsoft Q&A forum and providing details about the manifest and the error you're encountering.

To better understand the issue, could you please clarify a few points to help narrow down:

  • What's the main goal behind uploading and adding the custom app manually to each tenant, rather than publishing it to the Microsoft Teams App Store? For example, are you aiming for users to download/install it directly from a centralized location (like an internal catalog) without needing to upload it per-team? As Microsoft generally recommends publishing to the Teams App Store for broader distribution and easier management (kindly see Publish your app to the Microsoft Teams store)
  • When you registered this app (e.g., in Azure AD), was it primarily for management purposes, such as internal admin tools or custom integrations? Or is the focus on distributing the app internally within your organization(s) for collaboration features?
  • Is this for a multi-tenant setup (e.g., across different organizations) or within a single org with multiple tenants? In the meantime, to rule out configuration differences, could you provide an overview of the affected tenant's setup? Specifically, please check your Azure AD app registration settings and ensure they're consistent with the working tenants. For guidance, refer to this: Quickstart: Register an application with the Microsoft identity platform. Key things to verify include the supported account types (e.g., single-tenant vs. multi-tenant), API permissions, and any exposed APIs that match your manifest's webApplicationInfo.

To help me better understand this, could you share a screenshot of your app registration page in the Azure portal (similar to the example below)? Redact any sensitive info like GUIDs or tenant names if needed.

User's image

Please understand that our initial response may not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a resolution.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

Answer recommended by moderator

Andrus Shirnavana 145 Reputation points
2025-09-25T13:57:42.55+00:00

I’ve found the problem, I forgot to turn on the upload permission in the Global-Org policies.

But thank you for your time

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.