Set up the foundation
Define a suitable workspace and permissions, then choose lakehouse or warehouse storage for the scenario. Show how OneLake relates to the items created and document the responsibilities for connections and data ownership.
Data & AI / Overview
DIGITAL CLOUD / Data & AI
Microsoft Fabric Quickstart
Define a small initial Fabric scenario. Connect a suitable source, validate the data path and document what a wider deployment would require.
Plan your solution01
Microsoft Fabric Quickstart
Understanding the solution
Microsoft Fabric Quickstart establishes a working path from one source to a useful analytical output. Digital Cloud combines configuration with guided explanation so your team understands workspace, storage and processing choices. Preparation confirms access, capacity and a representative dataset.
Microsoft Fabric brings data integration, engineering and analytics capabilities into one platform, with OneLake as a shared data foundation. A project should define workspaces, ingestion, transformations and reporting together. Capacity and governance decisions shape how that environment is used and operated. Useful analytics depends on consistent definitions and reliable source data. Connecting platforms is only part of the work: ownership, quality, access and reconciliation determine whether people can trust the result.
Capabilities and scope
Build the first data path
Connect the selected source and implement a manageable ingestion and transformation flow. Check row counts, key fields and update behaviour; record failures and the steps required to rerun processing.
Expose and explain the result
Create a small query or report that answers the agreed question. Review the data path together and record what must be strengthened for wider use, including governance, monitoring and release management.
A practical example
A team loads a selected order dataset, prepares consistent dates and customer keys, then publishes a simple view of monthly order volumes.
What your project can deliver
- A configured initial workspace and documented architecture choices.
- A working sample data flow with validation evidence.
- A handover walkthrough and prioritized production-readiness backlog.
The final deliverables, licensing and responsibilities are agreed for your environment before implementation.
02
Requirements and considerations
List sources, reports, decision makers and data-quality concerns. Agree refresh needs, access rules, capacity and validation checks before moving a prototype into routine use.
Microsoft Fabric Quickstart
Project priorities
Initial source
Validated pipeline
Expansion requirements
We begin with a conversation about the task, the people involved and the systems already in place. Together we identify what a useful result would look like and which dependencies need attention first. The agreed proposal sets the delivery boundaries, responsibilities and acceptance criteria.
Your engagement
How Digital Cloud can help
| Project phase | What happens |
|---|---|
| 01Prepare | Involve the relevant process owners and prepare a representative example. Agree on the questions to answer, the preparation needed and the information that can be used safely. |
| 02Review | Work through the agreed scenario with the team. Capture decisions, open questions and the technical or organizational changes needed to move forward. |
| 03Validate | Review the outputs together and assign next actions. A workshop or prototype informs the next decision; production implementation and continuing support are scoped separately. |
Microsoft Fabric Quickstart
Questions before you start
Is the Quickstart a complete production platform?
Its scope is a focused first implementation. Production requirements, additional sources and ongoing operations are assessed separately and documented as next steps.
What determines the cost and schedule?
The starting environment, integrations, user groups and agreed outputs determine the effort. We confirm scope and commercial terms before work begins. Software licenses, infrastructure consumption and ongoing support may be separate items.
What will we receive?
The proposal identifies the deliverables: these may include findings, a prioritized roadmap, a tested configuration, a prototype, documentation or training. We agree what is included and how completion will be assessed.
Can this work with our existing systems?
We review the actual applications, data sources and access requirements before recommending an integration. Dependencies and compatibility limits are recorded so the delivery plan reflects your environment.
What happens after the initial work?
You can use the findings to guide your own team or discuss a follow-on phase. Any maintenance, monitoring or support includes separately agreed service hours, responsibilities and response targets.
Product documentationMicrosoft Learn ↗