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

Author: duongau

articles/azure-functions/functions-reference-python.md

@@ -1482,7 +1482,7 @@ To view the library for your Python version, go to:
 
 ### Azure Functions Python worker dependencies
 
-The Azure Functions Python worker requires a specific set of libraries. You can also use these libraries in your functions, but they aren't a part of the Python standard. If your functions rely on any of these libraries, they might be unavailable to your code when it's running outside of Azure Functions. You'll find a detailed list of dependencies in the "install\_requires" section of the [*setup.py*](https://github.com/Azure/azure-functions-python-worker/blob/dev/setup.py#L282) file.
+The Azure Functions Python worker requires a specific set of libraries. You can also use these libraries in your functions, but they aren't a part of the Python standard. If your functions rely on any of these libraries, they might be unavailable to your code when it's running outside of Azure Functions.
 
 > [!NOTE]
 > If your function app's *requirements.txt* file contains an `azure-functions-worker` entry, remove it. The functions worker is automatically managed by the Azure Functions platform, and we regularly update it with new features and bug fixes. Manually installing an old version of worker in the *requirements.txt* file might cause unexpected issues.

articles/azure-monitor/app/codeless-overview.md

@@ -3,15 +3,22 @@ title: Autoinstrumentation for Azure Monitor Application Insights
 description: Overview of autoinstrumentation for Azure Monitor Application Insights codeless application performance management.
 ms.topic: conceptual
 ms.custom: devx-track-js
-ms.date: 12/15/2023
+ms.date: 08/12/2024
 ms.reviewer: abinetabate
 ---
 
 # What is autoinstrumentation for Azure Monitor Application Insights?
 
 Autoinstrumentation enables [Application Insights](app-insights-overview.md) to make [telemetry](data-model-complete.md) like metrics, requests, and dependencies available in your [Application Insights resource](create-workspace-resource.md). It provides easy access to experiences such as the [application dashboard](overview-dashboard.md) and [application map](app-map.md).
 
-If your language and platform are supported, select the corresponding link in the [Supported environments, languages, and resource providers table](#supported-environments-languages-and-resource-providers) for more detailed information. In many cases, autoinstrumentation is enabled by default.
+The term "autoinstrumentation" is a portmanteau, a linguistic blend where parts of multiple words combine into a new word. "Autoinstrumentation" combines "auto" and "instrumentation." It sees widespread use in software observability and describes the process of adding instrumentation code to applications without manual coding by developers.
+
+The autoinstrumentation process varies by language and platform, but often involves a toggle button in the Azure portal. The following example shows a toggle button for [Azure App Service](../../app-service/getting-started.md#getting-started-with-azure-app-service) autoinstrumentation.
+
+:::image type="content"source="./media/azure-web-apps/enable.png" alt-text=" Screenshot that shows the Application Insights tab with Enable selected." lightbox="./media/azure-web-apps/enable.png":::
+
+> [!TIP]
+> *We do not provide autoinstrumentation specifics for all languages and platforms in this article.* For detailed information, select the corresponding link in the [Supported environments, languages, and resource providers table](#supported-environments-languages-and-resource-providers). In many cases, autoinstrumentation is enabled by default.
 
 ## What are the autoinstrumentation advantages?
 
@@ -28,7 +35,7 @@ The following table shows the current state of autoinstrumentation availability.
 Links are provided to more information for each supported scenario.
 
 > [!NOTE]
-> If your hosting environment or resource provider is not listed in the following table, autoinstrumentation is not supported. You can manually instrument your code using Application Insights SDKs or Azure Monitor OpenTelemetry Distros. For more information, see [Data Collection Basics of Azure Monitor Application Insights](opentelemetry-overview.md).
+> If your hosting environment or resource provider is not listed in the following table, then autoinstrumentation is not supported. In this case, we recoomend manually instrumenting using the [Azure Monitor OpenTelemetry Distro](opentelemetry-enable.md). For more information, see [Data Collection Basics of Azure Monitor Application Insights](opentelemetry-overview.md).
 
 |Environment/Resource provider                    | .NET Framework                                                                                                                                        | .NET Core / .NET                                                                                                                                      | Java                                                                                                                                                      | Node.js                                                                                                                                                                                      | Python                                                                                           |
 |-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|
@@ -52,18 +59,13 @@ Links are provided to more information for each supported scenario.
 > [!NOTE]
 > Autoinstrumentation was known as "codeless attach" before October 2021.
 
-## JavaScript (Web) SDK Loader Script injection by configuration
-
-When using supported Software Development Kits (SDKs), you can enable SDK injection in configuration to automatically inject JavaScript (Web) SDK Loader Script onto each page.
+## Frequently asked questions
 
+#### Should the term "autoinstrumentation" be hyphenated?
 
-   | Language   
-   |	:---	|
-   | [ASP.NET Core](./asp-net-core.md?tabs=netcorenew%2Cnetcore6#enable-client-side-telemetry-for-web-applications) |
-   | [Node.js](./nodejs.md#browser-sdk-loader) |
-   | [Java](./java-standalone-config.md#browser-sdk-loader-preview) |
+We follow the [Microsoft Style Guide](/style-guide/punctuation/dashes-hyphens/hyphens#prefixes) for product documentation published to the [Microsoft Learn](/) platform.
 
-For other methods to instrument your application with the Application Insights JavaScript SDK, see [Get started with the JavaScript SDK](./javascript-sdk.md).
+In general, we don’t include a hyphen after the "auto" prefix.
 
 ## Next steps
 

articles/azure-monitor/app/javascript-sdk.md

@@ -34,7 +34,11 @@ We provide the [Debug plugin](https://github.com/microsoft/ApplicationInsights-J
 Follow the steps in this section to instrument your application with the Application Insights JavaScript SDK.
 
 > [!TIP] 
-> Good news! We're making it even easier to enable JavaScript. Check out where [JavaScript (Web) SDK Loader Script injection by configuration is available](./codeless-overview.md#javascript-web-sdk-loader-script-injection-by-configuration)!
+> Good news! We're making it even easier to enable JavaScript with JavaScript (Web) SDK Loader Script injection by configuration.
+> 
+> - [ASP.NET Core](./asp-net-core.md?tabs=netcorenew%2Cnetcore6#enable-client-side-telemetry-for-web-applications)
+> - [Node.js](./nodejs.md#browser-sdk-loader)
+> - [Java](./java-standalone-config.md#browser-sdk-loader-preview)
 
 ### Add the JavaScript code
 

articles/azure-monitor/includes/azure-monitor-app-insights-opentelemetry-faqs.md

@@ -101,8 +101,8 @@ The following chart breaks out OpenTelemetry feature support for each language.
 | Filter requests, dependencies, logs, and exceptions by anonymous user ID and synthetic source                         | :x:                | :x:                | :x:                | :white_check_mark: |
 | Filter dependencies, logs, and exceptions by operation name                                                           | :x:                | :x:                | :x:                | :white_check_mark: |
 | [Adaptive sampling](../app/sampling.md#adaptive-sampling)                                                             | :x:                | :x:                | :x:                | :white_check_mark: |
-| [Profiler](../profiler/profiler-overview.md)                                                                          | :white_check_mark: | :x:                | :x:                | :warning:          |
-| [Snapshot Debugger](../snapshot-debugger/snapshot-debugger.md)                                                        | :white_check_mark: | :x:                | :x:                | :x:                |
+| [Profiler](../profiler/profiler-overview.md)                                                                          | :x:                | :x:                | :x:                | :warning:          |
+| [Snapshot Debugger](../snapshot-debugger/snapshot-debugger.md)                                                        | :x:                | :x:                | :x:                | :x:                |
 
 **Key**
 - :white_check_mark: This feature is available to all customers with formal support.

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

@@ -63,20 +63,38 @@ You can create an Azure support request to increase the adjustable limits from t
 >[!NOTE]
 > Depending on available resources in the region and the limit increase requested, Azure support may require additional information in order to determine the feasibility of the request.
 
-1. Go to **New Support Request** under **Support + troubleshooting**.   
+1. Navigate to **Help** then **Support + troubleshooting**.   
+1. Under the **How can we help you** heading, enter "regional capacity quota" in the text field then select **Go**. 
 
-2. Under the **Problem description** tab, provide the required information:
+    :::image type="content" source="./media/azure-netapp-files-resource-limits/support-how-can-we-help.png" alt-text="Screenshot that shows the How can we help heading." lightbox="./media/azure-netapp-files-resource-limits/support-how-can-we-help.png":::
+    
+    1. Under the **Current selection** heading, search for "Azure NetApp Files" in the text field for **Which service are you having an issue with?**.
+    1. Select **Azure NetApp Files** then **Next**. 
+
+        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-service.png" alt-text="Screenshot of choosing a service option." lightbox="./media/azure-netapp-files-resource-limits/support-service.png":::
+    
+    1. Under **Which resource are you having an issue with?**, locate and select your subscription. Then locate and select your resource (the NetApp account).
+    
+        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-resource.png" alt-text="Screenshot with the option to select your subscription and resource." lightbox="./media/azure-netapp-files-resource-limits/support-resource.png":::
+    
+    1. Under **Are you having one of the following issues?**, select **Storage: Azure NetApp Files limits** then **Next**.
+    
+        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-issue.png" alt-text="Screenshot showing the option to choose Azure NetApp Files limits as an issue." lightbox="./media/azure-netapp-files-resource-limits/support-issue.png":::
+    
+    1. Select **Create a support request**. 
+
+1. Under the **Problem description** tab, provide the required information:
     1. For **Issue Type**, select **Service and Subscription Limits (Quotas)**.
     2. For **Subscription**, select your subscription. 
     3. For **Quota Type**, select **Storage: Azure NetApp Files limits**.  
 
     ![Screenshot that shows the Problem Description tab.](./media/shared/support-problem-descriptions.png)
-
-3. Under the **Additional details** tab, select **Enter details** in the Request Details field.  
+    
+1. Under the **Additional details** tab, select **Enter details** in the Request Details field.  
 
     ![Screenshot that shows the Details tab and the Enter Details field.](./media/shared/quota-additional-details.png)
 
-4. To request limit increase, provide the following information in the Quota Details window that appears:
+1. To request limit increase, provide the following information in the Quota Details window that appears:
     1. In **Quota Type**, select the type of resource you want to increase.  
         For example:   
         * *Regional Capacity Quota per Subscription (TiB)*
@@ -90,7 +108,7 @@ You can create an Azure support request to increase the adjustable limits from t
 
     ![Screenshot that shows how to display and request increase for regional quota.](./media/azure-netapp-files-resource-limits/quota-details-regional-request.png)
 
-5. Select **Save and continue**. Select **Review + create** to create the request.
+1. Select **Save and continue**. Select **Review + create** to create the request.
 
 ## Next steps  
 

articles/azure-netapp-files/media/azure-netapp-files-resource-limits/support-how-can-we-help.png

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
 description: This article helps you better understand data included in Cost Management. It also explains how frequently data is processed, collected, shown, and closed.
 author: bandersmsft
 ms.author: banders
-ms.date: 06/04/2024
+ms.date: 08/12/2024
 ms.topic: conceptual
 ms.service: cost-management-billing
 ms.subservice: cost-management
@@ -13,7 +13,7 @@ ms.reviewer: micflan
 
 # Understand Cost Management data
 
-This article helps you better understand Azure cost and usage data included in Cost Management. It explains how frequently data is processed, collected, shown, and closed. You're billed for Azure usage monthly. Although billing cycles are monthly periods, cycle start and end dates vary by subscription type. How often Cost Management receives usage data varies based on different factors. Such factors include how long it takes to process the data and how frequently Azure services emit usage to the billing system.
+This article helps you better understand Azure cost and usage data included in Cost Management. It explains how frequently data is processed, collected, shown, and closed. You receive a bill for your Azure usage each month. Although billing cycles are monthly periods, cycle start and end dates vary by subscription type. How often Cost Management receives usage data varies based on different factors. Such factors include how long it takes to process the data and how frequently Azure services emit usage to the billing system.
 
 Cost Management includes all usage and purchases, including commitment discounts (that is, reservations and savings plans) and third-party offerings, for Enterprise Agreement (EA) and Microsoft Customer Agreement (MCA) accounts. Microsoft Online Services Agreement (MOSA) accounts only include usage from Azure and Marketplace services with applicable commitment discounts applied but don't include Marketplace or commitment discounts purchases. Support and other costs aren't included. Costs are estimated until an invoice is generated and don't factor in credits. Cost Management also includes costs associated with New Commerce products like Microsoft 365 and Dynamics 365 that are invoiced along with Azure.
 
@@ -161,7 +161,14 @@ Costs shown in Cost Management are rounded. Costs returned by the Query API aren
 
 ## Historical data might not match invoice
 
-Historical data for credit-based and pay-in-advance offers might not match your invoice. Some Azure pay-as-you-go, MSDN, and Visual Studio offers can have Azure credits and advanced payments applied to the invoice. The historical data shown in Cost Management is based on your estimated consumption charges only. Cost Management historical data doesn't include payments and credits. Historical data shown for the following offers might not match exactly with your invoice.
+Historical data for credit-based and pay-in-advance offers might not match your invoice. Some Azure pay-as-you-go, MSDN, and Visual Studio offers can have Azure credits and advanced payments applied to the invoice. The historical data (closed month data) shown in Cost Management is based on your estimated consumption charges only. For the following listed offers, Cost Management historical data doesn't include payments and credits. Additionally, price changes might affect it. *The price shown on your invoice might differ from the price used for cost estimation.*
+
+For example, you get invoiced on January 5 for a service consumed in the month of December. It has a price of $86 per unit. On January 1, the unit price changed to $100. When you view your estimated charges in Cost Management, you see that your cost is the result of your consumed quantity * $100 (not $86, as shown in your  invoice).
+
+>[!NOTE]
+>The price change might result in a a price decrease, not only an increase, as explained in this example.
+
+Historical data shown for the following offers might not match exactly with your invoice.
 
 - Azure for Students (MS-AZR-0170P)
 - Azure in Open (MS-AZR-0111P)