The release date in the opening paragraph is correct. The vendor announced Grok Bot 1.0 on Wednesday, November 11, 2026: the official Grok Bot account's post that day reads "Introducing Grok Bot 1.0. AI teammates that work alongside your whole team." November 2 was a different announcement, the Data Bot Team Bot for shared analytics, not the 1.0 launch. Windows Report also says Grok Bot 1.0 is available starting November 2.
Reports from other outlets don't all match. WebProNews says SpaceXSI took Grok Bot out of beta on Wednesday, Nov. 11, and Crypto Briefing says the release landed on or around November 11, 2026. The vendor's own dated post is the best source here.
What Grok Bot 1.0 says it does
The vendor groups the update into three areas: shared teammates, bots that take initiative, and bots that can do more.
- Shared ("multiplayer") bots: According to the launch post, users can share Bots and bring them into Slack, Microsoft Teams, and video calls. The vendor also claims that Bots learn from everyone they work with and keep improving their understanding of the team's knowledge and preferences.
- Bots that act first: The company says Bots can recognize work that needs to be done and offer to take it on. It adds that they can follow up on unfinished tasks, anticipate what a team needs next, and bring people in when a decision requires their judgment.
- More capable bots: The vendor claims bots are faster and more reliable in the browser, better at writing documents and building presentations, and better connected to Gmail, Google Calendar and GitHub. It also says they can also create interactive Pages that teams can edit together.
- Bots working with other bots: TeslaNorth reports that a shared Bot can follow a group discussion, bring in information from earlier conversations and coordinate with another Bot on a project.
None of these claims has been independently measured. AlphaSignal points out that the release provides no latency figures, task-success benchmarks, resource measurements, or cost comparisons. Treat words like "faster" and "more reliable" as the vendor's own claims.
Section summary: Grok Bot 1.0 bundles shared, proactive, more capable bots into one release. Its biggest claims come from the vendor and haven't been tested independently.
Teams support didn't appear overnight
Microsoft Teams access has been building for a while. In September, TeslaNorth reported that Grok Bot can now search, read, and send Microsoft Teams chats and channel messages, the official Grok Bot account said on September 11, 2026. That feature was a connector: the bot reached into Teams on behalf of a user.
Late in October, TestingCatalog spotted a deeper Teams integration in development, noting that Grok Bot already supports Slack and can use Teams messages to trigger routines, but the new functionality could provide more direct access to bots within Microsoft's collaboration platform. Version 1.0 delivers that: a Team Bot can now live inside Teams itself.
TeslaNorth also reports that an earlier November update added Team Bot sharing and login improvements alongside shopping and payments. The same outlet says Tailscale support recently gave bots a route to private company tools. Those two details come only from TeslaNorth. The vendor's launch post does confirm that Team Bots existed during the beta and have been improved since.
Who gets what: plan limits
Access depends on the plan, and outlets have reported it inconsistently.
| Feature | Plans, per the vendor |
|---|---|
| Team Bots (shared bots) | Team, Enterprise |
| Meetings | Team, Enterprise, Ultra |
| Turning on Meetings | Enterprise admins enable it in settings |
The x.ai launch post confirms that Team Bots are available on Team and Enterprise plans. Crypto Briefing reported that bots joining calls will need an Ultra plan. The vendor's own launch post and admin documentation list Meetings on Team, Enterprise and Ultra, so Ultra is one of three eligible plans, not the only one.
How a Grok bot gets into your Teams tenant
This is where it matters for Windows and Microsoft 365 admins. A user can't simply drop a bot into a Teams workspace. Grok Bot's admin documentation describes three gates:
- A Grok Bot team admin turns on Teams. On the Grok Bot page of the admin dashboard, under Shared Bots, the admin chooses Enable next to Enable Microsoft Teams. They then sign in with a Microsoft Teams administrator or Global administrator account. A Revoke option turns the integration off again.
- The bot's owner or a Manager connects it. They do this from the bot's details, under the option to bring it into the team's Microsoft Teams.
- A Microsoft Teams admin approves each bot in the Teams admin center.
WebProNews summed it up the same way: connecting a Bot to Microsoft Teams takes a team admin to turn it on, an owner or manager to connect the Bot and a Teams admin to approve it.
The admin dashboard also lists members who have linked a Microsoft Teams account and lets an admin unlink them. That's useful when someone leaves the company.
The vendor's documentation also says Grok Bot runs in Cursor's cloud, with each user's work on a separate Firecracker micro-VM. Security reviewers will want to factor in that third-party infrastructure.
Meetings: the part that needs the closest look
Grok Bot's documentation says the Meetings switch lets bots join Google Meet, Zoom and Microsoft Teams calls, transcribe them and report back. When the switch is off, bots can't join or read meetings. WebProNews, citing the changelog, says a Bot can now join a Google Meet, Zoom or Microsoft Teams call from a link, answer in the meeting chat and send a summary afterward. The vendor goes further and says bots track decisions and follow up after the call.
For compliance teams, the important word is transcribe. Any external bot that transcribes meetings can move meeting content outside your Microsoft 365 compliance boundary.
Microsoft offers its own control here. Teams meeting policies can require approval when an external bot is detected, which sends the bot to the lobby until someone admits it. Microsoft notes that this detection isn't perfect. Nothing shows that Grok Bot has been tested against it, but before you enable Meetings, it makes sense to:
- Review your Teams meeting policy for external bots alongside Grok Bot's own Meetings switch.
- Tell meeting organizers what a bot waiting in the lobby looks like, and that admitting it means its owner's settings now apply to your meeting.
- Get legal or records management to approve transcription for regulated meetings.
Shared bots, private chats and shared credentials
Grok Bot's documentation explains how shared bots work:
- Chats stay private. Sharing a bot doesn't make a copy, and each person's chat with a Team Bot is private, even from the bot's owner.
- Configuration is shared. Apps, secrets, skills and files added to a Team Bot work in every teammate's chat. Check them before you share a bot.
- Team learning needs approval. Suggested team memories and skill changes wait until the owner or a Manager approves them under Review learnings.
- Shared logins are off by default. If an admin enables Allow Shared Logins, everyone using that bot acts through one Manager's account, including when the bot makes changes.
- Each person pays. A Team Bot reply counts against the usage of the person it's answering.
The vendor also says bots respect each person's permissions, ask before sensitive actions, and check whether information is suitable for a public channel. Those are design goals. No one has independently shown that they prevent mistakes.
The bigger picture
AlphaSignal notes that Grok Bot 1.0 competes with Microsoft 365 Copilot, Claude Enterprise, and other agent platforms that operate inside workplace tools. The pitch is different, though. Copilot works inside Microsoft's own tenant boundary. Grok Bot is a third-party agent that enters Teams through admin consent and does its work on outside cloud computers. Choosing between them is a governance decision as much as a feature comparison.
Bottom line: Grok Bot 1.0 brings real Microsoft Teams integration and meeting attendance to Team, Enterprise and (for Meetings) Ultra customers. The admin checks are sensible, but they only help if admins actually use them. Read the setup steps above before anyone in the finance channel starts adding a new "colleague."
Correction (November 11, 2026): An earlier version of this article said the vendor's Grok Bot 1.0 launch post was dated November 2 and that November 11 was only the social media push. That was wrong: the vendor announced Grok Bot 1.0 on November 11, 2026, and the November 2 announcement was for Data Bot, a Team Bot for shared analytics. The opening paragraph's November 11 date was correct.