Create and manage action groups in the Azure portal


An action group is a collection of notification preferences defined by the owner of an Azure subscription. Azure Monitor and Service Health alerts use action groups to notify users that an alert has been triggered. Various alerts may use the same action group or different action groups depending on the user's requirements. You may configure up to 2,000 action groups in a subscription.

You configure an action to notify a person by email or SMS, they receive a confirmation indicating they have been added to the action group.

This article shows you how to create and manage action groups in the Azure portal.

Each action is made up of the following properties:

  • Name: A unique identifier within the action group.
  • Action type: The action performed. Examples include sending a voice call, SMS, email; or triggering various types of automated actions. See types later in this article.
  • Details: The corresponding details that vary by action type.

For information on how to use Azure Resource Manager templates to configure action groups, see Action group Resource Manager templates.

Create an action group by using the Azure portal

  1. In the portal, select Monitor. The Monitor pane consolidates all your monitoring settings and data in one view.

    The "Monitor" service

  2. Select Alerts then select Manage actions.

    Manage Actions button

  3. Select Add action group, and fill in the fields.

    The "Add action group" command

  4. Enter a name in the Action group name box, and enter a name in the Short name box. The short name is used in place of a full action group name when notifications are sent using this group.

    The Add action group" dialog box

  5. The Subscription box autofills with your current subscription. This subscription is the one in which the action group is saved.

  6. Select the Resource group in which the action group is saved.

  7. Define a list of actions. Provide the following for each action:

    a. Name: Enter a unique identifier for this action.

    b. Action Type: Select Email/SMS/Push/Voice, Logic App, Webhook, ITSM, or Automation Runbook.

    c. Details: Based on the action type, enter a phone number, email address, webhook URI, Azure app, ITSM connection, or Automation runbook. For ITSM Action, additionally specify Work Item and other fields your ITSM tool requires.

  8. Select OK to create the action group.

Manage your action groups

After you create an action group, it's visible in the Action groups section of the Monitor pane. Select the action group you want to manage to:

  • Add, edit, or remove actions.
  • Delete the action group.

Action specific information


See Subscription Service Limits for Monitoring for numeric limits on each of the items below.

Azure app Push - You may have a limited number of Azure app actions in an Action Group.

Email - Emails will be sent from the following email addresses. Ensure that your email filtering is configured appropriately


You may have a limited number of email actions in an Action Group. See the rate limiting information article

ITSM - You may have a limited number of ITSM actions in an Action Group. ITSM Action requires an ITSM Connection. Learn how to create an ITSM Connection.

Logic App - You may have a limited number of Logic App actions in an Action Group.

Function App - The function keys for Function Apps configured as actions are read through the Functions API, which currently requires v2 function apps to configure the app setting “AzureWebJobsSecretStorageType” to “files”. For more information, see Changes to Key Management in Functions V2.

Runbook - You may have a limited number of Runbook actions in an Action Group. Refer to the Azure subscription service limits for limits on Runbook payloads.

SMS - You may have a limited number of SMS actions in an Action Group. Also see the rate limiting information and SMS alert behavior for additional important information.

Voice - You may have a limited number of Voice actions in an Action Group. See the rate limiting information article.

Webhook - You may have a limited number of Webhook actions in an Action Group. Webhooks are retried using the following rules. The webhook call is retried a maximum of 2 times when the following HTTP status codes are returned: 408, 429, 503, 504 or the HTTP endpoint does not respond. The first retry happens after 10 seconds. The second retry happens after 100 seconds. After two failures, no action group will call the endpoint for 30 minutes.

Source IP address ranges


To receive updates about changes to these IP addresses, we recommend you configure a Service Health alert, which monitors for Informational notifications about the Action Groups service.

Next steps