Skip to content

Commit 13edbd0

Browse files
incorporating author feedback
1 parent 28d31c7 commit 13edbd0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/network-watcher/connection-monitor-2-preview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ For more information, see [Enable Network Watcher](https://docs.microsoft.com/az
8181

8282
## Create a connection monitor
8383

84-
Connection Monitor monitors communication at regular intervals. It informs you of changes in reachability and latency, and network topology between source agents and destination endpoints.
84+
Connection Monitor monitors communication at regular intervals. It informs you of changes in reachability and latency. You can also check the current and historical network topology between source agents and destination endpoints.
8585

8686
Sources can be Azure VMs or on-premises machines that have an installed monitoring agent. Destination endpoints can be Office 365 URLs, Dynamics 365 URLs, custom URLs, Azure VM resource IDs, IPv4, IPv6, FQDN, or any domain name.
8787

@@ -98,7 +98,7 @@ Sources can be Azure VMs or on-premises machines that have an installed monitori
9898

9999
In connection monitors that you create in Connection Monitor (Preview), you can add both on-premises machines and Azure VMs as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or any other URL or IP.
100100

101-
A Connection Monitor solution includes the following entities:
101+
Connection Monitor (Preview) includes the following entities:
102102

103103
* **Connection monitor resource** – A region-specific Azure resource. All of the following entities are properties of a connection monitor resource.
104104
* **Endpoint** – A source or destination that participates in connectivity checks. Examples of endpoints include Azure VMs, on-premises agents, URLs, and IPs.

0 commit comments

Comments
 (0)