microsoft-docs
Verifiedby github · Updated Apr 16, 2026
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
See It In Action
I'll query official Microsoft docs for all four topics in parallel.
Let me query all four topics in parallel using the Learn CLI and web searches.
Now let me read the existing project files for context, and search for a few more specific sub-topics.
Good, I now have the full context from the handbook and incident notes. Let me get the remaining specific URLs needed.
I have all the verified URLs. Let me create the source-of-truth doc.
Created docs-source-of-truth.md. Here's what it covers:
4 sections matching the handbook, each with:
- The correct docs surface (learn.microsoft.com vs. aspire.dev vs. code.visualstudio.com vs. GitHub)
- Verified, working URLs for every link the handbook had wrong
- Answers to all open questions from the handbook
- Version/package notes
Key corrections made:
- Azure Blob Storage — replaced old
docs.microsoft.comURLs with currentlearn.microsoft.compaths; added managed identity + upload tutorial link - Aspire — integration docs (Redis
AddRedis, PostgresAddPostgres) point to aspire.dev, not Learn - VS Code — all links now point to code.visualstudio.com/docs (never been on Learn);
debugpyattach config and Remote-SSH docs linked - Agent Framework — DevUI REST API reference is now published on Learn; workflow orchestration patterns (sequential, handoff, magentic, etc.) all have individual verified pages; GitHub repo linked for API-level detail ahead of published docs
A quick-reference surface map table at the bottom summarizes which site to use for what.
External Tools
| Tool | Type |
|---|---|
| context7 | mcp |
| aspire | mcp |
| node | binary |
| npx | binary |
| npm | binary |
Permissions
| Scope | Description |
|---|---|
| network:outbound | |
| process:spawn |
SKILL.md
Microsoft Docs
Research skill for the Microsoft technology ecosystem. Covers learn.microsoft.com and documentation that lives outside it (VS Code, GitHub, Aspire, Agent Framework repos).
Default: Microsoft Learn MCP
Use these tools for everything on learn.microsoft.com — Azure, .NET, M365, Power Platform, Agent Framework, Semantic Kernel, Windows, and more. This is the primary tool for the vast majority of Microsoft documentation queries.
| Tool | Purpose |
|---|---|
microsoft_docs_search | Search learn.microsoft.com — concepts, guides, tutorials, configuration |
microsoft_code_sample_search | Find working code snippets from Learn docs. Pass language (python, csharp, etc.) for best results |
microsoft_docs_fetch | Get full page content from a specific URL (when search excerpts aren't enough) |
Use microsoft_docs_fetch after search when you need complete tutorials, all config options, or when search excerpts are truncated.
CLI Alternative
If the Learn MCP server is not available, use the mslearn CLI from your terminal or shell (for example, Bash, PowerShell, or cmd) instead:
# Run directly (no install needed)
npx @microsoft/learn-cli search "BlobClient UploadAsync Azure.Storage.Blobs"
# Or install globally, then run
npm install -g @microsoft/learn-cli
mslearn search "BlobClient UploadAsync Azure.Storage.Blobs"
| MCP Tool | CLI Command |
|---|---|
microsoft_docs_search(query: "...") | mslearn search "..." |
microsoft_code_sample_search(query: "...", language: "...") | mslearn code-search "..." --language ... |
microsoft_docs_fetch(url: "...") | mslearn fetch "..." |
Pass --json to search or code-search to get raw JSON output for further processing.
Exceptions: When to Use Other Tools
The following categories live outside learn.microsoft.com. Use the specified tool instead.
.NET Aspire — Use Aspire MCP Server (preferred) or Context7
Aspire docs live on aspire.dev, not Learn. The best tool depends on your Aspire CLI version:
CLI 13.2+ (recommended) — The Aspire MCP server includes built-in docs search tools:
| MCP Tool | Description |
|---|---|
list_docs | Lists all available documentation from aspire.dev |
search_docs | Weighted lexical search across aspire.dev content |
get_doc | Retrieves a specific document by slug |
These ship in Aspire CLI 13.2 (PR #14028). To update: aspire update --self --channel daily. Ref: https://davidpine.dev/posts/aspire-docs-mcp-tools/
CLI 13.1 — The MCP server provides integration lookup (list_integrations, get_integration_docs) but not docs search. Fall back to Context7:
| Library ID | Use for |
|---|---|
/microsoft/aspire.dev | Primary — guides, integrations, CLI reference, deployment |
/dotnet/aspire | Runtime source — API internals, implementation details |
/communitytoolkit/aspire | Community integrations — Go, Java, Node.js, Ollama |
VS Code — Use Context7
VS Code docs live on code.visualstudio.com, not Learn.
| Library ID | Use for |
|---|---|
/websites/code_visualstudio | User docs — settings, features, debugging, remote dev |
/websites/code_visualstudio_api | Extension API — webviews, TreeViews, commands, contribution points |
GitHub — Use Context7
GitHub docs live on docs.github.com and cli.github.com.
| Library ID | Use for |
|---|---|
/websites/github_en | Actions, API, repos, security, admin, Copilot |
/websites/cli_github | GitHub CLI (gh) commands and flags |
Agent Framework — Use Learn MCP + Context7
Agent Framework tutorials are on learn.microsoft.com (use microsoft_docs_search), but the GitHub repo has API-level detail that is often ahead of published docs — particularly DevUI REST API reference, CLI options, and .NET integration.
| Library ID | Use for |
|---|---|
/websites/learn_microsoft_en-us_agent-framework | Tutorials — DevUI guides, tracing, workflow orchestration |
/microsoft/agent-framework | API detail — DevUI REST endpoints, CLI flags, auth, .NET AddDevUI/MapDevUI |
DevUI tip: Query the Learn website source for how-to guides, then the repo source for API-level specifics (endpoint schemas, proxy config, auth tokens).
Context7 Setup
For any Context7 query, resolve the library ID first (one-time per session):
- Call
mcp_context7_resolve-library-idwith the technology name - Call
mcp_context7_query-docswith the returned library ID and a specific query
Writing Effective Queries
Be specific — include version, intent, and language:
# ❌ Too broad
"Azure Functions"
"agent framework"
# ✅ Specific
"Azure Functions Python v2 programming model"
"Cosmos DB partition key design best practices"
"GitHub Actions workflow_dispatch inputs matrix strategy"
"Aspire AddUvicornApp Python FastAPI integration"
"DevUI serve agents tracing OpenTelemetry directory discovery"
"Agent Framework workflow conditional edges branching handoff"
Include context:
- Version when relevant (
.NET 8,Aspire 13,VS Code 1.96) - Task intent (
quickstart,tutorial,overview,limits,API reference) - Language for polyglot docs (
Python,TypeScript,C#)
FAQ
What does microsoft-docs do?
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
When should I use microsoft-docs?
Use it when you need a repeatable workflow that produces text report.
What does microsoft-docs output?
In the evaluated run it produced text report.
How do I install or invoke microsoft-docs?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does microsoft-docs support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does microsoft-docs need?
It uses context7, aspire, node, npx, npm; channels commonly include text; permissions include network:outbound, process:spawn.
Is microsoft-docs safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is microsoft-docs different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does microsoft-docs outperform not using a skill?
About microsoft-docs
When to use microsoft-docs
You need authoritative Microsoft docs or code samples for Azure, .NET, Windows, or related platforms. You need documentation from Microsoft-adjacent sites outside learn.microsoft.com such as aspire.dev, VS Code docs, or GitHub docs. You want to research API details, tutorials, configuration guidance, or CLI usage across the Microsoft ecosystem.
When microsoft-docs is not the right choice
You only need general web search rather than official Microsoft documentation sources. You need to execute deployments, manage cloud resources, or modify services rather than look up documentation.
What it produces
Produces text report.