Merge pull request #253084 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/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial.md

@@ -31,10 +31,6 @@ This tutorial describes the steps you need to perform in both GitHub Enterprise
 > * Provision groups and group memberships in GitHub Enterprise Managed User (OIDC)
 > * [Single sign-on](../manage-apps/add-application-portal-setup-oidc-sso.md) to GitHub Enterprise Managed User (OIDC) (recommended).
 
-> [!NOTE]
-> This provisioning connector is enabled only for Enterprise Managed Users beta participants.
-
-
 ## Prerequisites
 
 The scenario outlined in this tutorial assumes that you already have the following prerequisites:

articles/aks/access-private-cluster.md

@@ -28,6 +28,9 @@ The pod created by the `run` command provides `helm` and the latest compatible v
 
 `command invoke` runs the commands from your cluster, so any commands run in this manner are subject to your configured networking restrictions and any other configured restrictions. Make sure there are enough nodes and resources in your cluster to schedule this command pod.
 
+> [!NOTE]
+> The output for `command invoke` is limited to 512kB in size. 
+
 ## Run commands on your AKS cluster
 
 ### [Azure CLI - `command invoke`](#tab/azure-cli)

articles/aks/auto-upgrade-node-image.md

@@ -15,7 +15,7 @@ AKS now supports an exclusive channel dedicated to controlling node-level OS sec
 
 ## How does node OS auto-upgrade work with cluster auto-upgrade?
 
-Node-level OS security updates come in at a faster cadence than Kubernetes patch or minor version updates. This is the main reason for introducing a separate, dedicated Node OS auto-upgrade channel. With this feature, you can have a flexible and customized strategy for node-level OS security updates and a separate plan for cluster-level Kubernetes version auto-upgrades [auto-upgrade][Autoupgrade].
+Node-level OS security updates come in at a faster cadence than Kubernetes patch or minor version updates. This is the main reason for introducing a separate, dedicated Node OS auto-upgrade channel. With this feature, you can have a flexible and customized strategy for node-level OS security updates and a separate plan for cluster-level Kubernetes version [auto-upgrades][Autoupgrade].
 It's highly recommended to use both cluster-level [auto-upgrades][Autoupgrade] and the node OS auto-upgrade channel together. Scheduling can be fine-tuned by applying two separate sets of [maintenance windows][planned-maintenance] - `aksManagedAutoUpgradeSchedule` for the cluster [auto-upgrade][Autoupgrade] channel and `aksManagedNodeOSUpgradeSchedule` for the node OS auto-upgrade channel.
 
 ## Using node OS auto-upgrade

articles/azure-monitor/essentials/collect-custom-metrics-linux-telegraf.md

@@ -14,7 +14,7 @@ ms.date: 08/01/2023
 This article explains how to deploy and configure the [InfluxData](https://www.influxdata.com/) Telegraf agent on a Linux virtual machine to send metrics to Azure Monitor. 
 
 > [!NOTE]
-> InfluxData Telegraf is an open source agent and not officially supported by Azure Monitor. For issues wuth the Telegraf connector, please refer to the Telegraf GitHub page here: [InfluxData](https://github.com/influxdata/telegraf)
+> InfluxData Telegraf is an open source agent and not officially supported by Azure Monitor. For issues with the Telegraf connector, please refer to the Telegraf GitHub page here: [InfluxData](https://github.com/influxdata/telegraf)
 
 ## InfluxData Telegraf agent 
 

articles/cosmos-db/partial-document-update-faq.yml

@@ -20,7 +20,7 @@ sections:
       - question: |
           Is this an implementation of JSON Patch RFC 6902?
         answer: |
-          Azure Cosmos DB partial document update is *inspired* by [JSON Patch RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902). There are other features such as [Conditional Patch](partial-document-update.md#supported-modes) while some of the features of JSON Patch RFC 6902 such as (`Copy`, `Move`, `Test`) have not been implemented.
+          Azure Cosmos DB partial document update is *inspired* by [JSON Patch RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902). There are other features such as [Conditional Patch](partial-document-update.md#supported-modes) while some of the features of JSON Patch RFC 6902 such as (`Copy`, `Test`) have not been implemented.
 
       - question: |
           Is partial document update compatible with serverless, provisioned throughput and autoscale modes of billing?

articles/iot-central/core/howto-authorize-rest-api.md

@@ -17,13 +17,13 @@ The IoT Central REST API lets you develop client applications that integrate wit
 
 Every IoT Central REST API call requires an authorization header that IoT Central uses to determine the identity of the caller and the permissions that caller is granted within the application.
 
-This article describes the types of token you can use in the authorization header, and how to get them.
+This article describes the types of token you can use in the authorization header, and how to get them. Please note that service principals are the recommended method for access management for IoT Central REST APIs.
 
 ## Token types
 
 To access an IoT Central application using the REST API, you can use an:
 
-- _Azure Active Directory bearer token_. A bearer token is associated with an Azure Active Directory user account or service principal. The token grants the caller the same permissions the user or service principal has in the IoT Central application.
+- _Azure Active Directory bearer token_. A bearer token is associated with an Azure Active Directory user account or service principal. The token grants the caller the same permissions the user or service principal has in the IoT Central application. 
 - IoT Central API token. An API token is associated with a role in your IoT Central application.
 
 Use a bearer token associated with your user account while you're developing and testing automation and scripts that use the REST API. Use a bearer token that's associated with a service principal for production automation and scripts. Use a bearer token in preference to an API token to reduce the risk of leaks and problems when tokens expire.

articles/key-vault/certificates/create-certificate.md

@@ -31,7 +31,7 @@ The following descriptions correspond to the green lettered steps in the precedi
 4. Your chosen CA responds with an X509 Certificate.
 5. Your application completes the new certificate creation with a merger of the X509 Certificate from your CA.
 
-- **Create a certificate with a known issuer provider:** This method requires you to do a one-time task of creating an issuer object. Once an issuer object is created in you key vault, its name can be referenced in the policy of the KV certificate. A request to create such a KV certificate will create a key pair in the vault and communicate with the issuer provider service using the information in the referenced issuer object to get an x509 certificate. The x509 certificate is retrieved from the issuer service and is merged with the key pair to complete the KV certificate creation.  
+- **Create a certificate with a known issuer provider:** This method requires you to do a one-time task of creating an issuer object. Once an issuer object is created in your key vault, its name can be referenced in the policy of the KV certificate. A request to create such a KV certificate will create a key pair in the vault and communicate with the issuer provider service using the information in the referenced issuer object to get an x509 certificate. The x509 certificate is retrieved from the issuer service and is merged with the key pair to complete the KV certificate creation.  
 
 ![Create a certificate with a Key Vault partnered certificate authority](../media/certificate-authority-2.png)  
 
@@ -92,4 +92,4 @@ When an order is placed with the issuer provider, it may honor or override the x
 ## See Also
 
  - How-to guide to create certificates in Key Vault using [Portal](./quick-create-portal.md), [Azure CLI](./quick-create-cli.md), [Azure PowerShell](./quick-create-powershell.md)
- - [Monitor and manage certificate creation](create-certificate-scenarios.md)
+ - [Monitor and manage certificate creation](create-certificate-scenarios.md)

articles/machine-learning/prompt-flow/how-to-deploy-to-code.md

@@ -40,7 +40,7 @@ For managed online endpoints, Azure Machine Learning reserves 20% of your comput
 
 Each flow will have a folder which contains codes/prompts, definition and other artifacts of the flow. If you have developed your flow with UI, you can download the flow folder from the flow details page. If you have developed your flow with CLI or SDK, you should have the flow folder already.
 
-This article will use the [sample flow "basic-chat"](https://github.com/Azure/azureml-examples/examples/flows/chat/basic-chat) as an example to deploy to Azure Machine Learning managed online endpoint.
+This article will use the [sample flow "basic-chat"](https://github.com/microsoft/promptflow/tree/main/examples/flows/chat/basic-chat) as an example to deploy to Azure Machine Learning managed online endpoint.
 
 > [!IMPORTANT]
 >

articles/networking/nva-accelerated-connections.md

@@ -9,9 +9,9 @@ ms.author: steveesp
 
 ---
 
-# Accelerated connections and NVAs (Preview)
+# Accelerated connections and NVAs (Limited GA)
 
-This article helps you understand the **Accelerated Connections** feature. When Accelerated Connections is enabled on the virtual network interface (vNIC) with Accelerated Networking, networking performance is improved. This high-performance feature is available on Network Virtual Appliances (NVAs) deployed from Azure Marketplace and offers competitive performance in Connections Per Second (CPS) optimization, along with improvements to handling large amounts of simultaneous connections. To access this feature during preview, use the [Preview sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
+This article helps you understand the **Accelerated Connections** feature. When Accelerated Connections is enabled on the virtual network interface (vNIC) with Accelerated Networking, networking performance is improved. This high-performance feature is available on Network Virtual Appliances (NVAs) deployed from Azure Marketplace and offers competitive performance in Connections Per Second (CPS) optimization, along with improvements to handling large amounts of simultaneous connections. To access this feature during limited GA, use the [sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
 
 > [!IMPORTANT]
 > This feature is currently in public preview. This public preview is provided without a service-level agreement and shouldn't be used for production workloads. Certain features might not be supported, might have constrained capabilities, or might not be available in all Azure locations. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -24,7 +24,7 @@ Accelerated Connections is implemented at the network interface level to allow m
 Network Virtual Appliances (NVAs) with most large scale solutions requiring v-firewall, v-switch, load balancers and other critical network features would experience higher CPS performance with Accelerated Connections.
 
 > [!NOTE]
-> During preview, this feature is only supported for NVAs available on the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps?search=network%20virtual%20appliance&page=1&filters=virtual-machine-images%3Bpartners).
+> During limited GA, this feature is only supported for NVAs available on the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps?search=network%20virtual%20appliance&page=1&filters=virtual-machine-images%3Bpartners).
 >
 
 **Diagram 1**
@@ -41,14 +41,14 @@ Network Virtual Appliances (NVAs) with most large scale solutions requiring v-fi
 
 ### Considerations and limitations
 
-* This feature is available only for NVAs deployed from Azure Marketplace during preview.
-* To enable this feature, you must sign up for the preview using the [Preview sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
-* During preview, this feature is only available on Resource Groups created after sign-up.
+* This feature is available only for NVAs deployed from Azure Marketplace during limited GA.
+* To enable this feature, you must sign up using the [sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
+* During limited GA, this feature is only available on Resource Groups created after sign-up.
 * This feature can be enabled and is supported on new deployments using an Azure Resource Manager (ARM) template and preview instructions.
 * Feature support may vary as per the NVAs available on Marketplace.
 * Detaching and attaching a network interface on a running VM isn't supported as other Azure features.
-* Marketplace portal isn't supported for the public preview.
-* This feature is free during the preview, and chargeable after GA.
+* Marketplace portal isn't supported for the limited GA.
+* This feature is free during the limited GA, and chargeable after GA.
 
 ## Prerequisites
 
@@ -57,7 +57,7 @@ The following section lists the required prerequisites:
 * [Accelerated networking](../virtual-network/accelerated-networking-overview.md) must be enabled on the traffic network interfaces of the NVA.
 * Custom tags must be added to the resources during deployment (instructions will be provided).
 * The data path tags should be added to the vNIC properties.
-* You've signed up for the preview using the [Preview sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
+* You've signed up for the limited GA using the [sign-up form](https://go.microsoft.com/fwlink/?linkid=2223706).
 
 ## Supported regions
 
@@ -67,11 +67,24 @@ This list will be updated as more regions become available. The following region
 * West Central US
 * East US
 * West US
+* East US 2
+* Central US
 
 ## Supported SKUs
 
-This feature is supported on all SKUs supported by Accelerated Networking except the Dv5 VM family, which isn't yet supported during preview.
+This feature is supported on all SKUs supported by Accelerated Networking except the Dv5 VM family, which isn't yet supported during limited GA.
+
+## Supported enablement methods
+
+This feature enablement and deployment is supported using following methods: 
+
+* PowerShell
+* ARM templates via Azure portal
+* Azure CLI
+* Terraform
+* SDK Package Deployment
+
 
 ## Next steps
 
-Sign up for the [Preview](https://go.microsoft.com/fwlink/?linkid=2223706).
+Sign up for the [Limited GA](https://go.microsoft.com/fwlink/?linkid=2223706).

articles/open-datasets/dataset-panancestry-uk-bio-bank.md

@@ -19,7 +19,7 @@ This dataset is a mirror of the data store at https://pan.ukbb.broadinstitute.or
 
 ## Data volumes and update frequency
 
-This dataset includes approximately 756 TB of data, and is updated monthly during the first week of every month.
+This dataset includes approximately 144 TB of data, and is updated monthly during the first week of every month.
 
 ## Storage location