Update 3/4/2022: The REST API for on-premises mailboxes preview is ending. Please see this blog post for more information.
Hybrid customers are able to take advantage of the REST APIs for both Offi...
Updated Mar 04, 2022
Version 3.0
Blog Post
Hi Ross,
From a load-balancer perspective, since the recommendation is to do L7 then you can just do it with smart load-balancers able to do pool selection (e.g. F5, ALOHA/HAProxy) :
- create a RestAPI Pool - monitor /api/healthcheck.htm
- use that pool for the /api/* Uri Path (e.g. with F5 this is done by using an iRule, with ALOHA/HAProxy this is done by configuring the back-end appropriately)
That way, anything aiming at https://exchange.contoso.com/api (whatever the namespace you choose) will target Exchange 2016 CAFE only. If the Autodiscover web service is also involved, then leave only Ex2016 servers in the AutoD pool...
Makes sense ?
Now, this is with L7 and advanced LBs. L4 is not recommended so anyone using a "recommended" implementation should be able to continue coexistence flawlessly.