Posted on 03-07-2023 01:35 AM
Hi, we have recently set up a configuration profile for the Azure SSO Extension, and installed Microsoft Authenticator on all devices. - But I cannot verify if it is working or not.
When I open Authenticator after enrollment, nothing seems different; I still have to sign in, as if I used it on my private device.
What to expect, how is the sign-in procedure? - Or should I be able to see something in Authenticator's settings?
I miss a lot of documentation on this.
Thanks in advance.
Posted on 03-07-2023 07:44 AM
Hey @dannilundgren ...when we were moving to Jamf Connect with Azure, I watched this video and it helped immensely....
Also, here is a link to the Jamf documentation on setting up Jamf Connect with Azure.
Integrating_with_Microsoft_Azure_AD.html
Hope it helps.
Posted on 03-07-2023 02:13 PM
Regarding this comment: "When I open Authenticator after enrollment, nothing seems different; I still have to sign in, as if I used it on my private device."
There are specific Azure settings as well as policies that do need to be set up to send an MFA prompt or for you or your end users to get a visual on how all is working or not working.
If you have not configured both sides of the process then yes the link and info @steve_summers posted will be helpful.
Posted on 03-07-2023 11:39 PM
Thank you for your responce. - I have forgotten to point out that this is regarding Jamf School and Azure SSO on iPads. We do not have Jamf Connect. We have only configure the Single Sign-on payload in a profile in Jamf School.
Posted on 03-08-2023 07:37 AM
I am 100% on the Jamf School and SSO integrations but I would think it is still true you need to have the enterprise app and app registration done so the handshake (for lack of a better word) takes place and end-used can authenticate properly and security. This is the Nation I am certain others will chime in when they have a second. Hang in there!