The Real Power of Copilot in Excel Isn’t Formulas. It’s Repeatability.

image

The first thing most people do when they open Copilot in Excel is ask it for a formula.

That’s understandable. For decades, Excel expertise has often been measured by how quickly someone can build complex formulas, create PivotTables, or untangle messy spreadsheets. Copilot changes that. You can now describe what you want in plain English and let the AI do much of the heavy lifting.

But after looking at the latest capabilities around Copilot Skills in Excel, I think many people are missing the bigger opportunity.

The real value isn’t that Copilot can generate a formula.

It’s that it can help you repeat a proven process over and over again.

In most organisations, especially SMBs and MSPs, there are a handful of people who know how to make Excel sing. They’re the people who understand financial models, reporting structures, forecasting tools, and data analysis techniques. Everyone else tends to rely on them whenever something complicated appears in a workbook.

That creates a bottleneck.

I’ve seen it countless times. Month-end reporting arrives and everyone waits for the same person. Quarterly forecasting needs updating and the same expert gets involved again. A new staff member arrives and spends weeks learning spreadsheet processes that only exist in somebody’s head.

That’s not really an Excel problem.

It’s a knowledge-sharing problem.

Copilot Skills in Excel feel like Microsoft’s attempt to address exactly that issue. Rather than repeatedly explaining the same process, you can package those instructions into a reusable skill that Copilot can invoke when required. According to Microsoft’s documentation, skills allow Copilot in Excel to perform repeatable tasks using predefined instructions, and organisations can create custom skills stored in OneDrive for reuse. [support.mi…rosoft.com], [support.mi…rosoft.com]

That might sound like a small change, but I think it’s significant.

From Spreadsheet Expert to Process Expert

Imagine you’ve spent years refining a monthly reporting workbook.

You know exactly how the raw data is imported. You know which columns need cleaning. You know which calculations matter and which charts management expects to see.

Traditionally, every new employee needed training. Documentation had to be updated. Mistakes inevitably crept in.

Now imagine creating a skill that guides Copilot through that process.

Instead of asking a colleague to remember twenty separate steps, they simply invoke the skill and allow Copilot to perform the work in a consistent manner.

The expertise becomes transferable.

That’s a very different proposition from merely generating formulas.

Excel Is Becoming More Conversational

Something else strikes me here.

For years, becoming good at Excel meant learning Excel’s language. You memorised formulas, syntax, functions, and workarounds.

Copilot flips that model.

Now Excel is increasingly learning your language.

You can ask questions about data. Request analysis. Generate charts. Create reports. Import information. Explain formulas. Build dashboards. And increasingly, define repeatable business processes using natural language instructions. [support.mi…rosoft.com], [support.mi…rosoft.com]

That’s a major shift.

The barrier to entry drops dramatically.

People who previously avoided advanced spreadsheet work now have a capable assistant sitting beside them.

The Opportunity for MSPs

From an MSP perspective, I think this capability will become particularly interesting.

Most advice around AI focuses on content generation, meeting summaries, or email drafting. Those are valuable, but they’re often incremental productivity gains.

Skills have the potential to standardise operations.

Imagine creating repeatable Excel processes for:

  • Monthly financial reporting

  • Customer profitability analysis

  • Service desk trend reporting

  • Project forecasting

  • Licence consumption tracking

  • Security compliance reporting

Rather than documenting procedures in lengthy manuals, organisations can embed that knowledge directly into skills that guide Copilot.

That’s a much more scalable approach.

And importantly, it helps preserve organisational knowledge when staff move on.

The Human Still Matters

Of course, none of this removes the need for human oversight.

One lesson I’ve repeated many times with Microsoft 365 Copilot is that AI works best when it’s treated as a capable assistant, not an autonomous decision maker.

If Copilot analyses data, review the results.

If it creates a forecast, validate the assumptions.

If it generates a report, make sure the conclusions make sense.

The person remains accountable. Copilot simply removes much of the repetitive effort.

Final Thoughts

When people think about AI in Excel, they often focus on saving a few minutes creating formulas or formatting data.

That’s useful.

But I think the more interesting story is the ability to capture expertise and make it reusable.

The organisations that benefit most from AI won’t necessarily be those with the smartest prompts. They’ll be the ones that systematically turn repeatable knowledge into repeatable processes.

Excel Skills look like another step in that direction.

And for many businesses, that could end up being far more valuable than any individual formula.

CIAOPS Need to Know Microsoft 365 Webinar – June

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

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:

June Registrations

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

The details are:

CIAOPS Need to Know Webinar – June 2026
Friday 26th of June 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.

Need to Know podcast–Episode 365

In this episode, we dig into Cowork Skills and why they represent a genuine shift from “AI as a novelty” to “AI as part of how work actually gets done.” Not more prompts. Not more tools. But fewer decisions, less friction, and more consistency across the business.
If you’ve ever thought “Copilot is interesting, but it’s not really embedded yet”, this episode is for you.

Brought to you by www.ciaopspatron.com

you can listen directly to this episode at:

https://ciaops.podbean.com/e/episode-365-skills-not-apps/

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

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
CIAOPS MSP Skills

Microsoft Build

Choose how OneNote opens Microsoft 365 file links

How Storm-2949 turned a compromised identity into a cloud-wide breach

Disrupting Fox Tempest: A cybercrime service that turned “verified” software into a pathway for ransomware

Exposing Fox Tempest: A malware-signing service operation

A faster, more efficient Editor experience with Narrator in Word

Launched: Microsoft 365 Copilot Adoption Hub Redesign

3 Ready‑to‑Use Copilot Cowork SKILL.md Examples for MSPs

3 Ready-to-Use Copilot Cowork SKILL.md Examples for MSPs

image


Below are three practical, production‑ready Copilot Cowork custom skills designed specifically for MSP use cases.
Each skill follows Microsoft’s supported structure:
YAML frontmatter (name, description) followed by Markdown instructions,
and is intended to live in:

/Documents/Cowork/Skills/<skill-name>/SKILL.md


Copilot Cowork automatically discovers these skills at the start of each conversation.
Each one targets repeatable, high‑value MSP workflows rather than one‑off prompts.


1) MSP Client Monthly Executive Summary (QBR‑lite)

Folder: /Documents/Cowork/Skills/msp-client-exec-summary/
File: SKILL.md

---
name: MSP Client Executive Summary
description: Creates a monthly executive summary for an MSP client using M365 activity evidence (emails, meetings, files) and a consistent MSP-friendly format.
---

## Purpose
Produce a client-ready monthly executive summary (QBR-lite) that is consistent, factual, and easy for non-technical stakeholders to read.

## Inputs to request (ask if missing)
1. Client name (exact)
2. Reporting period (e.g., "March 2026")
3. Where client artefacts live (SharePoint site / Teams name / OneDrive folder path)
4. Any key initiatives/projects to include (list)
5. Any sensitive exclusions (e.g., "do not mention incident details")

## Data gathering rules
- Prefer evidence from Microsoft 365 content: emails, meeting notes, and files in OneDrive/SharePoint.
- Use only artefacts the user has access to.
- If you can’t find evidence for an item, mark it as “No supporting evidence found in M365 sources provided”.

## Output format (Word document)
Create a Word document titled:
"Executive Summary - <Client> - <Reporting Period>"

Use these sections and headings exactly:

1. Headline Summary (5 bullets max)
   - Outcomes delivered (business language)
   - Risks/issues (non-alarmist)
   - Decisions needed from client (if any)

2. Service Health Snapshot
   - Identity & access notes
   - Device management posture
   - Security themes at a high level

3. Work Completed (Outcomes, not tasks)
   - Outcome
   - Evidence reference
   - Business value

4. Open Items & Blockers
   - What’s stuck
   - Who owns it
   - Next trigger/date

5. Recommendations for Next Month
   - 3–5 pragmatic recommendations
   - Include effort (S/M/L) and impact (Low/Med/High)

6. Appendix: Evidence List
   - Files, meetings, and email subjects used

## Tone & constraints
- Australian English.
- No vendor hype.
- Client-safe wording only.


2) MSP Incident Communications Pack

Folder: /Documents/Cowork/Skills/msp-incident-comms-pack/
File: SKILL.md

---
name: MSP Incident Comms Pack
description: Drafts an MSP incident communications pack (client update + internal summary + next-steps checklist) with approval-safe wording.
---

## Purpose
Create consistent, calm, defensible communications during an incident.

## Inputs to request (ask if missing)
1. Client name
2. Incident label (short)
3. Timeline of events
4. Confirmed facts vs suspected items
5. Client audience
6. Desired update cadence

## Data gathering rules
- Use M365 artefacts only (emails, meetings, Teams messages, files).
- Do not invent technical detail.
- Ask for clarification where facts are missing.

## Outputs
### A) Client Update Email (Outlook draft)
Subject:
"Update: <Client> - <Incident> - <Date>"

Include:
- What we know
- What we’re doing
- What we need from the client
- Next update timing

### B) Internal Technician Summary (Teams)
- Incident label + severity
- Current status
- Owner and next actions
- Links to evidence

### C) Next-Steps Checklist (Word)
Include:
1. Containment
2. Investigation
3. Recovery
4. Communications
5. Post-incident follow-up

## Tone & constraints
- Calm, factual, non-alarmist.
- Australian English.
- No blame, no absolutes.


3) MSP Onboarding Kickstart Pack (SMB‑friendly)

Folder: /Documents/Cowork/Skills/msp-onboarding-kickstart-pack/
File: SKILL.md

---
name: MSP Onboarding Kickstart Pack
description: Creates an MSP onboarding pack including welcome email, onboarding schedule, folder structure, and checklists.
---

## Purpose
Deliver a consistent, professional first-30-days onboarding experience for SMB clients.

## Inputs to request (ask if missing)
1. Client name and primary contact
2. Services in scope
3. Target go-live date
4. Preferred meeting times
5. Tenant state (new or existing)

## Outputs
### A) Welcome Email (Outlook draft)
Include:
- Week 1 expectations
- Required client inputs
- Communication model
- Links to onboarding artefacts

### B) Onboarding Plan (Word)
Title:
"Onboarding Plan - <Client> - First 30 Days"

Break down by week:
- Meetings
- Deliverables
- Dependencies

### C) Folder Structure
Create or propose:
- 01 - Commercial & Contacts
- 02 - Tenant Baseline
- 03 - Security & Compliance
- 04 - Devices & Intune
- 05 - Documentation & SOPs
- 06 - Projects
- 07 - Reports

### D) Onboarding Checklist (Word)
Include:
- Identity baseline
- Device enrolment
- Security configuration
- Documentation completion
- Client sign-off points

## Rules
- Step-by-step.
- SMB-realistic (no enterprise bloat).
- Australian English.



Implementation reminder:
Each skill must live in its own folder under /Documents/Cowork/Skills/,
must be named SKILL.md, and should have a specific description so Cowork knows when to load it.

Creating Custom Copilot Cowork Skills That Actually Matter for SMBs

image

If you’re still using Copilot like a fancy chatbot, you’re missing the point.

Copilot Cowork is Microsoft’s quiet shift from AI that answers questions to AI that actually does work. And the real power move for SMBs isn’t the built‑in skills—it’s custom Cowork skills that encode how your business actually runs. [learn.microsoft.com]

This is where Copilot stops being impressive and starts being profitable.

What a Custom Cowork Skill Really Is

A custom Cowork skill is not code, not an agent, and not a Power Automate flow. It’s a structured set of instructions written in a simple SKILL.md file and stored in the user’s OneDrive under:

/Documents/Cowork/Skills/<skill-name>/SKILL.md

Copilot Cowork automatically discovers up to 20 custom skills per user at the start of every conversation and loads them when relevant. No prompting gymnastics required. [learn.microsoft.com]

Think of a custom skill as:

“Every time I do this type of work, follow these rules, pull this data, and produce that output.”

For SMBs, that’s gold.


Example 1: Client Meeting Prep for a 10‑Person Consultancy

The problem:
SMB consultants spend 15–30 minutes before every client meeting digging through emails, Teams chats, and old documents. It’s repetitive, error‑prone, and always rushed.

The custom Cowork skill:
Client Meeting Brief

What the skill does:

  • Pulls calendar context for the upcoming meeting

  • Finds recent emails and Teams messages with that client

  • Identifies open actions from last meeting notes in OneDrive

  • Produces a 1‑page Word briefing with:

    • Client objective

    • Outstanding issues

    • Risks and next steps

Why it works for SMBs:
It saves time without introducing new tools. Everything stays inside Microsoft 365, using data they already trust. No CRM integration required.
[learn.microsoft.com]


Example 2: Weekly Operations Report for an Owner‑Managed Business

The problem:
Business owners hate status reporting, but flying blind is worse. Most weekly reports are inconsistent, late, or ignored.

The custom Cowork skill:
Weekly Ops Summary

What the skill does:

  • Reviews sent emails and calendar activity from the past 7 days

  • Pulls key numbers from a defined Excel file in OneDrive

  • Generates a consistent Word report using the owner’s template

  • Flags anything that looks overdue or hasn’t progressed

Why it works for SMBs:
Custom skills enforce discipline without admin overhead. The report looks the same every week, uses the same data sources, and takes seconds—not hours—to produce.


Example 3: Standardised Client Follow‑Ups for Professional Services

The problem:
Follow‑up emails are inconsistent. Some are overly casual, others too formal, and key details get missed.

The custom Cowork skill:
Client Follow‑Up Drafter

What the skill does:

  • Detects completed meetings

  • Creates a draft email using the company’s approved structure:

    • Summary

    • Decisions made

    • Actions and owners
  • Saves the draft for approval before sending

Copilot Cowork always asks for confirmation before external communication, which is critical for SMB risk management.


What Doesn’t Work Well as a Custom Skill

Not everything should be a skill.

Avoid:

  • One‑off tasks (“Summarise this document”)

  • Highly variable creative work

  • Anything that relies on local files (Cowork only accesses OneDrive and SharePoint)

The sweet spot is repeatable, boring, but important work.


Why MSPs Should Care (Even More Than SMBs)

For MSPs, custom Cowork skills become:

  • A standardised service delivery layer
  • A way to encode best practice for L1–L3 staff

  • A differentiator that isn’t just “we sell Copilot licences”

You don’t deploy Copilot.
You operationalise it.

Custom Cowork skills are how you turn AI from a novelty into a system—especially in SMB environments where consistency matters more than scale.

If you’re not teaching your customers how to do this, someone else will.


Further reading:
Microsoft Learn – Create custom Copilot Cowork skills
https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/use-cowork#create-custom-skills