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.
Related
I am trying to create an Outlook add-in with the onSend function. I can see on the GitHub onSend Tutorial that onSend is only supported on Outlook web and 365. Has this been updated now (the readme is 2 years old)? I am trying to debug mine on Outlook desktop 2016 (using Visual Code + Edge extension) and the debugger never reaches the function I created and that is supposed to be reached during the onSend event.
If still not supported, can I still deploy this add-in via 365 (admin) and get it reflected on Outlook desktop 2016?
Thank you very much.
The On-Send feature is supported by the desktop editions of Outlook for Windows. Make sure you deal with the supported version of Windows, Exchange server, Outlook. Read more about that in the On-send feature for Outlook add-ins article.
OnSend is not supported in Outlook Desktop 2016.
How can I find which Outlook build numbers/versions correspond/support the different Mailbox API requirement sets? I have an add-in that requires the API requirement set 1.8 or higher, but I do not know which Outlook versions/build numbers correspond to this API requirement set.
Support for 1.8 in Outlook on Windows with a Microsoft 365 subscription or a retail one-time purchase is available from version 1910 (build 12130.20272). Read more about requirements sets and supported hosts in the Outlook JavaScript API requirement sets article.
Note, if your target Exchange server and Outlook client support different requirement sets, then you're restricted to the lower requirement set range. For example, if an add-in is running in Outlook 2016 on Mac (highest requirement set: 1.6) against Exchange 2013 (highest requirement set: 1.1), your add-in is limited to requirement set 1.1.
That's why I'd always recommend using the Office.context.requirements.isSetSupported method at runtime to be sure the API is supported.
I've submitted my outlook add-in 6 times now and every time the certification failed for a different reason. The last rejection reason I got was that my add-in didn't work on Office 2013 and Office 2016 (which they also refer to as O365 Perpetual).
I develop on a Mac and I have no idea how to go about debugging why my add-in is not working on those older Offices. Can't I just drop support for older Office suites? How could I test these environments?
I'm pretty close to quitting and just not publishing my outlook addin. I have never experienced a worse app review process.
If you want to be published on the Office Store, you need to support all the platforms for the minimum Outlook API Requirement Set in your manifest.
If you do not need to support Outlook 2013 or Outlook 2016, you can set your minimum API requirement set to 1.5, which will drop support for those versions (1.4 was the last version supported by those versions of Outlook). When you submit to the Office Store, please make a note that your minimum API set means that the add-in will not run in those Office clients.
I have developed a web addin for outlook. This is an on send feature for outlook web email. This is working as expected for the 'the new Outlook on the web' version of office 365 but is not working for the classic web version of office 365.
to enable the on-send feature on classic (old) OWA, you have to request your admin to run cmdlets as described in the URL here
Enabling onSend for classic OWA
Classic OWA will cutover to the New OWA shortly. Classic OWA will be retained only for on-prem users
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.