Adding Add-ins to Exchange 2016 onprem redirects me to Exchange Online

Question

I am trying to add the new GoTo for Outlook add-in to our onprem Exchange server.
The process is as follows:

1. Open Exchange ECP
2. Go to Organization, Add-ins, Click "+" sign
3. Select Add from the Office Store
4. Select "Get it now" button on GoTo for Outlook addin
5. get redirected to Exchange Online Addins section
6. Accept defaults for plugin and it is added to Exchange Online Addins section

I believe the issue has something to do with a few years ago we were testing hybrid mode between our Exchange onprem and Exchange online. We have since disabled/removed the hybrid connection but I think there is still a redirect for our Exchange onprem to Exchange online for addins.

I have tested adding the addin from a test install of Exchange 2016 and was able to install the addin on the local Exchange server. So the issue is not with the addin.

Can someone point me to where in the registry or in Exchange I can see where or how Exchange knows to go to Exchange online instead of using the local onprem exchange server?

Thanks,
Thomas

Answer 1

Hi @TDx2

Thanks for your feedback above which shared more information and glad to know that your issue is resolved now! Since our forum has the policy that The question author cannot accept their own answer. They can only accept answers by others, and according to the scenario introduced here: Answering your own questions on Microsoft Q&A

I would make a brief summary of this post so that other forum members could easily find useful information here:

[Adding Add-ins to Exchange 2016 onprem redirects me to Exchange Online]

Issue Symptom:
When performing the action Adding Add-ins in Exchange 2016 ECP, the page will get redirected to Exchange Online Addins section

(Possible) Cause:
O365 license is assigned to the admin account

Solution:
When created a new user that had not been assigned O365 licenses. Then made it an administrator for Exchange and when I added the new addin it worked as it should.

You could "Accept Answer" for this summary to close this thread, and your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding!

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The issue ended up being related to our O365 license. I created a new user that had not been assigned O365 licenses. Then made it an administrator for Exchange and when I added the new addin it worked as it should.