Thanks for the report. The language server bundles ~250 provider schemas to provide a helpful out-of-the-box experience. The bundled azuread schema in the current terraform-ls release is v2.43.0, which still contains the application_id. This would explain the discrepancy.
However, when we detect a local provider installation, we use this schema to be more accurate. So, if you run terraform init in your configuration, the editor should use the latest local schema.
Thank you! I primarily run terraform commands in a workflow as opposed to locally so this was helpful. I did need to provide the optional “-upgrade” flag to terraform to use v2.45. After doing so my editor is clear of errors.
For reference:
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/azuread: locked provider Terraform Registry 2.44.1 does not match configured version constraint ~> 2.45; must use
│ terraform init -upgrade to allow selection of new versions