Update alerts-action-rules.md

Author: ananthradhakrishnan

articles/azure-monitor/platform/alerts-action-rules.md

@@ -12,16 +12,19 @@ ms.component: alerts
 
 # Action rules (preview)
 
-This article describes what action rules are, and how to configure and manage them.
+Action rules allow you to define actions (or suppression of actions) at any Resource Manager scope (Subscription, Resource Group, or Resource). They have a variety of filters that allow you to narrow down to the specific subset of alert instances that you want to act on. 
 
-## What are action rules?
+## Why and when should you use action rules?
 
-Action rules allow you to define actions (or suppression of actions) at any Resource Manager scope (Subscription, Resource Group, or Resource). They have a variety of filters that allow you to narrow down to the specific subset of alert instances that you want to act on. 
+### Suppression of alerts
+
+There are often many scenarios where it would be useful to suppress the notifications generated by alerts, which could range from suppression during a planned maintenance window to suppression during non-business hours. For example, the team responsible for 'ContosoVM' wants to suppress alert notifications for the upcoming weekend since 'ContosoVM' is undergoing a planned maintenance. While they can disable each and every alert rule configured on 'ContosoVM' manually (and re-enable it post the maintenance), it is not a simple experience. Action rules allow you to define alert suppression at scale with the ability to flexibly configure the period of suppression. Going back to the previous example, the team can now define one action rule on 'ContosoVM' that will suppress all alert notifications for the weekend.
+
+
+### Actions at scale
 
-With action rules you can:
+Although alert rules allow you to define the action group that triggers when the alert is generated, customers often tend to have a common action group across their scope of operations. For example, a team responsible for the resource group 'ContosoRG' will probably define the same action group for all alert rules defined within 'ContosoRG'. Action rules allow you to simplify this process by allowing you to define actions at scale, so that an action group can be triggered for any alert generated on the configured scope. Going back to the previous example, the team can now define one action rule on 'ContosoRG' that will trigger the same action group for all alerts generated within it.
 
-* Suppress actions and notifications if you have planned maintenance windows or for the weekend/holidays, instead of having to disable each alert rule individually.
-* Define actions and notifications at scale: Instead of having to define an action group individually for each alert rule, you can now define an action group to trigger for alerts generated at any scope. For example, I can choose to have action group 'ContosoActionGroup' trigger for every alert generated within my subscription.
 
 ## Configuring an action rule