Teams App Header Still Visible Despite isFullScreen: true Configuration

Question

I have set "isFullScreen": true in the app manifest; however, after uploading the app in the test environment, the default header (Home/About) is still visible in Microsoft Teams.

Could you please confirm if there is any additional configuration required to hide the header, or if this is a limitation from the Teams side?

Answer 1

Hi @Vishva Sengamalai

Based on the information you provided, I understand that you have set the "isFullScreen": true property in your Teams app manifest, but you are still seeing the default header (Home/About) when viewing the app in your test environment. You are looking to confirm if there is a missing configuration or if this is a known limitation.

Based on my research, the "isFullScreen": true property (when placed at the root level of the manifest.json file) is indeed designed to hide the default tab header (the bar showing tabs like Home and About in personal/static tab apps) and allow your app to render in full screen.

However, the catch here is that this specific property only takes effect when the app package is published to your organization's App Catalog. It does not function properly when you are sideloading the app, using a test environment, or uploading it directly via the Developer Portal / App Studio.

To get this working and completely hide the header, you can consider the following steps:

1. Publish to the App Catalog: Upload your app package directly to the Organization App Catalog via the Microsoft Teams Admin Center.
2. Verify Manifest: Double-check your manifest.json one last time to ensure "isFullScreen": true is strictly at the root level.
3. Clear Cache: Force Microsoft Teams to completely clear its cache and restart so it pulls the newly published org-level version rather than a cached sideloaded version.

I hope this information helps you. Let me know if you have any other questions.

---

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.

Answer 2

Hello @Vishva Sengamalai,
Setting "isFullScreen": true in the Teams app manifest only expands your app’s content within the available tab canvas and does not remove Teams‑controlled UI elements such as the Home/About tab header, top bar, or navigation chrome. These components are part of the Teams client shell and cannot be hidden through manifest configuration, so the behavior you're seeing in the test environment is expected and by design. There is no additional setting available to suppress these headers in a personal tab; the only supported workaround to achieve a more immersive or chrome-less experience is to define a single static tab to reduce tab navigation or open the app using Stage View, which renders content in a near full‑screen modal and minimizes most of the default Teams tab UI.

Answer 3

isFullScreen: true in the Teams app manifest does not remove or hide the Teams-provided header (such as Home/About) for personal apps or tabs. It only controls how the content area is rendered within the Teams frame.

There is no additional manifest configuration in the provided documentation that hides the Teams header; this behavior is a product limitation on the Teams side. The platform explicitly notes that some apps can “render personal apps and dialogs without a Teams-provided header,” but this is controlled by the platform for specific first-party apps (like the Updates app), not by a general manifest flag available to custom apps.

---

References:

• Manage the Updates app for your organization in Microsoft Teams
• Teams Manifest
• Public developer preview for Teams