Copilot Studio Pattern Library

Only read the pattern file relevant to the current task — do NOT read all files.

How to use patterns

Patterns are recommendations, not requirements. How you present them depends on your role:

If you are the Advisor agent:

• Present each pattern as a suggestion — explain the challenge it solves and why it's relevant
• Use status-appropriate language:
  • proven: "This is a proven pattern used in production — consider it for…"
  • recommended: "A recommended approach that works well — consider it for…"
  • experimental: "This is an experimental approach, not yet fully validated — you may want to test thoroughly before adopting"
• Always say "you could consider…" or "a common approach is…", never "you must…"
• Let the user decide — do NOT auto-apply patterns without confirmation

If you are the Author agent:

• When implementing a pattern the user or Advisor has already chosen, read the relevant pattern file for the correct YAML structure