Forum Discussion

Kevin_Davies_40's avatar
Kevin_Davies_40
Icon for Nacreous rankNacreous
Sep 28, 2017

Office 365 SAML idp and Outlook 2016 solution?

Does anyone know when F5 expect the Office 365 SAML idp endpoint to support thick client Outlook 2016 authentication for federated domains?   https://f5.com/solutions/deployment-guides/microsoft-o...
application delivery
BIG-IP Access Policy Manager (APM)
saml
  • Kevin_Davies_40's avatar
    Kevin_Davies_40
    Oct 03, 2017

    This was due to a federation issue. You need to wait 24-48 hours after de-federating from ADFS before you federate to F5 idp.

     

Kevin_Davies_40's avatar
Kevin_Davies_40
Icon for Nacreous rankNacreous

This was due to a federation issue. You need to wait 24-48 hours after de-federating from ADFS before you federate to F5 idp.

 

Niels_van_Sluis's avatar
Niels_van_Sluis
Icon for MVP rankMVP
Oct 03, 2017

Hi Kevin, good to hear you found a solution. Could you help me and try something out for me. I have also deployed the F5 APM to fully replace ADFS and everything seems to be working fine. There is only one issue with shared licenses in a non persistent VDI environment and I'm not sure if the problem is within my F5 APM configuration or within Office 365/Azure. I'm trying to validate my setup using the Microsoft connectivity test, but I'm not sure if this test is reliable. Could you run a test on your setup and share your results?

What I do is:

In my setup it fails with the following messages:

An error was found in the domain registration.
Additional Details
The Metadata Exchange URL in the domain registration isn't valid. URL:
Elapsed Time: 1 ms.

We have set the metadataexchangeuri, so I wonder if I can ignore this error. I would like to know if your setup shows the similar error messages.