Skip to main content

Azure Active Directory Microsoft Entra ID

Microsoft Entra ID (formerly Azure Active Directory) stores information about objects on the network and makes this information easy for administrators and users to find and use. Microsoft Entra ID uses a structured data store as the basis for a logical, hierarchical organization of directory information.

Creating an Microsoft Entra ID connection

Use one of the following methods to make a connection:

Using OAuth

This method will not work if your Azure User Type is Guest.

Creating your connection

  1. In the Blink platform, navigate to the Connections page > Add connection. A New Connection dialog box opens displaying icons of external service providers available.
  2. Select the Azure Active Directory icon. A dialog box with name of the connection and connection methods appear.
  3. (Optional) Edit the name of the connection. At a later stage you cannot edit the name.
  4. Click Microsoft Entra ID to authenticate using OAuth.
  5. Sign in using your credentials.
info

Need admin approval? please refer to the Need Admin Approval guide.

Using App Registration

To create the connection you need:

  • A client ID
  • A client secret
  • A tenant ID

Obtaining the credentials

  1. Log into the Azure Portal.

  2. Go to the Microsoft Entra ID resource.

    Azure Active Directory Resource

  3. In the left-hand menu, click App registrations.

    App Registrations

  4. Create a new application registration or click on one of your existing applications.

    My App

  5. In the left-hand menu, click API permissions.

    API Permissions

  6. Click Add a permission and select Microsoft Graph.

    Add Permission

  7. Choose Application permissions and mark the permissions you wish to add.

    Application Permissions

    To support all of Blink's actions, these are the required application permissions:

info

As a best practice, request the least privileged permissions that your app needs in order to access data and function correctly. Requesting permissions with more than the necessary privileges is poor security practice, which may cause users to refrain from consenting and affect your app's usage. For additional information, refer to Microsoft Graph permissions.

Least privileged permissionsHigher privileged permissions
GroupMember.ReadWrite.AllDirectory.AccessAsUser.All
IdentityRiskyUser.ReadWrite.AllDirectory.ReadWrite.All
Group.CreateGroup.ReadWrite.All
User.ReadWrite.AllUser.ReadWrite.All
Group.ReadWrite.AllDirectory.Read.All
User.Read.AllSecurityAlert.ReadWrite.All
SecurityAlert.Read.AllGroupMember.ReadWrite.All
GroupMember.Read.AllGroup.Read.All
LicenseAssignment.ReadWrite.AllUser.EnableDisableAccount.All
User.ManageIdentities.All
  1. Click Add permissions to save the changes.

  2. Click Grant admin consent for <your tenant> on the API permissions page. Only admins can grant consent. Only admins can grant consent.

    Grant Admin Consent

  3. Confirm that the added permissions are now verified.

    Granted Admin Consent

  4. Navigate to Overview and Copy your client ID and tenant ID.

    Client ID &amp; Tenant ID

  5. Create a new client secret.

    Client Secret

  6. Copy the secret value.

    Client Secret

Creating your connection

  1. In the Blink platform, navigate to the Connections page > Add connection. A New Connection dialog box opens displaying icons of external service providers available.
  2. Select the Microsoft Entra ID icon. A dialog box with name of the connection and connection methods appear.
  3. (Optional) Edit the name of the connection. At a later stage you cannot edit the name.
  4. Select App Registration as the method to create the connection.
  5. Fill in the parameters:
    • The client ID
    • The client secret
    • The tenant ID
  6. (Optional) Click Test Connection to test it.
  7. Click Create connection. The new connection appears on the Connections page.

Using LDAP

Microsoft Entra ID supports administration using the LDAP protocol, allowing you to manage your workspace using Blink's LDAP actions instead of the Microsoft Entra ID integration.

In order to expose your Microsoft Entra ID workspace as an LDAP server, follow these steps:

  1. Set up an Microsoft Entra ID Domain Services managed domain.
  2. Access the domain controller's virtual subnet.
  3. If your runner is running on premises and connected to the Azure virtual subnet, your LDAP server URL is the domain controller's IP address.
  4. Otherwise, in order to use an external runner, you need to add a public IP to the virtual subnet and assign it to your domain controller.
  5. To create an LDAP connection to this server:
    • Use the IP address accessible to the runner as your URI, with ldap:// protocol, or ldaps:// if you enabled "Secure LDAP"
    • Acquire the Distinguished Name of a Microsoft Entra ID user who has permissions to the server. You can use dsquery on a connected Windows Server to obtain the full name of a user.
    • Use the password of the specified user. After activating your domain controller, the user should reset their password so that it is properly synced.

Interactive Tutorial Guides

You can also refer to the following tutorial guides for a more in-depth understanding of how to create a Microsoft Entra ID connection.