Merge pull request #265889 from duongau/retirementnote

Azure Internet Analyzer retirement notice

Author: v-shils

articles/internet-analyzer/internet-analyzer-cli.md

@@ -13,6 +13,8 @@ ms.author: kumud
 ---
 # Create an Internet Analyzer test using CLI (Preview)
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 There are two ways to create an Internet Analyzer resource - using the [Azure portal](internet-analyzer-create-test-portal.md) or using CLI. This section helps you create a new Azure Internet Analyzer resource using our CLI experience. 
 
 

articles/internet-analyzer/internet-analyzer-create-test-portal.md

@@ -13,6 +13,8 @@ ms.author: kumud
 ---
 # Create an Internet Analyzer test using Portal (Preview)
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 There are two ways to create an Internet Analyzer resource- using the Azure portal or using [CLI](internet-analyzer-cli.md). This section helps you create a new Azure Internet Analyzer resource using our portal experience.
 
 > [!IMPORTANT]

articles/internet-analyzer/internet-analyzer-custom-endpoint.md

@@ -14,6 +14,8 @@ ms.author: kumud
 
 # Measure custom endpoints to evaluate in your Internet Analyzer tests 
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 This article demonstrates how to set up a custom endpoint to measure as part of your Internet Analyzer tests. Custom endpoints help evaluate on-premises workloads, workloads running on other cloud providers, and custom Azure configurations.  Comparing two custom endpoints in one test is possible if one endpoint is an Azure resource. For more information on Internet Analyzer, see the [overview](internet-analyzer-overview.md). 
 
 > [!IMPORTANT]

articles/internet-analyzer/internet-analyzer-embed-client.md

@@ -14,6 +14,8 @@ ms.author: kumud
 
 # Embed the Internet Analyzer client
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 This article shows you how to embed the JavaScript client in your application. Installation of this client is necessary to run tests and receive scorecard analytics. **The profile-specific JavaScript client is provided after the first test has been configured.** From there, you may continue to add or remove tests to that profile without having to embed a new script. For more information on Internet Analyzer, see the [overview](internet-analyzer-overview.md). 
 
 > [!IMPORTANT]

articles/internet-analyzer/internet-analyzer-faq.md

@@ -11,21 +11,9 @@ ms.author: kumud
 ---
 # Azure Internet Analyzer FAQ (Preview)
 
-This is the FAQ for Azure Internet Analyzer- if you have additional questions, go to the [feedback forum](https://aka.ms/internetAnalyzerFeedbackForum) and post your question. When a question is frequently asked, we add it to this article so it can be found quickly and easily.
-
-## How do I participate in the preview?
-
-The preview is available to select customers. If you are interested in joining the preview, please do the following:
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Navigate to the **Subscriptions** page.
-3. Click on the Azure subscription that you plan to use Internet Analyzer with.
-4. Go to the **Resource providers** settings for the subscription.
-5. Search for **Microsoft.Network** and click on the **Register** (or **Re-register**) button.
-![access request](./media/ia-faq/request-preview-access.png)
-
-6. [Request approval](https://aka.ms/internetAnalyzerContact) by providing us your email address and the Azure subscription ID that was used to make the access request.
-7. Once your request has been approved, you will receive an email confirmation and will be able to create/update/modify Internet Analyzer resources from the newly allowed Azure subscription.
+This is the FAQ for Azure Internet Analyzer- if you have additional questions, go to the [feedback forum](https://aka.ms/internetAnalyzerFeedbackForum) and post your question. When a question is frequently asked, we add it to this article so it can be found quickly and easily.
 
 ## Do I need to embed the client to run a test?
 

articles/internet-analyzer/internet-analyzer-overview.md

@@ -13,6 +13,8 @@ ms.author: kumud
 ---
 # What is Internet Analyzer? (Preview)
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 Internet Analyzer is a client-side measurement platform to test how networking infrastructure changes impact your customers’ performance. Whether you’re migrating from on-premises to Azure or evaluating a new Azure service, Internet Analyzer allows you to learn from your users’ data and Microsoft’s rich analytics to better understand and optimize your network architecture with Azure—before you migrate.
 
 Internet Analyzer uses a small JavaScript client embedded in your Web application to measure the latency from your end users to your selected set of network destinations, we call _endpoints_. Internet Analyzer allows you to set up multiple side-by-side tests, allowing you to evaluate a variety of scenarios as your infrastructure and customer needs evolves. Internet Analyzer provides custom and preconfigured endpoints, providing you both the convenience and flexibility to make trusted performance decisions for your end users. 

articles/internet-analyzer/internet-analyzer-scorecard.md

@@ -11,33 +11,35 @@ ms.author: kumud
 ---
 # Interpreting your scorecard
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 The scorecard tab contains the aggregated and analyzed results from your tests. Each test has its own scorecards. Scorecards provide quick and meaningful summaries of measurement results to provide data-driven results for your networking requirements. Internet Analyzer takes care of the analysis, allowing you to focus on the decision.
 
 The scorecard tab can be found in the Internet Analyzer resource menu. 
 
 
 ## Filters
 
-* ***Test:*** Select the test that you’d like to view results for - each test has its own scorecard. Test data will appear once there is enough data to complete the analysis – in most cases, this should be within 24 hours. 
+* ***Test:*** Select the test that you’d like to view results for - each test has its own scorecard. Test data will appear once there's enough data to complete the analysis – in most cases, this should be within 24 hours. 
 * ***Time period & end date:*** Three scorecards are generated daily – each scorecard reflects a different aggregation period – the 24 hours prior (day), the seven days prior (week), and the 30 days prior (month). Use the “End Date” filter to select the last day of the time period you want to see. 
 * ***Country:*** For each country that you have end users, a scorecard is generated. The global filter contains all end users.
 
 ## Measurement count
 
-The number of measurements impacts the confidence of the analysis. The higher the count, the more accurate the result. At minimum, tests should aim for a minimum of 100 measurements per endpoint per day. If measurement counts are too low, please configure the JavaScript client to execute more frequently in your application. The measurement counts for endpoints A and B should be very similar although small differences are expected and okay. In the case of large differences, the results should not be trusted.
+The number of measurements impacts the confidence of the analysis. The higher the count, the more accurate the result. At minimum, tests should aim for a minimum of 100 measurements per endpoint per day. If measurement counts are too low, please configure the JavaScript client to execute more frequently in your application. The measurement counts for endpoints A and B should be very similar although small differences are expected and okay. In the case of large differences, the results shouldn't be trusted.
 
 ## Percentiles
 
-Latency, measured in milliseconds, is a popular metric for measuring speed between a source and destination on the Internet. Latency data is not normally distributed (i.e. does not follow a "Bell Curve") because there is a "long-tail" of large latency values that skew results when using statistics such as the arithmetic mean. As an alternative, percentiles provide a "distribution-free" way to analyze data. As an example, the median, or 50th percentile, summarizes the middle of the distribution - half the values are above it and half are below it. A 75th percentile value means it is larger than 75% of all values in the distribution. Internet Analyzer refers to percentiles in shorthand as P50, P75, and P95.
+Latency, measured in milliseconds, is a popular metric for measuring speed between a source and destination on the Internet. Latency data isn't normally distributed (i.e. doesn't follow a "Bell Curve") because there's a "long-tail" of large latency values that skew results when using statistics such as the arithmetic mean. As an alternative, percentiles provide a "distribution-free" way to analyze data. As an example, the median, or 50th percentile, summarizes the middle of the distribution - half the values are above it and half are below it. A 75th percentile value means it's larger than 75% of all values in the distribution. Internet Analyzer refers to percentiles in shorthand as P50, P75, and P95.
 
 Internet Analyzer percentiles are _sample metrics_. This is in contrast to the true _population metric_. For example, the daily true population median latency between students at the University of Southern California and Microsoft is the median latency value of all requests during that day. In practice, measuring the value of all requests is impractical, so we assume that a reasonably large sample is representative of the true population.
 
-For analysis purposes, P50 (median), is useful as an expected value for a latency distribution. Higher percentiles, such as P95, are useful for identifying how high latency is in the worst cases. If you are interested in understanding customer latency in general, P50 is the correct metric to focus on. If you are concerned with understanding performance for the worst-performing customers, then P95 should be the focus. P75 is a balance between these two.
+For analysis purposes, P50 (median), is useful as an expected value for a latency distribution. Higher percentiles, such as P95, are useful for identifying how high latency is in the worst cases. If you're interested in understanding customer latency in general, P50 is the correct metric to focus on. If you're concerned with understanding performance for the worst-performing customers, then P95 should be the focus. P75 is a balance between these two.
 
 
 ## Deltas
 
-A delta is the difference in metric values for endpoints A and B. Deltas are computed to show the benefit of B over A. Positive values indicate B performed better than A, whereas negative values indicate B's performance is worse. Deltas can be absolute (e.g. 10 milliseconds) or relative (5%).
+A delta is the difference in metric values for endpoints A and B. Deltas are computed to show the benefit of B over A. Positive values indicate B performed better than A, whereas negative values indicate B's performance is worse. Deltas can be absolute (for example, 10 milliseconds) or relative (5%).
 
 ## Confidence interval 
 

articles/internet-analyzer/troubleshoot.md

@@ -11,11 +11,13 @@ ms.author: dibotero
 ---
 # Azure Internet Analyzer troubleshooting
 
+[!INCLUDE [Azure Internet Analyzer retirement notice](../../includes/internet-analyzer-retirement.md)]
+
 This article contains troubleshooting steps for common Internet Analyzer issues.
 
 ## Things to keep in mind
 - The client script must be embedded into an **HTTPS** website. Measurements won't be collected if the script runs in a plaintext (**http://**) or local (**file://**) website.
-- Measurement data will only be collected if the Internet Analyzer profile's client script has been embedded into an application that is receiving real user traffic. Synthetic traffic (for example, Azure WebApp Performance Tests) does not typically execute embedded JavaScript code, so no measurements will be generated by that type of traffic.
+- Measurement data will only be collected if the Internet Analyzer profile's client script has been embedded into an application that is receiving real user traffic. Synthetic traffic (for example, Azure WebApp Performance Tests) doesn't typically execute embedded JavaScript code, so no measurements will be generated by that type of traffic.
 
 ## Azure portal
 **"A scorecard hasn't been generated for the selected filter combination" in the Scorecards section**
@@ -24,7 +26,7 @@ This article contains troubleshooting steps for common Internet Analyzer issues.
 
 **"Total Measurement Count" is zero for one or both endpoints in a test**
 - Time series and measurement counts are computed once an hour, so you'll need to wait at least that amount of time for new measurement data to show up.
-- Internet Analyzer only counts successful measurements (i.e., HTTP 200 responses) for its analysis. If one or both endpoints in a test are unreachable or returning a non-200 HTTP code, they will show up with zero total measurements.
+- Internet Analyzer only counts successful measurements (i.e., HTTP 200 responses) for its analysis. If one or both endpoints in a test are unreachable or returning a non-200 HTTP code, they'll show up with zero total measurements.
 
 ## Next steps
 Read the [Internet Analyzer FAQ](internet-analyzer-faq.md)

includes/internet-analyzer-retirement.md

@@ -0,0 +1,13 @@
+---
+ title: Internet Analyzer retirement notice
+ description: include file
+ services: internet-analyzer
+ author: duongau
+ ms.service: internet-analyzer
+ ms.topic: include
+ ms.date: 02/09/2024
+ ms.author: duau
+ ms.custom: include file
+---
+> [!IMPORTANT]
+> Azure Internet Analyzer will be retired on **March 15, 2024**. To avoid any service disruption, it is important that you delete your Azure Internet Analyzer profiles and tests by March 2024. For detailed information, see [**Azure Internet Analyzer retirement**](https://azure.microsoft.com/updates/azure-internet-analyzer-will-be-retired-on-15-march-2024-delete-profiles/).