Skip to content

Provision Azure infrastructure for ZavaStorefront Web (dev env, Bicep/AZD) #29

@yortch

Description

@yortch

Provision Azure infrastructure for the ZavaStorefront web application as a development environment.

Requirements:

  • All resources should be deployed to a single resource group in westus3.
  • Use Azure Developer CLI (azd) in conjunction with Bicep to define and deploy the infrastructure.

Resources needed:

  • App Service (Linux) for a web app, deployment should use Docker container images. (No Docker installation required on local machine)
  • Azure Container Registry (ACR) for storing Docker images. AppService should use Azure RBAC (not passwords/secrets) to pull images from ACR.
  • Application Insights for monitoring the App Service.
  • Microsoft Foundry: enable/support GPT-4 and Phi model access (these are available in westus3).

Other notes:

  • All resources—App Service, ACR, Application Insights, Foundry—should be in the same region and resource group.
  • Include scripts/instructions for using azd for provisioning and deployments, emphasizing no need for local Docker.
  • Set up RBAC-based authentication between resources; no secrets in code or config files.

Acceptance Criteria:

  • Bicep definitions for all listed resources
  • azd templates/scripts for provisioning
  • AppService configured to pull Docker images from ACR using managed identity (via RBAC)
  • Monitoring enabled via Application Insights
  • Foundry is available for use with GPT-4 and Phi models
  • Everything deploys via a single azd up command

This is a dev environment setup for rapid iteration, not production.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions