Bulk Provisioning and Updates: Directory Object Management in Bulk from Configurable Data Sources
PeopleNexus allows you to delegate bulk user, contact, group, and computer creation and updates in Active Directory, Azure Active Directory, and G Suite. Bulk management releases IT from mundane, error-prone data entry tasks. Data in your directories becomes cleaner and more consistent.Schedule a Demonstration Request a Quote
Bulk Actions on Multiple Platforms
Perform bulk provisioning, deprovisioning, and update actions in Active Directory, Azure Active Directory, and/or G Suite individually or all at once.
Provisioning involves creating new things and configuring what happens when a duplicate is encountered.
- Active Directory Bulk Provisioning
- Azure Active Directory (Office365) Bulk Provisioning
- G Suite Bulk Provisioning
Bulk management involves updating objects in bulk. This includes discrete actions such as cloning, moving, or deleting an object.
- Active Directory Bulk Management
- Azure Active Directory (Office365) Bulk Management
- G Suite Bulk Management
Deprovisioning is what you do when an object is no longer needed at that moment in time.
- Active Directory Bulk Deprovisioning
- Azure Active Directory (Office365) Bulk Deprovisioning
- G Suite Bulk Deprovisioning
Grab Data From Multiple Data Sources at Whatever Frequency you Want
Funnel data into your provisioning and update processes from multiple data sources. Schedule processes to run with whatever frequency you want to run them “hands-free” or run ad-hoc jobs manually. You define the fields that come in from your data source and how they are combined and used to fill attributes in your directory.
Complex Updates Made Easy
Configurable business rules make it so that setting or a change to a single attribute can have far-reaching effects. For example, a bulk action that changes a user’s location can cascade into the user’s OU, group membership, and several attributes changing in the backend according to business rules you’ve set up. This makes your bulk activities less error-prone and easier to configure.
Transform Input Data Any Way You Want and Put it Where You Want
Transform data from your bulk data sources. Typical examples might include formulating a user’s email address based on their name or a group’s name based on its location and the title of its manager. Complex transformations are also possible. For example, input data might contain a student’s grade level and have that translated into them being created in an Active Directory OU and/or G Suite Org Unit Path by their graduation year which was calculated from their grade level and the current date.
After your data is exactly how you want it, you can put it into any attribute you want no matter the object you’re creating and on what platform it is created.
Configure business rules to help organize and complete your directories the way that you want. This is especially important when performing bulk operations. Business rules can be set up so that certain inputs to the provisioning or update process can automatically control how objects are created or updated. For example, when provisioning a user, you might have their job title and/or location affect what OU they get put into, how and if their home shares, login scripts, profile paths, group membership, etc. are created. You could even, as an example, set up business rules to control group membership but also make choosing additional groups part of your provisioning input data.
Business rules can be triggered by any input you desire in the provisioning process and can control things like:
- The Active Directory OU or G Suite Org Unit Path where an object is created
- A user or contact’s group membership and licensing (for example their Azure Active Directory licensing)
- A group’s user membership
- A user’s home shares, profile path, login script, etc.
- An object’s manager
- How a user’s password is generated: generate a password randomly, with values that depend on inputs to the process, to a combination of these, or a fixed value
You can have these under the control of business rules or also optionally make them inputs from your data sources.
You control what constitutes a duplicate and what happens as a result. Options include updating the record, ignoring duplicates (but being notified about it optionally), and always creating objects (with the software automatically creating a unique name for you). Duplicate handling is important during bulk processes. Often bulk processes are called on to both insert and update directory data.
Record Keeping and Notifications
Optional notifications when an object is provisioned or updated. Often with bulk processes, however, you only want a notification if an exception occurs. Configuring this is also possible. Email templates are fully configurable and can include raw or transformed data from the provisioning process. You can have different emails go out to different people– as many as are needed. Full record keeping of provisioning actions by user, object, and platform.