F5 APM SAML for Office 365 not working for Office Apps

Hello

 

Need some help!

 

I have managed to follow the implementation of using the F5 as SAML Idp for O365 instead of ADFS. It works perfectly for logging in online but falls over when we try and launch our Office Apps. When launching Office 2016 it asks to login to your O365 account which then sends a SAML request to APM it then seems to prompt a Windows Security login from the Idp address like a 401 challenge. If you then put your details in again it goes through and looks as though you have logged in but doesn't seem like the session is valid as it complains about not having a shared activation license.

 

Previously with ADFS Office wouldn't even prompt for a login it would presumably use Kerberos\NTLM, we'd like the same with this.

 

Any help appreciated

 

Regards

 

Stuart