# Setting up Azure Account Connections
Learn how to set up your credentials in Azure AD, so you can sync your Azure data to via an Azure Cloud Account connection.
- 1. Register an Application in Azure Active Directory
- 2. Assigning permissions for Reserved Instance information
- 3. Create a new Cloud Account in Cloud Ctrl
# 1. Register an Application in Azure Active Directory
Azure Active Directory (AD) Applications are identities that you create and control within your own AD tenant and can be granted privileges on the resources that you specify. These applications have their own login credentials and are intended to be used in code, such as in Cloud Ctrl.
Cloud Ctrl uses the AD Applications to connect to the Azure Resource Manager and gather metadata and metrics from your subscriptions.
For all these steps, Microsoft have published documentation covering the process in the Azure Portal. View the Microsoft Documentation (opens new window)
# Collect the Tenant ID
- Log in to the Azure Management Portal (opens new window) using tenant admin credentials.
- From the left-side menu, click Azure Active Directory.
- Select Properties from the list.
- From the properties screen, copy the Directory ID. This is your Tenant ID.
# Register a New Application
- Navigate to the Manage section of Azure Active Directory, then click App Registrations > New Registration.
- Enter a Name for your application.
- For Support Account Types, leave the default.
- For User Redirect URI, leave the default.
- Click on Register.
- Copy the Application ID after successful registration. This is your Client ID.
- Generate the client secret
- Go to Manage > Certificates & secrets
- Under Client Secrets, click New client secret.
- Add a Description for the secret and select an expiration period.
- Click on Add.
- Copy down the Client Secret Value that is generated as this cannot be displayed again. (==Important!==)
For the name, we suggest using “Cloud Ctrl” so it can easily be identified later when viewing through the portal.
There are two options when it comes to applying role authorisation to the application.
# OPTION 1: Assignment of READER role to the application
You can assign the built in READER role to the application for each subscription you want to connect to Cloud Ctrl. This option is the simpliest to perform when there are only a few subscriptions. If however, you have many subscriptions to assign, option 2 may be more suitable. Option 2 also limits the READER permissions to just those needed by Cloud Ctrl.
Follow the Microsoft documentation (opens new window) to assign the standard READER role or a custom role to each subscription.
# OPTION 2: Assign custom role using Powershell
Learn how to use PowerShell in Azure's Cloud Portal to assign a custom role to a registered application for all Subscriptions in Azure.
The custom role contains explicit read only permissions required by the application.
Details of the custom role can be viewed in the role template here (opens new window).
- An Admin account in Azure with access to the PowerShell portal.
- An existing Azure AD Application in Azure.
- At least one active Azure subscription.
Run the Script in Powershell
- Log in to your Azure portal. In the top navigation bar, click Cloud Shell.
- In the Cloud Shell window, select PowerShell.
- Download the role assigment script from here (opens new window).
- Upload the script file to the Azure Cloud Shell
- From the Cloud Shell prompt enter the
./and the uploaded file name to execute the script.
The script will then promt you for some information:
- The Name you gave to the Azure AD application (created in an earlier step) that you want to assign the role to.
- The Azure location / region where the role template will store deployment data, this has little impact on the execution, we recommend choosing a region where you have resources already deployed.
- some example options are: (australiaeast, centralus, southeastasia, japaneast, canadacentral, uksouth)
- The Role Name for the new custom role; use something that can easily identify the roles pupose i.e.
Cloud Ctrl Read Only
The script will then execute and assign the new role to the Application principle in all subscriptions visible to the current powershell user. If you experience any errors during execution please contact our support team.
# 2. Assigning permissions for Reserved Instance information
To collect information about reserved instances, for the inventory and prorating cost informtaion you will need to grant some additional permissions to the AD application, this time at a tenant level.
When you buy an Azure reservation, access is restricted to the user who bought it (e.g. user-adm@IT.on.microsoft.com) and the account administrator.'
# Assign the Reservations Reader role at the tenant level
Assigning the reservation reader role at the tenant level automatically grants read access to all reservations in the Azure AD tenant (directory). When you grant access at the tenant level, you do not need to grant access to new reservations as they are acquired, nor do you need to provide access to each subscription individually.
Using the Powershell script below you can add a Reservations reader role to the Azure Active Directory (AD) Application service principal you have created for your Azure ARM Connection.
This can be run in the Azure Portal using the Cloud Shell (opens new window)
#Import required resources Import-Module Az.Accounts Import-Module Az.Resources # Connect to Active Directory Connect-AzAccount -Tenant <Tenant ID> -UseDeviceAuthentication # Get the Service Principal ID for you AD App Registration $ServicePrincipalId = (Get-AzADServicePrincipal -DisplayName <AD Application Registration Display Name> -First 1).Id # Assign the Reservation Reader role to the Application Service Principal New-AzRoleAssignment -Scope "/providers/Microsoft.Capacity" -PrincipalId $ServicePrincipalId -RoleDefinitionName "Reservations Reader"
Refer to the Microsoft Official Azure documentation (opens new window) for details.
# 3. Create a new Cloud Account in Cloud Ctrl
To start importing usage data for Microsoft Azure, you need to create an Azure Cloud Account.
- To add a new cloud account go to Settings > Cloud Accounts > Create
- The New Cloud Account window will appear, select Azure Account
You will be prompted for a name for the Cloud Account as well as the Tenant Id, Application / Client Id and the Application / Client Secret you got from the ARM Connection.
The name is an internal name used within the platform for you to be able to identify this connection among multiple connections, e.g. Azure MSDN, Azure PAYG, etc.
Once you submit we get to work loading your data, initially as we load you account history it may take upto 24hrs for your usage in the portal to be loaded completely.