Requirements for Azure Active Directory Activities Package

Help Activities
, , , ,
1

Hi, All!

There’s a project that I’m working on that needs to use the Azure Active Directory Activities Package. I see that there’s a need for Tenant ID, Client ID, and Client Secret. I don’t have any idea yet about Azure or how I can generate these requirements. Does anybody know how? Or do you happen to know any reading materials with step by step process?

Thank you!

2

Certainly! If you’re using the UiPath platform and the Azure Active Directory Activities Package, here’s a step-by-step guide to help you generate the required credentials (Tenant ID, Client ID, and Client Secret) specifically for UiPath:

  1. Azure Account and Subscription:
    If you don’t have an Azure account, you’ll need to sign up for one. Once you have an account, create a new Azure subscription if you don’t have one already.

  2. Register an Application in Azure AD:

    • Go to the Azure portal (https://portal.azure.com/).
    • In the left-hand menu, click on “Azure Active Directory.”
    • Click on “App registrations.”
    • Click the “New registration” button.
    • Provide a name for your application, choose the appropriate supported account types (usually “Accounts in any organizational directory and personal Microsoft accounts”), and enter a valid redirect URI.
    • Click the “Register” button.

  3. Get the Tenant ID:

    • In the Azure portal, navigate to the “Azure Active Directory” section.
    • Click on “Properties.”
    • Copy the value of the “Directory ID” field. This is your Tenant ID.

  4. Get the Client ID (Application ID):

    • In the Azure portal, go to your registered application.
    • Copy the value of the “Application (client) ID” field. This is your Client ID.

  5. Generate a Client Secret:

    • In your registered application, go to the “Certificates & secrets” section.
    • Under “Client secrets,” click on the “+ New client secret” button.
    • Enter a description for the secret, select an expiration (or choose “Never”), and click the “Add” button.
    • After the secret is created, copy the secret value. This is your Client Secret. Store it securely.

  6. Configure UiPath Orchestrator:

    • Log in to your UiPath Orchestrator instance.
    • Go to the “Settings” section.
    • Click on “Security.”
    • Under the “AzureAD” section, provide the Tenant ID, Client ID, and Client Secret you obtained earlier.
    • Save your changes.

Now, UiPath Orchestrator is configured to use the Azure Active Directory credentials. You can use the Azure Active Directory Activities Package in your UiPath workflows to interact with Azure services securely.

3

Hi, @Usha_Jyothi ! Thanks for your quick response. For Step 2, Bullet 5, where can I get a valid redirect URL?

Also, for step 6, I don’t see Azure AD section on my Settings. Do I need to be in an enterprise subscription to make this work?

4

When you’re registering an application in Azure Active Directory, you’ll need to specify a valid redirect URI. The redirect URI is used for authentication purposes and is the URL where the user will be redirected after successfully authenticating with Azure AD. Here’s how you can choose a valid redirect URI:

  1. Choose the Type of Application:
    The type of application you’re registering will determine the appropriate redirect URI:

    • Web Application or Web API: If your application is a web application or a web API that users will access through a browser, you’ll typically use a URL associated with your application’s authentication callback route. For example: https://your-app-domain.com/auth/callback.

    • Native Application: If your application is a native application (e.g., a desktop or mobile app), you might use a custom URI scheme registered for your app. For example: yourapp://auth.

    • Single-Page Application (SPA): For SPAs, you can use a URL within the same domain where the SPA is hosted, often with a route that handles the authentication callback. For example: https://your-spa-domain.com/auth-callback.

  2. Considerations:

    • The redirect URI must be registered in the Azure AD application registration to ensure security and prevent unauthorized access.
    • For security reasons, Azure AD will only redirect to registered redirect URIs.
    • The URI must be a valid and reachable URL where your application can handle the authentication response.
    • Make sure the redirect URI you choose matches the authentication callback route in your application’s code.

  3. Register the Redirect URI:
    When you’re registering your application in Azure AD, provide the chosen redirect URI in the appropriate field. Here’s how you can do it:

    • During the application registration process, you’ll find a field to enter the redirect URI.
    • Enter the exact URI that you’ve chosen based on the type of your application.
    • After registering the application, Azure AD will recognize this URI as a valid callback point for authentication.

Remember that the specific steps might vary based on the Azure portal’s version and updates that have occurred since my last knowledge update. Always refer to the official Azure documentation or the documentation specific to your application framework for the most accurate and up-to-date information.

5

Subscription Level : Some features in UiPath Orchestrator, including advanced security features like Azure AD integration, might be available only in enterprise editions

6

@_pjflo

Please check this how to register app…you can register as a service …so that no redirect url is needed

For permissions needed check individual activities which show the required permissions

Example

image
image1222×266 21.1 KB

cheersx