Unable to Use Cost Management APIs and Exports for Microsoft Sponsorship Subscription

Hello Sindur N Gowda

Thank you for posting your query on Microsoft Q&A platform.

The root cause here is that Microsoft Azure Sponsorship subscriptions (Offer ID: MS-AZR-0036P) are explicitly listed as an unsupported subscription type for both Azure Cost Management features and the Azure Consumption APIs.

This means the following features are not available for your sponsorship subscription:

• Cost Analysis in the Azure portal
• Cost Management Exports (automated CSV/Parquet to storage account)
• Budgets and Alerts via Cost Management
• Azure Consumption Usage Details API

You can verify this in two official places:

1. The "Supported Microsoft Azure offers" table on the Cost Management data page — Sponsorship is not listed among supported offers: Understand Cost Management data
2. The Azure Consumption REST API overview page explicitly lists MS-AZR-0036P (sponsored) under "List of Unsupported Subscription Types": Azure Consumption REST APIs

This is a platform-level limitation by design, not a configuration issue. Microsoft Support cannot override or enable Cost Management features for sponsorship subscriptions.

Below are the supported Workarounds:

Even though native Cost Management is unavailable, you can still build automated cost visibility using the following approaches:

Option 1: Azure Retail Prices API (No Authentication Required)

The Azure Retail Prices REST API provides pay-as-you-go retail pricing for all Azure services. It's a free, public, unauthenticated API — no Azure subscription or login needed to call it.

Endpoint:

GET https://prices.azure.com/api/retail/prices

You can filter by serviceName, armRegionName, skuName, etc. to get per-meter pricing. Then combine this pricing data with resource-level usage metrics (from Azure Monitor) to estimate costs per resource/resource group.

Reference: Azure Retail Prices REST API overview

Option 2: Azure Monitor Metrics for Resource-Level Usage

Azure Monitor automatically collects platform metrics from your Azure resources at no extra cost, this works regardless of your subscription offer type. You can track resource-level utilization metrics (CPU, storage, network, etc.) and use these alongside the Retail Prices API to build cost estimates.

Reference: Azure Monitor Metrics overview

Option 3: Azure Resource Graph for Resource Inventory

Azure Resource Graph lets you query all deployed resources across your subscription with complex filtering, grouping, and sorting. You can use it to get a complete inventory of resources by resource group, type, location, and tags — which helps you map usage to specific teams or projects.

Reference: What is Azure Resource Graph?

Option 4: Azure Sponsorship Portal

For aggregated cost data, the Azure Sponsorship Portal remains the official source. It shows resource-level details like resource name, type, region, and cost — though only the subscription owner can access it.

Portal: https://www.microsoftazuresponsorships.com/Usage

Azure Credit Offer – Microsoft for Startups

For enterprise-level automation on a sponsorship subscription, here's a practical approach:

1. Use Azure Resource Graph to get a full resource inventory grouped by resource group.
2. Use Azure Monitor metrics to pull resource-level utilization data.
3. Query the Retail Prices API to get per-meter pricing.
4. Combine pricing × usage in a PowerShell or Python script to calculate estimated costs.
5. Automate on a schedule using Azure Automation Runbooks or Azure Functions.
6. Export results to Blob Storage and distribute via Logic Apps or Power Automate for email reporting.

Once your sponsorship credits expire or you transition to a supported offer type (Pay-As-You-Go, Enterprise Agreement, or Microsoft Customer Agreement), all Cost Management features — Cost Analysis, Exports, Budgets, Alerts, and APIs — become available automatically.

Reference: Change your Azure subscription offer

Hope this helps clarify things. Please let me know if you have any follow-up questions!

Thanks,
Suchitra.