MS Teams web hook wont apply

John Wilson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 1, 2024

I am trying to set up the web hook connection for Teams in the Statuspage/AppsMicrosoft Teams area.  No problem generating the web hook for the target channel but when I add it to the input screen along with the integration name I get "Yikes! It looks like the input you provided is invalid".  Have tried a few times with various options combinations and get the same result.

Is this feature supposed to be working?  Anyone else with the same problem?

5 answers

1 vote
Jesse Klein
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 8, 2024

Hey John,

Would you try adding the webhook connection again? My colleague and I did some testing yesterday and it seems to be working properly for us. We'd love to know if you're getting similar results. If not, would you be willing to submit a ticket under support.atlassian.com so we can get more details?

Regards,
Jesse 

1 vote
Jesse Klein
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 7, 2024

Hello everyone,

This is being tracked under the following bug report:

https://jira.atlassian.com/browse/STATUS-836

Please feel free to follow it there and add yourself as an affected user.

Regards,
Jesse

Clint Payton November 7, 2024

This is not correct.  You are confusing two different issues.  I've added a comment to the bug item you mentioned.. I also replied to your email with my cell number.  Please call so we can clarify.:
Please consider reading the MS announcement closely again.  For an immediate fix to this bug, Statuspage simply needs to accept the new URL format in the input field of the MS Teams integration app dialogue (controlled by Atlassian statuspage).  The complete retirement of O365 connectors which will necessitate the move to MS Teams workflows is over a year away.  This bug item is conflating two different issues considering I was directed here as a result of this forum thread: https://community.atlassian.com/t5/Statuspage-questions/MS-Teams-web-hook-wont-apply/qaq-p/2857574

0 votes
Clint Payton November 6, 2024

Here is additional info / instructions directly from Atlassian on using the Teams workflow integration, but I encounter the same error indicating my URL did not pass some form of validation and cannot be updated (step 7 in this case):
https://support.atlassian.com/statuspage/docs/set-up-microsoft-teams-integration/

0 votes
Clint Payton November 6, 2024

I have this same issue.  Can someone from Statuspage side please look at what validation is being performed on the webhook URL input field in the setup dialogue so we can start troubleshooting what might be triggering this error?  I can reproduce at will if a support person would like to capture a demo.

 

There is a validation issue with the new URL's that MS is providing.  MS is sunsetting the old URL format at the end of January.  More details here:
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

 

Clint

0 votes
Egor
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 4, 2024

Hey John,
Thanks for reaching out to Atlassian Community!

The error message "Yikes! It looks like the input you provided is invalid" typically indicates that there might be a format or compatibility issue with the webhook URL or the data being entered.

Here are some quick tips to help troubleshoot this:

  1. Webhook URL Validation: Make sure the webhook URL copied from Microsoft Teams is complete and properly formatted. Even a small typo or character issue can cause this error.
  2. Correct Integration Type: Double-check that you're using the correct type of webhook URL generated specifically for Teams. Webhook URLs from other services or that are misconfigured might not be accepted.
  3. Browser and Session: Try clearing your browser cache or using an incognito/private window to rule out session or caching issues.

I hope this helps. 

Best Regards,
Egor

Clint Payton November 6, 2024

It's not user error, There is a validation issue with the new URL's that MS is providing.  MS is sunsetting the old URL format at the end of January.  More details here:
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events