Merge pull request #280479 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/governance/policy/concepts/definition-structure-basics.md

@@ -130,10 +130,7 @@ When Azure Policy versioning is released, the following Resource Provider modes
 ## Version (preview)
 Built-in policy definitions can host multiple versions with the same `definitionID`. If no version number is specified, all experiences will show the latest version of the definition. To see a specific version of a built-in, it must be specified in API, SDK or UI. To reference a specific version of a definition within an assignment, see [definition version within assignment](../concepts/assignment-structure.md#policy-definition-id-and-version-preview) 
 
-The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey level of
-> change to a built-in policy definition or initiative and state. The format of `version` is:
-> `{Major}.{Minor}.{Patch}`. Specific states, such as _deprecated_ or _preview_, are appended to the
-> `version` property or in another property as a **boolean**.
+The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey level of change to a built-in policy definition or initiative and state. The format of `version` is: `{Major}.{Minor}.{Patch}`. Specific states, such as _deprecated_ or _preview_, are appended to the `version` property or in another property as a **boolean**.
 
 - Major Version (example: 2.0.0): introduce breaking changes such as major rule logic changes, removing parameters, adding an enforcement effect by default.
 - Minor Version (example: 2.1.0): introduce changes such as minor rule logic changes, adding new parameter allowed values, change to `roleDefinitionIds`, adding or moving definitions within an initiative.

articles/operator-insights/operator-insights-faq.yml

@@ -20,7 +20,7 @@ sections:
           Azure Operator Insights doesn't move or store customer data out of the region it's deployed in.
           
           The only exceptions to this are:
-          - Data processing for the Azure Operator Insights Copilot feature (currently in preview). This is because the Azure Open AI service used by the Copilot feature is not available in all regions yet. Data processing may happen cross region but within the same geo.
+          - Data processing for the Azure Operator Insights Copilot feature (currently in preview). This is because Azure OpenAI Service used by the Copilot feature is not available in all regions yet. Data processing may happen cross region but within the same geo.
           - Data storage for the West Central US or South Central US regions. If you deploy to these regions, the data is stored in the East US region.
       - question: Does Azure Operator Insights support CMK-based encryption?
         answer: |

articles/site-recovery/azure-to-azure-powershell.md

@@ -251,7 +251,7 @@ When enabling zone to zone replication, only one fabric will be created. But the
 
 ```azurepowershell
 $primaryProtectionContainer = Get-AzRecoveryServicesAsrProtectionContainer -Fabric $fabric -Name "asr-a2a-default-westeurope-container"
-$recoveryPprotectionContainer = Get-AzRecoveryServicesAsrProtectionContainer -Fabric $fabric -Name "asr-a2a-default-westeurope-t-container"
+$recoveryProtectionContainer = Get-AzRecoveryServicesAsrProtectionContainer -Fabric $fabric -Name "asr-a2a-default-westeurope-t-container"
 ```
 
 ### Create a replication policy
@@ -641,4 +641,4 @@ Remove-AzRecoveryServicesAsrReplicationProtectedItem -ReplicationProtectedItem $
 
 ## Next steps
 
-View the [Azure Site Recovery PowerShell reference](/powershell/module/az.RecoveryServices) to learn how you can do other tasks such as creating recovery plans and testing failover of recovery plans with PowerShell.
+View the [Azure Site Recovery PowerShell reference](/powershell/module/az.RecoveryServices) to learn how you can do other tasks such as creating recovery plans and testing failover of recovery plans with PowerShell.