Reference: level of support for Azure MCA and EA accounts

Turbonomic uses a service principal to connect to your Microsoft Customer Agreement (MCA) or Enterprise Agreement (EA) accounts and discover billing data.

Note:

For Azure Government, Azure currently supports EA accounts only. The Azure Billing target in Turbonomic aligns with this level of support.

Currently, Turbonomic support for MCA and EA accounts is identical in the following areas:

  • Discovery of pricing data

    Pricing data is available for VMs, volumes, SQL databases (DTU and vCore), dedicated SQL pools (for Azure Synapse Analytics), and App Service plans (web apps, logic apps, and function apps).

  • Usage of pricing data when recommending actions

    All actions for Azure workloads are supported, including actions to optimize/buy reservations.

  • Support for the Buy VM Reservations plan

    The plan is fully supported.

  • Scope for cost exports (if used to collect billing data)

    The following scopes are not supported:

    • Subscription

    • Management Group

    • Resource Group

The level of support differs in the following areas.

Item MCA EA
Required role Billing Account Reader role Enrollment Reader role
Discovery of Azure reservations All reservations charged under the billing account are discovered. However, the percentage of workloads covered by reservations is currently not discovered. All reservations charged under the billing account are discovered.
Discovery of Azure reservations costs in non-US dollar currencies Enabled by default Not enabled by default. To enable discovery, follow the instructions in this topic.
Scope for cost exports (if used to collect billing data) Cost exports must be created at the Billing Profile scope. If you previously set up a cost export at the Billing Account scope, you must delete the cost export and then create a new one at the Billing Profile scope. Create this cost export for each active Billing Profile that falls under your MCA Billing Account. All cost exports you create for your active Billing Profiles are required to have the same name. Cost exports must be created at the Billing Account scope.