I want to sideload an office add-in to my ms-office word application, but do not want to enable the privacy options to allow office to connect to the online services from microsoft.
I have the restriction that the office application should only use my web-addin within our network.
But my add-in only loads when I enable the option: "Allow office to connect to online services from microsoft..."
(Word > Options > Trust Center > Privacy Options > "Allow office to connect to online services...")
At this time I tried two ways:
load it from Registry with a Add-In Developer entry
load it from network share as a trusted catalog (set via registry)
Is there a way to load my add-in anyway by setting registry keys?
Maybe somebody has a possible way to load it anyway?
Instead of turning off any connections you may consider using the admin center and deploy add-ins centralized, so the admin could manage add-ins that are allowed to run. See Manage add-ins in the admin center for more information.
As an organization you may wish to prevent the download of new Office add-ins from the Office Store. This can be used in conjunction with Centralized Deployment to ensure that only organization-approved add-ins are deployed to users within your organization.
Related
I have notice this error happens for ALL modern Outlook Office Add-ins. Searching the net I can also see that many other Modern Outlook Add-ins are having the same issue. We know that this is an Outlook Client issue. You never get the error on OWA.
I have also seen that Microsoft are suggesting
Open Internet Explorer
Click Tools
Click Internet Options
Click Security tab
Select Internet Sites zone
Select Enable Protected Mode (make sure box is un checked)
Click OK
Restart Internet Explorer and Outlook
However, we cannot ask customer to do this. Many are not even using IE. And it doesn't work most of the times!
In our case the Add-in service is running on Azure. We have enabled application insight and are monitoring failures on a daily basis. Our service is running on 20% of the avilable capacity. I feel that we have done all that we could. We are stock! and very frustrated.
Logically, when the Add-in works with no error in OWA, and only fails in the Outlook client this can only mean the error is in Outlook or windows or.... meaning it is a Microsoft error.
This error is by-design for add-ins in Outlook clients that are rendered using IE and do not have Protected Mode enabled. Protected Mode is a security feature when using IE, and it is strongly recommend that it be enabled while using add-ins.
If you do not or cannot enable Protected Mode, a possible workaround is to upgrade to a newer Windows and Office, so add-ins are rendered using Edge Webview instead of IE. Details about what versions that Webview are supported can be found here.
We have developed an addin for Word 2016 (relevant for 2013 as well) which consists of a manifest.xml and a web project serving html and javascript. We want to distribute this addin to all the users in an organization.
We do not have any trouble setting up the webservice and pointing the manifest to it, however the issue is distributing the xml and installing it into the Word instances on user's computers.
What is the simplest way for an organization admin to inject this addin into users Word applications?
Have you considered centralized deployment?
The Office 365 admin center makes it easy for an administrator to deploy Office Add-ins to users and groups within their organization. Add-ins deployed via the admin center are available to users in their Office applications right away, with no client configuration required. You can use Centralized Deployment to deploy internal add-ins as well as add-ins provided by ISVs.
My company uses MS dynamics CRM 4.0 and I can only access the client side of it (using the URL in IE to open the CRM system).
I can see that the system could do with some enhancements and plug-ins.I want to work on them because when I suggested these enhancements I was told that the system will be upgraded, after maybe 2 years. So no one is working on making it better even though the extension could really help the users.
Details: Currently, users enter details for each sale into the system. This takes a lot of time because the server and centralised database is in another continent. What I want to do is to have the users enter their data into an excel sheet and a system scheduler will upload the data overnight.
My question is can I develop, plug-ins or extensions etc, on the CRM with VS Express Edition? I have no access to the CRM Server or database since I'm using only the browser to use the system to enter data, just the client side CRM window.
Edit This is not lack of research. I have not found an answer to this anywhere.
I appreciate your expertise and experience.
If you are talking about .NET, server-side plugins, you'll need the following things as described on the "Creating a Simple Plug-in" page of the 4.0 SDK:
To complete this walkthrough, you will need the following:
Visual Studio 2005 or Visual Studio 2008.
A pre-built version of the Plug-in Registration tool.
A Microsoft Dynamics CRM SDK installation.
Network access to a Microsoft Dynamics CRM 4.0 server.
A Microsoft Dynamics CRM system account with either the System
Administrator or System Customizer security role, which is also a
member of the Deployment Administrators group in Deployment Manager.
The line about network access to the server I'm not so sure about. If you register the plugin to the database as you typically would, I don't think you'd need network access; if you deploy to disk, that's when I think you need it.
If by "extensions" you mean things like adding scripts to forms, the only thing you'd need is the System Customizer or System Administrator roles.
Update based on your addition to question:
If you want to schedule a daily import, you should be able to do that with the limited, web-only access you have (assuming you have enough privileges to kick off imports [which, if you can do it through the UI, you can do it programmatically]). Your program could run and kick off import jobs (see "Configuring Data Import" page of SDK). I know for sure you could kick off imports of csv's, not sure about programmatically importing excel files, but you could programmatically transform the excel files to csv and then kick off the jobs.
I am having a horrible time getting started at creating an add-in for Outlook. I want to use the new html/javascript/manifest approach. I have been able to create a manifest and application which works great with outlook.live.com. Where I am completely getting stuck is with desktop Outlook. How do I install/debug my add-in with desktop Outlook?
I cannot find anything in the UI which will let me add this style of add-in. Additionally the Microsoft documentation did not make things any clearer. Their docs seem to hint using this type of add-in is only possible if you are connecting to an Exchange server.
Any help would be greatly appreciated.
Yes the add-in will load on Outlook desktop only if your mailbox is Exchange. I am not sure the add-ins work with a personal Microsoft account (e.g hotmail.com, outlook.com) and Office desktop. Keep in mind that the support of mail add-ins for personal account is relatively new (officially announced in march 2016).
To develop your add-in I suggest you to use a organizational account (i.e. Office365 account). Support for organizational account has been released in 2013 and is a much more mature solution for you to get started. You can have a free dev account at dev.office.com.
Edit: October 2016 personal account are supported now by "Personal mailbox accounts" aka outlook.com accounts
Let us keep in mind that a mail add-in is not installed on a mail client (desktop, OWA) but on the mail account. When you "install" an add-in you only set a xml file on your mailbox that basically says "there is a web add-in out there called X and that is served at this url...". Then, if you install add-in X on your mailbox smaclell#mytestcompany.onmicrosoft.com, this add-in will load the add-in web iframes whether you are consulting your mailbox with Outlook Web Access (OWA) or Outlook Desktop.
To install the add-in for one user mailaccount, you have to use the Outlook Web Access. See this blog post. Note also that you can install the add-in for the whole organisation (Admin > Exchange Admin > Add-ins). Finally, Visual Studio is also able to push the manifest to your office 365 mailbox. To have this you need Office Development Tools.
For debugging in Outlook Desktop, I know two approaches.
Use the Office Developement Tools with visual studio
and select your sample add-in project as 'Starting project' and in properties select 'Office Desktop'.
Plain web development.
Personally, I do not use really much the Office Development Tools. I install manually my add-in with "https://localhost:XXXX" for url and I start the web project on IIS express to do the debugging. For stepping into the source code, I use the debugger of my browser (Chrome, Edge, IE etc.) when browsing in OWA. When I need to step into source code specifically on Desktop (For windows or for Mac) I use Vorlon.js see also this blog post.
My advice is also to test/debug frequently with IE 11 (still available in Win10!) and OWA. Indeed, the browser used internally by Office Desktop for the add-ins is IE.
I want to develop all-in-one add-in for Outlook. This means that this add-in will be available for all Outlook clients (desktop, web).
I read here that i can do this. I already created add-in for Outlook Web Application and tried to deploy it to desktop client, but didn't figure how to make it. So how to make it set on desktop and outlook.com? Is that really possible? And if yes, how it can be done?
Technically you can't make an add-in that will work 100% on all clients. The web-based add-ins currently only work with Mailboxes hosted on Office 365 or Exchange 2013 or greater, and with Outlook 2013 or greater. Outlook.com integration is coming this spring. COM/desktop add-ins work with Outlook 2000-2016, but not in OWA.
To deploy an add-in you need to either publish it to the Office Store or an Exchange Server. See here for more info: https://msdn.microsoft.com/en-us/library/office/fp123515.aspx.
To install a self-published add-in that is not in the Office Store you just add the manifest file from the "Manage add-ins" page in OWA: https://msdn.microsoft.com/en-us/library/office/fp142256.aspx
Note also that you must host your web add-in code in your own web server, and secured with an SSL certificate.