How to deploy Templafy Library web add-in with manifest file?

Updated February 22, 2023 08:57

About this article

For a better user experience, Templafy supports deploying the Library web add-in (Office online & Mac) using a manifest.xml file. Please follow the steps in this article.

Seamless SSO and provisioning
Step-by-step guide deployment

Prerequisites

On a Windows device, Version 1704 or later of Office 365 ProPlus. On a Mac, Version 15.34 or later. Check all requirements here: Determine if Centralized Deployment of add-ins works for your organization
You need to be a Global Azure Admin to perform the below steps
Contact your Partner or Templafy Support at support@templafy.com for a custom manifest.xml file

Please notice: Centralized deployment of add-ins requires that the users are using Microsoft 365 Enterprise SKUs: E3/E5/F3 or Business SKUs: Business Basic, Business Standard, Business Premium (and are signed into Office using their organizational ID), and have Exchange Online and active Exchange Online mailboxes

Seamless SSO and provisioning

For SSO to work without user interaction, you must reach out to your Partner or Templafy Support for a custom manifest.xml file. This is to ensure that users are redirected correctly to your tenant-URL to initiate the SP-login and provision the users correctly to your own tenant.

Step-by-step guide deployment

Go to the O365 Admin Portal (https://admin.microsoft.com)
Click "Settings"
Click "Integrated apps"
Click "Upload custom apps"
Select "I have the manifest file (.xml) on this device." and click "Choose file"
Browse location of the manifest file (.xml) for upload
Click "Upload"
Select which Users/Groups should have access (or "Everyone") and click "Deploy"

Note

It usually takes up to 15 minutes for the add-in to be deployed but can take up to 24 hours in some cases. You will receive an email notification confirming your successful deployment. Users might need to relaunch ‎Office‎ to see the add-in icon in the ribbon.

If your Office version for Mac is lower than 16.36 (released on 04/13/2020) the WebAdd-in may not automatically display in the ribbon. If this occurs, users will have to manually add the WebAdd-in from the Admin managed part of the Add-in store (WebAdd-in is deployed to O365 devices but not being displayed)