Skip to content

Bulk Onboarding of Servers and Users into a Privileged Access Tool

Technology services company, Middle East

In short

How do you onboard many servers and users into a privileged access tool at once?

Adding servers and users to a privileged access management tool one at a time is slow, and one wrong port or user type can break a connection or leave a server unprotected. The client had more than 100 entries to onboard. We put in place a bulk process that prepares them in a checked sheet and loads them in one import.

Results in numbers

entries per batch
100+
import template columns
45

At a glance

  • More than 100 entries to onboard in one batch
  • About 20 connection types in scope
  • One 45-column import template

The client

The client is a technology and digital services company based in the Middle East. Its IT team manages many servers and network devices, and uses a privileged access management tool to control who reaches them.

What it was costing them

  • Manual effort: each server, connection type and user needs its own entry, repeated more than 100 times.
  • Typing errors: a wrong port, domain or user type breaks a connection or leaves a gap in control.
  • Credential exposure: the import template has fields for credentials, so a copy left on a shared drive is a security risk.

What we built

We built a repeatable bulk onboarding process built on the tool's own import template and a controlled source sheet.

  • One import instead of many: the 45-column service import template is filled once and loaded in bulk.
  • Fewer wrong entries: a lookup sheet of about 20 connection types and two user types, so every row uses a valid ID.
  • Clean input: a working list of servers and the people who need access, checked for gaps and duplicates before the import.
  • Safer secrets: credentials are supplied by their owners at import time and the filled sheet is deleted after loading.
  • Proof it worked: a post-import check compares rows loaded with rows in the sheet.
  • Repeatable next time: a named reviewer signs off each batch and a short runbook guides later ones.

Results

  • The working list holds more than 100 entries and the import template has 45 columns.
  • Preparing and loading a batch of this size takes hours instead of days.

The risk most teams miss

Bulk loads fail quietly. By month three the sheet has drifted from the real servers: some retired, owners changed, and the tool still lists access that no longer exists. We add a quarterly review against the source of truth.

What we would add today

Improvements we would add on top of what is live.

  • Keep the server and user inventory in Dataverse, with a Power Apps request form so onboarding starts from an approved request.
  • Store secrets in Azure Key Vault with service principal access, so credentials never sit in a spreadsheet.
  • Record who requested and approved each onboarding with Power Automate approvals and Dataverse auditing.

Technology

Excel, the tool's bulk import template, Power Automate, Power Apps, Dataverse, Azure Key Vault.

Tell us how many servers and administrators you still have to add to your access tool, and we will tell you how to load them in one controlled import.

Products and capabilities

  • Power Automate
  • Azure Key Vault
  • privileged access management
  • bulk import
  • IT operations
  • Excel

Related use cases

IT and platform teams

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.