Home

Traffic Manager- - ADFS

%3CLINGO-SUB%20id%3D%22lingo-sub-131557%22%20slang%3D%22en-US%22%3ETraffic%20Manager-%20-%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131557%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20two%20ADFS%20servers%20in%20different%20data%20centers.%20I've%20tested%20I%20can%20connect%20to%20them%20both%20externally%20by%20changing%20my%20local%20host%20file%2C%20no%20problem.%20I'm%20trying%20to%20set%20up%20Azure%20Traffic%20Manager%20for%20failover%20from%20the%20primary%20site%20to%20the%20secondary.%20Under%20configuration%20--%26gt%3B%20for%20the%20path%20--%26gt%3B%20is%20it%20fqdn%2Fadfs%2Fls%2Fidpinitiatedsignon.aspx%20%3F%20Or%20adfs%2Fprobe%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20not%20finding%20much%20information%20on%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInternally%20I%20can%20browse%20fqdn%2Fadfs%2Fls%2Fidpinitiatedsignon.aspx%20but%20when%20I%20try%20adfs%2Fprobe%2C%20I%20receive%20a%20blank%20page.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-131557%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ETraffic%20Manager%20-%20ADFS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386538%22%20slang%3D%22en-US%22%3ERe%3A%20Traffic%20Manager-%20-%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386538%22%20slang%3D%22en-US%22%3EYou%20should%20use%20adfs%2Fprobe.%20It%20listens%20on%20TCP%2080%20so%20this%20must%20be%20open.%3CBR%20%2F%3EBe%20aware%20if%20you%20want%20full%20redundancy%20(in%20case%20of%20both%20WAP%20or%20ADFS%20backend%20failure)%20you%20need%20to%20use%20a%20workaround%20in%20your%20Azure%20Traffic%20Manager%20(or%20AWS%20Route%2053)%20and%20your%20WAP%20configuration.%20You%20find%20the%20workaround%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Fskrubbeltrang.com%2Ffault-tolerant-adfs-setup%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fskrubbeltrang.com%2Ffault-tolerant-adfs-setup%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131690%22%20slang%3D%22en-US%22%3ERe%3A%20Traffic%20Manager-%20-%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131690%22%20slang%3D%22en-US%22%3E%3CP%3Etry%20following%20this%20guide%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-adfs-in-azure-with-azure-traffic-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-adfs-in-azure-with-azure-traffic-manager%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Scott Saldana (AID)
Visitor

We have two ADFS servers in different data centers. I've tested I can connect to them both externally by changing my local host file, no problem. I'm trying to set up Azure Traffic Manager for failover from the primary site to the secondary. Under configuration --> for the path --> is it fqdn/adfs/ls/idpinitiatedsignon.aspx ? Or adfs/probe?

 

I'm not finding much information on it.

 

Internally I can browse fqdn/adfs/ls/idpinitiatedsignon.aspx but when I try adfs/probe, I receive a blank page.

 

 

2 Replies
Highlighted
You should use adfs/probe. It listens on TCP 80 so this must be open.
Be aware if you want full redundancy (in case of both WAP or ADFS backend failure) you need to use a workaround in your Azure Traffic Manager (or AWS Route 53) and your WAP configuration. You find the workaround here: http://skrubbeltrang.com/fault-tolerant-adfs-setup/
Related Conversations