This document provides guidance on deploying the Content Processing Solution Accelerator when you have limited Azure OpenAI model quota available.
By default, the solution requires:
- GPT model: 100,000 Tokens Per Minute (TPM)
If your Azure OpenAI service has lower quota limits, you can modify the deployment to work with reduced capacity.
Before proceeding, ensure you have:
- Azure Developer CLI (azd) installed
- Access to your Azure OpenAI service quota settings
- Knowledge of your current TPM limits
You have two approaches to deploy with less quota:
Remove the metadata section (lines 23-30) from the infra/main.bicep file:
@metadata({
azd: {
type: 'location'
usageName: [
'OpenAI.GlobalStandard.gpt-4o,100'
]
}
})Update the values on lines 77-78 in infra/main.bicep to match your available quota:
@metadata({
azd: {
type: 'location'
usageName: [
'OpenAI.GlobalStandard.gpt-4o,50' // Changed from 100
]
}
})After modifying the Bicep file, configure your deployment capacity:
azd env set AZURE_ENV_MODEL_CAPACITY="50"Note: Adjust the values (50) to match your actual available quota.
Once configured, proceed with deployment:
azd upFor optimal performance, we recommend maintaining at least 100,000 TPM for GPT models when possible.
For more detailed information, refer to:
- Deployment Guide - Complete deployment instructions
- Customizing azd Parameters - Advanced configuration options
- Check or update Quota - Check or update quota from Azure Portal
- Quota Check - Script for checking Azure OpenAI quota limits
-
The solution uses built-in Azure Developer CLI (azd) quota validation to prevent deployment failures. Specifically, azd performs pre-deployment checks to ensure sufficient quota is available i.e. 100k TPM for gpt model.
-
These quota thresholds are hardcoded in the infrastructure file because azd's quota checking mechanism doesn't currently support parameterized values. If your Azure OpenAI service has quota below these thresholds, the deployment will fail during the validation phase rather than proceeding and failing later in the process.
-
By following the steps above, you can either:
- Bypass quota validation entirely by removing the metadata block
- Lower the validation thresholds to match your available quota (e.g., 50,000 TPM)
-
This ensures successful deployment while working within your quota constraints.