This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
![](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)
Thanks for raising your issue. We will check this at our end and will update you accordingly.
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)
@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.
Corné Eggebeen - Please do share the connector URL along with tenant id, so that we can raise a Bug/ICM for this.Thanks!
@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.
@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!
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!
@Prasad-MSFT any updates ?
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!
![](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)
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.