Merge pull request #276582 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/azure-functions/functions-add-output-binding-azure-sql-vs-code.md

@@ -223,16 +223,16 @@ Update *HttpExample\\function_app.py* to match the following code. Add the `toDo
 import azure.functions as func
 import logging
 from azure.functions.decorators.core import DataType
+import uuid
 
 app = func.FunctionApp()
 
 @app.function_name(name="HttpTrigger1")
 @app.route(route="hello", auth_level=func.AuthLevel.ANONYMOUS)
-@app.generic_output_binding(arg_name="toDoItems", type="sql", CommandText="dbo.ToDo", ConnectionStringSetting="SqlConnectionString"
-    data_type=DataType.STRING)
+@app.generic_output_binding(arg_name="toDoItems", type="sql", CommandText="dbo.ToDo", ConnectionStringSetting="SqlConnectionString",data_type=DataType.STRING)
 def test_function(req: func.HttpRequest, toDoItems: func.Out[func.SqlRow]) -> func.HttpResponse:
      logging.info('Python HTTP trigger function processed a request.')
-     name = req.params.get('name')
+     name = req.get_json().get('name')
      if not name:
         try:
             req_body = req.get_json()
@@ -242,7 +242,7 @@ def test_function(req: func.HttpRequest, toDoItems: func.Out[func.SqlRow]) -> fu
             name = req_body.get('name')
 
      if name:
-        toDoItems.set(func.SqlRow({"id": uuid.uuid4(), "title": name, "completed": false, url: ""}))
+        toDoItems.set(func.SqlRow({"Id": str(uuid.uuid4()), "title": name, "completed": False, "url": ""}))
         return func.HttpResponse(f"Hello {name}!")
      else:
         return func.HttpResponse(

articles/azure-government/documentation-government-csp-list.md

@@ -381,6 +381,7 @@ Below you can find a list of all the authorized Cloud Solution Providers (CSPs),
 |[Saasplaza](https://www.intwo.cloud/)|
 |[Science Applications International Corporation](https://www.saic.com)|
 |[Secure-24](https://www.secure-24.com)|
+|[Sela Cloud](https://www.selacloud.com)|
 |[Selex Galileo Inc](http://www.selexgalileo.com/)|
 |[Sentinel Blue](https://www.sentinelblue.com/)|
 |[Sev1Tech](https://www.sev1tech.com/)|

articles/azure-monitor/containers/container-insights-persistent-volumes.md

@@ -2,7 +2,7 @@
 title: Configure PV monitoring with Container insights | Microsoft Docs
 description: This article describes how you can configure monitoring Kubernetes clusters with persistent volumes with Container insights.
 ms.topic: conceptual
-ms.date: 2/28/2024
+ms.date: 5/15/2024
 ms.reviewer: aul
 ---
 
@@ -12,7 +12,7 @@ Starting with agent version *ciprod10052020*, the Container insights integrated
 
 ## PV metrics
 
-Container insights automatically starts monitoring PV usage by collecting the following metrics at 60-second intervals and storing them in the **InsightMetrics** table.
+Container insights automatically starts monitoring PV usage by collecting the following metrics at 60-second intervals and storing them in the **InsightsMetrics** table.
 
 | Metric name | Metric dimension (tags) | Metric description |
 |-----|-----------|----------|
@@ -54,4 +54,4 @@ Persistent volumes where storage class is "azureblob-*" won't collect PV metrics
 
 ## Next steps
 
-To learn more about collected PV metrics, see [Configure agent data collection for Container insights](./container-insights-data-collection-configmap.md).
+To learn more about collected PV metrics, see [Configure agent data collection for Container insights](./container-insights-data-collection-configmap.md).

articles/azure-monitor/visualize/workbooks-limits.md

@@ -33,7 +33,7 @@ This table lists the limits of specific data visualizations.
 
 |Visualization|Limits |
 |---------|---------|
-|Grid|By default, grids only display the first 250 rows of data. This setting can be changed in the query component's advanced settings to display up to 10,000 rows. Any further items are ignored, and a warning appears.|
+|Grid|By default, grids only display the first 250 rows of data. This setting can be changed in the query component's advanced settings to display up to 10,000 rows. Any further items are ignored, and a warning appears.<br>The checkbox for toggling the selection of all items is available only when the grid displays 150 rows of data or fewer.|
 |Charts|Charts are limited to 100 series.<br>Charts are limited to 10,000 data points. |
 |Tiles|Tiles is limited to displaying 100 tiles. Any further items are ignored, and a warning appears.|
 |Maps|Maps are limited to displaying 100 points. Any further items are ignored, and a warning appears.|
@@ -48,4 +48,4 @@ This table lists the limits of specific data parameters.
 |Drop down|Drop-down-based parameters are limited to 1,000 items. Any items returned by a query after that are ignored.<br>When based on a query, only the first four columns of data produced by the query are used. Any other columns are ignored.|
 |Multi-value|Multi-value parameters are limited to 100 items. Any items returned by a query after that are ignored.<br>When based on a query, only the first column of data produced by the query is used. Any other columns are ignored. |
 |Options group|Options group parameters are limited to 1,000 items. Any items returned by a query after that are ignored. <br>When based on a query, only the first column of data produced by the query is used. Any other columns are ignored.|
-|Text|Text parameters that retrieve their value based on a query will only display the first cell returned by the query (row 1, column 1). Any other data is ignored.|
+|Text|Text parameters that retrieve their value based on a query will only display the first cell returned by the query (row 1, column 1). Any other data is ignored.|

articles/azure-resource-manager/management/lock-resources.md

@@ -61,6 +61,7 @@ Applying locks can lead to unexpected results. Some operations, which don't seem
 - A read-only lock on a **storage account** protects RBAC assignments scoped for a storage account or a data container (blob container or queue).
 
 - A read-only lock on a **storage account** prevents the creation of a blob container.
+-  A read-only lock on a **storage account** prevents the creation of a blob container. However, create operations on a storage account can be done through both the control plane and data plane. Read-only locks only block control plane create requests, but a user can still perform a valid create operation on the resource through the data plane.
 
 - A read-only lock or cannot-delete lock on a **storage account** doesn't prevent its data from deletion or modification. It also doesn't protect the data in a blob, queue, table, or file.
 

articles/machine-learning/v1/how-to-deploy-azure-kubernetes-service.md

@@ -88,13 +88,9 @@ In Azure Machine Learning, deployment is used in the more general sense of makin
 The front-end component (azureml-fe) that routes incoming inference requests to deployed services automatically scales as needed. Scaling of azureml-fe is based on the AKS cluster purpose and size (number of nodes). The cluster purpose and nodes are configured when you [create or attach an AKS cluster](../how-to-create-attach-kubernetes.md). There's one azureml-fe service per cluster, which might be running on multiple pods.
 
 > [!IMPORTANT]
-> When using a cluster configured as `dev-test`, the self-scaler is *disabled*. Even for FastProd/DenseProd clusters, Self-Scaler is only enabled when telemetry shows that it's needed.
-
-> [!IMPORTANT]
-> Azure Machine Learning does not upload and or save container logs, even for system containers. For full debuggability, you should [enable Container Insights for your AKS cluster](../../azure-monitor/containers/kubernetes-monitoring-enable.md#enable-container-insights) on your own to save and manage container logs, and share the related logs with AML team when necessary. Otherwise, AML does not commit SLA on azureml-fe related issues.
-
-> [!NOTE]
-> The maximum request payload is 100MB.
+> * When using a cluster configured as `dev-test`, the self-scaler is *disabled*. Even for FastProd/DenseProd clusters, Self-Scaler is only enabled when telemetry shows that it's needed.
+> * Azure Machine Learning doesn't automatically upload or store logs from any containers, including system containers. For comprehensive debugging, it's recommended that you [enable Container Insights for your AKS cluster](../../azure-monitor/containers/kubernetes-monitoring-enable.md#enable-container-insights). This allows you to save, manage, and share container logs with the AML team when needed. Without this, AML can't guarantee support for issues related to azureml-fe.
+> * The maximum request payload is 100MB.
 
 Azureml-fe scales both up (vertically) to use more cores, and out (horizontally) to use more pods. When making the decision to scale up, the time that it takes to route incoming inference requests is used. If this time exceeds the threshold, a scale-up occurs. If the time to route incoming requests continues to exceed the threshold, a scale-out occurs.
 

articles/storage/tables/table-storage-design-modeling.md

@@ -113,7 +113,7 @@ You can persist instances of the two concrete classes in the Table service using
 
 ![Person table](media/storage-table-design-guide/storage-table-design-IMAGE04.png)
 
-For more information about working with multiple entity types in the same table in client code, see the section Working with heterogeneous entity types later in this guide. This provides examples of how to recognize the entity type in client code.  
+For more information about working with multiple entity types in the same table in client code, see the section [Working with heterogeneous entity types](table-storage-design-patterns.md#working-with-heterogeneous-entity-types) later in this guide. This provides examples of how to recognize the entity type in client code.  
 
 
 ## Next steps

includes/container-instances-create-docker-context.md

@@ -16,8 +16,9 @@ ms.custom: include file
 To use Docker commands to run containers in Azure Container Instances, first log into Azure:
 
 ```bash
-docker login azure
+docker login azure --tenant-id "[tenant ID]"
 ```
+Browse to the Microsoft Entra ID properties to find your tenant ID.
 
 When prompted, enter or select your Azure credentials.
 
@@ -35,4 +36,4 @@ Run `docker context ls` to confirm that you added the ACI context to your Docker
 
 ```
 docker context ls
-```
+```