# bhanutejagiddaluru/microsoft-copilot-agent-spectrum architecture

> Architecture diagram of the GitHub repository bhanutejagiddaluru/microsoft-copilot-agent-spectrum, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-03-31). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum
- Repository: https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum

## Overview

1. **What this repository is**
   - This is a **documentation-first demo repo** for Microsoft’s Copilot Agent Spectrum.
   - It does not contain application source code or deployable infrastructure; instead it describes how to assemble and govern three AI agent patterns using Microsoft enterprise services.

2. **Top-level architecture theme**
   - The repo’s core model is a progression of agent capability:
     - **Retrieval agent**: answers from trusted documents
     - **Task agent**: reads/writes to business systems
     - **Autonomous agent**: reacts to triggers and runs workflows with human review
   - The repo is organized to explain that progression, not to implement a single product.

3. **Main architectural building blocks**
   - The architecture centers on four layers:
     - **User or trigger source**: employee prompt, email arrival, or other event
     - **Agent layer**: Microsoft Copilot / Copilot Studio / Agent Builder
     - **Knowledge and action sources**: SharePoint, ServiceNow, Outlook/Exchange, Teams
     - **Workflow execution**: Power Automate for business process steps and connector orchestration
   - The output is a business outcome such as a grounded answer, a PTO update, or a draft reply.

4. **Retrieval agent boundary**
   - The retrieval pattern is a **read-only knowledge boundary**.
   - It uses **SharePoint-hosted enterprise documents** as the trusted source of truth.
   - The agent is expected to summarize and ground answers in approved content, not invent policy or data.
   - Example domain: HR benefits and policy Q&A.

5. **Task agent boundary**
   - The task pattern crosses from knowledge into **operational systems**.
   - It still uses SharePoint for policy grounding, but also reads and writes business records in **ServiceNow**.
   - **Power Automate** acts as the action orchestration layer for updates and workflow execution.
   - Example domain: checking vacation balances and submitting PTO changes.

6. **Autonomous agent boundary**
   - The autonomous pattern adds **event-driven execution**.
   - Instead of waiting for a user prompt, a trigger such as a **new email** starts the workflow.
   - The agent reads inbound content, searches supporting documentation, drafts a response, and saves it for review.
   - This pattern is explicitly constrained by **human-in-the-loop review** to avoid uncontrolled outbound actions.

7. **Shared enterprise services**
   - The repo repeatedly references the same enterprise integration set:
     - **Microsoft 365 Copilot / Agent Builder** for grounded Q&A experiences
     - **Copilot Studio** for building action-capable and trigger-based agents
     - **SharePoint** for curated knowledge sources
     - **Power Automate** for process automation and connector calls
     - **ServiceNow** for transactional HR data
     - **Outlook / Exchange** for email-triggered workflows
     - **Teams** as a likely user interaction surface
   - These are the practical integration points that define the architecture.

8. **Data flow pattern**
   - The common flow is:
     - source content or event enters the system
     - the agent retrieves context from SharePoint or another business system
     - the model generates a response or decision
     - if needed, Power Automate executes the business action
     - results are surfaced back to the user or stored for review
   - The repo emphasizes that the action step is what turns a chatbot into a business workflow tool.

9. **Governance and security boundary**
   - A major architectural concern in this repo is **controlled access**.
   - The docs stress least privilege, connector security, auditable behavior, and safe publishing.
   - The boundaries are important:
     - not all employees should see all PTO data
     - autonomous replies should not always be sent directly
   - This makes governance part of the architecture, not an afterthought.

10. **Repository structure as documentation architecture**
   - `docs/` contains the conceptual framework:
     - agent spectrum explanation
     - architecture overview
     - security and governance guidance
   - `demos/` contains walk-throughs for the three agent types.
   - `examples/` contains prompts and sample use cases.
   - `flows/` contains notes on Power Automate usage and flow patterns.
   - This structure mirrors the solution layers: concept, demo, prompt design, and workflow automation.

11. **Demo scenarios represented**
   - The repo illustrates three concrete business scenarios:
     - HR knowledge assistant
     - HR PTO assistant tied to ServiceNow
     - inbox auto-reply assistant using email triggers
   - These are not isolated examples; they map directly to the architecture progression from read-only to action-oriented to event-driven automation.

12. **Key diagramming takeaway**
   - If you draw this architecture, the main boxes should be:
     - **trigger/user**
     - **Copilot/Copilot Studio agent**
     - **SharePoint knowledge**
     - **Power Automate workflow layer**
     - **external business systems such as ServiceNow and Outlook**
     - **human review / approval**
   - The main arrows are knowledge retrieval, workflow action, and trigger-based execution, with governance surrounding all three.

Main entry points: [`docs/architecture-overview.md`](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/architecture-overview.md) (Architecture), [`docs/security-and-governance.md`](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/security-and-governance.md) (Governance), [`examples/prompts.md`](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/prompts.md) (Prompts), [`examples/sample-use-cases.md`](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/sample-use-cases.md) (Use cases)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_repo_docs["Repo docs"]
  node_agent_spectrum["Agent Spectrum<br/>doc<br/>[agent-spectrum.md]"]
  node_architecture_overview["Architecture<br/>doc"]
  node_security_governance["Governance<br/>doc"]
end

subgraph group_demos["Demos"]
  node_retrieval_demo["Retrieval demo<br/>walkthrough"]
  node_task_demo["Task demo<br/>walkthrough<br/>[task-agent-demo.md]"]
  node_autonomous_demo["Autonomous demo<br/>walkthrough"]
end

subgraph group_examples["Examples"]
  node_prompt_catalog["Prompts<br/>prompt set<br/>[prompts.md]"]
  node_sample_use_cases["Use cases<br/>examples"]
end

subgraph group_flows["Flows"]
  node_power_automate_notes["Flow notes<br/>automation notes"]
end

subgraph group_runtime["Agent runtime"]
  node_user_trigger(("User or trigger<br/>entry point"))
  node_copilot_agent["Copilot agent<br/>agent layer"]
  node_sharepoint_knowledge[("SharePoint<br/>knowledge source")]
  node_power_automate{{"Power Automate<br/>workflow layer"}}
  node_servicenow[("ServiceNow<br/>system of record")]
  node_outlook_exchange["Outlook / Exchange<br/>mail source"]
  node_teams_surface["Teams<br/>surface"]
  node_human_review{{"Human review<br/>approval gate"}}
end

node_agent_spectrum -->|"frames"| node_architecture_overview
node_architecture_overview -->|"bounded by"| node_security_governance
node_architecture_overview -->|"illustrated by"| node_retrieval_demo
node_architecture_overview -->|"illustrated by"| node_task_demo
node_architecture_overview -->|"illustrated by"| node_autonomous_demo
node_sample_use_cases -->|"maps to"| node_retrieval_demo
node_sample_use_cases -->|"maps to"| node_task_demo
node_sample_use_cases -->|"maps to"| node_autonomous_demo
node_prompt_catalog -->|"supports"| node_retrieval_demo
node_prompt_catalog -->|"supports"| node_task_demo
node_prompt_catalog -->|"supports"| node_autonomous_demo
node_power_automate_notes -->|"describes"| node_power_automate
node_user_trigger -->|"starts"| node_copilot_agent
node_copilot_agent -->|"retrieves"| node_sharepoint_knowledge
node_copilot_agent -->|"invokes"| node_power_automate
node_power_automate -->|"updates"| node_servicenow
node_power_automate -->|"reads/writes"| node_outlook_exchange
node_copilot_agent -->|"surfaces"| node_teams_surface
node_copilot_agent -->|"routes to"| node_human_review
node_human_review -->|"approves"| node_outlook_exchange
node_security_governance -->|"controls"| node_sharepoint_knowledge
node_security_governance -->|"controls"| node_servicenow
node_security_governance -->|"governs"| node_power_automate

click node_agent_spectrum "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/agent-spectrum.md"
click node_architecture_overview "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/architecture-overview.md"
click node_security_governance "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/security-and-governance.md"
click node_retrieval_demo "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/retrieval-agent-demo.md"
click node_task_demo "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/task-agent-demo.md"
click node_autonomous_demo "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/autonomous-agent-demo.md"
click node_prompt_catalog "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/prompts.md"
click node_sample_use_cases "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/sample-use-cases.md"
click node_power_automate_notes "https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/flows/power-automate-notes.md"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_agent_spectrum,node_architecture_overview,node_security_governance toneBlue
class node_retrieval_demo,node_task_demo,node_autonomous_demo toneAmber
class node_prompt_catalog,node_sample_use_cases toneMint
class node_power_automate_notes toneRose
class node_user_trigger,node_copilot_agent,node_sharepoint_knowledge,node_power_automate,node_servicenow,node_outlook_exchange,node_teams_surface,node_human_review toneIndigo
```

## Components

### Repo docs

Conceptual documentation and guidance files

- [Agent Spectrum](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/agent-spectrum.md): doc · Top-level concept for the retrieval, task, and autonomous progression · `docs/agent-spectrum.md`
- [Architecture](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/architecture-overview.md): doc · Repository-wide architecture framing and solution boundaries · `docs/architecture-overview.md`
- [Governance](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/docs/security-and-governance.md): doc · Security, access control, and safe publishing guidance · `docs/security-and-governance.md`

### Demos

Walkthroughs for the three agent patterns

- [Retrieval demo](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/retrieval-agent-demo.md): walkthrough · Read-only knowledge assistant scenario · `demos/retrieval-agent-demo.md`
- [Task demo](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/task-agent-demo.md): walkthrough · Operational assistant scenario with record updates · `demos/task-agent-demo.md`
- [Autonomous demo](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/demos/autonomous-agent-demo.md): walkthrough · Event-driven assistant scenario with human review · `demos/autonomous-agent-demo.md`

### Examples

Prompts and sample use cases

- [Prompts](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/prompts.md): prompt set · Representative prompts used to shape the agents · `examples/prompts.md`
- [Use cases](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/examples/sample-use-cases.md): examples · Business scenarios mapped to the agent patterns · `examples/sample-use-cases.md`

### Flows

Notes on Power Automate patterns

- [Flow notes](https://github.com/bhanutejagiddaluru/microsoft-copilot-agent-spectrum/blob/main/flows/power-automate-notes.md): automation notes · Power Automate usage and connector orchestration patterns · `flows/power-automate-notes.md`

### Agent runtime

The shared enterprise services and execution layers described by the repo

- **User or trigger**: entry point · Employee prompt, email arrival, or other event that starts the flow
- **Copilot agent**: agent layer · Microsoft Copilot, Copilot Studio, or Agent Builder experience
- **SharePoint**: knowledge source · Trusted enterprise documents and policy source of truth
- **Power Automate**: workflow layer · Process orchestration and connector execution layer
- **ServiceNow**: system of record · Transactional HR or business records used by task agents
- **Outlook / Exchange**: mail source · Inbound email and outbound draft storage for autonomous workflows
- **Teams**: surface · Likely employee interaction surface for agent experiences
- **Human review**: approval gate · Required review step before autonomous outbound actions

## Connections

- Agent Spectrum → Architecture: frames · Defines the repository's architecture narrative
- Architecture → Governance: bounded by · Architecture is constrained by governance requirements
- Architecture → Retrieval demo: illustrated by · Shows the read-only knowledge pattern
- Architecture → Task demo: illustrated by · Shows the action-capable pattern
- Architecture → Autonomous demo: illustrated by · Shows the event-driven pattern
- Use cases → Retrieval demo: maps to · Contains HR knowledge assistant scenario
- Use cases → Task demo: maps to · Contains PTO and ServiceNow scenario
- Use cases → Autonomous demo: maps to · Contains inbox auto-reply scenario
- Prompts → Retrieval demo: supports · Provides grounding prompts for Q&A
- Prompts → Task demo: supports · Provides task-oriented prompts
- Prompts → Autonomous demo: supports · Provides trigger and reply prompts
- Flow notes → Power Automate: describes · Explains workflow orchestration patterns
- User or trigger → Copilot agent: starts · Prompt or event enters the agent layer
- Copilot agent → SharePoint: retrieves · Grounds answers in trusted documents
- Copilot agent → Power Automate: invokes · Hands off actions to workflow orchestration
- Power Automate → ServiceNow: updates · Reads and writes HR or business records
- Power Automate → Outlook / Exchange: reads/writes · Consumes email triggers and stores drafts or replies
- Copilot agent → Teams: surfaces · Delivers the experience to employees
- Copilot agent → Human review: routes to · Requires approval before autonomous outbound action
- Human review → Outlook / Exchange: approves · Approved drafts can be saved or sent
- Governance → SharePoint: controls · Imposes least-privilege access to content
- Governance → ServiceNow: controls · Restricts access to transactional data
- Governance → Power Automate: governs · Covers connector security and auditable actions
