How to fix API version was not found for Microsoft in Terraform

If you don't have permission to register Resource Providers, use the skip_provider_registration flag in your Terraform provider block:

provider "azurerm" {
  skip_provider_registration = true
  features {}
}

Alternatively, use the newer resource_provider_registrations option set to "none" to disable auto-registration.

Use a recent version of the AzureRM provider in your terraform block. Older versions don't know about newer API versions:

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 4.0"
    }
  }
}

Run terraform init to update the provider, then check your provider's version history for API version updates.

The error typically includes a list of supported API versions for your region. For example, if the error says 'supported api-versions are 2021-06-01-preview', change your resource to use that version. Some resources don't expose API versions directly in Terraform, so this may require provider updates or using the AzAPI provider instead.

The user, service principal, or managed identity running Terraform must have permission to register Resource Providers. If you see a 403 AuthorizationFailed error with 'does not have authorization to perform action Microsoft.X/register/action', you need to either:

- Request elevated permissions (Contributor or higher role)
- Use skip_provider_registration = true if another admin has pre-registered the providers

If you need to use a specific API version or access the latest Azure features not yet available in AzureRM, switch to the AzAPI provider. It's a thin layer on top of the Azure REST APIs and allows you to specify any API version:

provider "azapi" {
  features {}
}

resource "azapi_resource" "example" {
  name      = "myResource"
  type      = "Microsoft.Foo/bars@2024-01-01"
  location  = "eastus"
}

You can use AzAPI alongside AzureRM. The aztfmigrate tool helps migrate resources between the two providers.