u/Unable_Drawer_9928

I'm trying the registration campaign with some test users, but I'm getting no prompts to install MS authenticator. The target is, as said MS authenticator, which is set as push and available for all users. The test users are the only ones targeted by the campaign, and those users only have SMS/phone as enrolled MFA method, No MS authenticator set or installed. The Campaign policy is enabled, targeted to Authenticator, 0 days allowed to snooze and applied to the right group. One of these user had no MFA method set initially, then on the first logon he was able to setup the SMS method. The campaign has been activated at least 4 hours ago, and still no sign of the MS authenticator push during the MFA process. Everything seems in place, and I think 4 hours should be enough for the campaign to be active. Any suggestion on what to look for?

This was indeed a nice comeback from summer holidays... Anyway, we found out about this change, we already have MS authenticator, FIDO2 keys and passkeys enabled and working in our environment but not for all users. Many blue collars are still relying on SMS for authentication, so we have to plan a campaign for that, in addition to all the necessary communications.

Now what is not that clear to me, is if MS Authenticator is still considered as enough to avoid the passkey nudge. The documentation says that if a user only (only being the keyword here) has SMS/call as MFA method, then he will be targeted. I guess this won't happen for those having MS authenticator enabled but without passkeys?

I have one doubt:
In autopatch group you set the target version for that group, the deferral and the deadline. Clear enough.
When creating an autopatch multiphase release, then I need to select again a target version.

so what's the difference between the two versions? the one in the AP group is the anchor (minimum version) and all that is deployed with the multiphase can be equal or newer to that release?

let's say I set 24h2 as the target version in the AP group policy, then deploy a feature release update targeting 25h2. Is this update going to happen, or do i need to move also the AP group policy version to 25h2?