Dubem Gbuzue
Identity and security consultant, and CTO at Frost Eagle. Based in Sydney, Australia.
I help organisations bring order to who has access to what, and why. I've led the technical delivery of identity governance and privileged access work across manufacturing, financial services, higher education and healthcare in Australia and New Zealand, working with IT and business leaders to turn HR and payroll data into access that is automatic, auditable and easy to defend.
Most of that work happens in hybrid environments, where Active Directory is still in the picture and the documentation stops well short of what production needs. My focus is on the decisions that matter to the business: what should happen automatically, who approves what, what happens when the data is wrong, and how to show an auditor the answer. Underneath that sit Microsoft Entra ID Governance, HR-driven provisioning, hybrid Active Directory and privileged access with BeyondTrust.
I write up what I find in the articles below, rebuilding every example in my own lab with client details removed. If you'd like help with something similar, see how Frost Eagle works, email hello@frosteagle.com, or message me on LinkedIn.
Articles by Dubem Gbuzue
628 users in AD, 180 in Entra, and one account that belonged to two people
Two small mistakes in a lab provisioning pipeline: a UPN expression that left spaces in, and an employee ID shared by two people. One hid most of my users. The other quietly merged two identities.
Moving custom attributes from Connect Sync to Cloud Sync? Check which app they belong to
A custom AD attribute synced into Entra ID gets a name that includes the ID of an app. Change sync engines and you can end up with a new app, a new name, and every rule that used the old one quietly pointing at nothing.
Why your Logic App can't set a hybrid user's first password
Graph will happily change a synced user's password from automation. The change just never reaches Active Directory, and the new starter is left with a password that doesn't work.
The 204 that does nothing: resuming Lifecycle Workflows from a second Logic App
A Lifecycle Workflows resume call can come back 204 No Content and still leave the task waiting. If a different identity is sending the callback, that is very likely why.
Following a new starter from payroll to Entra ID, one hop at a time
A walk through a hybrid HR-driven provisioning pipeline: what each hop does to a person's record, and where each one tends to break.