← Docs

Docs · Connector reference

Microsoft Teams connector reference

Operations, inputs, troubleshooting, and questions for the Microsoft Teams connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Microsoft Teams connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

ResourceRecord identityStart withPage coverage
Joined teamsidTop levelNext-page URL
Team channelsidJoined teamsNext-page URL
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Next-page URL
Next-page URL. Follow the continuation returned by the provider before treating the collection as complete.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
OperationEffectApprovalProvider permissionsInputs
Message SendActionApproval requiredChannelMessage.Send3
Bot ReplyActionBy policyNone named4
Bot Reply CardActionBy policyNone named5
Bot Post CardActionBy policyNone named4
Bot Update ActivityActionBy policyNone named5

Inputs by operation

Message Send Action · approval required
Inputs for Microsoft-Teams Message Send
InputRequirementAccepted value
channel_idRequiredstringMinimum characters: 1Maximum characters: 512
contentRequiredstringMinimum characters: 1Maximum characters: 4000
team_idRequiredstringMinimum characters: 1Maximum characters: 512
Bot Reply Action
Inputs for Microsoft-Teams Bot Reply
InputRequirementAccepted value
conversation_idRequiredstringMinimum characters: 1Maximum characters: 512
reply_to_idRequiredstringMinimum characters: 1Maximum characters: 512
service_urlRequiredstringMinimum characters: 1Maximum characters: 2048
textRequiredstringMinimum characters: 1Maximum characters: 28000
Bot Reply Card Action
Inputs for Microsoft-Teams Bot Reply Card
InputRequirementAccepted value
cardRequiredobject
conversation_idRequiredstringMinimum characters: 1Maximum characters: 512
fallback_textRequiredstringMinimum characters: 1Maximum characters: 28000
reply_to_idRequiredstringMinimum characters: 1Maximum characters: 512
service_urlRequiredstringMinimum characters: 1Maximum characters: 2048
Bot Post Card Action
Inputs for Microsoft-Teams Bot Post Card
InputRequirementAccepted value
cardRequiredobject
conversation_idRequiredstringMinimum characters: 1Maximum characters: 512
fallback_textRequiredstringMinimum characters: 1Maximum characters: 28000
service_urlRequiredstringMinimum characters: 1Maximum characters: 2048
Bot Update Activity Action
Inputs for Microsoft-Teams Bot Update Activity
InputRequirementAccepted value
activity_idRequiredstringMinimum characters: 1Maximum characters: 512
cardOptionalobject
conversation_idRequiredstringMinimum characters: 1Maximum characters: 512
service_urlRequiredstringMinimum characters: 1Maximum characters: 2048
textOptionalstringMinimum characters: 1Maximum characters: 28000

When the Microsoft Teams task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the oauth connection and its access to the specific resource; a successful connection does not establish access to every object.

Resolve parent resources first: Joined teams. A matching display name is not enough for a child lookup.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Microsoft Teams connector

Can I use my existing agent with Microsoft Teams?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Microsoft Teams?

This connector supports 1 action, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Microsoft Teams?

Prepare Client ID, Client secret, Access token; the connection uses OAuth, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Microsoft Teams keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.