Craig Stanley

Microsoft AI, in the work people already do.

Abstract print: dark blue planes, one cobalt shape, a thin rust line, on warm paper.

I help organisations get more from their investment in Microsoft technologies. Real problems, solved with Copilot, agents, Microsoft 365, skills, and change that people will actually do.

Where that has been: large Microsoft 365 and Copilot programmes. SharePoint and information architecture on one side. Licensing, readiness and agent guardrails on the other. A tool nobody understands the boundaries of does not get adopted. It gets quietly avoided.

Talk on LinkedIn

That is the door. This site is the window onto the work.

Three lenses

The same change, read three ways.

Three columns: Risk, what it may see. Cost, what it costs to run. Enablement, whether people use it.

Risk

What the agent may see, who owns the data, what gets logged, and what happens when it is wrong. Decided in the system, not in a slide after the rollout.

Cost

Seat, add-on, and consumption. Read them on one sheet before a workflow is allowed to run, and again after people start using it.

Enablement

Named workflows, named people, and a measure that existed before the project. Tools ship. Habits do not, unless someone stays for that.

Why come back

The Microsoft 365 roadmap, through those lenses.

A feature is not news until you know whether it changes what people can see, what you will pay, or whether anyone will use it. Three items from Microsoft’s roadmap, read that way.

  1. Risk · Retention by last access

    Purview can keep a SharePoint or OneDrive file based on when someone last opened it. Preview November 2026, general availability January 2027. If Copilot can read a file, how long that file lives is part of the boundary. Roadmap 472030.

  2. Cost · Copilot usage in Graph

    Copilot usage is in Microsoft Graph, so the numbers behind a licence can be reported rather than guessed. Launched, general availability November 2025. A seat you cannot measure is a cost you cannot defend. Roadmap 396562.

  3. Enablement · Agents in OneDrive

    People can build and share agents on the files already in OneDrive. Launched. The habit starts where the files already are, which is also where the permissions already are. Roadmap 469503.

Status and dates as published by Microsoft. They move. The reading is mine.

How the value shows up

Small tools, written down, that someone else can run.

The useful things are not a list of skills. They are a cost sheet, a guardrail, a skill tied to a real task, and a note on one roadmap item that says what to do on Monday. I build those in GitHub. This site is where the ones worth sharing are explained, in the section they belong to.

What is not here yet, and will not be invented: a system I wrote that users touched, and a check that can fail a change. Those are the next things to put in public.