microsoftgraph
Missing New-MgBetaIdentityConditionalAccessPolicy in v2.30
Describe the bug
it seems as MS forgot to include the command New-MgBetaIdentityConditionalAccessPolicy in v2.30 in the push. it is NOT mentioned in Microsoft.Graph.Beta.Identity.SignIns.psd1
'New-MgBetaIdentityConditionalAccessAuthenticationContextClassReference',
'New-MgBetaIdentityConditionalAccessAuthenticationStrengthAuthenticationMethodMode',
'New-MgBetaIdentityConditionalAccessAuthenticationStrengthPolicy',
'New-MgBetaIdentityConditionalAccessAuthenticationStrengthPolicyCombinationConfiguration',
'Remove-MgBetaIdentityConditionalAccessAuthenticationContextClassReference',
'Remove-MgBetaIdentityConditionalAccessAuthenticationStrength',
'Remove-MgBetaIdentityConditionalAccessAuthenticationStrengthAuthenticationMethodMode',
'Remove-MgBetaIdentityConditionalAccessAuthenticationStrengthPolicy',
'Remove-MgBetaIdentityConditionalAccessAuthenticationStrengthPolicyCombinationConfiguration',
Expected behavior
it is missing in the PS module
How to reproduce
New-MgBetaIdentityConditionalAccessPolicy : The term 'New-MgBetaIdentityConditionalAccessPolicy' is not recognized as the name of a cmdlet, function, script file, or operable pro gram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:38 char:1
- New-MgBetaIdentityConditionalAccessPolicy -BodyParameter $params
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.beta.identity.signins/?view=graph-powershell-beta here are all the expected cmdlets, but many are missing
Also the command Update-MgBetaIdentityConditionalAccessPolicy isn't present.
Seems to be the case because the corresponding OpenApi docs (both v1.0 and beta) do not contain the /conditionalAccess/policies url route. The last refresh of those docs was two months ago.
As @FabienTschanz notes, the missing paths in the openApi documents show this is an issue related to the metadata being used to generate the cmdlets.
In general this is an area where we are working on some wider reaching improvements that are intended to stop this kind of issue from occurring again in the v1.0 cmdlets. The Beta set of cmdlets while they will be helped with this are much harder to validate as removals are expected as a normal part of the Beta process
