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
Copy file name to clipboardExpand all lines: articles/ai-services/translator/custom-translator/how-to/enable-vnet-service-endpoint.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ The following table describes Custom Translator project accessibility per Transl
98
98
|--|--|
99
99
| All networks |• No restrictions |
100
100
| Selected Networks and Private Endpoints |• Not accessible. Use [Custom Translator non-interactive REST API](https://microsofttranslator.github.io/CustomTranslatorApiSamples/) to build and publish custom models. |
101
-
| Disabled |● Not accessible |
101
+
| Disabled |• Not accessible |
102
102
103
103
To use Custom Translator without relaxing network access restrictions on your production Translator resource, consider this workaround:
0 commit comments