How to Automatically Block External Meeting Bots in Microsoft Teams

IT administrator configuring Teams meeting protection

External AI note-takers and meeting bots are turning up in more and more Teams meetings, often invited by someone outside your organisation and often without anyone really thinking about where that recording or transcript ends up. Microsoft has been steadily adding controls for this, and the latest one is a Teams meeting policy option that automatically blocks identified external meeting bots from joining. Here’s what it does and exactly how I’d roll it out.

What’s changing

This is covered in Message Center post MC1459141 (Roadmap ID 566201). Today, Teams can already detect external bots, mark them in the lobby and require the organiser to admit them. The new option goes one step further: when it is enabled, identified external meeting bots are simply prevented from joining meetings governed by that policy.

The key points from Microsoft are:

  • It’s a new option in the existing Manage bots meeting protection settings in Teams meeting policies.
  • It is off by default. Nothing changes unless an administrator turns it on.
  • It can be assigned to specific users or groups through normal meeting policy assignment.
  • Existing bot detection and visibility for organisers and administrators stays the same.
  • Targeted Release started mid-September 2026 and was due to complete by late September. General Availability began in early October 2026 and is now expected to complete by the end of November 2026 (timeline updated 3 November).

For background, Microsoft Learn’s Manage external bots and their access to meetings page explains how detection works, using infrastructural and behavioural signals during the join process. Detection isn’t perfect, so a bot that isn’t identified can still get in, and occasionally a human may be misclassified.

Before you start

  • You need the Teams Administrator or Global Administrator role.
  • The option may not appear yet if the rollout hasn’t reached your tenant. If you don’t see it, check back later rather than hunting for a workaround.
  • I haven’t confirmed the exact wording of the new toggle across tenants, so look for the option to automatically block identified external meeting bots inside the Manage bots section rather than expecting a specific label.
  • Remember this may block note-taker and recording bots that some of your people rely on. That’s why piloting matters.

Step-by-step: enable auto-block

  1. Sign in to the Teams admin center at https://admin.teams.microsoft.com.
  2. Go to Settings & policies, then Meeting policies.
  3. Choose where to apply it. For a pilot (recommended), select Add to create a new policy, such as Pilot – Block meeting bots. To apply it to everyone, open Global (Org-wide default).
  4. Scroll to the Manage bots section.
  5. Turn on the option to automatically block identified external meeting bots.
  6. Select Save.
  7. If you created a pilot policy, assign it to the pilot users or a group. You don’t need to assign the Global policy, as it already applies to everyone without another policy.
  8. Wait a few hours for the policy to apply. Changes to meeting policies aren’t instant.
  9. Test it. Schedule a meeting as a pilot user and have an external bot try to join. It should be blocked rather than sitting in the lobby waiting for approval.

Doing it with PowerShell

If you prefer scripting, the Set-CsTeamsMeetingPolicy documentation lists an ExternalBotAccessMode parameter with three values: AllowAllBots, RequireApprovalWhenDetected (the default) and BlockDetectedBots. Using the Microsoft Teams PowerShell module:

Connect-MicrosoftTeams
New-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots"
Set-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" -ExternalBotAccessMode BlockDetectedBots
Grant-CsTeamsMeetingPolicy -Identity "user@yourdomain.com" -PolicyName "Pilot-BlockBots"
Get-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" | Select-Object Identity, ExternalBotAccessMode

As always, test the cmdlets in your own tenant first, as parameter availability can lag the rollout.

Microsoft’s recommendations

Microsoft suggests the following if you plan to enable automatic blocking:

  • Review your organisation’s use of meeting bots and automated meeting applications.
  • Evaluate the feature with a pilot group before broader deployment.
  • Review existing Teams meeting policies and decide which users or groups should receive the policy.
  • Update internal documentation and help desk guidance.
  • Communicate the change to meeting organisers and users who rely on automated meeting bots.

My take

For most businesses I work with, this is a sensible control to have, but it’s not one to flip on for the whole tenant on day one. Find out who is actually using external note-takers, pilot it with a group that isn’t, then widen it once you know what breaks. Pair it with a clear position on which AI meeting tools are approved, because blocking the unapproved ones works best when people know what they should be using instead.

How to let Grok Bot make outbound phone calls with Bland.ai

Linocut print of a telephone handset resting on a notebook beside a coffee cup on an office desk at morning

Grok Bot can already place phone calls on its own. There’s a catch for me, though. The official Grok Bot docs say built-in phone calls are available in the US only, and I’m in Australia. Most of the people I’d want a Bot to ring are on +61 numbers.

So I set up a dedicated Bot I call dial bot, connected to Bland.ai, which is a US voice AI platform built for exactly this. It has made real calls to Australian mobiles for me. This post walks through how I set it up, what it costs, what comes back after each call, and the guardrails I’d insist on before an MSP or SMB lets a Bot near a phone.

What this gives you, and why an MSP should care

Picture a Bot that can ring a client to confirm Thursday’s onsite visit, call a supplier to check whether a part has arrived, or follow up a prospect who asked for a callback. You tell it who to call, why, and what to cover. It makes the call in a natural voice, and then gives you a summary, a transcript and the cost.

For a small MSP that’s a few hours a week of phone tag handed off. And it comes with a written record.

I’ve written before that AI with a human in control beats AI on its own. Phone calls are where that matters most, because you can’t unsend a phone call.

What you need before you start

  1. A Bland account. Sign up at app.bland.ai. You can also create one during the Grok Bot sign-in flow described below.
  2. A Bland API key, or the device sign-in. If you use a key, it’s in the Bland dashboard under Settings, API Keys.
  3. Credits. Bland bills per minute from a credit balance. Its docs say international calls need a completed purchase: at least US$5 of credits bought under Billing, or auto-recharge turned on. Calls to Australia count as international, so plan on that first purchase.
  4. A Grok Bot you’re happy to dedicate to calling. I keep calling in its own Bot so its instructions, memory and approvals stay separate from everything else.

Step 1: Add the Bland connector to Grok Bot

Bland publishes an official command-line tool, bland-cli, which includes an MCP server. MCP is the standard way an AI assistant connects to an outside tool. When I set this up in October, the Grok Bot plugin catalog had no Bland entry, so the Bot added the official server as a custom connector instead.

You don’t type any of this yourself. In my case:

  1. I asked the Bot to add Bland’s official connector.
  2. It checked the catalog, found nothing for Bland, and asked me to confirm with a question card before it changed anything.
  3. It added a connector called Bland AI that runs Bland’s official server, npx -y bland-cli mcp, on the Bot’s own computer.
  4. It ran a harmless test, listing the calls on my account, to prove the connection worked.

Bland also runs a hosted MCP server at https://api.bland.ai/v1/mcp, which takes your API key as a bearer token. The local one suits a brand new setup because of the sign-in flow in Step 2.

One thing to know: connectors are added to your Grok Bot account, not to a single Bot, so other Bots you own can see it too. That’s one more reason to keep the calling rules in the dedicated Bot’s instructions.

Step 2: Give the Bot access without pasting a key into chat

This is the step I’d be strictest about. Never paste an API key into a chat message. Grok Bot gives you two safer ways to do it.

Option A: the secure secret box. When dial bot first started, it asked for my Bland key and showed a secure entry box in the chat rather than asking me to type it. The key is stored as a secret on the Bot’s computer and made available to it as an environment variable, BLAND_API_KEY. The Bot never sees the value, and any output that would contain it shows as redacted.

Option B: Bland’s device sign-in. The Bland AI connector includes two tools, bland_auth_login and bland_auth_poll. The Bot starts the sign-in and shows you a short code and a link. You open the link, sign in to Bland (or create an account there), and approve the request. Bland saves the key to the connector’s profile on the Bot’s computer, and the key never appears in the conversation.

A tip from my own setup: the first value I gave the Bot was the wrong kind of ID, and Bland rejected it as unauthorised. If your first test fails with an authentication error, check you copied the API key itself and not an organisation or voice ID.

Step 3: Pick a voice and set sensible defaults

Bland has stock voices, and you can clone your own in its Voices studio. I started with a stock voice called Josh and later moved to my own.

I also had the Bot save a call template, so every call starts from the same baseline. These settings made calls sound like a person, not a robocall:

  • Wait for the greeting. The Bot waits for the other person to say hello before it speaks, rather than talking the instant the line connects.
  • A casual first sentence that discloses. Mine opens with “Hi, it’s Robert Crane’s AI assistant, just so you know, this call’s recorded.”
  • A short briefing, not a script. Purpose, talking points, and what success looks like.
  • A maximum duration. Mine is 10 minutes, so a confused call can’t run up the bill.
  • A voicemail rule. Either hang up, or leave a short message pointing to my email.
  • Call screening handling. If an automated screener asks for a name and reason, give one line and wait for a human.

Step 4: Place your first call

Bland requires numbers in E.164 format. In Australia that means dropping the leading zero and adding +61, so 0412 345 678 becomes +61412345678. One of my early calls went sideways because a number was given to the Bot as “+16 416…”, which is a malformed country code. My Bot now flags odd country codes before dialling.

Start with a call to your own mobile. Then try something like this:

Call Sam on +614XXXXXXXX. Sam is the practice manager at a client site. Purpose: confirm Thursday’s 2pm onsite visit to replace the reception PC. Talking points: check the time still works, ask whether someone can let us in, and ask if parking is available. If Sam wants to change the time, agree a new day and time in Sydney time and say I’ll send an updated invite. If it goes to voicemail, leave a short message asking Sam to reply by email.

Before it dials, my Bot reads the plan back: the number, the voice, the opening line and what happens on voicemail. Then it asks Good to place the call? with options to call now, add a voicemail, or cancel. Nothing gets dialled until I say yes.

Step 5: Read what comes back

When Bland accepts the request it returns a call ID. My Bot treats that as “submitted”, not “answered”. It then checks the call every so often until it finishes, and reports:

  • the outcome, such as answered, voicemail or failed
  • how long the call ran
  • what it cost, in US dollars
  • Bland’s short summary of the conversation
  • the full transcript, only when I ask for it, which keeps each check light

If a call is recorded, Bland also provides a recording link in the call details. A timeout or a missing result isn’t treated as success. The Bot checks the existing call ID before even suggesting another attempt, and it never redials on its own.

What it costs

Here’s Bland’s published pricing as of November 2026, from its pricing page and billing docs. All figures are in US dollars:

  • Start plan: free, with US$0.14 per connected minute and no platform fee. Limits are 100 calls a day and 10 at once.
  • Build plan: US$299 a month, with US$0.12 a minute.
  • Billing: charged to the second, with a minimum of US$0.015 for each outbound attempt.
  • Agent Phone Plan: US$19.99 a month for one dedicated number, with unlimited calls and texts to the US and Canada. Calls to other countries still come out of your credit balance.

My own calls to Australian numbers lined up with that rate. A one-minute call cost US$0.16, a two-minute call US$0.29, and a three-minute call US$0.43. Check the current numbers on Bland’s site before you budget, because it changed its pricing in December 2025.

Australian considerations

  • Caller ID. By default, Bland places calls from its own pool of US-based numbers, so the number your contact sees can change from call to call. A consistent number means buying one from Bland or connecting your own Twilio number. If you want an Australian number, check that with Bland first.
  • Expect screening. A US caller ID is more likely to be ignored here, so tell people a call is coming.
  • Content filters. Bland rejected one of my calls because of a single word in the briefing. It was a security term. Rewording the briefing fixed it.

Consent, recording and the law

This is general information, not legal advice.

Australian call recording rules vary by state and territory, and some are stricter than others. Several generally require consent from everyone on the call. Your contact may also be in a different state from you. Telling the person up front that they’re talking to an AI assistant and that the call is recorded is the honest default, and it’s why my opening line does both.

Think about where the data goes, too. Bland is a US company, and it holds the audio and transcripts. When I wanted old recordings removed, I had to send Bland a request, because there was no way to do it from the Bot. Only share recordings or transcripts with people who were on the call, unless you’ve had proper advice.

Finally, only call people who expect to hear from you. If anything starts to look like telemarketing, check the ACMA’s Do Not Call Register and telemarketing rules first. Grok Bot’s terms make you the caller of record for its own calls; hold yourself to the same standard with Bland.

Troubleshooting

  • Unauthorised or 401 errors. Wrong key, a non-API ID, or an expired sign-in. Re-run the sign-in, or enter the key again in the secure box.
  • “Insufficient balance” or international calls blocked. Buy credits under Billing in the Bland dashboard. Don’t assume the balance is the problem without seeing the actual error.
  • The call is rejected straight away. Check the number is in E.164 format, then look for a flagged word in the briefing.
  • The Bot talks over the greeting. Make sure it waits for the greeting before speaking.
  • No result yet. Ask the Bot to check the existing call ID. Don’t place a second call.

Summary

Built-in Grok Bot calling is US-only for now. Bland fills the gap for Australians, and setting it up takes about ten minutes:

  1. Add the official Bland connector.
  2. Sign in with the device code or the secure secret box, never by pasting a key.
  3. Buy a few dollars of credit.
  4. Save a call template that discloses up front.
  5. Make the Bot confirm every call before it dials.

Keep a human in the loop and the Bot becomes a genuinely useful teammate on the phone. If you’re also looking at the voice features built into Grok Bot, I covered those in how to set up voice in Grok Bot, and what is limited from Australia.

Sources

  • Grok Bot docs, Message and collaborate, Have a Bot make a phone call (docs.x.ai/grok-bot/chat-and-collaboration), checked 19 November 2026
  • Grok Bot terms, section 2.7 Phone Calls (cursor.com/terms/grok-bot), checked 19 November 2026
  • Bland docs: Send Call API, Billing & Plans, CLI, MCP Server and Agent onboarding (docs.bland.ai), checked 19 November 2026
  • Bland pricing (bland.ai/pricing), checked 19 November 2026

GPT 6.2 Astra beats Sol and Opus 5.5 in my latest Cowork evaluation

Three marbled-ink circular swirls in indigo, vermilion and gold on cream, in the suminagashi style

On 13 November I called a winner in Copilot Cowork: Opus 5.5 edges Fable 5.2. That head-to-head was Opus 5.5 at 8.9 against Fable 5.2 at 8.6. I said then that I had not re-run Astra, so it was not a new overall series winner, and that I would test the next model when it turned up.

The next round is in. I have now put two new GPT 6.2 reports through the same kind of evaluation, alongside the Opus 5.5 report from September. The full evaluation is here on GitHub. The winner is not Opus 5.5 this time.

What was compared

The evaluation assessed three reports, all responding to the same underlying prompt: is the traditional MSP and TSP business model becoming obsolete between 2029 and 2036? The three documents are:

  • Document A: the GPT 6.2 Astra report from Cowork, dated 18 November 2026, written as an Australian owner and investor decision report for CIAOPS.
  • Document B: the Opus 5.5 report from Cowork, dated 23 September 2026, a strategic research report for MSP owners, Microsoft partners, boards and private equity investors.
  • Document C: the GPT 6.2 Sol report from Cowork, dated 18 November 2026, a board and investment briefing for CIAOPS.

Scoring uses four weighted criteria: Argument 35%, Evidence 25%, Detail 20% and Presentation 20%. The evaluation is relative and substance-focused.

The result

RankDocumentOverallArgumentEvidenceDetailPresentation
1A: Astra / GPT 6.28.939.29.08.58.8
2C: Sol / GPT 6.28.789.08.98.78.5
3B: Opus 5.58.698.58.79.28.5

Document A, the GPT 6.2 Astra report, comes first. The evaluation calls it the tightest on epistemic discipline, with a fully reconciled decision model and the most practical capital gates for an owner or investor audience. The Sol report is a very close second. Opus 5.5 is third, but it still wins on Detail, 9.2 against 8.5 and 8.7, because it has the broadest coverage of market, security and history.

The evaluation says A and C are both clearly ahead of B on the two heaviest criteria, Argument and Evidence. Its stated reason is that Opus 5.5 was more assertive on magnitude and probability claims than its evidence strictly supports, including the 30 to 60 per cent labour-removal figure. It also says the earlier research cut-off meant Opus 5.5 missed some later November Microsoft detail that A and C used.

Where Astra and Sol differ

The gap between first and second is small. According to the evaluation, A is tighter on capital gates, inference language and the executive reading path. C is stronger on cash-trough quantification, pricing-headroom sensitivity and residual multi-vendor service, and uses a larger reference firm. The file notes that C’s title says the traditional model is becoming obsolete, while its body concludes it remains viable. It lists that as the only notable polish issue, and says C would pass A with a title that matches the body and tighter tranche limits.

How this compares with 13 November

In Opus 5.5 edges Fable 5.2, Opus 5.5 beat Fable 5.2 on evidence (9.2 against 8.3) and detail (9.3 against 8.4), while Fable 5.2 was the more polished read. The same pattern shows up again here. Opus 5.5 is still the most detailed report and still loses points for how tightly it handles claims. What has changed is the competition: two GPT 6.2 reports, Astra and Sol, are now ahead of it on overall score.

A few cautions. This is a different evaluation from the one in the 13 November post, so the Opus 5.5 score of 8.69 here should not be set against the 8.9 there as if it were a drop. Fable 5.2 was not part of this evaluation, so I cannot tell you where it would land among these three. The file does not include credit costs, so there is no price comparison here. And this is one prompt on one topic, so it is a data point, not a verdict on every task.

I have not checked which of these models are available, or in which Microsoft 365 Copilot surfaces, for your tenant. This post says nothing about availability. Check Microsoft’s official documentation for that.

What it means for choosing models in Copilot

For an MSP, I think the useful lesson is about what you are choosing for. The evaluation rewarded the reports that were careful about what they could and could not claim, and that turned analysis into reversible, bounded decisions. That is the same quality I want in a client-facing report. A longer, broader report lost to tighter ones on the criteria that carried the most weight.

So I would not pick a model on the scoreboard alone. Run your own representative prompt, such as a client QBR, a security review summary or a pricing paper. Then judge the outputs on argument and evidence first and detail second. If you need breadth, Opus 5.5 still earned the best Detail score here. If you need something a board or an owner can act on, the GPT 6.2 reports did better in this test.

Model names matter here: Astra and Sol are both GPT 6.2, and Opus 5.5 is a different model again. Keep a record of exactly which model produced each output when you compare, because they change quickly and the winner changes with them.

As soon as the next model shows up in Cowork, I will run it through the same test.

How to Update All Apps on a Windows Device with Winget

IT technician relaxing with a coffee while a laptop updates in teal and amber light

Keeping every app on a Windows device up to date is one of those jobs everyone agrees matters and nobody enjoys. Browsers, PDF readers, runtimes, utilities, each with its own updater, or none at all. Out-of-date apps are also a favourite way in for attackers. The good news is that Windows already includes a tool that can update most of them in one hit. It’s called winget.

What is winget?

Winget is the command-line client for the Windows Package Manager. It lets you search for, install, upgrade and remove applications from the command prompt or PowerShell, using community and Microsoft sources. Think of it as one updater for many apps.

Step 1: Check winget is installed

On current versions of Windows 10 and 11, winget comes with the App Installer package from the Microsoft Store. Open Terminal or PowerShell and run:

winget --version

If you get a version number back, you’re good to go. If not, install or update App Installer from the Microsoft Store and try again.

Step 2: See what needs updating

Before changing anything, have a look. Running upgrade on its own lists every app with an update available, along with the installed and available versions:

winget upgrade

I always do this first. It’s a quick health check of a machine, and often a surprising one.

Step 3: Update everything

To upgrade every app that has an update available:

winget upgrade --all

For a hands-off run, add the switches that suppress prompts:

winget upgrade --all --silent --accept-package-agreements --accept-source-agreements

Here’s what those do:

  • --silent runs installers without showing their UI
  • --accept-package-agreements accepts app licence agreements so you aren’t prompted
  • --accept-source-agreements accepts the source agreements so you aren’t prompted
  • --include-unknown also upgrades apps whose current version winget can’t determine

That last one is worth knowing. Some apps don’t report a version, so winget skips them during --all unless you add --include-unknown.

Step 4: Update just one app

Sometimes you only want to update a single app. Grab its ID from the winget upgrade list and target it directly:

winget upgrade --id Microsoft.PowerToys

Step 5: Run it elevated

Many apps are installed for all users, so their installers need administrator rights. Run Terminal as administrator before running winget upgrade --all, otherwise you’ll be hit with UAC prompts or failures for machine-wide apps.

Step 6: Pin apps you don’t want touched

Not everything should update automatically. A line-of-business app might need a specific version, or a tool may need testing first. Winget handles this with pins:

winget pin add --id Microsoft.PowerToys

A standard pin excludes the app from winget upgrade --all but still lets you upgrade it deliberately. Add --blocking to stop upgrades altogether until the pin is removed, or --version with a wildcard, such as 0.70.*, to keep it within a version range. Use winget pin list to see current pins and winget pin remove to clear one.

Step 7: Schedule it

Running this by hand is fine for your own machine, but the real win is automation. On a single device, create a Task Scheduler task that runs the silent command with highest privileges on a regular schedule.

For managed fleets, I’d look at Intune instead. Intune remediations can run a detection script to check for available upgrades and a remediation script to apply them. One caution: winget is installed per user, so running it under the SYSTEM account needs extra care with how you call it. Test thoroughly on a pilot group before rolling out widely.

The MSP angle

For MSPs, winget is a simple way to close a common security gap across every client device. Third-party apps are often the forgotten part of patching, sitting outside Windows Update entirely. A standard winget routine, deployed through Intune and backed by pins for anything sensitive, gives you consistency without buying another tool.

It also makes a nice reporting story. A regular winget upgrade list shows clients exactly what was out of date and what you fixed. And if you’re using Copilot or other AI tools to help write and review scripts, winget commands are a great place to start because the syntax is clean and well documented.

Start with your own machine today. Run winget upgrade, see what turns up, and I suspect you’ll be convinced.

How to set up voice in Grok Bot, and what is limited from Australia

Gouache painting of an Australian coastal dusk seen from a wooden window ledge, with concentric ripples on the water

Voice in Grok Bot is more than a microphone button. Officially, it covers dictation into the composer, live voice chat with a Bot, voice memos a Bot can send you, phone calls a Bot can place, and, on some plans, a Bot joining a Google Meet, Zoom or Microsoft Teams meeting.

I have gone through the official Grok Bot documentation, the changelog, the Grok Bot terms, and the actual Settings paths in the app, and I have checked the Australian limitations that are actually published. This is a setup guide, not a sales pitch, and it is not legal advice. Where something is not documented, I have said so rather than guessed.

I have written about claiming a Grok Bot email address carefully. Voice needs the same caution, because a spoken conversation and a recorded phone call are easier to treat casually than a draft sitting in a mailbox.

First, tell the two voice features apart

Dictation and voice chat are easy to mix up.

Dictation, which the desktop docs also call Start voice input, turns your speech into text in the composer. You read it, edit it, and send it like any other message. The Bot replies in text.

A voice chat is a live spoken conversation with one Bot. The Bot answers out loud and keeps listening until you hang up. It works in the desktop app and the phone app. It is not the same thing as a Bot placing a telephone call to a business, and it is not a voice memo.

A voice memo is a spoken reply a Bot can leave in the conversation. You play it, pause it, and expand it to read the transcript.

Get that split clear before you start clicking, because the buttons sit next to each other and do different jobs.

Set the microphone on the desktop

On the desktop app, open Settings from the account menu at the bottom left of the sidebar, or press Cmd+, on a Mac or Ctrl+, on Windows or Linux. The official Settings map also lists a command palette item, Open settings. There is no gear icon in the sidebar for this.

In Settings, stay on General. Under System, Microphone lets you pick System Default or a specific device. That is the microphone Grok Bot listens to when you talk to it.

If the app says microphone access was denied, allow Grok Bot to use the microphone in your computer’s system settings, then try again. If it says no microphone was found, connect one and try again. Those messages, and this Settings path, are in the official docs.

The phone app uses the device microphone and asks for access when you start talking. Official mobile docs do not list a separate microphone picker like the desktop Settings row.

Dictate a message

On desktop, focus the composer, then choose Start voice input, or press Cmd+D or Ctrl+D. You can also hold those keys while you talk.

On iPhone and Android, use Start dictation in the composer. Official docs say to stop dictation before you start a voice chat.

The result is text. Edit it before you send it. That matters in an MSP or an SMB, where a dictated client update can easily include the wrong name or a number you would not want to send.

On iPhone, Grok Bot also adds Shortcuts you can run from Siri, Spotlight or the Shortcuts app, including Start Dictation. Official mobile docs say Start Dictation lets you dictate a message to a Bot without opening the app, as long as the iPhone is not locked, and a Live Activity can show progress, with buttons to cancel or send.

Start a voice chat

  1. Open the chat with the Bot you want to talk to, and leave the composer empty.
  2. Choose Start voice chat, the waveform button in the composer. Official docs are explicit: this button shows only when the composer is empty, there is no keyboard shortcut for it, and if the composer is empty and you still do not see it, update Grok Bot.
  3. Allow microphone access if your computer or phone asks.

The call shows Connecting… on desktop or Calling… on the phone, then the Bot starts talking. While you are on the line, the app shows Voice chat, and on desktop the sidebar can show Voice chat in progress.

During a call you can Mute or Unmute your microphone, Hang up, or choose Show transcript to read along. In a call with your own Bot, Show settings changes the Voice, the Speed and the Language. Auto-detect picks the language from what you say. Official docs do not publish a full list of voice names, speeds, or whether Australian English is a distinct spoken option, so I am not going to invent one. The app language setting, under Settings then General then Language on desktop, or Language in the phone Settings, changes menus and messages, and the FAQ says new Bots write to you in that language unless you write to them in another one. Voice chat has its own Language setting. The FAQ also says the desktop and phone apps each have 38 app languages. That is the app UI, not a documented list of spoken accents.

You can open other chats while the call runs. On desktop, choose Return to the voice chat to go back. Only one voice chat runs at a time. Starting another asks End the current voice chat?; choose End and Chat to switch.

Voice chat works with one Bot at a time, not in group chats. Open that Bot’s own chat to start a call. On desktop you can also voice chat with a teammate’s Team Bot from your own chat with it.

If the connection drops, Grok Bot tries to reconnect on its own first. If it cannot, the call ends with Voice chat failed, and the notice may say Connection lost, No connection, or The call ended unexpectedly. Choose Dismiss, check your internet connection, and start the voice chat again.

On the phone app, version 1.18 and later, a voice chat ends when a phone call, FaceTime, or another app takes over the audio. That is the same as hanging up, and the voice chat does not resume on its own. Short interruptions on Android, such as a navigation prompt, only pause the conversation.

When the call ends, the conversation includes a Voice chat card with the call’s length. Open it to read the full transcript. If the call left work to do, the Bot may follow up in the chat. Grok Bot may also ask How was the call?; you can choose Good or Bad.

On an iPhone with an Action Button, official mobile docs say you can press it to talk with a Bot. In the iPhone’s Settings, choose Action Button, swipe to Shortcut, and choose Grok Bot, then Start Voice Chat. If you do not pick a Bot for the shortcut, Grok Bot asks which one. Press it again while you are on the line to hang up.

Play a voice memo

When a Bot replies with a voice memo, choose Play voice memo to listen, Pause voice memo to stop, and expand the memo to read the transcript. Official docs describe playback in the conversation. They do not document a separate settings page for memo voices.

Have a Bot place a phone call: US only

This is the main Australian limitation, and it is stated clearly in the official product docs: phone calls are available in the US only, from the Grok Bot desktop and phone apps.

A Bot can call a business for you, for example to book a table or ask about an order, and then tell you how it went. The first time, the Bot asks you to agree to the calling terms, including that you will only call US businesses and people who have consented to hear from you. Choose Accept or Decline. Before each call, the Bot shows who it will call; choose Call or Cancel.

While the call runs, its card shows the status and a live transcript. You can End call. When Take over shows, you can join the call yourself; the card says Connecting you… and then Transferred to you. If the other side asks something the Bot cannot answer, a card shows the question and how long you have to respond. Type in Your answer and choose Send, or choose Skip. If the Bot wants to give the call more details while it is live, it asks you first.

When the call is over, the card says Ended, with the length. Open the call card to read the transcript and play the recording. On desktop, the Call actions menu also has Copy transcript, Export transcript, and Download recording. Official docs say phone calls a Bot makes are not used to train the models, whatever your privacy settings.

The Grok Bot terms add points that matter even if you are not in the United States. Calls are treated as agentic actions. You are the caller of record and are responsible for them, including applicable telemarketing, caller ID and call-recording laws. You may only call people who have agreed to hear from you. You may not use calls for marketing or mass calls, fraud, harassment, impersonation, emergency services, or any purpose prohibited by the acceptable use policy. Calls identify themselves as made by a virtual assistant on your behalf and may be recorded, and you may not alter or disable those disclosures. Calls are not a telephone service and cannot be used to reach emergency services. Temporary numbers, if assigned, remain the provider’s property and may be reclaimed.

From Australia, the practical consequence is simple. Official product documentation does not currently offer Bot-placed phone calls outside the US. Do not plan a customer process around it. Voice chat with your own Bot, dictation, voice memos, and, on eligible plans, meeting joins are the voice features that are documented without that US-only limit.

Add a Bot to a meeting

A Bot can join a Google Meet, Zoom or Microsoft Teams call, listen, take notes, answer questions in the meeting chat, and send a summary and action items when the call ends. Official docs say meetings are available on Team, Enterprise and Ultra plans. Enterprise admins can turn Meetings on or off for everyone’s Bots under Bot Capabilities on the Grok Bot page of the team dashboard.

To add a Bot:

  1. Paste the Google Meet, Zoom or Microsoft Teams link into your chat with the Bot, and ask it to join and take notes.
  2. Approve the card when the Bot asks.
  3. When the meeting starts, the host admits the Bot. It joins as the Bot name, plus your first name’s Bot, transcribing, or as a Team Bot, transcribing, depending on the type.

A Bot that follows your calendar can also join scheduled meetings on its own. You can ask for a routine that joins meetings; official docs say a Bot a routine sends takes notes but does not answer in the meeting chat.

Open the Bot’s details to manage Upcoming meetings. Meeting actions include Disable Interactivity, which keeps the Bot listening and taking notes without answering, Cancel, and Quit. Address the Bot by name in the meeting chat to talk to it there. Official docs say it will not share your credentials in a meeting.

I have not found an official geographic restriction on meeting joins the way there is for phone calls. If something is not written down, I am not going to invent a country list. What I would still do, from Australia, is treat a transcribing Bot as a recording-like activity and tell the other people in the meeting, because Australian rules on recording private conversations are not identical in every state and territory.

Australian legal points, kept general

This is general information, not legal advice. You should check the official sources that apply to you, and get advice if the use case is a customer or marketing call.

For telemarketing, the ACMA explains the Do Not Call Register and the rules around unsolicited telemarketing calls. After a number has been on the register for 30 days, telemarketers can only call if they have consent or an exemption. ACMA also sets out calling-time and identification rules for telemarketers, including that they must say who they are and why they are calling, and end the call if the person asks them to stop. The Do Not Call Register Act 2006 is the Commonwealth legislation. The Grok Bot terms already ban marketing and mass calls and require consent, which sits in the same direction, but the product feature itself is still documented as US only.

The Spam Act, which ACMA also administers, is mainly about commercial electronic messages such as email and SMS, not the same rules as the Do Not Call Register.

Official Grok Bot docs and terms are clear that Bot-placed calls may be recorded, that those disclosures must stay in place, and that a recording and transcript can be played afterwards. Meeting joins also produce transcripts and summaries. In Australia, recording or listening to private conversations is regulated in part under state and territory surveillance devices laws, and those laws are not all the same. The Commonwealth Telecommunications (Interception and Access) Act 1979 also deals with intercepting communications as they pass over a telecommunications network. If you are going to keep a recording or a transcript, check the official law that applies to the people on the call, and tell them what is happening.

Official Grok Bot documentation does not, that I can find, publish a separate Australia availability page for voice chat, dictation or voice memos, or a documented Australian English voice. Those features are described for the desktop and phone apps generally. Phone calling is the feature with an explicit US-only limit. Emergency use is prohibited in the terms, wherever you are; do not treat a Bot as a way to reach emergency services.

What to be aware of, especially in an MSP or SMB

Voice chat is a conversation with a Bot that can already reach your connected apps, files and, if you allow it, actions that need approval. I have also written about Grok Bot Privacy Mode, and the same instinct applies: know what the Bot can see before you start talking.

Do not put customer credentials, one-time codes, or card details into a voice chat just because it is quicker than typing. Do not ask a Bot to place a customer telephone call from Australia and assume it will work. If a teammate in the United States can use phone calling, they still need consent, and they are the caller of record under the terms.

For meetings, tell the host and the attendees that a Bot will join to transcribe. On Enterprise teams, confirm that Meetings is actually turned on before you promise it in a service description. Voice chat does not work in Grok Bot group chats, so do not plan a multi-Bot spoken stand-up around a feature the docs say is one-to-one.

On a phone, remember that an incoming mobile call can end the voice chat on version 1.18 and later. If you are walking between client sites, that matters.

And keep the approval habit. A spoken “yes, send it” is still a decision. The Bot may follow up in the chat after a voice call with work still to do. Read it before anything goes to a customer.

The useful setup, for me, is this. Turn on the right microphone. Learn dictation for quick text, and voice chat for a live conversation. Play memos when a Bot sends them. Use meeting joins on an eligible plan, with people told that a transcript is being made. Leave US-only phone calling out of any Australian operating procedure until official documentation says otherwise.

Sources

I ran MAI Image 2.7 through my usual espresso machine test

Bauhaus-inspired abstract composition of red, blue, yellow and black circles, squares and triangles on an off-white field

Microsoft introduced MAI Image 2.7 and MAI Image 2.7 Flash on 17 November 2026. I added both to the same image comparison I have been running for months: a technical cutaway illustration of a precision espresso coffee machine.

That test lives on my image comparison page. I have written about earlier rounds, including when I put the gallery on one page and when MAI Image 2.6 arrived. The page itself does not rank the models or give a score. It shows the results side by side, at the same display scale, with the date, dimensions and file details for each one. What follows is what those images actually show, plus what Microsoft has published about the new models, and what I think that means if you are choosing an image model for business work.

What Microsoft says MAI Image 2.7 is

The official product name, on Microsoft AI, is MAI Image 2.7, with a faster variant called MAI Image 2.7 Flash. I am using that capitalisation rather than the more compact “mai-image2.7” you will sometimes see in filenames.

Microsoft’s 17 November announcement, and the November 2026 model card, describe a diffusion-based model for text-to-image generation and controllable image-to-image editing. The card lists 20 billion non-embedding parameters, a 32,000-token context window, and a maximum output of 4,194,304 pixels, equivalent to 2,048 by 2,048, with either side allowed to exceed 2,048 so long as the total stays inside that limit. Training is listed as April to November 2026, and the release date on the card is 17 November 2026. An earlier Microsoft AI post, on 27 October, described a preview of the editing model, with text-to-image generation still to come. The November announcement is the one that introduces both 2.7 and 2.7 Flash together, along with Canvas, a new workspace in MAI Labs powered by the Flash model.

On availability, the announcement and the model card say you can try both models in MAI Labs, including Canvas, and that they are in public preview through Microsoft Foundry, as well as through partners including fal, Genspark, OpenRouter and Vercel. Microsoft also says the MAI Image family has been the default model family powering Bing Image Creator since the Build event in June. That is a claim about the family, not a statement I can verify that Microsoft 365 Copilot Chat or Copilot Create has already switched to 2.7. The Copilot results on my comparison page are dated 5 September 2026, before this release, so they should be read as earlier Copilot surfaces, not as 2.7.

On price, the 17 November announcement says that in public preview on Microsoft Foundry, MAI Image 2.7 costs about US$35 per 1,000 images and Flash about US$10 per 1,000 images. I am quoting those approximate figures as published. I did not find a more precise public SKU on the Azure Foundry pricing page I checked, and the Microsoft Learn article on deploying MAI image models in Foundry, when I looked on 18 November 2026, still listed models up to MAI-Image-2.6, not 2.7. Foundry preview terms also say a preview is provided without a service-level agreement and is not recommended for production workloads.

Microsoft has published its own leaderboard claims as well. As of 16 November 2026, it says MAI Image 2.7 ranks first on Artificial Analysis image editing, with a score of 1,215 Elo from 5,478 votes, four Elo ahead of GPT Image 2.6 Sunburst (max), and that it is a top-two lab on Arena for image generation and editing. Those are Microsoft’s published figures, not measurements from my espresso machine test.

What the comparison page actually shows

The gallery is a single prompt set: “Technical cutaway illustration of a precision espresso coffee machine.” The 2.7 and 2.7 Flash results were created on 18 November 2026. The other ten results were created between 4 July and 11 September 2026. Resolutions are not identical. The new flagship came out at 1,536 by 1,536 pixels. Others range from 730 by 720 up to 1,254 by 1,254. The page displays them at the same scale, but it is not a lab test with every variable locked down. It is a consistent brief, run through the models and surfaces I actually use.

The label quality is the first thing I look at, because a technical drawing is useless if you cannot read it.

MAI Image 2.5 Flash, from 4 July, still looks like a cutaway at a glance, but the callouts collapse into nonsense: garbled part names, broken dimensions, text you would never put in front of a customer. MAI Image 2.5, from 24 July, is better as a drawing and still weaker as a document. The title on that one even says “EXPRESSO.” By MAI Image 2.6 in August, and 2.6 Flash in September, the typography has settled down. Those two already produce dense, readable technical posters, with numbered callouts, materials lists, dimensions and secondary diagrams. That jump, from 2.5 Flash to 2.6, is larger than the jump from 2.6 to 2.7.

The new 2.7 result is the most crowded “manual page” in the set. It is a stainless machine in cutaway, with a copper boiler, colour-coded pipework, a 93°C display, cups on the warming tray, a brew-path sketch, a front view, a materials key and dimension lines. The text is readable. Flash, at 1,024 pixels, is in the same family: a similar poster layout, slightly less packed, and it chose a hopper-equipped machine rather than the two cups on top. Neither result is a radical break from 2.6. Both look like a firming up of the same idea, with the flagship carrying more detail at a higher resolution.

MAI Image 2.7 result: a technical cutaway illustration of a stainless espresso machine with labelled parts, dimensions and diagrams
MAI Image 2.7 result, 18 November 2026, from my image comparison page.
MAI Image 2.7 Flash result: a technical cutaway illustration of a hopper-equipped espresso machine with labelled parts and diagrams
MAI Image 2.7 Flash result, 18 November 2026, from the same comparison page.

The non-Microsoft results are a reminder not to treat this as a one-horse race. The page’s Copilot Create and Copilot Chat images, both from 5 September, are already dense, usable technical posters, especially Copilot Create, with numbered callouts, a materials table and cross-sections. The PowerPoint GPT Image 2 result is very much an engineering drawing, complete with a bill of materials, though it also invents a drawing date of 18 May 2024 and a designer name. The result labelled Nano-Bananna2 is a clean product cutaway with mostly readable labels and a couple of typographic slips. Grok, from 11 September, is also a complete technical poster, mostly readable, in a taller portrait frame, with a Grok watermark and at least one typo in a heading. Claude Sonnet 5 is the outlier. The labels and boxes are tidy, but the machine itself is a grey geometric block, not a realistic espresso machine. You get the structure of a teardown and almost none of the object.

I am not going to invent a winner the page does not declare. On this one brief, the new MAI Image 2.7 models sit with the better recent results, not out on their own. The practical improvement over 2.6 is real but incremental. The improvement over mid-year 2.5 Flash is obvious. And a couple of other tools, including Copilot Create from September, already produce work you could use in a first draft of a technical figure.

What I would tell a business

If you are an MSP or an SMB picking an image model, the question is not “which one won a leaderboard.” It is where the work happens, who can use it, and whether the output is good enough for the job.

For most Microsoft 365 tenants, that job still starts in Copilot. Picture a marketing lead in PowerPoint who needs a cutaway, a product-style hero, or a simple diagram for a slide, or someone in Word or Teams who wants a visual without opening a separate design tool. I have been testing those Copilot surfaces with this same prompt for months. They are already good enough, on this brief, that I would not tell a customer to leave Microsoft 365 just to get a slightly sharper espresso machine drawing. I also would not tell them that Copilot is already running 2.7 until Microsoft says so in product.

If you need the new models themselves, the official path today is MAI Labs, including Canvas, or public preview in Microsoft Foundry, with the pricing Microsoft has published and the usual preview caveats. Foundry is the more natural fit for a controlled, identity-backed deployment. Bing Image Creator is the consumer-facing place Microsoft says already uses the MAI Image family. Those are different doors, with different governance.

I would also be careful with anything that has to be right. These models can now render a lot of text, but they still invent specifications, dates and part names. A technical figure for a customer proposal still needs a human to check the words and the numbers. The 2.5 Flash result is a useful warning from only a few months ago: a drawing can look finished and still be unusable.

My working view, from this test and from the official details, is simple. MAI Image 2.7 is a credible, cheaper-to-run option in Microsoft’s own image family, with a faster Flash variant for volume work. On my espresso machine brief, it belongs in the leading group, alongside recent 2.6 and Copilot Create results. It does not, by itself, change the advice I would give most businesses: use the image tool that already sits in the workflow you have, check the output, and only add another model when you have a job the current one cannot do.

Sources

AI Doesn’t Take Your Job, It Extends Your Wingspan

Curious woman working on an electronics project at a workbench in teal and amber light

Every week I hear the same fear. AI is coming for our jobs. I understand why, but I think it misses what’s really happening. AI doesn’t take your job. It extends your wingspan.

Think of wingspan as your reach. It’s how much ground you can cover, how many roles you can step into and how many skills you can put to work. For most of us, that reach has always been limited by time, training and what we happened to learn along the way. AI stretches it further than we’ve ever been able to stretch it on our own.

Your reach used to stop at your training

Doing something new used to mean years of practice or paying someone who already had the skill. Want to write well, code, design, analyse data or run a project? You either invested heavily or stayed in your lane.

AI widens that lane. Copilot can help you draft a clear proposal in Word, build a formula or pivot in Excel, turn rough notes into a PowerPoint deck or tame a messy Outlook inbox. You don’t need to be a writer, an analyst or a designer to get a solid first result. Your wingspan now reaches into territory that was out of range.

That doesn’t make expertise worthless. Experts extend their wingspan too. It means the distance between what you can do and what you’d like to do has shrunk for everyone.

Stretching my own wings

I’ve felt this myself. Lately I’ve been building a robot arm that plays tic-tac-toe, with AI helping me write the code, and I even published a worked guide to how minimax plays perfect tic-tac-toe on CIAOPS Labs. That project was well outside my reach not long ago.

Scripts are the same. I now write PowerShell to monitor Microsoft 365 tenants, with AI doing much of the heavy lifting. I described how that kind of assistant changed my day in Finally, AI That Just Gets Things Done. I still have to understand the result, test it and own it, but my range is far wider than it was.

Curiosity decides how far you fly

If AI gives everyone a longer wingspan, what separates people? Whether they actually spread their wings. The people who thrive ask what else is now within reach, then go and try it.

The traits that matter most:

  • Curiosity to explore tasks beyond your usual role
  • Willingness to learn enough to judge the output
  • Persistence when the first attempt falls flat
  • Honesty about when you still need an expert

Those who assume a task isn’t for them will fall behind. Not because AI replaced them, but because someone curious flew into that space first.

What a wider wingspan means for MSPs

For MSPs, this is a real shift. Picture a technician who’s never written marketing copy producing a solid client newsletter with Copilot. Or a service desk lead building a Power Automate flow without being a developer. Or an owner analysing profitability in Excel without hiring an analyst. Each person covers more ground, so the whole team covers more ground.

It’s also a message worth taking to clients. Their staff can reach much further than they think, as long as they’re encouraged, trained and given safe tools inside Microsoft 365. Helping them stretch, with the right guardrails and a bit of patience, is valuable work that builds trust.

So stop asking whether AI will take your job. Ask how far your wingspan now reaches. Then spread your wings and go and use it.

Your Grok Bot can have its own email address. Claim it carefully.

Soft 3D still life of a pale blue envelope with a gold clasp and coral seal on a white background

I claimed a Grok Bot email address in October 2026, and I have used it since then for newsletter and service sign-ups. It is useful, and easy to misunderstand if you treat it like a second Outlook mailbox.

Each account can claim one unique address at mail.grokbot.com. Plus addressing works too, so you can hand a service a tagged alias without claiming a second inbox. That is what I want MSPs and small businesses to understand: how to turn it on, how the aliases work, and what you should not use it for.

What you actually get

The official documentation is clear enough. You can claim one address, such as yourname@mail.grokbot.com. Your Bots can then receive, read, search and send email from it. With that address, a Bot can sign up for services and pick up a verification code or link with your approval, collect receipts, newsletters and reports, draft email for you, forward a message from its inbox, and run a routine when mail arrives.

A few details matter immediately. You get one address, and you cannot rename or delete it. Addresses are never reissued, even if the account that claimed one is later deleted. The address belongs to you, not to a single Bot. All of your Bots can use it in your own chats and in routines you set up. It is not used in Slack threads, or in chats where someone else is talking to the Bot, and a Team Bot does not get a shared team address.

There is no inbox view in the apps, and you do not get new-mail notifications. You ask a Bot, for example, “What arrived in your inbox today?” Mail from the last minute may not show up in a search yet. The official docs also make a useful distinction: the Email app gives your Bots their own address, rather than connecting a mailbox you already have. This is not a replacement for the Outlook mailbox you use for Microsoft 365, clients, or account recovery.

How to claim the address

The steps below come from the official “Give your Bots an email address” guidance on docs.x.ai.

If you use Grok Bot through a Cursor team, stop here first. Agent email is off by default. A team admin has to turn on Agent Email under Bot Capabilities on the Grok Bot page of the Cursor dashboard before anyone can claim an address.

You then have two official ways to claim it.

The simplest is to ask a Bot, in chat, something like “Get yourself an email address.” The Bot asks what name you want, checks that the name is free, and shows an approval card. Nothing is claimed until you approve that card.

The other official path is the Email app. Open Connect apps, choose Email, type a name in Choose a name under Email address, and choose Create address. On iPhone and Android, the same docs say to open Settings, then Connect apps, then Email. After you claim it, the app shows your address with a button to copy it.

Choose the name carefully. Official rules allow lowercase letters, digits, dots, hyphens and underscores, starting and ending with a letter or digit, at most 64 characters. Reserved words such as support, admin, billing, security, help, info, team, cursor, grok and xai are not allowed. If the name is taken, retrying it will not work, because addresses are never reissued. Pick something you are happy to give to a service.

If claiming fails, match the official message. “Agent email is not enabled for this account” means it is not available on your account yet. A message about your team admin having turned it off means you need that dashboard switch. “You can have one agent email address” means you already have one; ask the Bot what it is, or open the Email app.

Plus addressing is supported

This is the part a lot of people will actually use. The official documentation confirms that the address takes plus aliases. Mail to yourname+receipts@mail.grokbot.com lands in the same inbox as yourname@mail.grokbot.com, so you can give each service its own alias without claiming another address. A Bot can also send from an alias. A routine that watches an alias runs only for mail sent to that alias, while a routine on the plain address runs for all of it. The changelog on 14 October 2026 recorded the same behaviour.

In practice, I can sign up to a newsletter as yourname+newsletters@mail.grokbot.com, give a vendor yourname+billing@mail.grokbot.com, and keep the base address for everything else. I still have one inbox. The tag is how I sort the mail, and how I point a routine at one kind of message.

The official docs add an important caveat. An alias is a label, not a lock. Anyone can write to it. If a routine should act only for certain senders, keep a sender filter on it. I would also treat the alias as organisational, not secret. Anyone who sees yourname+newsletters@ can guess the base address.

Incoming mail does not wake a Bot on its own

This is the misunderstanding I want to kill early. New mail does not start a chat or wake a Bot by itself. To act on it, you set up a routine that watches for mail from anyone, from specific addresses, or from a whole domain such as *@example.com. By default, that routine only runs for senders that pass standard email authentication checks, and routines cannot filter by subject.

I have written before about how Grok Bot can watch Microsoft 365 status. The same idea applies here. The address can sit quietly and collect mail. The routine is what makes it useful. If you have no routine, the mail is still received and kept. You just have to ask a Bot to look.

What to be aware of

First, privacy and who can read it. The address is yours, and all of your Bots can use it in your own chats and routines. That is useful if you want any of your assistants to search the inbox, and a reminder that this is not a private mailbox for one specialist Bot. I would still be careful about what you allow to land there, in the same spirit as I wrote in what MSPs should understand about Grok Bot security and customer Microsoft 365 data. This is a good place for newsletters and service notices, and a poor place for customer data you would not want sitting in a shared assistant inbox.

Second, use it for sign-ups, not as your important identity mailbox. The product is designed for a Bot to sign up for services with its own address and, with your approval, pick up a verification code or link. I would still keep multi-factor authentication and account recovery on your real Outlook or Gmail mailbox: the one you watch, and the one that is not shared across every Bot on the account. The official docs do not ban the Bot address for one-time codes; they even note that a Bot can read a code from its own inbox. I am simply saying I would not make yourname@mail.grokbot.com the recovery address for a Microsoft 365 admin account, a bank, or a domain registrar.

Third, outgoing mail still needs approval. When you ask a Bot in chat to send an email, it goes out once Auto Review allows it, and you see an approval card if Auto Review needs you. Email from a routine, or from any other turn you did not start with that request, waits as a draft until you press Send. There is no option for unattended sending. Instructions inside an email never count as your permission to send or act. Do not expect a routine to quietly reply on your behalf.

Fourth, anyone can send mail to the address. Mail that fails the spam or virus scan is kept without its body or attachments, and it never starts a routine. That is useful, but it is not the same as a well managed Microsoft 365 inbox. Be sceptical of unexpected messages, and do not assume a plus alias hides you.

Fifth, if you later delete your Grok Bot account, your mail and attachments are deleted and the address is retired. On a team, if an admin turns Agent Email off later, Bots lose their email tools and email routines stop, but existing addresses still receive and keep mail, and members keep their addresses.

The practical verdict

I am glad this exists. A unique address for newsletters, a vendor portal, or a service I want a Bot to watch is genuinely useful, and plus aliases make that tidier. The mistake is treating it like a second primary mailbox.

Claim the name carefully, because you only get one. Use plus addressing to keep sign-ups organised. Put a routine on the aliases you actually want acted on. Keep MFA and recovery on the Outlook or Gmail address you already trust. And remember that mail arriving at mail.grokbot.com will sit there quietly until you, or a routine you set up, ask a Bot to look.

This is general information about a product feature, and official guidance can change. Check the current documentation before you rely on a particular behaviour, and review anything a Bot drafts before you send it.

Sources