Open mrmueller opened 1 year ago
Thanks for bringing this to our attention.
The API error suggests that the endpoint is not valid hence the No HTTP resource was found that matches the request URI
. I'll transfer the issue to the metadata repo for a fix to be made in the service metadata, which describes the path as valid - POST https://graph.microsoft.com/beta/users/upn/authentication/methods/id/microsoft.graph.enableSmsSignIn
.
Enable-MgUserAuthenticationPhoneMethodSmsSignIn
is still available for use in the latest version of the SDK (v2.8.0) - https://learn.microsoft.com/graph/api/phoneauthenticationmethod-enablesmssignin?view=graph-rest-1.0&tabs=powershell#request.
<Action Name="disableSmsSignIn" IsBound="true">
<Parameter Name="bindingParameter" Type="graph.phoneAuthenticationMethod" />
</Action>
<Action Name="enableSmsSignIn" IsBound="true">
<Parameter Name="bindingParameter" Type="graph.phoneAuthenticationMethod" />
</Action>
<Action Name="disableSmsSignIn" IsBound="true">
<Parameter Name="bindingParameter" Type="graph.authenticationMethod" />
</Action>
<Action Name="enableSmsSignIn" IsBound="true">
<Parameter Name="bindingParameter" Type="graph.authenticationMethod" />
</Action>
Describe the bug The command Enable-MgBetaUserAuthenticationMethodSmsSignIn fails with version 2.7 of the module. Prior to 2.7, the command was called Enable-MgUserAuthenticationPhoneMethodSmsSignIn and worked as expected
To Reproduce Steps to reproduce the behavior:
Enable-MgBetaUserAuthenticationMethodSmsSignIn -AuthenticationMethodId $id -UserId $upn
Expected behavior Method gets enabled for SMSSignin
Debug Output
Module Version
Environment Data
Screenshots
Additional context