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

Author: duongau

articles/azure-monitor/containers/container-insights-cost-config.md

@@ -2,8 +2,7 @@
 title: Monitoring cost for Container insights | Microsoft Docs
 description: This article describes the monitoring cost for metrics and inventory data collected by Container insights to help customers manage their usage and associated costs. 
 ms.topic: conceptual
-ms.custom: ignite-2022
-ms.date: 08/29/2022
+ms.date: 01/24/2023
 ms.reviewer: viviandiec
 ---
 # Understand monitoring costs for Container insights
@@ -24,7 +23,8 @@ The Azure Monitor pricing model is primarily based on the amount of data ingeste
 
 The following types of data collected from a Kubernetes cluster with Container insights influence cost and can be customized based on your usage:
 
-- Stdout and stderr container logs from every monitored container in every Kubernetes namespace in the cluster
+- Perf, Inventory, InsightsMetrics, and KubeEvents can be controlled through [cost optimization settings](../containers/container-insights-cost-config.md)
+- Stdout and stderr container logs from every monitored container in every Kubernetes namespace in the cluster via the [agent ConfigMap](../containers/container-insights-agent-config.md)
 - Container environment variables from every monitored container in the cluster
 - Completed Kubernetes jobs/pods in the cluster that don't require monitoring
 - Active scraping of Prometheus metrics
@@ -80,6 +80,31 @@ This workbook helps you visualize the source of your data without having to buil
 
 To learn about managing rights and permissions to the workbook, review [Access control](../visualize/workbooks-overview.md#access-control).
 
+### Determining the root cause of the data ingestion
+
+Container Insights data primarily consists of metric counters (Perf, Inventory, InsightsMetrics, and custom metrics) and logs (ContainerLog). Based on your cluster usage and size, you may have different requirements and monitoring needs.
+
+By navigating to the By Table section of the Data Usage workbook, you can see the breakdown of table sizes for Container Insights.
+
+[![Screenshot that shows the By Table breakdown in Data Usage workbook.](media/container-insights-cost/data-usage-workbook-by-table.png)](media/container-insights-cost/data-usage-workbook-by-table.png#lightbox)
+
+If the majority of your data comes from one of these following tables:
+- Perf
+- InsightsMetrics
+- ContainerInventory
+- ContainerNodeInventory	
+- KubeNodeInventory
+- KubePodInventory
+- KubePVInventory
+- KubeServices
+- KubeEvents
+
+You can adjust your ingestion using the [cost optimization settings](../containers/container-insights-cost-config.md) and/or migrating to the Prometheus metrics addon (../essentials/prometheus-metrics-overview.md)
+
+Otherwise, the majority of your data belongs to the ContainerLog table. and you can follow the steps below to reduce your ContainerLog costs.
+
+### Reducing your ContainerLog costs
+
 After you finish your analysis to determine which sources are generating the data that's exceeding your requirements, you can reconfigure data collection. For more information on configuring collection of stdout, stderr, and environmental variables, see [Configure agent data collection settings](container-insights-agent-config.md).
 
 The following examples show what changes you can apply to your cluster by modifying the ConfigMap file to help control cost.
@@ -123,6 +148,12 @@ The following examples show what changes you can apply to your cluster by modify
 
 After you apply one or more of these changes to your ConfigMaps, apply it to your cluster with the command `kubectl apply -f <config3. map_yaml_file.yaml>`. For example, run the command `kubectl apply -f container-azm-ms-agentconfig.yaml` to open the file in your default editor to modify and then save it.
 
+### Configure Basic Logs
+
+You can save on data ingestion costs on ContainerLog in your Log Analytics workspace that you primarily use for debugging, troubleshooting, and auditing as Basic Logs. For more information, including the limitations of Basic Logs, see [Configure Basic Logs in Azure Monitor](../logs/basic-logs-configure.md). ContainerLogV2 is the configured version of Basic Logs that Container Insights uses. ContainerLogV2 includes verbose text-based log records.
+
+You must be on the ContainerLogV2 schema to configure Basic Logs. For more information, see [Enable the ContainerLogV2 schema (preview)](container-insights-logging-v2.md).
+
 ### Prometheus metrics scraping
 
 If you use [Prometheus metric scraping](container-insights-prometheus.md), make sure that you limit the number of metrics you collect from your cluster:
@@ -131,12 +162,6 @@ If you use [Prometheus metric scraping](container-insights-prometheus.md), make
 - Container insights supports exclusion and inclusion lists by metric name. For example, if you're scraping **kubedns** metrics in your cluster, hundreds of them might get scraped by default. But you're most likely only interested in a subset of the metrics. Confirm that you specified a list of metrics to scrape, or exclude others except for a few to save on data ingestion volume. It's easy to enable scraping and not use many of those metrics, which will only add charges to your Log Analytics bill.
 - When you scrape through pod annotations, ensure you filter by namespace so that you exclude scraping of pod metrics from namespaces that you don't use. An example is the `dev-test` namespace.
 
-### Configure Basic Logs
-
-You can save on data ingestion costs by configuring certain tables in your Log Analytics workspace that you primarily use for debugging, troubleshooting, and auditing as Basic Logs. For more information, including the limitations of Basic Logs, see [Configure Basic Logs in Azure Monitor](../logs/basic-logs-configure.md). ContainerLogV2 is the configured version of Basic Logs that Container Insights uses. ContainerLogV2 includes verbose text-based log records.
-
-You must be on the ContainerLogV2 schema to configure Basic Logs. For more information, see [Enable the ContainerLogV2 schema (preview)](container-insights-logging-v2.md).
-
 ## Data collected from Kubernetes clusters
 
 ### Metric data

articles/azure-monitor/containers/container-insights-cost.md

@@ -97,7 +97,7 @@ For Profiler to work properly, make sure:
 
       :::image type="content" source="./media/profiler-troubleshooting/profiler-web-job-log.png" alt-text="Screenshot of the Continuous WebJob Details pane.":::
 
-If Profiler still isn't working for you, you can download the log and [send it to our team](mailto:serviceprofilerhelp@microsoft.com).
+If Profiler still isn't working for you, you can download the log and [submit an Azure support ticket](https://azure.microsoft.com/support/).
 
 #### Check the Diagnostic Services site extension' status page
 

articles/azure-monitor/containers/media/container-insights-cost/data-usage-workbook-by-table.png

@@ -960,6 +960,8 @@ items:
         href: containers/container-insights-agent-config.md
       - name: Enable ContainerLogv2 (preview)
         href: containers/container-insights-logging-v2.md
+      - name: Enable cost optimization settings (preview)
+        href: containers/container-insights-cost-config.md
     - name: Monitor
       items:
       - name: Monitor performance

articles/azure-monitor/profiler/profiler-troubleshooting.md

@@ -21,6 +21,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## February 2023
 
+* The `Vaults` API is deprecated starting with Azure NetApp Files REST API version 2022-09-01.  
+
+    Enabling backup of volumes doesn't require the `Vaults` API. REST API users can use `PUT` and `PATCH` [Volumes API](/rest/api/netapp/volumes) to enable backup for a volume.
+    
 * [Volume user and group quotas](default-individual-user-group-quotas-introduction.md) (Preview)
 
     Azure NetApp Files volumes provide flexible, large and scalable storage shares for applications and users. Storage capacity and consumption by users is only limited by the size of the volume. In some scenarios, you may want to limit this storage consumption of users and groups within the volume. With Azure NetApp Files volume user and group quotas, you can now do so. User and/or group quotas enable you to restrict the storage space that a user or group can use within a specific Azure NetApp Files volume. You can choose to set default (same for all users) or individual user quotas on all NFS, SMB, and dual protocol-enabled volumes. On all NFS-enabled volumes, you can set default (same for all users) or individual group quotas.

articles/azure-monitor/toc.yml

@@ -12,11 +12,6 @@ ms.custom: devx-track-azurecli
 
 Learn how to use Azure CLI with [Azure Resource Manager](overview.md) to manage your Azure resource groups. For managing Azure resources, see [Manage Azure resources by using Azure CLI](manage-resources-cli.md).
 
-Other articles about managing resource groups:
-
-- [Manage Azure resource groups by using the Azure portal](manage-resources-portal.md)
-- [Manage Azure resource groups by using Azure PowerShell](manage-resources-powershell.md)
-
 ## What is a resource group
 
 A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to add resources to resource groups based on what makes the most sense for your organization. Generally, add resources that share the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group.

articles/azure-netapp-files/whats-new.md

@@ -10,11 +10,6 @@ ms.author: jgao
 
 Learn how to use the [Azure portal](https://portal.azure.com) with [Azure Resource Manager](overview.md) to manage your Azure resource groups. For managing Azure resources, see [Manage Azure resources by using the Azure portal](manage-resources-portal.md).
 
-Other articles about managing resource groups:
-
-- [Manage Azure resource groups by using Azure CLI](manage-resources-cli.md)
-- [Manage Azure resource groups by using Azure PowerShell](manage-resources-powershell.md)
-
 [!INCLUDE [Handle personal data](../../../includes/gdpr-intro-sentence.md)]
 
 ## What is a resource group

articles/azure-resource-manager/management/manage-resource-groups-cli.md

@@ -12,11 +12,6 @@ ms.custom: devx-track-azurepowershell
 
 Learn how to use Azure PowerShell with [Azure Resource Manager](overview.md) to manage your Azure resource groups. For managing Azure resources, see [Manage Azure resources by using Azure PowerShell](manage-resources-powershell.md).
 
-Other articles about managing resource groups:
-
-- [Manage Azure resource groups by using the Azure portal](manage-resources-portal.md)
-- [Manage Azure resource groups by using Azure CLI](manage-resources-cli.md)
-
 ## What is a resource group
 
 A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to add resources to resource groups based on what makes the most sense for your organization. Generally, add resources that share the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group.
@@ -77,7 +72,7 @@ For more information about deploying a Bicep file, see [Deploy resources with Bi
 
 ## Lock resource groups
 
-Locking prevents other users in your organization from accidentally deleting or modifying critical resources.. 
+Locking prevents other users in your organization from accidentally deleting or modifying critical resources. 
 
 To prevent a resource group and its resources from being deleted, use [New-AzResourceLock](/powershell/module/az.resources/new-azresourcelock).
 

articles/azure-resource-manager/management/manage-resource-groups-portal.md

@@ -1,5 +1,6 @@
 ---
 title: Understand Azure IoT Hub message routing
+titleSuffix: Azure IoT Hub
 description: This article describes how to use message routing to send device-to-cloud messages. Includes information about sending both telemetry and non-telemetry data.
 author: kgremban
 ms.service: iot-hub
@@ -109,6 +110,12 @@ You can configure the synthetic partition key value by specifying a template in
 > [!CAUTION]
 > If you're using the system assigned managed identity for authenticating to Cosmos DB, you must use Azure CLI or Azure PowerShell to assign the Cosmos DB Built-in Data Contributor built-in role definition to the identity. Role assignment for Cosmos DB isn't currently supported from the Azure portal. For more information about the various roles, see [Configure role-based access for Azure Cosmos DB](../cosmos-db/how-to-setup-rbac.md). To understand assigning roles via CLI, see [Manage Azure Cosmos DB SQL role resources.](/cli/azure/cosmosdb/sql/role)
 
+## Route to an endpoint in another subscription
+
+If the endpoint resource is in a different subscription than your IoT hub, you need to configure your IoT hub as a trusted Microsoft service before creating a custom endpoint. When you do create the custom endpoint, set the **Authentication type** to user-assigned identity.
+
+For more information, see [Egress connectivity from IoT Hub to other Azure resources](./iot-hub-managed-identity.md#egress-connectivity-from-iot-hub-to-other-azure-resources).
+
 ## Routing queries
 
 IoT Hub message routing provides a querying capability to filter the data before routing it to the endpoints. Each routing query you configure has the following properties: