## 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
```text
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