Skip to main content

After configuring user authentication from Microsoft Entra ID (Azure Active Directory), why do I get an error message when logging into the platform?

  • Updated

This article describes the most common causes of authentication errors in SMARTFENSE via Microsoft Entra ID (Azure Active Directory) and how to resolve them.

Basic checks

If you see an error when authenticating with Microsoft Entra ID, check the following items:

  1. The user you are trying to sign in with must exist in the SMARTFENSE platform and must be active.
  2. The username you are authenticated with on your PC -or in Microsoft Entra ID- must match the username you use to sign in to SMARTFENSE.
  3. The user must be logged into their Active Directory from the device they want to use to sign in to SMARTFENSE.

If you prefer, you can access the platform with an administrative user using SMARTFENSE credentials. To do this, add /admin at the end of your instance's URL. For example: instancename.takesecurity.com/admin. You can also use the Administrative login link on the sign-in screen.

Error due to user assignment not allowed

Another possible error is the following message:

This is an error caused by an internal Microsoft Entra ID configuration that does not grant users permission to authenticate to third-party apps. This permission must be enabled.

 

There are two ways to resolve this, depending on how the customer wants to manage access.

Option 1: Assign users or groups explicitly

If the customer prefers to control who can authenticate through specific groups or users, they must assign them manually in:

Microsoft Entra ID > Enterprise applications > [SMARTFENSE application] > Users and groups.

Option 2: Disable required assignment

If they prefer that any user in the tenant can authenticate without explicit assignment:

  1. Go to Microsoft Entra ID > Enterprise applications > [SMARTFENSE application].
  2. Go to Properties.
  3. Change Assignment required? to No.
  4. Press Save.

💡 Best practices

  • Confirm the user's status and activation in SMARTFENSE before ruling out a Microsoft Entra ID configuration issue.
  • Verify that the username in SMARTFENSE exactly matches the one in Microsoft Entra ID to avoid correlation failures.
  • Use the administrative login as a fallback method while resolving an authentication issue.
  • Discuss with the customer whether to assign access by groups or disable required assignment, based on their user management model.
  • Document in the customer's internal inventory which assignment option was configured.

 

Related to

Related articles