Move existing users to N-able Login with Entra ID

If your organization currently uses Microsoft Entra ID (Azure AD) to authenticate N-central users, you can modernize your identity strategy by moving to N-able Login with Microsoft Entra ID. The move updates your authentication method to using the Microsoft cloud-based identity platform, Entra ID.

When you move users from Azure AD to N-able Login with Entra ID, existing Azure AD users are automatically converted to N-able Login with Entra ID users. See What to Expect.

By moving to N-able Login with Microsoft Entra ID, your organization benefits from centralized, cloud-based identity management, stronger security through modern authentication controls, and a seamless login experience across all N-able products. This not only reduces administrative overhead but also positions your environment for future scalability and compliance.

This process involves two key steps

  • Converts the authentication system by registering N-central as an enterprise application in Entra ID and configuring it allows N-able Login (MSP SSO) to use Entra ID as the authenticator.

  • Moves existing users to N-able Login (MSP SSO) functionality while preserving the security and authentication through the use of their Entra ID ID identities.

What to Expect

For existing N-central users, the configuration of N-able Login with Entra ID may affect how they log in. However, it requires the configuration of the Entra enterprise application as well as the associated users to be added to this new application as detailed in this guide.

To convert an existing user to N-able Login with Entra ID, you must ensure that the user is part of an Entra group added to the Provisioning application within the Entra console or add the user directly to the Provisioning application within the Entra console. The existing user is identified by their unique email address used to login to both N-central and Microsoft.

Here is what to expect when an existing user is added to an N-able user provisioning application in Entra:

  • Existing local users will be enrolled in N-able Login (MSP SSO) and converted to use Entra ID for authentication.

  • Existing N-able Login users will be converted to use Entra ID for authentication. This will affect the login of other N-able products used with their N-able Login account. All N-able products using their N-able Login account will now use Entra ID for authentication, giving full SSO capabilities.

  • Existing legacy identity provider (IdP) users that are logging into N-central using a previously configured identity provider (legacy Azure AD, Active Directory, LDAP etc), these users will be automatically converted to use N-able Login with Entra ID for authentication. They will be automatically disconnected from the previous identity provider and linked to this new Entra ID for authentication.

These affected users are not required to take any additional action and will see the change the next time they log in. You can see what users are impacted by viewing the Recently Migrated Users section of the new Provisioned Users section in N-central. It is recommended that you add only a few users you would like to convert to Entra ID first, to the User Provisioning application. This will allow you to validate functionality before a full existing user conversion.

High-level steps

What changes for users

  • Users move from signing in with previous credentials to using their Entra ID (Microsoft 365) accounts.

  • Authentication redirects shift from any previous IdP to the Microsoft cloud login portal for Entra.

  • Multi-factor authentication (MFA) policies managed through Entra ID may now apply.

  • Conditional Access Policies managed through Entra ID may now apply.

  • User access continuity is preserved by carefully linking user accounts during the transition.