How to Configure Single Sign-On in Azure Active Directory for Drip7

Use this guide to set up SSO for Drip7 with Azure AD, enabling users to authenticate using their organization credentials for seamless access.

‍

Steps:

Register Drip7 as an Application in Azure AD (Requires network admin permissions)

1. Open the Azure Portal and navigate to Azure Active Directory, then click on Enterprise Applications.

Note: Copy the Tenant ID now for later use.

2. Click on New Application.
3. Create your own application: In the pane, name it Drip7 and select to integrate with Azure AD.
4. Fill out the details: Choose supported account types based on your needs.
5. For Redirect URI, select "Single-page application (SPA)" and enter your Drip7 subdomain followed by ".drip7.com" (e.g., yoursubdomain.drip7.com).

‍

Set Up API Permissions:

1. Return to Azure Active Directory home and click on Enterprise Applications. Locate Drip7 (refresh if needed) and open its details.
2. Click on API Permissions.
3. Add a permission: Select Microsoft Graph, then Application permissions.
4. Search for “groupmember” and add GroupMember.Read.All (for group syncing).
5. Search for “directory” and add Directory.Read.All (for user emails).
6. Note the Application (client) ID and Directory (tenant) ID from the Drip7 app page.

‍

Configure the New Tenant in Drip7 (Requires admin permissions in Drip7):

1. In the Drip7 Admin Portal, open the Tenants tab. Select your tenant from the dropdown if managing multiple.
2. At the bottom, change the User/Password dropdown to Azure SSO.
3. Click "Configure Single Sign-On" to open the dialog.
4. Fill in: Application (client) ID, Tenant ID, and Redirect URL (same as in Azure, e.g., yoursubdomain.drip7.com).
5. Configure group syncing: Select AD groups to include or ignore in Drip7.
6. Check "Automatically Sync New Groups" if you want new AD groups added automatically to Drip7.
7. Save the configuration.

You can now log in at https://yoursubdomain.drip7.com using organization credentials.TipThis setup syncs groups and emails for notifications; test login after configuration to ensure groups reflect correctly in Drip7.

‍