Question

Your team develops prompt flows in Azure AI Foundry and stores the flow definitions (including the flow.dag.yaml and prompt templates) in a Git repository. The team lead wants a repeatable process so that when a validated prompt change is merged into the main branch, the flow is automatically evaluated and deployed to the staging Foundry project without manual portal steps. Which approach best meets this requirement?

Accepted Answer

Configure a CI/CD pipeline (e.g., GitHub Actions) that, on merge to main, uses the Azure CLI/az ml commands to run the flow evaluation and deploy the flow to the staging project

Answer

Have each developer manually export the flow from the Foundry portal and re-import it into the staging project after every merge

Answer

Store the prompt templates as secrets in Azure Key Vault so that the staging project automatically picks up the latest version on merge

Answer

Enable autosave on the authoring flow so changes replicate directly to the staging project in real time