> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/planning-and-installation/weka-installation-on-azure/troubleshooting.md).

# Troubleshooting

During the deployment process, errors may occur. You can use the Azure Console tools to verify the resource status and the Azure quota limitations.

For additional Terraform logs during the WEKA cluster deployment, you can run the Terraform with the option `TF_LOG variable=ERROR`.

The following is a partial list of errors and the corrective actions that may occur during the deployment:

### Error when creating virtual machines

When deploying the WEKA cluster, an error indicates that more virtual machines have been requested than the quota limit in your Azure subscription.

**Resolution:**

Submit a quota increase to Microsoft Azure using the URL specified in the error message.

For more details, see [Increase VM-family vCPU quotas](https://learn.microsoft.com/en-us/azure/quotas/per-vm-quota-requests) on the Microsoft site.

### The storage account name is already taken

Creating a storage account name must be unique across the Azure environment.

**Resolution:**

In the Terraform variables file, ensure the `prefix` and `cluster_name` variables are unique.

The specified resource group in the Terraform variables file was not found because it was not created (as part of the prerequisites).

**Resolution:**

Create the Azure resource group before applying the Terraform file using the Azure console or Azure CLI.

In Azure CLI, use the following command:

`az group create --name <myResourceGroup> --location <region>`

Example:

`az group create --name weka-jack-rg --location eastus`

**Related topics**

[Deployment on Azure using Terraform](/planning-and-installation/weka-installation-on-azure/deployment-on-azure-using-terraform.md#prerequisites)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.weka.io/planning-and-installation/weka-installation-on-azure/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.