It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda SecureEdge

How to Connect Your Microsoft Entra ID or LDAP with SecureEdge Access

  • Last updated on

Barracuda SecureEdge Access allows administrators to select either Microsoft Entra ID (formerly Azure Active Directory) or LDAP and sync with Zero Trust access. You can also configure custom client networks with respect to each point of entry. The Barracuda SecureEdge Agent running on the client connects to the SecureEdge unified cloud UI. In addition, you can enforce agent web filtering policies to the web traffic that the clients connect to via the SecureEdge Agent in order to establish a secure connection to access internal and external company resources. 

Before You Begin

Connect a Microsoft Entra ID/LDAP

  1. Go to and log in with your existing Barracuda Cloud Control account.
  2. In the left menu, click the Tenants/Workspaces icon.
  3. From the drop-down menu, select the workspace your SecureEdge Access should be configured for.
  4. In the left menu, click the Access icon, and select Settings.
  5. The Settings page opens. Specify values for the following:
    • Tenant Domain – From the drop-down menu, select the tenant domain you want to sync with the Zero Trust Access service. You can select either Microsoft Entra ID or LDAP.

      Note that changing the Microsoft Entra ID will not revoke access to users, but it keeps them from proceeding with the initial authentication.

    • DNS Suffix – Enter a DNS suffix to be used for your client network. 
    • In the ACCESS AGENT NETWORK CONFIGURATION section, specify a value for the following:
      • Manual Configuration – Click to enable/disable. When enabled, specify values for the following:
        • Client Network – Enter the network used for the clients. Defining a custom client network is mandatory. With the client network default value, routing will not work and the SecureEdge Agent will not connect to any resources that are not directly connected to it. You can optionally configure the client network as a private IP.

        • Pool Bitmask– Enter the bitmask of the network pool to allocate each agent access point.

          It is not mandatory to change the default values for the custom client network range and pool size. Note, however, that if you configured a custom range and pool size, you are not allowed to go back to the default value. 


  6. Click Save.
  7. In the CLOUDGEN FIREWALL CLIENT CERTIFICATE section, click Download certificate.
  8. Install this root certificate on all your clients to assure parallel operations with CloudGen Firewall client-to-site and SecureEdge Agent Access.