terraform-provider-azuread VS terraform-provider-google

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

It can be for anything. Here is the provider for Azure Active Directory. It looks like it has over a million downloads this week alone so someone is using it..

Since the provider doesnt currently support licensing on [users directly](https://github.com/hashicorp/terraform-provider-azuread/issues/745) i think the only other option is to create a group that maintains specific licenses for user-members... however, that seems to be pay-walled behind Business Premium or azure ad p1

Not officially supported yet: https://github.com/hashicorp/terraform-provider-azuread/issues/68

The support for privileged identity management in Terraform is very limited. One open issue that tracks it is https://github.com/hashicorp/terraform-provider-azuread/issues/547

Source: https://github.com/hashicorp/terraform-provider-azuread/blob/main/internal/services/directoryroles/directory_role_resource.go

I haven't particularly worked with this, but if you're looking for things to see before doing, I would recommend looking at the examples provided by Microsoft: https://docs.microsoft.com/en-us/azure/developer/terraform/ and read through the provider documentation to see the individual pieces: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs

> DNS without CGO works perfectly

It does not. I know this because it impacts my daily work and the work of others. Honestly if you could make my day and go figure out exactly what's going wrong with the pure go DNS implementation it would make my life alot simpler and I wouldn't have to maintain shell scripts that update etc/hosts to hard code in ipv4 addresses for the APIs I access with terraform.

https://github.com/hashicorp/terraform-provider-google/issue...

GCP Terraform Provider

I think the equivalent for AWS is https://registry.terraform.io/providers/hashicorp/aws/latest/docs and for GCP https://registry.terraform.io/providers/hashicorp/google/latest/docs

There's an open issue in the gcp provider for exactly this. I'd recommend thumbs-upping it if you haven't already, as well as subscribing to notifications so you can see when there are updates.

only some people inside google could answer that but here's an issue already? https://github.com/hashicorp/terraform-provider-google/issues/11648

Not sure if you've solved for this or not, but it didn't work for me running terraform as a service account, it appears that it doesn't handle HTTP headers correctly: https://github.com/hashicorp/terraform-provider-google/issues/6738 but it does work with impersonation of that account, which is what I did. Note that your org can only have 1 access policy, and in my case I had to make google_access_context_manager_access_level anyways.

All I can find is an old thread saying cannot do. https://github.com/hashicorp/terraform-provider-google/issues/6413 Has there been any update to this, or does anyone know of a work around?

If you followed that request, you get to this PR which added the feature and updated this documentation