| name | microsoft-docs |
| description | This skill should be used when the user asks to "look up Microsoft docs", "check Azure documentation", "find a .NET tutorial", "what are the limits for [service]", or needs official Microsoft Learn documentation for Azure, .NET, Microsoft 365, Power Platform, or Windows technologies — architecture overviews, quickstarts, configuration guides, limits, and best practices. |
| context | fork |
Microsoft Docs
Prerequisite: Requires Microsoft Learn MCP Server (https://learn.microsoft.com/api/mcp).
Tools
| Tool | Use For |
|---|
microsoft_docs_search | Find documentation—concepts, guides, tutorials, configuration |
microsoft_docs_fetch | Get full page content (when search excerpts aren't enough) |
When to Use
- Understanding concepts — "How does Cosmos DB partitioning work?"
- Learning a service — "Azure Functions overview", "Container Apps architecture"
- Finding tutorials — "quickstart", "getting started", "step-by-step"
- Configuration options — "App Service configuration settings"
- Limits & quotas — "Azure OpenAI rate limits", "Service Bus quotas"
- Best practices — "Azure security best practices"
Query Effectiveness
Good queries are specific:
# Bad: Too broad
"Azure Functions"
# Good: Specific
"Azure Functions Python v2 programming model"
"Cosmos DB partition key design best practices"
"Container Apps scaling rules KEDA"
Include context:
- Version when relevant (
.NET 8, EF Core 8)
- Task intent (
quickstart, tutorial, overview, limits)
- Platform for multi-platform docs (
Linux, Windows)
When to Fetch Full Page
Fetch after search when:
- Tutorials — need complete step-by-step instructions
- Configuration guides — need all options listed
- Deep dives — user wants comprehensive coverage
- Search excerpt is cut off — full context needed
Why Use This
- Accuracy — live docs, not training data that may be outdated
- Completeness — tutorials have all steps, not fragments
- Authority — official Microsoft documentation
