...
You will need proper rights to follow the installation process.
Step 1 — Connect to your tenant administration Add-In management page
Here is the link to follow : https://admin.microsoft.com/AdminPortal/Home?#/Settings/AddIns
You can also find the Add-ins option in : Settings / Add-ins menu.
...
Step 2 — Follow the Deploy Add-in Wizard.
Click on the “Deploy Add-in” button
...
| Info |
|---|
Wedia project managers can find the manifest.xml files in the /samples/office-picker-confi-sample directory in our internal git directory. Please ask to Product team for any question related to configuration of these xml files. Users with a git access can follow this link. https://bitbucket.org/wediaproduct/portal/src/master/samples/office-picker-config-sample/manifest-dev-club-wed.xml |
Step 3 - Validate the manifest.xml
Whereas this step is not mandatory, it’s a good idea to validate your customised manifest file.
Given node is installed on your machine, you can run the following command:
| Code Block | ||
|---|---|---|
| ||
npx --ignore-existing office-addin-manifest validate <PATH_TO_YOUR_MANIFEST_FILE> |
Detailed explanations can be found at https://docs.microsoft.com/fr-fr/office/dev/add-ins/testing/troubleshoot-manifest
...
If the upload is successful, a recap screen will show you this plugin screen :
...
This can also be used to disable the add-in completely.
Validate the manifest.xml
You might encounter an error when deploying manifests if they are not valid. You can get detailed explanations to know how to correct your manifests.
Given node is installed on your machine, you can run the following command:
| Code Block | ||
|---|---|---|
| ||
npx --ignore-existing office-addin-manifest validate <PATH_TO_YOUR_MANIFEST_FILE> |
Detailed explanations can be found at https://docs.microsoft.com/fr-fr/office/dev/add-ins/testing/troubleshoot-manifest