@JeffYang-MSFT I have been trying MAPI over HTTP2 with latest exchange server 2019 and IIS 10.
HTTP2 is enabled on my IIS 10 server.
There are several virtual directory mapped on my exchange server(see below).
While I am able to get HTTP2 connection for some of the virtual directories(ecp, owa - these two I have tried) for others it is still HTTP 1.1 and '/mapi' is one of them.
Even though this time I am certain that I have enabled HTTP2 for IIS server MAPI connections still uses HTTP1.1.
I am wondering now if MAPI over HTTP2 has been disabled intentionally.!! If yes, why!!