'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 Add-in Centralized Deployment Failure
Question details
The administrator is unable to complete the centralized deployment of an add-in from the Microsoft 365 admin center.
- Product
- Microsoft 365 Admin Center
- Device & OS
- not provided
- Scenario
- An IT administrator is attempting to centrally deploy an Office add-in to users within their Microsoft 365 tenant.
- Observed behavior
- The deployment process fails to complete, returning an error or stalling, potentially due to browser session issues, insufficient privileges, or active Microsoft service outages.
Ensure you are logged into the Microsoft 365 Admin Center with an account that has Global Administrator or Exchange Administrator permissions before attempting to configure deployments.
Use a Different Browser or Administrator Account
Resolve potential browser cache issues or account-level permission glitches by changing your browsing environment or testing with an alternate admin account.
Browser cache anomalies or stale session tokens frequently cause deployment scripts to fail in the Microsoft 365 Admin Center. Isolating the session or switching the executing account helps bypass these blocks.
Launch a new private browsing (Incognito) window in your current web browser, or switch to a completely different browser (e.g., Microsoft Edge, Google Chrome).
Navigate to the Microsoft 365 Admin Center (admin.microsoft.com) and log in using your Global Administrator credentials.
Go to Settings > Integrated apps > Add-ins and attempt the centralized add-in deployment process again.
If the deployment still fails, ask another Global Administrator within your Microsoft 365 tenant to log in and perform the deployment from their computer.
Verify Microsoft 365 Service Health and Contact Support
Determine if an active Microsoft service incident is preventing the deployment and escalate the issue to Microsoft support if the tenant is healthy.
Looking for a simpler Office solution? Try WPS Office
If managing complex Microsoft 365 admin configurations and add-in deployments is slowing down your team, consider switching to WPS Office. It provides a lightweight, user-friendly suite for Word, Excel, and PowerPoint files without the need for complicated centralized tenant deployments or heavy IT overhead.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install the Software: Run the setup file and follow the on-screen prompts to complete the lightweight installation in minutes.
- 3. Start Creating: Open WPS Office to immediately start working on your documents, spreadsheets, and presentations without complex tenant setups.
Frequently Asked Questions
What admin roles are required to centrally deploy add-ins in Microsoft 365?
To centrally deploy add-ins, you must be assigned the Global Administrator, Exchange Administrator, or the specific Centralized Deployment role within the Microsoft 365 admin center.
Why is the 'Deploy Add-in' button greyed out in the Microsoft 365 admin center?
This usually occurs if your account lacks the necessary administrative permissions, or if your organization's directory is not fully configured or synchronized with Microsoft Entra ID (Azure AD). Double-check your active role assignments.
How long does it take for centrally deployed add-ins to appear for end users?
After a successful deployment in the admin center, it can take up to 24 hours for the new add-in to appear in the users' Office applications, particularly on desktop clients. Web clients may see the changes sooner.
Does centralized deployment support users on Mac and web versions of Office?
Yes, centralized deployment supports Windows, Mac, and Office on the web, provided the users are signed in with their organizational Microsoft 365 accounts and the add-in itself is coded to support those platforms.
