Data Engineering Role?

[memurphyiii]

Hi, I'm working through some LinkedIn tutorials and one step is to change to a "Data Engineering Role" to accomplish some of the steps. I am in a Fabric Trial and I don't see this role. What am I missing? Thanks.

[Vinodh247 · Accepted solution]

In Fabric, the “Data Engineering” role is not something you manually assign or enable in a trial. It is just a persona-based experience switch in the UI, not an actual permission or role like in AAD. In a Fabric trial, this option may not appear if your tenant settings, UI version, or feature rollout do not include the role switcher yet. You are not missing any access, just proceed by directly using the Data Engineering workloads like Lakehouse, Notebooks and Data pipelines, which are already available in your environment.

[memurphyiii]

Thank you. Your comment helped to support the previous comments and allowed me to get past the issue!

[arabalca · Accepted solution]

Hi @memurphyiii ,

Great question! This confuses a lot of people coming from other environments. Let's clear it up from the ground up.

What the tutorial calls "switching to the Data Engineer role" is not a security role or a permission — it's a workload experience switch within Microsoft Fabric. Let's break down what that means

What is Microsoft Fabric?

Microsoft Fabric is not a single tool — it's a unified platform that brings multiple capabilities together under one roof. Think of it as a building with several specialized floors: you can move between them depending on what you need to do at any given moment.

Each "floor" is what Fabric calls a workload or experience, and you select it from the experience switcher in the bottom-left corner of the screen.

What workloads are available?

- Power BI — Build reports, dashboards, and semantic models. The most familiar entry point for most users.

- Data Factory — Data orchestration and movement. This is where Pipelines, Dataflows Gen2, and Copy Jobs live.

- Data Engineering — This is the one your tutorial is referring to. Inside this workload you'll find:

  - Lakehouses — unified storage for files and Delta tables

  - Notebooks — Spark code (Python, Scala, SQL) for data transformation

  - Spark Job Definitions — run Spark jobs in production

  - Pipelines — also available here to orchestrate data flows

- Data Science — ML-oriented notebooks, experiments, and registered models. Shares many elements with Data Engineering but focused on data science workflows.

- Data Warehouse — Full T-SQL warehouse with support for views, stored procedures, and classic relational queries.

- Real-Time Intelligence — For streaming data. This is where you'll find Eventstreams, Eventhouses (KQL), and real-time dashboards.

- Database 

- Fabric IQ

Pic to learn workload

How do I switch experiences?

In the bottom-left corner of the Fabric interface, you'll see the name of the currently active workload (for example, "Power BI"). Click on it and the experience switcher will appear with all available workloads. Select Data Engineering and you're good to go — you'll be in the experience the tutorial is asking for.

What if the workload doesn't appear?

This happens often in trial environments. Check these three things:

1. Your workspace must have a Fabric capacity assigned (trial or paid). A workspace on shared Power BI capacity does not unlock all workloads.

2. Fabric must be enabled at the tenant level. An admin needs to have turned it on in the Admin Portal under Tenant settings → Microsoft Fabric.

3. Make sure your workspace is not a classic Power BI workspace, but one created within the Fabric environment.

If my comment helped solve your question, it would be great if you could like the comment and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.

Thanks a lot, I really appreciate it.

[memurphyiii]

Thank you. I appreciate the explanation and it helped me to recognize the role of workloads in workspaces. This led me to understand and review the workloads list. Once I did that, I saw the data engineering workload that I had been looking for and when I selected to use a sample data space, Fabric automatically created a lakehouse with the appropriate configuration and data similar to what I was seeing in the tutorial. It boiled down to needing the access the workload in a different manner from what was explained in the tutorial but I'm past the issue now. Thanks again!

[Vinodh247 · Accepted solution]

In Fabric, the “Data Engineering” role is not something you manually assign or enable in a trial. It is just a persona-based experience switch in the UI, not an actual permission or role like in AAD. In a Fabric trial, this option may not appear if your tenant settings, UI version, or feature rollout do not include the role switcher yet. You are not missing any access, just proceed by directly using the Data Engineering workloads like Lakehouse, Notebooks and Data pipelines, which are already available in your environment.