4,144 questions
Hi @Meet Rathod
Please use the workaround for new Jira Server connectors. Editing will be blocked until issue on new Teams client is fixed. Instead of editing you can try to recreate a connector.
Regards,
Volodymyr B.
When edit an existing configured connector in New Teams, instead of modifying the existing configuration, a new configuration for the connector is being created
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 48%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Meet Rathod
25
Reputation points
In New Microsoft Teams, we’ve observed that when we attempt to edit an existing configured connector, instead of updating the existing configuration, new configurations are being created for the connector. Interestingly, this behaviour differs from the behaviour in classic Teams, where everything works as expected. Additionally, in the new Teams, the webhook URL changes each time we edit an existing configured connector, whereas webhook URL remains unchanged in classic Teams. I am here providing two webhook URL that suppose two remain same instead it is changing every time we tried to edit existing connector configure.
- first time while adding connector configuration webhook URL https://connectors.msteams-atlassian.com/JiraServer/a49b24fb-bbc9-4202-8f60-b56f71e78de6@3adb963c-8e61-48e8-a06d-6dbb0dacea39/d0cfa88f-4a35-4428-8a99-f947c50b1162/ddd2f499116a40b5ad2da12ed23f2cf7/8e13c472-3a13-4dc2-a914-f75d71c45d49?tenantName=xyz
- after editing same configuration webhook URL https://connectors.msteams-atlassian.com/JiraServer/a49b24fb-bbc9-4202-8f60-b56f71e78de6@3adb963c-8e61-48e8-a06d-6dbb0dacea39/d0cfa88f-4a35-4428-8a99-f947c50b1162/4f2a47fa38f748c18a284ae7e9177c6b/8e13c472-3a13-4dc2-a914-f75d71c45d49?tenantName=xyz
Microsoft Teams | Development
Microsoft Teams | Microsoft Teams for business | Other
10,942 questions
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 78%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator2024-03-18T05:51:07.33+00:00 Thanks for raising your issue. We will check this at our end and will update you accordingly.
-
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator
2024-03-18T09:16:22.8566667+00:00 Hi Meet Rathod, we tried to repro this issue by editing an already created incoming webhook connector in New Teams, however the webhook URL didn't change.
Incoming webhook URL prior edit:
https://m365x17798679.webhook.office.com/webhookb2/959f02ee-b8eb-4acc-8d36-75e19f7b519b@4ad59956-0f88-4b88-a9d0-570b6eb4e66b/IncomingWebhook/026e4c0131964f94a159ee820c6235a3/ce9def33-d7fc-444c-8728-be1f95e6b6f2
After edit:
https://m365x17798679.webhook.office.com/webhookb2/959f02ee-b8eb-4acc-8d36-75e19f7b519b@4ad59956-0f88-4b88-a9d0-570b6eb4e66b/IncomingWebhook/026e4c0131964f94a159ee820c6235a3/ce9def33-d7fc-444c-8728-be1f95e6b6f2 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 36%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECE%3C/text%3E%3C/svg%3E)
Corné Eggebeen 5 Reputation points2024-03-21T09:19:10.27+00:00 @Prasad-MSFT We are experiencing the same issue. It is not a problem for the Incoming Webhook connector, but for custom connectors. I posted our situation on: https://answers.microsoft.com/en-us/msteams/forum/all/new-microsoft-teams-webhook-url-retrieved-from/f3b28ebd-233d-40d7-ad3f-da9efffa1bec.
It is quite problematic for us, since the classic Teams version will force users to migrate to the new Teams client on March 31st. This will unfortunately make our connector unusable if the webhook URL keeps changing.
-
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator
2024-03-22T08:11:06.9433333+00:00 Corné Eggebeen - Please do share the connector URL along with tenant id, so that we can raise a Bug/ICM for this.Thanks!
-
Meet Rathod 25 Reputation points
2024-03-22T08:30:47.93+00:00 @Prasad-MSFT I have tested both Incoming Webhook connector and custom connector. but the webhook URL change things happening in custom connectors only. For the furthered validate this issue I have used available connector of other product ex. Jira Server . Same thing are also happening in other available connector.
-
Corné Eggebeen 5 Reputation points
2024-03-22T10:27:58.22+00:00 @Prasad-MSFT Our connector is SuperOffice for Teams. This points to our production version of our connector, however, we also experience the same issue in our testing and staging environment for the sideloaded version of this connector. Our tenant id is: b43de5cd-783a-4286-a89c-1dcb58666e6c.
Thanks for looking into this!
-
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator
2024-03-27T10:05:34.9566667+00:00 Corné Eggebeen We have raised an ICM for this issue and engineering team is looking into it. We will inform you once we have further update. Thanks!
-
Meet Rathod 25 Reputation points
2024-04-04T06:41:24.88+00:00 @Prasad-MSFT any updates ?
-
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator
2024-04-08T05:21:54.8866667+00:00 Meet Rathod- Apologies. At the moment, we have not received any updates from the engineering team. As soon as we receive any updates from them, we will notify you in this thread.
Thank you!
-
Meet Rathod 25 Reputation points
2024-06-05T08:41:43.5166667+00:00 @Prasad-MSFT Any updates?
-
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator
2024-07-08T08:23:58.3266667+00:00 We got an update from engineering team that, Fix has reached GA 100%. Please do verify.
-
Corné Eggebeen 5 Reputation points
2024-10-30T13:08:16.3033333+00:00 It has worked for a while after the last comment in this thread. However, after Microsoft announced to retire connectors (https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams) and released an update on 16-10-2025 to provide additional security mechanisms to the webhook URLs, the old issue started to come back after recreating the connectors as instructed on https://learn.microsoft.com/en-us/microsoftteams/m365-custom-connectors#update-connectors-url. Now it is not working again.
-
Corné Eggebeen 5 Reputation points
2024-11-06T14:46:38.91+00:00 @Prasad-MSFT Do you know if the team is working on this?
Sign in to comment
1 answer
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 18%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVB%3C/text%3E%3C/svg%3E)
Volodymyr Batrukh 0 Reputation points2024-04-30T15:52:36.15+00:00