Onboarding Solution Assessment and Action Plan
Global software and cloud solutions provider
In short
Why do Power Platform updates fail when you only have a production environment?
The onboarding solution is a global onboarding solution that people and culture teams rely on. It ran in a single production environment, so every hand edit added a hidden layer that blocked later updates. We assessed the whole solution and gave the client a clear action plan to bring it back under control.
Results in numbers
- connection references
- c. 30
At a glance
- Production-only setup found, no development environment in use
- About 30 connection references, target one per app
- Seven step action plan to a dev, test and prod path
The client
The client is a global software and cloud solutions provider. The onboarding solution belongs to its HR digitalisation work around the HR system, and combines canvas apps, a model-driven app, flows, Excel files on OneDrive and Dataverse tables.
What it was costing them
- Updates that do nothing: edits in production created unmanaged layers, so imported fixes sat underneath and never became active.
- Fragile data: Excel files on OneDrive were the main database, so a wrong data type or a missing column could stop a flow.
- Connection sprawl: around 30 connection references made deployment and support hard.
- Silent failures: flows had no error handling, so errors inside loops went unseen.
What we did
We reviewed environments, data, publisher, connections, four apps and the flows, then wrote a step by step plan to fix them in order.
- A working lifecycle: add a development environment and move to dev, test and production.
- A way out of the layer trap: copy the managed components into a new solution, remove the managed originals and export the result to development.
- Reliable data without extra licences: move Excel data to SharePoint lists, one site per environment.
- Simple deployment: one connection reference per app, and a named publisher with a meaningful prefix.
- Safe configuration: turn IDs and email addresses held in flow variables into environment variables.
- Faster flows: filter in the action that reads the data, and check whether the flow is active first.
- Visible failures: wrap key actions in a scope and send a message when it fails.
- Licence awareness: the model-driven app and its Dataverse table need premium licences for every user, so sharing stays with the few who run it.
Results
- Written assessment issued in April 2023 covering four platform areas, four apps and four flow patterns.
- Seven step action plan that starts with a development environment and ends with the cleanup of apps and flows.
- Result: with a dev, test and production path, updates take effect on the first import instead of hiding under an unmanaged layer.
The risk most teams miss
The month three risk is a second round of drift. Once a development environment exists, the first urgent fix is made in production and the layer problem returns. The plan prevents it with managed deployments only, environment variables per environment and a rule that nobody edits in production.
What we would add today
Improvements we would add on top of what is live.
- Move the onboarding tables to Dataverse and license the HR users, with row-level security by legal entity.
- Promote between environments with Power Platform pipelines and Managed Environments, replacing manual export and import.
- Run flows under a service principal with connection references, and log failures in a Dataverse table.
- Draft induction plans from the leader's answers with an AI Builder prompt, for review before sending.
Technology
Power Apps (canvas and model-driven), Power Automate, Dataverse, SharePoint Online, Excel Online, Microsoft Teams, Outlook.
Tell us where your Power Platform solution is edited today, and we will tell you what it is hiding and how to fix it.
Products and capabilities
- Power Apps
- Power Automate
- Dataverse
- ALM
- solution assessment
- environment strategy
- connection references
- unmanaged layers
The service behind this work
Power Platform governanceThe service behind this work
Power Platform development
Related use cases
HR and peopleGlobal Onboarding Automation
New joiners at a global company expect the same welcome in every country. When people and culture teams send it by hand, steps get missed and the first week depends on who is paying attention. We automated the journey from offer acceptance to six months with the onboarding solution, driven by the HR system.
- 25+
- message types
- 20 min
- saved per joiner
Buddy App, Onboarding App and Hiring Manager Academy
When onboarding information is scattered across mails and documents, new joiners lose time, and buddies and hiring managers repeat the same explanations. At the client we built three Power Apps, the Buddy App, the Onboarding App and the Hiring Manager Academy, as part of a programme of more than 150 automations and apps.
- 15+
- new joiners a week
- 150+
- apps and automations
Payroll and HR Process Automation with Power Automate RPA
Three key payroll processes covering 15 countries kept 18 full-time employees busy with manual data processing, GDPR-sensitive employee files took 30 days to handle, and a changed promotion letter took a week. We automated all three with Power Automate and cut manual data processing by 46%.
- 46%
- less manual payroll work
- 3 days
- per GDPR case, was 30 days
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.