Creating or editing a webhook fails when using Microsoft’s Power Automate as a receiver for ArcGIS Enterprise organization webhooks

Description

Creating or editing a webhook fails when using Microsoft’s Power Automate as a receiver for ArcGIS Enterprise organization webhooks. ArcGIS Enterprise versions 10.7 through 12.0 are impacted.

An error message similar to the following example may be returned when attempting to create a webhook.

Unable to create webhook for the account '0123456789ABCDEF' due to 'Unable to add webhook registry named ‘new webhook’'
Error: 400
Database error occurred while processing webhook with name or id ‘new webhook’ due to 'Unable to add webhook registry named ‘new webhook'.'

An example JSON message of the error when making the API call is shown in the following image:

Portal administrator debug logs show a database exception from the attempt to insert a row.

Cause

In August 2025, Microsoft announced changes to the webhook URL provided through Power Automate. Any new flows created that use the “When an HTTP request is received” trigger provide URLs in a new format. 

On November 30, 2025, all 'old-format' URLs cease to function, the new format URL must be obtained from the Power Automate flow, and existing webhooks must be updated.

The new format URL has increased in length by over 80 characters — more when using Shared Access Signature (SAS) authentication. Organization webhooks have a maximum of length of 250 characters for the webhook payload URL. All new URLs from the “When an HTTP request is receiver” trigger will exceed the maximum length, and attempting to create or edit a webhook will result in an error as the URL is too large for the field.

Workaround

Webhook workflows may need to be migrated to another platform. Esri is committed to increasing the maximum URL length in ArcGIS Enterprise 12.1