Merge pull request #302136 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/automation/automation-runbook-types.md

@@ -67,6 +67,7 @@ The following are the current limitations and known issues with PowerShell runbo
 > [!NOTE]
 > Currently, PowerShell 7.4 runtime version is supported for both Cloud and Hybrid jobs in all Public regions except Brazil Southeast and Gov clouds.
 
+- Powershell 7.4 is only available in [runtime environment experience](runtime-environment-overview.md).
 - For the PowerShell 7.4 runtime version, the module activities aren't extracted for the imported modules. Use [Azure Automation extension for VS Code](automation-runbook-authoring.md) to simplify runbook authoring experience.
 - PowerShell 7.x doesn't support workflows. For more information, see [PowerShell workflow](/powershell/scripting/whats-new/differences-from-windows-powershell#powershell-workflow) for more details.
 - PowerShell 7.x currently doesn't support signed runbooks.

articles/azure-government/azure-secure-isolation-guidance.md

@@ -174,7 +174,7 @@ When you create a key vault in a resource group, you can [manage access](/azure/
 #### Managed HSM
 **[Managed HSM](/azure/key-vault/managed-hsm/overview)** provides a single-tenant, fully managed, highly available, zone-resilient (where available) HSM as a service to store and manage your cryptographic keys. It's most suitable for applications and usage scenarios that handle high value keys. It also helps you meet the most stringent security, compliance, and regulatory requirements. Managed HSM uses [FIPS 140 Level 3 validated HSMs](/azure/compliance/offerings/offering-fips-140-2) to protect your cryptographic keys. Each managed HSM pool is an isolated single-tenant instance with its own [security domain](/azure/key-vault/managed-hsm/security-domain) controlled by you and isolated cryptographically from instances belonging to other customers. Cryptographic isolation relies on [Intel Software Guard Extensions](https://software.intel.com/sgx) (SGX) technology that provides encrypted code and data to help ensure your control over cryptographic keys.
 
-When a managed HSM is created, the requestor also provides a list of data plane administrators. Only these administrators are able to [access the managed HSM data plane](/azure/key-vault/managed-hsm/access-control) to perform key operations and manage data plane role assignments (managed HSM local RBAC). The permission model for both the management and data planes uses the same syntax, but permissions are enforced at different levels, and role assignments use different scopes. Management plane Azure RBAC is enforced by Azure Resource Manager while data plane-managed HSM local RBAC is enforced by the managed HSM itself.
+When a managed HSM is created, the requester also provides a list of data plane administrators. Only these administrators are able to [access the managed HSM data plane](/azure/key-vault/managed-hsm/access-control) to perform key operations and manage data plane role assignments (managed HSM local RBAC). The permission model for both the management and data planes uses the same syntax, but permissions are enforced at different levels, and role assignments use different scopes. Management plane Azure RBAC is enforced by Azure Resource Manager while data plane-managed HSM local RBAC is enforced by the managed HSM itself.
 
 > [!IMPORTANT]
 > Unlike with key vaults, granting your users management plane access to a managed HSM doesn't grant them any access to data plane to access keys or data plane role assignments managed HSM local RBAC. This isolation is implemented by design to prevent inadvertent expansion of privileges affecting access to keys stored in managed HSMs.

articles/confidential-computing/confidential-nodes-aks-addon.md

@@ -55,9 +55,9 @@ You don't have to check for backward compatibility with PSW and DCAP. The provid
 
 ### Out-of-proc attestation for confidential workloads
 
-The out-of-proc attestation model works for confidential workloads. The quote requestor and quote generation are executed separately, but on the same physical machine. The quote generation happens in a centralized manner and serves requests for QUOTES from all entities. Properly define the interface and make the interface discoverable for any entity to request quotes.
+The out-of-proc attestation model works for confidential workloads. The quote requester and quote generation are executed separately, but on the same physical machine. The quote generation happens in a centralized manner and serves requests for QUOTES from all entities. Properly define the interface and make the interface discoverable for any entity to request quotes.
 
-![Diagram of quote requestor and quote generation interface.](./media/confidential-nodes-out-of-proc-attestation/aesmmanager.png)
+![Diagram of quote requester and quote generation interface.](./media/confidential-nodes-out-of-proc-attestation/aesmmanager.png)
 
 The abstract model applies to confidential workload scenarios. This model uses the already available AESM service. AESM is containerized and deployed as a daemon set across the Kubernetes cluster. Kubernetes guarantees a single instance of an AESM service container, wrapped in a pod, to be deployed on each agent node. The new SGX Quote daemon set has a dependency on the `sgx-device-plugin` daemon set, since the AESM service container would request EPC memory from `sgx-device-plugin` for launching QE and PCE enclaves.
 

articles/cost-management-billing/manage/mca-request-billing-ownership.md

@@ -57,9 +57,9 @@ You can also go along with the following video that outlines each step of the pr
 
 >[!VIDEO https://www.youtube.com/embed/gfiUI2YLsgc]
 
-### Required permission for the transfer requestor
+### Required permission for the transfer requester
 
-The product transfer requestor must have one of the following permissions:
+The product transfer requester must have one of the following permissions:
 
 For a Microsoft Customer Agreement, the person must have an owner or contributor role for the billing account or for the relevant billing profile or invoice section. For more information, see [Billing roles and tasks](understand-mca-roles.md#invoice-section-roles-and-tasks).
 

articles/cost-management-billing/manage/mpa-request-ownership.md

@@ -52,7 +52,7 @@ When there's a currency change during or after an EA enrollment transfer, reserv
 
 Before you begin, make sure that the people involved in the product transfer have the required permissions. 
 
-### Required permission for the transfer requestor
+### Required permission for the transfer requester
 
 To request the billing ownership, you must have the **Admin Agent** or [billing admin](/partner-center/account-settings/permissions-overview#billing-admin-role) role. To learn more, see [Partner Center - Assign users roles and permissions](/partner-center/permissions-overview).
 

articles/databox/data-box-disk-deploy-picked-up.md

@@ -193,9 +193,9 @@ If needed, you can contact Quantium Solution Support (Japanese language) at the
     To:  [email protected]
     Subject: Microsoft Azure Pickup - XZ00001234567
     Body:
-     a.    Requestor name
-     b.    Requestor contact number
-     c.    Requestor collection address
+     a.    Requester name
+     b.    Requester contact number
+     c.    Requester collection address
      d.    Preferred collection date
     ```
 

articles/iot-operations/create-edge-apps/concept-about-state-store-protocol.md

@@ -125,7 +125,7 @@ The following example output shows state store RESP3 payloads:
 
 ### Response format
 
-When the state store detects an invalid RESP3 payload, it still returns a response to the requestor's `Response Topic`. Examples of invalid payloads include an invalid command, an illegal RESP3, or integer overflow. An invalid payload starts with the string `-ERR` and contains more details.
+When the state store detects an invalid RESP3 payload, it still returns a response to the requester's `Response Topic`. Examples of invalid payloads include an invalid command, an illegal RESP3, or integer overflow. An invalid payload starts with the string `-ERR` and contains more details.
 
 > [!NOTE]
 > A `GET`, `DEL`, or `VDEL` request on a nonexistent key is not considered an error.

articles/site-recovery/hyper-v-azure-troubleshoot.md

@@ -139,7 +139,7 @@ An app-consistent snapshot is a point-in-time snapshot of the application data i
 2. To generate VSS snapshots for the VM, check that Hyper-V Integration Services is installed on the VM, and that the Backup (VSS) Integration Service is enabled.
     - Ensure that the Integration Services VSS service/daemons are running on the guest, and are in an **OK** state.
     - You can check this from an elevated PowerShell session on the Hyper-V host with command **Get-VMIntegrationService -VMName\<VMName>-Name VSS** You can also get this information by logging into the guest VM. [Learn more](/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services).
-    - Ensure that the Backup/VSS integration Services on the VM is running and in healthy state. If not, restart these services, and the Hyper-V Volume Shadow Copy requestor service on the Hyper-V host server.
+    - Ensure that the Backup/VSS integration Services on the VM is running and in healthy state. If not, restart these services, and the Hyper-V Volume Shadow Copy requester service on the Hyper-V host server.
 
 ### Common errors
 

articles/traffic-manager/traffic-manager-load-balancing-azure.md

@@ -23,7 +23,7 @@ In this tutorial, we first define a customer use case and see how it can be made
 At a conceptual level, each of these services plays a distinct role in the load-balancing hierarchy.
 
 * **Traffic Manager** provides global DNS load balancing. It looks at incoming DNS requests and responds with a healthy endpoint, in accordance with the routing policy the customer has selected. Options for routing methods are:
-  * Performance routing to send the requestor to the closest endpoint in terms of latency.
+  * Performance routing to send the requester to the closest endpoint in terms of latency.
   * Priority routing to direct all traffic to an endpoint, with other endpoints as backup.
   * Weighted round-robin routing, which distributes traffic based on the weighting that is assigned to each endpoint.
   * Geography-based routing to distribute the traffic to your application endpoints based on geographic location of the user.

articles/virtual-wan/how-to-network-virtual-appliance-inbound.md

@@ -141,7 +141,7 @@ The following section describes some common troubleshooting scenarios.
 
 ### <a name="healthprobeconfigs"></a> Load balancer health probes
 
-NVA with internet inbound/DNAT capabilities relies on the NVA responding to three different Azure Load Balancer health probes to ensure the NVA is functioning as expected and route traffic. Health probe requests are always made from the nonpublically routable Azure IP Address [168.63.129.16](../virtual-network/what-is-ip-address-168-63-129-16.md). You should see a three-way TCP handshake performed with 168.63.129.16 in your NVA logs.
+NVA with internet inbound/DNAT capabilities relies on the NVA responding to three different Azure Load Balancer health probes to ensure the NVA is functioning as expected and route traffic. Health probe requests are always made from the nonpublicly routable Azure IP Address [168.63.129.16](../virtual-network/what-is-ip-address-168-63-129-16.md). You should see a three-way TCP handshake performed with 168.63.129.16 in your NVA logs.
 
 For more information on Azure Load Balancer health probes, see [health probe documentation](../load-balancer/load-balancer-custom-probe-overview.md).