Update 11/27/2018: Few more updates to the article.
This post explains the configuration steps needed to get rich document collaboration working between Exchange Server 2016, SharePoint Server ...
Updated Apr 17, 2020
Version 3.0
Blog Post
6 MIN READ
Configure rich document collaboration using Exchange Server 2016, Office Online Server (OOS) and SharePoint Server 2016
We have all on-premises Exchange 2019 mailboxes, Sharepoint 2016 with ODB on MySite running, Skype for Business 2019, and OOS 2016 for document rendering.
- OOS integration for Exchange 2019, SharePoint 2016 and Skype for Business is running normally.
- S2S integration between Exchange 2019 and Skype for Business is also running normally.
- All communication is via HTTPs with commercial SSL certificates.
However, we are quite stumped in completing this article's objective of having attachment link from within OWA to the on-premise's ODB.
Maybe somebody could shed some light on possible steps we missed?
1. SharePoint 2016->Exchange 2019 S2S configuration was completed using the Config-SPSOAuth.ps1 script (apparently the script requires SharePoint's App Management shared service to be installed beforehand)
2. Exchange 2019 -> SharePoint 2016 S2S was also done via Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint script.
3. Created & applied a OWAMailboxPolicy to a test mailbox on Exchange 2019 & restarted the OWA App Pool.
After all the above, clicking the Attach link in OWA always opens the legacy Open window and we are still not able to display the OneDrive integration attachment choice as described.