Merge pull request #41255 from aaravzen/aasingh_tm_tcp

Clarify TM TCP Endpoint Probing expectations

Author: Jak-MS

articles/traffic-manager/traffic-manager-FAQs.md

@@ -413,7 +413,10 @@ Yes. You can specify TCP as the monitoring protocol and Traffic Manager can init
 
 ### What specific responses are required from the endpoint when using TCP monitoring?
 
-When TCP monitoring is used, Traffic Manager starts a three-way TCP handshake by sending a SYN request to endpoint at the specified port. It then waits for a period of time (as specified in the timeout settings) for a response from the endpoint. If the endpoint responds to the SYN request with a SYN-ACK response within the timeout period specified in the monitoring settings, then that endpoint is considered healthy. If the SYN-ACK response is received, the Traffic Manager resets the connection by responding back with a RST.
+When TCP monitoring is used, Traffic Manager starts a three-way TCP handshake by sending a SYN request to endpoint at the specified port. It then waits for a SYN-ACK response from the endpoint for a period of time (specified in the timeout settings).
+
+- If a SYN-ACK response is received within the timeout period specified in the monitoring settings, then that endpoint is considered healthy. A FIN or FIN-ACK is the expected response from the Traffic Manager when it regularly terminates a socket.
+- If a SYN-ACK response is received after the specified timeout, the Traffic Manager will respond with an RST to reset the connection.
 
 ### How fast does Traffic Manager move my users away from an unhealthy endpoint?