Here are the most common failure scenarios and solutions:
-
The subscription (
AZURE_SUBSCRIPTION_ID) doesn't have access to the Azure OpenAI service. Please ensureAZURE_SUBSCRIPTION_IDmatches the ID specified in the OpenAI access request process. -
You're attempting to create resources in regions not enabled for Azure OpenAI (e.g. East US 2 instead of East US), or where the model you're trying to use isn't enabled. See this matrix of model availability.
-
You've exceeded a quota, most often number of resources per region. See this article on quotas and limits.
-
You're getting "same resource name not allowed" conflicts. That's likely because you've run the sample multiple times and deleted the resources you've been creating each time, but are forgetting to purge them. Azure keeps resources for 48 hours unless you purge from soft delete. See this article on purging resources.
-
After running
azd upand visiting the website, the website takes a long time to load and answer on the first request. Because we're using serverless technologies, the first request to the Azure Functions API might take a few seconds to start up. This happens because the service is scaled to zero when not in use to optimize the costs, and it takes a few seconds to start up when it's first accessed. However, this slight delay can be removed by using the Azure Functions Premium plan.