Merge pull request #301754 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/cost-management-billing/understand/review-enterprise-agreement-bill.md

@@ -49,6 +49,7 @@ You receive an Azure invoice when any of the following events occur during your
     - Visual Studio Enterprise (Annual)
     - Visual Studio Professional (Monthly)
     - Visual Studio Professional (Annual)
+    - Azure Communication Services (SMS and PSTN)
 - **Marketplace charges**: Azure Marketplace purchases and usage aren't covered by your organization's credit. So, you're invoiced for Marketplace charges despite your credit balance. In the Azure portal, an Enterprise Administrator can enable and disable Marketplace purchases.
 
 Your invoice shows Azure usage charges with costs associated to them first, followed by any marketplace charges. If you have a credit balance, it gets applied to Azure usage and your invoice shows Azure usage and marketplace usage without any cost, last in the list.

articles/cyclecloud/how-to/cluster-templates.md

@@ -266,7 +266,7 @@ all of the available machine types. The other ParameterType values are:
 
 ## Chef Server Support
 
-Azure CycleCloud suports [ChefServer](https://docs.chef.io/server_components.html).
+Azure CycleCloud supports [ChefServer](https://docs.chef.io/server_components.html).
 
 Create the file `chefserver.json` and add your credentials. `ValidationKey`
 corresponds to the validation.pem file for your chef server. You also must prove the

articles/cyclecloud/how-to/mount-disk.md

@@ -76,7 +76,7 @@ The above example shows there are three volumes that should be attached to the n
 ## Disk Encryption
 CycleCloud supports server-side encryption (SSE) for OS and data disk Volumes using [Azure Disk Encryption Sets](/azure/virtual-machines/disk-encryption).
 Azure uses _Platform Managed Keys_ (PMK) by default. However, to use _Customer Managed Keys_ (CMK), you must first set up an Azure Disk Encryption Set and a Key Vault with your key.
-Follow the documention here to [set up your Disk Encryption Set](/azure/virtual-machines/disks-enable-customer-managed-keys-portal).  
+Follow the documentation here to [set up your Disk Encryption Set](/azure/virtual-machines/disks-enable-customer-managed-keys-portal).  
 
 Record the ``Resource ID`` of the Disk Encryption Set when you create it.  You can find this in the Azure Portal under **Properties** in the **Disk Encryption Sets** blade.
 

articles/cyclecloud/how-to/running-in-locked-down-network.md

@@ -130,7 +130,7 @@ cd "${RELEASE_VERSION}"
 # Download release artifacts from githug (on a machine with github access)
 cyclecloud project fetch "${RELEASE_URL}" .
 
-# Create a tarbal with the project files pre-staged
+# Create a tarball with the project files pre-staged
 cyclecloud project build
 mv ./build/slurm "./${RELEASE_VERSION}"
 tar czf "slurm-${RELEASE_VERSION}.tgz" ./blobs "./${RELEASE_VERSION}"

articles/data-factory/concepts-change-data-capture.md

@@ -86,14 +86,14 @@ In the monitoring section, you always have the chance to rerun a pipeline. When
 
 ## Tutorials
 
-The followings are the tutorials to start the change data capture in Azure Data Factory and Azure Synapse Analytics.
+The following are the tutorials to start the change data capture in Azure Data Factory and Azure Synapse Analytics.
 
 - [SAP CDC tutorial in ADF](sap-change-data-capture-introduction-architecture.md#sap-cdc-capabilities)
 - [Incrementally copy data from a source data store to a destination data store tutorials](tutorial-incremental-copy-overview.md)
 
 ## Templates
 
-The followings are the templates to use the change data capture in Azure Data Factory and Azure Synapse Analytics.
+The following are the templates to use the change data capture in Azure Data Factory and Azure Synapse Analytics.
 
 - [Replicate multiple objects from SAP via SAP CDC](solution-template-replicate-multiple-objects-sap-cdc.md)
 

articles/data-factory/copy-activity-fault-tolerance.md

@@ -35,7 +35,7 @@ To configure fault tolerance in a Copy activity in a pipeline with UI, complete
    :::image type="content" source="media/copy-activity-fault-tolerance/configure-fault-tolerance.png" alt-text="Shows the UI for a Copy Data activity on the Settings tab with the Fault Tolerance configuration highlighted.":::
 
 ### Configuration 
-When you copy binary files between storage stores, you can enable fault tolerance as followings: 
+When you copy binary files between storage stores, you can enable fault tolerance as following: 
 
 ```json
 {
@@ -91,7 +91,7 @@ linkedServiceName | The linked service of [Azure Blob Storage](connector-azure-b
 path | The path of the log files. | Specify the path that you use to store the log files. If you do not provide a path, the service creates a container for you. | No
 
 > [!NOTE]
-> The followings are the prerequisites of enabling fault tolerance in copy activity when copying binary files.
+> The following are the prerequisites of enabling fault tolerance in copy activity when copying binary files.
 > For skipping particular files when they are being deleted from source store:
 > - The source dataset and sink dataset have to be binary format, and the compression type cannot be specified. 
 > - The supported data store types are Azure Blob storage, Azure Data Lake Storage Gen1, Azure Data Lake Storage Gen2, Azure Files, File System, FTP, SFTP, Amazon S3, Google Cloud Storage and HDFS.

articles/frontdoor/migrate-cdn-to-front-door.md

@@ -33,7 +33,7 @@ We recommend that your plan this migration well in advance and test the function
     
 ## Migrate your workloads
 
-The followings steps assume you're using an Azure Blob Storage account as your origin. If you're using a different origin, adjust the steps accordingly.
+The following steps assume you're using an Azure Blob Storage account as your origin. If you're using a different origin, adjust the steps accordingly.
 
 :::image type="content" source="./media/migrate-cdn-to-front-door/cdn-traffic-manager.png" alt-text="Diagram of Azure Traffic Manager distributing traffic between Azure Front Door and Azure CDN from Edgio.":::
 

articles/sap/monitor/enable-trusted-access.md

@@ -37,7 +37,7 @@ To use the trusted access using MSI feature, you need to meet the following prer
 1. Log in to the Azure portal and navigate to your Azure Monitor for SAP solutions resource.
 2. Migrate to Dedicated app service plan: [Follow steps here](https://go.microsoft.com/fwlink/?linkid=2306196)
 3. Go to the identity tab and enable the system assigned identity and wait for the operation to complete and monitor should be in succeeded state after the operation.
-![Screenshot of Enabling Trusted Access under Indentity tab.](../monitor/media/enable-trusted-access/enable-mi-existing-customer.png)
+![Screenshot of Enabling Trusted Access under Identity tab.](../monitor/media/enable-trusted-access/enable-mi-existing-customer.png)
 
 ## Disable Identity on existing AMS
 * Go to Identity tab for AMS and disable the identity and save.

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

@@ -48,7 +48,7 @@ There's some SQL Server in IaaS specific information you should know before cont
 
 
 ## New M-series VMs and SQL Server
-Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family should't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accommodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16&preserve-view=true#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
+Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family shouldn't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accommodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16&preserve-view=true#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
 - M176(d)s_3_v3 - disable SMT or use M176bds_4_v3 or M176bds_4_v3 as alternative
 - M176(d)s_4_v3 - disable SMT or use M176bds_4_v3 as alternative
 - M624(d)s_12_v3 - disable SMT or use M416ms_v2 as alternative

articles/service-connector/how-to-use-service-connector-in-aks.md

@@ -203,7 +203,7 @@ The Service Connector Kubernetes extension is built on top of [Azure Arc-enabled
 
 ### Check Kubernetes cluster logs
 
-If an error occurs during the extension installation and the error message in the `statuses` property doesn't provide sufficient information, you can further investigate by checking the Kubernetes logs with the followings steps.
+If an error occurs during the extension installation and the error message in the `statuses` property doesn't provide sufficient information, you can further investigate by checking the Kubernetes logs with the following steps.
 
 1. Connect to your AKS cluster.