Merge pull request #288998 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: TimShererWithAquent

articles/security/fundamentals/customer-lockbox-overview.md

@@ -83,7 +83,7 @@ The following steps outline a typical workflow for a Customer Lockbox for Micros
     - Whether the requester is an isolated identity or using multifactor authentication.
     - Permissions levels.
     Based on the JIT rule, this request might also include an approval from Internal Microsoft Approvers. For example, the approver might be the Customer support lead or the DevOps Manager.
-1. When the request requires direct access to customer data, a Customer Lockbox request is initiated. For example, remote desktop access to a customer's virtual machine.
+1. When the request requires direct access to customer data, a Customer Lockbox request is initiated.
 
     The request is now in a **Customer Notified** state, waiting for the customer's approval before granting access.
 1. One or more approvers at the customer organization for a given Customer Lockbox request are determined as follows:
@@ -156,7 +156,7 @@ We introduced a new baseline control ([PA-8: Determine access process for cloud
 
 Customer Lockbox requests are not triggered in the following scenarios:
 
-- Emergency scenarios that fall outside of standard operating procedures and require urgent action from Microsoft to restore access to online services or to prevent corruption or loss of customer data. For instance, a major service outage or a security incident demands immediate attention to recover or restore services under unexpected or unpredictable circumstances. These "break glass" events are rare and, in most cases, do not necessitate access to customer data for resolution. The controls and processes governing Microsoft's access to customer data in core online services align with NIST 800-53 and are validated through SOC 2 audits. For further information, refer to the [Azure security baseline for Customer Lockbox for Microsoft Azure](/security/benchmark/azure/baselines/customer-lockbox-for-microsoft-azure-security-baseline).
+- Emergency scenarios that fall outside of standard operating procedures and require urgent action from Microsoft to restore access to online services or to prevent corruption or loss of customer data, or to investigate a security or abuse incident. For instance, a major service outage or a security incident demands immediate attention to recover or restore services under unexpected or unpredictable circumstances. These "break glass" events are rare and, in most cases, do not necessitate access to customer data for resolution. The controls and processes governing Microsoft's access to customer data in core online services align with NIST 800-53 and are validated through SOC 2 audits. For further information, refer to the [Azure security baseline for Customer Lockbox for Microsoft Azure](/security/benchmark/azure/baselines/customer-lockbox-for-microsoft-azure-security-baseline).
 - A Microsoft engineer accesses the Azure platform as part of troubleshooting and is inadvertently exposed to customer data. For example, the Azure Network Team performs troubleshooting that results in a packet capture on a network device. It is rare that such scenarios would result in access to meaningful quantities of customer data. Customers can further protect their data through the use of Customer-managed keys (CMK), which is available for some Azure service. For more information see [Overview of Key Management in Azure](key-management.md).
 
 External legal demands for data also do not trigger Customer Lockbox requests. For details, see the discussion of [government requests for data](https://www.microsoft.com/trust-center/) on the Microsoft Trust Center.

articles/virtual-network/create-vm-accelerated-networking-cli.md

@@ -202,9 +202,10 @@ Once you create the VM in Azure, connect to the VM and confirm that the Ethernet
    ```powershell
    PS C:\ > Get-NetAdapter | Where-Object InterfaceDescription –like "*Mellanox*Virtual*" | Get-NetAdapterStatistics
 
-   Name       ReceivedBytes ReceivedUnicastPackets SentBytes SentUnicastPackets
-   ----       ------------- ---------------------- --------- ------------------
-   Ethernet 2 492447549     347643                 7468446   34991
+   Name                             ReceivedBytes ReceivedUnicastPackets       SentBytes SentUnicastPackets
+   ----                             ------------- ----------------------       --------- ------------------
+   Ethernet 2                           492447549                 347643         7468446              34991
+
    ```
 
 > [!NOTE]