Many surfaces
Microsoft 365, Copilot Studio, Power Platform, GitHub, Azure, and Azure DevOps each reveal a piece of the estate.
The control plane for Microsoft agents
Operate your agent estate with evidence.
Celest starts with a read-only Agent Estate Review that joins available evidence across the Microsoft estate—inventory, ownership, access, tools, usage, cost, and risk—without pretending that missing data is known.
inventoryownershipaccesstoolsusagecostrisk
Read-only by design. Evidence before action.
Illustrative estate / evidence plane
Sample Microsoft agent estate
Read-only
The operating gap
The cloud is connected.
The operating model isn't.
An agent can cross products. The evidence, authority, and accountability usually cannot.
One unclear state
Ownership, identity, tools, usage, cost, risk, and lifecycle status rarely join into one durable record.
Manual decisions
Specialists connect evidence to spreadsheets, tickets, and approvals by hand—or skip the step entirely.
No closed loop
An API response is not proof that the intended change happened, or that the finding is resolved.
The destination is a canonical path for humans and agents from observation → decision → bounded action → verified outcome.
- Microsoft 365
- Copilot Studio
- Power Platform
- GitHub
- Azure DevOps
- Azure
The starting offer · design-partner delivery
Start read-only.
Earn the right to act.
A fixed-scope, two-week Microsoft Agent Estate Review is designed to turn available registry, configuration, usage, cost, security, and ownership evidence into an operating plan.
Normalized inventory with source and join provenance.
Findings that preserve false, zero, unknown, and unavailable.
Prioritized proposed work with expected outcomes.
A 30/60/90-day AgentOps operating plan.
Development proof
Read-only Estate Review
Supported read-only sync and empty-estate persistence are proven in Dev. Populated detail, findings, and acknowledgement validation are in progress.
Trust gate
Propose + approve
Inspect-only lifecycle plans and explicit authority decisions are the next controlled step.
Roadmap
Execute + reconcile
Provider actions, immutable receipts, and fresh observed state follow evidence—not precede it.
The governed-action vision
Trust is a lifecycle,
not a checkbox.
The current Dev boundary proves read-only discovery and diagnosis contracts. Populated-estate validation is in progress; every action step remains roadmap.
- 01
Discover Dev proof
Collect scoped state with source health and provenance.
- 02
Diagnose Dev proof
Turn supported evidence into deterministic findings.
- 03
Propose roadmap
Explain work, rationale, scope, and expected effect.
- 04
Approve roadmap
Make human or policy authority explicit.
- 05
Execute roadmap
Use provider-native actions within bounded scope.
- 06
Verify roadmap
Capture immutable receipts, not just success codes.
- 07
Reconcile roadmap
Re-read state and close the originating loop.
Evidence before action. Unknown stays unknown. Authority is data. Provider-native power survives the abstraction.
The same insight, one layer higher
Remove the seams between intent and the cloud.
After creating Amplify Flutter at AWS, Dillon took the original Celest through Y Combinator W24 as “The Vercel of Flutter”: keep builders in Dart while Celest handled the cloud. The reborn Celest applies that same insight one layer higher—to human-plus-agent organizations operating across Microsoft.
“Remove the seams between what a builder intends and what the cloud requires.”
Microsoft Agent Estate Review
Turn agent sprawl into an operating plan.
We’re opening a small number of design-partner reviews for Microsoft-centric teams moving from Copilot pilots to an operating model. Bring a bounded tenant scope; together we’ll map the evidence that exists and the gaps that still need proving.