Merge pull request #269113 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/ai-services/openai/concepts/provisioned-throughput.md

@@ -44,7 +44,7 @@ You need to speak with your Microsoft sales/account team to acquire provisioned
 
 ### Provisioned throughput units
 
-Provisioned throughput units (PTU) are units of model processing capacity that customers you can reserve and deploy for processing prompts and generating completions. The minimum PTU deployment, increments, and processing capacity associated with each unit varies by model type & version.
+Provisioned throughput units (PTU) are units of model processing capacity that you can reserve and deploy for processing prompts and generating completions. The minimum PTU deployment, increments, and processing capacity associated with each unit varies by model type & version.
 
 ### Deployment types
 

articles/aks/use-trusted-launch.md

@@ -95,7 +95,7 @@ Perform the following steps to deploy an AKS cluster using the Azure CLI.
    The following example creates a cluster named *myAKSCluster* with one node in the *myResourceGroup*, and enables Secure Boot and vTPM:
 
     ```azurecli
-    az aks create --name myAKSCluster --resource-group myResourceGroup --enable-secure-boot --enable-vtpm --enable-managed-identity --generate-ssh-keys
+    az aks create --name myAKSCluster --resource-group myResourceGroup --node-count 1 --enable-secure-boot --enable-vtpm --enable-managed-identity --generate-ssh-keys
     ```
 
 2. Run the following command to get access credentials for the Kubernetes cluster. Use the [az aks get-credentials][az-aks-get-credentials] command and replace the values for the cluster name and the resource group name.
@@ -214,4 +214,4 @@ In this article, you learned how to enable trusted launch. Learn more about [tru
 [azure-generation-two-virtual-machines]: ../virtual-machines/generation-2.md
 [verify-secure-boot-failures]: ../virtual-machines/trusted-launch-faq.md#verifying-secure-boot-failures
 [tusted-launch-ephemeral-os-sizes]: ../virtual-machines/ephemeral-os-disks.md#trusted-launch-for-ephemeral-os-disks
-[skip-gpu-driver-install]: gpu-cluster.md#skip-gpu-driver-installation-preview
+[skip-gpu-driver-install]: gpu-cluster.md#skip-gpu-driver-installation-preview

articles/azure-monitor/agents/agents-overview.md

@@ -247,7 +247,7 @@ View [supported operating systems for Azure Arc Connected Machine agent](../../a
 > Machines and appliances that run heavily customized or stripped-down versions of the above distributions and hosted solutions that disallow customization by the user are not supported. Azure Monitor and legacy agents rely on various packages and other baseline functionality that is often removed from such systems, and their installation may require some environmental modifications considered to be disallowed by the appliance vendor. For instance, [GitHub Enterprise Server](https://docs.github.com/en/enterprise-server/admin/overview/about-github-enterprise-server) is not supported due to heavy customization as well as [documented, license-level disallowance](https://docs.github.com/en/enterprise-server/admin/overview/system-overview#operating-system-software-and-patches) of operating system modification.
 
 > [!NOTE]
-> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage COGS savings, compared to other Azure VMs that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
+> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage savings, compared to other Azure VMs that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
 
 ### Linux Hardening Standards
 

articles/cost-management-billing/savings-plan/scope-savings-plan.md

@@ -23,7 +23,7 @@ You have the following options to scope a savings plan, depending on your needs:
 - **Single subscription scope** - Applies the savings plan benefit to the eligible resources in the selected subscription.
 - **Shared scope** - Applies the savings plan benefit to eligible resources within subscriptions that are in the billing context. If a subscription was moved to different billing context, the benefit will no longer be applied to this subscription and will continue to apply to other subscriptions in the billing context.
   - For Enterprise Agreement customers, the billing context is the enrollment. The savings plan shared scope would include multiple Microsoft Entra tenants in an enrollment.
-  - For Microsoft Customer Agreement customers, the billing scope is the billing profile.
+  - For Microsoft Customer Agreement customers, the billing scope is the billing profile. Usage from all billing subscriptions under the billing profile, is eligible to receive benefits for a Shared scoped savings plan.
 - **Management group** - Applies the savings plan benefit to eligible resources in the list of subscriptions that are a part of both the management group and billing scope. To buy a savings plan for a management group, you must have at least read permission on the management group and be a savings plan owner on the billing subscription.
 
 ## Scope processing order
@@ -39,4 +39,4 @@ You can always update the scope after you buy a savings plan. To do so, go to th
 
 ## Next steps
 
-- [Change the savings plan scope](manage-savings-plan.md#change-the-savings-plan-scope).
+- [Change the savings plan scope](manage-savings-plan.md#change-the-savings-plan-scope).

articles/virtual-machines/trusted-launch-faq.md

@@ -58,6 +58,9 @@ $adminPassword = <PASSWORD> | ConvertTo-SecureString -AsPlainText -Force
 $vmCred = New-Object System.Management.Automation.PSCredential($adminUsername, $adminPassword)
 New-AzVM -Name MyVm -Credential $vmCred -SecurityType Standard
 ```
+### Can I disable Secure Boot option for Trusted Launch VMs?
+
+Secure Boot is NOT enabled by default but it is recommended to enable it if you are not using custom unsigned kernel or drivers. Once a VM is created with Trusted Launch and Secure Boot option enabled, you can go to VM, under Settings tab, go to Configurations and unselect 'Enable secure boot' option. 
 
 ---