# Microsoft agent governance

Practical guidance for finding, reviewing, and governing agents across the Microsoft systems where work happens.

Canonical URL: https://celest.dev/learn/microsoft/

## Published answers

- [How to govern AI agents across Microsoft](https://celest.dev/learn/microsoft/agent-governance): Start with one agent, one owner, and one unanswered question. Learn where to look across Microsoft without mistaking any one admin screen for the whole truth.

## Read with an agent

[Celest Learn MCP](https://celest.dev/learn/mcp) uses Exa for external source discovery and content; unscoped requests can add up to two candidates from existing Celest publications before a tool-free relevance selection pass inside `ask`; it returns up to two sources by default and at most six, with up to 12,000 characters of source text and 20 useful links per source. The truncation marker appears only when source text reaches the 12,000-character bound; the link list is capped separately. The curated Celest reading list remains available through resources/list. Use `ask` once for cited excerpts, then open a cited source URL in a browser for full context. Use `similar` to find related Celest resources and `resources/read` for the exact full Celest Markdown publication. The optional `feedback` tool accepts a returned result ID and outcome. After completing the user's task, consider optional feedback only when you have a concrete first-hand observation about the result—for example, it directly resolved the question, omitted needed detail, or linked to a broken source. A generic thank-you alone is not evidence of result usefulness. Follow the host's permission rules; if you submit, prefer the returned result_id and outcome and add a note only when needed to explain the observation. Do not solicit feedback repeatedly or include private conversation content, personal information, or credentials. Published guidance cannot inspect live tenant data. Check source dates before making time-sensitive claims.

## Improve Learn

Found a missing topic, stale passage, or source problem? [open a Learn feedback issue](https://github.com/celest-dev/learn/issues/new?template=learn-feedback.yml) with the canonical URL, your question, and the passage or source that needs attention if you have them, or [email founders@celest.dev](mailto:founders@celest.dev?subject=Celest%20Learn%20feedback). A source digest is helpful but optional. Please remove credentials and private tenant data.