Migration - Case: New Automation Cloud Account

Prerequisites

To start your journey with the new Automation Hub experience, you must ensure that the following prerequisites are met at the Automation Cloud level.

First prerequisite requires you to have an Automation Cloud Organization created.

How to Create a New Automation Cloud Organization

• You can automatically have an Automation Cloud Organization by creating a new Automation Hub trial in a couple of seconds by going to the UiPath Automation Hub webpage and selecting Try Automation Hub free.
• Sign up using Single Sign On (Google, Microsoft, LinkedIn) or with your e-mail and password.
• After completing the process, you'll be redirected to the Automation Hub service (in the newly created Automation Cloud organization) where you'll be able to provision your service by following the steps from How to provision Automation Hub.

How to Enable the Automation Hub Service From Automation Cloud

Automation Hub can be enabled on an existing Automation Cloud tenant, or you can choose to add the service on a new tenant of your choice.

Note: You need to be an Organization Admin in Automation Cloud to perform this action.

• Go to your Automation Cloud Admin Menu → Tenants.
• Select the tenant where you want Automation Hub enabled.
• Then select Tenant Settings and enable the Automation Hub option.

• Select Save.

To complete the Automation Hub provisioning, continue with How to provision Automation Hub.

See more details here: Enabling Automation Hub in Automation Cloud

How to Provision Automation Hub

Note: Enabling the Automation Hub service from the Tenants menu in Automation Cloud is not enough to start using the service.

• After enabling the Automation Hub service from Automation Cloud, you need to access the Automation Hub service by clicking on the link from the Tenants menu in Automation Cloud or on the Icon on the Left Navigation.

• This will open a presentation page where you'll be able to read about Automation Hub benefits and will be able to view the Continue button.

The Continue button will act differently based on whether you already have an existing Automation Hub instance or not.

Here are the possible scenarios:

How to Link/Migrate Your Existing Automation Hub Instance to Your New Automation Cloud Account

By linking your existing Automation Hub instance to Automation Cloud, you'll be able to continue your activity uninterrupted. Your data (ideas, users, setup, activity) is not affected during the migration and the operation is 100% reversible.

Note:

Please note that the current account owner for standalone Automation Hub needs to perform the linking/migration.

If the account owner is not available or has left the company, they can be changed by filing a support ticket.

• After clicking the Continue button, based on your e-mail address, in the side panel, you'll be able to identify all the existing Automation Hub instances for which you have the Account Owner role.

• Select the Automation Hub standalone instance from the list.

  Note: If the Migrate existing Automation Hub option isn't displayed, that means that you aren't the Account Owner for that Automation Hub instance you wish to migrate.

• After selecting the tenant, you have different options to choose from to perform the operation:

  • Full Migration

  • Partial Migration

How to Perform a Partial Migration

This will allow only you (the user who performs the operation) to use Automation Hub as a service in Automation Cloud. The rest of the users won't be affected and can use the existing Automation Hub instance as before (same URLs, same interface). This option is recommended before performing the change (full migration) to the entire existing Automation Hub user base.

• Select Partial Migration and then click Confirm.

The Partial Migration takes a couple of seconds and has the following outcomes:

• The user who performs the migration will experience the new Automation Hub setup (in Automation Cloud).
• All new functionalities will be in place and can be tested before going forward with the Full Migration.

• When you are ready for the rollout, you can perform the Full Migration from Automation Hub → Admin → Account → Settings.

The Partial Migration is an experience that allows only one user to interact with Automation Hub integrated with Automation Cloud.

The activity and data won't be affected by this migration. The database and user activity remains the same, which means that:

• All new automations created by the migrated user will be visible also to the other users.
• All new automations created by the non-migrated users will be visible to the migrated user.

See more details here: Provisioning from Automation Hub.

How to Perform a Full Migration

We recommend you perform this only when you have fully tested the feature and have prepared your users for the new experience of using Automation Hub in Automation Cloud.

The rollout process is important, and we want to offer you full control over how users will receive this change.

• Select Full Migration and then click Confirm.

Before you start the Full migration:

• The Azure Active Directory plays an important role in the Full Migration process, as it impacts the way the users will be notified when the operation is done.
• Based on the status of your Azure Active Directory connection, please consider the following options for the Full Migration:

Full Migration with the Azure Active Directory Connected

• With this option, we will not notify your users (via e-mail) when the migration is performed.
• You can control what e-mail to send (manually) to your users and at what time.
• All the users from the existing Automation Hub instance that are part of the connected Azure Active Directory will be able to access the service.
• The uses that aren't part of Azure Active Directory will have to be added manually in Automation Cloud to regain access to Automation Hub.
• All existing data will be unaffected.
• All URLs will be changed, and redirects will be in place to shift the users to the new experience.

Full Migration without the Azure Active Directory connected

• This option will trigger e-mail invitations to all the existing Active and Pending users from Automation Hub to join Automation Cloud.
• The users will have to accept the Automation Cloud invitation to access Automation Hub in the new setup.
• All users will be imported to Automation Cloud and gain basic permissions as part of the Everyone group.
• All URLs will be changed, and redirects will be in place to shift the users to the new experience.

See more details here: Provisioning from Automation Hub

What Changes Will Be Seen in the Interface

The new Automation Cloud experience brings minimal changes to the Automation Hub interface. Here is a summary of the changes:

• User Groups: Manage your users by leveraging the groups you have created in Automation Cloud and map them to the existing roles from Automation Hub (see more here: Managing Groups).
• User management: search and add users from Automation Cloud.
• Left navigation: contains the Automation Hub icon (together with the other services from Automation Cloud) and the language switcher.
• Tenant switcher: appears in the Automation Hub header and allows navigating between Automation Cloud tenants.
• Logo update/Co-branding: your custom logo can be added in the header next to the product logo from Automation Cloud level and applies to all services.

How to Setup Your Azure Active Directory Integration

The main benefit of the Active Directory integration is the ease of user management. You will be able to connect your Azure Active Directory instance to Automation Cloud and easily manage all the users and groups.

All the connected cloud services in Automation Cloud will leverage the Azure Active Directory integration, including Automation Hub.

The main changes at Automation Hub level when Azure Active Directory is connected are:

• Bulk user upload via CSV will not be available anymore (as users will be managed via Azure Active Directory Groups).
• When searching for Users and Groups, you will get results from both Automation Cloud (local directory) and from the connected Azure Active Directory.
• If you perform a Full Migration, the users in the existing Automation Hub instance will not receive invites to join Automation Cloud, as they will be able to connect with their Azure Active Directory Identity.

See more details here: Setting Up the Azure AD Integration and Active Directory Integration.