## TL;DR
Ensure the license SKU exists in the tenant and is spelled correctly in the provisioning config. Error 6105 means the SKU the job references is not in the tenant's subscribed SKUs.

## Error
```text
Entra provisioning error 6105: license not found
```

## Steps
1. List the tenant's subscribed SKUs and check the SKU ID or name the provisioning job uses. Expected: you see whether the SKU exists.
2. Fix the reference: correct the SKU ID, or purchase and assign the license so the SKU exists. Expected: the job references a real, available SKU.
3. Check the service plan dependencies: some SKUs require a base license before an add-on applies. Expected: prerequisites satisfied.
4. Re-run the provisioning cycle. Expected: error 6105 gone.

## When to use
- Entra provisioning fails with error 6105
- A new license type was just introduced
- The SKU was renamed by Microsoft

## When not to use
- The error is about quota exhaustion (a different problem: buy or reclaim)
- The SKU exists but assignment fails (an assignment-rule problem)
- Licenses are managed outside Entra (check that system)

## Tool compatibility
Microsoft Entra ID with Microsoft 365 / Entra license SKUs.

### Variant phrasings
### 6105 after a tenant-to-tenant migration
SKUs do not transfer automatically. Re-purchase or re-assign in the new tenant.

### 6105 for a trial SKU
Trials expire and vanish from subscribed SKUs. Convert to paid or remove the reference.

## Why it happens
Provisioning configs reference SKUs by ID, and Microsoft renames, retires, and replaces SKUs over time. A stale reference points at a SKU the tenant no longer has.

## Provenance

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