Skip to content

Commit a321afa

Browse files
authored
Update event-overview.md
Small changes
1 parent 62ec327 commit a321afa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/governance/policy/concepts/event-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,10 @@ There are two primary entities when using Event Grid:
5151

5252
A common Azure Policy event scenario is tracking when the compliance state of a resource changes
5353
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.
5555

5656
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
5858
non-compliant can be remedied. Learn more about [remediation structure](../concepts/remediation-structure.md).
5959
> Remediation requires a managed identity and policies must be in Modify or DeployIfNotExists effect. [Learn more about
6060
effect types](../how-to//remediate-resources.md).

0 commit comments

Comments
 (0)