Over the last several months, we have seen many customers adopting Microsoft Teams, even if their mailboxes are still hosted in an on-premises environment. One of the common issues in this scenario i...
Updated Nov 09, 2023
Version 8.0
Blog Post
Hi Exchange Team,
thank you so much for these insights. Finally, some official info’s on this topic.
I have so many customers using HTTP redirect for AutoDv1 to handle multiple domains without purchasing certificates for each domain.
I found (by accident 
) that your AutodiscoverV2 redirect also honors SRV records. If the on-premises Exchange has valid SRV records for those domains the redirect works and AutodiscoverV2 is successful.
For example:
- Primary Autodiscover is: autodiscover.contoso.com
- 2nd Domain has: autodiscover.nwtraders.com with SRV Record target: autodiscover.contoso.com
- I test: https://outlook.office365.com/autodiscover/autodiscover.json?Email=test@nwtraders.com&Protocol=EWS&RedirectCount=5
- Get redirected to: https://autodiscover.contoso.com/autodiscover/autodiscover.json
- Teams integration works fine without publishing Autodiscover for each domain.
Question: Is using SRV records supported for production? Why is SRV working and HTTP redirect not?
Has this something todo with: "This is why we support V2 from middle tier and have best effort support for now with V1."
regards
Peter