Skip to content

Commit ce03871

Browse files
committed
updated the migration note
1 parent fe712ec commit ce03871

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

articles/network-watcher/connection-monitor-create-using-portal.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,13 @@ ms.date: 11/30/2023
1212
---
1313
# Create a connection monitor using the Azure portal
1414

15-
This article describes how to create a monitor in Connection Monitor by using the Azure portal. Connection Monitor supports hybrid and Azure cloud deployments.
15+
This article describes how to create a monitor in Connection monitor using the Azure portal. Connection monitor supports hybrid and Azure cloud deployments.
1616

17-
> [!IMPORTANT]
18-
> As of July 1, 2021, you can no longer add new tests in an existing workspace or enable a new workspace in Network Performance Monitor. You also can no longer add new connection monitors in Connection Monitor (classic). You can continue to use the tests and connection monitors that were created prior to July 1, 2021.
19-
>
20-
> To minimize service disruption to your current workloads, [migrate your tests from Network Performance Monitor ](migrate-to-connection-monitor-from-network-performance-monitor.md) or [migrate from Connection Monitor (classic)](migrate-to-connection-monitor-from-connection-monitor-classic.md) to the new connection monitor in Azure Network Watcher before February 19, 2024.
17+
[!INCLUDE [Migrate connection monitor (classic)](../../includes/network-watcher-connection-monitor-classic.md)]
2118

2219
## Before you begin
2320

24-
In monitors that you create by using Connection Monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure Virtual Machine Scale Sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
21+
In monitors that you create by using Connection monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure Virtual Machine Scale Sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
2522

2623
Here are some definitions to get you started:
2724

@@ -219,7 +216,7 @@ Connection monitors have these scale limits:
219216
* Maximum sources and destinations per connection monitor: 100
220217
* Maximum test configurations per connection monitor: 2 via the Azure portal
221218

222-
## Next steps
219+
## Related content
223220

224221
* [Learn how to analyze monitoring data and set alerts](./connection-monitor-overview.md#analyze-monitoring-data-and-set-alerts).
225222
* [Learn how to diagnose problems in your network](./connection-monitor-overview.md#diagnose-issues-in-your-network).

0 commit comments

Comments
 (0)