Deployment errors (cosmosdb, apim and graphrag-deploy) while deploying graphRAG

Question

Hi,

I'm facing three issues while deploying graphRAG using this command bash deploy.sh -p deploy.parameters.json :

1- cosmodb deployment: having this error log:

Database account creation failed. Operation Id: xxxxxx, Error : Message: {"code":"ServiceUnavailable","message":"Sorry, we are currently experiencing high demand in East US region, and cannot fulfill your request at this time Thu, 04 Jul 2024 20:10:22 GMT. To request region access for your subscription, please follow this link https://aka.ms/cosmosdbquota for more details on how to create a region access request.

2- apim deployment, with this error:

Api service already exists: apim-xxxx (Code: ServiceAlreadyExists)

3- graphrag-deploy :

Deployment failed with multiple errors:

'Authorization failed for template resource 'xxxx' of type 'Microsoft.Authorization/roleAssignments'. The client 'live.com#xxx' with object id 'xxxx' does not have permission to perform action 'Microsoft.Authorization/roleAssignments/write' at scope '/subscriptions/xxx/resourceGroups/graphRAG/providers/Microsoft.	

Can you help with this? Thx

Answer 1

I will split your issue into 3 parts :

Part 1 :

• The East US region is experiencing high demand. Consider deploying your Cosmos DB account in a different region that has availability.
• Follow the link provided in the error message to request region access for your subscription. This can help increase the quota for the desired region.
• Sometimes, these issues are temporary. Retry the deployment after some time.

Part 2 :

• Verify if the API Management service apim-xxxx already exists in your subscription. If it does, you might need to update the existing service rather than trying to create a new one.
• If the service already exists and you need a new one, change the name of the API Management service in your deploy.parameters.json file to a unique name.
• If the existing service is not needed, consider deleting it and redeploying.

Part 3 :

The error indicates that the client does not have the necessary permissions to assign roles. Ensure that the client has the Owner or User Access Administrator role assigned at the subscription or resource group level.