Will this change affect powershell connection that still uses the legacy part? Thank you

Off the top of my head, it might be possible to establish some associations (with some doubts 🤔): phoneAuthMethod+mobile = OneWaySMS+TwoWayVoiceMobile. However, it's certainly not a walk in the park. That said, I see your point—if the module is going to be retired, why should I rack my brains? 😄

I understand that the deprecated modules can't show new authentication methods. However, I would have appreciated documentation from Microsoft that clearly outlines any "possible" mappings. If a mapping is not feasible (due to different modules and sources), a note indicating this would be helpful.

Perfect. I might be missing something, but I still wonder how to map only some new values to the old ones:
TwoWayVoiceMobile
TwoWaySms
TwoWayVoiceOffice
TwoWayVoiceOtherMobile
TwoWaySmsOtherMobile
OneWaySms
PhoneAppNotification
PhoneAppOTP
I don't know if this makes sense

Thank you for your response 🙏. I'm aware of the Microsoft Graph API endpoint, but I'm confused as it seems the StrongAuthenticationMethods property from the Get-msolUser cmdlet isn't currently supported in #MicrosoftGraph. I would expect to have an equivalent result:

Will they be deprecated? @merill.net