I did some research on Publishing Outlook addins in Appsource. There is a slight confusion on whether SSO addins are accepted in AppSource or not.
I have found an requirement document on the Appsource site that SSO is an requirement however, on the SSO addin site it mentions SSO addins are not accepted in AppSource. Please help me on this :)
The documentation you linked to is correct. As of January 2020:
The Single Sign-on API is currently supported in preview only. It is
available to developers for experimentation; but it should not be used
in a production add-in. In addition, add-ins that use SSO are not
accepted in AppSource.
Related
Our company is unable to log into a particular Office Add-in using ADFS SSO. The SSO does not appear to “hook” correctly and instead redirects to a blank page. This issue only occurs in Outlook 365 for Windows. We tested this on both managed and unmanaged machines as well as on and off prem. Outlook 365 for Mac and Outlook 2019 Professional Plus for Windows both work fine.
We examined our firewall and ADFS logs but nothing appears to be blocked. We also checked Office 365 admin center to see if there were security settings preventing Office Add-ins from working correctly but did not find any.
We troubleshooted with the developers of the Add-In but they have not been able to identify the cause of this issue. At this point we are scratching our heads. Is this a programming issue or something else?
Thanks in advance!
Does outlook 2016 (desktop) support SSO with add-ins?
I can't use OfficeRuntime.auth.getAccessToken and Office.auth.getAccessToken in desktop outlook client.(error with undefined)
Systeminfo:
Windows 10 Enterprise(19044.1706)
Microsoft Outlook 2016( 16.0.5197.1000) MSO(16.0.5278.1000) 32bit
(Microsoft Office Professional Plus 2016)
SSO requires Identity API set 1.3. To require this API set in your Outlook add-in code, check if it's supported by calling isSetSupported('IdentityAPI', '1.3'). Declaring it in the Outlook add-in's manifest isn't supported. You can also determine if the API is supported by checking that it's not undefined.
The following table lists the Identity API requirement sets, the Office client applications that support that requirement set, and the build or version numbers for the Office application.
If you are working with an Outlook add-in, be sure to enable Modern Authentication for the Microsoft 365 tenancy. For information about how to do this, see Exchange Online: How to enable your tenant for modern authentication.
Can we deploy outlook web-addins for O365 accounts using centralized deployment as described here ?
Three/Four months before, if I tried to install outlook add-in using this method, installation itself would fail. Now, I don't get any errors while installing, but the add-in does not appear in Outlook clients (Outlook 2016 in Windows and OWA in browsers).
Are centralized deployments supported for Outlook add-ins now? Also, are there any client side requirements? I found some related information here. But I am doubtful if it is up-to date.
Thanks for the query bala. Centralized deployment for Outlook add-ins is not supported as of now and will come very soon. There are no specific client requirements other than minimum requirements for add-ins.
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.
Here was said All-in-one add-in for outlook that this is possible to create the web-based add-in working both with Mailboxes hosted on Office 365 or Exchange 2013 or greater, and with Outlook 2013 or greater, so with web and desktop Outlook versions.Am I right? Can you provide some references on how to develop such an add-in and then install it for both clients? Thanks you.
Best regards
You can start reading the Official documentation on Office add-ins. These new Office add-ins are web applications "served" inside Office products, you will have to be a little familiar with web technologies to develop.
Regarding Outlook add-in, as written by Eric Legault (in the question link), the add-in is not installed on a specific client but on the exchange account whether it is at organisation level or at user level. Consequently, with one install you will have the add-ins working on all Outlook clients (Desktop, OutlookWebAccess etc.).
Take care: Office add-ins now describes both technologies the new one that we are discussing (formerly app for office) and the old COM add-ins. I have written a blog post to explain the in-and-outs of the two technologies.
You are right. You have the opportunity to create a web-based add-in for Office 365 and Office 2013 desktop. But, Microsoft's JavaScript API has limited functionality. I want to recommend you read the following document first: https://msdn.microsoft.com/en-us/en-us/library/office/fp161015.aspx. If you plan to write a small add-in for yourself, the web-based add-in is a great option.