Microsoft 365 Agents SDK is a C# and .NET software development kit for building agents that interact with users across Microsoft 365, Teams, Copilot Studio, Webchat, and selected third-party services. Developers use it to handle conversations, coordinate requests, generate responses, and enable collaboration between agents. The catalogue entries provide coding-agent instructions and agents for working with this SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agents-for-net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Agents-for-net/main/.github/instructions/oauth-flows.instructions.mdgit clone --depth 1 https://github.com/microsoft/Agents-for-netWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/microsoft/agents-for-net/oauth-flows)<a href="https://agentmods.dev/instructions/microsoft/agents-for-net/oauth-flows"><img src="https://agentmods.dev/badge/instructions/microsoft/agents-for-net/oauth-flows/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/microsoft/agents-for-net/oauth-flows"><img src="https://agentmods.dev/badge/instructions/microsoft/agents-for-net/oauth-flows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00574 | $0.00574 |
| Opus 5.5 | $0.00230 | $0.00230 |
| Sonnet 5.5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
Agents-for-net oauth-flows.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OAuth & User Sign-In Flow Context
When working on OAuth, token exchange, or user sign-in code, reference these sequence diagrams:
docs/teams-sso-sequence-diagram.md— High-level Teams SSO scenarios (SignedIn, No Consent, Consent Required, Exchange Failure)docs/oauth-internal-sequence-diagram.md— Detailed internal flow through UserAuthorization → UserAuthorizationDispatcher → AzureBotUserAuthorization → OAuthFlow → IUserTokenClient
Key Design Points
- Sign-in is a multi-turn operation — flow state is stored between turns. Successful completion marks the flow inactive and persists it; terminal failures and reset/sign-out paths delete it.
- The Token Service Client caches successful tokens from
GetTokenOrSignInResource. - If OBO is configured, OBO is performed on the token returned by Token Service prior to setting the Turn Token.
- A Continuation Activity is stored when sign-in starts and replayed proactively after successful token acquisition.
- ConsentRequired (412) triggers Teams to prompt the user, followed by another
signin/tokenExchangeinvoke.signin/verifyStateis the separate interactive magic-code completion path. - Non-consent exchange failures return 400 — Teams will NOT retry.
Related Source Files
| Component | Path |
|---|---|
| UserAuthorization (App-level) | src/libraries/Builder/Microsoft.Agents.Builder/App/UserAuth/UserAuthorization.cs |
| UserAuthorizationDispatcher | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/UserAuthorizationDispatcher.cs |
| AzureBotUserAuthorization | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/AzureBotUserAuthorization.cs |
| OAuthFlow | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/OAuthFlow.cs |
| UserTokenClientWrapper | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/UserTokenClientWrapper.cs |
| IUserTokenClient | src/libraries/Client/Microsoft.Agents.Connector/IUserTokenClient.cs |
| OBOExchange | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/OBOExchange.cs |
| Authentication.Msal | src/libraries/Authentication/Authentication.Msal/ |
| High-level diagrams | docs/teams-sso-sequence-diagram.md |
| Detailed internal diagrams | docs/oauth-internal-sequence-diagram.md |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 27d ago Changed · +24 tokens per session 4677632ef31d
- 2mo ago First seen · 40 lines · 550 tokens per session scan A d5e1d5493d70
Agents-for-net oauth-flows.instructions.md is an instructions file published in the GitHub repository microsoft/Agents-for-net (183 stars, last pushed today), licensed MIT. It adds 574 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.