I have deployed an Office Add-in and uploaded through the O365 Admin Center The Add-In appears in the Excel Ribbon but can use it as a message appears “We could not open the Add-In from LocalHost.
Should I modify anything in the Manifest File?
The Add-In was created with Yeoman and it´s addressed to “LocalHost:3000”.
It´s just a template (taskpane example)
Many thanks in advance!!!
Regards,
José.
Localhost is only used to host the add-in during development. If you have deployed the add-in with Centralized Deployment, then you should be hosting the add-in on a web server or cloud account. In that case, the URLs in the manifest should be changed to the domain that is hosting the add-in.
Related
I am stuck with deploying a Web Office Add-in in M365.
I notice that if I’m deploying a web office word add-ins using the M365 admin center (process that is recommended now), the add-in is only available for Word Online and not in Word desktop.
The only way to make it available for both (Word Online and Word desktop) is to deploy it using the SharePoint AppCatalog.
I have to add that the add-in I am testing is the sample provided with VisualStudio 2022 Wizard with no code modification.
Did I have to add a special trusted catalog in Word Desktop for deployment using admin center ?
Thanks for you help.
A word add-in that has been deployed using the M365 admin center will be available for both Word Online and Word desktop.
The following is my test. You can see the "Open in Word" shown in the list after the deployment. Then I used another user account to log in on the word desktop and as it's shown the add-in is available.
I have made a OneNote add-in, as specified here. All local tests were successful.
This project is a prototype for the development of a proprietary OneNote add-in for a client. Hence the add-in will not be published to the Office Store.
I will not be giving a development phase add-in for my clients so following Microsoft's publishing guide here, I have hosted the add-in as a Static Website on Azure. This process has provided me with a permanent link where the add-in will reside.
Using the guide provided by Microsoft, add-ins will be able to be loaded from a local manifest.xml file. but there is no input for loading the add-in from a url.
My question is, how can the client load the add-in from the link provided?
My environment:
1st VM/server: Active Directory Domain Controller
2nd VM/server: SharePoint 2016 On-Premises
3rd VM/server: Office Online Server (old Office Web Apps) also
On-Premises - version from November 2017
Done already:
Communication between SharePoint and OOS. I have also custom Office Excel Add-in uploaded to Apps for Office list in App Catalog site. Add-in itself should be fine - it works in other environment.
Issue:
When I try to install add-in in Excel in web/browser, I'm getting "Your administrator has not installed Web Add-ins for your organization" message:
screenshot
I have got also uploaded Office Excel Add-in to Apps for Office list in App Catalog, and it still does not work. Did I miss something in the configuration to allow adding custom add-ins?
I suppose a sharepoint catalog and app store add-ins are mixed in you post.
Instead of uploading the add-in Office 365, under Setting>Service & add-ins, try uploading the add-in in SharePoint Online Add Catalog site. To do this, please follow the steps below:
Sign in to Office 365 portal with admin credentials.
Go to Admin Center>SharePoint Online Admin Center.
Once you are in SharePoint Admin center, go to App Catalog site, URL should be something like https://tenant.sharepoint.com/sites/AppCatalog
Click Apps for Office on the left navigation panel to upload the add-in for Office apps.
Click Upload and browser the path where the custom add-in is saved on your system.
See Excel does not show Office 365 custom add-in for more information
My custom Office Excel add-in does not work in my DEV environment (1) with the following three VMs.
Proper DEV on-prem environment:
AD Domain Controller
SharePoint 2016 on-prem
Office Online Server (updated November 2018)
OOS works as I can open Office docs in the browser. Both SharePoint and OOS run on http.
Online environment (just to test add-in itself):
I have tested the same - sample Excel add-in generated by Yeoman - in different environment too: O365 and SharePoint Online (developer tenant). It works, manifest is added to Apps for Office in AppCatalog and server works on https://localhost. I can see task pane of add-in in the browser. I can also debug both: desktop and web.
The same add-in (with server running on https://localhost) which works in online environment (2), does not work in DEV environment (1). It does not work when I upload XML manifest to AppCatalog, and it does not work when I try to debug generated add-in too.
I saw Excel add-in working in Internet Explorer on environment also with SharePoint 2016 and Office Online Server (/Office Web Apps). However, I do not have more details about that environment and how this add-in has been installed.
I have written a small officeJS addin for excel which run perfectly on desktop excel client. Also office online from onedrive gives an option of installing the addin from the ribbon menu. I want to use this officeJS addin to run on either of the following configuration:
On premise office online server configured with on premise
sharepoint server.
On premise office online server with my own
implementation of wopi host.
How to deploy an officeJS addin on office online on premise server which is preferably managed centrally by the administrator.
Also why is the add-ins option is not available on the office online configured with sharepoint, pfa image:
office online onedrive v/s office online onprem with sharepoint
Thank You
The Office Online Server currently doesn't enable Office store by default. As part of the configuration, you'd have to enable it. I'm not 100% sure about the exact setting. It may be this: set the AllowExternalMarketplace flag to true.
More here
Try this. On a server in the farm, open the SharePoint Management Shell (PowerShell). Run this command:
Set-OfficeWebAppsFarm - OfficeAddinEnabled:$true
You probably have to be logged in as a farm administrator.
There is some documentation here: Set-OfficeWebAppsFarm