Merge pull request #103890 from anavinahar/patch-224

Update load-balancer-tcp-reset.md

Author: PRMerger15

articles/load-balancer/load-balancer-tcp-reset.md

@@ -15,14 +15,11 @@ ms.date: 05/03/2019
 ms.author: allensu
 ---
 
-# Load Balancer with TCP Reset on Idle (Public Preview)
+# Load Balancer with TCP Reset on Idle
 
 You can use [Standard Load Balancer](load-balancer-standard-overview.md) to create a more predictable application behavior for your scenarios by enabling TCP Reset on Idle for a given rule. Load Balancer's default behavior is to silently drop flows when the idle timeout of a flow is reached.  Enabling this feature will cause Load Balancer to send bidirectional TCP Resets (TCP RST packet) on idle timeout.  This will inform your application endpoints that the connection has timed out and is no longer usable.  Endpoints can immediately establish a new connection if needed.
 
 ![Load Balancer TCP reset](media/load-balancer-tcp-reset/load-balancer-tcp-reset.png)
-
->[!NOTE] 
->Load Balancer with TCP reset on idle timeout functionality is available as Public Preview at this time. This preview is provided without a service level agreement and is not recommended for production workloads. Certain features may not be supported or may have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for details.
 
 You change this default behavior and enable sending TCP Resets on idle timeout on inbound NAT rules, load balancing rules, and [outbound rules](https://aka.ms/lboutboundrules).  When enabled per rule, Load Balancer will send bidirectional TCP Reset (TCP RST packets) to both client and server endpoints at the time of idle timeout for all matching flows.
 
@@ -68,7 +65,6 @@ Available in all regions.
 
 ## Limitations
 
-- Portal cannot be used to configure or view TCP Reset.  Use templates, REST API, Az CLI 2.0, or PowerShell instead.
 - TCP RST only sent during TCP connection in ESTABLISHED state.
 
 ## Next steps