I am having some problems with free/busy information and Lync <-> Exchange integration that I think may boil down to an autodiscover problem.
The environment with issues is a hybrid Exchange 2010 On-Premise and Exchange Online setup in which we use a single domain (let's say "contoso.com"). I have migrated one user, "testuser@contoso.com," to the online environment.
When I use Microsoft's Remote Connectivity Analyzer to test autodiscover, I get the following results:
1. When using any user which is located on the On-Premise server, such as internaluser@contoso.com, the typical full autodiscover information is returned.
2. When using testuser@contoso.com, I receive a redirect from the autodiscover service, with the RedirectAddr field set to "testuser@contoso.com" which is the same address that information was originally requested for. This obviously creates a loop until the client decides to quit trying.
I have very limited knowledge of how this hybrid setup works on the back-end, but I would think that the autodiscover request for testuser@contoso.com should receive a redirect response with the address of testuser@contoso.onmicrosoft.com. I would think that an autodiscover against this domain would then return the correct autodiscover information for the Microsoft Online portion of our hybrid setup.
We also use ADFS for SSO between the environments. I have no idea if this has any impact on any of these issues.
Does anybody have any suggestions on how to get this issue resolved, or even just further insight into how it should actually be working?