how to deploy non-M365 add-ins to user desktops using intune

Question

Previous admin set up the tenant that non M365 add-ins can't be installed. Any suggestion how to bypass that?

Answer 1

Hello leah Ogeto,

The centralized management of M365 add-ins usually happen from the admin center, whether deploying add-ins and restricting usage or disabling access to marketplace for add-ins.

Refer to: Manage Add-ins in the Microsoft 365 Admin Center - Microsoft 365 admin | Microsoft Learn

For disabling access to Marketplace (called as Office Store) to restrict add-ins for users, refer to: https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-addins-in-the-admin-center?view=o365-worldwide&tabs=word-excel-powerpoint#enable-or-disable-access-to-the-microsoft-marketplace-for-all-apps

Also, refer to: Requirements to use centralized deployment for Office Add-ins - Microsoft 365 admin | Microsoft Lea…

Hope this helps!

If you found the information above helpful, please Click Yes. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.

Answer 2

Non–Microsoft 365 (line-of-business or third‑party) Office add-ins are controlled at the tenant level by how add-ins are deployed and by whether users are allowed to acquire add-ins from Microsoft Marketplace. To deploy such add-ins with Intune-managed desktops, use centralized deployment or the integrated apps portal rather than trying to bypass tenant restrictions.

Use the following approaches:

1. Check and use Centralized Deployment
   • As a Microsoft 365 admin, deploy Office add-ins to users or groups via Centralized Deployment instead of letting users self-install.
   • Centralized Deployment can be managed either:
     • In the Microsoft 365 admin center (recommended primary method), or
     • With PowerShell using the O365CentralizedAddInDeployment module.
   • Install and connect the module:

          Install-Module -Name O365CentralizedAddInDeployment
          Import-Module -Name O365CentralizedAddInDeployment
          Connect-OrganizationAddInService
     

   • Once connected, use the Centralized Deployment cmdlets to upload the manifest for the non‑M365 add-in and assign it to users or groups.
2. Use the integrated apps portal for internal or ISV add-ins
   • In the Microsoft 365 admin center, use Integrated apps to deploy internal add-ins or ISV add-ins to users and groups.
   • This method makes add-ins available directly in Office apps without client-side configuration.
   • If the add-in uses the unified manifest and is distributed as an internal add-in via Integrated apps, verify that users’ Office clients are on supported versions as described in the unified manifest client and platform support documentation.
3. Control user access and deployment method
   • If the previous admin disabled user self-install from Microsoft Marketplace, keep that control in place and instead push the add-ins centrally.
   • Centralized Deployment supports three deployment methods for Outlook add-ins:
     • Fixed – automatically deployed; users cannot remove it.
     • Available – users can install from Home > Get More add-ins > Admin-managed.
     • Optional – automatically deployed but users can remove it.
   • Choose the method that matches the organization’s policy; this avoids “bypassing” restrictions while still delivering non‑M365 add-ins.
4. If add-ins are blocked via app settings (for example, OneNote)
   • Some apps (such as OneNote) can have add-ins disabled via Intune configuration (for example, DisableOfficeAddins for OneNote on iOS or a Windows 10 OMA-URI policy).
   • If such a policy was set by the previous admin and needs to be changed, update or remove the corresponding Intune app or device configuration profile so that add-ins can run again.

In summary, instead of bypassing tenant restrictions, deploy non‑M365 add-ins centrally using Centralized Deployment or Integrated apps, and adjust any Intune policies that explicitly disable add-ins in specific Office apps.

---

References:

• Use the Centralized Deployment PowerShell cmdlets to manage add-ins
• Deploy and publish Office Add-ins
• Centralized deployment FAQ
• Enterprise Data Protection considerations in Microsoft OneNote