That issue is being discussed with the Graph SDK development team at https://github.com/microsoftgraph/microsoft-graph-docs/issues/17374

I have pinged some folks that I know to see what the current state of play might be.

Thank you Tony for the article you shared, it is very useful when it comes to reporting of MFA status of available users accounts.
What we need to accomplish same behavior when you set MFA auth state to Enforced using MSOL module, but this time using graph API.
Setting MFA status to “Enforced” for particular user forces that user to register at least one MFA Authentication method and use it as default each time he signs in, if not then the user is not allowed to sign in.

In the Graph world, these are called authentication methods and you can script them with cmdlets in the Microsoft Graph PowerShell SDK. Here’s an example of reporting authentication methods for Azure AD accounts: https://office365itpros.com/2022/10/07/authentication-methods-scripts/

Example bellow:

$user = “testMFADisabled@sometenant.onmicrosoft.com
$auth = New-Object -TypeName Microsoft.Online.Administration.StrongAuthenticationRequirement
$auth.RelyingParty = “*”
$auth.State = “Enforced”
$authst = @($auth)
Set-MsolUser -UserPrincipalName $user -StrongAuthenticationRequirements $authst

License assignment cmdlets will stop working on the dates as stated. The modules are due for deprecation in early 2023. I imagine Microsoft will align this with the March 31, 2023 date for license assignment.