Customer 360 Enterprise Data Platform — Denodo on Azure · View 01 of 39 · Context and scope
Decisions
- Read-only against every system of record. The platform never writes a customer attribute back into Salesforce, SAP or ServiceNow — remediation is routed to the owning system as a task.
- Five sources are federated live and three are physically landed. That split is not convenience; it follows the freshness contract on view 17.
- Microsoft Purview federates the Denodo catalogue rather than replacing it, so the estate-wide search works without a second definition of Customer360.
Assumptions
- Entra ID is the single identity provider for all human access; no local Denodo accounts exist outside break-glass.
- Source systems can sustain the federated query load quantified on view 12; this must be confirmed by workload testing before Phase 3.
- Contact-centre volume of 9,400 calls a day at 60 requests per second peak, 1,100 Power BI report consumers, 500 concurrent sessions.
Out of scope
- Campaign execution, CRM customisation and case management — the platform reads their output, it does not replace them.
- Customer-facing self-service portals; the partner portal is the only external consumer in scope.
- Product 360, Supplier 360 and Risk 360 — the pattern is designed to extend to them, but nothing here is built for them yet.
