Skip to main content
Question

Microsoft Flow Webhook update - too long?

  • September 11, 2025
  • 3 replies
  • 140 views

Forum|alt.badge.img+4

My Microsoft Tenant has started warning me to update my Webhooks URLs, the new URLs being longer (going past 255 characters, in case that’s a common limit).

 

As a result, a couple of my workflows have stopped working (on the Microsoft side they’re not being triggered).

 

Anyone know of any solutions, I’d rather not sign up for any risky url-shortening services.

3 replies

ktrojano
Forum|alt.badge.img+20
  • Jamf Heroes
  • September 15, 2025

I’d be interested in the answer to this as well.


Forum|alt.badge.img+13
  • Valued Contributor
  • September 15, 2025

I just got finished working through some troubleshooting and found it was cutting the signature value off the end of the URL (after finding out I need to decode the URL first before putting it in Jamf). I’ve already opened a case and suggest anyone else having this issue do the same.


dennisnardi
Forum|alt.badge.img+15
  • Jamf Heroes
  • September 16, 2025

I ran into the same thing as I use webhooks with PowerAutomate. The workaround I found was to use a URL shortener. I used tinyurl. I also tried bit.ly but that didn’t work for me. 

I contacted Jamf support about this and they confirmed that the current url limit for a webhook is 255 characters. There is a feature request here around Jamf increasing the character limit: ideas.jamf.com/ideas/JPRO-I-1188