Grok in Microsoft Copilot: Word, Excel, not the phone
Grok in Microsoft Copilot entered Frontier preview Sept 12, 2026 in Word, Excel, and PowerPoint. Admin opt-in only — it still will not answer the phone.
On September 12, 2026, Microsoft started putting Grok inside Copilot in Word, Excel, and PowerPoint. Satya Nadella posted the welcome the same day. That is a document-app event, not a teammate event.
I sell the owned Slack setup for shops in the 10–250 range. The announcement still maps to the same buying decision: a model picker in Office is not the workflow that captures a request, writes the CRM, and pings the person who can say yes.
What did Grok in Microsoft Copilot actually ship?
Grok in Microsoft Copilot is a Frontier Program preview in Word, Excel, and PowerPoint on web and desktop. A Global admin has to opt the tenant in. It is not Grok Bot, not Teams, not Outlook, and not a phone agent.
Microsoft Learn is blunt about the plumbing. SpaceXAI hosts the models outside Microsoft. If you turn this on, prompts and document contents leave Microsoft-managed environments. Microsoft’s customer agreements, data residency commitments, and SLAs do not cover that hop. You sit on xAI’s enterprise terms instead.
The control plane is the Microsoft 365 admin center: Copilot settings, other large-language-model providers, SpaceXAI, terms checkbox, then named users or security groups. Microsoft says the connection can take a few hours. Copilot Studio needs a second allow in the Power Platform admin center. Frontier tenants in the EU, EFTA, and the UK are out of the first preview. SpaceXAI is on Microsoft’s Online Services Subprocessor List. Off by default is the whole product.
This is also not the Grok 4.6 Microsoft Foundry listing. Foundry is an Azure catalog endpoint. Copilot is a model choice inside the apps your staff already open. Neither one is Grok Bot. The Bot is a named teammate with a shared cloud computer, bundled into SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium. Copilot did not ship that.
Does Copilot Grok replace the Slack workflow you actually need?
No. A model inside a Word doc does not capture an inbound request, structure it, write it to the CRM, or escalate a dollar threshold to a named owner. That four-part path is still the job.
The map I deploy for Microsoft-shop teams usually lives in Slack:
- Trigger: a slash command, a workflow button, or a message in a named channel.
- Agent action: collect the missing fields, classify urgency, draft the next step.
- System of record: HubSpot, Salesforce, Jira, or a shared sheet — not the chat thread and not the Word draft.
- Human escalation: a named owner for anything above a threshold, any customer-facing promise, or any destructive write.
That is the same shape as AI for small business: pick one lane first, keep the record as truth, keep judgment with a person. Grok in Copilot can sit in step 2 for a spreadsheet formula or a slide outline if your admin opts in. It does not invent steps 1, 3, or 4. Microsoft says Teams, Outlook, and general commercial tiers come later, after Frontier feedback. Even then, Copilot is still an in-app assistant, not an always-on channel agent.
When should a Microsoft shop ignore this announcement?
Ignore it if your leak is missed calls, after-hours intake, or a website that does not convert. Ignore it if you are not in Frontier, or if you cannot send prompts off Microsoft’s estate. Ignore it if you wanted a chatbot in Slack without writing back to a system of record.
Use it if you already pay for Microsoft 365 Copilot, you already decided Grok is worth a bake-off against OpenAI and Anthropic inside Word and Excel, and a Global admin will own the opt-in. Then treat the preview as a document tool. The product is still the workflow.
I sell the owned version of that plumbing: a Slack AI Agent at $3,000–$6,000 one time for companies in the 10–250 range. You own the setup. You pay Microsoft or the model vendor for usage. There is no per-seat bot rent from me.
