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 steps in this article.
Jump to section:
- Seamless SSO and provisioning
- Step-by-step guide deployment
-
How retrieve the original product ID if your manifest upload failed due to a product ID issue
Prerequisites
|
|
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
Uploading a new add-in
- Go to the Microsoft 365 Admin Portal (https://admin.microsoft.com)
- Click
Settings
- Click
Integrated apps
- Click
Upload custom apps
- Select
Upload manifest file (.xml) from device.
and clickChoose file
Browse location of the manifest file (.xml) for upload, select it and click "Open" - Select which Users/Groups should have access (or Everyone) and click
Next
- Accept permissions request by clicking
Next
- Click
Finish deployment
to begin the deployment of the add-in - On this step, the progress for the deployment can be monitored
Updating an existing add-in
- Go to the Microsoft 365 Admin Portal (https://admin.microsoft.com)
- Click
Settings
- Click
Integrated apps
- From the list of deployed apps, choose Templafy Company Templates
- Double click the Templafy app to open the app overview
- In the app overview, select
Update add-in
from the Actions menu - Select
Upload manifest file (.xml) from device.
and clickChoose file
Browse location of the manifest file (.xml) for upload, select it and click "Open" - Click
Next
- Accept permissions and initiate the update by clicking
Accept and update
|
How retrieve the original product ID if your manifest upload failed due to a product ID issue:
- Open the developer tools from your browser (F12 for Windows, Cmd+Opt+J for Mac)
- Reupload the manifest to trigger the error message
- In the developer tools click on the uploadCustomApp reuqest
- You can find the original product ID under the Payload header
- Please note, that the product ID can only be retrieved from the developer tools. IDs that might appear in upload error message are not related to the product ID.
Note
|
If your Office version for Mac is lower than 16.36 (released on 04/13/2020) the web add-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)
Comments
0 comments
Article is closed for comments.