Merge pull request #301573 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/azure-netapp-files/network-attached-storage-protocols.md

@@ -119,7 +119,7 @@ Some organizations have pure Windows or pure UNIX environments (homogeneous) in
 * SMB and [NTFS](/windows-server/storage/file-server/ntfs-overview) file security
 * NFS and UNIX file security - mode bits or [NFSv4.x access control lists (ACLs)](https://wiki.linux-nfs.org/wiki/index.php/ACLs)
 
-However, many sites must enable data sets to be accessed from both Windows and UNIX clients (heterogenous). For environments with these requirements, Azure NetApp Files has native dual-protocol NAS support. After the user is authenticated on the network and has both appropriate share or export permissions and the necessary file-level permissions, the user can access the data from UNIX hosts using NFS or from Windows hosts using SMB.
+However, many sites must enable data sets to be accessed from both Windows and UNIX clients (heterogeneous). For environments with these requirements, Azure NetApp Files has native dual-protocol NAS support. After the user is authenticated on the network and has both appropriate share or export permissions and the necessary file-level permissions, the user can access the data from UNIX hosts using NFS or from Windows hosts using SMB.
 
 ### Reasons for using dual-protocol volumes
 

articles/azure-netapp-files/performance-virtual-machine-sku.md

@@ -25,7 +25,7 @@ Storage performance involves more than the speed of the storage itself. The proc
 For the most consistent performance when selecting virtual machines, select from SKUs with a single type of chipset – newer SKUs are preferred over the older models where available. Keep in mind that, aside from using a dedicated host, predicting correctly which type of hardware the E_v3 or D_v3 virtual machines land on is unlikely. When using the E_v3 or D_v3 SKU:
 
 * When a virtual machine is turned off, deallocated, and then turned on again, the virtual machine is likely to change hosts and as such hardware models.
-* When applications are deployed across multiple virtual machines, expect the virtual machines to run on heterogenous hardware.
+* When applications are deployed across multiple virtual machines, expect the virtual machines to run on heterogeneous hardware.
 
 ## Differences within and between SKUs
 

articles/backup/backup-support-matrix.md

@@ -35,7 +35,7 @@ The following table describes the features of Recovery Services vaults:
 **Machines in a vault** | Up to 2000 datasources across all workloads (like Azure VMs, SQL Server VM, MABS Servers, and so on) can be protected in a single vault.<br><br>Up to 1,000 Azure VMs in a single vault.<br/><br/> Up to 50 MABS servers can be registered in a single vault.
 **Data sources** | Maximum size of an individual [data source](./backup-azure-backup-faq.yml#how-is-the-data-source-size-determined-) is 54,400 GB. This limit doesn't apply to Azure VM backups. No limits apply to the total amount of data you can back up to the vault.
 **Backups to vault** | **Azure VMs:** Once a day.<br/><br/>**Machines protected by DPM/MABS:** Twice a day.<br/><br/> **Machines backed up directly by using the MARS agent:** Three times a day.
-**Backups between vaults** | Backup is within a region.<br/><br/> You need a vault in every Azure region that contains VMs you want to back up. You can't back up to a different region.
+**Backups between vaults** | Backup is within a region and subscription.<br/><br/> You need a vault in every Azure region and subscription that contains VMs you want to back up. You can't back up to a different region. Cross subscription backup (RS vault and protected VMs are in different subscriptions) isn't a supported scenario.
 **Move vaults** | You can [move vaults](./backup-azure-move-recovery-services-vault.md) across subscriptions or between resource groups in the same subscription. However, moving vaults across regions isn't supported.
 **Move data between vaults** | Moving backed-up data between vaults isn't supported.
 **Modify vault storage type** | You can modify the storage replication type (either geo-redundant storage or locally redundant storage) for a vault before backups are stored. After backups begin in the vault, the replication type can't be modified.

articles/backup/install-mars-agent.md

@@ -64,11 +64,11 @@ To modify the storage replication type, follow these steps:
 > You can't modify the storage replication type after the vault is set up and contains backup items. If you want to do this, you need to re-create the vault.
 >
 
-## Configure Recovery Services vault to save passphrase to Recovery Services vault
+## Configure Recovery Services vault to save passphrase to Azure Key Vault
 
-Azure Backup using the Recovery Services agent (MARS) allows you to back up file or folder and system state data to Azure Recovery Services vault. This data is encrypted using a passphrase provided during the installation and registration of the MARS agent. This passphrase is required to retrieve and restore the backup data and needs to be saved in a secure external location, such as Azure Key Vault.
+Azure Backup using the Recovery Services agent (MARS) allows you to back up file or folder and system state data to Azure Recovery Services vault. This data is encrypted using a passphrase provided during the installation and registration of the MARS agent. This passphrase is required to retrieve and restore the backup data and needs to be saved in a secure external location, such as Key Vault.
 
-We recommend you to create a Key Vault and provide permissions to your Recovery Services vault to save the passphrase to the Key Vault. [Learn more](save-backup-passphrase-securely-in-azure-key-vault.md).
+We recommend you create a key vault and provide permissions to your Recovery Services vault to save the passphrase to the key vault. [Learn more](save-backup-passphrase-securely-in-azure-key-vault.md).
 
 ### Verify internet access
 
@@ -152,4 +152,4 @@ To install and register  the MARRS agent, follow these steps:
 
 ## Next step
 
-Learn how to [Back up Windows machines by using the Azure Backup MARS agent](backup-windows-with-mars-agent.md)
+Learn how to [Back up Windows machines by using the Azure Backup MARS agent](backup-windows-with-mars-agent.md)

articles/confidential-computing/confidential-containers-on-aks-preview.md

@@ -30,7 +30,7 @@ In alignment with the guidelines set by the [Confidential Computing Consortium](
 *	Code integrity: Runtime enforcement is always available through customer defined policies for containers and container configuration, such as immutable policies and container signing. 
 *	Isolation from operator: Security designs that assume least privilege and highest isolation shielding from all untrusted parties including customer/tenant admins. It includes hardening existing Kubernetes control plane access (kubelet) to confidential pods.
 
-But with these features of confidentiality, the product should additionally its ease of use: it supports all unmodified Linux containers with high Kubernetes feature conformance. Additionally, it supports  heterogenous node pools (GPU, general-purpose nodes) in a single cluster to optimize for cost.  
+With these confidentiality features fulfilled, the product should additionally support all unmodified Linux containers with high Kubernetes feature conformance. Additionally, it supports heterogeneous node pools (GPU, general-purpose nodes) in a single cluster to optimize cost.  
 
 ## What forms Confidential Containers on AKS?
 

articles/confidential-computing/confidential-nodes-aks-faq.yml

@@ -30,7 +30,7 @@ sections:
         answer: |
           No. [AKS-Engine based confidential computing nodes](https://github.com/Azure/aks-engine/blob/master/docs/topics/sgx.md) support confidential computing nodes that allow custom installations and have full control over your Kubernetes control plane.
 
-      - question: Can I run ACC Nodes with other standard AKS SKUs (build a heterogenous node pool cluster)? 
+      - question: Can I run ACC Nodes with other standard AKS SKUs (build a heterogeneous node pool cluster)? 
         answer: |
           Yes, you can run different node pools within the same AKS cluster including ACC nodes. To target your enclave applications on a specific node pool, consider adding node selectors or applying EPC limits. Refer to more details on the quick start on confidential nodes [here](confidential-enclave-nodes-aks-get-started.md).
 

articles/iot-hub-device-update/understand-device-update.md

@@ -47,7 +47,7 @@ You can use Device Update management and deployment controls to maximize product
 - An update management experience integrated with Azure IoT Hub.
 - Programmatic APIs to enable automation and custom portal experiences.
 - Subscription- and role-based access controls available through the Azure portal.
-- At-a-glance update compliance and status views across heterogenous device fleets.
+- At-a-glance update compliance and status views across heterogeneous device fleets.
 - Azure CLI support for creating and managing Device Update resources, groups, and deployments.
 
 ### Control over deployment details

articles/iot-hub/iot-hub-device-management-overview.md

@@ -100,7 +100,7 @@ Device Update for IoT Hub offers optimized update deployment and streamlined ope
 * Update management UX integrated with Azure IoT Hub
 * Gradual update rollout through device grouping and update scheduling controls
 * Programmatic APIs to enable automation and custom portal experiences
-* At-a-glance update compliance and status views across heterogenous device fleets
+* At-a-glance update compliance and status views across heterogeneous device fleets
 * Support for resilient device updates (A/B) to deliver seamless rollback
 * Content caching and disconnected device support, including those devices that are in nested configurations, through built-in Microsoft Connected Cache and integration with Azure IoT Edge
 * Subscription and role-based access controls available via the [Azure portal](https://portal.azure.com)

articles/migrate/create-application-assessment.md

@@ -12,7 +12,7 @@ ms.date: 11/05/2024
 
 This article shows you how to create an application assessment to migrate or modernize your application workloads using Azure Migrate. Creating an application assessment for your application provides you the multiple migration strategies that you can use to migrate your workloads identify the recommended as well as alternative targets and key insights such as **readiness**, **target right-sizing**, and **cost** to host and run these workloads on Azure month over month.  
 
-You can also create a cross-workload assessment using the following steps. A cross-workload assessment can constitute multiple workloads that do not necessarily combine to form just one application, it can be a group of multiple applications or it can be just a group of heterogenous workloads in your datacenter.  
+You can also create a cross-workload assessment using the following steps. A cross-workload assessment can constitute multiple workloads that do not necessarily combine to form just one application, it can be a group of multiple applications or it can be just a group of heterogeneous workloads in your datacenter.  
 
 In this article, you’ll learn how to:  
 

articles/sap/workloads/dbms-guide-sqlserver.md

@@ -76,7 +76,7 @@ A VM configuration, which runs SQL Server with an SAP database and where tempdb
 
 The diagram displays a simple case. As eluded to in the article [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md), Azure storage type, number, and size of disks is dependent from different factors. But in general we recommend:
 
-- For smaller and mid-range deployments, using one large volume, which contains the SQL Server data files. Reason behind this configuration is that it's easier to deal with different I/O workloads in case the SQL Server data files don't have the same free space. Whereas in large deployments, especially deployments where the customer moved with a heterogenous database migration to SQL Server in Azure, we used separate disks and then distributed the data files across those disks. Such an architecture is only successful when each disk has the same number of data files, all the data files are the same size, and roughly have the same free space.
+- For smaller and mid-range deployments, using one large volume, which contains the SQL Server data files. Reason behind this configuration is that it's easier to deal with different I/O workloads in case the SQL Server data files don't have the same free space. Whereas in large deployments, especially deployments where the customer moved with a heterogeneous database migration to SQL Server in Azure, we used separate disks and then distributed the data files across those disks. Such an architecture is only successful when each disk has the same number of data files, all the data files are the same size, and roughly have the same free space.
 - Use the D:\drive for tempdb as long as performance is good enough. If the overall workload is limited in performance of tempdb located on the D:\ drive, you need to move tempdb to Azure premium storage v1 or v2, or Ultra disk as recommended in [this article](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist).
 
 SQL Server proportional fill mechanism distributes reads and writes to all datafiles evenly provided all SQL Server data files are the same size and have the same frees pace. SAP on SQL Server delivers the best performance when reads and writes are distributed evenly across all available datafiles. If a database has too few datafiles or the existing data files are highly unbalanced, the best method to correct is an R3load export and import.  An R3load export and import involves downtime and should only be done if there's an obvious performance problem that needs to be resolved. If the datafiles are only moderately different sizes, increase all datafiles to the same size, and SQL Server is rebalancing data over time. SQL Server automatically grows datafiles evenly if trace flag 1117 is set or if SQL Server 2016 or higher is used without trace flag.