Revisiting Copilot image generation analysis

A while back I shared the results of an identical image prompt in a number of AI tools. That article is here:

https://blog.ciaops.com/2026/03/07/image-generation-analysis/

Now that Copilot has access to OpenAI Image 2 model I thought I’d re-run and share the results.

This is the result from the previous test with Copilot chat:

image

This is the updated response using the identical prompt as before with Copilot Chat again:

image

This is the same prompt with Copilot Chat again BUT with ‘Create a detailed infographic using the new openAI image 2 model’ added at the beginning of the prompt:

image

This is the original prompt but used in the dedicated ‘Create Image’ part of Copilot:

 image

Still not perfect if you examine each closely but a significant improvement from the last round.

BitLocker Silent Enablement via Intune: The Deployment Pattern That Actually Sticks

image

Every MSP ends up doing BitLocker. Very few do it silently on the first attempt. Between TPM quirks, third-party encryption leftovers, and the three different Intune policy surfaces that all claim to configure BitLocker, the difference between “encrypted fleet with recoverable keys” and “2am call from a locked-out CEO” is a handful of settings. Here’s the pattern to deploy in production under Microsoft 365 Business Premium.

Prerequisites people skip

Silent means standard user, no prompts, no elevation — which is a higher bar than “BitLocker on.”

  • TPM 2.0, ready state, UEFI, Secure Boot on. If the TPM reports “not ready” or is owned by a prior OEM image, silent encryption aborts. Check with Get-Tpm before blaming policy.

  • Entra joined or Hybrid joined. Workgroup and AD-only devices have no key escrow target and will not silently encrypt.

  • No third-party encryption agent. McAfee DE, Sophos SafeGuard, legacy Dell Data Protection — all block BitLocker takeover until fully decrypted and uninstalled.

  • No startup PIN or startup key requirement. Silent mode and pre-boot authentication are mutually exclusive. Pick one.

  • WinRE present and healthy. BitLocker uses it for recovery.

If any of those are wrong, don’t touch policy yet. Fix the device first.

Where to configure it

Ignore the Settings Catalog for this one. Microsoft is explicit that the Settings Catalog does not expose the TPM startup authentication controls silent enablement depends on (docs).

Use the Endpoint security path:

Intune admin center → Endpoint security → Disk encryption → Create Policy → Platform: Windows → Profile: BitLocker.

The settings that actually matter for silent:

  • Enable full disk encryption for OS and fixed data drives: Yes
  • Hide prompt about third-party encryption: Yes
  • Allow standard users to enable encryption during Autopilot: Yes
  • Require device to back up recovery information to Azure AD: Yes (gates encryption on successful escrow — this is the setting that saves you)

  • Recovery password rotation: Enable on Entra and Hybrid-joined devices
  • OS and fixed drive: XTS-AES 256, TPM-only protector, no PIN

Full setting reference: Disk encryption profile settings.

The rollout pattern

Do not target All Devices. Ever.

  1. Pilot ring (5–10 devices): your own, one per client hardware family. Watch the Endpoint security → Disk encryption report for “Encrypted” status and a recovery key present in Entra. If the key isn’t there, the device isn’t safe, regardless of what Windows says.

  2. Early ring (10–20% by dynamic group): let this soak for a week. Check the encryption report daily. Anything stuck in “Waiting for response” usually means TPM readiness or a WinRE issue — remediate per device, don’t loosen policy.

  3. Broad rollout: remaining corporate devices via a dynamic group filtered on deviceOwnership eq "Company". Never include BYO.

  4. New builds: bake the policy into Autopilot so encryption completes during ESP. Standard-user silent enablement only works if “Allow standard users to enable encryption during Autopilot” is Yes — double-check before you cut a new image.

The help desk also needs the recovery-key retrieval flow documented before you go broad, not after the first lockout.

The pitfalls that bite

  • Silent and startup PIN are incompatible. If compliance demands pre-boot auth, you’re running standard BitLocker, not silent. Decide once.

  • Recovery key escrow failures hide in plain sight. Without “Require device to back up recovery information to Azure AD = Yes”, devices encrypt, keys never land in Entra, and you discover it the day a laptop gets stolen. Audit the encryption report monthly — the ground truth is “Recovery key: Yes/No” per device, not policy compliance.

  • Don’t mix endpoint protection + disk encryption profiles targeting the same devices. Conflicts resolve unpredictably. Pick the Disk encryption profile and delete the legacy Endpoint protection one (policy comparison).

Get those three right and BitLocker becomes a checkbox — exactly what your clients are paying for.

Progress Is Quiet. That Doesn’t Mean It Isn’t Working.

image

One of the hardest things to accept in business—and in life—is that real progress is mostly invisible.

We’re conditioned to look for obvious signals. Big wins. Public milestones. Announcements, launches, applause. If none of that is happening, it’s easy to assume we’re stuck. Or worse, going backwards.

But that’s not how meaningful progress actually works.

Every problem you solved before it became a crisis.
Every decision you didn’t rush just to feel productive.
Every shiny “opportunity” you said no to because it wasn’t aligned.

That’s progress. Quiet progress. The kind that happens in the background while no one is watching.

In MSPs and IT businesses, this shows up all the time. You harden security instead of chasing a new tool. You standardise processes instead of custom‑building for every client. You invest time learning Copilot properly instead of posting another “AI will replace us” hot take on LinkedIn.

None of that feels exciting in the moment. It feels slow. Boring, even. And because there’s no immediate payoff, the temptation is to assume those are “lost days”.

They’re not.

Those slow days are doing the heavy lifting. They’re building the foundation that lets everything else scale later—reliably, profitably, and without burning you out.

The problem is that we often misdiagnose what’s missing. We assume we need a better routine. A new framework. A clever hack. Another app, another system, another morning ritual.

Most of the time, that’s not the issue.

The issue is trust.

Trust that the work you’re doing—when it’s deliberate and aligned—actually compounds. Trust that saying no is as powerful as saying yes. Trust that progress doesn’t need to announce itself to be real.

This is especially true with long‑term capability building. Training staff properly. Improving documentation. Fixing fundamentals. Learning how to use tools like Microsoft Copilot effectively instead of dabbling and moving on.

There’s no dopamine hit for that. No instant validation. Just steady, unglamorous effort.

But it adds up.

And one day, usually without warning, things feel easier. Decisions get clearer. Results come faster. Other people start calling it “overnight success”.

It wasn’t overnight. You just did the work when no one was clapping.

So if today feels slow, that doesn’t mean it’s wasted. If it feels like you’re laying bricks instead of building towers, that’s exactly how it’s supposed to feel.

You don’t need to overhaul everything.
You don’t need a new system.
You don’t need to panic‑pivot.

You just need to keep going.

Trust the work. It’s adding up—even when you can’t see it yet.

CIAOPS Need to Know Microsoft 365 Webinar – May

laptop-eyes-technology-computer_thumb

Now in our tenth year!

Join me for the free monthly CIAOPS Need to Know webinar. Along with all the Microsoft Cloud news we’ll be taking a look at Copilot Cowork.

Shortly after registering you should receive an automated email from Microsoft Teams confirming your registration, including all the event details as well as a calendar invite.

You can register for the regular monthly webinar here:

May Registrations

(If you are having issues with the above link copy and paste – https://bit.ly/n2k2605 )

The details are:

CIAOPS Need to Know Webinar – May 2026
Friday 29th of May 2026
11.00am – 12.00am Sydney Time

All sessions are recorded and posted to the CIAOPS Youtube channel.

Also feel free at any stage to email me directly via director@ciaops.com with your webinar topic suggestions.

I’d also appreciate you sharing information about this webinar with anyone you feel may benefit from the session and I look forward to seeing you there.

CIAOPS AI Dojo 012

image

What’s the session about?

This month we will be focusing on new Copilot features and updates as well as optimising AI for Small Business.

Who should attend?

This session is perfect for:

  • IT administrators and support staff
  • Business owners
  • People looking to get more done with Microsoft 365
  • Anyone looking to automate their daily grind

Save the Date

Date: Friday the 29th of May 2026

Time: 9:30 AM Sydney AU time

Location: Online (link will be provided upon registration)

Cost: $80 per attendee (free for Dojo subscribers)

Register Now

DSPM: The End of Guessing About Your Sensitive Data

image

Most Microsoft 365 tenants I walk into are flying blind on data.

The sensitivity labels exist. A couple of DLP policies exist. Someone once turned on Insider Risk Management because a consultant said so. And then nothing. Nobody knows what’s working, what’s exposed, or which sensitive files are sitting wide open in a SharePoint site shared with half the planet.

That’s not a security posture. That’s a guess.

The tool that finally ends the guessing is Microsoft Purview Data Security Posture Management. If you’ve got E5 or the Purview Suite and you’re not showing this to your clients, you’re leaving value on the table.

What is DSPM, really?

DSPM is the dashboard that tells you, in plain English, where your sensitive data is sitting unprotected and which users are handling it carelessly. It pulls signals from the tools you already pay for — DLP, Information Protection, Insider Risk Management, Adaptive Protection — and stitches them into one view.

The clever bit is the correlation. Before DSPM, you’d open five different blades, cross-reference three different reports, and still miss half of it. Now the findings and recommendations land on one page, with a one-click path to spin up the matching policy.

That’s not a report. That’s a to-do list with context.

Step-by-Step: turning DSPM on

Portal only. Stay in the GUI — easier for you, easier to hand off to the next admin.

Open the Purview portal

Sign in to the Microsoft Purview portal as a member of the Data Security Management role group, an Insider Risk Admin, or a Compliance Administrator. Global Admin works too, but please don’t use it if you can help it.

Open the DSPM solution

From the home page, go to SolutionsData Security Posture ManagementOverview.

Turn on analytics

On the Overview page, click Turn on analytics. That one switch also enables DLP analytics and Insider Risk analytics behind the scenes if they aren’t already on. One click, three switches. The full checklist is in the Get started with DSPM article.

Wait

Yes, really. The automated scan across your tenant can take up to three days on anything larger than a handful of users. Walk away. Brew a coffee. Come back on Thursday.

Review the recommendations

Back on the DSPM dashboard, open Recommendations. Each one tells you what was found, why it matters, and offers a one-click path to create the DLP or Insider Risk policy that fixes it. You don’t start from a blank policy screen anymore — you start from your tenant’s real gaps.

Track trends over time

Use the Analytics and Reports tabs in client reviews. A trend line of risky activity going down beats any invoice justification I’ve ever tried to write.

Why this actually changes behaviour

“Are we protected?”

That’s the question every SMB owner asks. Most of us have been answering with vibes. Good vibes, educated vibes, but vibes.

DSPM changes the answer. You can point at a number. You can point at a recommendation you actioned last month and the unprotected file count that dropped because of it. You can show, not tell.

For MSPs, that’s a QBR slide that sells itself. For internal IT, it’s the evidence you need when the CFO asks what the Microsoft Purview licence is actually doing for the business.

And if Copilot is already in the tenant — which, let’s be honest, it increasingly is — then DSPM for AI is your next stop. Same lens, pointed at what people are pasting into Copilot prompts and what’s flowing back out.

Copilot doesn’t slow down. Neither does your data sprawl. Use something that keeps up.

DSPM isn’t there to create more work. It’s there to stop the guessing.

Prospects don’t buy in straight lines, so stop trying to force them down one

image

Most marketing is built on a comforting lie.

That lie is the “nice, neat funnel”.

Awareness.
Consideration.
Decision.
Purchase.

It looks logical. It’s easy to diagram. It makes marketers feel in control.

And it’s almost completely divorced from how people actually buy.

Prospects don’t move in straight lines. They loop, stall, disappear, reappear, second‑guess themselves, ask peers, ignore you for months, then suddenly act. If your marketing assumes linear progress, you’re not guiding buyers—you’re frustrating them.

The problem isn’t your funnel. It’s your assumptions.

Most marketing is designed around how we wish people bought:

  • Read the blog

  • Download the guide

  • Book the call

  • Buy the service

But real buyers don’t behave like that. Especially in B2B. Especially in IT.

An MSP prospect might:

  • Hear about you on LinkedIn

  • Ignore you for six months

  • Get hit with a security incident

  • Ask a peer in a WhatsApp group

  • Re‑read a blog they skimmed months ago

  • Watch half a webinar

  • Then finally reach out—already 80% decided

If your marketing only supports one “next step”, you lose relevance the moment they step off your rails.

People buy when their timing aligns, not when your campaign says so

This is where most MSP marketing falls apart.

You’re pushing:

  • “Book a call”

  • “Act now”

  • “Limited time offer”

While the buyer is thinking:

  • “I need to understand this better”

  • “Is this actually a problem for me?”

  • “What happens if I do nothing?”

Forcing urgency doesn’t create trust. It creates resistance.

Good marketing doesn’t push people forward. It removes friction wherever they are.

What non‑linear marketing actually looks like

If people don’t buy in straight lines, your marketing shouldn’t either.

That means:

  • Content that stands alone (not “part 3 of 7”)

  • Clear explanations without requiring prior context

  • Repeated ideas from different angles, not “new for the sake of new”

  • Easy re‑entry points for people who went quiet

It also means accepting that most prospects will consume far more content than you’ll ever see evidence of.

They’re watching. Reading. Lurking. Evaluating.

Silence does not mean disinterest.

Design for the buyer’s journey, not your sales process

Your sales process is internal. Your buyer’s journey is not.

When you design marketing around your CRM stages, you optimise for reporting—not conversion.

Instead, ask:

  • What questions are buyers asking before they talk to us?

  • What objections do they have that they’re not voicing?

  • What would make them feel smarter, safer, or more confident right now?

Answer those questions—over and over—without demanding anything in return.

Stop trying to control the path

Marketing isn’t about herding people down a funnel.

It’s about being present, useful, and credible whenever the buyer decides to engage.

So stop marketing the way you wish people bought.

Start marketing the way people actually buy: Messy. Non‑linear. On their own timeline.

Your job isn’t to force the journey.

It’s to make sure you’re still relevant when they finally decide to move.

Autopilot + ESP: The Deployment Pattern That Actually Survives Contact With Real Users

image

If you’re still PXE-booting laptops in the back room in 2026, you owe your techs a better life. Windows Autopilot with a properly configured Enrollment Status Page (ESP) is the MSP deployment pattern that scales — but only if you stop treating ESP as a tick-box and start treating it as the gate that enforces your security posture before the user ever sees a desktop. Here’s the deploy-it-well version.

Prerequisites People Miss

Business Premium gets you the licensing — Entra ID P1, Intune, and Windows 11 Pro/Enterprise entitlements. The bits that actually bite:

  • Automatic MDM enrollment must be on. Entra admin center → Mobility (MDM and WIP)Microsoft Intune → MDM user scope = All (or a group). Miss this and the device joins Entra but never enrols into Intune, and the ESP just hangs.

  • Hardware hash registration path. For anything beyond a one-off, get the reseller to register devices to your tenant at purchase. Manual CSV uploads at OOBE are fine for a test VM; they’re a tax on your L1 team in production.

  • TPM 2.0 + device attestation are non-negotiable for self-deploying and pre-provisioning scenarios. VMs won’t cut it, and attestation needs outbound HTTPS to vendor-specific endpoints.

  • Cloud-native over hybrid join. Microsoft’s own guidance is explicit: deploy new devices as Entra-joined. If you’re still standing up the Intune Connector for AD in 2026, have a very good reason written down.

Full list: Windows Autopilot requirements.

Where To Configure

Everything lives in the Microsoft Intune admin center. Two paths you’ll wear out:

  • Deployment profileDevices → Windows → Device onboarding → Enrollment → Windows Autopilot → Deployment Profiles → Create profile → Windows PC. User-driven, Entra-joined, Standard user account type, hide EULA and privacy settings, set a device name template, allow pre-provisioned deployment.

  • ESP profileDevices → Device onboarding → Enrollment → Windows tab → Enrollment Status Page → Create. Do not edit the default “All users and all devices” profile — create your own and give it a higher priority.

References: Configure Windows Autopilot profiles and Set up the Enrollment Status Page.

The Rollout Pattern That Works

Three rings, same as your update rings. Don’t skip this.

  1. Pilot (IT / internal). Loose ESP — Block device use = No, timeout 90 minutes, log collection on. You want visibility, not gates.

  2. Early adopters. ESP enforced at the device phase only. Block device use = Yes, timeout 60 minutes, custom error message with your service desk number. Turn off the User / Account Setup phase — the overwhelming majority of ESP failures happen there, and device-targeted apps have already installed by that point.

  3. Production. Lock it. Required blocking apps = your EDR (Defender), BitLocker initiation, and one small “canary” Win32 app that proves apps are actually flowing. No more than five blocking apps total.

Assign both profiles to a dynamic device group filtered on (device.devicePhysicalIDs -any _ -contains "[ZTDId]") so Autopilot-registered devices land automatically.

Top Pitfalls

  • Too many blocking apps. Every blocking app is a potential ESP timeout. Keep it to security essentials; let the rest stream in post-desktop via required assignments.

  • User-phase ESP left enabled. User-targeted apps plus Known Folder Move plus OneDrive sync at first login is a timeout factory. Disable the account setup phase unless you have a specific, measured reason to keep it.

  • Dynamic group latency. Group membership can take minutes to evaluate and devices race ahead of policy. Mitigation: move to Autopilot device preparation (enrollment-time grouping) for new greenfield tenants, or accept the ring-one pilot friction as the cost of dynamic groups.

For the broader lifecycle picture, start at Overview of Windows Autopilot.

Deploy it once, deploy it tight, and your zero-touch goes from aspirational to boring — which is exactly what production should be.