At a glance
Use Dots in Microsoft Teams
OpenAI’s current ChatGPT Learn guide says you can message the same dot in Microsoft Teams, Slack, and ChatGPT. Connecting Teams gives you another place to reach your dot; it does not automatically connect every Teams file, channel, or app to its work.
Use Teams when you want to ask your dot for a progress update, clarify a decision, or receive a prepared draft in a familiar conversation. The dot can keep relevant context across connected contact methods, but each channel keeps its own messages. Before it shares information from a private conversation with other people, it checks that you have allowed it.
Availability and setup depend on the account and workspace. Treat the Add menu in your dot’s profile and your workspace’s current controls as the source of truth.
Keep two permissions distinct: messaging your dot in Teams and giving a dot access to connected app data are separate choices. A Teams conversation does not grant access to every team, chat, file, or tenant.
Connection
How to connect your dot to Microsoft Teams
Open your dot’s profile in ChatGPT and select Add. The profile shows the contact methods available for that dot and account. Choose Microsoft Teams if it appears, then follow the prompts to connect the intended Teams account or tenant. Use the same dot you expect to reach from ChatGPT.
- Check the account. Confirm that ChatGPT is signed in to the account that owns the dot and that Teams is signed in to the organization you intend to use.
- Review the connection prompt. Read the access and audience details before continuing. If the setup asks for organizational consent or the option is unavailable, contact the workspace or Teams administrator.
- Start with a private, low-risk test. Message the dot in a one-to-one conversation or an approved test location. Ask it to summarize facts you include directly in the request.
- Check the result and destination. Confirm that the response appears in the expected Teams conversation and that no unrelated private context was shared.
For managed workspaces, administrators can control who may use dots and whether messaging channels are available. OpenAI documents these controls for eligible Enterprise workspaces during the beta. The exact workspace settings and rollout can change, so use the admin guide linked below for current instructions.
What setup does not prove: a successful Teams message does not confirm that the dot can read a particular channel history, meeting transcript, or connected file. Test each source and permission separately before relying on it.
Access boundaries
Teams messaging and connected data are different
There are two distinct ways Teams may relate to a dot:
| Connection | What it is for | What to verify |
|---|---|---|
| Teams as a contact method | Sending messages to your dot and receiving replies or updates in Teams. | That the contact method is available, the right account or tenant is connected, and the conversation audience is appropriate. |
| Teams or another app as a work source | Giving the dot access to information through an authorized app connection or workspace capability. | The connected account, allowed sources, available actions, and any approval requirement. Read access does not automatically grant write or send access. |
OpenAI’s documentation says that connecting a messaging channel and connecting apps are separate. A dot can use only the app connections available to it and the access granted by the connected account. If a company administrator manages the workspace, ask them which dots capabilities and app controls apply to your role.
Messages in Teams are visible to people in that conversation. Keep sensitive details in the narrowest appropriate channel, and ask for a draft when a response could affect another person, team, or external audience.
First use
A practical first Teams task
Choose a short, approved project update with a known source. Ask the dot to prepare a decision summary from information you include or identify explicitly. Do not start by asking it to post a broad announcement.
Example request
“Using the notes in this message and the named project channel, prepare a short status brief. Separate confirmed facts, proposals, and open questions. Show the message or file supporting each point when available. Do not infer an owner or deadline. Draft any Teams follow-up for my review; do not send it.”
Review whether the brief separates agreed decisions from suggestions. Check every owner, deadline, and source. If the dot cannot access the named channel or file, the useful answer is a clear limitation and a request for the missing material, not a guessed summary.
When your team needs repeatable meeting agendas, decision notes, or follow-up tables, see the separate Microsoft Teams workflows guide. This page stays focused on connecting Teams and understanding what the connection allows.
Troubleshooting
If the Teams connection does not work
- Teams is missing from Add: check account eligibility, rollout availability, and workspace controls. For managed workspaces, ask an administrator whether dots and messaging channels are enabled for your role.
- The dot does not respond: confirm you are messaging the intended dot from the connected account. Try a new, short message in a supported one-to-one or approved channel conversation.
- A source is missing: check app connections separately from messaging. Confirm the correct account and source permissions, then ask the dot to identify which source it used.
- A team member cannot see the result: verify the destination conversation and the file or link’s own sharing permissions. A visible link does not mean every recipient can open it.
- The result mixes sources: request a revision with the allowed channel, date range, and source list stated explicitly. Ask it to show conflicting or missing evidence instead of silently resolving it.
For broader app access failures, use the existing Dots connection troubleshooting guide. For data handling and permission boundaries, see Dots privacy and permissions.
Copyable brief
A safe first-use task brief
Use this as a starting point, then replace the brackets with sources and an audience that are appropriate for your account.
Your review
Check the connection before expanding the task
Use this checklist for the first pass. Tick only what you have actually confirmed.
0 of 5 checked
Questions
Microsoft Teams and Dots FAQ
How do I connect my dot to Microsoft Teams?
Open your dot’s profile and select Add to see the contact methods available to your account. Choose Microsoft Teams if it is offered, then follow the connection prompts. Workspace controls may apply, and availability can vary by account.
Does connecting Teams let my dot read every team or file?
No. A messaging connection and connected app access are separate. A dot can use only sources and actions available through the permissions and authorizations you have granted.
Does Teams messaging use the same dot as ChatGPT?
Yes. OpenAI’s current guide says connected contact methods reach the same dot. Messages remain in their respective channels rather than being copied across every conversation, while relevant context may carry between them.
Why can’t I see Microsoft Teams in the Add menu?
Check that you are signed in to the account that owns the dot and that the feature is available to your account. In eligible managed workspaces, an administrator may need to enable dots and messaging capabilities first.
Can the dot post in a Teams channel automatically?
A channel connection does not by itself define a monitoring schedule or approve every future post. State which channel to use, what the dot should prepare, and what needs your review. Check the audience before sharing private context.
Where can I find the current setup details?
Use OpenAI’s Message your dot guide for contact methods and the current workspace admin guide for organization controls. Availability and controls can change during rollout.