Troubleshooting Centrally Deployed Office Add-ins (Word/Excel/PowerPoint)

Guide: 

Troubleshooting Centrally Deployed Office Add-ins (Word/Excel/PowerPoint)

---

1) Verify Deployment & User Assignments

Before troubleshooting clients, confirm the add-in is still correctly deployed:

• Sign into Microsoft 365 admin center → Settings → Integrated apps → Add-ins.
• Confirm the add-in is active and assigned to the correct user(s) or group(s).
• Centrally deployed add-ins do not support nested groups. A user must be a direct member of the target group.
• If the user was removed from the group, they lose access to the add-in.

2) Refresh the Add-ins List in Office

On the user's Office client:

1. Open Word/Excel/PowerPoint.
2. Go to Insert → Get Add-ins.
3. Switch to the Admin-managed tab.
4. Click Refresh in the top-right corner. This forces Office to re-download the deployed add-in list from Microsoft 365. 

If the add-in supports add-in commands, the icon should also appear on the ribbon after it's downloaded.

3) Full Office Sign-Out & Restart

Sometimes Office holds onto stale credentials or cached state:

• Have the user completely sign out of all Office apps.
• Close all Office applications.
• Wait ~30–60 seconds.
• Sign back into Office and open the relevant app. This often forces a fresh token refresh and manifest re-sync.

4) Clear the Local Office Add-in Cache

Office caches add-in manifests locally. A corrupted or stale cache can make an add-in disappear even if it's still deployed.

Windows

1.Close all Office apps.

2. Delete everything in:

%LOCALAPPDATA%\Microsoft\Office\16.0\Wef\

3. Re-open Word/Excel/PowerPoint.

Mac

1. Quit the Office app.

2. Delete the equivalent Wef folder under:

~/Library/Containers/com.microsoft.[Word|Excel|PowerPoint]/Data/Library/Application Support/Microsoft/Office

3. Relaunch the app.

Clearing the cache forces Office to re-fetch add-in manifests from Microsoft 365. 

5) Check in Office on the Web first

Have the user open the same file in Office for Web:

• Go to https://www.office.com and open Word/Excel/PowerPoint online.
• Open Insert → My Add-ins → Admin-managed.

If the add-in shows up online but not on desktop, it confirms the issue is client-side caching or credentials, not deployment.


6) Give Time for Backend Propagation

Centrally deployed add-ins can take time to propagate through the Microsoft 365 backend, especially after changes:

• New deployment → up to 24 hours for visibility to users.
• Deployment changes (turn on/off, assignments) → up to 72 hours to fully propagate.

If the issue just started or the assignment changed recently, it's worth waiting and re-checking after propagation completes.


7) Optional: Run the Compatibility Checker

Microsoft provides a Centralized Deployment Compatibility Checker that verifies users meet the licensing and environment requirements for centralized deployment (Office version, Exchange support, etc.). 

See:
https://learn.microsoft.com/en-us/microsoft-365/admin/manage/centralized-deployment-of-add-ins

Quick Diagnostic Flow (for support teams)

1. Does the add-in show in Office for Web?
   
   → Yes → Client issue (cache/login).
   → No → Deployment eligibility / group assignment issue.
   
   
2. Refresh the Admin-managed list in the Office Add-ins dialog.
   
   
3. Full Office sign-out + restart.
   
   
4. Clear the local add-in cache.
   
   
5. Confirm user is direct member of assigned group and wait for propagation.
   
   

Important Notes

• Microsoft's centralized deployment doesn't support nested groups, this is the most common assignment issue. (Microsoft Learn)
• Users must be running a supported version of Office with organizational sign-in. (Microsoft Learn)
• Caches and tokens often cause disappearing behaviour more than actual deployment errors. (Microsoft Learn)