State Ombudsman

Moving data off ageing on-premises systems risked gaps in security, retention and destruction. We built the governance framework first.

Why it mattered

A state ombudsman operates under regulatory requirements that do not soften because a migration is underway. Moving to Microsoft Fabric without a governance position first would have carried real risk: unclear retention, unclear destruction, and security gaps discovered after the data had already moved.

What we did

• Wrote the governance policy. Aligned to state frameworks rather than generic best practice.
• Ran a security gap analysis. Finding vulnerabilities before migration rather than after.
• Set retention and destruction policies. Cloud-ready and aligned with their legal mandates.
• Built the Fabric workspace. For data integration, curation and analytics.
• Documented it properly. Policy documents, architectural blueprints and training resources.
• Mapped the Purview roadmap. For data loss prevention and classification as the next step.

The difference it made

• Compliance with state regulatory requirements, with the risk of non-compliance reduced.
• A stronger security posture going into the migration, not after it.
• Centralised data producing insight rather than sitting in ageing systems.
• A foundation that scales as data volumes and obligations grow.