Skip to content

Commit 09b9edb

Browse files
committed
Fix typo
HTTPs -> HTTPS
1 parent 925fe3b commit 09b9edb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/load-balancer/manage-probes-how-to.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Health probes have the following properties:
2929
| Port | Port of the health probe. The destination port you would like the health probe to use when it connects to the virtual machine to check the virtual machine's health status. You must ensure that the virtual machine is also listening on this port (that is, the port is open). |
3030
| Interval (seconds) | Interval of health probe. The amount of time (in seconds) between consecutive health check attempts to the virtual machine |
3131
| Used by | The list of load balancer rules using this specific health probe. You should have at least one rule using the health probe for it to be effective |
32-
| Path | The URI used for requesting health status from the virtual machine instance by the health probe (only applicable for HTTPs probes).
32+
| Path | The URI used for requesting health status from the virtual machine instance by the health probe (only applicable for HTTPS probes).
3333

3434
>[!IMPORTANT]
3535
>Load Balancer health probes originate from the IP address 168.63.129.16 and must not be blocked for probes to mark your instance as up. To see this probe traffic within your backend instance, review [the Azure Load Balancer FAQ](./load-balancer-faqs.yml).

0 commit comments

Comments
 (0)