Sign in with Microsoft
Self-managed customers can log in to ESET PROTECT Hub, ESET PROTECT, ESET Inspect, ESET Cloud Office Security and ESET Secure Authentication using their Microsoft account credentials (single sign-on with Microsoft Entra ID).
Configure single sign-on with the Microsoft account
1.Connect tenants from Microsoft Entra ID.
2.Add domain groups and manage connections.
When the single sign-on with Microsoft Entra ID is configured, users can log in with the Microsoft account.
Connect Microsoft Entra ID tenants
The ESET PROTECT Hub superuser can connect Microsoft Entra ID tenants to enable users to log in with their Microsoft account credentials.
1.In ESET PROTECT Hub, navigate to 
Admin settings > Single sign-on section.
2.Click New connection, type the tenant name and click Connect.
3.Send the generated link to the Microsoft Entra ID Administrator (the domain owner).
4.The Microsoft Entra ID Administrator (the domain owner) performs the following steps:
a.Log in to your Microsoft account using the provided link.
b.A Permissions requested window appears, displaying the permissions required by ESET. Approve the permissions by clicking Accept to create an integration between the Microsoft Entra ID and ESET PROTECT Hub. Tenant status changes to Active in ESET PROTECT Hub > Admin settings > Single sign-on > Manage connections.
5.The Connection successful notification appears in the top corner—Add domain groups or View the list of connections. The tenant appears in Admin settings > Single sign-on > Manage connections with the Active registration status.
6.Continue by adding domain groups (as described below).
Add domain groups
You must add connected Microsoft Entra ID domain groups and assign permissions:
1.In ESET PROTECT Hub, navigate to either of these places:
• Admin settings > Single sign-on > Manage connections. Click the three dots 
icon next to the connection name or the Actions button > click Add domain groups.
•
Users > 
Microsoft Entra ID groups. Click Add groups.
2.In Groups, select the Microsoft Entra ID groups by clicking the check boxes next to the group names. Click Next.
3.In Permissions, set the permissions for the selected Microsoft Entra ID groups. Click Next.
|
Permissions enable users to authenticate, manage user group assignments and apply security policies. Permissions in ESET PROTECT Hub for Microsoft Entra ID users are assigned via groups. Users in a group in Microsoft Entra ID linked to ESET PROTECT Hub receive access to ESET PROTECT Hub with permissions assigned to that group. Users in multiple groups get the highest permission level based on their group membership. |
4.Review the Summary and click Create.
5.In Groups, you can see the Microsoft Entra ID groups with the assigned permissions for each cloud console.
Manage connections
In Admin settings > Single sign-on > Manage connections, click the three dots icon next to the connection name or the Actions button at the bottom:
•Refresh connection—Update the connection between Microsoft Entra ID and ESET PROTECT Hub.
•Add domain groups—You must add Microsoft Entra ID domain groups when configuring the single sign-on with Microsoft Entra ID. You can add more domain groups later.
•Remove—Remove the tenant. Alternatively, select the check box next to the tenant name, click the Actions button at the bottom and select Remove.
|
Removing the tenant permanently removes all the data associated with the tenant and the tenant's domain, and deletes the tenant's ESET cloud consoles from Microsoft Azure. Users from the Microsoft Entra ID user groups can no longer use their Microsoft account to access ESET cloud consoles. |
Sign in with Microsoft
After configuring the single sign-on with Microsoft Entra ID, users can log in with their Microsoft account:
1.Click the Sign in with Microsoft button on the login page of:
2.Type your Microsoft account email and click Next.
3.Type your Microsoft password and click Sign in.
4.If the Two-Factor Authentication is required, follow the additional verification steps.
|
For a list of known issues for single sign-on login via Microsoft account, refer to the section Known issues. |
