Merge pull request #92630 from MonikaReddy-MSFT/patch-1

Update app-service-hybrid-connections.md

Author: PRMerger6

articles/app-service/app-service-hybrid-connections.md

@@ -35,7 +35,7 @@ Through the two joined connections, your app has a TCP tunnel to a fixed host:po
 When your app makes a DNS request that matches a configured Hybrid Connection endpoint, the outbound TCP traffic will be redirected through the Hybrid Connection.  
 
 > [!NOTE]
-> This means that you should try to always use a DNS name for your Hybrid Connection. Some client software does not do a DNS lookup if the endpoint uses an IP address instead.
+> This means that you should try to always use a DNS name for your Hybrid Connection. Some client software does not do a DNS lookup if the endpoint uses an IP address instead. 
 >
 
 ### App Service Hybrid Connection benefits ###
@@ -60,6 +60,9 @@ Things you cannot do with Hybrid Connections include:
 - Support LDAP, because it can require UDP.
 - Support Active Directory, because you cannot domain join an App Service worker.
 
+### Prerequisites ###
+ - Windows App service is required. It is only available in Windows.  
+
 ## Add and Create Hybrid Connections in your app ##
 
 To create a Hybrid Connection, go to the [Azure portal][portal] and select your app. Select **Networking** > **Configure your Hybrid Connection endpoints**. Here you can see the Hybrid Connections that are configured for your app.