Remove -AuthorizationPolicyId which doesn't exist (anymore?)

[cnotin]

This parameter doesn't exist. At least in the latest v1.0 version of the Graph PowerShell module. Perhaps it used to exist?
Proof in doc: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.identity.signins/update-mgpolicyauthorizationpolicy?view=graph-powershell-1.0
And in this error:

PS> Update-MgPolicyAuthorizationPolicy -AuthorizationPolicyId $authorization_policy -BodyParameter $body
Update-MgPolicyAuthorizationPolicy : A parameter cannot be found that matches parameter name 'AuthorizationPolicyId'.

PS> Get-InstalledModule Microsoft.Graph

Version              Name                                Repository           Description
-------              ----                                ----------           -----------
2.19.0               Microsoft.Graph                     PSGallery            Microsoft Graph PowerShell module

Edit: Actually! It exists, but only for the beta version!
https://learn.microsoft.com/en-us/powershell/module/Microsoft.Graph.Beta.Identity.SignIns/Update-MgBetaPolicyAuthorizationPolicy?view=graph-powershell-beta

There are significant differences between the v1.0 and beta versions of this API (returning an object vs. array, authorization policy under defaultUserRolePermissions.permissionGrantPoliciesAssigned vs. permissionGrantPolicyIdsAssignedToDefaultUserRole)

Currently all the content in the page refers to the beta version of the API and the commands. My advice is to either adapt it to v1.0, or keep beta but make it very explicit and use instead Update-MgBetaPolicyAuthorizationPolicy

[prmerger-automator]

@cnotin : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b98b548:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/identity/enterprise-apps/configure-user-consent.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@omondiatieno

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team