nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Service Management webhook not working with new Power Automate URLs

Nikhil Khairnar_lbb8dl

Hello Community

I am using Jira Service Management Cloud and have configured system webhooks that post events to Microsoft Power Automate.

Previously, the webhooks worked with the older Power Automate trigger URLs (e.g. <a href="https://prod-XX.westus.logic.azure.com/" rel="noopener nofollow noreferrer" target="_blank">https://prod-XX.westus.logic.azure.com/</a>...). However, Microsoft has updated their trigger endpoints to new URLs in the format:

When I update the webhook in Jira to use the new URL, the webhook does not send any payloads. I have tried both with and without the :443 suffix, but it still fails.

It seems Jira Cloud may not be able to reach the new *.environment.api.powerplatform.com domain. Could you please confirm if this domain is supported for Jira Cloud outbound webhooks? If not, can it be added to the allowlist for Jira Cloud?

I also can’t use Jira Automation as a workaround, because these are frequent ticket movement updates and my license has limited rule runs.

Thanks in advance for your help,
Nikhil

Accepted answers

Nikhil Khairnar_lbb8dl

Hi,
I found the issue here — I had neglected a few things that aren’t usually required in a normal webhook but are needed in a Jira system webhook.

The sp=%2Ftriggers%2Fmanual%2Frun part of the Power Automate URL needs to be decoded to sp=/triggers/manual/run. Also, the Power Automate domain must be added to Jira’s allowlist, otherwise it gets blocked. Posting here so it may help others facing the same problem.

Thanks ,
Nikhil

All comments

Marc -Devoteam-

Hi @Nikhil Khairnar

Provide this informaiton to Atlassian by raising a Support ticket.

https://support.atlassian.com/contact/

Here in community, most of us are Atlassian users like yourself, not (necessarily) employees of Atlassian. We don't have access to your environment.

This community is an open public forum.

Haripriya

Hello @Nikhil Khairnar!

I hope you’re having a wonderful day! I wanted to reach out regarding your admin Webhooks used to send data to Microsoft Power Automate. I understand there have been some recent changes to the Microsoft Webhook URL, and it sounds like that might be causing some hiccups in Jira.

While we don’t have any specific restrictions for apps, just to clarify, port 443 is perfectly fine for our needs, as mentioned in the documentation here.

A webhook in Jira is defined by the following information, which you need to provide when registering (i.e. creating) a new webhook:

a name for webhooks created in Jira Administration
the URL where the callback should be sent:
- Only secure HTTPS URLs are allowed. For the latest list of supported TLS protocols and ciphers, refer to: Supported security protocols for Atlassian cloud products.
- The receiving web server must have a valid SSL/TLS certificate, signed by a globally trusted certificate authority.
- You can indicate a port from the following list: 443 1880-1890 4044 6017 7990 8060 8080 8085 8089 8090 8443 8444 8900 9900 9420 9520 for webhooks created in Jira Administration (Note that port 80 is not allowed).
- Up to 5 redirects per URL are allowed.
(optional) the scope of the webhook, for example either "all issues" or a limited set of issues specified by JQL ("project = TEST and fixVersion = future")
the events to post to the URL, either "all events" or a specific set of events

You need to allow-list IP address ranges for outgoing connections to ensure webhook delivery.

Next steps:

Could you please try creating a new webhook Trigger from Jira Administration and see if that works?
Make sure that the webhook is enabled in both Jira and in Microsoft Power Automate.
Does the same webhook URL trigger the automation in microsoft if it were sent from Postman or Jira Automation?

If none of the above works, we could create a support request on your behalf to check this further! Awaiting your response!

Thanks and Regards,
Haripriya

Nikhil Khairnar_lbb8dl

Hi @Haripriya

Thanks for your quick reply! I’ve tried all possible ways to set this up — even tested the new URL via Postman, and it sends alerts successfully. However, it still fails to trigger my "When a Teams webhook request is received" trigger in Power Automate.

Interestingly if I add this new URL in a Jira Automation rule, it triggers perfectly, but it fails when used in a system webhook.
As a note, I cannot rely on Jira Automation as a workaround, since my license has limited runs and this webhook is meant for continuous ticket movement updates.

Appreciate your support in helping me resolve this further.

Best regards,
Nikhil

Haripriya

Hi Nikhil,

Thank you for the response. This requires further troubleshooting and data access approval for your site. I have created a support ticket on your behalf. You will receive a confirmation email regarding the same. We look forward to supporting you!

Thanks,
Haripriya

Nikhil Khairnar_lbb8dl

Hi @Haripriya ,

Thank you . I appreciate your prompt help and will look out for the confirmation email.

Best regards,
Nikhil

Nikhil Khairnar_lbb8dl

Hi,
I found the issue here — I had neglected a few things that aren’t usually required in a normal webhook but are needed in a Jira system webhook.

Thanks ,
Nikhil

Haripriya

That's Awesome @Nikhil Khairnar!

Thanks a ton for sharing it here...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management