chore: upgrade `microsoft/fabric` Terraform provider from `1.3.0` to `1.10.0`

[katriendg]

Summary

All Terraform components and blueprints in edge-ai pin the microsoft/fabric provider at 1.3.0 (released June 2025). The latest stable version is 1.10.0 (released May 07, 2026). Upgrade is low-risk with no breaking changes for any resource currently used in the repo.

Files to Update (11 total)

• src/000-cloud/031-fabric/terraform/versions.tf
• src/000-cloud/031-fabric/terraform/modules/workspace/versions.tf
• src/000-cloud/031-fabric/terraform/modules/lakehouse/versions.tf
• src/000-cloud/031-fabric/terraform/modules/eventhouse/versions.tf
• src/000-cloud/031-fabric/ci/terraform/versions.tf
• src/000-cloud/032-fabric-rti/terraform/versions.tf
• src/000-cloud/032-fabric-rti/ci/terraform/versions.tf
• src/100-edge/130-messaging/terraform/modules/fabric-rti/versions.tf (currently >= 1.3.0, pin to 1.10.0)
• blueprints/fabric/terraform/versions.tf
• blueprints/fabric-rti/terraform/versions.tf
• blueprints/full-multi-node-cluster/terraform/versions.tf

Change each version = "1.3.0" (and >= 1.3.0) to version = "1.10.0".

Risk Assessment

Overall: LOW

The only breaking change across all 7 releases (fabric_workspace_git requiring git_credentials.source in v1.6.0) does not apply — fabric_workspace_git is not used anywhere in the repo.

One behavioral change to be aware of: v1.4.0 added capacity-state validation to fabric_workspace that errors if the assigned Fabric capacity is paused or suspended. v1.9.0 added skip_capacity_state_validation = true on the fabric_workspace resource to mitigate this if non-prod capacities are ever inactive.

Acceptance Criteria

• All 11 versions.tf files updated to version = "1.10.0"
• npm run tf-validate passes with no errors
• npm run tflint-fix-all passes with no errors
• Optional: add skip_capacity_state_validation = true to fabric_workspace in src/000-cloud/031-fabric/terraform/modules/workspace/main.tf if non-prod Fabric capacities may be paused

References

• Terraform Registry — microsoft/fabric 1.10.0
• GitHub Releases — terraform-provider-fabric

[PratikWayase]

I don't have access to an Azure subscription. Is there a way to run tf-validate locally without Azure authentication, or is it expected that CI performs this validation?

[katriendg]

I don't have access to an Azure subscription. Is there a way to run tf-validate locally without Azure authentication, or is it expected that CI performs this validation?

The command tf-validate does need an Azure subscription, though it will not deploy anything. Our current CI does not check this, but you may be able to run terraform validate locally without an Azure subscription, if that works, it should be good.
Would you like to be assigned this issue?

[PratikWayase]

I completed the provider upgrade and validated the updated Terraform configurations locally. Since I don't have an Azure subscription, I couldn't run npm run tf-validate, but I followed the suggested approach of running terraform init and terraform validate directly on the affected Terraform roots, and all validations passed. I'll open a PR shortly.