Update Start-AzPolicyRemediation.md

[Iam-Manishkumar]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Iam-Manishkumar]

@wyunchi-ms @dolauli @isra-fel @VeryEarly @YanaXu @vidai-msft @NoriZC @notyashhh @Pan-Qi

Can this be reviewed please?

[VeryEarly]

Hi @Iam-Manishkumar ,
Can you please provide context or evidence to proof this change is valid? We do not own the service and cannot tell the policy.

[Iam-Manishkumar]

Hi @VeryEarly

To provide context: Azure Policy remediation is supported for both deployIfNotExists and modify effects. This is documented right here. https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources?tabs=azure-portal and https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources?tabs=azure-powershell#create-a-remediation-task

I also validated this in my own subscription by running Start-AzPolicyRemediation against a policy assignment with the modify effect, and the remediation completed successfully on non-compliant resources.

This PR updates the documentation stating that both deployIfNotExists and modify effects can be remediated using the pwsh Start-AzPolicyRemediation.

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).