Practical AI tools for everyday life and business. Explore what AI can do
Learning Hub
PRACTICAL AI FIELD GUIDE

Microsoft Copilot & GitHub Copilot

Use the right Copilot for the task, with a source, an output format and a review step.

Free guide8 min readReviewed

Microsoft 365 Copilot supports work such as documents and meetings where enabled. GitHub Copilot is a coding product. Access, licenses, supported features and administrator settings differ; this guide does not activate either service.

Your first useful task

Start with one small win

  1. For office work, open the document or source you want to use in the supported Microsoft app.
  2. For coding, open the relevant repository and files in your supported Copilot environment.
  3. Ask for one result, review it against the original material, then request a targeted revision.

Practical tips that make a difference

Use goal, context, source and expectations

Tell Microsoft Copilot what to produce, why it matters, which material to use and how the output should look. A useful business request might name a proposal file, its audience and a word limit instead of asking for a generic summary.

Based on: Microsoft · Write a great Copilot prompt ↗

Make one precise Word edit

Ask Copilot in Word to shorten an introduction, change its tone or reuse a document structure. Identify the source file when work context is needed. Review names, numbers and meaning before sharing the edited document.

Based on: Microsoft · Effective prompts in Word ↗

Refine the result in place

Once the result is close, ask for a specific improvement such as a shorter opening or a clearer action list. Keep the source and desired outcome in view. Our practical habit is to recheck any facts affected by the revision, rather than rereading only the polished wording.

Based on: Microsoft · Effective prompts in Word ↗

Developer notes

Give GitHub Copilot relevant code context

Name the function or file, describe the goal and provide example input and output. Split a large coding task into smaller changes. For completions in an editor, keep the relevant files open so the available context fits the work.

Based on: GitHub · Copilot prompt engineering ↗

Store repository conventions once

For supported GitHub Copilot surfaces, .github/copilot-instructions.md supplies repository-wide guidance. Path-specific instructions use files below .github/instructions/. Check the support matrix for your editor and feature; instruction support is not identical everywhere.

Based on: GitHub · Copilot custom instructions ↗

Review generated code as a change proposal

Ask for a relevant test and inspect the suggested implementation. Check error handling, unwanted data exposure and existing project conventions. Our review pattern is to require observed test results and a human-readable diff before a production merge.

Based on: GitHub · Copilot prompt engineering ↗

Copy, adapt, then check

Original Utilising AI examples. Replace bracketed placeholders before use. These buttons copy text only; they do not run code or contact an AI provider.

Proposal → decision brief

Using [select or attach proposal file], write a decision brief for the business owner: goal, deliverables, price stated in the source, open questions and next step. Maximum 250 words. Mark missing details as “not provided”. Keep recommendations separate from facts.

Use in a supported Microsoft 365 Copilot experience with access to the chosen file.

Based on: Microsoft · Write a great Copilot prompt ↗

Refine a Word draft

Shorten the selected introduction to 100 words for a non-technical reader. Preserve the offer, dates and prices. Flag any sentence whose meaning is unclear instead of inventing a replacement fact.

Original example for an existing draft; review the edited text.

Based on: Microsoft · Effective prompts in Word ↗

GitHub Copilot project instructions starter

# Repository guidance
- Runtime and framework: [actual versions].
- Relevant test command: [actual command].
- Follow the existing error-handling pattern in [file].
- Preserve these public interfaces: [list].
- Report tests run and any remaining verification gaps.

Save an adapted version as .github/copilot-instructions.md where supported. This is guidance, not an enforced access policy.

Based on: GitHub · Copilot custom instructions ↗

Check your result

  • Did the tool actually have access to the selected source?
  • Were office facts checked, and were coding changes tested?
  • Have you confirmed the feature exists in your account or editor?

Common mistakes to avoid

  • Confusing Microsoft 365 Copilot with GitHub Copilot.
  • Assuming naming a file grants the tool access to it.
  • Accepting generated code or document claims without review.

Sources & review notes

Reviewed on 15 November 2026. Tips are paraphrased from the linked documentation; examples and practical recommendations are our own. This is a documentation review, not a hands-on test of every provider account or feature. Interfaces, plans and commands can change.

Independent learning resource by Utilising AI Pty Ltd. No endorsement by the named providers is claimed. Review your chosen tool’s permissions and data handling before supplying business information.

Keep building your AI skills

Create your free assistant prompt Browse all six guides
Microsoft Copilot & GitHub Copilot | UtilisingAI