Skip to content

Commit 708429c

Browse files
Merge pull request #301967 from seligj95/patch-4
Update app-service-hybrid-connections.md
2 parents 7e9f2e5 + 2e0b665 commit 708429c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ When a Hybrid Connection is added to your app, you can see details on it simply
8989

9090
To create a Hybrid Connection using an ARM/Bicep template, add the following resource to your existing template. You must include the `userMetadata` to have a valid Hybrid Connection. If you don't include the `userMetadata`, the Hybrid Connection doesn't work. If you create the Hybrid Connection in the Azure portal, this property is automatically filled in for you.
9191

92-
The `userMetadata` property should be a string representation of a JSON array in the format `[{"key": "endpoint", "value : "host:port"}]`. The following Bicep template has a sample for this property. For more information, see [Microsoft.Relay namespaces/hybridConnections](/azure/templates/microsoft.relay/namespaces/hybridconnections).
92+
The `userMetadata` property should be a string representation of a JSON array in the format `[{/"key/": /"endpoint/", /"value/" : /"<HOST>:<PORT>/"}]`. For more information, see [Microsoft.Relay namespaces/hybridConnections](/azure/templates/microsoft.relay/namespaces/hybridconnections).
9393

9494
```bicep
9595
resource hybridConnection 'Microsoft.Relay/namespaces/hybridConnections@2024-01-01' = {

0 commit comments

Comments
 (0)