EDP Workspace Access
Choose the right way to use governed Enterprise Data Platform data in Microsoft Fabric and Power BI. Most teams should start with a shared semantic model or a curated lakehouse before requesting direct warehouse access.
Start With What You Need To Do
The best access level depends on the work your team needs to accomplish, how much modeling you want to own, and how much data governance support is required. Use this guide to narrow the request before contacting EDBI.
I need a trusted dataset for Power BI reports.
Use a curated model when you want approved relationships, measures, and refreshes already handled.
Best fit: Shared semantic model.
I need curated tables and more modeling flexibility.
Use a lakehouse when your team will combine EDP data with local sources or build your own semantic model.
Best fit: Lakehouse shortcut access.
I need direct SQL access to specific warehouse objects.
Use a governed warehouse slice when your team has an advanced analytics need that cannot be met through a model or lakehouse.
Best fit: Approved warehouse slice.
I work closely with EDBI on enterprise analytics.
Broad warehouse object access is rare and reserved for trusted partners working across institutional data domains.
Best fit: Full warehouse object access.
Access Levels
EDBI uses the least access needed for the work. All customer access to EDP tables is read-only, and EDBI manages platform development, pipelines, and production data warehouse administration.
| Access Level | Best For | What You Can Do | What To Know |
|---|---|---|---|
| Shared semantic model | Teams building Power BI reports from governed definitions. | Build reports from an approved model with prepared relationships, calculations, measures, and refresh patterns. | This is the recommended first option when the available model answers your reporting need. |
| Lakehouse shortcut access | Teams that need curated EDP tables in a Fabric workspace. | Use selected tables in a lakehouse, combine them with your own data, and build your own reports or models. | Your team owns more modeling and report design decisions. |
| Approved warehouse slice | Advanced users who need direct SQL access to specific approved tables or views. | Query a limited data warehouse slice for department analytics and reusable solutions. | Requires a clear business purpose, data steward approval, and a more detailed access review. |
| Full warehouse object access | Highly trusted enterprise analytics partners working closely with EDBI. | Read broad production warehouse objects for deep institutional analysis. | This level is uncommon and reviewed carefully because it exposes the most EDP data. |
What To Gather Before You Request Access
A complete request helps EDBI route your work to the right access level and avoid follow-up cycles.
- The business question or decision you are trying to support.
- The data domains, subject areas, reports, tables, or measures you think you need.
- The department, workspace owner, and primary contact for the request.
- The data steward or business owner approval path, if known.
- The expected users or group that should receive access.
- Whether you need Power BI reporting, Fabric workspace access, SQL querying, or consultation.
- Any sensitive data, row-level security, audience, or sharing considerations.
- Your timeline and whether the work supports a recurring process, one-time analysis, or new data product.
How To Request Workspace Access
Submit a request after you have a likely access level and the supporting details. EDBI will confirm the best path, review governance needs, and coordinate provisioning.
Choose the likely access level.
Start with the smallest access option that supports your work. If you are unsure, describe your goal and EDBI will help classify it.
Submit the request.
Include the business purpose, data needed, expected users, department owner, and approval context.
EDBI reviews the best fit.
The team checks stewardship, security, least-privilege access, and whether an existing data product already meets the need.
Access is provisioned and confirmed.
Approved access is typically assigned through a managed group so departments can maintain consistent access over time.
Common Questions
Do I need direct warehouse access?
Usually no. If your goal is reporting, start with a semantic model. If you need flexible table-level work in Fabric, start with a lakehouse. Direct warehouse access is for advanced use cases that require SQL against approved objects.
Can my team manage its own reports?
Yes. Fabric workspaces and Power BI reports can be department-owned, but access to EDP data remains governed and read-only.
Who approves data access?
Approval depends on the data domain, sensitivity, and intended use. EDBI will help identify the right steward or business owner when the approval path is unclear.
Can I request help choosing a path?
Yes. If you cannot tell whether you need a model, lakehouse, or warehouse slice, submit the business question and the team will recommend the most appropriate solution.