Saved prompt
Use it when the instructions repeat but the source changes. You collect the material, run the prompt and review the draft.
Chapter 6 of 8
Power users don't start with the cleverest feature. They make one regular job clear enough to run, review and improve.
Your first workflow should be frequent, mildly annoying and easy for you to judge. Good candidates include:
Avoid high-stakes decisions, final approvals and unfamiliar work as your first build. Choose something where you can spot a bad answer in seconds.
This card separates process design from prompt wording. If you can't fill it out, Copilot has the same problem.
Help me define one repeatable work process before we write a prompt. Ask one question at a time to establish: - the trigger - required inputs and where they come from - the steps a capable person follows - the exact output and audience - the quality checks - the human reviewer and final action Challenge unclear words and missing decisions. Don't design automation yet. Finish with a one-page workflow card and list the parts that still need an owner or policy answer.
Here's a fictional workflow with enough detail to run.
Draft this week's project update for the steering group. Use only the meeting notes, action register and previous update I provide. Order: 1. status in one sentence 2. changes since last week 3. decisions needed 4. current risks 5. next actions with owners and dates where supplied Keep it under 180 words. Use plain Australian English. Don't invent progress, dates, approval or sentiment. After the draft, list any unsupported claim, conflict or missing owner as a question for me. Wait for all three sources before drafting.
Use it when the instructions repeat but the source changes. You collect the material, run the prompt and review the draft.
Use it when the job relies on a stable set of approved references and benefits from its own working space.
Consider it when the workflow needs a dedicated role, shared use, governed knowledge or actions beyond a single chat.
Microsoft describes Agent Builder inside Microsoft 365 Copilot as the quicker route for agents used by an individual or small team. Copilot Studio is the fuller build environment for multi-step workflows, external integrations, broader deployment and stronger governance.
Licence or metered use
Public-website grounding can be available without a Microsoft 365 Copilot licence. Agents that access shared tenant data require a Microsoft 365 Copilot licence or metered billing. Your admin can also restrict agent creation, publishing and data access.
Ask IT before expanding
Bring IT the workflow card, intended users, approved sources and required actions. That's a clearer starting point than asking for “an AI agent”.
Review this workflow card and tell me whether it needs a saved prompt, a Copilot Notebook or an agent. Judge it on: - how stable the sources are - whether other people will use it - whether it needs to take actions - permissions and sensitive data - required human approval - how failures will be noticed Recommend the lightest option that meets the need. List any licensing, admin or policy question I need to confirm. Don't assume a feature is enabled in my tenant.
For the first five runs, write down:
You're looking for repeated misses. A one-off awkward sentence needs an edit. A repeated invented owner needs a stronger source boundary and check.
Chapter complete
The next chapter sets the monitoring and data boundary so you can use it openly inside the system your organisation approved.