Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into lb-arm

Author: halkazwini

.openpublishing.redirection.json

@@ -1649,6 +1649,11 @@
             "source_path_from_root": "/articles/dns/dns-getstarted-create-recordset.md",
             "redirect_url": "/azure/dns/dns-getstarted-powershell",
             "redirect_document_id": false
+        },
+		{
+            "source_path_from_root": "/articles/time-series-insights/migration-to-adx.md",
+            "redirect_url": "/azure/time-series-insights/migration-to-fabric.md",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/dns/dns-operations-dnszones-cli-nodejs.md",

articles/ai-studio/how-to/create-azure-ai-resource.md

@@ -102,12 +102,45 @@ For hubs that use CMK encryption mode, you can update the encryption key to a ne
 
 ### Update Azure Application Insights and Azure Container Registry
 
-To use custom environments for Prompt Flow, you're required to configure an Azure Container Registry for your hub. To use Azure Application Insights for Prompt Flow deployments, a configured Azure Application Insights resource is required for your hub.
+To use custom environments for Prompt Flow, you're required to configure an Azure Container Registry for your hub. To use Azure Application Insights for Prompt Flow deployments, a configured Azure Application Insights resource is required for your hub. Updating the workspace-attached Azure Container Registry or ApplicationInsights resources may break lineage of previous jobs, deployed inference endpoints, or your ability to rerun earlier jobs in the workspace. 
 
-You can configure your hub for these resources during creation or update after creation. To update Azure Application Insights from the Azure portal, navigate to the **Properties** for your hub in the Azure portal, then select **Change Application Insights**. You can also use the Azure SDK/CLI options or infrastructure-as-code templates to update both Azure Application Insights and Azure Container Registry for the hub.
+You can use the Azure Portal, Azure SDK/CLI options, or the infrastructure-as-code templates to update both Azure Application Insights and Azure Container Registry for the hub.
+
+# [Azure portal](#tab/portal)
+
+You can configure your hub for these resources during creation or update after creation. 
+
+To update Azure Application Insights from the Azure portal, navigate to the **Properties** for your hub in the Azure portal, then select **Change Application Insights**.
 
 :::image type="content" source="~/reusable-content/ce-skilling/azure/media/how-to/resource-manage-update-associated-resources.png" alt-text="Screenshot of the properties page of the hub resource in the Azure portal." lightbox="~/reusable-content/ce-skilling/azure/media/how-to/resource-manage-update-associated-resources.png":::
 
+# [Python SDK](#tab/python)
+
+```python
+from azure.ai.ml.entities import Hub
+
+my_app_insights = "{APPLICATION_INSIGHTS_ARM_ID}"
+my_container_registry = "{CONTAINER_REGISTRY_ARM_ID}"
+
+# construct a basic hub
+my_hub = Hub(name="myexamplehub", 
+             location="East US", 
+             application_insights=my_app_insights,
+             container_registry=my_container_registry)
+
+# update_dependent_resources is used to give consent to update the workspace dependent resources.
+created_hub = ml_client.workspaces.begin_update(workspace=my_hub, update_dependent_resources=True).result()
+```
+
+# [Azure CLI](#tab/azurecli)
+
+See flag documentation for [```az ml workspace update```](/cli/azure/ml/workspace#az-ml-workspace-update)
+
+```azurecli
+az ml workspace update -n "myexamplehub" -g "{MY_RESOURCE_GROUP}" -a "APPLICATION_INSIGHTS_ARM_ID" -u
+```
+---
+
 ## Next steps
 
 - [Create a project](create-projects.md)

articles/ai-studio/how-to/create-projects.md

@@ -103,9 +103,28 @@ To view settings for the project, use the `az ml workspace show` command. For ex
 az ml workspace show --name {my_project_name} --resource-group {my_resource_group}
 ```
 
-
 ---
 
+## Project resource access
+
+Common configurations on the hub are shared with your project, including connections, compute instances, and network access, so you can start developing right away.
+
+In addition, a number of resources are only accessible by users in your project workspace:
+
+1. Components including datasets, flows, indexes, deployed model API endpoints (open and serverless).
+1. Connections created by you under 'project settings'.
+1. Azure Storage blob containers, and a fileshare for data upload within your project. Access storage using the following connections:
+   
+   | Data connection | Storage location | Purpose |
+   | --- | --- | --- |
+   | workspaceblobstore | {project-GUID}-blobstore | Default container for data upload |
+   | workspaceartifactstore | {project-GUID}-blobstore | Stores components and metadata for your project such as model weights |
+   | workspacefilestore | {project-GUID}-code | Hosts files created on your compute and using prompt flow |
+
+> [!NOTE]
+> Storage connections are not created directly with the project when your storage account has public network access set to disabled. These are created instead when a first user accesses AI studio over a private network connection.
+
+
 ## Next steps
 
 - [Deploy an enterprise chat web app](../tutorials/deploy-chat-web-app.md)

articles/aks/advanced-container-networking-services-overview.md

@@ -30,7 +30,7 @@ For more information about Advanced Network Observability, see [What is Advanced
 
 ## Pricing
 > [!IMPORTANT]
-> Advanced Container Networking Services will be a paid offering starting June 4th, 2024. 
+> Advanced Container Networking Services will be a paid offering. For more information about pricing, see [Advanced Container Networking Services - Pricing](https://azure.microsoft.com/pricing/details/azure-container-networking-services/)
 
 ## Next steps
 

articles/aks/configure-azure-cni-static-block-allocation.md

@@ -76,9 +76,9 @@ where N is any positive integer greater than 0
 
 Ideal values with no IP wastage would require the max pods value to conform to the above expression.
 
-**Example 1:** max_pods = 30, CIDR Blocks allocated per node = 2, Total IPs available for pods = (16 * 2) - 1 = 32 - 1 = 31, IP wastage per node = 31 - 30 = 1 **[Low wastage - Acceptable Case]**
-**Example 2:** max_pods = 31, CIDR Blocks allocated per node = 2, Total IPs available for pods = (16 * 2) - 1 = 32 - 1 = 31, IP wastage per node = 31 - 31 = 0 **[Ideal Case]**
-**Example 3:** max_pods = 32, CIDR Blocks allocated per node = 3, Total IPs available for pods = (16 * 3) - 1 = 48 - 1 = 47, IP wastage per node = 47 - 32 = 15 **[High Wastage - Not Recommended Case]**
+- **Example 1:** max_pods = 30, CIDR Blocks allocated per node = 2, Total IPs available for pods = (16 * 2) - 1 = 32 - 1 = 31, IP wastage per node = 31 - 30 = 1 **[Low wastage - Acceptable Case]**
+- **Example 2:** max_pods = 31, CIDR Blocks allocated per node = 2, Total IPs available for pods = (16 * 2) - 1 = 32 - 1 = 31, IP wastage per node = 31 - 31 = 0 **[Ideal Case]**
+- **Example 3:** max_pods = 32, CIDR Blocks allocated per node = 3, Total IPs available for pods = (16 * 3) - 1 = 48 - 1 = 47, IP wastage per node = 47 - 32 = 15 **[High Wastage - Not Recommended Case]**
 
 The planning of IPs for Kubernetes services remain unchanged.
 
@@ -87,7 +87,7 @@ The planning of IPs for Kubernetes services remain unchanged.
 
 ## Deployment parameters
 
-The [deployment parameters][azure-cni-deployment-parameters]for configuring basic Azure CNI networking in AKS are all valid, with two exceptions:
+The [deployment parameters][azure-cni-deployment-parameters] for configuring basic Azure CNI networking in AKS are all valid, with two exceptions:
 
 - The **vnet subnet id** parameter now refers to the subnet related to the cluster's nodes.
 - The parameter **pod subnet id** is used to specify the subnet whose IP addresses will be statically or dynamically allocated to pods in the node pool.
@@ -204,7 +204,7 @@ az aks nodepool add --cluster-name $clusterName -g $resourceGroup  -n newnodepoo
 
 - **Can some node pools in a cluster use Dynamic IP allocation while others use the new Static Block allocation?**
 
-Yes, different node pools can use different allocation modes. However, once a subnet is used in one allocation mode it can only be used in the same allocation mode across all the node pools it is associated.
+  Yes, different node pools can use different allocation modes. However, once a subnet is used in one allocation mode it can only be used in the same allocation mode across all the node pools it is associated.
 
 ## Next steps
 
@@ -221,4 +221,8 @@ Learn more about networking in AKS in the following articles:
 [azure-cni-prereq]: ./configure-azure-cni.md#prerequisites
 [azure-cni-deployment-parameters]: ./azure-cni-overview.md#deployment-parameters
 [az-aks-enable-addons]: /cli/azure/aks#az_aks_enable_addons
-
+[az-extension-add]: /cli/azure/extension#az-extension-add
+[az-extension-update]: /cli/azure/extension#az-extension-update
+[az-feature-register]: /cli/azure/feature#az-feature-register
+[az-feature-show]: /cli/azure/feature#az-feature-show
+[az-provider-register]: /cli/azure/provider#az-provider-register

articles/azure-functions/flex-consumption-how-to.md

@@ -514,7 +514,7 @@ Here's how you can set HTTP concurrency limits for an existing app:
 Use the [`az functionapp scale config set`](/cli/azure/functionapp/scale/config#az-functionapp-scale-config-set) command to set specific HTTP concurrency limits for your app, regardless of instance size.
 
 ```azurecli
-az functionapp scale config set -resource-group <RESOURCE_GROUP> -name <APP_NAME> --trigger-type http --trigger-settings perInstanceConcurrency=10
+az functionapp scale config set --resource-group <RESOURCE_GROUP> --name <APP_NAME> --trigger-type http --trigger-settings perInstanceConcurrency=10
 ```
 
 This example sets the HTTP trigger concurrency level to `10`. After you specifically set an HTTP concurrency value, that value is maintained despite any changes in your app's instance size setting. 

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

@@ -68,7 +68,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
         The **Available quota** field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.  
 
     * **Large Volume**
-        If the quota of your volume is less than 100 TiB, select **No**. If the quota of your volume is greater than 100 TiB, select **Yes**.  
+        
         [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
 
     * **Throughput (MiB/S)**   

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

@@ -63,7 +63,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
         The **Available quota** field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.  
 
     * **Large Volume**
-        For volumes between 50 TiB and 500 TiB, select **Yes**. If the volume does not require more than 100 TiB, select **No**. 
+
         [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
 
     * **Throughput (MiB/S)**   

articles/azure-netapp-files/azure-netapp-files-introduction.md

@@ -40,7 +40,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Small-to-large volumes | Easily resize file volumes from 100 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
 | 1-TiB minimum capacity pool size | 1-TiB capacity pool is a reduced-size storage pool compared to the initial 4-TiB minimum. | Save money by starting with a smaller storage footprint and lower entry point, without sacrificing performance or availability. Scale storage based on growth without high upfront costs.
 | 1,000-TiB maximum capacity pool | 1000-TiB capacity pool is an increased storage pool compared to the initial 500-TiB maximum. | Reduce waste by creating larger, pooled capacity and performance budget, and share and distribute across volumes.
-| 100-500 TiB large volumes | Store large volumes of data up to 500 TiB in a single volume. | Manage large datasets and high-performance workloads with ease.
+| 50-500 TiB large volumes | Store large volumes of data up to 500 TiB in a single volume. | Manage large datasets and high-performance workloads with ease.
 | User and group quotas | Set quotas on storage usage for individual users and groups. | Control storage usage and optimize resource allocation.
 | Virtual machine (VM) networked storage performance | Higher VM network throughput compared to disk IO limits enable more demanding workloads on smaller Azure VMs. | Improve application performance at a smaller VM footprint, improving overall efficiency and lowering application license cost.
 | Deep workload readiness | Seamless deployment and migration of any-size workload with well-documented deployment guides. | Easily migrate any workload of any size to the platform. Enjoy a seamless, cost-effective deployment and migration experience.

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -29,9 +29,9 @@ The following table describes resource limits for Azure NetApp Files:
 |  Maximum size of a single capacity pool    |  1000 TiB   |   Yes   |
 |  Minimum size of a single regular volume    |    100 GiB    |    No    |
 |  Maximum size of a single regular volume     |    100 TiB    |    No    |
-|  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) |     102,401 GiB |     No |
+|  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB |     No |
 | Large volume size increase | 30% of lowest provisioned size | Yes |
-|  Maximum size of a single large volume     |    500 TiB    |    No    |
+|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md)    |    500 TiB    |    No    |
 |  Maximum size of a single file     |    16 TiB    |    No    |    
 |  Maximum size of directory metadata in a single directory      |    320 MB    |    No    |    
 |  Maximum number of files in a single directory  | *Approximately* 4 million. <br> See [Determine if a directory is approaching the limit size](#directory-limit).  |    No    |