Forum Discussion
Developing Apps for Exchange Server
Yes, it's technically possible to build an app that integrates with on-premises Microsoft Exchange using Exchange Web Services (EWS), but it's far more complex and limited compared to Microsoft 365. Authentication typically relies on legacy methods like Basic Auth, NTLM, or Kerberos, with OAuth2 only available in hybrid Exchange 2016/2019 setups. There's no Graph API support, and each customer environment can vary widely, making development and deployment challenging. While some industries still use Exchange Server for security or compliance reasons, the trend is clearly toward Microsoft 365, so investing heavily in Exchange on-prem integration is generally not recommended unless you’re targeting a specific niche or offering migration support.
------------------------------------
Don't forget to mark as solution if my answer suits you
Yes, it's technically possible to build an app that integrates with on-premises Microsoft Exchange using Exchange Web Services (EWS), but it's far more complex and limited compared to Microsoft 365. Authentication typically relies on legacy methods like Basic Auth, NTLM, or Kerberos, with OAuth2 only available in hybrid Exchange 2016/2019 setups. There's no Graph API support, and each customer environment can vary widely, making development and deployment challenging. While some industries still use Exchange Server for security or compliance reasons, the trend is clearly toward Microsoft 365, so investing heavily in Exchange on-prem integration is generally not recommended unless you’re targeting a specific niche or offering migration support.
------------------------------------
Don't forget to mark as solution if my answer suits you
Got it, thanks. Marked your answer as solution.
I've researched more into the topic, so decided not to pursue any further discovery of this use-case.We'll continue to build ActorDo just for the cloud version.
Thank you for the answer!
