Fix Teams App Setup Policy Does Not Pin an App After Waiting 24 Hours

You configured a Teams app setup policy to pin a custom or third-party app for your users, but after waiting 24 hours the app still does not appear in the app bar. This delay usually happens because the policy assignment has not propagated, the app is not available for the user’s license, or the client cached an older policy. This article explains the root cause and walks you through the exact steps to force the policy update and verify the pin.

You will learn how to check the effective policy, clear the Teams cache, and confirm that the app is allowed in the org-wide app settings. By the end, you will be able to get the app pinned within minutes instead of waiting another day.

Why the App Setup Policy Does Not Pin the App After 24 Hours

The Teams app setup policy controls which apps appear in the app bar on the left side of the client. When you assign a policy to a user, the change is not applied instantly. The Teams client checks for policy updates periodically, and the refresh interval can take up to 24 hours. However, waiting longer than that usually means a different issue is blocking the pin.

The most common root cause is that the app itself is not available for the user. Every app in Teams has a status: Allowed, Blocked, or Available. If the app is set to Blocked at the org level, the setup policy cannot pin it. Another common cause is that the policy assignment is correct, but the user is signed in on a client that has cached the old policy, so the new policy is never fetched.

A third cause is that the app is not installed for the user. For third-party or custom apps, the app must be added to the org’s app catalog and granted to the user via an app permission policy. If the permission policy denies the app, the setup policy cannot override that.

How Policy Propagation Works

When you assign a setup policy, the Teams service sends the updated policy to the client during the next refresh cycle. This cycle runs every few hours, but it can be delayed by network conditions or the client being closed. Signing out and back in forces an immediate refresh. If the user has not signed out, the old policy persists.

Steps to Force the App Setup Policy and Pin the App

Follow these steps in order to diagnose and fix the pin issue. You need to be a Teams administrator to complete the first two steps.

1. Verify the app is allowed in the org-wide settings
   Open the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Manage apps. Find your app in the list. Check the Status column. If it says Blocked, select the app, click the ellipsis (three dots), and choose Publish or Allow. Wait 10 minutes for the status to propagate.
2. Confirm the setup policy is assigned to the user
   In the admin center, go to Teams apps > Setup policies. Select your policy and check the Pinned apps list. Make sure your app is listed. Then go to Users > Manage users, select the affected user, and open the Policies tab. Verify that the App setup policy shows your policy name. If it shows Global (Org-wide default), assign your policy directly to the user.
3. Check the app permission policy
   Go to Teams apps > Permission policies. Select the policy assigned to the user. Under Microsoft Apps, Third-party apps, or Custom apps, ensure the app is set to Allow. If it is Blocked, change it to Allow and click Save.
4. Sign out and sign back in to force a refresh
   Have the user open Teams. Click the profile picture at the top right. Select Sign out. Close the Teams client completely. Reopen Teams and sign in again. This forces the client to fetch the latest policies.
5. Clear the Teams cache if the app still does not appear
   Close Teams completely. Press Win+R on Windows 11 or Windows 10. Type %appdata%\Microsoft\Teams and press Enter. Delete all files and folders inside that directory. Restart Teams and sign in. The cache is rebuilt, and the new policy is applied.
6. Check the app’s availability in the Teams store
   Open the Teams app store in the client. Search for your app. If it does not appear, the app may not be available for your tenant. For a custom app, you need to upload it via Teams admin center > Teams apps > Upload new app. For a third-party app, check the app’s listing for any licensing requirements.

If Teams Still Does Not Pin the App

Teams Shows the App in the Store but the Pin Doesn’t Appear

The app is allowed and the policy is correct, but the pin is missing. This can happen if the user has multiple policies assigned. Go to Users > Manage users > select the user > Policies tab. Check the App setup policy and the App permission policy. If the user has a direct policy assignment, it overrides the global policy. Ensure the direct policy includes the pin.

The App Is Pinned but Disappears After a Few Hours

This usually occurs when the user has not signed out and the client reverts to a cached policy. Clear the cache as described in step 5. Also, verify that the policy is not changed by another admin. Check the audit log in the Teams admin center to see if any policy updates were made.

The User Does Not Have a Teams Enterprise License

Some apps require a Teams license or a specific add-on license. Check the user’s license in the Microsoft 365 admin center. If the app is marked as requiring a license, assign the appropriate license. Without it, the app will not be available to pin.

New Teams Desktop vs Teams on the Web: Policy Refresh Differences

Item	New Teams Desktop	Teams on the Web
Refresh interval	Up to 24 hours, but forces on sign-in	Refreshes on page reload
Cache clearing	Requires deleting files in %appdata%	Clears when browser cache is cleared
Sign-out behavior	Forces policy fetch on next sign-in	Fetches new policy on reload
Best for testing	Yes, after clearing cache	Yes, immediate reload

The web client is often the fastest way to test a policy change because you can simply refresh the browser. The desktop client may require a full sign-out and cache clear. Use the web client first to confirm the policy is correct, then fix the desktop client.

You can now force the setup policy to apply within minutes by checking the app status, verifying the policy assignment, and clearing the client cache. Start with the web client to confirm the pin works, then apply the same fix to the desktop app. For future changes, remember that signing out and back in is the fastest refresh method. If the pin still fails, check the audit log to see if another admin changed the policy.