AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/services/functions/templates/recipes/mcp/README.md

MCP (Model Context Protocol) Recipe

MCP tool endpoints for AI agent integration via the JSON-RPC 2.0 protocol.

Template Selection

Resource filter: mcp
Discover templates via MCP or CDN manifest where resource == "mcp" and language matches user request.

Protocol

MCP uses the JSON-RPC 2.0 protocol. Two template types with different transport support:

  • Extension-based (mcp-server-remote-*) supports both Streamable HTTP and SSE transports
  • Self-hosted (mcp-sdk-hosting-*) — supports Streamable HTTP only

See MCP Specification for protocol details.

Troubleshooting

Transport Mismatch

Cause: Client and server using different transports — SSE client gets 404/405, HTTP client gets unexpected text/event-stream.
Solution: Extension-based templates support both Streamable HTTP and SSE. Self-hosted templates support Streamable HTTP only. In VS Code mcp.json, set "type": "sse" or "type": "http" to match the server.

Missing App Settings After Deploy

Cause: Required app settings not configured on the function app.
Solution: Ensure protected resource metadata settings are present. For C# self-hosted servers, verify host.json arguments points to the compiled DLL path.

See MCP extension trigger and bindings for extension-based servers, Self-hosted MCP servers for self-hosted architecture, and MCP tutorial troubleshooting for self-hosted deployment issues.

Eval

| Path | Description | |------|-------------| | eval/summary.md | Evaluation summary | | eval/python.md | Python evaluation results |