Prompting · BEGINNER GUIDE

Microsoft Copilot Prompting Guide for Beginners

Write better Microsoft Copilot prompts using goal, context, expectations and sources, with practical examples for learning and work.

WHAT YOU WILL LEARN

Key takeaways

  • State the goal first.
  • Add context that changes the answer.
  • Describe the response you expect.
  • Name trusted sources and review the result.
PROMPT ARCHITECTURE

Microsoft's four-part prompting framework

01
GoalWhat Copilot should do
02
ContextWhy and for whom
03
ExpectationsFormat and quality
04
SourceInformation to ground it
Use the parts that remove meaningful ambiguity from the task.

BEFORE YOU START

Four words to know

Read these simple meanings first. The same English terms are used in courses, documentation and interviews.

Goal
The result you want Copilot to help produce.
Expectation
A requirement for the content, tone, length or format.
Source
The information Copilot should use to ground the response.
Iteration
Improving a result through small, focused follow-up prompts.
01
START HERE

Use Microsoft's four-part framework

Microsoft's beginner prompting guidance describes four useful parts: goal, context, expectations and source. You do not need every part for every request, but the framework helps you notice missing information.

Put the most important outcome first. Add only context that affects the result, and make your expectations easy to check.

  • Goal: what should Copilot do?
  • Context: why and for whom?
  • Expectations: what should a good answer look like?
  • Source: which information should it use?
02
BUILD YOUR UNDERSTANDING

Make the goal specific

A topic is not a goal. ‘Project management’ leaves Copilot guessing, while ‘create a risk-review checklist for a student software project’ defines a useful result.

Use an action verb such as explain, compare, summarise, analyse, draft or critique. Name the decision or deliverable the answer should support.

TRY THIS PROMPT

Goal: create a one-page revision plan. Context: I have seven days before a cloud fundamentals assessment. Expectations: daily tasks, 60 minutes per day and a final self-test. Source: use only the syllabus pasted below.

03
BUILD YOUR UNDERSTANDING

Add constraints that improve review

A format can make an answer easier to use and check. Ask for a table, checklist, short memo or step-by-step explanation only when that structure fits the task.

Do not overload the prompt with decorative rules. Prioritise factual accuracy, scope, audience, sources and the decision the output must support.

  • Audience and knowledge level
  • Required sections or fields
  • Length or time limit
  • Facts that must not be assumed
04
BUILD YOUR UNDERSTANDING

Ground the response in sources

When accuracy matters, tell Copilot which source to use. In supported Microsoft 365 experiences, that may be a file, email, meeting or other authorised work information.

Ask Copilot to identify evidence for important conclusions and to label anything not supported by the source. Then open the source and verify it yourself.

TRY THIS PROMPT

Using the attached meeting notes, list confirmed decisions, owners and due dates. Do not infer missing owners. Put unclear items in a separate section and name the note heading supporting each decision.

05
BUILD YOUR UNDERSTANDING

Improve through focused follow-ups

Evaluate the first answer against your requirements. Ask for one meaningful improvement at a time so you can see which instruction helped.

If the source is incomplete or the task requires human judgement, prompting alone will not solve the problem. Identify the gap rather than asking Copilot to sound more confident.

TRY IT TODAY

Build a four-part prompt

A short activity to turn this guide into practical understanding.

  1. 1

    Choose one real learning or work task.

  2. 2

    Write one sentence each for goal, context, expectations and source.

  3. 3

    Run the prompt, identify one weakness and improve it with a follow-up.

ONE IMPORTANT HABIT

Check before you use.

AI can make mistakes. Check important facts, calculations, sources and code. Never share private information unless your school or organisation has approved the tool.

COMMON QUESTIONS

Microsoft Copilot Prompting Guide FAQ

What makes a good Copilot prompt?+

A good prompt clearly states the goal, includes relevant context, describes expectations and names a trusted source when one is needed.

Do prompts need to be long?+

No. Use enough detail to remove important ambiguity, but leave out information that does not affect the task.

Can I reuse the same prompt?+

Yes. Save useful prompt structures, then update the audience, source and success criteria for each real task.

Why does Copilot still make mistakes?+

Clear prompts improve direction but do not guarantee accuracy. Source quality, product capabilities and the underlying AI system also affect the result.

Sathish Kumar, Founder and Chief AI Educator at MaanavaN

WRITTEN AND REVIEWED BY

Founder & Chief AI Educator, MaanavaN · 17+ years of industry and learning experience

Practical AI guidance for Tamil-speaking learners using professional English terminology and human-reviewed learning pathways.

PRIMARY SOURCES

Official references

Features and product limits change. Use these official sources to verify current information.

MaanavaN is an independent learning platform and is not affiliated with Microsoft, GitHub, Anthropic or OpenAI. Product names and trademarks belong to their respective owners.

KEEP BUILDING YOUR AI SKILLS

Choose your next beginner guide.

Compare tools, practise clearer prompts and build safe AI workflows in professional English.
Browse all Insights