Forum Discussion
Hybrid Autodiscover Fails,RedirectAddr (same value as RemoteRoutingAddress) Must Be Same as O365 UPN
Thank you for taking the time to read this. I've been banging my head on why this must be or I've got something wrong with my hybrid configuration. I have a Full Hybrid environment setup between on-prem Ex2013 and O365 and it works great except the autodiscover part.
mailto:test@domain.com is the default SMTP address of this local domain user whose RemoteRoutingAddress is user@DOMAIN.mail.onmicrosoft.com. Autodiscover is pointed to on-prem Ex2013 because that's what you're supposed to do until all mailboxes are off of the on-prem Ex2013. Outlook finds the autodiscover.xml correctly but the RedirectAddr value that Ex2013 returns is the RemoteRoutingAddress value instead of the Default SMTP Address value for this user so unless the Office 365 UPN for this mailbox matches the RemoteRoutingAddress, Outlook fails to complete setup. How can I make Ex2013 return the Default SMTP address as the RedirectAddr value in the autodiscover response instead of the RemoteRoutingAddress of a user?
3 Replies
- I never confirmed this to be the issue, but I believe it was the users' local Active Directory UPN suffix (win.DOMAIN.com) was not a part of the Office 365 tenant's domain configuration. I suggest updating their local Active Directory UPN to match their default SMTP address (Email address removed) and running an AD Sync. The reason I never confirmed this is because I changed the autodiscover record to point to Office 365 so I avoided the issue but in a subsequent migration for another client, I changed the users' local Active Directory UPN to match their default SMTP address and it worked flawlessly. I hope this information helps someone.
- The record shall be the remote routing address not the default smtp cause I think you mean primary smtp is used only for sending emails so I think this is not the cause of your issue
- I never confirmed this to be the issue, but I believe it was the users' local Active Directory UPN suffix (win.DOMAIN.com) was not a part of the Office 365 tenant's domain configuration. I suggest updating their local Active Directory UPN to match their default SMTP address (Email address removed) and running an AD Sync. The reason I never confirmed this is because I changed the autodiscover record to point to Office 365 so I avoided the issue but in a subsequent migration for another client, I changed the users' local Active Directory UPN to match their default SMTP address and it worked flawlessly. I hope this information helps someone.
