The business problem
HR submitted employee information through a Teams app that emailed a CSV attachment. IT read the attachment, created the account, applied employee details, assigned licenses, and coordinated follow-up across other teams. A structured request still became a series of manual steps.
Changes and departures introduced more complexity. Information had to stay consistent across systems, and offboarding needed to happen at the right time and in the right order.
Automating the existing process
Kept the intake HR already used and connected it to Power Automate workflows. New-hire submissions created Entra ID accounts, populated directory attributes, and placed employees into the appropriate licensing groups. The workflows also recorded the request and notified the teams responsible for downstream setup.
Employee changes followed the same principle: use the submitted information to update the directory, then verify the result. Consistent department, region, and role information also supported the group membership and access policies that depended on those attributes.
Handling exceptions and approvals
Account creation and directory synchronization do not finish at the same instant. Follow-up automation checked whether the employee existed in the destination systems and retried when synchronization was still underway.
Offboarding followed a scheduled, technician-approved plan. Mailbox conversion and file handoff had to succeed before account disablement and license removal became eligible. The sequence was built into the automation rather than left to someone remembering a checklist under pressure.
IT retained verification, equipment preparation, approval of consequential changes, and responsibility for closing the work.
The result
Routine onboarding shifted from building accounts by hand to reviewing completed provisioning and handling the remaining physical tasks. HR kept a familiar process, while structured employee data flowed into the systems that needed it.
The improvement extended beyond time spent on each request: fewer fields needed re-keying, directory attributes followed consistent rules, and departures had an explicit schedule and dependency order.