Security Policy Errors

How to Sideload a Word Add-in When My Add-ins is Disabled

Natalie Taylor Sep 29, 2026 870 views

Question details

The user needs to sideload and test a custom Word add-in locally using only a manifest file, but organizational policies have disabled standard sideloading options.

How to Sideload and Test a Word Add-in When 'My Add-ins' Is Disabled

Product: Microsoft Word
Device & OS: not provided
Scenario: A developer or user is attempting to test a Word add-in locally via a manifest file within a highly restricted Microsoft 365 tenant environment.
Observed behavior: The 'My Add-ins' and 'Upload My Add-in' options are grayed out or disabled due to Microsoft 365 tenant policy, and network-share sideloading is unavailable.

Before you start

Ensure you have the valid add-in manifest file ready and identify your organization's Microsoft 365 IT administrator, as their permissions will be required to bypass tenant policy restrictions.

Solution 1Recommended

Deploy the Add-in Centrally via Microsoft 365 Admin Center

When local sideloading is blocked by policy, the officially recommended method is to have an administrator deploy the add-in centrally for specific users or testing groups.

Network-share sideloading is not supported for add-ins utilizing the Unified Manifest for Microsoft 365. Centralized deployment is the most reliable workaround in restricted environments.

Log into the Admin Center

Ask your Microsoft 365 administrator to log into the Microsoft 365 admin center using their administrator credentials.

Navigate to Integrated Apps

In the left-hand navigation menu, go to 'Settings', select 'Integrated Apps', and then click on 'Add-ins'.

Deploy the Add-in

Click the 'Deploy Add-in' button. The administrator can then follow the deployment wizard to manually upload your provided manifest file.

Assign to Testers

During the deployment setup, ask the administrator to assign the add-in specifically to your user account or a designated testing group so it appears in your Word client.

Deployment Sync Time: It may take up to 24 hours for a centrally deployed add-in to fully propagate and appear in your local Microsoft Word application.

Solution 2

Request a Policy Exception or Support Ticket

If centralized deployment is not feasible, work with your IT department to review local policies or escalate the issue directly to Microsoft Support.

Free Microsoft Office alternative

Try WPS Office for a Streamlined Document Experience

If strict Microsoft 365 tenant policies and complex add-in deployment restrictions are disrupting your workflow, consider switching to WPS Office. It provides a lightweight, highly compatible, and restriction-free environment for standard document processing.

1. Download WPS Office: Visit the official WPS website and download the free WPS Office installer.
2. Install the Suite: Run the downloaded installer and follow the on-screen instructions to set up WPS Office on your computer.
3. Open Your Documents: Launch WPS Writer and seamlessly open your existing Word documents (.docx) without formatting loss.

Free and lightweight Office suite with a fast installation processExcellent compatibility with Microsoft Word (.docx) formatsFamiliar user interface with no learning curveBypass complex Microsoft 365 tenant policy restrictions for everyday local document editing

microsoft office alternative - wps office

Frequently Asked Questions

Why is the 'My Add-ins' button grayed out in Microsoft Word?

This usually happens when your organization's Microsoft 365 IT administrator has configured tenant security policies to block users from installing local add-ins or uploading custom manifests manually.

Can I use network-share sideloading for Unified Manifest add-ins?

No, network-share sideloading is currently not supported for add-ins that utilize the Unified Manifest for Microsoft 365. You must use Centralized Deployment via the admin center instead.

How do I test an add-in if I only have the manifest file?

If local sideloading is disabled, you must provide the manifest file to your Microsoft 365 administrator. They can upload it via the 'Deploy Add-in' feature in the Microsoft 365 Admin Center and assign it to your account for testing.

Microsoft Office Security Issues