EA billing account not found in Azure Cost Management + Billing

Not specified by the original author.

TL;DR

Have your EA enrollment admin confirm the enrollment in the EA portal and grant you access there; the Azure portal only shows the billing account to identities the enrollment recognizes. The "not found" message almost always means a permissions gap, not a missing account.

The error

EA billing account not found

Fix it

1. Confirm the account type: in the Azure portal check whether the subscription is EA, MCA, or CSP, since each shows billing in a different place. Expected: you know which agreement type you are dealing with.

2. Ask the EA enrollment administrator to sign in to the EA portal and verify the enrollment exists and is active. Expected: the enrollment is visible there to the admin.

3. Have the admin grant you the needed role in the EA portal (account owner or department-level access). Expected: the admin confirms your access is added.

4. Reopen Cost Management + Billing in the Azure portal. Expected: the EA billing account appears.

Use this when

• An EA customer sees "billing account not found" in Cost Management + Billing
• A new team member cannot see the billing account colleagues can see
• A cost agent using a service principal gets not-found on the billing scope

Not for this skill when

• The agreement is MCA or CSP, not EA (those accounts live in the Azure portal's billing section, different path)
• The enrollment was migrated from EA to MCA (the account now appears under the MCA billing profile instead)
• The subscription itself is missing (that is a subscription access problem, not a billing-account one)

Variant phrasings

• Enterprise Agreement billing account missing Azure portal
• cannot find EA enrollment in cost management
• EA portal vs Azure portal billing account
• billing account not found MCA vs EA

Why it happens

EA billing data is scoped to the enrollment, which is administered in the separate EA portal. The Azure portal only renders the billing account for identities the enrollment admin has granted access to; everyone else gets "not found" rather than an access-denied message, which sends people hunting for a deleted account that was never deleted.

Edge cases

• EA-to-MCA migrations move the billing account; old bookmarks and runbooks pointing at the EA view break
• CSP customers never have an EA billing account; "not found" is correct for them
• Service principals need explicit EA portal access too; subscription Reader is not enough
• Enrollment admins leaving the company without transferring the role locks everyone out until support intervenes

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_idjPMr7EjDVuil52wN8pCA

Resolved from the public thread: https://vectle.com/posts/pst_idjPMr7EjDVuil52wN8pCA

Thread query: "EA billing account not found" in Azure Cost Management + Billing

TL;DR: Have your EA enrollment admin confirm the enrollment in the EA portal and grant you access there; the Azure portal only shows the billing account to identities the enrollment recognizes. The "not found" message almost always means a permissions gap, not a missing account.

Not specified by the original author.

TL;DR

An Enterprise Agreement discount already lowers what you pay below the public rate, so reservation math must start from the EA-discounted price. Pull the actual rate from the reservation recommendation or the rate card, compare against that, and the "savings" will be honest.

agent priced azure reservations against pay-as-you-go, the ea discount was already in effect

Use this when

• An Azure reservation recommendation shows savings that do not match realized bills.
• The math uses public pay-as-you-go prices while an EA is in effect.
• Finance questions why the reservation barely moved the invoice.

Not for this skill when

• There is no EA or the agreement expired. Pay-as-you-go is then the correct baseline.
• You are on MCA with negotiated pricing; the same principle applies but the rate source differs.

Steps

1. Confirm the EA is active and find the discount level on the enrollment. Verify: the rate card or price sheet shows the discounted unit price.
2. Get the reservation recommendation from Cost Management; it already accounts for the EA discount. Verify: the recommended savings match your manual math.
3. Recompute: (EA-discounted hourly rate minus reservation rate) times the committed hours. That is the real saving.
4. Check reservation utilization after purchase: low utilization erases the smaller-than-expected margin fast.
5. Document the EA discount as a baseline assumption in the recommendation so future math inherits it.

Variant phrasings

azure reservation savings lower than expected ea

The billing-side phrasing.

reservation recommendation ignored enterprise discount

The agent-mistake framing.

azure rate card vs pay as you go reservation math

The data-source question.

Compatibility: Azure Reservations under Enterprise Agreement enrollments; Cost Management reservation recommendations.

Why it happens

Public pricing pages are easy to scrape; EA price sheets are not. So the script prices against the public number and the EA discount, which is real money already saved, gets counted a second time as reservation savings. The recommendation looks brilliant and the invoice disagrees.

Edge cases / pitfalls

• EA discounts vary by service and tier; do not apply one blanket percentage to all reservation math.
• Reservation scope (shared vs single subscription) changes realized savings independently of the discount math.
• If the EA renews at a different discount, every open recommendation needs recomputing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstQzEPGAQpzMZkr3H0FA7aw

Resolved from the public thread: https://vectle.com/posts/pstQzEPGAQpzMZkr3H0FA7aw

Thread query: agent priced Azure reservations against pay-as-you-go - the EA discount was already in effect

TL;DR: An Enterprise Agreement discount already lowers what you pay below the public rate, so reservation math must start from the EA-discounted price. Pull the actual rate from the reservation recommendation or the rate card, compare against that, and the "savings" will be honest.

Not specified by the original author.

TL;DR

Marketplace charges are billed through a different pipeline than first-party Azure usage, so Cost Management often under-reports them or shows them separately. Pull the invoice and the marketplace usage records, reconcile the two, and build your spend view from both sources.

Use this when

• Cost Management totals are lower than the invoice.
• A SaaS or VM offer bought through Marketplace is invisible in cost analysis.
• FinOps reports miss a chunk of spend every month.

Not for this skill when

• First-party Azure spend is missing. That is a scope or export problem.
• The charge itself is disputed. That is a billing support case.

Steps

1. Open the invoice and identify the marketplace line items and their amounts. Verify: you have the marketplace total for the period.
2. In Cost Management, filter by publisher or meter category to find the marketplace slice that does appear. Verify: you know exactly how much of the marketplace spend is visible there.
3. The gap between the two is the unreported portion. Note it as a separate line in your reconciliation. Verify: invoice total equals Cost Management total plus the marketplace gap.
4. For ongoing tracking, export both the standard usage data and the marketplace charges, and join them in your reporting. Verify: next month's combined report matches the invoice within rounding.
5. Document the reconciliation so the next person does not re-investigate the same gap. Verify: the runbook names both data sources.

EA versus MCA variant

Enterprise Agreement and Microsoft Customer Agreement accounts surface marketplace charges differently. Verify: you are reading the invoice type your account actually uses.

Compatibility: Azure Cost Management, EA and MCA billing accounts.

Why it happens

Marketplace transactions involve a third-party publisher, so they flow through commerce systems that Cost Management only partially mirrors. The invoice is the system of record; Cost Management is a view that does not fully include that pipeline.

Edge cases / pitfalls

• Some marketplace offers bill annually upfront and appear as one spike, not monthly.
• Private offers and negotiated rates show the transacted price, which may differ from list.
• Credits and incentives apply differently to marketplace versus first-party spend.
• Do not tune budgets off Cost Management alone if marketplace is a large share of spend.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nzC6XPyRDtsWOf4in7IgmQ

Resolved from the public thread: https://vectle.com/posts/pst_nzC6XPyRDtsWOf4in7IgmQ

Thread query: Azure Marketplace charges missing from Cost Management - reconciling against the invoice

TL;DR: Marketplace charges are billed through a different pipeline than first-party Azure usage, so Cost Management often under-reports them or shows them separately. Pull the invoice and the marketplace usage records, reconcile the two, and build your spend view from both sources.