When you sign in to the new Teams client on a company-managed Windows device, you may notice that buttons like Meet, Apps, or Activity are grayed out or missing entirely. This usually happens because your organization’s IT policies restrict certain features, or because the client is running in an outdated compatibility mode. The new Teams client relies on your tenant settings, your assigned policies, and the local client configuration to decide which features appear. This article explains the root causes and gives you step-by-step fixes to restore full functionality.
Key Takeaways: Restore Missing Features in New Teams on a Managed Device
- Teams admin center > Teams apps > Manage apps: Check if an app is blocked or disabled for your organization, which can hide the Apps button.
- Teams admin center > Meetings > Meeting policies: Verify that the AllowMeetNow and AllowChannelMeetingScheduling toggles are enabled to show the Meet button.
- Teams client > Settings > General > Turn on new Teams: Ensure the new Teams toggle is on, because the classic client hides newer features.
- Group Policy > Computer Configuration > Administrative Templates > Microsoft Teams: Review the policy that disables the new Teams client; a value of 1 blocks the new client entirely.
Why the New Teams Client Hides Features on a Managed Device
The new Teams client is a web-based application that reads configuration from two sources: your Microsoft 365 tenant and your local Windows device. When a device is managed, IT can apply policies through Group Policy or Microsoft Intune. These policies can disable the new Teams client entirely, force it to run in classic mode, or block specific features like apps, meetings, or chat.
Another common cause is that the client is running on a Windows device that has not received the latest Teams update. The new Teams client updates automatically, but managed devices may have update deferral policies that delay the rollout. If your client is a few versions behind, some features that were added recently will not appear.
Finally, your user-level policies in the Teams admin center might be misconfigured. For example, if your meeting policy has the AllowMeetNow toggle off, the Meet button disappears from the left navigation. Similarly, if the app setup policy blocks third-party apps, the Apps button is hidden.
Steps to Diagnose and Fix Missing Features in the New Teams Client
Follow these steps in order. Each step addresses a different possible cause.
- Check if the new Teams client is actually enabled
Open Teams and click your profile picture at the top right. Select Settings > General. Look for the toggle labeled “Turn on new Teams”. If it is off, turn it on and restart Teams. If it is on but you still see missing features, proceed to the next step. - Verify your Teams version and update status
Click your profile picture, then select Settings > About. Note the version number. Compare it with the latest version listed on the Microsoft 365 roadmap page. If your version is older than a month, you may have an update deferral policy. Ask your IT admin to check the update policy in the Teams admin center under Teams > Update policies. - Review your meeting policy settings
Ask your IT admin to open the Teams admin center and go to Meetings > Meeting policies. Select the policy assigned to you and confirm that AllowMeetNow and AllowChannelMeetingScheduling are both set to On. If either is Off, the Meet button will not appear. - Check app setup policies for the Apps button
In the Teams admin center, go to Teams apps > Setup policies. Select the policy for your user and check if the Upload custom apps and User pinning toggles are enabled. Also go to Teams apps > Manage apps and make sure that the specific apps you expect are not blocked. - Inspect Group Policy for the new Teams client
On the managed device, open the Local Group Policy Editor by typing gpedit.msc in the Run dialog. Navigate to Computer Configuration > Administrative Templates > Microsoft Teams. Look for a policy named “Turn off the new Teams client”. If it is set to Enabled, the new Teams client is disabled. Set it to Not Configured or Disabled, then run gpupdate /force in a Command Prompt. - Clear the Teams cache
Close Teams completely. Press Ctrl+Shift+Escape to open Task Manager and end any Teams processes. Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. Delete all files and folders inside this directory. Restart Teams and sign in again. This often restores missing UI elements that were corrupted by a bad cache. - Reinstall the new Teams client
If the above steps fail, uninstall Teams from Settings > Apps > Installed apps. Then download the new Teams installer from the official Microsoft website and install it. After installation, sign in and check if the features appear.
If Teams Still Has Issues After the Main Fix
Teams Shows a Blank Window After Switching Work Accounts
When you sign out of one work account and sign in with another, the client may not refresh the policy cache. This causes missing features because the new account’s policies are not applied until a full restart. Fix this by clearing the cache as described in step 6 and then restarting the client.
Meet Button Is Missing Only on a Specific Channel
If the Meet button is missing in a channel but present in other areas, the channel’s moderation settings may be blocking members from starting meetings. The channel owner must go to the channel, click the ellipsis, select Manage channel, and check that the moderation option is not restricting members.
Apps Button Is Missing but Apps Work in the Classic Client
The new Teams client uses a different app framework. Some legacy apps are not compatible with the new client. Your IT admin must enable the app for the new client in the Teams admin center under Teams apps > Manage apps > select the app > App settings > Enable for new Teams.
Features Come Back Temporarily but Disappear Again After a While
This usually indicates that a policy refresh is reverting the changes. Check if your IT admin has configured a configuration service provider policy that re-enables the old client. Look for the policy “Teams with Microsoft 365” in the CSP and ensure it is set to allow the new client.
New Teams Client vs Classic Teams Client on a Managed Device
| Item | New Teams Client | Classic Teams Client |
|---|---|---|
| Feature updates | Roll out monthly with automatic updates | Updates are slower and often require manual install |
| App compatibility | Supports only apps built for the new Teams platform | Supports legacy apps that may not work in new Teams |
| Policy control | Uses the same admin policies but with a separate toggle | Uses the classic policy set that may override new client settings |
| Performance | Uses less memory and faster startup | Uses more memory and slower startup |
| Group Policy support | Can be disabled via the “Turn off the new Teams client” policy | Cannot be disabled by that policy; uses its own installation |
After following these steps, you should see the missing buttons and features in the new Teams client. If the issue persists, contact your IT admin to verify that your tenant policies are not blocking the new client. To avoid future problems, check the Teams admin center for any new policy changes that might affect your user profile. As an advanced tip, use the Teams admin center’s Policy Analytics tool to compare your assigned policies against the recommended settings for the new Teams client.