│ Error: checking for presence of existing Resource Group (Subscription: “a2b28c85-1948-4263-90ca-bade2bac4df4”
│ Resource Group Name: “kkvasu-rg”): unexpected status 403 (403 Forbidden) with error: AuthorizationFailed: The client ‘581d421b-bc99-4dfd-a69f-3ea712557f4a’ with object id ‘fd092b4f-d04d-4413-bd41-2771caf79ea7’ does not have authorization to perform action ‘Microsoft.Resources/subscriptions/resourceGroups/read’ over scope ‘/subscriptions/a2b28c85-1948-4263-90ca-bade2bac4df4/resourceGroups/kkvasu-rg’ or the scope is invalid. If access was recently granted, please refresh your credentials.
│
│ with azurerm_resource_group.rg,
│ on main.tf line 33, in resource “azurerm_resource_group” “rg”:
│ 33: resource “azurerm_resource_group” “rg” {
Could you please share the link to the lab?
here is the link
https://learn.kodekloud.com/learn/courses/terraform-on-azure/module/2dc00bf7-fa00-41df-a4e0-bce9fb23c19d/lesson/bf7e8242-be6f-4b24-9430-ebf52a7cf142
In our labs, we “pre-create” a resource group for you, and that’s the one you should use – you don’t create a new resource group, and you don’t need one.
In a console, and you have a resource group pop-up, you select the existing RG from that pop-up.
In a terminal that’s set up for azure’s az cli, you can find the RG by doing “az group list”.