Every department sees a different resident
In a local authority, data is spread across separate systems: the contact center, billing, social services, education, engineering, business licensing, GIS and scheduling. There is no single source of truth for residents, businesses and properties, management reports depend on manual refreshes, and AI use consists of point tools with no common governance.
One platform solves all three together, and prepares the authority for governed use of artificial intelligence, for both residents and staff.
Nine layers, all on Microsoft
Each layer has a clear role, well-known tools and is owned by the authority. For the data layer, we analyze the alternatives, Microsoft Fabric versus Azure Native, including a five-year TCO, and recommend based on the authority's needs.
Six decisions that make the difference
Data at rest in Israel, AI processing in Europe
Some AI services are not available in the Israel Central region. Data at rest stays in Israel, and processing runs in a European region, with no cross-region transfer.
One governed knowledge index
Instead of each tool's built-in indexing: a single index in Azure AI Search, with permission filtering and personal data checks, consumed by every agent.
Separate agents for staff and residents
Copilot Studio for internal processes. Azure AI Foundry for resident service, with custom authentication, a custom interface and a voice channel.
A golden record without a third-party engine
National ID numbers, company registration numbers and property numbers allow rule-based matching on Microsoft services, with no license for a commercial MDM engine and full authority ownership of the code and the rules.
Resilience to outages
If the AI region is unavailable, channels automatically switch to a degraded mode that runs from Israel: forms, callbacks and SMS.
Authority independence
Every component lives in the authority's own subscription, as Infrastructure as Code in its own Git, including prompts, configurations and indexes.
From requirements to a working environment you own
Zooz-tech supports the authority end to end: architecture, technology and regulatory decisions, a work plan, a cost model and implementation.
A target architecture document and flow diagrams for every layer.
An analysis of alternatives for the data layer, Microsoft Fabric versus Azure Native, including a five-year TCO.
A data flow map and data type register for the Privacy Protection Officer: what is sent, what is stored, where and for how long.
A phased work plan, an effort estimate in hours and a timeline.
A licensing and consumption estimate for Microsoft products, with procurement staged by project phase.
Golden record design: matching, survivorship, the data steward process and ongoing operations.
The environment itself: code, configurations, indexes, documentation and operating procedures, owned by the authority.
The platform is the foundation. Services run on top of it
Frequently asked questions
What is a golden record?
A golden record is a single, unified record for each resident, business and property, built from all source systems, with cross-reference IDs for every system and rules that decide which value wins when sources conflict.
Where is resident data stored?
Data at rest is stored in an Azure region in Israel. AI processing runs in a European region, because some services are not available in Israel, and the data flow map is submitted to the Privacy Protection Officer.
Microsoft Fabric or Azure Native?
Both options are viable. We analyze them against the authority's needs, including five-year cost, and the other layers (APIM, Purview, AI Search, the agents) stay the same in both.
How does this comply with Amendment 13?
Through Purview for cataloging and classification, DSPM for AI, keeping personal data out of the index, permissions through Entra, and a complete data flow map for every component.
Is your authority planning a data platform?
We would be glad to present the architecture and the path to the first phase.