Merge pull request #2899 from melghazali/main

Update enable-vnet-service-endpoint.md

Author: prmerger-automator[bot]

articles/ai-services/translator/custom-translator/how-to/enable-vnet-service-endpoint.md

@@ -91,12 +91,12 @@ The following table describes Custom Translator project accessibility per Transl
    :::image type="content" source="../media/how-to/allow-network-access.png" alt-text="Screenshot of allowed network access section in the Azure portal.":::
 
  > [!IMPORTANT]
- > If you configure **Selected Networks and Private Endpoints** via the **Networking** → **Firewalls and virtual networks** tab, you can't use the Custom Translator portal to create workspaces to train and publish models. However, you can still use the Translator resource with [Custom Translator non-interactive REST API](https://microsofttranslator.github.io/CustomTranslatorApiSamples/) to build and publish custom models.
+ > If you configure **Selected Networks and Private Endpoints** via the **Networking** → **Firewalls and virtual networks** tab, you can't use the Custom Translator portal to create workspaces to train and publish models. However, you can still use the Translator resource with [Custom Translator non-interactive REST API](https://github.com/MicrosoftTranslator/CustomTranslatorApiSamples/tree/arvadivel/adding_curl) to build and publish custom models.
 
 | Translator resource network security setting | Custom Translator portal accessibility |
 |--|--|
 | All networks | • No restrictions |
-| 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. |
+| Selected Networks and Private Endpoints | • Not accessible. Use [Custom Translator non-interactive REST API](https://github.com/MicrosoftTranslator/CustomTranslatorApiSamples/tree/arvadivel/adding_curl) to build and publish custom models. |
 | Disabled | • Not accessible |
 
 To use Custom Translator without relaxing network access restrictions on your production Translator resource, consider this workaround:
@@ -105,7 +105,7 @@ To use Custom Translator without relaxing network access restrictions on your pr
 
 * Prepare your custom model in the Custom Translator portal on the development resource.
 
-* Copy the model on your development resource to your production resource using [Custom Translator non-interactive REST API](https://microsofttranslator.github.io/CustomTranslatorApiSamples/) `workspaces` → `copy authorization and models`  → `copy functions`.
+* Copy the model on your development resource to your production resource using [Custom Translator non-interactive REST API](https://github.com/MicrosoftTranslator/CustomTranslatorApiSamples/tree/arvadivel/adding_curl) `workspaces` → `copy authorization and models`  → `copy functions`.
 
 ## Billing region codes
 
@@ -151,4 +151,4 @@ Congratulations! You learned how to use Azure `VNet` service endpoints with Cust
 
 ## Learn more
 
-Visit the [**Custom Translator API**](https://microsofttranslator.github.io/CustomTranslatorApiSamples/) page to view our non-interactive REST APIs.
+Visit the [**Custom Translator API**](https://github.com/MicrosoftTranslator/CustomTranslatorApiSamples/tree/arvadivel/adding_curl) page to view our non-interactive REST APIs.