Connect Azure During Trial Registration

Use this guide to connect the first Azure subscription while registering for a Cloudaware trial.

If the Cloudaware account is already active and another Azure AD or subscription must be added, use Add an Azure Directory or Subscription from the Admin Panel instead.

Prerequisites

Before you begin, ensure that you have Azure tenant admin privileges to create applications and assign roles.

Start in Azure

Register an Azure application for Cloudaware

1. Log in to the Azure portal.

2. Go to App registrations.

3. Click + New registration.

4. Configure the application:

   • Name: Enter a descriptive name, for example, cloudaware-api-access.

   • Supported account types: Select Single tenant only - Default Directory (Accounts in this organizational directory only) or Multiple Entra ID tenants (Accounts in any organizational directory).

   • Redirect URI: (optional) Select Web and enter https://cloudaware.com.

5. Click Register.

6. Copy and save the following values:

   • Application (client) ID

   • Directory (tenant) ID

Configure API permissions

1. On the application, go to API permissions.

2. Click Add a permission.

3. Under Microsoft APIs, add Azure Service Management:

   • Delegated permissions: Select user_impersonation.

4. Add Microsoft Graph permissions:

   • Delegated permissions: Select Directory.Read.All.

   • Application permissions: Select Directory.Read.All.

5. Click Grant admin consent for the tenant.

Permissions may take up to 30 minutes to propagate.

Assign Azure RBAC roles

Assign RBAC roles based on the required discovery scope.

Tenant-wide discovery

Use this option to let Cloudaware discover subscriptions automatically across the tenant.

In the Azure portal:

1. Go to Management groups.

2. Select the Tenant Root Group.

3. Open Access control (IAM).

4. Click + Add → Add role assignment.

5. Assign the Reader role to the Cloudaware application (in this example, cloudaware-api-access).

6. Click Review + assign.

Subscription-level discovery

Use this option if you want to limit Cloudaware discovery to specific subscriptions.

In the Azure portal:

1. Go to Subscriptions.

2. Select the subscription.

3. Open Access control (IAM).

4. Click + Add → Add role assignment.

5. Assign the Reader role to the Cloudaware application (in this example, cloudaware-api-access).

6. Click Review + assign.

Tip: If additional capabilities are required, such as Key Vault metadata, AKS details, reservations, or tagging, assign the required optional roles at the appropriate scopes. For details, see Additional permissions in Azure.

Create a client secret

Cloudaware supports two authentication methods for Azure: client secret and certificate (recommended). However, for the trial registration, it is sufficient to use a client secret.

1. Open the Cloudaware application in Azure.

2. Go to Certificates & secrets.

3. Open the Client secrets section.

4. Click New client secret.

5. Configure the secret:

   • Description: Enter a descriptive name, for example, ca-api-key.

   • Expires: Select the required expiration period.

6. Copy and securely save the secret value. Note: The client secret value cannot be retrieved after this step.

Complete the setup in Cloudaware

Return to the Cloudaware Launcher (Control Hub) and click Connect Azure.

1. Fill out the form:
   

   

   • Subscription Name: Enter the Azure subscription name.

   • Subscription ID: Enter the Azure subscription ID.

   • Active Directory Name: Enter the Azure Active Directory name.

   • Active Directory ID (Tenant ID): Enter the Azure Active Directory (tenant) ID.

   • Application ID (Client ID): Enter the Cloudaware application ID.

   • Environment: Select the Azure environment from the dropdown.

   • Client Secret: Enter the client secret.

2. Click Continue to check the credentials.

3. Click Save.

After Cloudaware validates the Azure subscription, the trial registration is submitted.

Next steps

Check the inbox for the Registration Complete email.

Registration may take up to 1 hour.