Experimental

A Development Journey

Building M365
Multi-Agent Collaboration

From vision to working system — with Amplifier as my co-developer

Diego Colombo · January 2026

Chapter 1

The Dream

"I want different instances of Amplifier to collaborate on a project — using Teams channels for posting findings, Planner for shared tasks, and M365 as a way to share context in a collaborative way."

— My initial request to Amplifier

💬

Teams Channels

Agents post findings and communicate

📋

Planner Tasks

Shared work plans and assignments

🤝

Shared Context

M365 as collaboration backbone

Chapter 2

The Challenge

Authentication hell, permissions maze, and licensing gotchas.

AADSTS65002: Consent between first party application '1950a258-227b-4e31-a9cf-717495945fc2' and first party resource '00000003-0000-0000-c000-000000000000' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens. # My reaction: "mm failed" "try device code again once and cache token"

This was just the beginning...

The Pain

Four Walls I Hit

🔐 Authentication Maze

Device Code Flow vs Client Credentials vs ROPC
Each method has different limitations
"Why not using client auth flow so you can capture the token?"

📝 Permission Iterations

"I granted the permission you wanted..."
"Test now, I granted the permission you asked"
"What do I need to add to permissions?"

🔑 MFA Complications

"The password is ... there can be MFA"
"Do you have options to automate the authenticator?"
"Ok let's exclude the agent accounts from MFA"

💳 Licensing Gotchas

Created users without licenses
"Users must have Microsoft Teams Enterprise"
"Microsoft 365 E5 (no Teams) isn't enough"

Chapter 3

Enter Amplifier

Not just an assistant — a co-developer that took work off my plate.

🏗️

zen-architect

Designed the complete architecture — auth flows, tool modules, bundle structure

🔧

modular-builder

Implemented 12+ tool modules across the platform and bundle

🧪

shadow-operator

Tested in isolated environments without breaking main session

The Pattern That Emerged

                I describe the vision
                →
                Amplifier architects
                →
                Amplifier builds
                →
                Amplifier tests
                →
                I grant permissions
            

Before Building

Amplifier Asked First

Authentication Method?

Client Credentials	App-only, best for automation
Device Code Flow	User signs in via browser
ROPC (chosen)	Automation with user context

Capabilities Needed?

✓ Users & Groups ✓ Email ✓ Teams ✓ Calendar ✓ Planner ✓ To-Do

"Do you have an Azure AD App Registration already? What specific capabilities do you need?"

— Amplifier, before writing a single line of code

Chapter 4

The Build

12+ modules created across the M365 platform — Graph API tools, governance hooks, and orchestration.

🔐 token_manager

🌐 graph_client

👥 m365_users

👥 m365_groups

📧 m365_email

💬 m365_teams

📅 m365_calendar

📋 m365_planner

✅ m365_todo

🟢 m365_presence

⚠️ errors

📄 bundle.md

amplifier-bundle-m365/ ├── bundle.md ├── pyproject.toml ├── src/amplifier_bundle_m365/ │ ├── auth/ │ │ ├── token_manager.py # ROPC + caching │ │ └── graph_client.py # HTTP client │ └── tools/ │ ├── m365_teams.py │ ├── m365_planner.py │ └── ... 6 more

12+ modules span amplifier-m365-platform (37 commits) and amplifier-bundle-m365-collab (9 commits)

Agent Personas

Five Collaborators Created

D

Diego

amplifier-diego

Research & Architecture

M

Marc

amplifier-marc

Review & Guidance

S

Samuel

amplifier-samuel

Testing & Validation

B

Brian

amplifier-brian

Final Review

A

Alex

amplifier-alex

Implementation

Each agent has their own M365 account with E5 license, excluded from MFA
All agents can post to Teams, create Planner tasks, and collaborate through the tenant

The Iteration

Permission by Permission

First attempt: AADSTS65002

Consent error — needed admin approval

"I granted the permissions you wanted"

Still failing — missing User.Read.All

Teams working, but no channel access

Added Channel.Message.Send

"Permission added for calendar"

Calendars.ReadWrite enabled

Full collaboration working!

Teams + Planner + Calendar integrated

PERMISSIONS GRANTED:

User.Read.All Group.ReadWrite.All Team.ReadBasic.All Channel.Message.Send Tasks.ReadWrite Calendars.ReadWrite Mail.ReadWrite Presence.Read.All

Safe Testing

Shadow Environments

"Use shadow environment so the current session is not compromised"

# Shadow test scenario 1. Create shadow with local source: /home/colombod/amplifier-bundle-m365 2. Install Amplifier + M365 bundle 3. Configure automation credentials 4. Test ROPC delegated auth for Diego 5. Post message to Findings channel ✓ Results verified in isolation

Why Shadow Testing?

Test auth changes without breaking main session
Isolated from production environment
Can fail safely and retry
Validates the complete integration

3

Shadow sessions created

Chapter 5

Proving It Works

"Can the agents use other collaborative features, not only Teams? Can they use Planner or To-Do lists? Set up tasks that a session on behalf of Marc can see, and produce a final response for Brian."

— Pushing for real multi-agent collaboration

1

Diego researches

Analyzes codebase, posts findings to Teams

2

Creates Planner tasks

Assigns work items to Marc and Samuel

3

Marc reviews

Sees the Planner tasks, reviews findings

4

Samuel validates

Tests integration points

5

Brian receives final report

All context aggregated from collaborative work

How It Works

Collaboration Architecture

MICROSOFT 365 TENANT

💬

Teams

📋

Planner

✅

To-Do

📅

Calendar

🟢

Presence

AGENT COLLABORATION LAYER

D

Diego

M

Marc

S

Samuel

B

Brian

A

Alex

Going Further

Agent Discovery

"Can the bundle help find other team members who are active and contributing?"

The Request

"Add discovery to see who is active and contributing — that would help with direct messages and call-outs"

See online/away status via Presence API
Know who's available for collaboration
Enable targeted communication

The Solution

# Check who's available presence = await m365_presence.get_user_presence() Diego: 🟢 Available Marc: 🟡 Away Samuel: 🟢 Available Brian: ⚫ Offline Alex: 🟢 Available # Route task to available agent

Chapter 6

What I Learned

Technical Insights

Auth is complex — Device Code vs Client Creds vs ROPC all have trade-offs
Permissions are iterative — expect multiple grant cycles
Licensing is hidden — E5 required for Teams features
MFA adds friction — automation accounts need exclusion
Token caching matters — asyncio.Lock prevents race conditions

Development Patterns

Vision first — describe what you want, not how to build it
Let AI architect — zen-architect designs better than I would
Test in isolation — shadow environments save sessions
Iterate on permissions — expect the cycle
Trust the delegation — agents know their domains

The Real Value

What Amplifier Did For Me

What I Would Have Done

Research Graph API documentation for hours
Write boilerplate auth code from scratch
Debug permission errors one by one
Build each tool module manually
Test in production, break things
Write documentation myself

~3–4 weeks

estimated without AI assistance

What Amplifier Did

Architected the complete solution
Implemented 12+ tool modules across the platform
Handled token caching with proper locking
Created comprehensive error handling
Tested in shadow environments
Generated documentation

1 day

elapsed calendar time for initial integration

My role: Vision, permissions, validation
Amplifier's role: Everything else

By The Numbers

The M365 Bundle

~54

conversation turns*

12+

platform modules

5

agent personas

3

shadow tests

5+

M365 services integrated

Teams, Planner, To-Do, Calendar, Email, Presence

8

Graph API permissions

Configured through iteration

1

day to working system

Elapsed calendar time for initial integration

*Approximate, from session analysis

Sources

Research Methodology

Data as of: February 20, 2026

Feature status: Experimental

Research performed:

• Git log: git log --oneline on ramparte/amplifier-bundle-m365-collab (9 commits)
• Git log: git log --oneline on amplifier-m365-platform (37 commits)
• Contributors: git log --format="%an" | sort | uniq -c
• File structure: find . -maxdepth 4 -type f

Gaps: Conversation turn count (~54) from session analysis, not independently verified. Time estimates for manual development are qualitative.

Primary contributor: Diego Colombo (featured developer/user); Platform: Sam Schillace (~76%), Marc Goodner (~24%)

The Takeaway

I described what I wanted.
Amplifier built it.

My job was vision, permissions, and validation.
Everything else was handled.

Started with

A vision

→

Ended with

Working multi-agent collaboration

Building M365Multi-Agent Collaboration