Add-in activation rule about office-js-docs-reference HOT 4 CLOSED

Hi @exextoc, I would like to add here, this same bug also is still present in Exchange 2019.

As reported by our colleague @sarea in OfficeDev/office-js#991, some customers of us are facing CORS issues when they try to run our (self-hosted) OWA Add-in on their Exchange 2019 server, when our Add-In is trying to request the rest API that is defined at Office.context.mailbox.restUrl.

We have tried, but up to now, without any luck, to configure IIS to allow CORS those requests. We also posted this question on SO, since we cannot find any relevant documentation on the subject anywhere.

Is there any documentation available somewhere that explains how to configure IIS to allow self hosted OWA Add-ins in On-Premise Exchange? Either 2016 or 2019, that should not make much of a difference.

from office-js-docs-reference.

@exextoc: Please take a look at this scenario.
@vtiti: Are you able to tell which method was not allowed?

from office-js-docs-reference.

I would like to clarify a little:
I made an Outlook addin, which using the O365 REST API to get the current email attachments.

I published the addin in the AppSource.

One of our customer wants to use the addin on their Exchange 2016 On-Premises installation.

I was able to load the addin when I tried it on my test Exchange 2016 installation.
My problem was: as I stated in the manifest I supporting the 1.5 version javascript API, it shouldn't be loaded into the Exchange 2016 OWA, as it only supports the 1.3 javascript API. But it loaded, and it is suboptimal:

• I'm using the pin feature in my addin (it works with O365, but not on the Exchange).
• the REST API is not supported by the documentation, and I got 405 error for my REST API request (it works with O365, but not on the Exchange).
• I tried to workaround the REST API issue, by using the runtime check method for the getCallbackTokenAsync call, and it says it is supported both on O365 and Exchange.

I was able to use the REST API on the Exchange 2016 in the end of the day, enabling the CORS on the Exchange 2016 server's IIS.

My question really was: is the documentation wrong, or the Exchange server? What is the supported way to determine if I using my addin hosted on O365 or On-Premises?

from office-js-docs-reference.

This seems like a bug in Exchange 2016 OWA. If a client reports that it supports a certain requirement set (e.g. 1.3), it shouldn't receive add-ins that are installed on the mailbox that have a minimum requirement set about that (like 1.5)

from office-js-docs-reference.