Share via

Troubleshooting in Azure carbon optimization (Preview)

  • Article

This article helps you diagnose and troubleshoot common issues you might encounter when using carbon optimization.

Access issues

The following sections describe common access issues and their solutions.

Access denied on Carbon Optimization

Problem: Permissions issues when accessing the Carbon Optimization page.

Solution:

  • Request appropriate permissions.
  • Carbon emissions data is accessible to Carbon Optimization Reader, Subscription Owner, and Subscription Contributor roles. These roles let you view carbon emissions data on the Emission Trends and Emission Details pages.
  • Permissions are set at the subscription level.

Steps to Assign Carbon Optimization Reader Role:

To assign the Carbon Optimization Reader role, you need to be a subscription owner or contributor.

  1. Go to the Subscriptions page in the Azure portal.
  2. Select the subscription where you want to assign the role.
  3. Select Access control (IAM).
  4. Select Add role assignment.
  5. Select Carbon Optimization Reader from the Role drop-down list.
  6. Select the user or group you want to assign the role to.
  7. Select Save.

Data limitations

The following sections describe common data limitations and their solutions.

View data for more than 100 subscriptions

Problem: Data is available for a maximum of 100 subscriptions selected at a time when viewing carbon emissions data on the carbon optimization page.

Current behavior: If you select more than 100 subscriptions, data shows only for the first 100 subscriptions selected.

Solution: Select up to 100 subscriptions to view accurate and complete data.

Tips for selecting relevant subscriptions:

  • Review your selection to ensure it doesn't exceed 100 subscriptions. The subscription selection filter shows the number of subscriptions selected.
  • Select subscriptions most relevant to your carbon optimization goals (for example, highest usage or emissions).
  • Perform analysis in multiple steps, selecting different sets of up to 100 subscriptions at a time.

Note

To access data for more than 100 subscriptions or other large-scale data operations, use the Microsoft Azure emissions insights capability. It's available as part of the Sustainability data solutions in Fabric.

Twelve month lookback period for emissions data

Problem: Azure Carbon Optimization shows emissions data for resources for the last 12 months.

Solution: For data beyond the last 12 months, consider using:

Emissions data issues

The following sections describe common emissions data issues and their solutions.

All or most scope 2 emissions are zero

Explanation: This error occurs because scope 2 market data is shown instead of scope 2 location data. For more information, see the calculation methodology.

API issues

The following sections describe common API issues and their solutions.

API authentication error

Error: Failed to send request to Microsoft.Carbon due to AAD authentication error

Explanation: This error might occur if the tenant admin disables the app in your tenant.

Solution:

  • Contact your tenant admin to check if "Prod-AzureSustainability" is disabled in your tenant. If it is disabled, enable it.

One month date scope supported in certain API Report types

Problem: When attempting to request data spanning multiple months, an error occurs, suggesting a request should be made for one month at a time.

Example error:

"error": {
          "code": "InvalidRequestPropertyValue",
          "message": "The start date 11/01/2023 00:00:00 and end date 12/01/2023 00:00:00 should be equal for report type ItemDetailsReport."
        }

Expected behavior: 'ItemDetailsReport' and 'TopItemsSummaryReport' only support a single month at a time.

Solution:

  • Query data for a single month when using the 'ItemDetailsReport' and 'TopItemsSummaryReport' API report types.
  • Enter the first day of each month to get emissions data for the whole month.

Request throttling

Problem: The API has a limit of 100 queries per minute (QPM) per tenant.

Expected behavior: Exceeding this limit might result in throttling, and other requests are queued or rejected until the rate drops below the limit.

Solution: Monitor and manage your query rate to avoid throttling, especially during periods of high demand.

General limitations

The following sections describe common general limitations and their solutions.

Can't display data for the selected subscriptions in the Carbon Optimization page

Problem: The error message Data can't be displayed for the selected subscriptions might appear for several reasons:

  • Missing Carbon Optimization Reader role for some subscriptions.
  • New subscriptions with no data available yet (data takes at least a month to appear).
  • Subscriptions with no resource usage, hence no emissions data.

Solution:

  • Make sure you have the necessary permissions. For more information, see Access Denied on Carbon Optimization.
  • Wait for data to become available for new subscriptions.
  • Check subscription usage in the Cost Analysis page or Resource page.

One-hour wait for tenant registration on first-time visit

Problem: Some tenants might wait up to one hour on their first visit.

Expected behavior: If you're on a tenant viewing the Azure carbon optimization page for the first time, there's a 30-minute to one-hour wait for your tenant to register in the system. During this time, you might see a message indicating that tenant registration is in progress, or a blank page is shown. When the registration is complete, you can see your data. Once your tenant is registered, other users in your organization on the same tenant have access to the data without any wait time.

Data latency

Problem: Changes to a resource configuration appear in the emissions data of the following month.

Solution:

  • Data updates by the 19th day of the following month.
  • Plan your analysis accordingly, taking into account this data update schedule.

Related content