Skip to content

Commit fd0abe9

Browse files
committed
Learn Editor: Update action-groups.md
1 parent 7c82572 commit fd0abe9

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/azure-monitor/alerts/action-groups.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ The following table describes the role membership requirements that are needed f
147147
<sup>1</sup> The custom role must have the **Microsoft.Insights/createNotifications/*** permission.
148148

149149
> [!NOTE]
150-
> - If a user is not a member of the above Role Memberships with the correct permissions to generate this notification, the minimum permission required to test an action group is "**Microsoft.Insights/createNotifications/***"
150+
> - If a user is not a member of the above Role Memberships with the correct permissions to generate this notification, the minimum permission required to test an action group is "**Microsoft.Insights/createNotifications/***"
151151
> - You can run a limited number of tests per time period. To check which limits apply to your situation, see [Azure Monitor service limits](../service-limits.md).
152152
> - When you configure an action group in the portal, you can opt in or out of the common alert schema.
153153
> - To find common schema samples for all sample types, see [Common alert schema definitions for Test Action Group](./alerts-common-schema-test-action-definitions.md).
@@ -508,8 +508,7 @@ For information about pricing for supported countries/regions, see [Azure Monito
508508
## Webhook
509509

510510
> [!NOTE]
511-
>
512-
> If you use the webhook action, your target webhook endpoint must be able to process the various JSON payloads that different alert sources emit. You can't pass security certificates through a webhook action. To use basic authentication, you must pass your credentials through the URI. If the webhook endpoint expects a specific schema, for example, the Microsoft Teams schema, use the Logic Apps action to transform the alert schema to meet the target webhook's expectations.
511+
> If you use the webhook action, your target webhook endpoint must be able to process the various JSON payloads that different alert sources emit. The webhook endpoint must also be publicly accessible. You can't pass security certificates through a webhook action. To use basic authentication, you must pass your credentials through the URI. If the webhook endpoint expects a specific schema, for example, the Microsoft Teams schema, use the Logic Apps action to transform the alert schema to meet the target webhook's expectations.
513512
Webhook action groups generally follow these rules when called:
514513
- When a webhook is invoked, if the first call fails, it is retried at least 1 more time, and up to 5 times (5 retries) at various delay intervals (5, 20, 40 seconds).
515514
- The delay between 1st and 2nd attempt is 5 seconds

0 commit comments

Comments
 (0)