Known issues
Known issues are only available in English. |
Known Issue |
Description |
|---|---|
Two-Factor Authentication limitation with Microsoft Entra ID |
Single sign-on with Microsoft Entra ID does not support actions that require Two-Factor Authentication (2FA) in ESET Inspect Terminal and the Run Command task in ESET PROTECT. Workaround: To perform actions that require 2FA, use a superuser account with 2FA enabled, or create a new native user account in ESET PROTECT Hub. Create the account with a different email address than the existing Microsoft Entra ID user accounts, and enable 2FA. A general fix is planned for the upcoming months. |
Show activation key unavailable for Microsoft Entra ID users |
Microsoft Entra ID users with write permissions who log in to ESET PROTECT Hub using their Microsoft account credentials (single sign-on) cannot use the Show activation key feature in subscription details. Workaround: To perform actions that require 2FA, use a superuser account with 2FA enabled, or create a new native user account in ESET PROTECT Hub. Create the account with a different email address than the existing Microsoft Entra ID user accounts, and enable 2FA. A general fix is planned for the upcoming months. |
Requests |
This feature is available only for managing requests from standard resellers and MSPs who have completed the migration to ESET PROTECT Hub. |
Subscription data discrepancy |
There may be a discrepancy between the subscription unit consumption data shown in the Subscriptions tab and the actual number of active subscription units listed in the Active Units tab. |
Reinserting deleted subscriptions |
Standard subscriptions deleted in an ESET PROTECT Hub Customer account migrated from ESET Business Account cannot currently be reinserted. |
Delayed subscription unit allocation refresh |
When the user changes the allocation of subscription units in Sites, updates to unit counts in Sites and the root pool may take time or require a manual refresh. Both allocation from Sites to the root pool and vice versa are affected. During the delay: •ESET Secure Authentication activation may succeed even when no subscription units are present in the respective site or root pool. •ESET Secure Authentication activation may fail even though subscription units have just been allocated. |
Site-level access limitation |
If a user is granted access only to a site in ESET PROTECT Hub, it is currently not possible to provide access to the ESET PROTECT Web Console. A general fix is planned for the upcoming months. |
ESET PROTECT installer functionality after migration |
After the migration from ESET Business Account and ESET MSP Administrator, the existing installers in ESET PROTECT may no longer function. Workaround: Recreate the installer in ESET PROTECT. A general fix is planned for the upcoming months. |