Active Directory and Nintex. If you're like me, these words may have inspired fear in your heart. I don't manage our Active Directory (AD), and I don't know much about it so when I ran into a requirement to create AD entries with a Nintex Workflow, I panicked—this was going to be difficult! Right?!
What is Active Directory?
Active Directory is a database that stores all of your organization’s user accounts and their passwords. Protected in one centralized location, it allows you to manage those user accounts and passwords along with various other details, such as department, role, and manager. When working with Nintex Workflow, Active Directory speaks to the workflow and vise-versa to provide account information.
Adding a New User to Active Directory Using Nintex
Even if you've never touched an AD entity in your life, you can do this. It takes ONE action in Nintex:
Consider this for a second: undoubtedly in your corporation (and many others), a new employee is provisioned only after IT receives an alert from HR, perhaps via email or perhaps via (ugh) paper. IT will provision the user by copying and pasting, or by typing directly into the AD fields. IT becomes the middleman in this operation.
Back to what I was saying earlier: one action. Defined once by the hero that sets up this Nintex workflow.
All you need to start is a SharePoint list, the AD address (and associated Organizational Units), and a valid account with permissions to provision in AD. Here’s a breakdown of how to accomplish this:
1. Create a SharePoint list with columns for a name, and an email.
I've named mine AD_Name, and AD_Email, so I know what they're going to be used for.
2. Create a blank Nintex Workflow and drag in the "Create AD User" action.
Be sure that you also have an account name and password that has the appropriate security settings to create Active Directory accounts.
The LDAP path may seem confusing, but your AD administrator can help you out with establishing it. Keep in mind that you can use variables in place of some of these, if – for example – a particular location or role requirements a different OU:
3. Run the workflow on a list item (or set it to automatically run on any new items)
Tah-dah! -- you have a new AD account. Don't believe me? Use your people picker and enter the name you've provisioned - you'll see it pop up!
However, let's be honest - automatically creating an AD account based on one or two pieces of data isn't a great practice. Adding some error handling and checks would make this workflow a great addition to any HR department and save many hours, dollars, and potentially a large number of trees! To learn more about Nintex Workflows and how they can help drive the adoption of your Intranet check out this video.