Forum Discussion
Kevin_Davies_40
Sep 28, 2017Nacreous
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...
- 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
Nacreous
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
Oct 03, 2017Nacreous
Please note i have updated the comment above, the MetadataExhangeUri has nothing to do with SAML exported meta data. It is not needed in a SAML environment so you can delete it. Try setting it to "" to clear it.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects