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:

No sign-in. You do not need Microsoft 365 admin consent to add it. That removes the usual “which account?” friction.
Trusted content. Answers can cite official Learn pages instead of a random blog from 2021.
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

Using Microsoft Learn, what are the eligible prerequisite licences for Microsoft 365 Copilot? Summarise the commercial table and link the page.
Using Microsoft Learn, what does an Intune Windows compliance policy check for firewall, BitLocker and Defender? Bullet list with the Learn link.
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

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.
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.
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

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.
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.
Using Microsoft Learn, search for PowerShell samples to work with Conditional Access policies. Prefer official samples and link them.

Comparing options

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.
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

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.
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.
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

Want to Know Where You’re Heading? Look Back

A business owner standing on a long highway at dusk, looking back at the road he has travelled

Nobody can tell you exactly where your business will be in two years. I certainly can’t. But I’ve found a surprisingly reliable way to get a preview, and it doesn’t involve forecasts, vision boards or a strategy offsite. It involves turning around.

Instead of staring at the horizon, look at the road behind you. Specifically, the last 90 days.

The honest 90-day review

Ask yourself a few plain questions. Are you making more money than you were three months ago? Are you spending more of your week on work you actually enjoy? Do you have more freedom, or less? Are you enjoying your life, or just getting through it?

The answers are usually one of three: yes, no or sorta. Most MSP owners I speak with land on sorta. Revenue is fine. The team is busy. Tickets get closed. Yet the owner is still the escalation point for everything, still writing proposals at 10pm and still promising themselves that next quarter will be different.

Here’s the uncomfortable part. Sorta is not a resting place. It’s a direction.

Your trajectory is already set

The easiest way to see where you’ll end up is to take what you did over the last 90 days and extend the line. Picture repeating the same actions, and just as importantly the same inactions, every single day for the next two years.

The Copilot licence you bought but never rolled out properly. The SharePoint clean-up you keep deferring. The documentation that lives in one tech’s head. The pricing review you haven’t had time for. None of these feel urgent today. Multiply them by 730 days and they become the shape of your business.

So where does that line take you? Somewhere great? Somewhere not so great? Or just okay? Be honest, because okay compounds too.

Use the tools to read the road

This is one place where I find Microsoft 365 Copilot genuinely useful, not as a magic fix but as a mirror. Your last 90 days are already sitting in Outlook, Teams, Planner and your Excel reports. Picture asking Copilot to summarise what consumed your calendar this quarter, which client conversations kept recurring, or what you committed to in meetings and never followed up. The patterns are often obvious once someone lays them out in front of you.

Then do the same for your team. Where are the repeated questions? Which processes in your PSA or SharePoint keep generating rework? A short, honest review like this tells you more about your future than any five-year plan.

Small changes in direction matter more than big declarations. I wrote earlier about how worthwhile change accumulates in Give It Time to Become Something, and that applies here. Shift the daily habits and the two-year destination moves with them.

If you’re already heading somewhere great

Maybe your review comes back as a clear yes. More revenue, better clients, more freedom. Brilliant. Keep doing what’s working.

But between you and me, I reckon there’s a way to get you there faster. It usually comes from removing the busywork that still drags on your best people, rather than adding more effort. Automate the repetitive reporting with Power Automate. Let Copilot draft the first pass of the QBR deck. And as I said in Stop Acting Like the Business You Have Not Built Yet, stop carrying overhead you don’t need yet.

Take an hour this week. Look back at the last 90 days, then extend the line. If you don’t like where it ends, today is the cheapest day to change the angle.

MSP Summer School 2027: The AI MSP Make the Successful Transition

For a number of years I’ve run an MSP Summer School during January.

For January 2027, I want to tackle what I believe is one of the biggest changes the MSP industry has faced:

The transition to becoming an AI-enabled MSP.

AI isn’t simply another product that MSPs need to understand so they can sell it to customers.

I think the change is much bigger than that.

For the past 20 years, MSPs have helped customers navigate major technology transitions. We’ve moved customers from servers to cloud, perpetual licensing to subscriptions, on-premises infrastructure to Microsoft 365 and traditional security models towards Zero Trust.

This time, the MSP itself needs to make the transition.

That’s what the 2027 MSP Summer School will be about.

The AI MSP: Make the Successful Transition

The plan is to run four live online sessions during January:

Date	Time
Wednesday, 6 January 2027	10:00 am–12:00 pm AEDT
Wednesday, 13 January 2027	10:00 am–12:00 pm AEDT
Wednesday, 20 January 2027	10:00 am–12:00 pm AEDT
Wednesday, 27 January 2027	10:00 am–12:00 pm AEDT

That’s eight hours across four Wednesday mornings, with a week between sessions to take what we discuss, try it inside your MSP and come back with the results.

The program will follow a simple progression:

Understand → Build → Sell → Operate

This won’t be eight hours of AI theory.

The objective is to help you start building the AI-enabled version of your MSP.

Week 1: The AI MSP

What does an MSP need to become?

We’ll begin with the strategic question.

What does AI actually mean for the MSP business model?

We’ll look at areas including:

how AI changes the way an MSP operates
where existing MSP revenue may come under pressure
what customers will increasingly expect from their technology provider
AI-enabled service delivery
Microsoft 365 Copilot, agents and automation
opportunities for new recurring services
moving towards managed business outcomes
Shadow AI, security and governance
assessing your current AI maturity

The objective will be to start creating an AI MSP Transition Map for your business.

Week 2: Build the AI-enabled MSP

Use it yourself before you try to sell it

I strongly believe MSPs need to start using AI internally before attempting to advise customers on their own AI transformation.

We’ll therefore get practical.

We’ll look at opportunities across:

service desk
technical documentation
sales
marketing
proposals
account management
customer reporting
project delivery
security
administration
knowledge management
business process automation

We’ll also explore technologies such as Microsoft 365 Copilot, Copilot Chat, Copilot Studio, agents, Power Automate, Azure AI, RAG, private/local AI and MCP.

One question will feature heavily:

Would I currently pay an employee to do this manually?

If the answer is yes, we should at least investigate whether AI can assist, accelerate or automate some of that work.

The objective will be for each participant to identify at least 10 processes inside the MSP that could potentially be redesigned using AI.

Week 3: Selling AI

How do we turn this into revenue?

Using AI internally is only half of the opportunity.

The next challenge is turning AI knowledge and experience into something customers will actually buy.

I don’t think simply offering “AI consulting” or “prompt engineering” is enough.

We need packaged outcomes.

For example:

AI Readiness Assessment
AI Governance Foundation
Microsoft 365 Copilot Readiness and Deployment
AI Productivity Workshop
Business Process Automation
Custom AI Agents
Managed AI Services

We’ll work through customer discovery, demonstrations, packaging, pricing, ROI and the increasingly common objection:

“We’re already using ChatGPT.”

The goal will be for every MSP to leave this session with the foundations of three AI services that could be taken to customers.

Week 4: Operating the AI MSP

Turn the ideas into action

The final week brings everything together.

We’ll explore areas including:

AI governance
customer data protection
identity and access
Microsoft Purview
DLP
Shadow AI
agent governance
human oversight
AI acceptable-use policies
quality assurance
measuring AI ROI
developing staff skills
internal AI champions
continuous improvement

Most importantly, every MSP should finish January with a:

90-Day AI MSP Transition Plan

That could look something like this.

Days 1–30: Adopt

Start internal AI adoption, establish governance, train staff and identify repeatable use cases.

Days 31–60: Build

Package offerings, create demonstrations, establish pricing and identify pilot customers.

Days 61–90: Sell

Deliver pilots, measure results, capture case studies and start converting successful projects into managed services.

The question at the end of Summer School will be very simple:

What is your MSP going to do differently on Monday morning?

Constant Recording. Constant Iteration.

There’s another idea I want to explore throughout Summer School.

Record → Analyse → Improve → Repeat

Subject to appropriate privacy, consent and governance, MSPs generate enormous amounts of useful information every day:

customer questions
support interactions
meetings
sales conversations
customer objections
procedures
documentation
repetitive tasks
successful prompts
failed approaches
automation opportunities

Historically much of that information disappeared as soon as the conversation or interaction ended.

AI potentially changes that.

Activity can become knowledge.

Knowledge can produce insight.

Insight can drive automation.

Automation can produce better processes.

That leads to a principle I want to explore throughout Summer School:

Constant recording. Constant iteration. Constant improvement.

You’ll be doing, not just watching

I don’t want this to be four webinars where everyone watches presentations for two hours.

Each session will combine:

current AI developments
key concepts
live demonstrations
MSP-specific examples
practical workshops
group discussion
take-home challenges

There will also be work between sessions.

After Week 1

Identify 20 repetitive activities inside your MSP.

After Week 2

Select five and experiment with AI.

After Week 3

Have an AI-focused conversation with three customers.

After Week 4

Choose one AI service to launch.

The goal isn’t simply to attend Summer School.

It’s to start building your AI MSP during Summer School.

What will it cost?

I’m proposing to price Summer School per MSP rather than per person.

That’s deliberate.

I’d much rather an MSP owner bring a technical lead, service manager or salesperson along so that multiple people inside the business understand what needs to change.

Each registration will therefore cover up to three people from the same MSP.

Proposed pricing

Registration	Price + GST	Saving
Standard	A$895	–
Patron member	A$795	A$100
AI Dojo member	A$745	A$150
Patron + AI Dojo member	A$645	A$250

For those who are members of both Patron and AI Dojo, you’ll receive the special combined-member price rather than having to work out multiple overlapping discounts.

Member prices won’t stack with other promotional offers.

I’m also considering an additional post-Summer School implementation clinic for people who are members of both Patron and AI Dojo.

What’s included?

My current plan is for registration to include:

four live two-hour sessions
up to three participants from the same MSP
session recordings
practical worksheets
templates
AI MSP planning resources
AI service development frameworks
exercises to complete inside your MSP
your own 90-Day AI MSP Transition Plan

The emphasis throughout will be firmly on practical outcomes rather than AI theory.

Who is Summer School for?

I’m designing this primarily for:

MSP owners and principals
practice managers
technical leaders
service managers
sales and business development leaders

You certainly don’t need to be an AI expert.

In fact, that’s rather the point.

If you’re asking questions such as:

What does AI actually mean for my MSP?

Where should I start?

How should we use AI internally?

What AI services should I take to customers?

How can we make money from this?

How do we manage the security and governance risks?

How do I stop AI becoming another technology distraction?

then this is exactly the sort of program I’m planning.

Interested? Register your interest now

At this stage I’m asking MSPs to register their interest.

There’s no commitment simply from expressing interest. It will help me gauge demand for the January program and keep interested people informed as the final agenda, registration arrangements and supporting material are confirmed.

Register your interest in MSP Summer School 2027

If you’re considering joining me in January, register your interest now so I can keep you updated as the program takes shape.

The goal

I’m not going to promise that eight hours of Summer School will magically transform an MSP.

I think there’s a much more useful objective.

By the end of January, I want participating MSPs to understand:

Where they are now.

Where AI could take their business.

What they should use internally.

What they could sell to customers.

What they shouldn’t do.

And, most importantly:

What they are going to do next.

Because the basic premise behind Summer School 2027 is straightforward:

MSPs have spent the last 20 years helping customers make successful technology transitions.
Now it’s our turn.

MSP Summer School 2027

The AI MSP: Make the Successful Transition

6, 13, 20 and 27 January 2027
10:00 am–12:00 pm AEDT
Live online

Standard: A$895 + GST per MSP
Patron: A$795 + GST
AI Dojo: A$745 + GST
Patron + AI Dojo: A$645 + GST

Up to three attendees from the same MSP.

Register your interest

Your Market Needs a Mayor. Why Not You?

A professional standing confidently in a busy town square at golden hour as people turn to them for guidance

Most MSPs I talk to want to be seen as the leader in their patch. They want the referrals, the respect and the clients who call them first. Then they try to get there by being louder. More ads, more logos on more slides, more posts about how great they are. I think that misses the point. Leading a market isn’t a title you claim. It’s a job you do. Think of it as being the mayor of your town, and the mayor’s real job has never been prestige. It’s service. Whoever is most useful gets the role.

Usefulness beats volume

Your clients are drowning in noise right now. Copilot keeps changing. Every week brings a new security scare. Microsoft licensing still confuses people who have bought it for a decade. Nobody needs another voice shouting. They need someone calm who makes sense of it all.

I wrote earlier about how to make your business easier to buy. This is the same idea seen from the other side. When you’re consistently the person who explains things clearly, buying from you stops feeling like a risk. People already trust your judgement before they ever see a quote.

Three jobs every mayor takes on

The way I see it, the work comes down to three habits.

Turn fear into confidence. When a scary phishing story hits the news, don’t wait for panicked emails. Send clients a short note covering what it means for them, what you’ve already checked in Entra and Defender, and the one thing they should do.
Turn uncertainty into clarity. Picture running a twenty-minute monthly Copilot briefing in Teams. Show what changed, what’s worth trying in Outlook or Word, and what to ignore. No pitch, just clarity.
Answer before they ask. If Microsoft is about to change something in Teams or Outlook, you already know the question your clients will raise. Put a plain-English explainer in their inbox first. When licensing shifts again, give them a one-page summary in SharePoint showing what it means for their seats and their budget.

None of this needs a marketing department. It needs attention and a willingness to share what you already know. Copilot can even help you draft these updates faster, as long as the judgement in them is yours.

The rewards follow the service

Here’s what I’ve seen over many years. Status, influence and revenue rarely go to the loudest operator in town. They drift towards the person everyone already relies on. When people know you’ll tell them the truth, they bring you their problems. That’s a far stronger position than any campaign can buy.

It also changes how you sell, or rather how little you need to. In Stop Selling. Start Letting People Decide. I argued that pressure drives good clients away. Being genuinely useful is the opposite of pressure. You give first, consistently, and let people come to you when they’re ready.

Being useful also compounds. Every clear explanation makes the next one more trusted. Every early warning makes clients a little more likely to forward your notes to a colleague. Over time you’re no longer one provider among many. You’re the person the town turns to.

Take the job

So here’s my challenge. Pick your market, whether that’s a suburb, an industry or a niche within Microsoft 365. Then commit to being the most useful person in it. Start this month with one briefing, one explainer or one early warning. Nobody is going to hand you the mayor’s chain. You earn it by showing up and serving. The job is open. Take it today.

Need to Know podcast – Episode 373

In this episode, I look ahead to Microsoft Ignite and the continuing evolution of Copilot, Work IQ, AI agents and cybersecurity, before exploring a bigger question: is AI actually making businesses better, or simply helping them do more things faster? AI isn’t magic pixie dust that can fix broken processes. Before automating, businesses need to identify bottlenecks, simplify and document processes, establish measurable outcomes and decide where AI genuinely adds value. The real opportunity isn’t generating more emails, documents and automation, but using AI to create better outcomes, reclaim valuable time and continuously improve the way the business operates.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-373-effectiveness/

Subscribe via iTunes at:

https://itunes.apple.com/au/podcast/ciaops-need-to-know-podcasts/id406891445?mt=2

or Spotify:

https://open.spotify.com/show/7ejj00cOuw8977GnnE2lPb

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show

Resources

CIAOPS Need to Know podcast – CIAOPS – Need to Know podcasts | CIAOPS

X – https://www.twitter.com/directorcia

director@ciaops.com

CIAOPS Blog

Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron

CIAOPS AI Dojo

CIAOPS weekly news update – CIA Brief – CIAOPS

CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS

Get your M365 questions answered via email

Join my email list

A special thanks to the CIAOPS Patron community for making this podcast possible. You can find the benefits of a subscription to the community and become a member at https://www.ciaopspatron.com

Copilot & AI

Security

Microsoft 365 & Partners

From CIAOPS

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.

CIA Brief 20261107

Security

Threat actors use agentic AI tooling to find and abuse exposed secrets
Microsoft has seen attackers use the ARTEX agentic framework to scan public GitHub repos for credentials and API keys, then act on them, in one case going from a GitHub scan to exfiltrating Azure Key Vault data in five minutes. Since 28 October it has also seen service principal sign-ins from 199.19.77[.]84 using stolen multi-tenant app credentials to reach downstream tenants. Hunt service principal and non-interactive sign-ins for the listed IPs in every tenant you manage, and rotate any secret that has ever touched a repo.
https://www.microsoft.com/en-us/security/blog/2026/11/05/threat-actors-use-agentic-ai-tooling-to-find-and-abuse-exposed-secrets/

Inside a malicious Claude Code-branded extension and its persistent SSH backdoor
A tampered copy of the Claude Code extension (versions 2.1.312 and 2.1.313) sat in the Cursor extension marketplace for about 11 hours on 29 October, adding an attacker SSH key, enabling SSH, opening a reverse tunnel and setting up persistence. The Visual Studio Marketplace and npm packages weren’t affected. If your team or clients use Cursor, check for those versions and remember the keys and persistence can be left behind even when the tunnel failed.
https://www.microsoft.com/en-us/security/blog/2026/10/30/inside-malicious-claude-code-branded-cursor-extension-persistent-ssh-backdoor/

Email threat landscape: Q3 2026 trends and insights
Microsoft detected about 7.3 billion email phishing threats in Q3, with September up 41% on August, and CAPTCHA-gated phishing coming back via SVG attachments. The standout finding is that around 129 million spoofed messages were delivered because org or user exceptions overrode protection even after they failed authentication. Good reminder to go and audit those “just allow this sender” exceptions in every tenant.
https://www.microsoft.com/en-us/security/blog/2026/11/05/email-threat-landscape-q3-2026-trends-and-insights/

What exploited vulnerabilities have in common: A data-driven analysis of real-world attacks
Of roughly 383,000 CVEs disclosed since 1999, only about 2,000 (around 0.5%) have been exploited in the wild, and attackers overwhelmingly go after remote code execution, privilege escalation and authentication bypass. Patching is slow while exploitation is fast, and AI will only shorten that window. Worth a look for prioritising patching by impact and exposure rather than just CVSS score.
https://www.microsoft.com/en-us/security/blog/2026/11/02/exploited-vulnerabilities-common-data-driven-analysis-real-world-attacks/

Fake-download campaign uses trojanized installers to deliver monetization payloads
People searching for cracked software, free games and activators are getting trojanised installers that silently turn their machines into proxy nodes, distributed-computing workers or hosts for bundled “offers”. Nothing groundbreaking, but it’s exactly the stuff that turns up on staff laptops. Turn on potentially unwanted application protection in Defender and block untrusted software sources.
https://www.microsoft.com/en-us/security/blog/2026/11/03/fake-download-campaign-uses-trojanized-installers-deliver-monetization-payloads/

What’s new in Microsoft Security: November 2026
This month’s Intune and Defender roundup is heavy on agent security: Dynamic Permissions that scope an agent’s authority to its task, Dynamic Agent Risk and Dynamic Conditional Access, plus Microsoft Execution Containers (MXC), now generally available, to contain what agents can touch at the OS level. There are also endpoint elevation and Exposure Management updates. Still early for most SMBs, but this is the toolkit you’ll need once clients start running agents.
https://www.microsoft.com/en-us/security/blog/2026/11/05/whats-new-in-microsoft-security-november-2026/

Microsoft 365 & Windows

Introducing SharePoint tools in Work IQ
More than 60 native SharePoint operations are now in public preview through the Work IQ MCP server, so Copilot, Copilot Studio and other agents can find, create, organise and share SharePoint content directly. Microsoft says task pass rates went from 70.1% to 84.6% while using 16% fewer tokens. Worth a look if you’re building agents for clients, but remember they’ll be acting on SharePoint with whatever permissions you give them, so tidy up oversharing first.
https://techcommunity.microsoft.com/blog/SPBlog/introducing-sharepoint-tools-in-work-iq/4569917

How Outlook Search is changing: ranking, resilience, and the feedback loop
Outlook now shows up to seven relevance-ranked results before falling back to date order, across classic Outlook (Current and Monthly Enterprise Channel), new Outlook, the web and mobile, with Mac following in November. Classic Outlook also leans on the local Windows index when the network is flaky. Good to know when users ring the help desk saying “search is broken” and it’s really just ranking differently.
https://techcommunity.microsoft.com/blog/outlook/how-outlook-search-is-changing-ranking-resilience-and-the-feedback-loop/4568760

Cloud & AI

Gemini 4 Carbon: our next frontier model
Google’s new frontier model leads on cybersecurity benchmarks for finding, exploiting and patching vulnerabilities, and is built for agentic tasks that run for days. Access is starting with a subset of cyber defenders and trusted partners, with wider release later at $2 per million input tokens and $10 per million output tokens. Still early, but models this good at exploitation are exactly why patch windows keep shrinking.
https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-carbon/

Humanist AI in practice: A public consultation on our Code of Conduct for MAI Models
Microsoft AI has published a first draft of the code of conduct that governs how its MAI models are trained and how they should behave once deployed, and is asking for public feedback. It’s built around Mustafa Suleyman’s idea of AI that is “subordinate, aligned, and contained”. Nothing groundbreaking for day-to-day work, but it’s useful context when clients ask how Microsoft’s own models are governed.
https://microsoft.ai/news/mai-code-of-conduct/

Fair use benefits everyone
OpenAI has rounded up the amicus briefs filed in support of fair use in the New York Times lawsuit, from library groups, the EFF and law professors through to the US Government. The outcome will shape whether AI training on copyrighted content stays lawful. Still early, and it’s one side’s argument, but it’s a case worth following because it affects the tools every client is adopting.
https://openai.com/index/fair-use-benefits-everyone/

Giving every team a data scientist with Grok Bot
SpaceXSI’s data science team built Data Bot, a shared Team Bot that it teaches through skills covering metrics, experiments and query logic, so anyone can query the warehouse and get answers the way a data scientist would. Experts improve the skills once and everyone benefits. Worth a look as a model for MSPs: package your team’s know-how into a shared bot instead of being the bottleneck.
https://x.ai/news/data-bot

Elon Musk throttles Grok Bot limits due to ‘unsustainably high’ costs
Over Halloween weekend some Grok Bot users found their weekly usage limits suddenly maxed out, and Musk confirmed it was deliberate because the cost of serving it was “unsustainably high relative to revenue”. No word yet on what the limits will be going forward. Good reminder that AI pricing and quotas are still moving targets, so don’t build client services that assume today’s limits.
https://techcrunch.com/2026/11/02/elon-musk-throttles-grok-bot-limits-due-to-unsustainably-high-costs/

How AI agents run insurance’s back office
Harper describes always-on ambient agents that wake on events, work on their own cloud computer and drive carrier websites that have no API, the way a broker would. Since September an agent has helped bring more than 200 small businesses current with their premium-finance lender, with a person still signing off before money moves. Swap “carrier portal” for “vendor portal” and you can see how much MSP back-office work this could take on.
https://www.harperinsure.com/engineering/ambient-agents/

Other

What Happens to MSPs When Grok Bot Can Do the Work?
My latest post takes Harper’s account of running its back office on ambient agents and asks what that means for MSPs when ticket triage, remote repair, tenant checks and reporting can be packaged up and shared. If the instructions become a template anyone can download, the value has to sit somewhere else. I look at what’s left for the MSP, the vendor and the customer.
https://blog.ciaops.com/2026/11/06/what-happens-to-msps-when-grok-bot-can-do-the-work/

How Grok Bot Can Resolve Help Desk Issues Through Remote Desktop
My latest post walks through having Grok Bot open a remote-support tool like TeamViewer or AnyDesk on its own computer, connect to an approved attended session and fix a user’s Outlook problem itself, then retest and write up the ticket. I also cover the guardrails: identity and consent checks, and treating inbound email as untrusted. It’s a workflow you configure and test, not something that happens just because the bot has an inbox.
https://blog.ciaops.com/2026/11/06/how-grok-bot-can-resolve-help-desk-issues-through-remote-desktop/

One Prompt, Three Tenants: The Benefits of Grok Bot Group Chat
My latest post shows how I put three tenant bots into one Grok Bot group chat and ran Microsoft’s exposed-secrets hunting guidance across all of them with a single prompt. Each bot checked its own tenant and the answers came back side by side. I also explain why an invalid or expired secret error on its own doesn’t prove compromise.
https://blog.ciaops.com/2026/11/06/one-prompt-three-tenants-the-benefits-of-grok-bot-group-chat/

After hours

SpaceX – “GO FOR ORBIT” Documentary – https://www.youtube.com/watch?v=wlWF7kJokvk

Editorial

If you found this valuable, the I’d appreciate a ‘like’ or perhaps a donation at https://ko-fi.com/ciaops. This helps me know that people enjoy what I have created and provides resources to allow me to create more content. If you have any feedback or suggestions around this, I’m all ears. You can also find me via email director@ciaops.com and on X (Twitter) at https://www.twitter.com/directorcia.

If you want to be part of a dedicated Microsoft Cloud community with information and interactions daily, then consider becoming a CIAOPS Patron – www.ciaopspatron.com.

Watch out for the next CIA Brief next week

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.