📋 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 Content processing solution accelerator from the AVM (Azure Verified Modules) repository.
After successfully deploying the Content Processing Solution Accelerator using the AVM template, you'll need to complete some configuration steps to make the solution fully operational.
Before starting the post-deployment process, ensure you have the following:
-
PowerShell (v7.0+ recommended) - Available for Windows, macOS, and Linux
-
Azure CLI (v2.50+) - Command-line tool for managing Azure resources
-
Git - Version control system for cloning the repository
-
Deployed Infrastructure - A successful Content processing solution accelerator deployment from the AVM repository
If you encounter issues running PowerShell scripts due to execution policy restrictions, you can temporarily adjust the ExecutionPolicy by running the following command in an elevated PowerShell session:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy BypassThis will allow the scripts to run for the current session without permanently changing your system's policy.
First, clone this repository to access the post-deployment scripts:
git clone https://github.com/microsoft/content-processing-solution-accelerator.git
cd content-processing-solution-acceleratorFollow the Post Deployment Steps section in the main Deployment Guide, which includes:
- Optional: Publishing Local Build Container to Azure Container Registry
- Register Schema Files
- Import Sample Data
- Add Authentication Provider
Once configuration is complete, see the Next Steps section in the main Deployment Guide to start using the solution.