[BUG] Issue with deploy.sh in az deployment group create

[ntsarb]

Describe the bug
graphrag-accelerator version: 2.3.0

I use the Deployment Guide and, on Step 5 (in VS Code, using Dev Container), I invoke:

bash deploy.sh -p deploy.parameters.json

An unhelpful error message is presented, as shown below. I traced the issue to the deploy.sh script, line 357:
AZURE_DEPLOY_RESULTS=$(az deployment group create --name "$deployName" \

To help look deeper, I added the --debug option in the az deployment group create command. The complete log is attached.

I'd be grateful if you helped address this. Thank you

To Reproduce
Follow the instructions of the Deployment Guide. On Step 5 (using VS Code, Dev Container), invoke:

bash deploy.sh -p deploy.parameters.json

Expected behavior
The deployment should be completed successfully, or an informative error message to help resolve any issue should be shown.

Screenshots
See attached Log file.

Desktop (please complete the following information):

• OS: Windows 11 Pro for Workstations (VS Code)
• Version 10.0.26100 Build 26100

Additional context

Deployment Error.txt

The standard log, here, is not very helpful. See the attached .txt file containing the output with az's --debug parameter included.

$ bash deploy.sh -p deploy.parameters.json
   _____                 _     _____           _____
  / ____|               | |   |  __ \    /\   / ____|
 | |  __ _ __ __ _ _ __ | |__ | |__) |  /  \ | |  __
 | | |_ | '__/ _` | '_ \| '_ \|  _  /  / /\ \| | |_ |
 | |__| | | | (_| | |_) | | | | | \ \ / ____ | |__| |
  \_____|_|  \__,_| .__/|_| |_|_|  \_/_/_   \_\_____|
     /\           | | | |              | |
    /  \   ___ ___|_|_| | ___ _ __ __ _| |_ ___  _ __
   / /\ \ / __/ __/ _ | |/ _ | '__/ _` | __/ _ \| '__|
  / ____ | (_| (_|  __| |  __| | | (_| | || (_) | |
 /_/    \_\___\___\___|_|\___|_|  \__,_|\__\___/|_|


Checking for required tools... Done.
Checking required parameters... Done.
Setting environment variables...
        LOCATION = uksouth
        RESOURCE_GROUP = graphRAG_resource_group
        AI_SEARCH_AUDIENCE = https://search.azure.com
        AISEARCH_ENDPOINT_SUFFIX = search.windows.net
        APIM_TIER = Developer
        CLOUD_NAME = AzurePublicCloud
        GRAPHRAG_IMAGE = graphrag:backend
        PUBLISHER_EMAIL = publisher@microsoft.com
        PUBLISHER_NAME = publisher
        COGNITIVE_SERVICES_AUDIENCE = https://cognitiveservices.azure.com/.default
        GRAPHRAG_API_VERSION = 2023-03-15-preview
        GRAPHRAG_LLM_MODEL = gpt-4
        GRAPHRAG_LLM_MODEL_QUOTA = 80
        GRAPHRAG_LLM_MODEL_VERSION = turbo-2024-04-09
        GRAPHRAG_LLM_DEPLOYMENT_NAME = gpt-4
        GRAPHRAG_EMBEDDING_MODEL = text-embedding-ada-002
        GRAPHRAG_EMBEDDING_MODEL_QUOTA = 300
        GRAPHRAG_EMBEDDING_MODEL_VERSION = 2
        GRAPHRAG_EMBEDDING_DEPLOYMENT_NAME = text-embedding-ada-002
Checking cloud region for VM sku availability... Done.
Checking Location for SKU Quota Usage... Done.
Checking if resource group graphRAG_resource_group exists... Yes.
Checking if APIM was soft-deleted... Done.
Deploying Azure resources...
Deployment name: graphrag-deploy-2025-05-23_00-46-30
WARNING: The configuration value of bicep.use_binary_from_path has been set to 'false'.
ERROR: The content for this response was already consumed
 ________________________________
/  Uh oh, an error has occurred. \
\  Please see message below.     /
 ‾‾‾‾‾‾‾‾‾‾/‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
          /
      __ /
     /  \
    ~    ~
   / \  /_\
   \o/  \o/
    |    |
    ||   |/
    ||   ||
    ||   ||
    | \_/ |
    \     /
     \___/

Error deploying Azure resources...

[ntsarb]

To test my Azure account configuration, I deployed graphrag using the second method, from here. I manually deployed the ai models in azure openai and configured the graphrag settings. All worked fine.

I am still interested in deploying the accelerator solution, if possible.

[ntsarb]

Update: The issue was caused by the following setting of deploy.sh:
GRAPHRAG_LLM_MODEL_QUOTA="80"

The default quota for the LLM resources I had reserved on Azure was reportedly 8, so changing the above setting from 80 to 8 worked fine for the deployment. I'll have to update the quota in Azure for performance purposes, but it's fine for now, to learn how to use the platform.

Obviously due to my lack of experience with Azure, it took me longer to figure this out.

Ideally, if it's possible to update the script so that it stops for errors like this, it will be much easier to tell what went wrong.