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.

 

Kevin_Davies_40's avatar
Kevin_Davies_40
Icon for Nacreous rankNacreous
Oct 03, 2017

I am unable to do this as we had to revert to ADFS. Another script we use to map drives to sharepoint is heavily dependant on ADFS.. it actually scrapes information from ADFS webpages! So I am adapting that at the moment, only 3000 lines of powershell 8-|

But I recall the metadata exchange URL didn't change for us as well. The federation command does not seem to affect this URL at all. I believe you have to manually set this yourself using ...

Set-MsolDomainFederationsettings -DomainName  -MetadataExchangeUri