Subscribe

UiPath Marketplace

UiPath Marketplace Guide

To successfully establish a connection and send requests to the Microsoft Translator, the Microsoft Translator Scope activity must complete authentication using the supported authentication methods that Translator supports. Please see Quickstart: Get started with Translator for more information in how to get started with Microsoft Translator.

To give the *Microsoft Translator Scope activity the ability to authenticate and to enable the other activities to successfully send requests to Microsoft Translator API, you must complete the following steps:

1. Obtain the Subscription key

  1. Create an Azure subscription if you do not already have one. You can create one for free.
  2. Once you have an Azure subscription, create a Translator resource in the Azure portal to get your key and endpoint. After it deploys, select Go to resource.
    a. You'll need the key and endpoint from the resource to connect your application to the Translator service.
    b. Save your key and endpoint as you will need them for the Microsoft Translator Scope activity.

2. Build your project

  1. Create a new automation project.
    1. Open UiPath Studio.
    2. Under New Project, click Process (this opens a New Blank Process window).
    3. Enter a project Name, Location, and Description.
    4. Click Create.
  2. Install the UiPath.MicrosoftTranslator.Activities package.
    1. In the Design ribbon, click Manage Packages (this opens the Manage Packages window).
    2. Under All Packages, click Connect
    3. In the Search bar, enter Microsoft Translator.
    4. Click, install and accept the license for the UiPath.MicrosoftTranslator.Activities.
      • For more information about Uipath Studio packages, see Managing Packages in the Studio Guide.

You're done!

Now that you have completed the setup, you can start adding the Microsoft Translator activities to your project.

Updated 11 months ago


Setup


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.