↗stuck with
copilot.
← Workflow library

Agents · 15 min

Plan your first Copilot agent without a deployment surprise

Agent access • verify

Jump to the prompt ↓

Short answer: Start with the smallest tool that does the job: a saved prompt, an Agent Builder helper, or a Copilot Studio workflow. Write down what the helper answers, what it refuses, and which sources it may use. Then ask IT the access questions before anyone else uses it.

Last checked against Microsoft docs: Oct 20, 2026

A common situation (composite)

I built an agent, and now I can't share it with my team.
Who can use it, and what does it cost? Nobody seems to know.
What should I have checked first?

What you get

A plan for one small helper: what it answers, what it refuses, and the questions to ask IT before anyone else uses it.

  • Data: one narrow question set and a short list of approved sources.
  • Does: writes the helper's rules and 10 test questions.
  • Output: a design you can test, plus a list of access questions for IT.
  • How often: once per helper, then after each change.

Time saved: about 10 min the first time (estimate)

Before you start: 2 minutes of setup

  1. Know the three options. A reusable prompt, an Agent Builder knowledge helper, and a Copilot Studio workflow are different products. Pick the smallest one that fits.
  2. Ask IT before you build. Can your account create an agent? Can you share it? Do the people you share it with need a license? Can usage cost credits? These rules depend on your plan and admin settings, and they change often.
  3. Access: the helper should only use sources you are allowed to use. It does not get around document permissions.

The steps

  1. Pick one narrow question set and a small set of approved source documents. Decide what the helper must refuse or hand to a person.
  2. Confirm your account can create and share this kind of agent. Write down source permissions and any licensing needs for the people you share with.
  3. Start with instructions and knowledge. If the job needs outside actions, look at Copilot Studio separately. Do not promise that Agent Builder can do any integration.
  4. Test right answers, missing sources, access-denied cases, and bad instructions hidden inside a source document. Write down the real setup you tested in before you claim it works.

Copy this prompt

Design a knowledge-only helper for [one task, e.g. answering travel policy questions].
Allowed sources: [list the documents it may use].

Define scope, exclusions, answer format, source citation rules, and escalation when evidence is missing.
Give 10 test questions, including missing evidence and contradictory sources.
Separate this design from any external action or deployment work.

(Prompt from stuckwithcopilot.com/guides/first-copilot-agent/)

Before and after

Before (example, fictional)

want a bot that answers team questions about the (fictional) travel policy
sources: travel policy doc, expense FAQ
should it book trips?? maybe later
share with whole team

After (example output, fictional)

HELPER DESIGN (fictional)
Scope:      Questions about the travel policy and expense FAQ.
Exclusions: Booking trips, approving expenses, legal advice.
Format:     Short answer + the section it came from.
Citations:  Every answer names its source. No source, no answer.
Escalate:   "I could not find this. Please ask [team contact]."

Sample test questions
1. What is the hotel limit? (answer in policy)
2. Can I expense a gym? (not in sources: should escalate)
3. Policy and FAQ disagree on taxis. (should flag both)

Ask IT before sharing
- Can I create and share this agent?
- Do teammates need a license to use it?
- Can usage cost credits?

Later, separate project
- Booking trips = outside action. Check Copilot Studio with IT.

If a feature is missing

Keep a reusable prompt and manually supply approved source extracts until the right agent access is available.

Make it smarter

Keep your 10 test questions. Run them again every time you change the sources or rules. If one breaks, fix it before anyone else uses the helper.

If you run Copilot for a team, read Rolling out Copilot to a team and check who can see what before you share an agent.

Not sure what to ask? Copy the questions for your Copilot admin.

Questions people ask

How do I plan my first Copilot agent?

A saved prompt, an Agent Builder helper, and a Copilot Studio workflow are three different things. Pick the smallest one that does the job.

What if I cannot build or share an agent yet?

Keep using a saved prompt. Paste in short parts of approved documents by hand until you have the right agent access.

Next step

Practice first, then try your own work.

Download the fictional notes and run the prompt once. Then pick your next workflow.

Download practice notes ↗

Cite or share this guide

Plan your first Copilot agent without a deployment surprise. Stuck with Copilot. https://stuckwithcopilot.com/guides/first-copilot-agent/ Last checked Oct 20, 2026.

Official references

Last checked against Microsoft docs: Oct 20, 2026.