Skip to content

Commit 3b69821

Browse files
Clarify Secure Webhook Usage
1 parent 21569f2 commit 3b69821

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -263,7 +263,11 @@ You may have a limited number of Logic Apps actions per action group.
263263

264264
### Secure webhook
265265

266-
When you use a secure webhook action, you must use Azure AD to secure the connection between your action group and your protected web API, which is your webhook endpoint. For an overview of Azure AD applications and service principals, see [Microsoft identity platform (v2.0) overview](../../active-directory/develop/v2-overview.md). Follow these steps to take advantage of the secure webhook functionality.
266+
When you use a secure webhook action, you must use Azure AD to secure the connection between your action group and your protected web API, which is your webhook endpoint.
267+
268+
The secure webhook Action authenticates to the protected API using a Service Principal instance in the AD tenant of the "AZNS AAD Webhook" AAD Application. To make the action group work, this AAD Webhook Service Principal needs to be added as member of a role on the target AAD application that grants access to the target endpoint.
269+
270+
For an overview of Azure AD applications and service principals, see [Microsoft identity platform (v2.0) overview](../../active-directory/develop/v2-overview.md). Follow these steps to take advantage of the secure webhook functionality.
267271

268272
> [!NOTE]
269273
>

0 commit comments

Comments
 (0)