Technology evidence
Use the platform that fits the workload and the team that must own it.
Microsoft is a priority, not an exclusive boundary. The matrix distinguishes established depth, source-system context, and platforms that require an assigned qualified delivery lead.
Semantic models, DAX, Power Query, reports, governance, performance, release, and administration.
OneLake, lakehouse, warehouse, pipelines, workspace, capacity, deployment, and analytical workloads.
Architecture, SQL transformations, access, workload design, cost, performance, and BI integration.
Transformation, validation, automation, forecasting, orchestration, and controlled source integration.
EHR, practice management, claims, billing, scheduling, workforce, finance, ERP, CRM, and approved exports or interfaces.
Implementation or optimization requires an assigned qualified delivery lead and a documented project boundary.
Architecture and delivery depth are confirmed for each engagement before scope is accepted.
Existing estates can be assessed and integrated; deeper delivery requires a verified specialist in the engagement team.
Expansion rule