Skip to content

Commit ff291a9

Browse files
authored
small number of changes
updated a few things based on questions received in email and online
1 parent 8b95d1f commit ff291a9

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: na
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: article
16-
ms.date: 07/26/2018
16+
ms.date: 06/06/2019
1717
ms.author: ccompy
1818
ms.custom: seodec18
1919

@@ -39,7 +39,6 @@ When your app makes a DNS request that matches a configured Hybrid Connection en
3939
> 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.
4040
>
4141
42-
4342
### App Service Hybrid Connection benefits ###
4443

4544
There are a number of benefits to the Hybrid Connections capability, including:
@@ -137,7 +136,7 @@ To add one or more Hybrid Connections to your HCM:
137136
2. Select **Configure another Hybrid Connection**.
138137
![Screenshot of Configure New Hybrid Connections][8]
139138

140-
1. Sign in with your Azure account.
139+
1. Sign in with your Azure account to get your Hybrid Connections available with your subscriptions. The HCM does not continue to use your Azure account beyond that.
141140
1. Choose a subscription.
142141
1. Select the Hybrid Connections that you want the HCM to relay.
143142
![Screenshot of Hybrid Connections][9]
@@ -224,7 +223,9 @@ The status of "Connected" means that at least one HCM is configured with that Hy
224223

225224
The primary reason that clients cannot connect to their endpoint is because the endpoint was specified by using an IP address instead of a DNS name. If your app cannot reach the desired endpoint and you used an IP address, switch to using a DNS name that is valid on the host where the HCM is running. Also check that the DNS name resolves properly on the host where the HCM is running. Confirm that there is connectivity from the host where the HCM is running to the Hybrid Connection endpoint.
226225

227-
In App Service, the tcpping tool can be invoked from the Advanced Tools (Kudu) console. This tool can tell you if you have access to a TCP endpoint, but it does not tell you if you have access to a Hybrid Connection endpoint. When you use the tool in the console against a Hybrid Connection endpoint, you are only confirming that it uses a host:port combination.
226+
In App Service, the **tcpping** command line tool can be invoked from the Advanced Tools (Kudu) console. This tool can tell you if you have access to a TCP endpoint, but it does not tell you if you have access to a Hybrid Connection endpoint. When you use the tool in the console against a Hybrid Connection endpoint, you are only confirming that it uses a host:port combination.
227+
228+
If you have a command line client for your endpoint, you can test connectivity from the app console. For example, you can test access to web server endpoints by using curl.
228229

229230
## BizTalk Hybrid Connections ##
230231

0 commit comments

Comments
 (0)