minor changes

Author: AbhishekMallick01

articles/backup/backup-azure-files-policy-automation.md

@@ -20,13 +20,13 @@ The following table lists the various policy types that allows you to manage Azu
 
 | Policy type | Description |
 | --- | --- |
-| [Policy 1](#policy-1-back-up-untagged-files-in-an-existing-vault-from-the-same-region) | Configures backup for Azure Files without a given tag to an existing Recovery Services vault in the same location. |
-| [Policy 2](#policy-2-back-up-tagged-files-in-an-existing-vault-from-the-same-region) | Configures backup for Azure Files with a given tag to an existing Recovery Services vault in the same location. |
-| [Policy 3](#policy-3-back-up-untagged-azure-files-in-a-new-recovery-services-vault-using-a-new-policy) | Configures backup for Azure Files without a given tag to a new Recovery Services vault with a new policy. |
-| [Policy 4](#policy-4--back-up-tagged-azure-files-in-a-new-recovery-services-vault-using-a-new-policy) | Configures backup for Azure Files with a given tag to a new Recovery Services vault with a new policy. |
-| [Policy 5](#policy-5-audit-azure-files-backup-configuration-with-azure-backup) | Validates if Azure Backup is enabled on Azure Files. |
+| [Policy 1](#policy-1-configure-backup-for-azure-files-shares-without-a-given-tag-to-an-existing-recovery-services-vault-in-the-same-location) | Configures backup for Azure Files without a given tag to an existing Recovery Services vault in the same location. |
+| [Policy 2](#policy-2-configure-backup-for-azure-files-shares-with-a-given-tag-to-an-existing-recovery-services-vault-in-the-same-location) | Configures backup for Azure Files with a given tag to an existing Recovery Services vault in the same location. |
+| [Policy 3](#policy-3-configure-backup-for-azure-files-shares-without-a-given-tag-to-a-new-recovery-services-vault-with-a-new-policy) | Configures backup for Azure Files without a given tag to a new Recovery Services vault with a new policy. |
+| [Policy 4](#policy-4--configure-backup-for-azure-files-shares-with-a-given-tag-to-a-new-recovery-services-vault-with-a-new-policy) | Configures backup for Azure Files with a given tag to a new Recovery Services vault with a new policy. |
+| [Policy 5](#policy-5-azure-backup-should-be-enabled-on-azure-file-shares) | Validates if Azure Backup is enabled on Azure Files. |
 
-### Policy 1: Back up Untagged Files in an existing vault from the same region
+### Policy 1: Configure backup for Azure Files Shares without a given tag to an existing recovery services vault in the same location
 
 This policy enforces backup for all Azure Files by configuring them to use an existing central Recovery Services vault in the same location and subscription as the storage account. It suits scenarios where a central team manages backups across all resources in a subscription. You can exclude Azure Files in storage accounts with a specific tag to refine the policy scope.
 
@@ -38,9 +38,9 @@ The evaluation workflow operates as per the following conditions:
 
 - **Storage account isn't registered with a Recovery Services vault**: The storage account is registered with the specified Recovery Services vault, and all File Shares within the storage account is backed up automatically.
 
-### Policy 2: Back up tagged Files in an existing vault from the same region
+### Policy 2: Configure backup for Azure Files Shares with a given tag to an existing recovery services vault in the same location
 
-This policy enforces backup for all Azure Files by directing them to a specified Recovery Services vault in the same region and subscription as the storage account. It suits organizations with a central team managing backups. You can limit the policy scope to storage accounts with specific tags by setting the required *`TagName`* and *`TagValue`*.
+This policy enforces backup for all Azure Files by directing them to a specified Recovery Services vault in the same location and subscription as the storage account. It suits organizations with a central team managing backups. You can limit the policy scope to storage accounts with specific tags by setting the required *`TagName`* and *`TagValue`*.
 
 The policy checks storage accounts based on the provided tags and applies backup settings. If it finds an unprotected file share in an eligible account, it applies the following logic and shows the results in the Azure portal:
 
@@ -51,29 +51,29 @@ The policy checks storage accounts based on the provided tags and applies backup
 >[!Note]
 >Storage accounts with the specified inclusion tags appear during evaluation and on compliance reports.
 
-### Policy 3: Back up untagged Azure Files in a new Recovery Services vault using a new policy
+### Policy 3: Configure backup for Azure Files Shares without a given tag to a new recovery services vault with a new policy
 
-This policy enforces backup for all Azure Files by deploying a Recovery Services vault in the same region and resource group as the storage account. It suits organizations where application teams manage backups within their own resource groups. You can exclude storage accounts with specific tags (*`TagName`* and *`TagValue`*) to refine the policy scope. The policy checks each storage account based on the defined parameters, skips those storage accounts with exclusion tags, and omits them from compliance reports.
+This policy enforces backup for all Azure Files by deploying a Recovery Services vault in the same location and resource group as the storage account. It suits organizations where application teams manage backups within their own resource groups. You can exclude storage accounts with specific tags (*`TagName`* and *`TagValue`*) to refine the policy scope. The policy checks each storage account based on the defined parameters, skips those storage accounts with exclusion tags, and omits them from compliance reports.
 
 The evaluation workflow operates as per the following conditions:
 
-- **Storage account is already registered with a Recovery Services vault**: If all File Shares are already backed up, the policy takes no action. When a File Share doesn't have backups configured and the storage account matches the Recovery Services vault specified in the policy, the backup operation is triggered through a one-time remediation task. This task runs only once; future file shares in the same account are backed up automatically.
+- **Storage account is already registered with a Recovery Services vault**: If all File Shares are already backed up, the policy takes no action. If a File Share doesn't have backups configured and it's in the  storage account same as the Recovery Services vault specified in the policy, the backup starts after running a one-time remediation task. This task runs only once; future file shares in the same account are backed up automatically.
 
-- **Storage account isn't registered with any Recovery Services vault**: The policy creates a new Recovery Services vault in the same resource group and region as the storage account. It then registers the storage account with this vault, and all file shares within the account are automatically backed up.
+- **Storage account isn't registered with any Recovery Services vault**: The policy creates a new Recovery Services vault in the same resource group and location as the storage account. It then registers the storage account with this vault, and all file shares within the account are automatically backed up.
 
-### Policy 4- Back up tagged Azure Files in a new Recovery Services vault using a new policy
+### Policy 4- Configure backup for Azure Files Shares with a given tag to a new recovery services vault with a new policy
 
-This policy enforces backup for all Azure Files by creating a Recovery Services vault in the same region and resource group as the storage account. It suits organizations where application teams manage their own backup and restore operations within dedicated resource groups. You can limit the policy scope to storage accounts with specific tags (*`TagName`* and *`TagValue`*) for precise control.
+This policy enforces backup for all Azure Files by creating a Recovery Services vault in the same location and resource group as the storage account. It suits organizations where application teams manage their own backup and restore operations within dedicated resource groups. You can limit the policy scope to storage accounts with specific tags (*`TagName`* and *`TagValue`*) for precise control.
 
 The policy checks each storage account based on the defined parameters. It includes accounts that match the specified tags and reflects their compliance status in the Azure portal.
 
 The evaluation workflow operates as per the following conditions:
 
-- **Storage account is already registered with a Recovery Services vault**: If all file shares are already backed up, the policy takes no action. If any file share doesn't have backup configured, and the storage account matches the Recovery Services vault specified in the policy, the backup starts after running a one-time remediation task. After this task completes, future File Shares in the same account are backed up automatically.
+- **Storage account is already registered with a Recovery Services vault**: If all file shares are already backed up, the policy takes no action. If any file share doesn't have backup configured, and it's in the storage account same as the Recovery Services vault specified in the policy, the backup starts after running a one-time remediation task. After this task completes, future File Shares in the same account are backed up automatically.
 
-- **Storage account isn't registered with any Recovery Services vault**: The policy creates a new Recovery Services vault in the same region and resource group as the storage account, registers the storage account with this vault, and automatically backs up all File Shares within it.
+- **Storage account isn't registered with any Recovery Services vault**: The policy creates a new Recovery Services vault in the same location and resource group as the storage account, registers the storage account with this vault, and automatically backs up all File Shares within it.
 
-### Policy 5: Audit Azure Files backup configuration with Azure Backup
+### Policy 5: Azure Backup should be enabled on Azure file shares
 
 This policy validates if the protection of your Azure Files is configured with Azure Backup—a secure and cost-effective solution for safeguarding Azure workloads. It generates a report that lists both compliant and noncompliant resources.
 
@@ -83,7 +83,7 @@ The following table lists the supported and unsupported scenarios for the availa
 
 | Policy types | Supported | Unsupported |
 | --- | --- | --- |
-| **Policies 1 and 2** |  Can be assigned to a single region and subscription at a time. To enable backup for Files across regions and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of region and subscription. <br><br> - The specified vault and the Azure Files configured for backup can be under different resource groups. | Management group scope is currently unsupported. |
+| **Policies 1 and 2** |  Can be assigned to a single location and subscription at a time. To enable backup for Files across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription. <br><br> - The specified vault and the Azure Files configured for backup can be under different resource groups. | Management group scope is currently unsupported. |
 | **Policies 3 and 4** | Can be assigned to a single subscription at a time (or a resource group within a subscription). |           |
 
 ## Assign built-in policy for Azure Files backup