Skip to content

Commit 64db5bf

Browse files
committed
1 parent 40a7f91 commit 64db5bf

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/azure-monitor/app/availability-test-migration.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,23 +3,26 @@ title: Migrate from Azure Monitor Application Insights classic URL ping tests to
33
description: How to migrate from Azure Monitor Application Insights classic availability URL ping tests to standard tests.
44
ms.topic: conceptual
55
ms.custom: devx-track-azurepowershell
6-
ms.date: 07/19/2023
6+
ms.date: 09/27/2023
77
ms.reviewer: cogoodson
88
---
99

1010
# Migrate availability tests
1111

12-
In this article, we guide you through the process of migrating from [classic URL ping tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability) to the modern and efficient [standard tests](availability-standard-tests.md) .
12+
In this article, we guide you through the process of migrating from [classic URL ping tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability) to the modern and efficient [standard tests](availability-standard-tests.md).
1313

1414
We simplify this process by providing clear step-by-step instructions to ensure a seamless transition and equip your applications with the most up-to-date monitoring capabilities.
1515

1616
## Migrate classic URL ping tests to standard tests
1717

1818
The following steps walk you through the process of creating [standard tests](availability-standard-tests.md) that replicate the functionality of your [URL ping tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability). It allows you to more easily start using the advanced features of [standard tests](availability-standard-tests.md) using your previously created [URL ping tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability).
1919

20-
> [!NOTE]
21-
> A cost is associated with running [standard tests](availability-standard-tests.md). Once you create a [standard test](availability-standard-tests.md), you will be charged for test executions.
22-
> Refer to [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/#pricing) before starting this process.
20+
> [!IMPORTANT]
21+
>
22+
> On 30 September 2026, the **[URL ping tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability)** will be retired, and ping tests. Before that date, you'll need to transition to **[standard tests](/editor/availability-standard-tests.md)**.
23+
>
24+
> - A cost is associated with running **[standard tests](/editor/availability-standard-tests.md)**. Once you create a **[standard test](/editor/availability-standard-tests.md)**, you will be charged for test executions.
25+
> - Refer to **[Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/#pricing)** before starting this process.
2326
2427
### Prerequisites
2528

@@ -87,7 +90,6 @@ The following steps walk you through the process of creating [standard tests](av
8790
8891
We recommend using these commands to migrate a URL ping test to a standard test and take advantage of the available capabilities. Remember, this migration is optional.
8992
90-
9193
#### Do these steps work for both HTTP and HTTPS endpoints?
9294
9395
Yes, these commands work for both HTTP and HTTPS endpoints, which are used in your URL ping Tests.
@@ -98,4 +100,4 @@ Yes, these commands work for both HTTP and HTTPS endpoints, which are used in yo
98100
* [Availability alerts](availability-alerts.md)
99101
* [Troubleshooting](troubleshoot-availability.md)
100102
* [Web tests Azure Resource Manager template](/azure/templates/microsoft.insights/webtests?tabs=json)
101-
* [Web test REST API](/rest/api/application-insights/web-tests)
103+
* [Web test REST API](/rest/api/application-insights/web-tests)

0 commit comments

Comments
 (0)