As far as I know, the only way to deploy an Outlook add-in with a unified manifest (outside of AppSource) is through the Microsoft 365 Admin Center. You can do it manually by going to admin.microsoft.com - Settings - Integrated apps - Upload custom apps. It’s not scriptable, unfortunately, but for now, it’s the only officially supported method to deploy unified manifests to Outlook in a tenant.
Ways to use a script to deploy an Outlook add-in with unified manifest?
Buck I
16
Reputation points
I have an Outlook add-in that uses a unified manifest, and I want to deploy it to just my organization or my customers' organizations (so I don't want to put it in AppSource). Also, I'd like to be able to do this with a script. How can I do this? It seems like most mechanisms for deploying an Outlook add-in don't accept a unified manifest, is that true? Some methods I'm wondering about are:
- The ExchangeOnlineManagement PowerShell module. The
New-App
cmdlet does not seem to accept a unified manifest. - The Centralized Deployment PowerShell module. The
New-OrganizationAddIn
cmdlet does snot seem to accept a unified manifest. - The Microsoft Teams PowerShell module. The
New-TeamsApp
cmdlet accepts a unified manifest, but I'm not sure if it will work for an Outlook add-in.
Are there any other scripting or API ways to install an Outlook add-in that will work with a unified manifest?
Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
4,348 questions