From 4f43d501ceb8bebb2c1d282e6014d36c550a040a Mon Sep 17 00:00:00 2001 From: Rebecca Calixte Date: Thu, 6 Aug 2026 11:27:03 -0400 Subject: [PATCH 1/2] Update AzureRM feature comparison values --- articles/terraform/provider-selection-azurerm-vs-azapi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/terraform/provider-selection-azurerm-vs-azapi.md b/articles/terraform/provider-selection-azurerm-vs-azapi.md index 6c6220c835..6d2e0aec06 100644 --- a/articles/terraform/provider-selection-azurerm-vs-azapi.md +++ b/articles/terraform/provider-selection-azurerm-vs-azapi.md @@ -98,9 +98,9 @@ Most teams should start with an AzureRM-primary strategy and adopt AzAPI as need | Built-in property validation | Yes | Partial (via preflight) | | IDE autocomplete for properties | Yes | Yes (with VS Code extension) | | Response export / JMESPath filtering | No | Yes | -| Data plane resource management | No | Yes (selected resource types) | +| Data plane resource management | Yes (selected resource types) | Yes (selected resource types) | | Provider functions for ID construction | No | Yes (v2.0 and later) | -| Preflight validation at plan time | No | Yes—[Enable preflight validation](how-to-use-azapi-preflight-validation.md) | +| Preflight validation at plan time | Yes | Yes—[Enable preflight validation](how-to-use-azapi-preflight-validation.md) | ## Next steps From a5fd1ceb4e89aabb570d01f008f5ea2575686ecc Mon Sep 17 00:00:00 2001 From: Rebecca Calixte Date: Thu, 6 Aug 2026 21:34:31 -0400 Subject: [PATCH 2/2] Update data plane management and validation details --- articles/terraform/provider-selection-azurerm-vs-azapi.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/terraform/provider-selection-azurerm-vs-azapi.md b/articles/terraform/provider-selection-azurerm-vs-azapi.md index 6d2e0aec06..9bba216d9e 100644 --- a/articles/terraform/provider-selection-azurerm-vs-azapi.md +++ b/articles/terraform/provider-selection-azurerm-vs-azapi.md @@ -98,9 +98,9 @@ Most teams should start with an AzureRM-primary strategy and adopt AzAPI as need | Built-in property validation | Yes | Partial (via preflight) | | IDE autocomplete for properties | Yes | Yes (with VS Code extension) | | Response export / JMESPath filtering | No | Yes | -| Data plane resource management | Yes (selected resource types) | Yes (selected resource types) | +| Data plane resource management | Yes | Yes (selected resource types) | | Provider functions for ID construction | No | Yes (v2.0 and later) | -| Preflight validation at plan time | Yes | Yes—[Enable preflight validation](how-to-use-azapi-preflight-validation.md) | +| Preflight validation at plan time | Yes (selected resource types) | Yes—[Enable preflight validation](how-to-use-azapi-preflight-validation.md) | ## Next steps