OWA Doesn't Redirect in Hybrid Exchange

%3CLINGO-SUB%20id%3D%22lingo-sub-1868446%22%20slang%3D%22en-US%22%3EOWA%20Doesn't%20Redirect%20in%20Hybrid%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1868446%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20working%20on%20a%20new%20Hybrid%20Exchange%20Deployment%20and%20cannot%20get%20the%20On%20Premise%20URL%20for%20OWA%20to%20display%20the%20redirect%20link%20for%20my%20ExchangeOnline%20mailbox.%26nbsp%3B%20Note%20that%20I%20am%20still%20testing%20and%20am%20using%20the%20Teams%20Exploratory%20licensing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20my%20O365%20test%20mailbox%20user%20uses%20the%20link%20to%20our%20On%20Premise%20OWA%2C%20the%20page%20displays%20%22Something%20went%20wrong%2C%20we%20could%20not%20find%20a%20mailbox%20for%20this%20recipient.%20Either%20they%20don't%20have%20a%20mailbox%2C%20or%20don't%20have%20a%20license%20assigned.%22%26nbsp%3B%20The%20error%20references%20our%20on%20premise%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20test%20mailbox%20is%20accessable%20from%20the%20URL%20configured%20in%20the%20organization%20relationship%20as%20the%20TargetOWAURL.%26nbsp%3B%20Mail%20is%20correctly%20flowing%20to%20and%20from%20the%20mailbox%2C%20and%20free%2Fbusy%20information%20appears%20correct%20to%20on%20premise%20users.%26nbsp%3B%20I%20ran%20the%20HCW%20without%20error.%26nbsp%3B%20I%20don't%20believe%20that%20we%20have%20a%20CNAME%20record%20configured%20for%20the%20redirect%2C%20but%20I%20would%20have%20expected%20to%20receive%20a%20redirect%20page%2C%20rather%20than%20an%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20I%20check%20to%20find%20out%20why%20this%20doesn't%20work%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20assistance!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELisa%20J%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1868446%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1869526%22%20slang%3D%22en-US%22%3ERe%3A%20OWA%20Doesn't%20Redirect%20in%20Hybrid%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1869526%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F838393%22%20target%3D%22_blank%22%3E%40LJJohns925%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%2C%20when%20in%20hybrid%2C%20this%20is%20the%20expected%20behaviour.%26nbsp%3B%20You%20have%20some%20mailboxes%20still%20on%20premises%2C%20and%20some%20in%20the%20cloud.%26nbsp%3B%20Therefore%2C%20cloud%20mailboxes%20will%20access%20webmail%20via%20%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%3C%2FA%3E%26nbsp%3Band%20on-premises%20will%20continue%20with%20the%20URL%20which%20will%20be%20set%20from%20your%20OWA%20virtual%20directory%20in%20Exchange%20and%20should%20be%20on%20your%20public%20SSL%20cert.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20won't%20be%20able%20to%20get%20that%20URL%20to%20point%20to%20different%20locations%20for%20on-prem%20and%20cloud%20mailboxes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1874289%22%20slang%3D%22en-US%22%3ERe%3A%20OWA%20Doesn't%20Redirect%20in%20Hybrid%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1874289%22%20slang%3D%22en-US%22%3E%3CP%3EI%20took%20this%20one%20step%20further%20and%20setup%20a%20CNAME%20record%20per%20the%20instructions%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhybrid-deployment%2Fsimplify-owa-url%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhybrid-deployment%2Fsimplify-owa-url%3C%2FA%3E%26nbsp%3Band%20that%20was%20the%20step%20that%20I%20was%20missing.%26nbsp%3B%20In%20the%20end%2C%20I%20was%20just%20confused%20by%20the%20message%20and%20stopped%20the%20setup%20before%20it%20was%20finished.%26nbsp%3B%20Now%2C%20the%20user%20gets%20a%20link%20to%20their%20O365%20login.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELJ%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1878016%22%20slang%3D%22en-US%22%3ERe%3A%20OWA%20Doesn't%20Redirect%20in%20Hybrid%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1878016%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F838393%22%20target%3D%22_blank%22%3E%40LJJohns925%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWell%20I%20have%20learned%20something%20new%20there%20actually.%26nbsp%3B%20Never%20realized%20that%20you%20could%20do%20this.%26nbsp%3B%20Thank%20you%20for%20sharing%20your%20resolution!%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1882628%22%20slang%3D%22en-US%22%3ERe%3A%20OWA%20Doesn't%20Redirect%20in%20Hybrid%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1882628%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20also%20found%20that%20browser%20caching%20can%20interfere%20here.%20I%20needed%20to%20clear%20the%20browser%20cache%20for%20users%20whose%20mailboxes%20have%20moved.%20After%20that%20they%20got%20the%20correct%20redirect%20webpage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3Agrinning_face%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I am working on a new Hybrid Exchange Deployment and cannot get the On Premise URL for OWA to display the redirect link for my ExchangeOnline mailbox.  Note that I am still testing and am using the Teams Exploratory licensing.

 

When my O365 test mailbox user uses the link to our On Premise OWA, the page displays "Something went wrong, we could not find a mailbox for this recipient. Either they don't have a mailbox, or don't have a license assigned."  The error references our on premise server.

 

The test mailbox is accessable from the URL configured in the organization relationship as the TargetOWAURL.  Mail is correctly flowing to and from the mailbox, and free/busy information appears correct to on premise users.  I ran the HCW without error.  I don't believe that we have a CNAME record configured for the redirect, but I would have expected to receive a redirect page, rather than an error.

 

What can I check to find out why this doesn't work?

 

Thanks in advance for any assistance!

 

Lisa J

5 Replies

@LJJohns925 

 

Hi, when in hybrid, this is the expected behaviour.  You have some mailboxes still on premises, and some in the cloud.  Therefore, cloud mailboxes will access webmail via https://outlook.office365.com and on-premises will continue with the URL which will be set from your OWA virtual directory in Exchange and should be on your public SSL cert.

 

You won't be able to get that URL to point to different locations for on-prem and cloud mailboxes.

I took this one step further and setup a CNAME record per the instructions at https://docs.microsoft.com/en-us/exchange/hybrid-deployment/simplify-owa-url and that was the step that I was missing.  In the end, I was just confused by the message and stopped the setup before it was finished.  Now, the user gets a link to their O365 login.

 

LJ

@LJJohns925 

 

Well I have learned something new there actually.  Never realized that you could do this.  Thank you for sharing your resolution! :smile:

I have also found that browser caching can interfere here. I needed to clear the browser cache for users whose mailboxes have moved. After that they got the correct redirect webpage.

 

:grinning_face:

Re: the cname solution - make sure to heed the note about how you have to only go to the cname FQDN using HTTP. If you try HTTPS, you get the scary warning about certificate name mismatch, which surely will ruin the user experience. Best to create a link or bookmark for users to click if using the cname solution, so they don't type or end up at HTTPS by accident.