Skip to content

Commit 72a44eb

Browse files
xfz11yungezz
andauthored
Apply suggestions from code review
Co-authored-by: Yunge Zhu <[email protected]>
1 parent 1672e22 commit 72a44eb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-connector/concept-service-connector-internals.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,9 +99,9 @@ Service Connector offers three network solutions for users to choose from when c
9999

100100
3. **Private Endpoint**: This solution is a recommended way to connect resources via a virtual network and is only available if certain preconditions are met:
101101
- The compute resource must have VNet integration enabled. For Azure App Service, this can be configured in its networking settings; for Azure Spring Apps, users must choose to deploy their app in a VNet during the creation stage.
102-
- The target service must support VNet solutions. For a list of supported services, refer to [Private-link resource](/azure/private-link/private-endpoint-overview#private-link-resource).
102+
- The target service must support private endpoints. For a list of supported services, refer to [Private-link resource](/azure/private-link/private-endpoint-overview#private-link-resource).
103103

104-
When selecting this option, Service Connector does not perform any additional configurations in the compute or target resources. Instead, it verifies the existence of a valid private endpoint and fails the connection if no one is found. For added convenience, users can select the "New Private Endpoint" checkbox in the Azure Portal when creating a connection. With it, Service Connector will automatically create all related resources for the private endpoint in the proper sequence, simplifying the connection creation process.
104+
When selecting this option, Service Connector does not perform any additional configurations in the compute or target resources. Instead, it verifies the existence of a valid private endpoint and fails the connection if not found. For convenience, users can select the "New Private Endpoint" checkbox in the Azure Portal when creating a connection. With it, Service Connector will automatically create all related resources for the private endpoint in the proper sequence, simplifying the connection creation process.
105105

106106

107107

0 commit comments

Comments
 (0)