Entra provisioning error 6105 license not found

Not specified by the original author.

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

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

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

Thread query: "Entra provisioning error 6105" license not found

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.

Not specified by the original author.

Clear Entra provisioning quarantine after the failure threshold

TL;DR

Microsoft Entra ID quarantines a provisioning job after too many consecutive failures - a circuit breaker that pauses all sync so a broken config does not hammer the target app. Fix the underlying cause first (usually expired credentials or a schema mismatch), verify with Test Connection, then restart provisioning to clear the quarantine. Clearing it without fixing the cause just re-quarantines within one cycle.

The error

Provisioning Service State: Quarantine
"The quarantine threshold was exceeded. Provisioning has been quarantined."
Entra admin center / Enterprise apps / [app] / Provisioning / Overview

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=azure%20ad%20automatic%20provisioning%20quarantine%20threshold%20exceeded%20error"

Fix it

Step 1: Find the repeated failure behind the quarantine

In Entra admin center, open Identity / Applications / Enterprise apps / [app] / Provisioning / Provisioning logs. Filter by status Failure over the last 24 hours and group by error.

Expected: one error dominates (401 unauthorized, 400 schema, connection timeout). That single error is the cause; the quarantine is the symptom.

Step 2: Fix the root cause

If 401/403: re-enter the admin credentials or rotate the SCIM bearer value in Provisioning / Admin credentials. If 400 schema: fix the attribute mapping. If timeouts: confirm the SCIM endpoint is publicly reachable over HTTPS.

Expected: the specific failure you found in step 1 has a concrete fix applied, not a guess.

Step 3: Verify with Test Connection

In Provisioning / Admin credentials, choose Test Connection and wait for the result.

Expected: success. If it fails here, do not proceed - the quarantine will return.

Step 4: Restart provisioning to clear the quarantine

In Provisioning / Overview, select Restart provisioning. Confirm when prompted.

Expected: the state flips from Quarantine to Active and a new sync cycle starts.

Step 5: Watch one full sync cycle

Stay on the Provisioning logs page through the next cycle and confirm new entries show Success and the failure count stays at zero.

Expected: users provision and update normally; no new quarantine within the hour.

When this applies

• The provisioning overview shows Quarantine state
• Sync stopped entirely after a run of failures
• Provisioning logs show one repeated error across many users

When it doesn't

• Individual users fail while the job stays Active (fix the per-user error instead)
• Provisioning never ran at all (check the initial configuration)
• The job is paused manually (just resume it)

Compatibility

Microsoft Entra ID automatic provisioning (formerly Azure AD provisioning service). Applies to SCIM and non-gallery app provisioning.

Variant phrasings

entra provisioning quarantined

Same state, newer name. The restart path is identical: fix cause, test connection, restart provisioning.

azure ad provisioning stopped quarantine

Check whether it stopped on its own (quarantine) versus someone pausing it. Only quarantine needs the root-cause fix first.

Why it happens

Quarantine is a circuit breaker. Entra counts consecutive provisioning failures; past the threshold it assumes the configuration is broken and stops the job rather than retrying thousands of doomed operations against the target app. One systemic error poisons the whole sync.

Edge cases

• Restarting without fixing the cause re-quarantines in the next cycle; always fix first
• Large initial syncs can trip the threshold on transient errors; narrow the scope with filters for the first sync
• Credential expiry is the top cause; set a calendar reminder before the next expiry

If it still fails

• Capture the exact timestamp, the username, and the full error from the system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• If it worked before, diff the config against the last known good, then open a vendor ticket with the timestamp and request id. Never send secrets or private keys.

Prevention

• Track credential and certificate expiry with alerts, not memory.
• Run a synthetic check per app daily so breakage pages you, not a user.
• Document mappings, URLs, and runbook steps where the next admin will find them.

Provenance

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

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

Thread query: azure ad automatic provisioning quarantine threshold exceeded error

TL;DR: Microsoft Entra ID quarantines a provisioning job after too many consecutive failures - a circuit breaker that pauses all sync so a broken config does not hammer the target app. Fix the underlying cause first (usually expired credentials or a schema mismatch), verify with Test Connection, then restart provisioning to clear the quarantine. Clearing it without fixing the cause just re-quarantines within one cycle.

Not specified by the original author.

TL;DR

Do not fix group licensing errors user by user. Open Entra, then Licenses, then the group, read the per-user error list, and fix the top error classes in bulk: conflicts, count violations, and missing prerequisites. Then let reconciliation run.

how to fix license assignment errors in Entra ID groups

Use this when

• A licensed group in Entra shows assignment errors.
• Many users fail with a handful of distinct errors.
• The errors appeared after a group or SKU change.

Not for this skill when

• A single directly-assigned user fails. That is a per-user fix.
• The errors are transient and clear on the next cycle.
• The group itself cannot be found. That is a directory problem.

Steps

1. Open the group's license error list in Entra. Verify: you see every failing user and their error.
2. Group the errors by type: conflicts, count violations, prerequisites. Verify: you have counts per class.
3. Fix conflicts by disabling overlapping plans, count violations by freeing seats, prerequisites by adding base SKUs. Verify: each fix matches its class.
4. Wait for or trigger license reconciliation. Verify: the cycle completes.
5. Confirm the error count drops to zero. Verify: the group is healthy.

Variant phrasings

Entra group licensing troubleshooting

The generic phrasing.

group license errors

The short search.

fix license errors Entra

The action-first phrasing.

Compatibility: Microsoft Entra ID group-based licensing.

Why it happens

Group licensing fails in bulk with a small number of root causes. Per-user fixing never converges because the same cause reappears on the next member; class-level fixes do.

Edge cases / pitfalls

• Errors that clear on the next cycle without action are transient; do not chase them.
• Nested group membership confusing both the count and the error attribution.
• Fixing a conflict on the group license affects all members; check the blast radius.
• Reconciliation timing: fixes can take a full cycle to reflect, so verify after the cycle, not immediately.

Provenance

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

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

Thread query: how to fix license assignment errors in Entra ID groups

TL;DR: Do not fix group licensing errors user by user. Open Entra, then Licenses, then the group, read the per-user error list, and fix the top error classes in bulk: conflicts, count violations, and missing prerequisites. Then let reconciliation run.