What problem does it solve? Deploying a migrated ASP.NET MVC to Node.js + React application to Azure involves many decisions across hosting, databases, gateways, identity, and observability. This Skill provides a fixed reference topology, ready-to-use Bicep modules, Dockerfiles, and deployment recipes so teams can provision production infrastructure without designing everything from scratch. ## Core Features & Use Cases - Hosting decision matrix: Choose between Azure Static Web Apps, Container Apps, and App Service for the Vite SPA and Node.js API, with trade-offs documented for each path. - Bicep template set: Subscription-scoped main.bicep with modules for monitoring, Key Vault, PostgreSQL, Azure SQL, Blob Storage, Container Apps, Functions, Static Web Apps, and API Management. - Three deployment paths: All Container Apps, SWA + Container Apps API, or App Service PaaS, each with copy-paste CLI recipes and azd azure.yaml configuration. - Security and observability guidance: Managed identity, Key Vault secret references, APIM JWT validation policies, CSP headers, Application Insights setup, and alert thresholds. - Use Case: After migrating an ASP.NET MVC app to Node.js + React, ask the assistant to generate the Azure deployment assets; it copies the Dockerfile templates, parameterizes main.bicep, and walks you through az deployment sub what-if validation. ## Quick Start Ask the assistant to generate Azure deployment assets for the migrated Node.js API and React web app using the Bicep templates and a production parameter file.