AVM Post Deployment Guide

July 23, 2026 · View on GitHub

📋 Note: This guide is specifically for post-deployment steps after using the AVM template. For complete deployment from scratch, see the main deployment guide.

This document provides guidance on post-deployment steps after deploying the Chat with your data - Solution accelerator from the AVM (Azure Verified Modules) repository.

Pre-requisites

Ensure you have a Deployed Infrastructure - A successful Chat with your data - Solution accelerator deployment from the AVM repository

Post Deployment Steps

Step 1: Build, Push, and Update Container Images

Open Azure Cloud Shell (Bash) or a local terminal and clone the repository first if you haven't already:

az login
git clone https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator.git
cd chat-with-your-data-solution-accelerator

Important: The post-deployment scripts require Azure CLI version 2.87.0 or later. Check your version with az version and upgrade with az upgrade if needed.

Then build and push the application images to your Azure Container Registry and update the Container Apps:

Bash (Cloud Shell / Linux / macOS):

bash infra/scripts/post-provision/acr_build_push_update.sh -g "<your-resource-group-name>"

PowerShell (Windows):

.\infra\scripts\post-provision\acr_build_push_update.ps1 -ResourceGroupName "<your-resource-group-name>"

By default, images are built remotely using az acr build (no local Docker required). To build locally with Docker instead, use --mode local in Bash or -Mode local in PowerShell.

Step 2: Run the Post-Deployment Setup Script

Run the post-deployment setup script to configure the Function App client key and create PostgreSQL tables (if applicable):

Bash (Cloud Shell / Linux / macOS):

bash infra/scripts/post-provision/post_deployment_setup.sh "<your-resource-group-name>"

PowerShell (Windows):

.\infra\scripts\post-provision\post_deployment_setup.ps1 -ResourceGroupName "<your-resource-group-name>"

Note: The script auto-discovers all resources in the resource group. It handles private networking (WAF) deployments by temporarily enabling public access, performing the setup, then restoring the original state.

Step 3: Configure App Authentication

  1. After deployment is complete, navigate to your Container App in the Azure portal
  2. Follow the detailed instructions in Set Up Authentication to add authentication to your web app
  3. This will ensure only authorized users can access your application

Step 4: Access and Configure the Admin Interface

  1. Navigate to the admin interface at the /admin path of your frontend Container App:

    https://<frontend-container-app-name>.<region>.azurecontainerapps.io/admin

  2. Upload your documents:

    • Select Ingest Data from the admin interface
    • Upload your documents using the drag-and-drop interface
    • For testing purposes, you can use the sample data located in the /data directory of this repository

    Admin interface

  3. Monitor the ingestion process:

    • Wait for the documents to be processed and indexed
    • Verify successful ingestion through the admin interface

Step 5: Access the Chat Application

  1. Navigate to the chat application at the root of your frontend Container App:

    https://<frontend-container-app-name>.<region>.azurecontainerapps.io/

  2. Test the chat functionality:

    • Start a conversation by asking questions about your uploaded documents
    • Verify that the AI responds with relevant information from your data

Next Steps

Consider these additional configurations for enhanced functionality: