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."

Anton Borkivskyi 0

We have a MS 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 MS 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 error).

What could be the correct solution for the MS Teams app in M365 web interface to be opened without the "Unable to load requested application. No static tabs are configured." error?

Attaching a JSON manifest of the app. manifest.txt

0 comments

2 answers

Your answer

Answer 1

Hi @Anton Borkivskyi

Based on the behavior you described, the issue is most likely related to how Microsoft 365 handles personal apps compared to Microsoft Teams.

Your bot works correctly in Teams Desktop/Web because Teams can open the bot chat directly from the bots section, and the copilotAgents.customEngineAgents configuration allows it to open as a Copilot chat. However, Microsoft 365 Apps page typically expects the app to provide a launchable personal app experience through a valid personal static tab, usually using contentUrl.

In the current manifest, the staticTabs section only contains:

 "staticTabs": [
      {
        "entityId": "conversations",
        "scopes": [
          "personal"
        ]
      },
      {
        "entityId": "about",
        "scopes": [
          "personal"
        ]
      }
    ]

These entries are not considered launchable personal static tabs by the Microsoft 365 app launcher because they don’t define a hosted tab experience. As a result, M365 shows the error message: Unable to load requested application. No static tabs are configured.

You also mentioned that when adding staticTabs with contentUrl and websiteUrl, the app failed to open even in Teams. In that case, the issue is usually not the staticTabs definition itself, but the hosted tab page configuration.

Here are some common causes you may check:

-the contentUrl is not using HTTPS

-the domain is missing or mismatched in validDomains

-the hosted page does not load the Teams JavaScript SDK or does not call microsoftTeams.app.initialize()

-the page is blocked by X-Frame-Options or restrictive Content Security Policy (CSP) headers

-the page URL redirects to another domain that is not listed in validDomains

So, adding a real personal static tab is still required for Microsoft 365, but the hosted tab page must also be Teams-compatible.

A valid example would be:

"staticTabs": [
  {
    "entityId": "home",
    "name": "Home",
    "contentUrl": "https://yourdomain.com/tab",
    "websiteUrl": "https://yourdomain.com/tab",
    "scopes": ["personal"]
  }
],
"validDomains": [
  "yourdomain.com"
]

References:

I hope this information is helpful.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

Teddie-D 16,370 Reputation points Microsoft External Staff Moderator

2026-04-29T23:15:45.76+00:00

Hi @Anton Borkivskyi
May I know if you have got any chance to check my answer? If you need further assistance, please feel free to let me know. Thank you!
Anton Borkivskyi 0 Reputation points

2026-04-30T07:27:11.5533333+00:00

Thank you for your response! Adding a hosted Teams-compatible tab page is not on our roadmap for now. Is it possible to modify the manifest of the app so that it does not appear in M365 completely, while still working in MS Teams?
Teddie-D 16,370 Reputation points Microsoft External Staff Moderator

2026-04-30T07:50:32.71+00:00

Hi @Anton Borkivskyi

There isn’t a manifest-only way to prevent a Teams app from appearing in Microsoft 365 while keeping it functional in Teams. If your goal is to ensure the app continues to work in Teams but does not show up in Microsoft 365 launcher surfaces, the recommended approach is to manage visibility through Microsoft Entra rather than the Teams app manifest.

Microsoft provides an official setting to hide an enterprise application from both the My Apps portal and the Microsoft 365 app launcher. Please refer to Hide an enterprise application - Microsoft Entra ID | Microsoft Learn.

Also note that hiding the application does not revoke user permissions. In most cases, the app can continue working in Teams while no longer appearing in the Microsoft 365 launcher, since hiding the enterprise application only affects launcher visibility and does not remove user permissions. Users can still access it via direct links or through service dependencies; the setting only removes it from launcher and portal visibility.

Because of this, if you don’t plan to implement a hosted personal static tab, hiding the enterprise application is generally a cleaner and more reliable solution than trying to force Microsoft 365 launcher compatibility through the Teams app manifest.
Teddie-D 16,370 Reputation points Microsoft External Staff Moderator

2026-05-01T04:32:53.7166667+00:00

Hi @Anton Borkivskyi
Just checking in to see if the information above was useful to you. If you have any additional updates or need further assistance, don't hesitate to reach out. Warm thanks!

Answer 2

The error occurs because the Microsoft 365 app shell expects a static tab experience for a Teams app opened from the Microsoft 365 app launcher, but the app either has no valid staticTabs entry or the static tab configuration is invalid for the host.

Key points from the behavior described:

The app works in Teams (desktop/web) as a chat/agent and can be opened as a Copilot chat.
From the Microsoft 365 app page, it fails with: Unable to load requested application. No static tabs are configured.
When staticTabs were added with contentUrl/websiteUrl, the app stopped working even in Teams, which indicates the tab configuration did not meet manifest or runtime requirements.

To open the app from the Microsoft 365 app page without this error, the manifest must:

Use a manifest schema version that supports Microsoft 365 hosts
- Ensure the manifest uses schema 1.13 or later and a corresponding manifestVersion, for example:
```
     {
       "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.20/MicrosoftTeams.schema.json",
       "manifestVersion": "1.20"
     }
```
- This is required for a Teams personal tab (or agent with a tab) to run in Outlook and the Microsoft 365 app.
Define at least one valid static tab in personal scope
- The Microsoft 365 app shell needs a static tab to render when the app is launched from the app launcher. Configure staticTabs similar to:
```
     "staticTabs": [
       {
         "entityId": "index",
         "name": "Personal Tab",
         "contentUrl": "${{TAB_ENDPOINT}}/index.html#/tab",
         "websiteUrl": "${{TAB_ENDPOINT}}/index.html#/tab",
         "scopes": [
           "personal"
         ]
       }
     ],
```
- Ensure:
  - entityId is present (required).
  - contentUrl and websiteUrl are valid HTTPS URLs.
  - The domain of contentUrl/websiteUrl is either the same as the settings page domain or listed in validDomains.
Configure validDomains to match the tab URLs
- Add the tab’s domain to validDomains, for example:
```
     "validDomains": [
       "${{TAB_DOMAIN}}"
     ],
```
- If using Agents Toolkit variables (${{TAB_ENDPOINT}}, ${{TAB_DOMAIN}}), ensure they resolve correctly in the environment where the app is running.
Keep the chat/agent capability and static tab aligned via runtime requirements (optional but recommended)
- If using elementRelationshipSet and runtime requirement sets, ensure they do not exclude the static tab from Microsoft 365 hosts. The Microsoft 365 host must see at least one static tab capability that is allowed to run there.
Validate and troubleshoot the manifest and package
- Use Agents Toolkit to validate the manifest and identify schema or configuration errors.
- If the app fails to open in Teams after adding staticTabs, re-check:
  - JSON validity.
  - That staticTabs is an array of unique items and within the allowed limit.
  - That all URLs are HTTPS and domains are in validDomains.
- If manifest updates are not reflected, sign out and sign in again to clear cache.
Understand host support and adjust behavior at runtime
- Only a subset of Teams capabilities is supported in Outlook and Microsoft 365. Use the Teams JS SDK isSupported() checks for capabilities and provide fallback UI if a capability is not supported in the Microsoft 365 host.

In practice, the correct solution is:

Upgrade the manifest to a supported schema/manifest version for Microsoft 365.
Add a valid personal-scope static tab with working contentUrl/websiteUrl and matching validDomains.
Ensure no runtime requirement or relationship configuration hides that static tab from the Microsoft 365 host.

Once a valid personal static tab is present and the manifest is on a supported schema, the app should open from the Microsoft 365 app page instead of showing the “No static tabs are configured” error, while still functioning as a Copilot chat.

References:

Share via

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

2 answers

Your answer