Microsoft Fabric Guidance
The Fabric provider will guide target selection and create understandable workspace and item lifecycles. It will not reduce Fabric to a generic provisioning call.
Choose the item from the workload
Section titled “Choose the item from the workload”| Need | Likely starting point | Review before choosing |
|---|---|---|
| Transactional relational application | SQL database in Fabric | Transaction behavior, compatibility, connectivity, scale, recovery |
| Governed relational analytics | Warehouse | Dimensional model, T-SQL surface, loading, concurrency, downstream BI |
| Spark, open formats, or mixed data | Lakehouse | Delta layout, notebooks, medallion design, engineering skills |
This is guidance, not an automatic verdict. The plan will record workload evidence, rejected choices, capacity assumptions, preview limitations, and unresolved questions.
Workspace and item lifecycle
Section titled “Workspace and item lifecycle”The provider backlog covers:
- validate tenant settings, capacity access, region, identities, and licensing;
- plan workspace purpose, naming, domain, roles, capacity assignment, and network controls;
- create or reuse items only after capability and dependency checks;
- bind environment-specific connections and parameters without placing secrets in source control;
- probe the item after deployment and record unsupported behavior;
- preview teardown, preserve shared content, and explain what cannot be recovered.
Git metadata, item definitions, data, connections, permissions, and capacity are different lifecycle objects. Reports must not imply that versioning one protects all the others.
OneLake shortcuts
Section titled “OneLake shortcuts”A OneLake shortcut references data in OneLake or an external source; it is not automatically a copied dataset. The plan must identify the target, physical data location, connection identity, permissions, network path, freshness behavior, and ownership.
Optional shortcut caching can reduce repeated cross-cloud reads for supported shortcut types, but it creates workspace cache behavior and retention settings that need to be reported.
Deletion needs especially clear language:
- deleting the shortcut object does not cascade to the target data;
- deleting files or folders through the shortcut can delete them at the target when the identity has permission.
Teardown must remove only the shortcut object unless the user separately approves a data-deletion operation.
Fabric Unified Admin Monitoring is a community solution in Microsoft Fabric Toolbox, not an officially supported Microsoft product. The intended flow is validate first, show what is healthy or missing, and preserve an existing deployment by default.
Installing, salvaging, upgrading, or repairing FUAM requires a user-reviewed action summary and explicit confirmation. Detection alone never authorizes replacement or deletion.
Fabric CI/CD
Section titled “Fabric CI/CD”Fabric Git integration currently supports cloud-hosted Azure DevOps, GitHub, and GitHub Enterprise. Support also varies by Fabric item and can include preview limitations. GitLab, Gitea, and Forgejo belong to the toolkit’s broader Git-provider backlog; they are not currently supported Fabric Git integrations.
The Fabric workflow will:
- validate the current supported-item matrix before connecting a workspace;
- separate source-controlled definitions from data, credentials, and external connections;
- preserve environment parameters and access controls;
- use deployment pipelines or APIs only where the item supports them;
- probe promoted items and retain deployment evidence.
Microsoft documents several CI/CD and automation approaches, including Git integration, deployment pipelines, APIs, and Terraform. Full item coverage and equivalent behavior across PowerShell, Bicep, Terraform, and Fabric-native routes are exploratory, not a committed parity claim.