Teams tabs and apps are setup items tied to apps in a tenant, so you plan them as rebuild work after a migration. Learn what Microsoft says about tabs and app policies, how to list what users rely on and follow 6 steps to bring tabs back in the new tenant.
Channels look right on Monday, but the tab bar is empty. Your users miss their planner, their dashboard and their company site.
I see this on almost every Teams project. This guide explains how Teams tabs and apps behave after a migration, using Microsoft's own pages, and how to rebuild them without guessing.
Why are Teams Tabs and Apps Missing After a Migration?
Microsoft's Graph page on a Teams tab says a tab is pinned to a channel or a chat and links to an app. It also says the link to the app cannot change after you create the tab.
So a tab is not plain content. It points to an app that must exist in the destination tenant, and it needs its own settings. A message copy does not rebuild that link.
What Decides Which Apps Users can Use in the New Tenant?
Microsoft's page on managing access to and installing Teams apps names three controls. App permission policies decide which apps users can use for all users, a group or specific users.
App setup policies decide which apps are pinned or installed and in what order. Org wide app settings allow or block custom apps and set the allow or block status of single apps.
A blocked app means a dead tab. Check these settings in the new tenant before you rebuild anything.
| Control | What it decides |
|---|---|
| App permission policy | Which apps users can use |
| App setup policy | Which apps are pinned or installed and their order |
| Org wide app settings | Allow or block custom apps and individual apps |
| Custom app upload | Who can add apps your developers built |
How do You Rebuild Teams Tabs by Hand?
Open the channel, select the plus sign on the tab bar, choose the app and complete its setup. Users with the right permissions can do this per channel.
That works for ten channels. For two hundred you need a list of every tab, its app and its target, and the hand work adds up fast.
Developers have another route. Microsoft Graph has an Add tab to channel method, and it returns a teamsTab. Every tab also needs its configuration, so your developer must know the settings the app expects.
How do You Bring Back Teams Tabs and Apps After a Migration?
I follow six steps on every Teams project.
- Inventory the source. Record every tab in every channel, with its app, its name and where its data lives.
- List the apps. Mark which apps are Microsoft apps, store apps and custom apps built by your developers.
- Check the new tenant. Confirm the permission policy, setup policy and org wide settings allow every app on your list.
- Install and pin. Use setup policies to install key apps for users so they see them on day 1.
- Rebuild the tabs. Add tabs by hand or with Graph after the channel and its files exist, and point it at the new location.
- Test as a member. Open every channel as a member, check that every tab loads and remove anything stale.
For files behind tabs, read where Teams files live in SharePoint. For the wider list of gaps, read what does not migrate in Microsoft Teams. For the full plan, read how to migrate Microsoft Teams to another tenant.
What are the Best Practices for Teams Tabs After a Migration?
- Inventory first. Tabs vanish from memory fast, so write them down before cutover.
- Check policies early. A blocked app breaks its tab.
- Rebuild after content. Channels and files must exist before tabs can point at them.
- Install key apps. Setup policies save users from hunting for apps.
- Test as a member. Owners see settings that members do not.
Which Mistakes Break Teams Tabs After a Migration?
Teams repeat four errors. They rebuild tabs before the channel files exist, and they forget to allow custom apps in the new tenant. They also skip the inventory, and they test only as an owner.
My Verdict on Rebuilding Teams Tabs and Apps
Tabs are setup work, not content. Plan them as a separate task with its own list and its own test.
Inventory the source, open the app policies in the new tenant and rebuild after content lands. Then users find their tools on day 1.
Frequently Asked Questions
Do Teams Tabs Move to a New Tenant?
Plan them as rebuild work. A tab links to an app, and Microsoft says that link cannot change after the tab is created, so the new tenant needs the app and a new tab.
How do I Add a Tab to a Teams Channel?
Open the channel, select the plus sign on the tab bar, choose the app and finish its setup. Developers can use the Microsoft Graph Add tab to channel method.
Which Policies Control Teams Apps?
App permission policies, app setup policies and org wide app settings work together. They decide which apps users can use and which are pinned.
How do I Pin Apps for Users in Teams?
Microsoft says app setup policies control which apps are pinned to the app bar and in what order. They can also install apps for users without any user action.
Can I Use Custom Apps in the New Tenant?
Yes, if the new tenant allows it. Microsoft says org wide app settings allow or block custom apps, and setup policies control who can upload them.
Do Teams App Setup Policies Work on Mobile?
Yes. Microsoft says app setup policy changes apply to the web, desktop and mobile Teams clients.
Where do I Start When Tabs are Missing After a Migration?
Start with the app policies in the new tenant. A blocked or missing app is the first cause to rule out, then rebuild tabs from your source list.
Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.
Published 20 October 2026. Tab and app link details come from Microsoft's page on the Teams tab resource type. App policy details come from Microsoft's page on managing access to and installing Teams apps. Microsoft can change these limits, so check them before you plan.