Templafy SSO failure with Microsoft Enterprise SSO extension

[infrase2020]

Hi,

We have an issue with templafy where SSO fails when we have the Microsoft Enterprise SSO plug in enabled. 

I removed the profile from my machine and SSO works.

My question is does anyone know how to bypass or exclude SSO for Templafy as the documentation suggests you need the bundle ID but i do not want to exclude SSO for all office apps that may use SSO? 

Thanks in advance.

[mbrown2157]

Same issue here with a few of our users.  I have a Microsoft ticket opened, I will post if I find out anything.  I have not been able to reproduce this on my device, so troubleshooting will be difficult.  This was also posted yesterday.

https://community.jamf.com/t5/jamf-pro/ms-teams-microsoft-sso-extension-teams-sign-in-error-1000-100...

[barrycuda]

Hopefully Microsoft gets back to you.  We are in the middle of migrating to Jamf so half of our users are still on Intune, the problem is that you cannot have Intune remove the profile because the Company portal app is impacted by this so it is broke as well.  Not for sure how to remove that profile manually or disable the Microsoft Enterprise SSO plugin manually.

[mbrown2157]

Disabling Enterprise SSO is as simple as un-scoping the profile.  It takes affect almost instantly.

[barrycuda]

I can un-scope in Jamf and that is fine..  But un-scoping in Intune does not work because the profile won't remove from the client, which I suspect is because the issue impacts the Company Portal app.

[mbrown2157]

ouch good point, I am doing this from the jamf side.

[infrase2020]

I fixed the issue with the SSO extension breaking authentication to Templafy (via O365 Apps such as Word).

Basically the Microsoft article suggests this is only for iOS devices however thats not true as its not working for macOS devices. 

Add the following key and string to the plist config:

<key>AppCookieSSOAllowList</key>

    <string>com.microsoft.Word,com.microsoft.Excel,com.microsoft.Powerpoint</string>

[mbrown2157]

Looking at the other thread posted above, looks like it was in fact the company portal app.  Microsoft put a new version out last night which seems to have corrected it on my test device.

[barrycuda]

I can confirm that the updated company portal app solved our issues.