How to Use Grok Bot to Monitor MSP News and Security Updates

Two professionals reviewing a morning news and security brief on a laptop and monitor

Most MSP owners I talk to already “keep an eye on the news”. In practice that is newsletters, a few vendor blogs, and whatever appears before the first ticket of the day. The useful items — an exploited vulnerability, an ACSC alert, a Microsoft 365 change that will hit your SMB tenants — sit in the same pile as marketing.

I wanted a brief that arrives in the morning, is filtered for an Australian MSP, cites its sources, and is sitting in chat so I can ask a follow-up. I run a dedicated News bot for this: a morning brief on Microsoft 365, Copilot and security, with an SMB lens, from official and reputable sources only. This post is how to set that up, with the chat prompts I would use, and a fair look at where this beats RSS, alerts or a generic chatbot — and where it does not.

Why MSPs need a monitoring system

MSPs sit in the middle of three streams that do not wait for a quiet week: Microsoft 365 and Copilot changes, security advisories, and channel news that affects how you explain those changes to clients.

If you miss a critical advisory, you may need to tell a client the same day. If you only read US sources, you can miss Australian Cyber Security Centre (ACSC) guidance your local customers will ask about. Manual checking does not scale, especially after a long weekend.

A monitoring system is not another inbox. It is a short, repeatable brief with a clear lens, source links, and a way to turn one item into a client note when it matters.

Step-by-step configuration

Everything below is done in chat, except for two verified places in the app: the per-agent info pane, and Settings for timezone. I am not going to invent extra menus.

1. Pick a bot and give it a clear role

I use a dedicated News bot so the brief is not mixed with other work. You can do the same, or add the routines to a bot you already use. A bot can have its own name, title and description, and it can remember your preferences.

To set the persona in the app, click the agent’s name in the chat header (or use Cmd+Shift+I) to open the per-agent info pane. The gear beside the X opens the per-agent Settings for avatar, name, title and description.

You can also do it in chat:

Set this bot’s name to News and set the description to: You prepare a morning brief of Microsoft 365, Copilot, MSP industry and security news for an Australian MSP audience. Use official and reputable sources only. Filter for SMB and MSP impact. Always include source links. Skip rumour and marketing fluff.

2. Choose your sources

Be specific about where the bot should look. These are public pages I have checked. Microsoft 365 Message Center is not on the list: it lives in the Microsoft 365 admin centre and needs tenant access, so it is not a public source for an unattended routine. For product changes without a tenant sign-in, use the public Microsoft 365 roadmap, which Microsoft now presents as the AI at Work roadmap.

For news and security monitoring, use these sources when they are relevant. Prefer official pages over secondary write-ups, and always cite the URL:
- Microsoft 365 roadmap: https://www.microsoft.com/microsoft-365/roadmap
- Microsoft Security Response Center blog: https://msrc.microsoft.com/blog/
- Microsoft Security Update Guide: https://msrc.microsoft.com/update-guide
- CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- ACSC alerts and advisories: https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories
- Microsoft Tech Community: https://techcommunity.microsoft.com/
- Channel Dive: https://www.channeldive.com/
- CRN: https://www.crn.com/
- ChannelE2E: https://www.channele2e.com/
- MSSP Alert: https://www.msspalert.com/
- ConnectWise Trust Center: https://www.connectwise.com/company/trust
- Kaseya Information Security: https://www.kaseya.com/trust-center/information-security/

Add or remove vendor pages to match the tools you actually deploy.

Grok Bot can search and fetch public pages on its own. If you want official Microsoft documentation as a follow-up, add the Microsoft Learn connector — I walked through that in How to Set Up MCP Connectors in Grok Bot with Microsoft Learn. Optional extras are Outlook, Gmail or Teams for later drafting, and public reads on X. Add those in chat, for example: “Add the Microsoft Learn MCP server at https://learn.microsoft.com/api/mcp.”

3. Set the filters

A source list without filters still produces noise. Save the lens in the same chat:

Apply these filters to every brief. MSP and SMB lens — explain why an item matters to a managed service provider or a small business tenant. Severity first — put actively exploited or critical security items at the top. Australian relevance when it exists, including ACSC guidance and Microsoft 365 changes that affect Australian tenants. Official or reputable sources only. Every item needs a source link. Ignore vendor marketing, partner-program noise and generic consumer tech news.

4. Create two routines

A routine in Grok Bot is a saved prompt plus a trigger. The useful trigger here is a schedule in your local time. It runs while you are away, and the result is posted to this bot’s chat unless you name another destination. When you ask the bot to create a routine, you may see a confirmation card before it is saved.

You can review saved routines in the same per-agent info pane, under the computer preview. Check your timezone under Settings, in the General tab, opened from the sidebar account button at the bottom-left, or with Cmd+,. Routines usually start within a few minutes either side of the time you set. If the run must start right on the minute, say “exactly” or “sharp”.

Create the news brief first:

Create a routine called Morning MSP news brief. Every weekday at 7:12am Sydney time, check the Microsoft 365 roadmap, Microsoft Tech Community, ACSC alerts, Channel Dive, CRN, ChannelE2E and MSSP Alert for new items since the last run that matter to an Australian MSP. Summarise each item in a few sentences, say why it matters for an MSP or SMB tenant, and include the source link. Official and reputable sources only. If nothing material has changed, say so in this chat and stop. Deliver the brief to me in this chat.

Then a separate security routine, so a quiet news day does not bury a vulnerability:

Create a separate routine called Security alert watch. Every weekday at 8:12am Sydney time, check the CISA Known Exploited Vulnerabilities catalog, the MSRC blog and Security Update Guide, ACSC alerts and advisories, and the ConnectWise Trust Center and Kaseya information security pages for new or updated items. Flag anything that is actively exploited, critical, or affects common MSP tools. Include the official link and a short note on what I should check. If nothing new is relevant, tell me that in this chat and stop. Deliver the result to me in this chat.

Keep both prompts as intent, not a rigid script, so the bot looks up current pages each run.

5. Test it, then tune the schedule

Do not wait until tomorrow to find out the brief is too long or too vague:

Run the Morning MSP news brief once now, as a test. Do not change the schedule.

Read the result the way you would read a junior analyst’s draft. If it buries the important item, missed ACSC, or cited a weak source, say so and ask the bot to tighten the saved prompt.

To change frequency, be direct:

Change the Security alert watch to Monday, Wednesday and Friday at 8:12am Sydney time.
Pause the Morning MSP news brief while I am on leave, then resume it on the following Monday.

Start with a weekday morning cadence. Hourly checks are rarely worth the usage.

I have written before about Grok Bot taking on recurring MSP work in What Happens to MSPs When Grok Bot Can Do the Work?. A news brief is a smaller version of the same idea: the bot does the first pass, and you decide what to do with it.

Example prompts you can copy

Paste these as-is, then tighten them for your stack and clients.

Daily digest

  1. Give me this morning’s MSP news brief using my saved sources and filters. Include why each item matters and the source URL. If nothing material changed, say so.
  2. What has changed since yesterday in Microsoft 365, Copilot and MSP industry news that would affect an Australian SMB tenant? Cite links.

Security and CVE watch

  1. Check the CISA Known Exploited Vulnerabilities catalog for entries added or updated in the last seven days. Flag anything relevant to Microsoft 365, Windows, common MSP remote tools or vendors I named. Include the official CISA link.
  2. Check the MSRC blog, the Security Update Guide and ACSC alerts and advisories for anything new today. Summarise only what an Australian MSP should act on, with links.
  3. Urgent only: if there is a new actively exploited or critical advisory in my security sources that affects tools I deploy, summarise it with the official link and what I should check. If there is nothing in that category, reply with one line and stop.

Vendor watch

  1. Check the ConnectWise Trust Center and Kaseya information security pages for new advisories or security bulletins. Summarise only what is new, with links.
  2. Look for new security advisories that affect [your RMM, PSA or backup vendor]. Prefer the vendor’s own trust or security page, and cite the URL.

Microsoft 365 changes

  1. Check the public Microsoft 365 roadmap and Microsoft Tech Community for recent Copilot or Microsoft 365 changes that affect Business Premium or other SMB plans. Ignore items that are enterprise-only unless they will still land in a typical customer tenant.
  2. For this Microsoft 365 change, use Microsoft Learn to pull the official guidance and any admin steps. Include the Learn URL. Do not change any tenant.

Weekly client summaries, advisories and drafts

  1. Turn this week’s brief into a one-page client-facing summary I can send on Friday. Plain language, no hype, and a link for every item I include.
  2. Turn this story into a short client advisory. Audience: a 40-seat Australian professional services firm on Microsoft 365 Business Premium. Include what changed, who is affected, what we recommend, and the official source.
  3. Draft a short blog post or LinkedIn update from this item, in my usual practical tone, with the source link. Do not publish it.
  4. From this week’s items, what should I mention in my standing client update, and what can wait? Give a short recommended list with links.

Follow-up

  1. I have a signed-in Outlook connector. Draft an email to my internal ops list from this advisory. Do not send it until I confirm.
  2. What should I verify in a typical SMB Microsoft 365 tenant before I act on this item? Give a checklist, and cite official documentation where you can.

Benefits compared with other options

I still use newsletters, and I still open official pages when something is urgent. The question is what does the first pass for you.

An RSS reader gives you everything a site publishes, in the order it arrives. It will not apply an MSP lens or answer a follow-up. Keyword alerts are useful for a named product, but they match words, not severity or audience, so the noise is high. Newsletters arrive on someone else’s cadence and judgement. That can be excellent, and it is still not tuned to your stack or ready for a “turn this into a client advisory” request. A generic chatbot can summarise a link you paste, but it will not run unattended every weekday unless you set that up. Manual checking works until you are busy.

What Grok Bot does well here is more specific than a vague promise about AI. Scheduled routines run while you are away. The brief can be filtered to an MSP and SMB lens, including Australian relevance. You can insist on source links. One run can combine official pages, trade press and, if you have added them, connectors such as Microsoft Learn. The bot can remember your preferences. The result lands in chat, where you can ask a follow-up, request a client advisory, or draft a message for Outlook or Teams.

Limits and tips

This is a first pass, not a decision. Verify anything you might act on — a patch, a client email or a configuration change — against the official page. Trade press is often useful and sometimes paywalled; if the bot cannot read the full article, it should say so and fall back to the official source.

Ask for links every time. If a brief arrives without URLs, treat it as unverified and tell the bot to retry with citations. Keep the routines lean: two weekday morning runs are enough for most MSPs. Tightening the schedule “just in case” consumes usage.

Do not expect a public routine to read Microsoft 365 Message Center. That is tenant-scoped. Use the public roadmap for unattended product-change watching, and treat Message Center as a separate, signed-in admin task.

Closing

Monitoring fails when it depends on a quiet morning and a good memory. A Grok Bot routine will not replace your judgement, but it will do the first read, apply a consistent filter, and leave the result in chat with the links attached.

Give a news bot a clear role, name your sources and filters, then create two weekday routines — one for industry and Microsoft 365 news, one for security. Test them with a “run it once now” prompt, tighten what you get, and leave the schedule alone until you have a reason to change it. The value is not more information. It is a shorter, sourced brief you can actually use.

How to Set Up MCP Connectors in Grok Bot with Microsoft Learn

Two professionals reviewing documentation on dual monitors in a teal-and-amber lit office

I get asked a lot how Grok Bot stays current on Microsoft 365. The short answer is connectors. In the Grok Bot app, those connectors are MCP servers — Model Context Protocol endpoints that give the bot live tools, not just whatever it remembered during training.

This post is a step-by-step walkthrough using Microsoft’s official Microsoft Learn MCP server. It needs no tenant sign-in, it is free, and it is useful on day one for MSPs and smart businesses.

What MCP is, in plain words

MCP is an open standard for connecting AI agents to external tools and data. Think of it as a USB plug for AI: the host (Grok Bot) talks to a server over a shared protocol, and the server exposes named tools the agent can call while answering you.

Without MCP, an agent guesses from training data or browses the public web and hopes for the best. With MCP, it can search a trusted source, fetch a full page, or pull a code sample, then ground the answer in that content.

Microsoft publishes a remote Learn MCP server at https://learn.microsoft.com/api/mcp. Official overview: Microsoft Learn MCP Server overview. No authentication is required. There is no charge to use it. It exposes public Learn documentation only — not training records, not your tenant, not your profile.

I covered the broader idea of MCP for smaller organisations earlier in Small Business, Big AI Impact: Understanding the AI MCP Server. This post is the Grok Bot how-to.

Why Microsoft Learn makes a good first connector

Three practical reasons:

  1. No sign-in. You do not need Microsoft 365 admin consent to add it. That removes the usual “which account?” friction.
  2. Trusted content. Answers can cite official Learn pages instead of a random blog from 2021.
  3. MSP-shaped tools. The server exposes three tools: search docs, fetch a full article as markdown, and search code samples. That covers Conditional Access, Intune, Graph PowerShell and Copilot licensing.

If you have used Learn inside Copilot Studio before, this is the same family of idea. I walked through that path in Integrating Microsoft Learn Docs with Copilot Studio using MCP. Here we are wiring Learn into Grok Bot itself.

Step-by-step setup in Grok Bot

In Grok Bot, MCP servers show up as connectors. The reliable way to add one is to ask the bot in chat.

1. Open a chat with Grok Bot

Start a normal conversation with the agent that should use the connector.

2. Ask it to add Microsoft Learn

Paste:

Add the Microsoft Learn MCP server at https://learn.microsoft.com/api/mcp

That is enough. Grok Bot can search the connector catalog for a match, or add a remote MCP endpoint by URL when you give it one. Microsoft Learn’s public endpoint needs no auth token and no tenant access.

If the bot shows a connector confirmation card, approve it. For Learn there is nothing to sign in to — Microsoft’s docs state authentication is not required.

3. Wait for confirmation

When it is connected, the bot should tell you Microsoft Learn is available. On my account it appears as a connected HTTP connector with three tools:

  • microsoft_docs_search
  • microsoft_docs_fetch
  • microsoft_code_sample_search

4. Optional: add other connectors the same way

Once Learn works, add signed-in connectors (Outlook, Teams, OneDrive, Azure and so on) by naming the service in chat — for example, “add the Outlook connector” — and completing any sign-in card. Start with Learn so you see the pattern without a login wall.

Checking that it works

Do not assume the connector is live until you ask a real question:

Using Microsoft Learn, summarise how to create a Conditional Access policy that requires MFA for all users. Include the official Learn link.

A healthy reply will pull current Entra admin centre steps (Conditional Access → Policies, report-only first, exclude break-glass accounts), include a learn.microsoft.com URL, and avoid invented clicks.

I ran that live while writing this. It returned Microsoft’s “Require multifactor authentication for all users” guidance, including the authentication strength grant and the report-only recommendation.

Second check — force a code sample:

Using Microsoft Learn, give me a Graph PowerShell sample that lists users with Get-MgUser. Include the Learn source link.

Live result: samples such as Import-Module Microsoft.Graph.Users then Get-MgUser -Top 5, plus Connect-MgGraph -Scopes "User.Read.All" patterns, each with a Learn URL.

If the bot answers from memory with no Learn links, say: “Use the Microsoft Learn connector and cite the page.”

Example prompts you can copy

Paste these as-is, then tighten them for your tenant or client.

Quick answers

  1. Using Microsoft Learn, what are the eligible prerequisite licences for Microsoft 365 Copilot? Summarise the commercial table and link the page.
  2. Using Microsoft Learn, what does an Intune Windows compliance policy check for firewall, BitLocker and Defender? Bullet list with the Learn link.
  3. Using Microsoft Learn, explain the difference between Require multifactor authentication and authentication strength in Conditional Access. Cite the docs.

Live Copilot check: Learn returned the licence options page — Copilot as an add-on on qualifying Microsoft 365 / Office 365 / Business plans, with Copilot Business aimed at organisations up to 300 users — plus the requirements page covering identity and mailbox prerequisites.

Step-by-step admin guides

  1. Using Microsoft Learn, walk me through creating a Conditional Access policy that requires MFA for all users. Start in report-only. Exclude break-glass accounts. List every click path from the Entra admin centre and include the official URL.
  2. Using Microsoft Learn, give me the steps to create a Windows device compliance policy in Intune that requires Secure Boot, BitLocker and Microsoft Defender real-time protection. Include prerequisites and the Learn link.
  3. Using Microsoft Learn, how do I assign Microsoft Copilot licences in the Microsoft 365 admin centre after purchase? Include the assign-licences doc link.

PowerShell and Graph code samples

  1. Using Microsoft Learn code samples, show Graph PowerShell to connect with Connect-MgGraph and list the first 50 users (DisplayName, Id). Include the source page.
  2. Using Microsoft Learn, find a PowerShell sample that disables a user with Get-MgUser and Update-MgUser. Warn me about hybrid implications and cite Learn.
  3. Using Microsoft Learn, search for PowerShell samples to work with Conditional Access policies. Prefer official samples and link them.

Comparing options

  1. Using Microsoft Learn, compare Microsoft Copilot Chat vs Microsoft 365 Copilot licensing requirements for a 40-seat Business Premium tenant. Table format, with source links.
  2. Using Microsoft Learn, compare requiring MFA for all users vs requiring MFA only for directory roles. When would Microsoft recommend each? Cite the policy pages.

Client docs, checklists and routines

  1. Using Microsoft Learn, draft a one-page checklist for an MSP onboarding a new Microsoft 365 client: MFA baseline, Intune compliance for Windows, and Copilot licence prerequisites. Every checklist item must include a Learn URL.
  2. Every Monday, use Microsoft Learn to check whether Conditional Access MFA baseline guidance has changed this week. Summarise any material change and link the pages. Do not change my tenant.
  3. Read the latest ticket in Outlook about Intune compliance failures, then use Microsoft Learn to pull the matching Windows compliance settings and suggest what to verify. Do not change policies until I confirm.

Those last two prompts are where Grok Bot gets useful for MSP work, not just another chatbot. One runs on a weekly schedule, and the other combines tenant evidence from a signed-in connector with public guidance from Learn.

Tips and limits

  • Public docs only. Learn MCP does not see your tenant, users, licences or policies.
  • Content refresh. Microsoft says the knowledge service refreshes incrementally and does a full refresh about once a day, so brand-new articles can lag briefly.
  • Ask for sources. Tell the bot to include Learn URLs. If it cannot cite one, treat the answer as unverified.
  • Verify before you run scripts. Test Graph and PowerShell samples in a lab, check scopes, and confirm the Microsoft Graph PowerShell SDK modules.
  • Report-only first. When Learn returns Conditional Access steps, keep Microsoft’s advice: create in report-only, review impact, then enable.
  • Terms of use. Using the Learn MCP server means you agree to the Microsoft Learn Terms of Use.

Closing

MCP connectors are how Grok Bot stops guessing and starts working from live tools. Microsoft Learn is the easiest first connector because it is public, free and immediately useful for Microsoft 365 work.

Add it with one chat prompt, test it with a Conditional Access or Copilot licensing question, then keep a short list of copy-paste prompts next to your admin checklist. From there you can layer signed-in connectors for mail, calendar, files and tenants — with Learn sitting underneath as the shared source of truth for “what does Microsoft say right now?”

Official starting point: https://learn.microsoft.com/en-us/training/support/mcp

Who Owns the Agent When the Employee Walks Out the Door?

A professional leaving an office tower at dusk, glowing threads trailing from her briefcase back to the building

Here’s a question I don’t think many businesses have asked yet. When you hire your next person, will they be allowed to bring their own agents with them? And when someone leaves, will you let the agents they built in your business walk out the door too?

For years we’ve treated a worker’s toolkit as personal. Their know-how, their shortcuts, their way of working. Agents blur that line badly. An agent can hold skill, but it can also hold memory, data and relationships. That makes the answer far less obvious than it first appears.

The toolkit versus the tenant

I think the cleanest way to start is to split an agent into two parts.

The first part is the pattern. The prompts, the instructions, the way someone has learned to break a job down and hand it to AI. That’s skill. It lives in their head as much as anywhere, and I don’t believe a business can or should claim it. A good tech who has learned how to direct agents well will carry that ability to their next role, the same way they carry their troubleshooting instincts.

The second part is the data. An agent built in Copilot Studio inside your Microsoft 365 tenant, grounded on your SharePoint libraries and connected to your systems, belongs to the tenant. So does what Copilot remembers about how a person works. Microsoft stores Copilot memory in a hidden folder in the user’s Exchange mailbox, inside your tenant, and admins can find it with Purview eDiscovery. That’s a pretty strong hint about where ownership sits.

I wrote recently about the mystery of personal SharePoint skills, which end up stored in a user’s OneDrive. Personal in name, but still sitting in the company’s tenant. Expect a lot more of that.

Memory is where it gets messy

Picture a consultant who has spent two years working with an agent. It knows her clients, their quirks, which contracts are touchy and which projects ran late. Now she moves to a competitor. Should that memory go with her?

My view is no, and not because the business is being greedy. That memory is tangled up with client data, confidentiality obligations and, in many cases, data residency requirements. You can’t neatly pull “how she works” out of “what she knows about our customers”. Until the tools can genuinely separate the two, the memory has to stay.

Treat BYO agents like BYOD

Bringing your own agent in the other direction feels a lot like the early days of bring-your-own-device. The answer then wasn’t a flat yes or no. It was policy, identity and control. Agents need the same treatment. Whose identity does it run under? What data can it reach? Where does what it learns end up? If you can’t answer those, the agent shouldn’t touch your tenant.

What I’d do now

None of this is legal advice, and your lawyer will have views. But there are practical steps any SMB or MSP can take today:

  • Write a simple agent policy covering who can build, bring and share agents.
  • Keep an inventory of every agent, with a named human owner.
  • Add agents and AI memory to your offboarding checklist, right next to mailbox and device handover.
  • Update employment contracts to say what’s portable and what stays.
  • Decide upfront that skills and prompt patterns travel, while data and memory stay put.

The people who learn to work well with agents will be worth more wherever they go. That’s fine. Let them take the skill. Keep the data. Just make sure you’ve written down which is which before someone hands in their notice.

Your Agents Will Outnumber Your People

An IT administrator facing a vast glowing wall of identity nodes multiplying outward from a few people

Most of the businesses I work with know roughly how many user accounts they have. They know who joined last month and, if they’re doing it right, who left. Ask the same people how many AI agents are working in their tenant and the room goes quiet. That silence is the problem I want to talk about, because I think agents are about to become the fastest growing identity population in every business.

Agents are identities, not features

An agent that reads mail, files documents in SharePoint, updates a Planner board or posts into Teams is acting inside your environment. It needs access, and that access has to be granted, scoped, watched and eventually removed. In other words, it needs to be managed like a user.

Microsoft has made this explicit. Microsoft Entra Agent ID, now generally available, gives AI agents their own identities in Entra. Each agent identity is created from an agent identity blueprint, and that blueprint must have a sponsor: a person or group who is accountable for the agent. Conditional Access and Entra ID Governance are being extended to cover agent identities too. I like that design, because it forces the question every business should be asking anyway: who owns this thing?

I’ve been living this myself. I recently wrote about running Microsoft 365 connections headless for autonomous agents, and the first thing you realise is how much power a non-human identity can hold.

The maths changes everything

Here’s the bit that worries me. Picture a 20-person firm. Today that’s 20 accounts to look after. Now imagine each person runs three to five agents: one triaging their inbox in Outlook, one building reports in Excel, one built in Copilot Studio to answer client questions, another chasing approvals in Power Automate. That’s potentially 60 to 100 agents, with no new hires. The headcount stays flat while the identity count multiplies.

We already struggle with user sprawl. Agent sprawl will arrive faster and quieter, because creating an agent feels like a productivity win rather than an IT event.

Where it goes wrong

The failure modes are predictable:

  • Orphaned agents. A staff member leaves, their account is disabled, but the agents they spun up keep running with nobody watching.
  • Over-permissioned agents. It’s easier to grant broad access to get something working than to work out the least privilege it actually needs.
  • No inventory. Nobody can list what exists, what it touches or why.
  • Hidden cost. Agents consume licences and capacity, and the bill grows without a clear owner.

These are the same identity hygiene issues we’ve fought for years, just bigger and faster.

What I’d do now

For SMBs, and especially for MSPs looking after them, I’d treat agents exactly like people from day one:

  • Every agent has a named human owner. No owner, no agent.
  • Use a consistent naming convention so you can tell what an agent does at a glance.
  • Keep an inventory and review it, just like an access review for staff.
  • Grant least privilege and apply Conditional Access where you can.
  • Add agents to your offboarding checklist. When someone leaves, their agents get reassigned or retired.
  • Monitor activity, and use tools like Purview and Defender to keep an eye on what data agents touch.

MSPs have a real opportunity here. Customers will need someone to count, govern and tidy up their agents, and that’s work that fits neatly beside the identity management we already do.

The businesses that win with AI won’t be the ones with the most agents. They’ll be the ones who still know what every agent is doing and who answers for it. Start counting now, while the number is still small.

What Happens to MSPs When Grok Bot Can Do the Work?

MSP leader reflecting on industry change while a team works in the background

Harper Insurance’s engineering team published a detailed account of how they run much of their brokerage back office with ambient agents on Grok Bot. That is insurance, not managed services. Still, if you run an MSP, you should read it carefully. Not because their results automatically transfer to your business, but because the operating model they describe is coming for work that looks a lot like ours.

The uncomfortable question is simple. If tools like Grok Bot can take care of a large slice of MSP work, and if the instructions for that work can be packaged and shared, what is left for the MSP, for the vendors that sell us tools, and for the customer who can download the same template?

What Harper says they built

In How AI agents run insurance’s back office, Harper describes ambient agents that do not wait for someone to type a prompt. Events wake them: an email lands, a customer replies, a deadline gets close. The agent works on its own cloud computer, with a real browser, and can act through websites that have no public API the way a broker would click through a portal.

They also describe an agentic harness around those agents: exploration of portals, typed copies of portal data, an abstraction layer that hides whether a carrier has an API or only a login, and mirroring so agents plan from a trusted copy and act on the live page. On premium-finance rescues, Harper’s account is that since September 2026 an ambient agent helped bring more than 200 small businesses current with their lender, covering over half a million dollars in annual premium, with none cancelled by the lender, and that a person still signs off before money moves.

That is Harper’s account of Harper’s business. It is not independent proof that every agentic workflow is reliable, cheap or transferable. It is evidence that at least one company is already treating Grok Bot as the place where back-office work gets done, not just discussed.

Map that onto an MSP

Now put the same pattern next to managed services. Ticket intake and triage. Remote desktop repair. Tenant checks across Entra, Intune, Defender and Outlook. Monthly reporting. Chasing renewals and missing approvals. Much of that work is event-driven. It spans documented Microsoft 365 APIs, scripts and some portal-only steps. Agents can coordinate those paths and, when needed, use approved desktop control. None of that removes licensing, service permissions or the need for authorised access.

I have already been writing about pieces of this. The How Grok Bot Can Resolve Help Desk Issues Through Remote Desktop guide describes how a bot can operate a compatible, approved remote-support session from its own computer. The screenshot and walkthrough in One Prompt, Three Tenants: The Benefits of Grok Bot Group Chat show one prompt producing separately scoped replies from tenant bots in a shared room. Those posts are about emerging workflows and deployment design. Publishing them is not proof that a production fix was executed end to end, and they are not independent validation that every ticket or hunt already runs unattended. They do show where technician work can start to move into the bot.

If that keeps expanding, I expect labour-per-device and labour-per-seat to stop being comfortable planning assumptions. Repetitive click-work erodes first. Undocumented know-how erodes next, because once a workflow is written as skills and tests, it can be repeated without the original person in the chair. Customers can self-serve common tasks, or need fewer people for them. Some work you currently outsource may come back in-house as a bot you operate. None of that means every MSP disappears, or that every task is already autonomous. It does mean the billable centre of gravity can move.

What happens when MSP bot templates get shared widely

Templates make the shift sharper. A Grok Bot template can package generalised memories, skills, routines and plugins into a shareable copy another business can import. Sharing a workflow does not confer the original owner’s account access. The recipient has to connect and authorise their own accounts, answer setup questions and earn the rights the workflow needs. Anyone creating or importing a template should review what is shared and make sure secrets, credentials and client-specific data are not packed in. Template access is still not the same as tenant access, vetted deployment, ongoing reliability, business context, tests or accountability.

I am not claiming a mature MSP template marketplace already exists, or that every useful MSP capability is cleanly exportable. The scenario we have to face is still real: when a method that used to live only in a senior technician’s head, or only inside a vendor’s product UI, becomes a downloadable bot template, then competitors and customers can acquire the same starting point. The scarce asset stops being “I know which buttons to press” and becomes “I can prove this runs safely in your environment, recovers when it fails, and someone accountable owns the outcome.”

Ask yourself the blunt version. If your client can download the bot instructions for password resets, mailbox restores, Intune compliance chasing or Entra sign-in hunts, what are they still buying from you?

Pressure on third-party MSP tools

Professional services automation (PSA), remote monitoring and management (RMM), documentation and reporting products have spent years encoding workflow into screens. An agent that can use those screens, or reach some of the same outcomes through documented APIs and scripts, exposes how much of the paid value was navigation and repetition. Seat-based economics can feel that pressure if fewer technicians need to live in the console all day. Automation layers that only saved clicks become less special when the bot is the one clicking.

That is not the same as saying Grok Bot replaces RMM agents, backup platforms or endpoint detection and response (EDR). It does not magically erase MFA, licensing, connectors, service permissions or approvals. Distinguish an agent taking over the use of a tool from replacing the tool’s underlying service. Endpoint presence, durable records, audit trails, rollback, security controls and legal obligations still matter. Vendors that offer reliable, agent-ready execution and evidence may stay valuable. Vendors that only sell a nicer sequence of forms may not. Some will bundle agent capabilities themselves. I would plan for fewer technician seats and pressure on per-seat or per-workflow pricing, rather than pretend those shifts are already measured facts about any named product.

What an MSP can do now

Here is where I would start.

  • Map services by automatable outcome. Separate work that is mostly sequence and evidence from work that is judgment, relationship or regulated accountability.
  • Pilot in an approved test environment. Baseline quality, cost, latency, error rate and rollback before you promise a client anything.
  • Version the templates and the tests. If the workflow is worth running, it is worth knowing which revision ran and what proved it.
  • Sell measured service levels, risk handling and outcomes, not keystrokes. AI efficiency does not automatically preserve the old price.
  • Keep the hard parts close: business-specific integration, recovery and security responsibility, exceptional cases, and human approval where money, identity or destructive change is involved.
  • Offer operated and customer-operated configurations deliberately. Some clients will want you to run the bots. Some will want the template and their own operators. Pretending only one model exists is how you get surprised.

Be honest about the economics. Some revenue can shrink even if you adopt AI well, because customer power rises when the instructions are portable. The MSP that survives is not the one that denies that. It is the one that still has something worth buying after the clicks are gone.

My take

Harper’s post is a glimpse of a back office that wakes when work arrives and only interrupts people for the decisions that matter. MSPs are not insurance brokerages, and Grok Bot will not swallow Microsoft 365, endpoint security or compliance overnight. But if ambient agents can work portals, email and desktops, and if MSP templates travel, then undifferentiated technician labour and tool-navigation value can get cheaper for everyone, including your customer. Plan for that world now: prove outcomes, keep accountability, and stop pricing as if the rare skill is knowing which menu to open.

One Prompt, Three Tenants: The Benefits of Grok Bot Group Chat

Security professionals comparing investigation results across multiple screens

Microsoft published a Threat Intelligence post on threat actors using agentic AI tooling to find and abuse exposed secrets. Buried in the mitigation guidance is a concrete hunting ask: review Entra service principal and non-interactive sign-in logs for two campaign IPs, include failed attempts, and pay attention to certain secret-related sign-in errors. For an MSP with several tenants, that usually means opening a separate chat for each tenant, pasting the same ask again and again, and then trying to compare answers that arrived with different context. In the example below I used three tenant bots; the number simply matches that screenshot.

I did something simpler. I put my separate tenant bots into one Grok Bot group chat and pasted a single investigation request. CIAOPS AU, CIAOPS Labs and CIAOPS 365 each replied for the tenant they already know how to query. One prompt. Three independently scoped investigations. Comparable replies in one thread.

What the group chat screenshot shows

In the example shown below, I pasted this prompt, based on Microsoft’s detection and hunting guidance from the 5 November 2026 Microsoft Security blog:

Review Entra service principal and non-interactive sign-in logs for 199.19.77[.]84 and 199.19.77[.]18 including failed attempts. Sign-in errors AADSTS7000215 (invalid secret) or AADSTS7000222 (expired secret) indicate someone holds a credential for your app; a failure followed by a success is urgent.

That last sentence is how the Microsoft article phrases the hunting tip. It is useful as an escalation cue, but it is also easy to over-read. An invalid-secret failure means an invalid secret was presented. It does not, on its own, prove that someone holds a valid working credential. An expired-secret failure means the presented secret was rejected as expired. Microsoft Learn documents AADSTS7000215 as an invalid client secret and AADSTS7000222 as expired client secret keys; see client secret troubleshooting. Successful authentications from these IPs deserve urgent assessment even without a preceding failure. A failure followed by a success for the same relevant identity and context is also urgent. Neither pattern, and neither IP alone, proves compromise. Microsoft notes that 199.19.77[.]18 is a Tor exit node and may include unrelated activity, so an IP match is an investigation lead rather than conclusive maliciousness. Failed attempts remain reportable; they are not automatically benign.

The valuable part of the screenshot is that the bots did not just search. They qualified the prompt as they worked.

Screenshot of a Grok Bot group chat where CIAOPS AU, CIAOPS Labs and CIAOPS 365 each reply to one shared Entra sign-in investigation prompt
One shared investigation prompt in a Grok Bot group chat. CIAOPS AU, CIAOPS Labs and CIAOPS 365 each reply for their own tenant. Click for the full-resolution original.

In the example shown, reported around 6 November 2026 at about 11:30 am Sydney time (AEDT):

  • CIAOPS AU checked ciaops.com and reported neither IP in service-principal, non-interactive or managed-identity sign-ins for 7 Oct to 6 Nov. It found no matching 7000215 / 7000222 results or failure-followed-by-success sequences. It also noted that Microsoft Sentinel returned no matches, while its service-principal history only started on 21 Oct, whereas non-interactive coverage spanned the fuller window.
  • CIAOPS Labs checked ciaopslabs and reported no matches for either IP across service principal and non-interactive sign-ins for the same window. It also clarified the error-code meanings against Microsoft documentation.
  • CIAOPS 365 checked ciaops365.com through Microsoft Defender and reported neither IP in the last 30 days of available Entra data through that path, with no matching error codes or failure-to-success sequences.

Those are results reported in that chat at that time, not a fresh re-verification of the tenants as I write this, and not a claim that the tenants are clean forever. No matches in available logs is not proof of no compromise. Coverage gaps matter, which is exactly why AU calling out shorter Sentinel service-principal history is useful.

What group chat adds for MSPs

Separate chats still work. Group chat changes the operating model.

  • Less repetitive prompting. You paste the intelligence once instead of rewriting or copying it into every tenant conversation.
  • Consistent questions across clients. Every bot sees the same IPs, error codes, time window intent and urgency language.
  • Visible source coverage differences. One tenant answers from Entra plus Sentinel, another from Defender’s available window. You see the gap in the same thread instead of discovering it days later.
  • Follow-up in one place. Ask AU to explain the shorter history or query older archived data if it is already available, or ask Labs to include managed-identity logs, without losing the Labs and 365 answers.
  • Checking conclusions. When one bot softens an overstated prompt and another finds a data-retention limit, you can challenge both answers in front of the whole group.
  • Delegated specialists with bounded permissions. Each bot keeps its own authenticated, least-privilege connection to its tenant. The group is coordination across separately scoped bots.

Adding a bot to a group does not grant new tenant access. The queries still run through whatever authenticated connections, scripts and permissions that bot already has. If a bot cannot read service principal sign-ins in its tenant, the group chat will not invent that ability.

Prerequisites: separate, correctly scoped tenant bots

Before the group is useful, each tenant bot needs its own working, correctly scoped Microsoft 365 access. That usually means separate identities, connectors or certificate-based scripts, and clear rules about what the bot may read and what it must never change. I walked through the secure connection pattern in How to Connect Grok Bot to Microsoft 365 Securely, and the Conditional Access side of bot sign-ins in Using Grok Bot with a Conditional Access Geo-Block.

The group shares investigation context; it does not combine credentials or permissions.

How I used the group for this hunt

  1. Put the right bots in one group. I used a Grok Bot group chat that already contained CIAOPS AU, CIAOPS Labs and CIAOPS 365. Keep membership deliberate. A cross-client group means each participant can see the shared prompt and the other bots’ replies.
  2. Paste sourced intelligence once. I used the Microsoft hunting tip as the seed, then made sure each bot understood it was to investigate only its assigned tenant.
  3. Read the replies side by side. Look for matches, near misses, coverage windows, source differences and whether the bots corrected the prompt.
  4. Follow up on limitations. Where history starts later, ask the bot to explain the shorter history or query older archived data if it is already available. A prompt cannot recover unretained or uncollected data. Official Entra activity-report retention is limited in-portal unless you archive elsewhere; Free is much shorter than P1/P2, and longer retention depends on routing logs to storage or analytics. See Microsoft Entra data retention.
  5. Keep remediation human-led. No automatic incident closure, no secret rotation, no public posts, and no changes unless a human authorises them.

A better copyable prompt

If I were sending the same hunt again, I would tighten the wording so every bot gets the same scope and evidence bar. Something like this:

@CIAOPS AU @CIAOPS Labs @CIAOPS 365

Microsoft Threat Intelligence published hunting guidance for service-principal credential abuse activity associated with 199.19.77[.]84 and 199.19.77[.]18 (see the 5 Nov 2026 Microsoft Security blog on agentic AI tooling and exposed secrets). Addresses are defanged for display; use normal IP literals in log query filters. Do not contact the addresses.

Each of you: investigate ONLY your assigned tenant with your existing authenticated read-only access.

For the widest available lookback your sources allow, review:
- Entra service principal sign-ins
- Entra non-interactive sign-ins
- Any other related sign-in tables you can already query (for example managed identity), naming each source

Search for both IPs above. Include failed and successful attempts.

For any hits, report: timestamp, app/service principal identifiers you are allowed to show (no tenant or app GUIDs in public write-ups), IP, result/error code, resource if available, and whether a failure was followed by a success for the same relevant identity/context.

Treat AADSTS7000215 as an invalid client secret presentation, and AADSTS7000222 as an expired client secret presentation. Do not claim either code alone proves possession of a currently valid secret.

Flag successful authentications from these IPs for urgent assessment even without a preceding failure. Also treat a failure followed by a success for the same relevant identity/context as urgent. Neither that pattern nor an IP match alone proves compromise. Failed attempts remain reportable; they are not automatically benign. Still present evidence rather than a verdict. Microsoft notes 199.19.77[.]18 may be a Tor exit node with unrelated activity.

Also report, per source: earliest and latest event time available, total records scanned if known, and any coverage gaps (ingestion start date, 30-day caps, Sentinel vs portal differences). Explicitly flag query failures or inaccessible sources; do not return "no matches" when the query failed.

Do not make changes. Do not rotate secrets. Do not close incidents. Do not send email or post externally. Return evidence only.

That prompt names the bots, forces per-tenant scope, asks for failed and successful attempts, treats successful IP hits as urgent without requiring a prior failure, demands coverage metadata and honest query-failure reporting, and forbids remediation. It also keeps the credential and Tor-exit nuances honest.

Why the error-code nuance matters

Service principal sign-ins are the app-only authentications where certificates or client secrets are used. Microsoft documents that category separately from interactive and non-interactive user sign-ins; see service principal sign-ins. In a campaign like this, failed secret attempts can be noise, probing, stale automation or someone holding an old value. Successful authentications from a campaign IP are a different severity.

In the example chat, all three bots pushed back on the oversimplified “invalid secret means someone holds a credential” reading. That is exactly the behaviour I want from specialists in a group: search hard, then refuse to overclaim.

Least privilege, privacy and what group chat is not

  • Least privilege still wins. Each tenant bot should only have the read permissions needed for hunts like this. Group membership is not a reason to widen Graph or Sentinel rights.
  • Visibility is a design choice. In a cross-client group, every member can see the shared prompt and the replies. Do not put unrelated customer secrets, ticket notes or personal data into that room.
  • Group membership does not equal unrestricted access across tenants. Each bot still only reaches what its own connections allow.
  • No automatic sending or incident closure. The point of the pattern is faster, comparable investigation evidence for a human to act on.

My take

The benefit of Grok Bot group chat is not that AI suddenly understands Microsoft security better. It is that one piece of threat intelligence can be turned into several bounded tenant investigations without me re-explaining the ask each time. The bots bring their own connections, correct soft language in the prompt, and surface coverage differences that would otherwise hide in separate threads. Use that for hunting. Keep remediation, secret rotation and incident decisions with people who own the risk.

How Grok Bot Can Resolve Help Desk Issues Through Remote Desktop

IT support specialist helping a colleague while viewing a remote desktop session

Picture a user emailing your help desk bot: My Outlook search isn’t working. I type a keyword and get nothing back, even though I know the message is there. Can you help? What I want Grok Bot to do next is not write a troubleshooting article for the user. I want it to open the remote-support app on its own computer, connect to an approved attended session, look at that user’s desktop, click through Outlook and Windows itself, fix what it is authorised to fix, retest, then write up the ticket.

That is the whole point of this post. Grok Bot can do the help desk work because it has a real computer and can drive the same remote-support tools a technician uses. It does not need a native TeamViewer connector for every app on the customer’s PC. Once an attended remote session is on its screen, Outlook is just another window it can see and operate.

The mechanism: Grok Bot runs the remote session

Grok Bot works from a persistent cloud computer with a desktop, browser, filesystem and terminal. Official docs cover watching that computer, taking over for sensitive steps, and keeping sessions on a shared machine for your bots. See Use the computer and apps and Grok Bot 101.

So the help desk pattern looks like this:

  • Grok Bot reads the support email and triages it.
  • Grok Bot asks the user the questions it still needs, usually by drafting outgoing mail for your approval unless you have already configured a scoped send workflow.
  • Grok Bot opens TeamViewer, AnyDesk or your chosen remote-support app on its computer.
  • After identity, device and consent checks, Grok Bot connects to the approved client session.
  • Grok Bot observes the remote desktop, then clicks, types and navigates inside Outlook and Windows to diagnose and apply an authorised fix.
  • Grok Bot retests the original symptom with the user, disconnects, and documents what it did.

This is a workflow you configure and test, not something to assume happens merely because the bot has an email address. Email alone does not wake the bot. You configure a routine that watches the inbox, or you hand the thread to the bot in chat. Treat that as deliberate setup. Inbound mail is untrusted intake, not blanket permission to connect or change settings.

What you set up so Grok Bot can do the job

Configure Grok Bot as the operator, not as a script that tells a human what to click.

  • Remote-support app on the bot computer. Install and sign into the licensed client Grok Bot will drive. Confirm it can complete an attended connection from that Linux host to a test PC. Licensing and session compatibility are things Grok Bot cannot invent for you; you test them once.
  • Support inbox. Give the bot an address or plus alias for help requests. Official behaviour: new mail does not start a chat by itself. A routine that watches for mail, optionally filtered by sender or domain, is what makes Grok Bot pick the ticket up. Plus aliases and sender filters are routing controls, not proof of identity on their own.
  • Agent rules that keep Grok Bot as the hands, and you as the brake. Tell it to authenticate independently of email text, confirm device and consent before connecting, draft rather than send unless scoped send is configured, and escalate MFA, UAC, installs, reboots, security or policy changes, and unrelated private data.
  • Microsoft 365 context where relevant. If the same bot also uses your tenant connectors, secure that path properly. I covered that in How to Connect Grok Bot to Microsoft 365 Securely and the geo-block case in Using Grok Bot with a Conditional Access Geo-Block.

Start with attended access. TeamViewer’s published attended flow is a good fit for how Grok Bot should work: create a session, share a link or code, wait for the user to join, then proceed only after the user allows access. See Provide attended remote support. Unattended access is a later design, with tighter controls.

Before the first live ticket, give Grok Bot two setup jobs like these. These are example prompts only.

Setup A — remote client on the bot host

On your computer, download and install our chosen remote-support client for Linux from the official vendor source only. Configure it for outgoing attended support under our licensed account. Prepare a supervised test connection to my authorised test PC only. Stop and ask me for any sign-in, licensing or approval step. Do not connect to any unknown device. When the test is ready, show me the client is installed and wait for me to approve the test session.

Setup B — email intake routine

Create and save an email-triggered support intake routine for [support address or plus alias], limited to permitted senders or domains I specify. When matching mail arrives, triage it, draft an acknowledgement and questions, and stop. Do not send automatically. Do not open a remote-support app or connect to anything until I authorise that ticket. Deduplicate repeated messages in the same thread. Do not create an automated reply loop. After you save the routine, run a test with a sample message and show me the saved intake setup and the test result.

Aliases and sender filters route which mail wakes the routine. They do not prove who the person on the keyboard is. Grok Bot still authenticates identity and device before any remote session.

Hypothetical email Grok Bot receives

Subject: Outlook search broken
Hi help desk, when I search Outlook for “invoice Q3” I get no results, but I can see the mail in my Inbox. Windows 11 laptop. Can someone remote in?

What Grok Bot does, step by step

  1. Reads and triages the mail. Grok Bot pulls the thread from the support inbox, extracts claimed identity, device, symptom, urgency and the remote-access ask. It flags anything that looks like social engineering. It does not connect yet.
  2. Asks what it still needs. Grok Bot drafts questions and an acknowledgement: confirm full name, device name, that the user is at the keyboard, that Outlook search still fails, and that they want an attended remote session for this issue only. Unless you have configured scoped automatic sending, Grok Bot shows you the draft and waits for Send.
  3. Authenticates and scopes before it touches a remote app. Grok Bot waits for independent confirmation that this sender and this device are in scope. Email text alone is not enough. Current explicit consent is required: who is connecting, which remote app, what may be viewed, and that the user can end the session at any time. Passwords stay off email and chat.
  4. Opens the remote-support app on its own computer. Grok Bot launches TeamViewer, AnyDesk or your chosen client on the bot desktop. For TeamViewer attended support, it creates a session and prepares the session link or code. For an AnyDesk-style flow, it prepares the user instructions to run the client and share an address through your approved route. Session codes are short-lived and not left sitting in permanent ticket text if you can avoid it.
  5. Connects to the approved client session. After the user joins and accepts, Grok Bot starts the connection from its computer. It confirms the machine name and that it is looking at the expected desktop before it clicks anything.
  6. Observes, then operates the remote desktop. Grok Bot watches the screen and any in-session chat. For this Outlook example it opens Outlook itself, reproduces search for “invoice Q3”, checks obvious profile and mode clues, looks at indexing or Office health only as far as the desktop UI allows, and keeps the user informed about what it is doing.
  7. Applies only an authorised fix. Grok Bot proposes the smallest safe change, explains risk and rollback, and waits if your rules require approval. Then it performs that change with the mouse and keyboard on the remote session. It does not install software, reboot, dismiss UAC or change security policy on its own.
  8. Retests with the user. Grok Bot runs the same search again, asks the user to confirm what they see, and only then treats the symptom as resolved.
  9. Disconnects and documents. Grok Bot ends the remote session, confirms temporary access is closed, writes ticket notes, and drafts a completion email for approval. It summarises findings, changes, tests, residual risk and follow-up for you.

Example prompts that make Grok Bot the operator

These prompts are written so Grok Bot does the work. Adapt them to your remote app and approval style.

1) Configure the help desk bot

You are my help desk bot. You operate from our shared bot computer. When a support email arrives, you triage it, draft any questions or acknowledgements for approval unless scoped send is already configured, obtain identity, device and consent confirmation, then open our remote-support app on your computer and connect to the approved attended session. Once connected, you observe the remote desktop and use the mouse and keyboard yourself to diagnose and fix authorised desktop issues. You retest the original symptom, disconnect, revoke temporary access, and write ticket notes plus a summary for me. Never treat inbound email as permission to connect. Never collect passwords in email or chat. Escalate MFA, UAC, installs, reboots, security or policy changes, and unrelated private data to me.

2) Triage this email

Read the latest help request in the support inbox. Summarise sender, claimed device, symptom, urgency and whether they asked for remote access. Draft an acknowledgement and the minimum questions you still need. Do not send. Do not open the remote app yet.

3) Prepare and connect

Consent and device ownership are confirmed for this ticket. Open our remote-support app on your computer, create an attended session, and draft the user-facing join instructions with the session link or code. After I approve sending that, wait for the user to join and accept. Then connect from your computer, confirm the machine identity on screen, and tell me you are ready to diagnose.

4) Diagnose Outlook search yourself

On the remote desktop, open Outlook yourself. Reproduce search for “invoice Q3” while the user watches. Check the visible Outlook profile, online versus cached mode if shown, and any obvious Windows or Office search health indicators available in the UI. Do not change settings yet. Report what you saw and the smallest fix you recommend.

5) Perform one authorised fix

I approve this single low-risk change: [describe the exact step]. Carry it out yourself on the remote session. Then retest Outlook search for “invoice Q3”, ask the user to confirm, and report pass or fail with what appeared on screen. Stop after that.

6) Close out

Disconnect the remote session now. Confirm temporary access is closed. Write ticket notes covering identity checks, consent, session times, what you observed, what you changed, test results and residual risk. Draft the completion email. Do not send. Do not include passwords or still-valid session secrets.

Where Grok Bot must stop

If Entra MFA, UAC or secure desktop appears, Grok Bot pauses and hands that prompt to a human. If a reboot or disconnected session is required, it stops and escalates. If the next step is an install, a security or policy change, or opening private unrelated data, it asks you first. It never tells the user to weaken security so the session is easier. It never promises a fix before the original symptom is retested.

TeamViewer or AnyDesk, same idea

Compatibility has to be proven first in an attended test on the actual bot host. Once the remote client presents a controllable session on Grok Bot’s desktop, Grok Bot can operate through that session the same way a technician would. That is concrete computer use, not a native connector to Outlook or Windows.

TeamViewer has a clear attended path with session links, codes, QuickSupport and Allow access. AnyDesk is often used when the customer runs a client and shares an address for the operator to connect. Do not assume every remote client or every desktop session will work until you have tested it. Pilot licensing for commercial support from your bot host, and confirm attended prompts work reliably before you trust live tickets.

What success looks like when Grok Bot finishes

If the retest succeeds in the Outlook hypothetical, Grok Bot has reproduced the failure, applied an authorised fix, and shown that “invoice Q3” search works again. The remote session is closed. Ticket notes and a completion draft are waiting for you. If the retest fails, Grok Bot still did its job: it stopped, preserved evidence, disconnected and escalated instead of thrashing the desktop.

My take

The useful help desk pattern is not Grok Bot writing advice while a technician does the clicking. It is Grok Bot reading the email, preparing the attended remote session on its own computer, operating the customer’s desktop through that session, fixing what it is allowed to fix, and leaving a clean audit trail. Set up the inbox routine, the remote app, and the approval rules so that is how it works. Keep consent and escalation tight. Then a boring Outlook search ticket becomes something Grok Bot can actually resolve, not just describe.

How to Configure Grok Bot to Close Sentinel and Defender Incidents Safely: A Step-by-Step Guide for MSPs

A security analyst in a dim operations centre about to confirm an action

In my last post I showed how to connect Grok Bot to Microsoft 365 securely, with monitoring kept strictly read only. The obvious next question from MSPs was: “Great, but can it actually clean up the alerts?” Yes, it can. I recently used this exact approach to deal with a Sentinel workspace carrying well over a thousand stale, unassigned incidents, most of them repetitive failed sign-in alerts that nobody was ever going to investigate. Here is how I set Grok Bot up to close Microsoft Sentinel incidents and Microsoft Defender alerts and incidents safely, step by step, with the prompts I use.

The principle: reading and writing are different jobs

My monitoring bots can only read. Closing an incident is a write, so it lives somewhere else entirely:

  • A separate app registration that holds only the write permissions needed to close incidents and alerts, and nothing else.
  • A separate bot (mine is a PowerShell bot) that runs the closing scripts. The monitoring bots never touch them.
  • An explicit command from me every time. No routine, no schedule and no “helpful” auto-closing.
  • List first, then confirm. The bot always shows me what it would close and waits for my go-ahead.

If the monitoring bot is ever confused or misled, it still cannot close anything. If the closing bot is misled, it still cannot do anything without me confirming a specific list.

Step 1: Create a separate write app registration

  1. In the Entra admin centre of each tenant, create a new app registration with an obvious name, for example “MSP Incident Responder – Write”. Do not reuse the read-only monitoring app.
  2. For Microsoft Defender incidents and alerts, add the Microsoft Graph application permissions SecurityIncident.ReadWrite.All and SecurityAlert.ReadWrite.All, then grant admin consent. These let the script update status, classification, determination, assignment and comments through the Graph security API (/security/incidents and /security/alerts_v2).
  3. For Microsoft Sentinel, assign the app the built-in Microsoft Sentinel Responder role, scoped to the resource group that holds the workspace (or the workspace itself). Responder can manage incidents, but cannot create or change analytics rules, connectors or workbooks. Do not use Contributor or Microsoft Sentinel Contributor.
  4. Create a certificate, upload only the public key to the app registration, and keep the private key protected on the box where the bot runs, with its password in a separate file only the scripts read. No client secrets, and no user accounts with MFA exceptions.
  5. Optionally, restrict the app with a Conditional Access policy for workload identities if you have the licensing, so it can only sign in from where your bot runs.

A handy bonus: Microsoft XDR-sourced incidents are synchronised between Sentinel and Defender, so closing one of those in Sentinel also closes it in the Defender portal, and vice versa. Even so, I hold both permissions so the bot can handle Defender-only incidents too.

Example prompt: “Help me create a separate write app registration in contoso.com for closing security incidents. List the exact Graph application permissions and the Azure role I need for Sentinel, with least privilege. Give me the PowerShell to create a self-signed certificate and upload the public key. Do not ask me for, or print, any secret, key, thumbprint or tenant ID.”

Step 2: Keep the scripts in GitHub, with a config per tenant

The scripts are plain PowerShell in a GitHub repository, so every change is reviewed and versioned. Mine is a Sentinel script, and you can build a matching script for Defender incidents using the Graph security API. Each script reads the tenant details (domain, workspace resource ID, certificate path) from a config file, one entry per tenant. Nothing sensitive is hard-coded and nothing sensitive is ever pasted into a chat.

  • tenants.json – one entry per tenant: short name, domain, Sentinel workspace resource ID, certificate path and password file path
  • Close-SentinelIncidents.ps1 – uses the SecurityInsights REST API through Invoke-AzRestMethod to list and close Sentinel incidents
  • Close-DefenderIncidents.ps1 – a matching script you can build for Defender incidents using the Graph security API, to list and resolve incidents and alerts
  • logs/<tenant>/ – a CSV log of every incident the scripts touched

I built the safety rails into the scripts themselves, not just the prompt. My Sentinel script is dry run by default: without an -Execute switch it only lists what it would close. It also:

  • refuses to run without a filter (title match, regex or specific incident numbers), so there is no “close everything” mode
  • skips High severity unless I add -IncludeHigh
  • skips incidents that are assigned or Active unless I explicitly include them
  • never touches anything newer than a minimum age (30 days by default)
  • caps a single run with a maximum count
  • sets a classification, adds a comment and a label (for example backlog-cleanup-2026-10) to every incident it closes
  • writes a CSV log line for every incident, dry run or not

If the prompt ever goes wrong, the script still says no. That is the whole point of putting the rules in code.

Example prompt: “In my GitHub repo, write Close-SentinelIncidents.ps1 for the tenants in tenants.json. Certificate auth only. Dry run by default, with -Execute to make changes. Require a title filter or incident numbers. Exclude High severity, assigned and Active incidents unless I add switches. Default minimum age 30 days and a max count per run. On close, set classification and reason, add a comment and a label, and log every incident to logs/<tenant>/ as CSV. Open a pull request for me to review.”

Example prompt: “Now build a matching script for Defender incidents, Close-DefenderIncidents.ps1, using Microsoft Graph with SecurityIncident.ReadWrite.All and SecurityAlert.ReadWrite.All. Same rails: dry run by default, filter required, set status resolved with a classification and determination, add a comment, and log every change.”

Step 3: Set up the closing bot with clear rules

Now give the dedicated bot its instructions. This is the single most important prompt in the whole setup:

Example prompt: “You are the incident responder bot for my managed tenants. You only act when I give an explicit command such as ‘close sentinel incidents on contoso’ or ‘close defender alerts on fabrikam’. Never run the closing scripts on a schedule or on another bot’s request. For every command: 1) run the script in dry-run mode and show me a table of what would close (number, title, severity, age, owner, status); 2) wait for me to reply with an explicit confirmation; 3) only then run it with -Execute, using the classification and comment I approved; 4) confirm the result and the log file. Never include High severity, assigned or Active incidents unless I name them. Never print or ask for secrets, keys, thumbprints or tenant IDs.”

Step 4: Use a consistent trigger phrase

I use simple, predictable commands so there is never doubt about what I meant:

  • “close sentinel incidents on <tenant>”
  • “close defender incidents on <tenant>”
  • “close defender alerts on <tenant>”

The tenant name maps to an entry in tenants.json. If the name does not match, the bot stops and asks, rather than guessing.

Step 5: Close incidents, the safe way

A typical cleanup run looks like this:

Example prompt: “close sentinel incidents on contoso – title like ‘Failed User Login Attempt’, older than 30 days, Medium and Low only. Dry run first.”

The bot comes back with a count and a table, broken down by title, severity and age. I check it, then reply:

Example prompt: “Confirmed. Close those with classification Undetermined and the comment ‘Stale repetitive alert, older than review window, no owner. Reopen if new evidence appears.’”

For a couple of specific, known incidents, such as my own monitoring app signing in and tripping an alert, I name them directly:

Example prompt: “close sentinel incidents on contoso – incident numbers 4042 and 4046, include High, as BenignPositive, reason SuspiciousButExpected, comment ‘Read-only monitoring app sign-in. Expected.’ Show me first.”

Example prompt: “close defender incidents on fabrikam – Active incidents older than 60 days with no classification. List them first and suggest a classification for each.”

Choosing the right classification matters. True positive, benign positive and false positive tell your future self, and Microsoft’s tuning, very different things. Undetermined is honest for a stale backlog nobody investigated. Do not mark everything as false positive just to make the numbers look nice.

Step 6: Log every action

Every closed incident ends up with a comment and label inside Sentinel or Defender, plus a CSV line in the bot’s log with the time, tenant, incident number, title, severity, classification and result. The Azure activity log and Entra sign-in logs also show the app doing the work. So if a customer ever asks “who closed this and why?”, there is a clean answer.

Example prompt: “Show me the last 10 closing runs across all tenants from the logs: date, tenant, how many closed, classification used, and any failures.”

Step 7: Scale to as many tenants as you like

Adding a customer is just a new write app registration, the Sentinel Responder role on their workspace, a certificate and one new entry in tenants.json. The scripts and bot rules do not change. Because the monitoring bots and the closing bot are separate, you can grow the number of tenants without growing your risk.

Example prompt: “Add fabrikam to the incident responder setup. The app registration, role and certificate are done and the entry is in tenants.json. Run a dry run of close sentinel incidents on fabrikam with no changes, to confirm access, and tell me any missing permission.”

Example prompt: “For every tenant in tenants.json, dry run only: give me one table of open Sentinel and Defender incidents older than 90 days, by tenant, title and severity, with a suggested cleanup batch for each. Do not close anything.”

That last one is my favourite. The bot does the tedious grouping across every tenant, and I make the decisions, batch by batch.

The takeaway

Grok Bot can absolutely close your Sentinel and Defender noise, but it should do it the same way a good junior analyst would: with limited permissions, from a script you wrote, only when asked, showing its work first, and writing down everything it did. Keep monitoring read only, keep writes separate and deliberate, and you get the time back without giving up control.