Skip to content

Commit

Permalink
Merge branch 'public' into patch-1
Browse files Browse the repository at this point in the history
  • Loading branch information
wlibebe authored Jan 29, 2025
2 parents b28e4ab + b11198c commit 5416e86
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion Teams/m365-custom-connectors.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Connectors in Microsoft Teams deliver content and service updates directly from

Teams and Microsoft 365 groups use connectors. You can use the same connectors in Teams and Microsoft Exchange.

Any team member can add a connector to a channel, if the team permissions allow it. The updates from the service, that the connector fetches information from, notifies all the team members. Any team member with the permissions to add or remove can modify connectors setup done by other members.
Any team member can add a connector to a channel, if the team permissions allow it. The updates from the service, that the connector fetches information from, notifies all the team members.

> [!IMPORTANT]
> Developers can't register new connectors on the [Connector developer portal](https://aka.ms/connectorsdashboard).
Expand Down Expand Up @@ -59,6 +59,9 @@ To update the URL, follow these steps:

:::image type="content" source="media/connectors-update-url.png" alt-text="Screenshot showing the option to update a webhook URL.":::

> [!NOTE]
> If the **Update URL** button is greyed out and you're unable to update the URL, create a new connector configuration.
* For other types of connectors, remove the connector and recreate the connector configuration.

1. Use the updated URL or the new connection in the systems that were posting to the old URL. The Configure page displays that the URL is updated.
Expand Down

0 comments on commit 5416e86

Please sign in to comment.