magodo
LGTM! 
@sahilvarmacsi If your user account has the right permission, then you shall [auth via Azure CLI](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/azure_cli).
By looking at the Portal, the request for the sql server level is targeting to: `/subscriptions/xxxx/resourceGroups/test-rg/providers/Microsoft.Sql/servers/acctest-sqlserver-344/auditingSettings/default?api-version=2021-11-01-preview`, which is defined in https://github.com/Azure/azure-rest-api-specs/blob/c1d839d48ee936c9338431c38f2cbbfbc9879ea2/specification/sql/resource-manager/Microsoft.Sql/preview/2022-11-01-preview/BlobAuditing.json#L61. (Note that this endpoint only has `GET` and `PUT`)....
@andreykaipov Sorry for the slow response... I agree to expand the check here. Even further I'd suggest to move all the update condition checks to the `CustomizeDiff` function, so that...
You're right that we can't call API in the customize diff. I've tried to run the test, but it failed with: ``` ------- Stdout: ------- === RUN TestAccEventHub_dedicatedClusterPartitionCountUpdate === PAUSE...
Tset is passing. Note the failing test cases are iirelevant to this change.
@Oracen Sorry that you run into this issue.. The provider actually simply calls the underlying Azure SDK to send the creation request to Azure, which you can see via enabling...
Hi @IbrahimUmar Thank you for reaching out! Regarding your question: > Is there any tool or work around where we can reverse engineer the azure subscription exported to terraform code....
@IbrahimUmar Can you elaborate more on these security restrictions? E.g. If your principal lacks of permissions to `terraform import` a specific resource type, then it is beyond the scope of...