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

Author: halkazwini

articles/.openpublishing.redirection.private-multi-access-edge-compute-mec.json

@@ -0,0 +1,15 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/private-multi-access-edge-compute-mec/affirmed-private-network-service-overview.md ",
+            "redirect_url": "/azure/private-multi-access-edge-compute-mec/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/private-multi-access-edge-compute-mec/deploy-affirmed-private-network-service-solution.md ",
+            "redirect_url": "/azure/private-multi-access-edge-compute-mec/overview",
+            "redirect_document_id": false
+                
+        }
+   ]
+}

articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md

@@ -42,7 +42,7 @@ Now, you create an Azure Cosmos DB account as a [serverless account type](../cos
 
     |Prompt| Selection|
     |--|--|
-    |**Select an Azure Database Server**| Choose **Core (SQL)** to create a document database that you can query by using a SQL syntax. [Learn more about the Azure Cosmos DB](../cosmos-db/introduction.md). |
+    |**Select an Azure Database Server**| Choose **Core (NoSQL)** to create a document database that you can query by using a SQL syntax or a Query Copilot ([Preview](../cosmos-db/nosql/query/how-to-enable-use-copilot.md)) converting natural language prompts to queries. [Learn more about the Azure Cosmos DB](../cosmos-db/introduction.md). |
     |**Account name**| Enter a unique name to identify your Azure Cosmos DB account. The account name can use only lowercase letters, numbers, and hyphens (-), and must be between 3 and 31 characters long.|
     |**Select a capacity model**| Select **Serverless** to create an account in [serverless](../cosmos-db/serverless.md) mode. 
     |**Select a resource group for new resources**| Choose the resource group where you created your function app in the [previous article](./create-first-function-vs-code-csharp.md). |

articles/azure-netapp-files/azure-netapp-files-performance-considerations.md

@@ -14,7 +14,7 @@ ms.author: anfdocs
 > This article addresses performance considerations for *regular volumes* only.   
 > For *large volumes*, see [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md#requirements-and-considerations). 
 
-The combination of the quota assigned to the volume and the selected service level determines the [throughput limit](azure-netapp-files-service-levels.md) for a volume with automatic QoS . For volumes with manual QoS, the throughput limit can be defined individually. When you make performance plans about Azure NetApp Files, you need to understand several considerations. 
+The combination of the quota assigned to the volume and the selected service level determines the [throughput limit](azure-netapp-files-service-levels.md) for a volume with automatic QoS. For volumes with manual QoS, the throughput limit can be defined individually. When you make performance plans about Azure NetApp Files, you need to understand several considerations. 
 
 ## Quota and throughput  
 
@@ -24,23 +24,23 @@ Typical storage performance considerations contribute to the total performance d
 
 Metrics are reported as aggregates of multiple data points collected during a five-minute interval. For more information about metrics aggregation, see [Azure Monitor Metrics aggregation and display explained](../azure-monitor/essentials/metrics-aggregation-explained.md). 
 
-The maximum empirical throughput that has been observed in testing is 4,500 MiB/s. At the Premium storage tier, an automatic QoS volume quota of 70.31 TiB will provision a throughput limit that is high enough to achieve this level of performance.  
+The maximum empirical throughput that has been observed in testing is 4,500 MiB/s. At the Premium storage tier, an automatic QoS volume quota of 70.31 TiB provisions a throughput limit high enough to achieve this performance level.  
 
-For automatic QoS volumes, if you are considering assigning volume quota amounts beyond 70.31 TiB, additional quota may be assigned to a volume for storing more data. However, the added quota doesn't result in a further increase in actual throughput.  
+For automatic QoS volumes, if you're considering assigning volume quota amounts beyond 70.31 TiB, additional quota may be assigned to a volume for storing more data. However, the added quota doesn't result in a further increase in actual throughput.  
 
 The same empirical throughput ceiling applies to volumes with manual QoS. The maximum throughput can assign to a volume is 4,500 MiB/s.
 
 ## Automatic QoS volume quota and throughput
 
-This section describes quota management and throughput for volumes with the automatic QoS type.
+Learn about quota management and throughput for volumes with the automatic QoS type.
 
 ### Overprovisioning the volume quota
 
-If a workload’s performance is throughput-limit bound, it is possible to overprovision the automatic QoS volume quota to set a higher throughput level and achieve higher performance.  
+If a workload’s performance is throughput-limit bound, it's possible to overprovision the automatic QoS volume quota to set a higher throughput level and achieve higher performance.  
 
-For example, if an automatic QoS volume in the Premium storage tier has only 500 GiB of data but requires 128 MiB/s of throughput, you can set the quota to 2 TiB so that the throughput level is set accordingly (64 MiB/s per TB * 2 TiB = 128 MiB/s).  
+For example, if an automatic QoS volume in the Premium storage tier has only 500 GiB of data but requires 128 MiB/s of throughput, you can set the quota to 2 TiB so the throughput level is set accordingly (64 MiB/s per TB * 2 TiB = 128 MiB/s).  
 
-If you consistently overprovision a volume for achieving a higher throughput, consider using the manual QoS volumes or using a higher service level instead.  In this example, you can achieve the same throughput limit with half the automatic QoS volume quota by using the Ultra storage tier instead (128 MiB/s per TiB * 1 TiB = 128 MiB/s).
+If you consistently overprovision a volume for achieving a higher throughput, consider using the manual QoS volumes or using a higher service level instead. In this example, you can achieve the same throughput limit with half the automatic QoS volume quota by using the Ultra storage tier instead (128 MiB/s per TiB * 1 TiB = 128 MiB/s).
 
 ### Dynamically increasing or decreasing volume quota
 
@@ -62,6 +62,13 @@ If your performance requirements are temporary in nature, or if you have increas
 
 If you use manual QoS volumes, you don’t have to overprovision the volume quota to achieve a higher throughput because the throughput can be assigned to each volume independently. However, you still need to ensure that the capacity pool is pre-provisioned with sufficient throughput for your performance needs. The throughput of a capacity pool is provisioned according to its size and service level. See [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md) for more details.
 
+## Monitoring volumes for performance 
+
+Azure NetApp Files volumes can be monitored using available [Performance metrics](azure-netapp-files-metrics.md#performance-metrics-for-volumes). 
+
+When volume throughput reaches its maximum (as determined by the QoS setting), the volume response times (latency) increase. This effect can be incorrectly perceived as a performance issue caused by the storage. Increasing the volume QoS setting (manual QoS) or increasing  the volume size (auto QoS) increases the allowable volume throughput. 
+
+To check if the maximum throughput limit has been reached, monitor the metric [Throughput limit reached](azure-netapp-files-metrics.md#volumes). For more recommendations, see [Performance FAQs for Azure NetApp Files](faq-performance.md#what-should-i-do-to-optimize-or-tune-azure-netapp-files-performance). 
 
 ## Next steps
 

articles/azure-netapp-files/faq-performance.md

@@ -21,6 +21,10 @@ You can take the following actions per the performance requirements:
 
 There is no need to set accelerated networking for the NICs in the dedicated subnet of Azure NetApp Files. [Accelerated networking](../virtual-network/virtual-machine-network-throughput.md) is a capability that only applies to Azure virtual machines. Azure NetApp Files NICs are optimized by design.
 
+## How do I monitor Azure NetApp Files volume performance 
+
+Azure NetApp Files volumes performance can be monitored through [available metrics](azure-netapp-files-metrics.md). 
+
 ## How do I convert throughput-based service levels of Azure NetApp Files to IOPS?
 
 You can convert MB/s to IOPS by using the following formula:  
@@ -49,11 +53,11 @@ No, Azure NetApp Files does not support SMB Direct.
 
 ## Is NIC Teaming supported in Azure?
 
-NIC Teaming is not supported in Azure. Although multiple network interfaces are supported on Azure virtual machines, they represent a logical rather than a physical construct. As such, they provide no fault tolerance.  Also, the bandwidth available to an Azure virtual machine is calculated for the machine itself and not any individual network interface.
+NIC Teaming isn't supported in Azure. Although multiple network interfaces are supported on Azure virtual machines, they represent a logical rather than a physical construct. As such, they provide no fault tolerance. Also, the bandwidth available to an Azure virtual machine is calculated for the machine itself and not any individual network interface.
 
 ## Are jumbo frames supported?
 
-Jumbo frames are not supported with Azure virtual machines.
+Jumbo frames aren't supported with Azure virtual machines.
 
 ## Next steps  
 

articles/private-multi-access-edge-compute-mec/TOC.yml

@@ -8,16 +8,6 @@
       href: overview.md
     - name: Azure Private MEC partner solutions
       href: partner-programs.md   
-  - name: Private networks using Affirmed Private Network Service
-    items:
-    - name: Overview
-      items:
-      - name: What is Affirmed Private Network Service on Azure?
-        href: affirmed-private-network-service-overview.md
-    - name: How-to guides
-      items:
-      - name: Deploy Affirmed Private Network Service on Azure
-        href: deploy-affirmed-private-network-service-solution.md
   - name: Related
     items:
     - name: Azure Network Function Manager

articles/private-multi-access-edge-compute-mec/affirmed-private-network-service-overview.md

@@ -43,18 +43,6 @@ landingContent:
           - text: Deploy a private mobile network
             url: ../private-5g-core/how-to-guide-deploy-a-private-mobile-network-azure-portal.md
 
-  # Card
-  - title: About Affirmed Private Network Service on Azure
-    linkLists:
-      - linkListType: concept
-        links:
-          - text: What is Affirmed Private Network Service on Azure?
-            url: affirmed-private-network-service-overview.md
-      - linkListType: how-to-guide
-        links:
-          - text: Deploy Affirmed Private Network Service on Azure
-            url: deploy-affirmed-private-network-service-solution.md
-
   # Card
   - title: About Azure Network Function Manager
     linkLists: