The Microsoft Teams integration is a workflow app inside https://lengrowth.com/integrations.

The Teams integration is not a data source. It is a workflow app.

The visible setup copy says:

That means the integration relies on the Teams workspace and tenant setup rather than a generic analytics connector.

The card description also makes the use case clear: Teams is for pushing alerts into a channel and interacting directly with the AI from a place the team already uses.

Use Microsoft Teams when:

Choose the company from the header before opening the Teams card.

If no company is selected, the integrations page tells you to pick or create a company first.

In the Workflow Apps tab, open the Microsoft Teams card.

The card may show Not connected, Connected, Configured, or Active Tenant depending on the current state.

The visible input field is labeled Teams Tenant ID.

The page expects a Tenant ID before it can connect. If the input is blank, the app shows an error telling you to enter a Teams Tenant ID first.

Use the Connect button to save the tenant connection for the selected company.

If the connection succeeds, the app shows Teams connected.

After the connection is saved, the card should show a connected state.

The page also stores a status summary that can say Tenant ID saved locally when the company has an ID on file.

That is the easiest way to tell that the integration is active from the LenGrowth side.

Depending on how far the setup has progressed, the card may also show Configured or Active Tenant instead of the disconnected state.

Like Slack, the Teams card stays simple after it is connected.

It is mainly there to show:

This makes it easy to confirm the connection without leaving the integrations page.

Once Teams is connected, LenGrowth can send workflow activity into the Teams environment connected to the company.

The integrations page does not make unsupported promises about every possible Teams feature, so keep the guidance focused on what the UI actually shows:

Teams is part of the workflow-app side of LenGrowth, so it is the right choice when operational updates and interaction should happen inside Teams rather than in a reporting-only tool.

If you disconnect the card, the tenant value is cleared for that company and the card returns to the disconnected state.

That means the Teams Tenant ID field is empty. Paste the tenant ID before clicking Connect.

The help article should not invent a location if the app does not say one. The visible setup text only says to install the bot via Developer Portal and paste the tenant ID. If the customer cannot find it, they will need to check their Microsoft Teams admin or bot setup.

That usually means LenGrowth has saved the tenant value, but the Teams side still needs review.

Use the card’s disconnect action. After that, the tenant value is cleared from the selected company.

Make sure you are in the Workflow Apps tab, not Data Sources.

That usually means the tenant ID is saved, but the Teams side still needs a final check. Revisit the Teams setup in your Microsoft environment, then return to LenGrowth.

Switch the active company in the header first. The Teams connection always belongs to the selected company workspace.

Disconnect and reconnect the card with the new Tenant ID so the saved value stays aligned with the right workspace.

If something does not look right, confirm you are using the correct account, page, and permission level.