Microsoft Team app fails to open in M365 with error "Unable to load requested application. No static tabs are configured."

Question

Microsoft Team app fails to open in M365 with error "Unable to load requested application. No static tabs are configured."

Anonymous

We have a Microsoft Teams app (manifest v1.20) that provides chat capabilities. The app works correctly in MS Teams Desktop (Version 26072.608.4595.8484) and Web versions. The app also appears in the list of Apps in M365 (https://m365.cloud.microsoft/apps/). However, when trying to access it by clicking on the app name, the following error message is displayed: Unable to load requested application. No static tabs are configured. However, if you go to Apps > All Apps > Get more apps > Built for your org, and click on the same app, it will open the app as a Copilot chat, and will respond to messages. The following updates to the app manifest have been made while trying to resolve the issue:

removing/changing staticTabs (no impact);
adding copilotAgents.customEngineAgents field (helped for the app to be opened in Copilot, but not in the M365 app page);
adding elementRelationshipSet (no impact);
creating staticTabs with contentUrl and websiteUrl, while adding the domain to validDomains (app fails to open even in Microsoft Teams).

Also, a new app was created using the same manifest (staticsTabs removed, copilotAgents.customEngineAgents present). The app can be opened in Copilot chat, but is missing from the M365 App page (therefore, it is impossible to validate the Unable to load requested application. No static tabs are configured. error). What could be the correct solution for the Microsoft Teams app in the M365 web interface to be opened without the Unable to load requested application. No static tabs are configured. error? Attaching a manifest file of the app:

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.20/MicrosoftTeams.schema.json",
  "manifestVersion": "1.20",
  "version": "1.1.2",
  "id": "${{TEAMS_APP_ID}}",
  "developer": {
    "name": "Contoso",
    "websiteUrl": "
  }, 
  "icons": {
    "color": "logo.png",
    "outline": "outline.png"
  },
  "name": {
    "short": "short",
    "full": "full"
  },
  "description": {
    "short": "short",
    "full": "full"
  },
  "accentColor": "#FFFFFF",
  "bots": [
    {
      "botId": "${{BOT_ID}}",
      "scopes": [
        "personal"
      ],
      "supportsFiles": false,
      "isNotificationOnly": false,
      "commandLists": []
    }
  ],
  "copilotAgents": {
    "customEngineAgents": [
      {
        "type": "bot",
        "id": "${{BOT_ID}}"
      }
    ]
  },
  "composeExtensions": [],
  "configurableTabs": [],
  "staticTabs": [
      {
        "entityId": "conversations",
        "scopes": [
          "personal"
        ]
      },
      {
        "entityId": "about",
        "scopes": [
          "personal"
        ]
      }
    ],
  "permissions": [
    "identity",
    "messageTeamMembers"
  ],
  "validDomains": []
}

0 comments

1 answer

Your answer

Answer 1

Hi @Anton Borkivskyi

Thank you for the detailed information you provided.

Looks like this issue relate to how Microsoft 365 (M365) launches applications from the app launcher. Based on my research, apps in Teams, Outlook, and Microsoft 365 are rendered through tab-based experiences, which are essentially web pages hosted within an iframe. As a result, when a user opens an app from the M365 app launcher, the platform attempts to load a tab-based UI (static tab) rather than initiating a bot or chat session.

In your scenario, although staticTabs are present in the manifest, they may not include a valid contentUrl or contentBotId. Consequently, the M365 host is unable to render any UI surface, which leads to the following error: "Unable to load requested application. No static tabs are configured."

As far as I understand, static tabs are the primary mechanism that allows a Teams app to be extended and displayed across Microsoft 365 applications. These tabs must point to actual, renderable content (for example, via a valid HTTPS contentUrl) so that the Microsoft 365 host can load them within its embedded frame. Based on this design, a bot-only or Copilot-only experience works correctly within Teams or Copilot surfaces, however, it does not provide a UI surface that the M365 app launcher can render directly.

I understand that you have tried adding contentUrl and websiteUrl, but the app still fails to open even in Teams. This behavior may indicate that the issue is no longer related to the manifest structure itself, but rather that the tab content is not loading correctly within the Teams/M365 iframe environment.

In practice, the contentUrl must point to a fully accessible HTTPS page that can be embedded and rendered inside an iframe. If the page cannot be reached, is blocked from embedding, or is not properly initialized for the Teams host, the tab will fail to load, even in Teams, which aligns with the behavior you observed.

To resolve this issue, the app should include a valid personal static tab whose contentUrl loads successfully within Teams. Once the tab renders correctly in Teams, it should also open as expected from the M365 app launcher.

I hope this helps.

Please note that this summary is based on my own findings and may not fully address your concerns. To help you reach your goal more effectively, I recommend engaging with [GitHub Community Forum] for a deeper technical dive or to connect with individuals who have relevant experience and expertise. Some approaches may behave differently or be restricted depending on your specific environment and configuration. These forums include many experienced developers and Microsoft specialists who can assist with troubleshooting and guidance.

Apologies for redirecting you to the related development team support. As moderators in this community, we do not have access to your specific tenant configuration, and my testing environment is limited. Therefore, my guidance is based on available Microsoft documentation and resources. That said, I’ll do my best to provide additional insight where possible.

If you have any additional concerns, feel free to comment below. I would be more than happy to assist.

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.

Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2026-04-29T22:26:57.7733333+00:00

Hi @Anton Borkivskyi

I hope the provided information were able to fully addressed your concern.

In case you require further assistance regarding this topic, feel free to reach out.

We more than happy to assist.

Looking forward to hearing from you.