Terraform scenarios to set up Azure Cosmos DB with 'InvalidResourceId' scenarios despite correct configuration
Hey everyone, I'm running into an issue that's driving me crazy... I'm relatively new to this, so bear with me. I'm trying to provision an Azure Cosmos DB account using Terraform, but I'm running into an 'InvalidResourceId' behavior when I apply my configuration. Here's the relevant snippet of my Terraform code: ```hcl resource "azurerm_resource_group" "example" { name = "example-resources" location = "East US" } resource "azurerm_cosmosdb_account" "example" { name = "example-cosmosdb" location = azurerm_resource_group.example.location resource_group_name = azurerm_resource_group.example.name offer_type = "Standard" kind = "GlobalDocumentDB" consistency_policy { consistency_level = "Session" } database_accounts_capabilities { name = "EnableAggregationPipeline" } } ``` When I run `terraform apply`, I get the following behavior: ``` behavior: expected properties to be set for resource "azurerm_cosmosdb_account" "example": InvalidResourceId ``` I double-checked that my resource group exists and the name is spelled correctly. I also confirmed that I'm using the latest version of the `azurerm` provider (2.88.0). I attempted to change the `name` of the Cosmos DB to something different, but the behavior continues. Additionally, I verified my Azure subscription and service limits to ensure I haven’t hit any quota limits. I even tried removing the `database_accounts_capabilities` block to see if that was causing the scenario, but it didn't help either. Does anyone have insights on what might be causing this behavior or any suggestions on how to troubleshoot further? Thanks in advance! Any ideas what could be causing this?