We have not chosen a platform. Is this relevant?
Yes, if Microsoft Fabric is one of the options you are considering. Much of the assessment, including source data, ownership, integration and operating model, is relevant whichever platform you choose. We then assess Fabric suitability for the agreed workloads. Comparing alternative platforms is outside the assessment’s scope.
Does the assessment require an existing Fabric environment?
No. Evidence can come from your current applications, databases, integrations and reporting services. Discovery is scoped to the systems and workloads relevant to the decision.
What if Fabric is unsuitable?
The report states that conclusion for the assessed scope, explains the evidence and identifies unmet requirements. Where evidence is incomplete, further validation is recommended before a platform commitment.
Will you fix the issues identified?
The readiness phase identifies, prioritises and defines acceptance criteria for remediation. Agreed changes can then be delivered within the engagement by Kilvora, working with your team.
How does this differ from the Transformation Blueprint?
The assessment establishes suitability, readiness and the brief for design. The Blueprint resolves the target architecture and documents the decisions and implementation specifications. Detailed workspace, layer, security and deployment designs belong in the Blueprint.
Can this be delivered as part of an embedded engagement?
Yes. Readiness is the initial phase of an embedded day-rate engagement or a fixed-scope delivery programme, with agreed outputs and review points before progressing into architecture and implementation.
Is the introductory call a paid assessment?
No. The introductory call establishes fit and enough context to propose a scope. Evidence collection, detailed analysis and recommendations form the initial paid phase of the engagement.