Azure startup credits missing from a bill: an evidence-first checklist

Reconcile an Azure charge against the exact subscription, benefit activation time and covered service before assuming startup credits failed. A public sponsor relationship or an unused balance does not establish coverage for a particular invoice line.

Start with one charged line and its billing identity

Choose a single disputed charge and capture its usage dates, subscription identifier, service or meter, currency and billing period. Identify the account that owns the approved startup benefit. Keep a redacted copy for discussion and retain the full identifiers only in the authorized billing workflow. A screenshot of a company’s total credit balance cannot connect the benefit to the billed subscription. Do not change billing associations as an experiment while investigating: first establish where the charge belongs and who is authorized to request a correction.

Current primary documentation

Compare activation time with consumption time

Create a small timeline containing programme acceptance, benefit activation, subscription association and resource usage. Microsoft’s current startup billing guide describes account-level benefits and a transition to pay-as-you-go after depletion. The approved offer controls the actual account. In a hypothetical case, usage on 2 November precedes activation on 4 November. That explains a timing question worth raising; it does not establish a retroactive entitlement or refund. Use the provider’s usage timestamps rather than only the date an invoice became visible, since invoice publication and service consumption are different events.

Verify coverage for the specific product

Classify the service under the applicable current offer. First-party infrastructure, third-party models, Marketplace purchases and separately licensed tools may follow different rules. Keep the publisher and procurement route visible even when the service appears in the Azure portal. Check the actual credit details and supporting terms rather than inferring coverage from a friendly resource name. A charge can be correctly billed while other eligible workloads consume credits normally. The worksheet should mark unknown coverage as unresolved and keep its cash exposure visible until support or the terms resolve it.

Distinguish expiry, depletion and association

An expired benefit, a consumed balance and a subscription linked to the wrong account are different diagnoses. Capture the balance and status with their observation date, then reconcile them against the relevant period. A balance display may not answer whether a particular past line was eligible. Review account transitions and existing support cases before opening another. If the charge is a tax, support plan or partner product, preserve that classification for the billing specialist. Avoid repeatedly deleting and recreating resources in an attempt to force a billing change; it can destroy evidence and create additional usage.

Send a bounded support question with evidence

A useful support packet contains the redacted charge, timeline, benefit identifier, account association and exact policy question. Ask whether that line should have been covered under that offer and period, and what supported correction path exists. Do not promise a refund or imply that AptixLabs can approve one. After a documented resolution, verify a later eligible charge before closing the issue. Update the operating forecast for uncovered services and the pay-as-you-go transition so the same misunderstanding does not return at the next invoice.

Microsoft startup credits application checklist

Startup credits expiration budget

Bring a redacted invoice line and activation timeline to separate billing questions from architecture work.

B2B SaaS development: scope and acceptance