You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your service backends should be in a Virtual network and behind a Standard Load Balancer.
56
53
57
54
### How can I scale my Private Link service?
58
55
You can scale your Private Link service in a few different ways:
59
56
- Add Backend VMs to the pool behind your Standard Load Balancer
60
57
- Add an IP to the Private Link service. We allow up to 8 IPs per Private Link service.
61
58
- Add new Private Link service to Standard Load Balancer. We allow up to eight Private Link services per load balancer.
62
59
63
-
### Will VNet service endpoints be deprecated after private endpoints are available?
64
-
No. VNet service endpoints and private endpoints are independent technologies/resources. They can complement each other and both will co-exist. Some functionality and use cases may overlap. You can choose the model that fits your needs.
65
-
60
+
66
61
### How should I control the exposure of my Private Link service?
67
62
You can control the exposure using the visibility configuration on Private Link service. Visibility supports three settings:
68
63
@@ -71,7 +66,7 @@ You can control the exposure using the visibility configuration on Private Link
71
66
-**All** - Everyone can locate the service.
72
67
73
68
### Can I create a Private Link service with Basic Load Balancer?
74
-
No. Private Link service over a Basic Load Balancer is not supported. Standard Load Balancer is supported.
69
+
No. Private Link service over a Basic Load Balancer is not supported.
75
70
76
71
### Is a dedicated subnet required for Private Link service?
77
72
No. Private Link service doesn’t require a dedicated subnet. You can choose any subnet in your VNet where your service is deployed.
0 commit comments