Merge pull request #294516 from tfitzmac/0211edits1

copy edit

Author: denrea

articles/azure-resource-manager/bicep/overview.md

@@ -76,13 +76,13 @@ Bicep provides the following advantages:
 
   ---
 
-- **Authoring experience**: When you use the [Bicep Extension for VS Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) to create your Bicep files, you get a first-class authoring experience. The editor provides rich type-safety, IntelliSense, and syntax validation.
+- **Authoring experience**: When you use the [Bicep Extension for VS Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) to create your Bicep files, you get a first-class authoring experience. The editor provides rich type safety, IntelliSense, and syntax validation.
 
   ![A screen capture of authoring a Bicep file in real time](./media/overview/bicep-intellisense.gif)
 
   You can also create Bicep files in Visual Studio with the [Bicep extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 
-- **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence that your resources are deployed in a consistent manner. Bicep files are idempotent, which means that you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state instead of developing many separate files to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account when the specified properties already exist, changes aren't made:
+- **Repeatable results**: Deploy your infrastructure throughout the development lifecycle with confidence that your resources are deployed consistently. Bicep files are idempotent, which means that you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state instead of developing many separate files to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account when the specified properties already exist, changes aren't made:
 
   # [Bicep](#tab/bicep)
 
@@ -127,37 +127,37 @@ Bicep provides the following advantages:
   ```
 
 ---
-  
+
 - **Orchestration**: You don't have to worry about the complexities of ordering operations. Resource Manager orchestrates the deployment of interdependent resources so that they're created in the correct order. When possible, Resource Manager deploys resources in parallel, which helps your deployments to finish faster than serial deployments. You deploy the file through one rather than multiple imperative commands.
 
    :::image type="content" source="./media/overview/bicep-processing.png" alt-text="A diagram comparing deployment between a Bicep file and infrastructure as code not in a template." border="false":::
 
-- **Modularity**: You can use [modules](./modules.md) to segment your Bicep code into manageable parts. Modules help you to reuse code and simplify development. A module deploys a set of related resources. Add a module to a Bicep file any time you need to deploy those resources.
+- **Modularity**: Use [modules](./modules.md) to segment your Bicep code into manageable parts. Modules help you to reuse code and simplify development. A module deploys a set of related resources. Add a module to a Bicep file when you need to deploy those resources.
 - **Integration with Azure services**: Bicep integrates with Azure services such as Azure Policy, template specs, and Azure Blueprints.
-- **Preview changes**: You can use the [what-if operation](./deploy-what-if.md) to preview changes before deploying the Bicep file. The what-if operation shows you which resources will be created, updated, or deleted and any resource properties that'll be changed. It also checks the current state of your environment and eliminates the need to manage this state.
-- **No state or state files to manage**: All state is stored in Azure. Users can collaborate and be confident that their updates are handled as expected.
-- **No cost and open source**: Since Bicep is completely free, you don't have to pay for premium capabilities. It's also supported by Microsoft Support.
+- **Preview changes**: You can use the [what-if operation](./deploy-what-if.md) to preview changes before deploying the Bicep file. The what-if operation shows you which resources to create, update, or delete and any resource properties to change. It also checks the current state of your environment and eliminates the need to manage this state.
+- **No state or state files to manage**: Azure stores all state. You can collaborate with others and be confident that your updates are handled as expected.
+- **No cost and open source**: Since Bicep is free, you don't have to pay for premium capabilities. Microsoft Support supports it.
 
 ## Get started
 
 To start with Bicep:
 
-1. **Install the tools**. See [Set up Bicep development and deployment environments](./install.md) or use the [VS Code devcontainer/Codespaces repository](https://github.com/Azure/vscode-remote-try-bicep) to get a pre-configured authoring environment.
+1. **Install the tools**. For more information, see [Set up Bicep development and deployment environments](./install.md) or use the [VS Code devcontainer/Codespaces repository](https://github.com/Azure/vscode-remote-try-bicep) to get a preconfigured authoring environment.
 2. **Complete the [Quickstart](./quickstart-create-bicep-use-visual-studio-code.md) and [Learn modules for Bicep](./learn-bicep.md)**.
 
 To decompile an existing Resource Manager template to Bicep, see [Decompiling ARM template JSON to Bicep](./decompile.md). You can use [Bicep Playground](https://aka.ms/bicepdemo) to view Bicep and its equivalent, JSON, side by side.
 
 To learn about the resources that are available in your Bicep file, see [Bicep resource reference](/azure/templates/).
 
-Bicep examples can be found in the [Bicep GitHub repo](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts).
+You can find Bicep examples in the [Bicep GitHub repo](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts).
 
 ## About the language
 
 Bicep isn't intended as a general programming language to write applications. A Bicep file declares Azure resources and resource properties without writing a sequence of programming commands to create them.
 
 To track the status of the Bicep work, see the [Bicep project repository](https://github.com/Azure/bicep).
 
-Watch the following video to learn about Bicep:
+To learn about Bicep, watch the following video:
 
 > [!VIDEO https://www.youtube.com/embed/sc1kJfcRQgY]
 
@@ -177,6 +177,6 @@ The structure of the Bicep file is more flexible than a JSON template. You can d
 
 ## Next steps
 
-Get started with the [Quickstart](./quickstart-create-bicep-use-visual-studio-code.md).
+To get started, see the [Quickstart](./quickstart-create-bicep-use-visual-studio-code.md).
 
 For answers to common questions, see [Frequently asked questions for Bicep](frequently-asked-questions.yml).

articles/azure-resource-manager/management/preview-features.md

@@ -2,14 +2,14 @@
 title: Set up preview features in Azure subscription
 description: Describes how to list, register, or unregister preview features in your Azure subscription for a resource provider.
 ms.topic: how-to
-ms.date: 12/12/2024
+ms.date: 02/12/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 # Customer intent: As an Azure user, I want to use preview features in my subscription so that I can expose a resource provider's preview functionality.
 ---
 
 # Set up preview features in Azure subscription
 
-This article shows you how to manage preview features in your Azure subscription. Preview features let you opt in to new functionality before it's released. Some preview features are available to anyone who wants to opt in. Other preview features require approval from the product team.
+This article shows you how to manage preview features in your Azure subscription. Preview features let you opt in to new functionality before it releases. Some preview features are available to anyone who wants to opt in. Other preview features require approval from the product team.
 
 Azure Feature Exposure Control (AFEC) is available through the [Microsoft.Features](/rest/api/resources/features) namespace. Preview features have the following format for the resource ID:
 
@@ -26,7 +26,7 @@ You can list all the preview features and their registration states for an Azure
 # [Portal](#tab/azure-portal)
 
 > [!NOTE]
-> The portal only shows a preview feature when the service that owns the feature has explicitly opted in to the preview features management experience. In case the feature you are looking for doesn't appear on the list available, we recommend using [Azure CLI](./preview-features.md?tabs=azure-cli#list-preview-features) and [Azure Powershell](./preview-features.md?tabs=azure-powershell#list-preview-features).
+> The portal only shows a preview feature when the service that owns the feature explicitly opts in to the preview features management experience. If the feature you're looking for doesn't appear on the list, we recommend using [Azure CLI](./preview-features.md?tabs=azure-cli#list-preview-features) and [Azure PowerShell](./preview-features.md?tabs=azure-powershell#list-preview-features).
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 1. In the search box, enter _subscriptions_ and select **Subscriptions**.
@@ -37,15 +37,15 @@ You can list all the preview features and their registration states for an Azure
 
     :::image type="content" source="./media/preview-features/subscriptions.png" alt-text="Screenshot of Azure portal with subscription selection highlighted.":::
 
-1. From the left menu, under **Settings** select **Preview features**.
+1. From the left menu, under **Settings**, select **Preview features**.
 
     :::image type="content" source="./media/preview-features/preview-features-menu.png" alt-text="Screenshot of Azure portal with Preview features menu option highlighted.":::
 
 1. You see a list of available preview features and your current registration status.
 
     :::image type="content" source="./media/preview-features/preview-features-list.png" alt-text="Screenshot of Azure portal displaying a list of preview features.":::
 
-1. From **Preview features** you can filter the list by **name**, **State**, or **Type**:
+1. From **Preview features**, you can filter the list by **name**, **State**, or **Type**:
 
     - **Filter by name**: Must contain text from a preview feature's name, not the **Display name**.
     - **State**: Select the drop-down menu and choose a state. The portal doesn't filter by **Unregistered**.
@@ -150,16 +150,16 @@ InGuestPatchVMPreview   Microsoft.Compute   NotRegistered
 
 ## Register preview feature
 
-Register a preview feature in your Azure subscription to expose more functionality for a resource provider. Some preview features require approval.
+To expose more functionality for a resource provider, register a preview feature in your Azure subscription. Some preview features require approval.
 
-After a preview feature is registered in your subscription, you'll see one of two states: **Registered** or **Pending**.
+After you register a preview feature in your subscription, you see one of two states: **Registered** or **Pending**.
 
 - For a preview feature that doesn't require approval, the state is **Registered**.
 - If a preview feature requires approval, the registration state is **Pending**. You must request approval from the Azure service offering the preview feature. Usually, you request access through a support ticket.
   - To request approval, submit an [Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
   - After the registration is approved, the preview feature's state changes to **Registered**.
 
-Some services require other methods, such as email, to get approval for pending request. Check announcements about the preview feature for information about how to get access.
+Some services require other methods, such as email, to get approval for pending requests. Check announcements about the preview feature for information about how to get access.
 
 # [Portal](#tab/azure-portal)
 
@@ -209,7 +209,7 @@ Microsoft.Compute/InGuestPatchVMPreview  Registered
 ```
 
 > [!NOTE]
-> When the register command runs, a message is displayed that after the feature is registered, to run `az provider register --namespace <provider-name>` to propagate the changes.
+> When you run the register command, it returns a message that suggests running `az provider register --namespace <provider-name>` after the feature is registered to propagate the changes.
 
 # [Azure PowerShell](#tab/azure-powershell)
 
@@ -241,7 +241,7 @@ InGuestPatchVMPreview   Microsoft.Compute   Registered
 
 ## Unregister preview feature
 
-When you've finished using a preview feature, unregister it from your Azure subscription. You may notice two different statuses after unregistering the feature. If you unregister through the portal, the status is set to **Not registered**. If you unregister through Azure CLI, PowerShell, or REST API, the status is set to **Unregistered**. The status is different because the portal deletes the feature registration, but the commands unregister the feature. In both cases, the feature is no longer available in your subscription. In both cases, you can opt in to the feature again by re-registering it.
+When you finish using a preview feature, unregister it from your Azure subscription. You might notice two different statuses after unregistering the feature. If you unregister through the portal, the status is **Not registered**. If you unregister through Azure CLI, PowerShell, or REST API, the status is **Unregistered**. The status is different because the portal deletes the feature registration, but the commands unregister the feature. In both cases, the feature is no longer available in your subscription. You can opt in to the feature again by re-registering it.
 
 # [Portal](#tab/azure-portal)
 
@@ -250,7 +250,7 @@ You can unregister preview features from **Preview features**. The **State** cha
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 1. In the search box, enter _subscriptions_ and select **Subscriptions**.
 1. Select the link for your subscription's name.
-1. From the left menu, under **Settings** select **Preview features**.
+1. From the left menu, under **Settings**, select **Preview features**.
 1. Select the link for the preview feature you want to unregister.
 1. Select **Unregister**.
 
@@ -291,7 +291,7 @@ Microsoft.Compute/InGuestPatchVMPreview  Unregistered
 ```
 
 > [!NOTE]
-> When the unregister command runs, a message is displayed that after the feature is unregistered, to run `az provider register --namespace <provider-name>` to propagate the changes.
+> When you run the unregister command, it returns a message that suggests running `az provider register --namespace <provider-name>` after the feature is registered to propagate the changes.
 
 To find **Unregistered** preview features, use the following command. Replace `<ResourceProvider.Name>` with a provider name such as `Microsoft.Compute`.
 
@@ -349,7 +349,7 @@ InGuestPatchVMPreview   Microsoft.Compute   Unregistered
 
 ## Configuring preview features using Azure Policy
 
-Subscriptions can be remediated to register to a preview feature if not already registered using a [built-in](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fe624c84f-2923-4437-9fd9-4115c6da3888) policy definition. Note that new subscriptions added to an existing tenant won't be automatically registered.
+You can remediate subscriptions to register to a preview feature if they're not already registered using a [built-in](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fe624c84f-2923-4437-9fd9-4115c6da3888) policy definition. When you add new subscriptions to an existing tenant, they aren't automatically registered.
 
 ## Next steps
 

articles/azure-resource-manager/management/resource-manager-personal-data.md

@@ -3,18 +3,18 @@ title: Personal data
 description: Learn how to manage personal data associated with Azure Resource Manager operations.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 09/26/2024
+ms.date: 02/12/2025
 ---
 
 # Manage personal data associated with Azure Resource Manager
 
-To avoid exposing sensitive information, delete any personal information you may have provided in deployments, resource groups, or tags. Azure Resource Manager provides operations that let you manage personal data you may have provided in deployments, resource groups, or tags.
+To avoid exposing sensitive information, delete any personal information you provided in deployments, resource groups, or tags. Azure Resource Manager provides operations that let you manage personal data you provided in deployments, resource groups, or tags.
 
 [!INCLUDE [Handle personal data](~/reusable-content/ce-skilling/azure/includes/gdpr-intro-sentence.md)]
 
 ## Delete personal data in deployment history
 
-For deployments, Resource Manager retains parameter values and status messages in the deployment history. These values persist until you delete the deployment from the history. To see if you have provided personal data in these values, list the deployments. If you find personal data, delete the deployments from the history.
+For deployments, Resource Manager retains parameter values and status messages in the deployment history. These values persist until you delete the deployment from the history. To see if you provided personal data in these values, list the deployments. If you find personal data, delete the deployments from the history.
 
 To list **deployments** in the history, use:
 
@@ -30,7 +30,7 @@ To delete **deployments** from the history, use:
 
 ## Delete personal data in resource group names
 
-The name of the resource group persists until you delete the resource group. To see if you have provided personal data in the names, list the resource groups. If you find personal data, [move the resources](move-resource-group-and-subscription.md) to a new resource group, and delete the resource group with personal data in the name.
+The name of the resource group persists until you delete the resource group. To see if you provided personal data in the names, list the resource groups. If you find personal data, [move the resources](move-resource-group-and-subscription.md) to a new resource group, and delete the resource group with personal data in the name.
 
 To list **resource groups**, use:
 
@@ -46,7 +46,7 @@ To delete **resource groups**, use:
 
 ## Delete personal data in tags
 
-Tags names and values persist until you delete or modify the tag. To see if you have provided personal data in the tags, list the tags. If you find personal data, delete the tags.
+Tag names and values persist until you delete or modify the tag. To see if you provided personal data in the tags, list the tags. If you find personal data, delete the tags.
 
 To list **tags**, use: