How Power Automate Eliminates Manual IT Provisioning from Day One
Stop provisioning accounts by hand. See how Trasol Technologies automated Microsoft 365 employee onboarding from a single form submission - zero manual IT steps.
New hire onboarding usually starts with an email. HR sends a note to IT, an admin reads it, and then manually creates the account, assigns a license, sets the department and job title, and emails the new hire their login details. It works - until the email is formatted differently than last time, the admin is in a meeting, or a field gets mistyped.
At Trasoltech, we replaced this process for a client's IT team with a single Power Automate flow: one structured form, zero manual Microsoft Entra ID steps, and a new hire account ready the moment the form is submitted.
An HR email is free text. It depends on the sender remembering every field, formatting it consistently, and the admin parsing it correctly on the other end. In practice, that means:
None of this is a tooling problem. It is a process problem, and it scales badly the moment hiring picks up.
We replaced the email with a Microsoft Forms intake and a Power Automate flow that takes a submission straight through to a working account.
| Step | What Happens |
| Form submission | Employee details captured in structured fields, not free text |
| Trigger | Power Automate fires on "new response submitted" |
| Username logic | Auto-generates a username, or uses a preferred one if supplied |
| Account creation | User created directly in Microsoft Entra ID |
| License assignment | Correct SKU applied via Microsoft Graph |
| Role & department | Job title, department, and office written to the user profile |
| Manager link | Reporting manager assigned automatically |
| Notification | Welcome email sent to the new hire |
| Audit log | Run recorded in a SharePoint tracker |
Not every new hire gets the same username pattern. Some organizations want firstname.lastname, others want to let the employee request something specific. We built a condition into the flow: if the form's "Preferred Username" field is left blank, the flow generates one from the employee's full name. If it is filled in, the flow uses it instead - normalized and ready. Either path lands in the same variable, so every step after it behaves identically regardless of which branch ran.
Rather than running account creation through someone's personal Microsoft 365 sign-in, we registered a dedicated Entra ID app for the flow, scoped to exactly the Microsoft Graph permissions it needs - User.ReadWrite.All and Directory.ReadWrite.All - with tenant-level admin consent granted once.
The flow authenticates as that app, not as an individual. Provisioning keeps working even if the admin who set it up is unavailable, and there is a clear, auditable trail of what the automation is allowed to touch.
Everything here runs on Microsoft Forms, Power Automate, and Microsoft Graph - already inside a Microsoft 365 tenant. No third-party automation platform, no extra licensing, no external service handling employee data mid-flow. For an IT team already standardized on Microsoft 365, that means one less vendor relationship and one less thing to secure.
If new hire provisioning at your organization still depends on an email and an available administrator, it is worth a conversation. We have built and deployed this exact pattern, and the approach extends just as easily to offboarding.
