Connect Microsoft Teams

What is this connection for?

The Microsoft Teams connector sends a formatted message to a specific channel. It is designed for internal alerts and transmissions to a team.

Functionality to check. ELChat sends a formatted message to an old webhook entering Microsoft 365. Microsoft now recommends Workflows. The compatibility of this path with a new Workflows URL must be validated before presenting it as fully operational.

What you need

ELChat requests a URL of incoming webhook Teams. This URL contains a secret giving the right to publish in the configured destination. Never share it in a public conversation or document.

Create Microsoft recommended URL

1. In Teams, open the team and the destination channel.
2. Click•••next to the canal.
3. Open Workflows.
4. Look for a model such as Send webhook alerts to a channel.
5. Set up the owner, team and channel.
6. Save workflow.
7. Copy the generated URL.

This procedure comes from the Microsoft documentation on webhooks Teams.

Information to be completed: confirm that a Workflows URL accepts the map produced by ELChat without adaptation. If not, the connector must be updated before use.

Former incoming webhook

If your organization already has an old Incoming Webhook connector, its URL can be entered, but Microsoft no longer guarantees its sustainability. Do not create a new dependency on this historical journey.

Connect Teams to ELChat

1. Open Dashboard > your site > IA Actions > Connectors.
2. Click Connect on the Microsoft Teams map.
3. Paste the full URL of the webhook.
4. Validate.

Check connection

Send a test message without customer data. Check that it appears in the chosen channel and that its title and text are legible.

Capacity available

Actual capacity	Type
Send a formatted message to the configured webhook	Writing

ELChat does not read channels or messages, does not respond in a discussion, does not create team and does not dynamically choose another channel.

Reconnect or Disconnect

Create a new URL, replace the ELChat connection and test it before deleting the old workflow. To disconnect, click Disable, then delete or disable workflow/webhook in Teams.

Common problems

• No message: URL has expired, workflow is disabled or history connector is removed.
• ** Format error:** the new Workflows URL does not accept the formatMessageCardthe current of ElChat; an adaptation of the connector is required.
• **Workflow without owner:**Workflows are linked to users. Add a co-owner and plan to leave the original owner.
• Private channel: certain Workflows scenarios do not support publication in a private channel.

Security and limitations

Anyone with the URL can potentially publish to the channel. Store it as a secret, renew it in case of exposure and choose a channel that does not receive more sensitive data than necessary.

Example: internal alert channel

Create a workflow teams dedicated to the channelAlertes ELChat, copy its webhook URL to the connector, then send a test message without customer data, for exampleTest de connexion ELChat — 2026-09-17.

The separate channel allows you to check the format without polluting a production conversation. The test message confirms that the URL points to the right team and channel. Remove or disable the test if this channel should not remain active.