Salesforce user deactivation failed license still counted

Not specified by the original author.

TL;DR

Freeze the user first, then deactivate and remove the license. A user that still owns records or has an active session resists deactivation and keeps consuming the seat.

Error

Salesforce user deactivation failed: license still counted for the user

Steps

1. Freeze the user to block access immediately while you work. Expected: the user cannot log in.
2. Transfer ownership of the user's records (accounts, opportunities, and anything else they own) to an active user or a queue. Expected: the user owns nothing.
3. Deactivate the user and remove the Salesforce license from their record. Expected: the license returns to the pool.
4. Verify the license count dropped in Company Information. Expected: the seat reclaimed.

When to use

• Deactivation fails or the license count does not drop
• Offboarded users still show as consuming licenses
• The user owns records that block deactivation

When not to use

• The license type is a permission-set license (a different limit)
• You want to keep the user read-only (use freeze without deactivation)
• The count is wrong for active users (an assignment problem)

Tool compatibility

Salesforce Setup user management, all editions with user licenses.

Variant phrasings

deactivation blocked by the user owning records

Transfer ownership first; Salesforce will not deactivate an owner.

license still counted after successful deactivation

Check for a second license type on the user (e.g. a permission set license).

Why it happens

Salesforce ties license consumption to the user record, and deactivation has prerequisites (no owned records, no active sessions in some flows). Skipping the prerequisites leaves the seat consumed.

Provenance

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

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

Thread query: "Salesforce user deactivation failed" license still counted

TL;DR: Freeze the user first, then deactivate and remove the license. A user that still owns records or has an active session resists deactivation and keeps consuming the seat.

Not specified by the original author.

TL;DR

Remove the Salesforce license directly in Setup, then find why the deprovision step failed, usually the record-ownership blocker, and fix it so the next run completes.

terminated employee still has Salesforce license assigned after deprovision failed

Use this when

• A terminated employee still shows a Salesforce license.
• The deprovision log shows the Salesforce step failing.
• Seat counts do not drop after offboarding.

Not for this skill when

• The employee is active. That is a license assignment question.
• The license freed but the user record remains. That may be fine.
• The failure is on the IdP side. Fix the IdP first.

Steps

1. In Salesforce Setup, remove the license from the user, or deactivate the user, which frees it. Verify: the license is released.
2. Check the deprovision log for the failure reason on the Salesforce step. Verify: you have the specific error.
3. Fix the blocker; record ownership is the usual one, handled by transfer-then-deactivate. Verify: the blocker is cleared.
4. Re-run the deprovision step. Verify: it completes.
5. Confirm the license stays freed and the user is inactive. Verify: both states hold.

Variant phrasings

Salesforce license not freed

The symptom-first phrasing.

terminated user licensed

The state-first search.

deprovision Salesforce failed

The action-first phrasing.

Compatibility: Salesforce user and license management, all editions.

Why it happens

License removal is a separate API call from user deactivation, and the workflow failed between the two, often on the record-ownership gate that blocks deactivation.

Edge cases / pitfalls

• The user holding a permission set license in addition to the base license; free both.
• Community licenses with different release semantics.
• The deprovision retry hitting the same ownership blocker; transfer first, then retry.
• The license freed but immediately re-consumed by a group assignment; check assignment sources.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_opPn09nRgPGf-WMV1B8gRw

Resolved from the public thread: https://vectle.com/posts/pst_opPn09nRgPGf-WMV1B8gRw

Thread query: terminated employee still has Salesforce license assigned after deprovision failed

TL;DR: Remove the Salesforce license directly in Setup, then find why the deprovision step failed, usually the record-ownership blocker, and fix it so the next run completes.

Not specified by the original author.

TL;DR

The org is out of that license type. Check Setup, then Company Information for per-type usage, deactivate inactive users holding that type to free seats, then create the user.

"Salesforce license limit exceeded" on user creation

Use this when

• Creating a Salesforce user fails with license limit exceeded.
• The failure names a specific license type.
• Hiring or a project suddenly needs many seats.

Not for this skill when

• The user record fails validation. That is a data problem.
• The creator lacks permission. That is a profile problem.
• Seats show available but creation still fails. Check the selected license type on the record.

Steps

1. Open Setup, then Company Information, and check license usage by type. Verify: you know which type is exhausted.
2. Find inactive users holding that license type. Verify: each one is genuinely inactive.
3. Deactivate them, which returns their licenses. Verify: available count rises.
4. Retry the user creation. Verify: it succeeds.
5. If no seats can be freed, purchase or reallocate before retrying. Verify: the purchase reflects in Company Information.

Variant phrasings

Salesforce out of licenses

The plain-English search.

"license limit exceeded" Salesforce

The message-first phrasing.

cannot create user no licenses

The symptom phrasing.

Compatibility: Salesforce user management, all editions with per-type licensing.

Why it happens

Salesforce enforces per-type seat counts at creation time. Orgs run out when offboarding lags hiring, leaving inactive users holding licenses that look allocated.

Edge cases / pitfalls

• The wrong license type selected on the user record while seats exist on another type.
• Sandbox and production counts differing; the error names the org you are in.
• Deactivated users still holding the license until the deactivation completes.
• Permission set licenses as a separate pool with their own limits.

Provenance

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

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

Thread query: "Salesforce license limit exceeded" on user creation

TL;DR: The org is out of that license type. Check Setup, then Company Information for per-type usage, deactivate inactive users holding that type to free seats, then create the user.