Error
Last updated on
Aug 3, 2026
Find error descriptions and resolutions for automatic assignment rules in Admin Console.
Consult this reference when you encounter errors while creating, editing, or managing automatic assignment rules in the Admin Console, or when a rule's status changes from Active to Pending.
Each error includes its description, impact on users, license assignment, and steps to resolve the issue.
Error reference
|
|
Description |
Impact |
Mitigation |
|
Product Profile has been removed |
The product profile associated with a rule is deleted. The profile is removed from the rule, and the status changes from Active to Pending. |
Users who request access to a rule in a Pending state will not receive access to a license until a profile is reassigned to the rule. |
Assign another product profile to the rule. Navigate to Products > Product access automation > Automatic assignment rules, select the rule, and add a new product profile. |
|
Product has been removed |
A product is removed from the Admin Console, or its contract expires. The product is automatically removed from the rule, and the status changes from Active to Pending. |
The product is not available for automatic assignment. Users cannot request access. |
Navigate to Products > Product access automation > Automatic assignment rules, select the rule, and add a product profile. |
|
One or more domains are not active |
Domains associated with a rule are no longer active. The inactive domains are removed from the rule. The rule still applies to other selected active domains. If no chosen domains are active, the status changes from Active to Pending. |
Users who were previously eligible based on their email domain are no longer eligible and will not be granted automated access to a license upon request. |
Update the affected domains or remove them from the eligible domain list. Navigate to Products > Product access automation > Automatic assignment rules, select the rule, and update the domain selection. |
|
Select at least one domain If choosing a directory for eligibility |
No domain is selected when choosing a specific directory for user eligibility. |
A rule cannot be created or updated without a domain if you've selected Users in selected directories or domains as eligible users. |
Select at least one domain to proceed. When creating or editing the rule, ensure you select a domain from the directory. |
|
One or more directories are not active |
Directories associated with a rule are no longer active. The inactive directories are removed from the rule. The rule still applies to other active directories previously added. If the chosen directory is not active, the status changes from Active to Pending. |
Users who were previously eligible based on their email domain are no longer eligible and will not be granted automated access to a license upon request. |
Update the affected directories or remove them from the list of eligible directories. Navigate to Products > Product access automation > Automatic assignment rules, select the rule, and update the directory selection. |
|
No licenses available |
All available licenses for a product in a rule are in use. No additional licenses can be automatically assigned to eligible users who request access. |
Users cannot access the requested product until the administrator adds additional licenses. |
Purchase additional licenses, which automatically provision licenses to users who were previously approved and awaiting availability. To view pending users, navigate to Products, select the product, select NO ACCESS, then check the Users tab. |
Rule status indicators
Automatic assignment rules display one of two status values in the Admin Console:
- Active: The rule is functioning correctly and will automatically assign licenses to eligible users who request access.
- Pending: The rule has encountered an error and cannot assign licenses until the issue is resolved.
When a rule status changes to Pending, administrators receive an email notification with details about the specific error.
Note
Pausing or removing a rule does not affect users who were previously provisioned a license via automated approval.
