These docs are for v4.3. Click to read the latest docs for v4.4.

Onboarding for Azure Enterprise Agreements (EA)

❗️

Please read first:

Before proceeding with onboarding for this type of cloud account, you must ensure the required pre-onboarding steps have been completed first.

For more information on what these prerequisites are and how to address them, please refer to the Pre-Onboarding for Azure Enterprise Agreements (EA) user guide.

Introduction

An Azure Enterprise Agreement (EA) account allows enterprises under an Azure Enterprise Agreement to access and manage their Azure resources and billing data programmatically through applications.

The account onboarding process follows a step-by-step flow with five steps, described in the list below. Users must complete every step by filling in the appropriate details so that they can proceed to the next step.

The onboarding flow for Azure cloud accounts covers the following main steps:

  1. Azure Cloud Account Type: Select the type of Azure cloud account that needs to be onboarded.
  2. Prerequisites: Select the cloud account scope, access type, and product(s).
  3. Add & Validate Credentials: Select the authentication type and provide the required Azure account credentials.
  4. Basic Settings: Select and/or input the basic settings for the cloud account.
  5. Advanced Settings (optional): This optional step allows users to add tags and set up any required governance configurations. Account governance configurations can also be done after the onboarding steps.

As users add all necessary details for each step in the onboarding flow, it will be marked as completed and no longer appears greyed out in the left sidebar.

Detailed onboarding steps are explained in the sections below.

📘

Note:

Before starting the onboarding process on the platform, make sure that you have followed and completed all the prerequisite steps in the GCP cloud portal. Refer to the PRE-ONBOARDING user guides for more information on how to complete these steps.

Onboarding Steps

Perform the following steps to onboard an Azure Enterprise Agreement (EA Application):

  1. Log in to the platform and on the left menu bar, go to Settings > Onboard Accounts.

    The Onboard Cloud Accounts starting page will appear. Here, users can select which cloud provider to onboard a new account for based on the available options.

📘

Note:

Users can also use the Dashboard button in the upper right corner of the page to go directly to the Account Governance Dashboard (Cloud Accounts) as a shortcut.

  1. To start the onboarding process, hover over the Azure option under Public Cloud Providers, and an Onboard button should appear. Select Onboard to proceed.

  2. The page for the first step of the onboarding workflow should appear – Azure Cloud Account Type. In this step, users must select the specific Azure cloud account type to onboard. You can select one of the following account types to be onboarded:

    • Subscription

    • Enterprise Agreement (EA Application)

    • Microsoft Partner Agreement (CSP Direct)
      In this case, select Enterprise Agreement (EA Application).

  3. Click Next. The Prerequisites section appears.

  4. In the Select Cloud Account Scope field, select one of the following options:

    • Tenant: This scope allows the cloud account to be available only in the tenant it is onboarded to. This option is selected by default.
    • Account: This scope allows the cloud account to be available in all tenants.
  5. In the Select Access Type field, Read-Only is the only available option so it will be automatically selected:

    • Read-Only: This option provides viewing access without the ability to make changes.
  6. In the Select Product(s) field, FinOps is the only available option to be accessible for this cloud account type so it will automatically be selected.

  7. Click Next. The Add & Validate Credentials section appears.

  8. In the Add & Validate Credentials section, fill the following fields:

    • In the Enrollment ID box, type the enrollment ID.

    • In the Tenant ID box, type the tenant ID.

    • In the Application ID box, type the application ID.

    • In the Application Secret box, type the application secret code.

    • Click Save & Validate.

If the validation is successful, then a success message will be displayed.

If the validation fails, then an error message will be displayed along with an option for View Log. You can click View Log to view the error details and then click Re-Validate to retry the validation.

📘

Note:

After the completion of successful validation, the Save & Validate button turns to Re-Validate. You can click Re-Validate to validate the account again.

  1. Click Next. The Basic Settings section appears.

  2. Fill the following basic details:

    • In the Subscription list, select an appropriate account subscription.

    • In the Storage Account box, type the storage account name.

    • In the Report Path box, type a path where cost reports will be available.

    • In the Account Name box, the account name will be pre-populated. Based on the need, this field can be modified.

    • In the Currency list, click to select the currency in which the cost report will be downloaded from the cloud provider.

    • Select the Privacy Policy checkbox to accept the terms and continue with the onboarding process.

      📘

      Note:

      The Account Name field should not exceed the maximum character limit of 50 characters including special characters.

  3. You can click Next to set up advanced settings or click Finish to complete the account onboarding. Please note that the step for configuring advanced settings is not mandatory and can be skipped.

  4. If you click Next, then the Advanced Settings section will be displayed.

    • In the Add/Import Cloud Account Tags section, do any of the following to fill in the tag details:
      In the Custom Tags field:
      • In the Key box, type the tag key.
      • In the Value box, type the tag value.
      • Lastly, click Add Tag. The added tag appears below.
        After clicking View Master Account/Tenant Tags:
      • This opens the Custom Tags dialog box where you can select the required tags and click Add Selected Tags. The selected tags will now show up for the account to be onboarded.
    • In the Governance Configuration field, click Edit to configure the required settings. Refer to Governance Configuration for detailed steps.
  5. Click Finish.

The Onboarding Status dialog box appears that shows the progress of account onboarding. You can click Go to the Dashboard to return to the Account Governance Dashboard.

📘

Note:

We request that users ensure any individual Subscriptions that are part of the Azure EA root account have not already been onboarded when onboarding the Azure EA root account. If you want all Subscriptions to be part of the Azure EA root account after onboarding it, please remove any individual Subscription first, then onboard the Azure EA root account.

If an individual Subscription has already been onboarded and is not required to be part of the EA root account, you can still onboard the EA root account without mapping the Subscription to it.

Please note that individual Subscriptions show PAYG costs, while Subscriptions onboarded under the EA root will reflect costs according to rates applied in the EA root account.

Governance Configuration

The Governance Configuration page includes many sections where configurations can be made. You need to select the configuration you want to apply to your onboarded account. All the available configuration sections are explained below. Refer to the relevant configuration and follow the steps. These governance configurations can be made while onboarding the account or can be done post onboarding.

FinOps

The configurations that can be done for FinOps are explained below.

Cost Anomaly

Perform the following steps to configure cost anomaly:

  1. Expand the Cost Anomaly section.

  2. Ensure that Anomaly Detection Sensitivity field is enabled (the slider is on the right side).

  3. In the Resource Category Sensitivity box, the settings are applied by default. If you want to edit the default setting, add the sensitivity based on which anomaly would be detected.

  4. In the Notification section, click Configure. The Notifications Settings dialog box appears.

    1. Select the Enable Notification checkbox. The Email Address, Webhook, and Microsoft Teams Webhook fields are displayed.
    2. In the Email Address box, type the email address of the user(s) and click Add.
    3. In the Webhook box, type the webhook link(s) and click Add.
    4. In the Microsoft Teams Webhook box, type the URL(s) for Microsoft Teams Webhook and click Add.
    5. Click Save & Apply.