How microsoft/deploy-your-ai-application-in-production works
Main Components
• Infrastructure orchestration: The “infra” directory holds the Bicep files and JSON templates that provision core resources.
• Network components: Virtual Network, private endpoints (see infra/modules/virtualNetwork.bicep, privateEndpoints.bicep).
• Compute resources: The jumpbox virtual machine is used for admin access (as mentioned in the README) and potentially other managed compute resources (e.g., serverless functions from modules/functions.bicep).
• Data and storage: Includes optional databases such as Cosmos DB (modules/cosmosDb.bicep), SQL Server (modules/sqlServer.bicep) and storage account.
• Security components: Managed Identity, Key Vault, Microsoft Entra ID for authentication, API Management (as per the architecture steps outlined in the README).
• Additional modules: Custom types and VM provisioning modules (modules/customTypes, virtualMachine.bicep) and developer tooling support files (Dev Containers, GitHub workflows).
Relationships and Interactions
• Data flows from tenant users (logging in via Microsoft Entra ID and MFA) to the jumpbox VM and onward to the managed network.
• Communication between resources happens through private endpoints ensuring that external public traffic is blocked.
• API Management acts as the gateway between backend services and client applications.
• The infrastructure as code components (Bicep/JSON templates) tie together each resource, ensuring that network, compute, and storage resources are cohesively provisioned.
• Managed identities are used to secure communications among services without needing static credentials.
Architectural Patterns
• Infrastructure-as-Code: The extensive use of Bicep and JSON files indicates a declarative approach for resource provisioning.
• Network Isolation: The design follows a fully isolated production environment using virtual networking, jumpbox access and private endpoints.
• Security-by-Design: Incorporates role-based access control (via Entra ID), managed identities, and private endpoints to adhere to best practices.
• Modularity: The infra directory is modularized into separate components (Cosmos DB, SQL Server, VM, etc.) which supports extensibility and clarity.