Webhook Configuration
Applies to: Patch My PC Publisher
Overview
The Notification Webhook Configuration dialog is shown when creating a new webhook, editing an existing webhook, or copying a webhook.

Name
Specifies a friendly label used to identify the webhook in the Publisher.
Webhook Provider
Specifies the target messaging system used for webhook notifications. The selected provider determines the expected webhook payload format.
Microsoft Teams Workflow
This is the recommended option for Microsoft Teams. It uses the modern Microsoft Teams workflow based webhook model, which supports Adaptive Cards. See Create a Microsoft Teams Webhook URL for more information.
Microsoft Teams Legacy Webhook
This option exists only for backward compatibility with older Publisher configurations where Microsoft Teams webhooks were created using the legacy Microsoft Teams incoming webhook model.
Important
The legacy provider was used by earlier versions of the Publisher that relied on the older Teams message card format. It is retained to ensure existing customer configurations continue to function without requiring immediate changes.
Note
Customers using the legacy provider should plan to migrate to Microsoft Teams Workflow. See Update a Microsoft Teams Legacy Webhook to Use Workflows for more information.
Slack
This option sends webhook notifications to Slack using the Slack webhook payload format. see Create a Slack Webhook URL for more information.
Webhook URL
Specifies the destination webhook endpoint URL generated by the target messaging platform. This field is required and must be valid for notifications to be delivered.
Note
The webhook URL must start with http:// or https:// to be considered valid.
Notification Level
Controls which publishing events generate notifications for this webhook. This setting determines the overall verbosity of webhook messages.
All Sends notifications for all publishing events, including successes and errors.
Error Sends notifications only when a publishing error occurs.
Success Sends notifications only when publishing actions complete successfully.
Send alerts as each product is published
This option is enabled by default and is the recommended configuration.
When enabled, webhook notifications are sent after each product is processed during a publishing synchronization. Each notification represents an individual product that has been successfully processed or failed, making it easier to track progress during large publishing runs.

When this option is disabled, a single webhook notification is sent only after all products have finished processing at the end of the publishing synchronization.

The end of synchronization notification provides a consolidated summary of all processed products but does not provide visibility into progress while the synchronization is running.
Webhook Scope
The tabs shown in Product Selection reflect the same publishing areas available in the Publisher.
Each tab maps directly to a corresponding Publisher tab:
Updates
ConfigMgr Apps
Intune Apps
Intune Updates
This alignment ensures that webhook product scoping follows the same structure and product groupings used for publishing configuration.

You can expand vendors and select individual products to include in webhook notifications. Only the selected products generate notifications for the corresponding content type.
Use the filter field to quickly locate vendors or products by name.
Important
End of synchronization alerts cannot be filtered by specific product. If Send alerts as each product is published is unchecked, product selection is disabled and all products are included automatically.
MSP Configuration
If you are using an MSP or MSP Plus license with multiple tenants configured, webhook notifications support tenant level scoping.

When creating or editing a webhook, you can select which tenant or tenants the notification applies to. If no tenants are selected, the webhook applies to all tenants. If specific tenants are selected, the webhook applies only to those tenants.
Last updated
Was this helpful?