File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
articles/governance/policy/concepts Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -51,10 +51,10 @@ There are two primary entities when using Event Grid:
51
51
52
52
A common Azure Policy event scenario is tracking when the compliance state of a resource changes
53
53
during policy evaluation. Event-based architecture is an efficient way to react to these changes
54
- instead of scanning the compliance state of resources on a fixed schedule .
54
+ and aids in the event based reaction to compliance state changes .
55
55
56
56
Another scenario is to automatically trigger remediation tasks without manually ticking off 'create
57
- remediation task' on the policy portal page. Event Grid checks for compliance state and resources that are currently
57
+ remediation task' on the policy page. Event Grid checks for compliance state and resources that are currently
58
58
non-compliant can be remedied. Learn more about [ remediation structure] ( ../concepts/remediation-structure.md ) .
59
59
> Remediation requires a managed identity and policies must be in Modify or DeployIfNotExists effect. [ Learn more about
60
60
effect types] ( ../how-to//remediate-resources.md ) .
You can’t perform that action at this time.
0 commit comments