Why Copilot works differently now (and why that’s a good thing)

If you’ve noticed that Microsoft Copilot feels different lately—especially inside Word, Excel, PowerPoint, or Outlook—you’re not imagining it.

Nothing is “broken”.
What’s changed is how Copilot is positioned, licensed, and governed.

And while change can be frustrating, this shift is actually a step forward for security, reliability, and trust.

Here’s what’s going on—in plain English.

The short version

Copilot is no longer a “free helper everywhere”.
It’s now treated as a proper business system, with clear rules around:

Who can use it
What data it can see
Where it’s guaranteed to work
How it’s secured and audited

That’s good news for organisations that care about their data.

What Copilot was doing before

In late 2025, Microsoft made Copilot Chat broadly available across Microsoft 365.
For many organisations, this meant:

Copilot appeared inside Office apps
Users experimented freely
Expectations rose quickly

While this was great for awareness, it also created problems:

People assumed Copilot was “free forever”
Capabilities varied by tenant size and workload
Security and governance were often misunderstood
Businesses struggled to tell the difference between trial and production use

What changed (and why)

Microsoft has now drawn a clear line between:

✅ Copilot Chat (Basic)

General AI chat
Limited guarantees
Not deeply integrated with your business data
Useful for exploration and light assistance

✅ Microsoft 365 Copilot (Premium)

Fully integrated into Word, Excel, Outlook, Teams, etc.
Grounded in your organisation’s data (emails, files, meetings)
Governed by your security, compliance, and access controls
Licensed per user, with predictable behaviour

This separation wasn’t about removing features—it was about making responsibilities clear.

Why this is a good thing for your business

1️ Consistency beats surprises

When Copilot is licensed properly, its behaviour is predictable.

It works where you expect it to work
It respects your data boundaries consistently
Users stop asking “why did it work yesterday but not today?”

That’s what businesses need.

2️ Security becomes visible (not optional)

Copilot doesn’t invent access to information.

It uses:

Your permissions
Your sensitivity labels
Your data loss prevention rules

If something looks risky now, it was already risky—Copilot just made it obvious.

That’s a feature, not a flaw.

3️ Responsibility stays with people

Copilot assists.
It does not replace judgment.

The new model reinforces that:

People remain accountable for decisions
AI output must be reviewed
Policies still apply

This protects both the business and the staff using it.

4️ AI is treated like any other system

No business runs email, accounting, or security tools without governance.

Copilot is now treated the same way:

Licensed intentionally
Enabled where it adds value
Governed like a business system—not a novelty

That’s how AI becomes sustainable.

What hasn’t changed

It’s important to be clear about this:

Copilot still doesn’t bypass permissions
Copilot doesn’t share data externally
Copilot doesn’t “learn” from your data for other customers
Copilot respects your Microsoft 365 security model

The fundamentals are the same.
The clarity is new.

What this means for your organisation

This is a good moment to pause and ask:

Who actually benefits from Copilot day‑to‑day?
Is our data organised well enough to support AI?
Do we understand what Copilot can and can’t see?
Are expectations set correctly with staff?

Answering those questions now avoids frustration later.

The bottom line

Copilot didn’t get worse.
It got more honest.

Microsoft has moved Copilot from:

“Try it everywhere”
to
“Use it properly”

That shift improves:

Security
Trust
Reliability
Long‑term value

And that’s exactly what businesses should expect from AI that works with their data.

The Question That Tells You What to Fix Next

There’s a deceptively simple question I keep coming back to when I talk to business owners, especially MSPs:

Am I demand constrained, or supply constrained?

In plain English:
Is your biggest problem “I can’t get enough clients”?
Or is it “If I had more clients, things would break”?

Most people think they know the answer. Many are wrong. And a surprising number have never stopped long enough to ask the question properly.

This matters, because these are two very different problems. Confuse them, and you’ll work very hard on the wrong thing.

Demand constrained: not enough clients

If you’re demand constrained, your bottleneck is sales and marketing. The phone isn’t ringing. Leads are inconsistent. Referrals have slowed. You’ve got capacity sitting idle.

The giveaway signs are obvious once you’re honest with yourself:

You (or your team) have time on your hands
Onboarding a new client feels exciting, not stressful
You’re discounting, chasing, or “just seeing what happens”
You spend more time tweaking services than talking to prospects

In this mode, polishing internal processes is mostly procrastination. Perfecting your PSA workflows or rewriting your SOPs for the fifth time won’t magically create demand. Neither will buying another tool “just in case”.

The uncomfortable truth?
If you’re demand constrained, you need to work on being seen, being clear, and being chosen.

That usually means:

Sharpening your message so people know exactly who you help
Saying no to being “everything to everyone”
Talking to customers and prospects more than your tools
Getting comfortable with selling, not hiding behind tech

Demand problems are uncomfortable because they expose mindset issues. Fear of rejection. Fear of being visible. Fear of being judged. That’s why so many business owners avoid them and retreat into “busy work”.

Supply constrained: growth would hurt

If you’re supply constrained, demand isn’t the problem. You could sell more. In fact, you probably already are. The issue is that growth feels fragile.

Adding one more client means:

Response times slip
The same fires keep reappearing
Only a few people really know how things work
You’re the bottleneck for decisions, approvals, or fixes

This is where things get dangerous. From the outside, the business looks successful. Revenue is up. The pipeline is full. But internally, it’s held together with duct tape and heroics.

If you’re supply constrained and you push harder on sales, you don’t get leverage — you get burnout.

This is the stage where “working harder” finally stops working.

The fix here isn’t more leads. It’s leverage.

That usually means:

Documented, repeatable ways of delivering outcomes
Fewer services, done better, not more options
Clear standards instead of tribal knowledge
Letting go of being the smartest person in every room

Supply constraints force you to confront control issues. If everything depends on you, growth will always feel unsafe.

The trap: fixing the wrong constraint

The real danger is misdiagnosis.

I regularly see MSPs who feel supply constrained, but are actually demand constrained. They blame process, tools, or staff when the real issue is inconsistent sales. So they over-engineer systems for a scale that never arrives.

I also see the opposite: businesses with strong demand that keep pushing sales harder, hoping revenue will magically fix operational cracks. It doesn’t. It just widens them.

Revenue hides problems. Scale reveals them.

You can’t outgrow a broken delivery model. And you can’t systemise your way out of obscurity.

Constraints change — your focus must too

Here’s the part most people miss:
Constraints move.

Early on, you’re almost always demand constrained. Later, if you do things right, you become supply constrained. That’s not failure — that’s progress.

The mistake is clinging to last year’s strategy because it once worked.

What got you from zero to one won’t get you from one to ten.

This is why the most successful business owners spend more time working on themselves than on their business. They’re constantly reassessing where the real bottleneck is — and adjusting their behaviour accordingly.

Not chasing shiny tactics. Not copying someone else’s playbook. But doing the honest internal work.

Ask the question. Answer it honestly.

So ask yourself, properly:

If I doubled my leads tomorrow, would things improve or collapse?
Where do I personally spend time because “it’s quicker if I do it”?
What problem am I avoiding because it feels uncomfortable?

There is always a constraint. The job isn’t to eliminate it — it’s to identify it and work on the right thing at the right time.

Growth isn’t about doing more.
It’s about fixing what’s actually in the way.

And that starts with asking the right question.

Exactly How SMBs Should Measure ROI from a Microsoft 365 Copilot Investment

Most SMBs “measure” Copilot ROI the wrong way.

They count prompts.
They quote vendor stats.
They say “people feel more productive”.

That’s not ROI. That’s vibes.

If you want to justify Microsoft 365 Copilot to an SMB owner, you need numbers that connect cost → behaviour → business outcome. Here’s exactly how to do that, step by step.

Step 1: Lock in the true cost (don’t wing this)

Before measuring return, be honest about investment.

For an SMB, Copilot cost is typically:

Copilot licence per user per month
Time spent on onboarding and training
Light data clean‑up (because Copilot will surface your mess)

Write this down as a monthly cost per user. That’s your baseline. No magic. No “later we’ll optimise”.

If you can’t clearly say “this is what Copilot costs us per user per month”, stop here.

Step 2: Pick only three measurable activities (not everything)

SMBs fail when they try to measure Copilot “everywhere”.

Don’t.

Pick three everyday activities where Copilot realistically shows up:

Email handling (Outlook)
Meetings (Teams)
Document creation (Word / PowerPoint)

Microsoft already collects behavioural data for these via Viva Insights and Copilot Analytics. You don’t need custom tooling or surveys. [learn.microsoft.com]

Step 3: Capture a before baseline (this is non‑negotiable)

You must capture a baseline before rollout or you’ll be guessing forever.

Do this for a pilot group (10–20 users is fine):

Average daily email time per user
Average meeting hours per week
Time to create a “standard” document (proposal, report, policy)

These numbers already exist in Viva Insights for email and meetings. For documents, do a simple timing exercise with 3–5 users. [petri.com]

Write them down. Freeze them. This is your “before” state.

Step 4: Measure the delta after 30 and 60 days

Now roll out Copilot properly (licences and training) and re‑measure at:

30 days
60 days

Look only for deltas, not absolute values:

Reduction in email time per day
Reduction in meeting time or improved meeting outputs (summaries used instead of re‑watching)
Faster first‑draft document creation

Ignore:

Prompt counts
“Active users”
Dashboard vanity metrics

Usage is not value.

Step 5: Convert time saved into capacity, not dollars

This is where most ROI models fall apart.

Do not say:

“We saved 5 hours per week, therefore we saved $X.”

Instead ask:

Did sales respond to leads faster?
Did projects finish earlier?
Did client work backlog reduce?
Did staff stop working unpaid overtime?

Example:

A 15‑person professional services SMB reduces document creation time by 30 minutes per day per consultant. That doesn’t mean “money saved”. It means one extra billable task per week without hiring.

That’s capacity gain. Owners understand that instantly.

Step 6: Track one business outcome per role

Different roles = different ROI.

Sales: speed to quote, proposal turnaround
Admin: email backlog, meeting follow‑up time
Management: decision latency (time from question to answer)

Pick one outcome per role, not ten. If Copilot isn’t moving the needle there, it’s not paying for itself.

Step 7: Do a simple sanity check at 90 days

At 90 days, ask three brutal questions:

Are fewer hours being wasted on low‑value work?
Are decisions and deliverables happening faster?
Would removing Copilot cause disruption?

If the answer is “no” across the board, the problem isn’t Copilot. It’s adoption, data hygiene, or training—not licensing.

Final reality check

Copilot ROI is not magic and it’s not automatic.

But when SMBs measure behaviour change first, then tie that to capacity and outcomes, Copilot becomes defensible, repeatable, and scalable—exactly how an SMB expects technology to behave.

If your ROI story can’t survive a sceptical business owner, it’s not finished yet.

The Coach Won’t Just Give You a Strategy. They’ll Give You a Mirror.

Most MSPs don’t have a strategy problem.

They have a self‑awareness problem.

If you’re honest, you already know what needs fixing in your business. You know which services are messy. You know where margins are leaking. You know which clients drain energy, which staff issues you’ve been avoiding, and which “temporary” workarounds have somehow become permanent.

What’s missing isn’t another framework, playbook, or shiny roadmap.

What’s missing is someone who will hold up a mirror and make you look at yourself.

That’s the real value of a coach.

Strategy Is the Easy Part

Every MSP conference, podcast, and LinkedIn post is overflowing with strategy.

Productise your services
Standardise your stack
Raise your prices
Niche down
Automate more
Hire better
Delegate sooner

None of this is new. None of it is secret.

Yet many MSPs stay stuck for years, implementing some of it, occasionally, when things calm down. Spoiler: things never calm down.

The issue isn’t that you don’t know what to do.

It’s that strategy doesn’t force behaviour change.

A mirror does.

The Mirror Is Uncomfortable (That’s the Point)

A good coach doesn’t just say, “Here’s what successful MSPs do.”

They say things like:

“Why are you still approving every invoice?”
“Why do you keep saying you want scale, but act like a firefighter?”
“Why are you blaming the team when you won’t let go of control?”
“Why are you still selling bespoke work when you claim to want freedom?”

That’s not advice. That’s reflection.

And reflection is confronting because it removes your favourite excuses.

You can’t hide behind tools, vendors, or market conditions when someone calmly points out that you are the bottleneck.

MSPs Don’t Stall Because of Technology

MSPs stall because of identity.

At some point, the skills that made you successful become the very things holding you back:

Being the best tech
Being the fixer
Being indispensable
Being the hero

Letting go of that isn’t a technical challenge. It’s an emotional one.

A coach doesn’t replace your thinking. They expose the gaps between what you say you want and how you actually behave.

That’s why coaching feels different from consulting.

A consultant gives answers.

A coach asks questions you’ve been avoiding.

You Can’t Out‑Learn a Behaviour Problem

Many MSPs respond to discomfort by learning more.

Another course.
Another book.
Another certification.
Another vendor demo.

Learning feels productive, but it’s often just procrastination in disguise.

A coach cuts through that by asking, “What are you going to do differently this week?”

Not next quarter. Not after the next hire. Not when the tool is fully deployed.

This week.

And then they remember what you said last time.

That accountability is the mirror.

Growth Starts With Brutal Honesty

The MSPs that grow sustainably aren’t smarter than everyone else.

They’re more honest.

Honest about their time.
Honest about their energy.
Honest about what they enjoy.
Honest about what they’re avoiding.

A coach helps you see patterns you’re too close to notice. Patterns in how you lead, sell, hire, and react under pressure.

That’s not comfortable work.

But it’s the work that actually changes outcomes.

If You’re Feeling “Stuck”, Look Inward First

If your MSP feels stalled, chaotic, or heavier than it should, don’t immediately look for a new strategy.

Look for a mirror.

Ask yourself:

Where am I the constraint?
What am I protecting that no longer serves the business?
What hard decision have I been delaying?

A coach won’t magically fix your MSP.

But they will help you see it — and yourself — clearly.

And clarity beats strategy every time.

Microsoft Fabric: Turning Your Business Data into Decisions (Without the Headaches)

Most small and medium businesses already have plenty of data.

It lives in your accounting system, your CRM, Microsoft 365, spreadsheets, and half a dozen other apps you rely on every day. The problem isn’t a lack of data — it’s that turning that data into clear, trusted answers is still harder than it should be.

That’s where Microsoft Fabric comes in.

Despite the grand name, Fabric isn’t about “big data” or enterprise complexity. It’s Microsoft’s attempt to fix a very real, very common SMB problem: why is it still so hard to get reliable answers from our own business systems?

The real problem Fabric is trying to solve

In most SMBs, reporting looks like this:

Sales has their numbers
Finance has a different set of numbers
Operations has spreadsheets that “mostly” line up
Meetings start with arguing over which report is correct

Even when Power BI is in use, it’s often built on fragile spreadsheets, duplicated datasets, or one‑off solutions held together by good intentions and caffeine.

The issue isn’t the tools — it’s the lack of a single source of truth.

What Microsoft Fabric actually is (in simple terms)

Microsoft Fabric is a single platform that brings together:

Data from all your systems
Secure storage for that data
Reporting and dashboards (via Power BI)
Analytics and forecasting
AI‑assisted insights

Instead of bolting tools together, Fabric gives you one shared data foundation that everything else plugs into.

Think of it as the difference between:

Twenty shared spreadsheets passed around by email
and
One trusted set of numbers everyone agrees to use

Why this matters for SMBs (not just big enterprises)

Fabric isn’t about doing more reporting. It’s about doing less work for better answers.

For SMBs, the benefits are very practical:

1. Everyone works from the same numbers

Sales, finance, and leadership stop arguing about whose report is right, because they’re all looking at the same underlying data.

2. Better use of Power BI

Power BI becomes a decision‑making tool, not just a chart generator built on shaky spreadsheets.

3. Faster answers to real business questions

Questions like:

Are we actually profitable by customer?
Which products are quietly costing us money?
Where are we growing — and where are we stalling?

become easier to answer without weeks of manual effort.

4. AI that’s useful, not gimmicky

Fabric includes AI features that help explain trends and surface insights — not replace your judgement, but support it.

What Fabric is not

Let’s be clear about expectations.

Microsoft Fabric is:

❌ Not a magic fix for messy data
❌ Not “set and forget”
❌ Not something every small business needs on day one

Fabric makes sense when your business:

Relies on multiple systems
Is growing or changing
Needs better visibility to make confident decisions

If Excel still works for you, that’s fine. Fabric is for when Excel no longer does.

The bigger picture

For years, businesses have collected more and more data while decision‑making hasn’t actually improved. Fabric is Microsoft’s attempt to close that gap — by simplifying how data is stored, shared, and analysed.

Used properly, it helps turn reporting from:

“What happened last month?”

into:

“What should we do next?”

And that’s where real business value lives.

Proximity Is Power — Assemble Your AI Circle

Every real jump I’ve made with AI has come from a conversation, not a course. Not a YouTube deep-dive, not a whitepaper, not a bookmarked article I told myself I’d read later. A conversation. Usually over coffee, sometimes over Teams, almost always with someone who’d already done the thing I was still circling. I’ve stopped treating that as a coincidence.

The shortcut nobody uses

There’s a strange reluctance to ask for help with AI. People will spend three weekends wrestling with prompts, rebuilding the same agent four times, watching another hour of tutorials — before they’ll send one message to someone who has already solved the problem.

I don’t know why we do this. Maybe it feels like cheating. Maybe we think we have to earn it the hard way. But the person two steps ahead of you isn’t guarding anything. In my experience, they’re usually thrilled someone asked.

Open your phone right now. Scroll through LinkedIn. Flick through your contacts. There will be one or two names who are visibly doing more interesting work with AI than you are. Send them a message today. Not next week. Today.

Trade something for their time

If the person you want to learn from is properly ahead — running real projects, shipping real results — their time is the scarce resource. So offer to pay for it. Offer to buy them lunch. Offer the hour the way you’d pay any other professional.

Most people will wave the money away and take the coffee. A few will charge you, and they’ll be worth every cent. What you’re really buying is a compressed version of their last twelve months of learning — the dead ends, the tools they quietly stopped using, the one prompt pattern that changed everything for them. You don’t get that from a blog.

Even if nobody ever takes your money, the offer changes the tone of the conversation. You’ve signalled you take their experience seriously. People respond to that.

Make it a ritual

One of the best things I’ve locked into my week is a small AI lunch. Five of us, give or take, turning up to compare notes on what we’re actually doing — what we built, what broke, what surprised us, what we’re quietly worried about. No agenda, no slides.

A year of those lunches is worth more than any conference I’ve been to. Cadence matters. A monthly catch-up drifts to quarterly. A weekly one stays locked in. You start showing up with something to share because you know the others will.

You don’t need five people. Start with two. Pick a day, pick a cafe, and put it in the calendar on repeat.

The real edge

The tools are mostly the same for everyone now. Access isn’t the differentiator it was twelve months ago. What separates the people genuinely getting somewhere with AI from the people still reading about it is the circle they’ve built around themselves.

Assemble that circle on purpose. Proximity really is power — and the people you sit next to, even on a call, will shape how far you go.

“No” Is a Complete Sentence (And a Bloody Good MSP Strategy)

The most successful MSP owners I know aren’t superhuman.

They don’t have more hours in the day.
They don’t wake up at 4:30am to journal, ice-bathe, and manifest ARR.
They’re not running some secret productivity stack you’ve never heard of.

What they have done is get brutally honest about one uncomfortable truth:

Every yes has a price.

And once you see that clearly, you start saying no. A lot.

Not because you’re lazy.
Not because you don’t care.
But because you finally understand that attention is your scarcest resource.

The Hidden Cost of “Sure, Why Not”

MSPs are especially bad at this.

We say yes to:

“Can you just jump on a quick call?”
“Can you have a look at this while you’re here?”
“This could turn into something big…”
“We’ve always done it this way for this client.”

Each one feels harmless in isolation.
Collectively, they’re lethal.

That “quick call” blows out to 45 minutes.
That “small favour” turns into ongoing unpaid support.
That “opportunity” drags you sideways for six months with nothing to show for it.

And suddenly you’re busy all day… but somehow still stuck.

Busy is not the same as effective.

Why the Best MSP Owners Say No More Than Yes

The sharpest operators I know have made peace with disappointing people.

They say:

No to meetings that could have been an email.
No to shiny tools dressed up as “game changers”.
No to custom work that doesn’t scale.
No to clients who drain energy, margin, and morale.
No to doing work outside their chosen lane.

Not aggressively.
Not rudely.
Just calmly. Clearly. Consistently.

Because they understand something most MSPs don’t learn until burnout hits:

Every yes you give is a no to something else.

A yes to low-margin work is a no to building IP.
A yes to reactive firefighting is a no to strategic services.
A yes to everyone else’s priorities is a no to your own.

“No” Is How You Protect the Work That Matters

Here’s the uncomfortable bit.

Most MSPs don’t have a time problem.
They have a boundary problem.

They haven’t decided:

What kind of MSP they actually want to be
Who they are not for
What work they will never do again
What a “hell yes” client looks like

Without those decisions, everything feels equally urgent.
And when everything is urgent, nothing is important.

Saying no forces clarity.

It forces you to choose:

Productised services over bespoke chaos
Fewer better clients over more mediocre ones
Depth over breadth
Long-term leverage over short-term busyness

That’s not easy. But it’s necessary.

The Myth of the Missed Opportunity

MSPs are plagued by FOMO.

“What if this client becomes huge?”
“What if this product takes off?”
“What if I say no and regret it?”

Here’s the reality:
Most opportunities aren’t opportunities. They’re distractions.

The real risk isn’t missing out.
It’s being spread so thin you never execute properly on anything.

Focus compounds.
Fragmentation exhausts.

The MSPs that win aren’t chasing everything.
They’re doubling down on a few things and executing them relentlessly well.

How to Say No (Without Being a Jerk)

You don’t need a speech.
You don’t need a justification essay.

You need a default posture.

“That’s not something we offer.”
“This isn’t aligned with how we work.”
“We’re at capacity for that right now.”
“That sits outside our support model.”

Full stop.

No over-explaining.
No apologies for having a business model.
No discounting your own time to make others comfortable.

Professional boundaries increase respect. They don’t reduce it.

Final Thought

“No” isn’t negativity.

It’s prioritisation.
It’s maturity.
It’s leadership.

If you want a clearer business, a calmer head, and work that actually moves the needle, start here:

Say no to the noise.
Say no to the drains.
Say no like you mean it.

Because on the other side of all those no’s
is the space to build something that actually matters.

And that’s not just a mindset shift.

That’s a business strategy.

Need to Know podcast–Episode 363

I reflect on the significance of the day before diving into the week’s major developments, including the arrival of the Microsoft AI Tour in Sydney. The episode covers both partner and public events, with a focus on enterprise-level AI advancements and networking opportunities.

The podcast features a comprehensive weekly news roundup:

The general availability of Copilot Agent capabilities in Microsoft 365 apps.
New data security tools for AI in Microsoft Purview.
Innovations in identity resilience and backup with Microsoft Entra.
Microsoft’s $25 billion investment in Australian AI infrastructure and training.
Practical security playbooks for tenant protection and device analytics.
Updates on decluttering promotional mail with Microsoft Defender.
Guidance on preventing oversharing in Copilot, deploying Defender, and enforcing data security with Purview.

I also share my workflow for automating podcast production using Copilot Cowork, including narration scripts and link management. I discuss experimenting with AI-driven voice narration and invites listener feedback on pacing and voice options.

The episode concludes with reflections on the Microsoft AI Tour’s enterprise focus, the importance of networking, and the challenges SMBs face in accessing relevant content. Listeners are encouraged to reach out with questions or feedback and to stay tuned for upcoming events like Microsoft Build and Ignite.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-363-hello-cowork/

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 – CIAOPS – Information about SharePoint, Microsoft 365, Azure, Mobility and Productivity from the Computer Information Agency

Join my Teams shared channel – Join my Teams Shared Channel – CIAOPS

CIAOPS Merch store – CIAOPS

Become a CIAOPS Patron – CIAOPS Patron

CIAOPS Brief – CIA Brief – CIAOPS

CIAOPS Labs – CIAOPS Labs – The Special Activities Division of the CIAOPS

Support CIAOPS – Support CIAOPS

Get your M365 questions answered via email

Join the CIAOPS Email list – Please fill out this form

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

Show notes

Microsoft 365 Insider Round-Up — April 2026

Declutter and Defend: Reducing Promotional Mail Noise with Microsoft Defender

Prevent Oversharing in Microsoft 365 Copilot

Microsoft Defender Deployment Tool

From Oversharing to Enforcement: A Practical Guide to AI Data Security with Microsoft Purview

Investing in Australia’s AI Future

Copilot’s Agentic Capabilities in Word, Excel and PowerPoint Are Generally Available

Predictive Shielding: Just-in-Time Tamper Protection

Threat Hunting Agent in Advanced Hunting

Bringing Transparency to AI-Generated Content with Watermarks in Microsoft 365

Microsoft 365 Copilot Readiness and Resiliency with SharePoint and Microsoft 365 Backup