Measure What Moved

I have sat through enough business debriefs to know the pattern.

Someone explains how busy they were. The late nights. The campaign tweaks. The tools tested. The sheer amount of motion involved.

Then I ask the only question that really matters.

What changed?

Activity feels comforting because it proves something happened. It gives people something to report. It fills meetings, updates, and weekly summaries. But activity is not progress. You can have hardworking people and still be drifting sideways.

Effort is not the scorecard

I am not dismissing hard work. Effort matters when it is pointed at the right target. The problem is when effort becomes the defence for poor results.

A marketing push that produces almost no qualified leads is not a success because the team spent days on it. A support process that burns hours but leaves customers waiting is not working because people are “doing their best”. A sales pipeline full of conversations but no movement is not healthy because everyone is busy.

That is why I keep coming back to measurement. Not because I love dashboards for the sake of dashboards, but because measurement forces honesty. It removes the storytelling that creeps into business discussions. When the number is sitting there in front of everyone, the conversation changes.

The question shifts from “who tried hard?” to “what actually improved?”

Make the work visible

One of the biggest mistakes I see businesses make is leaving performance hidden in private inboxes, personal spreadsheets, and half-remembered conversations.

If sales numbers live in one person’s Excel file, the business does not really have a sales view. If customer follow-ups are buried in Outlook, the business does not really have a follow-up process. If project blockers only surface during a meeting once a week, the business is accepting delay as normal.

Microsoft 365 gives you ways to bring that work into the open. Put the shared tracker in SharePoint. Pin it in Teams. Use Planner for ownership. Use Excel to track the result, then ask Copilot in Excel to identify trends, gaps, and outliers. Use Copilot in Teams after the meeting to summarise decisions and actions, then compare those actions against the numbers next time.

That is not more admin. It is fewer hiding places.

What gets reviewed gets improved

The real discipline is not building the dashboard. Anyone can throw together a colourful report and feel productive for an afternoon. The discipline is reviewing it consistently, asking uncomfortable questions, and changing behaviour because of what it shows.

If a campaign is not producing leads, stop admiring the effort and fix the offer, the audience, or the follow-up. If service tickets keep backing up, stop saying the team is flat out and find the bottleneck. If Copilot is being rolled out, do not just count licences. Measure whether proposal turnaround, meeting follow-up, reporting quality, or response times are improving.

That is where Copilot becomes useful. Not as another shiny thing to justify, but as a way to reduce the drag between seeing a problem and doing something about it. Summarise the data. Draft the follow-up. Build the first version of the report. Help the team inspect the work faster.

But the human still has to care about the outcome.

The blunt test

Do not tell me how busy you were. Show me what moved.

If the number improved, understand why and repeat it. If it did not, stop decorating failure with effort and make a better decision.

A good business does not reward invisible busyness. It rewards useful progress.

That only happens when the work is visible, the numbers are reviewed, and people are honest enough to act on what they see.

Is Copilot Listening to Every Meeting? The Reality Is More Complicated

Every few weeks someone asks me a variation of the same question.

“Is Microsoft Copilot recording all my meetings?”

The concern is understandable. AI is becoming more capable, meeting summaries appear almost instantly, action items seem to materialise out of nowhere, and people naturally wonder whether Microsoft is quietly capturing everything that happens in Teams. Sometimes the question goes a step further: “Does it do this even if I don’t have a Copilot licence?”

In my experience, the answer is far less dramatic than many people expect.

The concern isn’t really about Copilot. It’s about visibility.

The Difference Between a Meeting and a Recording

I think a lot of confusion comes from people bundling several different technologies together and calling them all “Copilot”.

A Teams meeting can exist without being recorded.

A Teams meeting can be transcribed without being recorded.

A Teams meeting can be recorded and transcribed.

And Copilot may or may not be involved at all.

That’s an important distinction.

Copilot doesn’t magically create information from nowhere. It works with the information available to it. If your organisation has enabled meeting transcription or recording, that’s where much of the content comes from. Copilot can then use that information to answer questions, create summaries, identify action items and help participants catch up.

Without that underlying data, Copilot has far less to work with.

The key point is that recording and transcription settings are administrative decisions. They aren’t automatically triggered simply because somebody owns a Copilot licence.

What About People Without Copilot?

This is where things often become misunderstood.

I’ve spoken with organisations where only a handful of staff have Microsoft 365 Copilot licences, yet meeting transcripts still exist across the business. When employees see AI-generated meeting summaries, the assumption is that Copilot must be capturing everything.

In reality, those organisations may have enabled Teams transcription or recording policies independently of Copilot.

Think about it this way. Your ability to access information and Microsoft’s ability to store information are not the same thing.

Someone without a Copilot licence may still participate in a meeting that is being recorded or transcribed. The meeting data exists because the meeting organiser or organisation allowed that functionality. Whether an individual user has access to Copilot features is a separate licensing decision.

That’s a subtle difference, but an important one.

The Governance Question Most Businesses Miss

What I find interesting is that many organisations ask whether Copilot is recording meetings, but they rarely ask who should have access to the resulting information.

That’s the more important conversation.

If meeting recordings are stored in OneDrive or SharePoint, if transcripts are available through Teams, and if Copilot can surface information that already exists, then governance matters more than fear.

I’ve seen organisations spend hours debating AI risks while leaving years of meeting recordings scattered across Microsoft 365 with inconsistent permissions.

Copilot didn’t create that problem. It simply made the problem more visible.

A useful exercise is to ask Copilot in Teams or Microsoft 365 a question about a recent meeting and then investigate why the answer was possible. The answer usually points back to existing recordings, transcripts, shared files or meeting notes that were already being retained.

AI acts as a spotlight. It doesn’t necessarily create new information.

The Question I’m Watching Closely

As Copilot adoption grows, I think we’ll see a shift in how organisations think about meetings.

For years, many businesses treated meetings as temporary conversations. Once the meeting ended, most people assumed the discussion disappeared into the ether unless someone took notes.

That assumption no longer holds true.

Whether you’re using Copilot, Teams transcription, meeting recordings or a combination of all three, conversations increasingly become searchable organisational knowledge.

The question therefore isn’t whether Copilot is secretly listening to every meeting.

The better question is whether your organisation understands what meeting data is being captured, where it is stored, how long it is retained and who can access it.

That’s where the real risk lives.

And, just as importantly, that’s where the real value of Microsoft 365 Copilot begins.

Teams Sprawl Was Always Messy. Now It’s Costing Your Clients Answers.

Walk into almost any SMB that’s been on Microsoft 365 for a few years and open their list of teams. I’ll wager it’s long, it’s inconsistent, and at least a third of what’s there hasn’t had a message posted since someone left the business. There’s a “Project Handover”, a “Project Handover 2”, and a “Sales – DO NOT USE”. Nobody remembers who owns half of them.

For years I treated that as a tidiness problem — annoying, but low stakes. I don’t anymore. The moment a client turns on Microsoft 365 Copilot, that untidy structure stops being cosmetic and starts shaping the quality of the answers they get.

Fewer teams than the client thinks they need

The most common structural mistake I see is a team for every project. It feels organised in the moment and it ages terribly. Six months on, the client has forty teams, most of them half-dead, and no one can find anything.

The fix I push is boring and it works: a team should map to a group of people who work together regularly, not to a task. Channels carry the topics. So instead of spinning up “Q3 Campaign”, the marketing team already exists, and Q3 Campaign is a channel inside it. When the campaign ends, you archive a channel, not a whole team. The people, the files in the SharePoint site behind it, and the history all stay in one sensible place.

I tell clients to design the teams first and resist the reflex to create. Every new team is a new SharePoint site, a new permissions boundary, another thing to govern.

Private and shared channels are the other trap. They have their place, but I see them thrown around to hide a conversation between two people, and every one of them quietly spins up its own SharePoint site behind the scenes. I treat them as the exception, not the reflex. If half your channels are private, you haven’t structured a team — you’ve built a warren.

Ownership is a structural decision, not an afterthought

The other quiet failure is ownership. A team gets created by whoever had the idea, they leave, and now it’s an orphan — no owner, no one to manage membership, guest access frozen in whatever state it was left in.

I won’t stand up a team now without at least two owners named on day one. I set expiration and archiving policies so dormant teams get flagged instead of accumulating forever, and I lean on Purview and the group settings in Entra to keep naming and guest access consistent across the client’s tenant. Structure isn’t just the shape of the teams. It’s who’s responsible when the shape needs to change.

Structure is what Copilot actually reads

Here’s the part that’s changed my thinking. When a client asks Copilot in Teams to summarise a project or pull together what was decided, Copilot reads across their channels, chats and the files sitting in those SharePoint sites. If that content is scattered over a dozen abandoned teams with three copies of the same document, the answer comes back vague or wrong — and the client blames Copilot.

It isn’t Copilot. It’s the structure underneath it. A tidy, well-owned set of teams is the difference between a genuinely useful summary and a confident piece of nonsense.

So my order of operations for clients has flipped. I do the Teams structure work before we switch Copilot on, not after they complain. Get the containers right, get ownership right, get the content living in the right place — then let Copilot loose on something worth reading.

Tidy was always nice to have. Now it’s what makes the AI worth paying for.

The Answer Is Never "More"

Every business owner I talk to has the same instinct when something isn’t working. Add something. Not enough leads? Launch a new offer. Service slipping? Hire another person. Growth flat? Spin up a new program, a new campaign, a new line of work. Adding feels good. It feels like progress. It costs almost nothing in the moment, and it gives you something to point at when someone asks what you’re doing about the problem.

The trouble is that adding is the cheap part. Keeping the thing alive afterwards is where the real bill lands.

Adding is light, owning is heavy

A new offer takes an afternoon to design and an email to announce. But now it needs pricing, delivery, support, a place in your onboarding, a line in your reporting, and a person who owns it when it breaks. The new hire fills a gap on Monday and becomes a salary, a review cycle, and a management responsibility by Friday. None of that weight shows up on the day you make the decision. It accumulates quietly, one addition at a time, until you’re carrying a load you never consciously agreed to.

I see this constantly in the MSP world, because our whole industry is built on saying yes. A client asks for one more thing, and it’s easier to absorb it than to have the awkward conversation. Multiply that across a few years and a few dozen clients, and you end up with a service catalogue nobody can fully explain and a delivery model held together by the memory of whoever happens to still work there.

How the tangle gets built

Nobody sets out to build a mess. It happens in sensible-looking steps. A bolt-on tool here. A side agreement there. A special process for one customer that quietly becomes the process for everyone. A department that exists because two years ago a problem needed an owner. Each layer made sense on its own. Stacked together, they form something heavy and strangely fragile, and at some point you realise you’ve become the load-bearing wall. Pull you out and the whole thing sways.

That’s the part that catches people off guard. You set out to build a business that runs without you, and instead you’ve built one that can’t run at all unless you’re sitting in the middle of it, holding the seams together.

Subtraction is a skill worth practising

The harder, more valuable move is taking things away. Killing the offer that earns little and costs plenty. Retiring the program that three people use. Saying no to the request that doesn’t fit, even when yes would be easier today. Subtraction rarely feels like progress in the moment, which is exactly why so few owners do it. But a smaller, sharper business is far easier to run, sell, and live inside than a sprawling one.

You can’t subtract what you can’t see, though, and most owners genuinely don’t know what they’re carrying. This is where I’ve found Microsoft 365 quietly useful — not as a fix, but as a way to make the weight visible. Ask Copilot in Teams to summarise every service, project, and recurring commitment mentioned across your channels over the last quarter, and you’ll get an honest inventory of what your business is actually maintaining versus what you think it is. Point Copilot at your shared mailbox and ask which client requests keep recurring and which offers nobody has touched in months. The answers are usually uncomfortable, and that’s the point.

From there, a single SharePoint page or a Loop component listing every active offer, tool, and program — with an owner and a last-reviewed date against each — turns “we should clean this up someday” into something you can actually work through. I’ve had owners use Copilot in Excel to model what dropping their two worst-performing services would do to revenue and to workload, and the workload relief almost always dwarfs the revenue hit. That’s the number that frees you to cut.

The lighter business wins

The goal isn’t a bigger business. It’s a business light enough that you can still lift it. Every time you reach for “more” as the answer, it’s worth pausing to ask whether you’re solving the problem or just burying it under another layer you’ll have to carry next year.

The best thing I’ve removed from my own business cost me nothing to delete and gave me back hours every week. Adding will always feel easier. Removing is what actually sets you free.

A Cleaner Way to Connect PowerShell to Microsoft Teams

If you still rely on Connect-MicrosoftTeams with an interactive sign-in every time you need to do some administration, you already know the frustration.

Scripts stop and wait for credentials. Scheduled tasks simply can’t run unattended. MFA prompts interrupt automation. And if you’re managing multiple tenants as an MSP, jumping between browser windows and authentication prompts quickly becomes tedious.

Microsoft has supported certificate-based authentication for Teams PowerShell for some time. The challenge hasn’t been the technology. The challenge has been the setup.

I’ve created a script that handles that process for me, removing most of the manual work and making certificate-based authentication something I can deploy consistently across customer tenants. The approach follows the same design philosophy I’ve been using for Exchange Online and other Microsoft 365 workloads: automate the plumbing so I can focus on the outcome. You can find it here:

https://github.com/directorcia/Office365/blob/master/o365-connect-tms-cert.ps1

and the documentation is here:

https://github.com/directorcia/Office365/wiki/Certificate-based-connection-for-Teams

What the Script Actually Does

The script operates in two primary modes.

The first mode, -GenerateLocalCertificate, creates a self-signed certificate on the local machine and exports the information needed for authentication. If required, it can also provision the Entra ID application automatically. The local certificate becomes the device’s identity when connecting to Teams PowerShell.

The second mode, -UseCertificateAuth, performs the actual Teams connection using the existing certificate and application registration. No password. No browser pop-up. No MFA prompt in the middle of an automated process.

The really useful feature is combining certificate generation with application provisioning. In a single operation the script can:

Create the local certificate
Authenticate to Microsoft Graph using device code authentication
Create or reuse an Entra ID application registration
Upload the certificate to the application
Create the required service principal
Assign the necessary permissions
Store the configuration details for future use

Tasks that typically involve multiple portals, several copy-and-paste operations, and more than a few opportunities to make mistakes can be reduced to a single repeatable process.

Why Certificate Authentication Matters

The biggest advantage is that you’re no longer tying automation to an admin account.

Traditional approaches often depend on an account that someone logs into interactively. That works fine until MFA settings change, conditional access rules are updated, or the account password expires.

Certificate authentication shifts the trust model. Instead of trusting a username and password, Microsoft validates the certificate installed on the machine against the certificate registered in Entra ID. If they match, the connection succeeds. If they don’t, access is denied.

That makes the solution both more secure and more reliable.

For MSPs, it also provides a cleaner operational model. Each technician workstation can have its own certificate while sharing the same application registration inside the customer tenant. If a machine is retired or a staff member leaves, removing the associated certificate immediately blocks access from that device without affecting anyone else.

The MSP Advantage

This is where the approach starts to shine.

A common question is whether every machine requires a separate application registration. The answer is no.

The design I prefer is a single Teams application per tenant with multiple certificates attached to it. Each device gets its own unique certificate, but all of them authenticate through the same application registration. That keeps administration simple while still maintaining proper separation between devices.

When a new technician needs access:

Run the provisioning process.
Generate a new certificate.
Associate it with the existing application.
Start working.

When access needs to be removed:

Delete the certificate association.
Access from that machine immediately stops.

No password resets. No account changes. No disruption for other administrators.

Getting Started

If you’re still connecting to Teams PowerShell interactively for daily administration, I’d encourage you to investigate certificate-based authentication.

The technology isn’t new. What’s important is reducing the complexity required to deploy it.

The real benefit isn’t that you save a few clicks when connecting. The real benefit is that you create a repeatable, secure authentication framework that supports automation, improves operational consistency, and removes dependence on administrator credentials.

For MSPs managing multiple tenants, that’s a significant improvement.

The less time I spend authenticating, the more time I spend solving customer problems. And that, ultimately, is the point.

Consistency Doesn’t Show Up When Things Are Comfortable

A good month in an MSP can hide a lot. The pipeline is healthy, the techs are humming, the client tickets are getting closed, and Friday afternoon feels almost calm. In those weeks, every business looks disciplined. Every process looks tight. Every standard looks honoured.

That’s not consistency. That’s just a quiet stretch.

The real test arrives when something breaks — a bad migration, a difficult client, a tech walking out, a month where revenue doesn’t land. That’s when you find out whether your standards live in your head or live in the way your business actually behaves.

The discipline you don’t see in a good month

I’ve watched MSPs run beautifully for a quarter and then quietly drop the things that made them beautiful the moment work got heavy. The monthly client reviews stop. The patching cadence slips. The onboarding checklist becomes “we’ll get to that next week.” Nobody decides to lower the bar. It just happens, one small omission at a time, until what was a standard is now just a story you tell prospects.

What I’ve come to respect is the unglamorous stuff that keeps going regardless of mood. The same Monday standup at the same time every week. The same security baseline applied to every new tenant. The same call to a client at the same point in their lifecycle, even when there’s nothing wrong. Those rhythms only feel valuable when things get bumpy — and by then it’s too late to start them.

Build the rhythm, then defend it

This is where I think a lot of MSPs underuse what’s already sitting in their stack. A weekly cadence in Microsoft Planner with the same recurring tasks, surfaced through a Teams channel everyone actually opens, is more useful than a polished playbook nobody reads. A standing client review template in Word, kept in the same Teams tab month after month, builds a record that shows whether you actually turned up.

Copilot helps here in a way I didn’t fully appreciate until recently. Asking Copilot in Outlook to summarise a client’s last quarter of email before a review meeting takes ninety seconds and means the conversation starts with something real. Asking Copilot in Teams to recap the last three internal stand-ups before a leadership meeting means decisions don’t get re-litigated. Asking it to pull the highlights from a SharePoint site of project notes before a Monday catch-up turns ten minutes of digging into one minute of reading. The point isn’t the time saved — it’s that the rhythm becomes easier to maintain on the day you’d rather skip it.

Tools don’t create consistency. But the right ones lower the friction enough that you keep showing up on the days you don’t feel like it.

When nobody’s watching

The reason consistency is hard isn’t intelligence or capability. It’s that nobody claps for it. Doing the same review the same way for the eighteenth time in a row produces no dopamine. No client thanks you for the patches that didn’t cause an outage. No prospect signs because your internal documentation happens to be current.

But the MSPs I see growing steadily — not in spikes, but year after year — are almost always the ones doing the boring things on the bad days as well as the good ones. That’s the only kind of consistency that actually compounds, and it’s almost never visible from the outside until much later.

So the question I keep asking myself, and the one I’d put to anyone running an MSP right now, is simple. What did you still do well last month, when nothing was easy? That’s the answer that tells you who you actually are as a business.

Copilot in Teams meetings

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.

Your 15‑Minute Daily M365 Power Routine

“Transform your day in 15 minutes.”

Most people don’t have a productivity problem.
They have a starting problem.

The day kicks off reactively. Emails, Teams pings, half‑finished tasks from yesterday, and suddenly it’s 11am and you’re already behind. Not because you’re lazy or disorganised, but because you never took control of the day before it took control of you.

That’s where this comes in.

This is a simple, repeatable 15‑minute Microsoft 365 power routine you can run every morning. No new tools. No fancy systems. Just using what you already have – properly.

Do this consistently and you’ll stop feeling busy and start feeling deliberate.

The Rule

Before you touch email properly.
Before you open your tenth Teams chat.
Before you let someone else’s urgency define your priorities.

You run the routine.

Every. Single. Morning.

Minute 1–3: Outlook “My Day” – Reality Check

Open Outlook and bring up My Day.

This is where most people already go wrong. They either ignore their calendar completely or treat it as a suggestion rather than a commitment.

Look at:

Today’s meetings
Gaps between meetings
The real amount of time you actually have available

This isn’t about optimism. It’s about honesty.

If your calendar says you’ve got back‑to‑back meetings until 3pm, pretending you’ll “get some deep work done” before lunch is a lie you’ve told yourself too many times.

My Day shows you the truth. Accept it.

Minute 4–7: Microsoft To Do – Decide What Actually Matters

Now jump into Microsoft To Do.

Not your entire backlog.
Not your wish list.
Just today.

Ask one simple question:

“If I only got three things done today, what would move the needle?”

Flag or prioritise no more than three tasks. If everything is important, nothing is.

This is where most people sabotage themselves. They create a list that’s really just a guilt inventory. Don’t do that. Your job isn’t to remember everything. Your job is to progress the right things.

Everything else can wait.

Minute 8–10: Teams Check‑In – Reduce Noise Before It Starts

Send a short Teams check‑in.

This can be to:

Your team channel
A project chat
A key stakeholder

Something as simple as:

“Top priority today is X. I’ll be focused until lunch – ping me if urgent.”

This does two things:

It sets expectations (which reduces interruptions)
It forces clarity on your priorities

Most interruptions aren’t malicious. They’re caused by silence. A 60‑second message now can save you 20 distractions later.

Minute 11–15: Viva Insights – Protect Focus Time

Finally, open Viva Insights and block focus time.

Not “when I get a chance”.
Not “if the day allows”.

You schedule focus like you schedule meetings, because that’s what it is – an appointment with your most valuable asset: attention.

Even one 60–90 minute focus block changes the shape of the day. Without it, your time fragments. With it, work actually finishes.

If you don’t defend this time, nobody else will.

The Checklist (Save This)

Every morning:

Review Outlook My Day
Pick 3 priorities in To Do
Send a Teams check‑in
Block focus time with Viva Insights

That’s it.

No hacks. No dopamine tricks. Just discipline and consistency.

The Challenge

Follow this routine every morning for a week.

Not when you remember.
Not when it feels convenient.
Every morning.

Then ask yourself:

Did I feel more in control?
Did less work spill into the evening?
Did I stop reacting and start deciding?

If the answer is yes, you’ve just built a habit that scales better than any productivity app ever will.

If the answer is no, at least you’re now honest about how you’re starting your day.

Either way, you win.