Webhook URL Error for Send Microsoft Teams Message action webhookb2
Asked by JG Meillaud _:

Hello,

I cannot enable the Send MS Teams Message action because Automation tells me the webhook URL is not OK.

The webhook URL looks like this <https://COMPANY.webhook.office.com/webhookb2/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/IncomingWebhook/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX>

Automation gives me a warning sign /!\\ and "Please enter a valid webhook URL like <https://outlook.office.com/webhook/XXXXYYYY>..."

Thanks a lot!


Answers:
author: Gareth Cantrell
body: After upgrading to [Automation for Jira 7.2.6](https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?hosting=datacenter&tab=versions), you need to following the documentation at <https://confluence.atlassian.com/automation/setting-configuration-properties-1026539532.html> to set the **ms.teams.notification.action.url.prefix** property to the correct prefix.

If you don't set the prefix, it will default to *<https://outlook.office.com/webhook/>*

If you need both the old and new prefix, set the prefix to **https://** so that it matches any secure URL.

comments: author: Stephan Stahl
body: Worked perfectly for me after updating Automation for Jira to 7.2.6! Thanks for pointing out the instructions Gareth, much appreciated!


author: Leonie C_ Breitmoser
body: Worked for us as well. Thanks for pointing us in the right direction Gareth.


author: Aditya Verma
body: I am facing the same issue on Jira Data Center + A4J v7.2.8. Can you please suggest a solution for it ?

[@Gareth Cantrell](/t5/user/viewprofilepage/user-id/3178836) [@Sherry Goyal](/t5/user/viewprofilepage/user-id/3873899)

comments: author: Gareth Cantrell
body: [@Aditya Verma](/t5/user/viewprofilepage/user-id/1264946) the instructions I referred to above are for Jira Data Center/Server. If you're running Windows servers, use the script posted by [@Erik Ekengren](/t5/user/viewprofilepage/user-id/379340) above.


author: Aditya Verma
body: Thanks [@Gareth Cantrell](/t5/user/viewprofilepage/user-id/3178836) , I was able to follow it.


author: Erik Ekengren
body: Hi all!

I tried the work-around in this article [Setting configuration properties \| Automation for Jira Data Center and Server 7.2 \| Atlassian Documentation](https://confluence.atlassian.com/automation/setting-configuration-properties-1026539532.html) but had no luck. It turned out that since I run Jira on ++WINDOWS-machine++ then I was not able to use the CURL-command. After some talks with the Atlassian support they helped me with this Power-shell query and then I got it working:

```
$user = 'YOUR_USER_ADMIN'
$pass = 'PASSWORD'
$pair = "$($user):$($pass)"
$encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($pair))
$basicAuthValue = "Basic $encodedCreds"
$Headers = @{
Authorization = $basicAuthValue
}
$Uri = 'https://<jira-base-url>/rest/cb-automation/1/configuration/property/bulk'
$Form = @{
"ms.teams.notification.action.url.prefix"="https://"
}
Invoke-WebRequest -Uri $Uri -Method Put -Body ($Form|ConvertTo-Json) -ContentType "application/json" -Headers $Headers
```

Change User and Password in the script and also to your Base-url and this will work. This will allow all webhooks that starts with *https://*.

comments: author: Fox Chen
body: Hi Erik,

May I ask how to run the script? Thank you.

BR,  
Fox


author: Erik Ekengren
body: Hi Fox!

Log in to your Windows Server and open Powershell. Then copy this (replace user and password and also *\<jira-base-url\> to the base URL you have*) to Powershell and run it:

```
$user = 'YOUR_USER_ADMIN'
$pass = 'PASSWORD'
$pair = "$($user):$($pass)"
$encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($pair))
$basicAuthValue = "Basic $encodedCreds"
$Headers = @{
Authorization = $basicAuthValue
}
$Uri = 'https://<jira-base-url>/rest/cb-automation/1/configuration/property/bulk'
$Form = @{
"ms.teams.notification.action.url.prefix"="https://"
}
Invoke-WebRequest -Uri $Uri -Method Put -Body ($Form|ConvertTo-Json) -ContentType "application/json" -Headers $Headers
```

BR/

Erik


author: Fox Chen
body: it works, thank you so much.


author: Leonie C_ Breitmoser
body: Hi there,

we run into the same issue. Even with the bugfix update it won't work with the web-hook in our Jira. (Server 8.13.1 \& Automation 7.2.6).

I tried to find out if I need to change something in the setup, but didn't succeed. I still get the "lease enter a valid webhook URL like <https://outlook.office.com/webhook/XXXXYYYY>..." Error Message.

Did anyone find a solution for this?

Thanks,

Leonie

comments: author: robert Mugabuhamye
body: Hello [@Leonie C_ Breitmoser](/t5/user/viewprofilepage/user-id/4254845)

II'm still experiencing the issue on the 7.2.6 version too ?.

No solutions so far


author: Gareth Cantrell
body: [@robert Mugabuhamye](/t5/user/viewprofilepage/user-id/385916) 7.2.6 does indeed contain a solution for this issue, however it requires you make some configuration changes post installation.

It is not immediately obvious, until you read the release notes in conjunction with the documentation on setting configuration properties (see my [answer](#M1047) above).


author: robert Mugabuhamye
body: [@Gareth Cantrell](/t5/user/viewprofilepage/user-id/3178836) forgot to thank you. It worked for us ??


author: robert Mugabuhamye
body: hello [@Sherry Goyal](/t5/user/viewprofilepage/user-id/3873899)

We are seeing this issue on Jira datacenter + automation 7.1.17

Do you know by any chance in which version of Automation this has been corrected?

thanks

comments: author: Sherry Goyal
body: Hello [@robert Mugabuhamye](/t5/user/viewprofilepage/user-id/385916)

We fixed it in cloud. Sorry I am not aware of the server.


author: Gareth Cantrell
body: [@robert Mugabuhamye](/t5/user/viewprofilepage/user-id/385916) I see there was a new version for server that was released on 28/Jan that appears to address the MS Teams issues ([version 7.2.6](https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?hosting=datacenter&tab=versions))


author: robert Mugabuhamye
body: Thank you [@Gareth Cantrell](/t5/user/viewprofilepage/user-id/3178836) , I'm going to try that version


author: Sherry Goyal
body: Hello All,

Since Microsoft url has changed over time, we have removed the validation from Automation side in **cloud**. The new URL should be working now. Please let me know in case of issues. Apologies for the inconvenience.

Cheers  
Sherry


author: JG Meillaud _
body: Hi both,

Thanks for replying.

So this is a known bug:  
[\[AUT-2103\] Microsoft Teams webhooks are limited to specific URL](https://codebarrel.atlassian.net/browse/AUT-2103)

What's really frustrating is that it looks like this "URL verification" thing is a feature...  
If so, please Atlassian and partners, keep it simple, please ?.

Cheers,  
JG


author: Gareth Cantrell
body: Microsoft is apparently changing the format of all newly created Webhook URLs after 11/Jan, and the older "outlook.office.com/webhook" will be deprecated in 3 months

If you have access to the Microsoft365 Message Center, you can view the announcement here: [https://admin.microsoft.com/AdminPortal/home?ref=MessageCenter\&id=MC234048](https://admin.microsoft.com/AdminPortal/home?ref=MessageCenter&id=MC234048)

I'd suggest raising a support request with Atlassian to address this.


author: ?????????? ??????? ???????
body: We have same problem!


Tags: cloud