Check cost and permission before you delegate
This is a draft
The steps below were written but have not yet been performed end to end on every tenant type, and the time is planned rather than measured with a stopwatch. Treat timings and the failure list as provisional. Interfaces and licence flags change. What that means
After this you will be able to
Before you delegate work to Cowork, Code or Autopilot, check spending policy, permission, and what must stay with a person.
Skip this if you already refuse to start agentic Copilot work until you know the credit policy and the data boundary.
Before you start. Without looking: which Copilot work sits on a fixed licence, and which needs Copilot Credits?
Everyday Chat and Copilot in the Office apps sit on a fixed per-user licence. Cowork, Code, Autopilot and frontier models use Copilot Credits under usage-based billing. Microsoft leaves usage-based services off until an admin sets a spending policy. Delegating without checking is how people either hit a wall or spend without anyone meaning to.
Permission is not only IT policy. It is also what the tool is allowed to see and who it may contact.
What you need
- The task you chose in lesson 02, or another real task you might delegate.
- A way to ask IT or read your organisation’s Copilot / AI use guidance.
- Willingness to stop if the answer is unclear.
The steps
- Write whether your task is everyday Chat/in-app work (fixed licence) or agentic (Cowork, Code, Autopilot / credits).One label: fixed licence, credits, or not sure.
- Find out whether usage-based Copilot spend is enabled for people like you. If you cannot find out in ten minutes, write “unknown — do not proceed” and stop the agentic path.Enabled, disabled, or unknown. Unknown means stay on everyday Chat.
- List what the agent or Cowork session would need: files, mailboxes, people to contact, systems to change. Mark anything it must not touch.A short boundary list.
- Only if policy allows: run a small, non-sensitive delegation — or draft the objective and boundaries for a champion to review. If policy blocks you, send the boundary list to IT as the ask.Either a supervised small run, or a clear request that unblocks you without shadow work.
Try this one first
Complete this sentence: “I will not start Cowork / Code / Autopilot on real work until I know ____ and ____.”
Typical blanks: spending policy status; data I must not include. Keep the sentence.
If it goes wrong
The feature is visible but credits error when you start. That often means policy is incomplete. Stop and report it. Do not keep retrying with larger tasks.
Nobody in IT answers. Stay on everyday Copilot. Escalating into personal AI tools with work content is not a workaround.
You are asked to “just try Autopilot on the live supplier list”. Refuse until boundaries and policy are written. Live lists and outbound contact are high-impact.
Do today
Save your two blanks (policy status and data boundary) next to the task from lesson 02. If both are clear and allowed, run one small supervised delegation. If not, send one message to IT with those two questions.
Where else this works. Cost-and-permission checks belong before any agent, automation, or connector that can act while you are away.
Did this work? If it did not, say what happened — hello@howtobedigital.com
Every failure anybody sends in ends up in the section above.
Checked by a person · not auto-published
Published 27 September 2026 · Last checked 27 September 2026
Draft — steps not yet timed on every licence type — quality bar
Re-check window: 60 days for Copilot lessons
Next
Copilot and AgentsWhat adoption meansHabitual value · prompting → delegating → cost awareness