acrolinx pass

Author: TomArcherMsft

articles/governance/policy/assign-policy-terraform.md

@@ -1,6 +1,6 @@
 ---
 title: 'Quickstart: New policy assignment with Terraform'
-description: In this quickstart, you use Terraform and Hashicorp Configuration Language (HCL) syntax to create a policy assignment to identify non-compliant resources.
+description: In this quickstart, you use Terraform and Hashicorp Configuration Language (HCL) syntax to create a policy assignment to identify noncompliant resources.
 ms.date: 03/26/2025
 ms.topic: quickstart
 ms.custom: devx-track-terraform
@@ -10,10 +10,10 @@ content_well_notification:
   - AI-contribution
 ---
 
-# Quickstart: Create a policy assignment to identify non-compliant resources using Terraform
+# Quickstart: Create a policy assignment to identify noncompliant resources using Terraform
 
 The first step in understanding compliance in Azure is to identify the status of your resources. This quickstart steps you through the process of creating a policy assignment to identify virtual
-machines that aren't using managed disks. At the end of this process, you identify virtual machines that aren't using managed disks across subscription. They're _non-compliant_ with the policy assignment.
+machines that are not using managed disks.
 
 [!INCLUDE [azure-policy-version-default](../includes/policy/policy-version-default.md)]
 
@@ -50,13 +50,6 @@ The sample code for this article is located in the [Azure Terraform GitHub repo]
 1. Create a file named `outputs.tf` and insert the following code.
     :::code language="Terraform" source="~/terraform_samples/quickstart/101-azure-policy/outputs.tf":::
 
-> [!IMPORTANT]
-> If you are using the 4.x azurerm provider, you must [explicitly specify the Azure subscription ID](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#specifying-subscription-id-is-now-mandatory) to authenticate to Azure before running the Terraform commands.
->
-> One way to specify the Azure subscription ID without putting it in the `providers` block is to specify the subscription ID in an environment variable named `ARM_SUBSCRIPTION_ID`.
->
-> For more information, see the [Azure provider reference documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#argument-reference).
-
 ## Specify scope
 
 A scope determines what resources or grouping of resources the policy assignment gets enforced on. It could range from a management group to an individual resource. To use any of the following scopes, update the `scope` variable in the `variables.tf` file. If you leave the `scope` variable value blank, the "subscription" scope is used.
@@ -94,7 +87,7 @@ A scope determines what resources or grouping of resources the policy assignment
     armclient post "/subscriptions/<subscription_id>/providers/Microsoft.PolicyInsights/policyStates/latest/queryResults?api-version=2019-10-01&$filter=IsCompliant eq false and PolicyAssignmentId eq '<policyAssignmentID>'&$apply=groupby((ResourceId))" > <json file to direct the output with the resource IDs into>
     ```
     
-1. The results are comparable to what you see listed under **Non-compliant resources** in the Azure portal view.
+1. The results are comparable to what you see listed under **Noncompliant resources** in the Azure portal view.
 
 ## Clean up resources
 

articles/storage-actions/storage-tasks/storage-task-quickstart-terraform.md

@@ -7,7 +7,7 @@ ms.service: azure-storage-actions
 ms.custom: devx-track-terraform;build-2023-metadata-update
 ms.topic: quickstart
 ms.author: normesta
-ms.date: 03/25/2025
+ms.date: 03/26/2025
 #customer intent: As a Terraform user, I want to see how to create a storage task using Terraform.
 content_well_notification: 
   - AI-contribution
@@ -17,7 +17,7 @@ content_well_notification:
 
 A storage task can perform operations on blobs in an Azure Storage account. As you create a task, you can define the conditions that must be met by each object (container or blob), and the operations to perform on the object. You can also identify one or more Azure Storage account targets. See [What are Azure Storage Actions?](../overview.md).
 
-In this how-to article, you'll learn how to create a storage task using Terraform.
+In this how-to article, you learn how to create a storage task using Terraform.
 
 > [!IMPORTANT]
 > Azure Storage Actions is currently in PREVIEW and is available in these [regions](../overview.md#supported-regions).
@@ -61,15 +61,15 @@ The sample code for this article is located in the [Azure Terraform GitHub repo]
 1. Create a file named `outputs.tf` and insert the following code.
     :::code language="Terraform" source="~/terraform_samples/quickstart/101-azure-storage-actions-create-storage-task/outputs.tf":::
 
+## Initialize Terraform
+
 > [!IMPORTANT]
 > If you are using the 4.x azurerm provider, you must [explicitly specify the Azure subscription ID](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#specifying-subscription-id-is-now-mandatory) to authenticate to Azure before running the Terraform commands.
 >
 > One way to specify the Azure subscription ID without putting it in the `providers` block is to specify the subscription ID in an environment variable named `ARM_SUBSCRIPTION_ID`.
 >
 > For more information, see the [Azure provider reference documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#argument-reference).
 
-## Initialize Terraform
-
 [!INCLUDE [terraform-init.md](~/azure-dev-docs-pr/articles/terraform/includes/terraform-init.md)]
 
 ## Create a Terraform execution plan