The Command Line Is Quietly Coming Back

image

I had a quiet moment last week that made me stop and think. I was watching a younger colleague get something done in about thirty seconds — no mouse, no menus, no four browser tabs open. Just typed a sentence into a terminal, hit enter, and the work was done. It looked exactly like the way I used to work in the late nineties, except the thing on the other side of the prompt was now an AI.

That’s the part I keep turning over. For more than two decades we have been told the future is graphical. Click, drag, drop, swipe. Every product wanted to be more visual, more “intuitive”, more pointy and clicky than the last one. And now, very quietly, the command line is walking back into the room — with a tool like GitHub Copilot CLI under its arm.

Typing is faster than clicking, again

The reason this shift is happening isn’t nostalgia. It’s pace. When you can describe what you want in plain English and have a tool translate that into the right command, the whole “where is that menu again” tax disappears. I’ve watched people who genuinely could not tell you what grep does happily ask Copilot CLI to find every file on their machine that mentions a particular client, and get a clean answer in seconds.

That same pattern is now showing up everywhere I look in Microsoft 365. Copilot in Outlook is, in effect, a command line for your inbox. You type “find the email from the supplier about pricing last month and draft a reply” and you’re done. No folder hunting, no scrolling. Copilot in Excel does the same thing for data — you describe the pivot you want, the chart you want, the trend you want highlighted, and it happens. The mouse becomes optional.

The interface is becoming language

What I think we’re really watching is not a return to green text on black screens. It’s the recognition that human language is itself a pretty good interface. For years we tried to dumb computers down for people. Now we’re meeting in the middle. People type or speak what they want. The machine figures out the click path.

Look at Microsoft Teams. The new way to drive it isn’t to click through tabs and channels — it’s to ask Copilot what was decided in yesterday’s project meeting, who owes who an action item, and what changed in the shared OneNote since Friday. The chat box has quietly become the most powerful button in the application.

What it means for how we work

For business leaders this matters more than it might first appear. The people who get good at “talking” to their tools — whether that’s Copilot CLI on a developer’s laptop, Copilot in Word turning rough notes into a board paper, or Copilot in SharePoint pulling the right policy out of a thousand documents — are going to be visibly faster than the people still hunting through ribbons and right-click menus.

I’m telling clients to start treating prompt-writing as a normal workplace skill, the same way we once treated email etiquette. It is the new shortcut key.

What I’m watching next

The interesting question is whether this collapses the distinction between “technical” and “non-technical” users altogether. If everyone’s interface is a sentence, the playing field flattens fast. The command line never really left. It just learned to listen.

The Founder Is the Ceiling

image

I’ve watched plenty of MSP owners import a new strategy — a pricing model, a sales motion, an AI practice — and then sit back waiting for results that never quite arrive. The framework is fine. The consultant was competent. The slide deck is tidy. Nothing lands. After the third or fourth time you see this pattern, you start to suspect the strategy was never the problem. The person running it was running the same way they always had, with the same instincts, the same blind spots, the same calendar. And the strategy, for all its elegance, quietly gathers dust.

Strategies borrow their ceiling from the founder

Here’s the uncomfortable bit. Every strategy in your business is quietly capped by whoever owns it at the top. A sales playbook built for disciplined follow-up doesn’t survive contact with a founder who hates picking up the phone. A managed services model built around proactive account reviews doesn’t work for an owner who still treats quarterly business reviews as optional. A cyber practice built on hard conversations about risk doesn’t get off the ground when the founder is uncomfortable delivering bad news to clients. The strategy isn’t weak. It’s just being run through the wrong instrument. You can buy a better playbook, hire a better consultant, pay for a better PSA, and you’ll still end up with results shaped by your own habits. That’s not a criticism. It’s just mechanics. The business is a reflection of the person at the top, and the ceiling on your strategies is almost always the ceiling on you.

The tool is a mirror, not a transformation

This is where I see Copilot quietly doing more than most owners realise. Not as a productivity gadget — as a mirror. When I open Copilot in Outlook and ask it to summarise the week’s inbox, I’m confronted with what I’ve actually been spending my time on, not what I thought I was spending my time on. When I ask Copilot in Teams to pull the decisions out of a client meeting, I notice which decisions I keep ducking. When I use Copilot Chat to pressure-test a proposal before I send it, I catch lazy thinking I would have signed off on a year ago. None of that changes my strategy. It changes me. That’s the part that makes the strategy finally move. The upgrade isn’t in the tool. It’s in the habit of using the tool to confront how I actually work, then doing something about what I find. That is a very different thing to rolling Copilot out across the tenant and calling it a transformation.

The hardest part is seeing yourself

Most founders I talk to are genuinely willing to change their business. Far fewer are willing to change themselves. We’ll restructure the team, rewrite the service catalogue, and re-platform the ticketing system before we’ll look honestly at our own calendar, our own decision-making, or our own tolerance for avoidance. The interesting thing is that the same Microsoft 365 tools we’re selling to clients — Copilot, Loop, Planner, SharePoint — are the ones that expose our own patterns if we let them. A Loop page tracking your weekly commitments will tell you the truth about your follow-through in about a fortnight. That’s a confronting experience, and it’s where the real upgrade starts.

Before you import your next strategy, ask a harder question. What would I have to become for this to actually work in my business? If the honest answer is “someone I’m not yet”, the strategy isn’t the first thing that needs upgrading. You are. Everything else in the business eventually rises or falls to that line. That’s not an easy sentence to sit with. It’s also the one I keep coming back to whenever I watch a good strategy fail to stick.

What is connecting Copilot agents to Dataverse, Graph, and connectors, really?

image

When people hear “Copilot Studio agent,” they picture a chatbot. That’s the wrong mental model. A modern agent is a reasoning layer sitting on top of three very different pipes: your business data in Dataverse, your organisational content in Microsoft Graph, and the wider universe of SaaS via Power Platform connectors.

Each pipe has its own auth story. And that’s where almost every SMB and MSP rollout I see comes unstuck.

That’s not a configuration problem. That’s an identity problem dressed up as a configuration problem.

Step-by-Step: wiring an agent to the three pipes
Set the agent’s authentication first

Before you add a single tool, go to Settings → Security → Authentication in your agent. Pick Authenticate with Microsoft. This uses Microsoft Entra ID to identify whoever is chatting — and it’s the prerequisite for almost everything that follows.

Skip this step and your agent runs as nobody. Which means it can’t read Dataverse on the user’s behalf, can’t honour SharePoint permissions, and can’t call a connector as the signed-in user. Get the front door right and the rest gets easier.

Add a Dataverse table as knowledge

Open Knowledge → Add knowledge → Dataverse. You can wire up to 15 tables per agent. Two things that catch people out:

  • Dataverse search must be enabled on the environment first.

  • Add synonyms and glossary terms for any column where your users speak a different dialect to the schema.

“Why doesn’t it find my open opportunities?”

Because your column is called statuscode and your users say “stage.” Synonyms fix that.

Add a Microsoft 365 Graph connector for content

Graph connectors are the other knowledge model — they index external content (Jira, ServiceNow, file shares, intranets) into the same semantic graph that Copilot already uses for Teams, SharePoint, and mail. Set them up in the Microsoft 365 admin center → Search & intelligence → Connectors. ACL-based permission trimming is preserved, so users only see what they’re allowed to see. Microsoft has a clear overview here.

Notice what’s missing? Dataverse is agent-scoped knowledge. Graph connectors are tenant-scoped knowledge. Different governance owners. Plan accordingly.

Add a connector as a tool

In your agent, Tools → Add a tool → Connector. Pick a standard, premium, or custom Power Platform connector. Now the agent can act — create a row, post to Teams, hit your line-of-business API.

Tool = action. Knowledge = retrieval. Don't confuse the two.
Pick the right credentials mode

Every tool asks one question that quietly decides your security posture: Maker Credentials or End User Credentials?

  • Maker Credentials: the connection runs as you, the builder. Easy demos. Terrible for anything user-specific.

  • End User Credentials: each chatter authenticates with their own account. Slightly more clicks for users. The only sensible default for production. Details here.

My recommendation? Default to End User and only fall back to Maker when there’s a genuine service-account scenario — like reading a shared mailbox.

Why this actually changes behaviour

Here’s the real win. Once authentication is correctly threaded through the agent, the same prompt produces different, personally-relevant answers for every user — because it’s their identity flowing into Dataverse, their Graph results coming back, their connector permissions being honoured.

That’s not a chatbot. That’s a tenant-aware assistant.

The other thing I notice with clients: governance conversations get easier. “Who can see what?” becomes a question of existing Entra groups and Dataverse row security — not a brand-new permissions matrix you have to invent for the agent.

Get the auth pattern right once and every agent you build afterwards inherits it. Get it wrong and you’ll be unpicking the same mess for months.

Wire the pipes. Mind the credentials. Ship something your clients actually trust.

Align — Your Team Has To Be In On It

image

I’ve been watching a pattern play out in MSP after MSP lately, and it’s worth naming. The owner or managing director is genuinely switched on about AI. They’re up early on a Saturday tinkering with prompts. They’re subscribed to half a dozen newsletters. They’ve run a pilot on quoting, or proposal drafts, or ticket triage. They can tell you, with real confidence, what GPT-5 does differently to Claude.

Then Monday morning rolls around.

You walk past the techs’ desks and someone is printing a spreadsheet out to “have a proper look at it”. The account manager is manually copying fields from one system into another. The service coordinator is re-reading a long email thread for the third time trying to figure out what the client actually agreed to. Not one of them has opened an AI chat today. Maybe not this week.

The leader has moved. The business hasn’t.

The solo-operator trap

This is where most MSP AI journeys quietly stall. The owner is thinking AI-first. The team is still thinking the way they thought in 2022. And because the owner is the one doing all the experimenting, they can tell themselves a comforting story — we’re on it, we’re ahead of the curve, we’re investing in AI. On paper, yes. In the business, no.

Real adoption isn’t measured by how many prompts the boss has saved or how many pilots are running. It’s measured by what an average Tuesday looks like for the people doing the work. If the first instinct when someone hits a hard problem is to ring a colleague, send an email, or open a spreadsheet — AI hasn’t arrived yet. It’s just a hobby the owner has.

That’s a confronting thought, but it’s the honest one.

You are the coach now

The shift that moves the needle isn’t another tool or another pilot. It’s a change in your job description. At the next team meeting, you stop reporting on AI and start teaching it.

Walk your people through what you tried this week. Show them the prompt that didn’t work, then the one that did. Show them the output that saved you forty minutes on a scope. Let them see you thinking out loud. You don’t need to be an expert — you need to be visibly in motion. That’s what gives them permission to start moving too.

If you’re the most AI-literate person in the building and you keep it to yourself, you’re not leading. You’re collecting.

Make AI the front door

Here’s the non-negotiable I’d put in place this week, and it costs nothing. Every person in the business sets an AI chat — Claude, ChatGPT, or Gemini, pick one — as their browser homepage. Not Google. Not the intranet. Not the weather.

Every single time someone opens a browser, an AI chat window is the first thing they see. A blinking cursor, waiting for a question.

It sounds small. It’s not. Most of the friction stopping people from using AI isn’t capability, it’s habit. They forget it’s there. A homepage removes the remembering. It puts the tool under their nose, dozens of times a day, until asking it first stops feeling like a new behaviour and starts feeling like the normal one.

The real alignment test

So here’s the question I’d sit with. If I walked into your office on a random Tuesday and watched your team for an hour — not you, them — would I see an AI-first business, or would I see a business with an AI-first owner?

If the answer isn’t the same for both, that’s your next piece of work.

Copilot in Teams meetings

image

People keep telling me Copilot in Teams “writes notes for them”.

That’s not what it does. That’s what an action item list does.

What Copilot does is let you ask a meeting questions. Live, while it’s happening. Or three days later when someone CCs you in and asks for an opinion.

Most SMBs I work with have it switched on and have no idea. Staff have a Copilot license, the meeting has a transcript ticking along, and the Copilot pane sits there unused while everyone scrambles to take their own notes.

Notice what’s missing? The bit where someone actually uses it.

What is Copilot in Teams meetings, really?

It’s a question box that knows what was just said.

You open the Copilot pane during a call, type a question — what have we decided?, what did Sarah commit to?, am I even needed on this one? — and it answers from the live transcript.

After the meeting, that same pane becomes the intelligent recap: chapters, AI-generated notes, suggested follow-ups, and timestamps that jump you straight to the moment someone said the thing that matters.

That’s the whole product. Live Q&A on the meeting, plus a navigable recap after. There’s a broader catalogue of AI features in Teams, but this is the one that earns the license on day one.

Step-by-Step: Turning it on properly

Two things have to be true for any of this to work: a Copilot license on the user, and transcription enabled for the meeting. Without a transcript, the Copilot pane has nothing to read.

Here’s the order I run it.

Enable transcription in the meeting policy

In the Teams admin centre, go to Meetings → Meeting policies, open the policy that applies to your Copilot users, and switch Allow transcription to On. The default global policy is off in some tenants. Check.

Turn Copilot on in the same policy

Same screen, scroll down. Set Copilot to On with or without transcription for genuine flexibility, or On only with transcription if you want a paper trail every time. My recommendation? The second one, especially for any regulated client.

Set the room expectation

Drop one line into the meeting invite: This meeting uses Microsoft Copilot. A transcript will be generated. Teams shows attendees a banner anyway when transcription starts, but writing it once removes the awkward moment.

Show people the pane

Open a meeting. Click the Copilot icon in the toolbar. Ask it something live. Then do it again from the recap tab after the meeting ends. Two clicks. That’s the training.

Why this actually changes behaviour

The win isn’t the summary. The win is what people stop doing.

Here’s the real one. They stop typing notes mid-meeting. They stop joining meetings they didn’t need to be in, because the recap takes two minutes afterwards. They stop emailing what did we agree? — they ask Copilot, and it answers with a timestamp.

Can I just ask what I missed? Yes. That’s the whole point.

Copilot doesn’t replace the meeting. It replaces the scramble around the meeting.

For regulated clients, the privacy notes for intelligent recap are worth ten minutes — they’re the answer when a client asks “but is this safe?”

Copilot in Teams meetings isn’t there to take notes for you. It’s there to make notes optional.

If you’re not showing your SMB clients this in their next review, someone else will.

Copilot prompt libraries for your tenant

image

Most Copilot rollouts I see have a strange shape. The licences are bought. The admin centre is half-configured. And nobody is using it.

Six months in, a few power users are saving an hour a week. Everyone else opens Copilot, stares at a blank box, and closes the tab.

That’s not a Copilot problem. That’s a prompting problem.

And the worst part? Microsoft has already shipped the fix. Most tenants haven’t turned it on.

What is a tenant prompt library, really?

A prompt library is a list of known-good prompts pinned inside the Copilot experience itself. Your users see them when they open Copilot — in chat, in Word, in Excel, in Outlook, wherever you’ve published them.

Two layers matter for SMBs and MSPs.

The first is the Microsoft Copilot Prompt Gallery — the public set Microsoft maintains. Useful. Generic.

The second is promoted prompts — your own prompts, pushed to your own users from the Microsoft 365 admin centre. This is the layer almost nobody uses, and it’s the one that actually changes behaviour.

Think of it as the difference between handing someone a generic cookbook and putting a Post-it on their fridge that says “this is how we make pasta”.

Step-by-Step: publishing a tenant prompt library

Portal walkthrough, no PowerShell.

Open the admin centre

Sign in to the Microsoft 365 admin centre as a Global or Copilot admin. Expand Copilot in the left nav, then Settings, then Promoted prompts.

Write the prompt your users actually need

Don’t reach for a clever one. Reach for the boring one your help desk keeps explaining. “Summarise this week’s emails from my customers and group by client.” “Draft a weekly status update for my manager based on my meetings and Teams chats.” Plain English, written the way a non-technical user would actually type it.

Pin it to the right app

You can target the prompt to Microsoft 365 Copilot chat, Word, Excel, PowerPoint, Outlook, Teams, or OneNote. Pin one prompt per app where it’s actually useful. Five great prompts beats fifty mediocre ones.

Set the audience

Use a group, not “everyone”. Roll it to a pilot. Sales gets the sales prompts. Finance gets the finance prompts. The prompt is the training material.

Publish and watch adoption move

Promoted prompts surface at the top of the Copilot prompt UI for the assigned users within a few hours. Microsoft’s Copilot Prompt Gallery documents the surfaces they show up on.

Title: Weekly client summary
App:   Microsoft 365 Copilot chat
Prompt:
Summarise emails and Teams messages from
my customers this week. Group by client.
Highlight any unanswered questions.

Notice what’s missing? No mention of how Copilot does the work. No file picker. No talk of Work IQ. The user just asks once and gets the outcome. That’s the brief.

Why this actually changes behaviour

Most adoption programmes hand out PDFs nobody reads. Promoted prompts put the training inside the product, at the moment of use.

“I don’t know what to ask Copilot for.”

That sentence kills more rollouts than any licensing or governance issue. A prompt library answers it.

Three things shift the day you publish one:

  • New users see a starting point on day one instead of a blinking cursor.

  • Power users stop reinventing the same prompt twelve different ways.

  • You finally have a measurable, governable surface to iterate on.

That last one matters for MSPs. You can review the prompt library quarterly with your client, the same way you review a security baseline. Copilot doesn’t get tired. Use that.

For the deeper guidance on what makes a prompt land, Microsoft’s own write effective prompts page is worth lifting language from when you draft yours.

One closing thought

If you’re rolling out Copilot to a client and you haven’t published a single promoted prompt, you’re charging them for a tool and shipping them a blank page.

Promoted prompts aren’t there to teach people how to use Copilot. They’re there to remove the moment of not knowing what to ask completely.

Director or Doer? The AI Question Nobody’s Asking

image

Most of the AI conversations I have these days start the same way. Someone leans in and quietly asks, “Do you think AI is going to take my job?” I understand the worry — it’s everywhere, and it’s loud. But I think it’s the wrong question. The one worth asking is sharper and far more uncomfortable. Are you using AI, or is AI using you? That single reframing changes the whole game. And the window to land on the right side of it is narrowing faster than most people realise.

The Doer Trap

I see the Doer pattern everywhere. Someone types a rushed prompt, reads whatever comes back, tidies up a comma or two, and ships it. The email goes out. The deck gets shared. The summary lands in a meeting. The person feels productive because something got done — but they didn’t really direct any of it. The tool picked the angle, the structure, the tone, even the conclusion. They just drove the delivery truck.

The thing that makes this dangerous is that it feels like progress. Output is going up. Calendars are clearing. But the thinking is going down. The muscles that matter — judgement, taste, point of view — quietly shrink while everyone is busy celebrating how much faster the work moves. If AI is setting the pace, choosing the framing, and deciding what “good” looks like, you are no longer in charge of your own work. You are assisting it.

The Director Shift

The people I watch pulling away from the pack work very differently. They treat AI the way a good manager treats a capable team. They brief it properly. They tell it the audience, the constraint, the outcome they want, and what to leave out. They read the output the way an editor reads a draft — with scepticism, not relief. They push back. They ask it to try a sharper angle, to argue the opposite, to shorten by half. They know what great looks like before they ask for it, and they recognise when the answer is merely adequate.

Being the Director is harder. It takes domain knowledge, taste, and the patience to iterate. But the work that comes out the other side is genuinely yours. The ideas are yours, the standards are yours, the reasoning is yours. AI is doing the heavy lifting on the mechanics while you do the heavy lifting on the thinking. That’s the right shape of the partnership.

The Window Is Closing

Here’s what I think people underestimate. The gap between Directors and Doers is compounding. Every week spent actively learning how to brief, evaluate, and steer these tools is a week of skill you’re banking. Every week spent passively accepting output is a week of skill you’re quietly losing. Six months from now, a year from now, that gap will be visible from across the room — in the quality of decisions, the confidence of arguments, the crispness of output.

The people who dig in now, who actually invest the hours to learn this properly, aren’t just getting better at AI. They’re becoming more valuable than they were before AI existed. Their judgement is sharper. Their output is broader. Their leverage is higher. The people waiting for it to settle down are going to wake up behind, and it will take a lot more than a weekend of prompting tutorials to catch up.

So I’d stop asking whether AI is coming for your job. Ask instead who’s running whose day. Because that answer — today, this week, this month — is the one that decides where you end up.