Skip to Content

FAQ

Version 2.1 by Dimitri Rupp on 2026/06/11 09:16
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.
On this page

FAQ — Microsoft Fabric in SPL Tele

Information

Frequently Asked Questions rund um die Fabric-Implementierung bei SPL Tele.

General information

Why Fabric?

Microsoft Fabric brings together data engineering, data science, real-time analytics, and business intelligence into one unified platform. It simplifies data workflows by eliminating silos and offering seamless integration across tools like Power BI, Synapse, and Data Factory. With built-in OneLake storage, governance, and AI capabilities, Fabric empowers teams to build, share, and consume data products faster — with fewer handoffs and stronger compliance.

Data in Fabric

What data is available in Fabric?

In SPL, data available in Fabric comes from curated Lakehouses managed by the Fabric team. These Lakehouses contain cleaned, structured datasets ready for reporting and analysis.

These include data from:

If you need access to specific datasets, please reach out to the Fabric team.

Getting data into Fabric

What are the data orchestration methods in Fabric?

Fabric supports several orchestration methods to help teams automate and manage data movement and transformation:

MethodWhen to useDetails
Dataflows Gen2Low-code data preparation. Ideal for ingesting and transforming data from various sources into Lakehouse.→ Fabric Dataflows
NotebooksCode-based transformations using Python, SQL, or Spark. Best for complex logic or ML workflows.→ Fabric Notebooks
Data PipelinesVisual orchestration of activities like data copy, notebook execution, and conditional logic.→ Fabric Data Pipelines

Access and permissions

How is access to Fabric resources managed?

Access in Fabric is managed through workspaces and item-level permissions.

  • Workspace roles (Admin, Member, Contributor, Viewer) control what you can do across all items in that workspace.
  • In SPL, most users don't have direct access to the workspace.
  • For more granular control, item-level permissions can be set on individual Lakehouses, Notebooks, and Pipelines.

For details on workspace roles and Lakehouse-RBAC at SPL, see Fabric security for admins.

Decision-Helfer

flowchart TD
    Q[Welche Frage hast du?] --> A{Worum geht's?}
    A -->|"Was ist Fabric?"| Q1[General information
oben auf dieser Seite]
    A -->|"Welche Daten sind verfuegbar?"| Q2[Data in Fabric
Lakehouse-Liste]
    A -->|"Wie bringe ich Daten rein?"| Q3[Orchestration Methods
Dataflow / Notebook / Pipeline]
    A -->|"Wie bekomme ich Zugriff?"| Q4[Access and permissions]
    A -->|"Architektur verstehen"| Q5[Fabric for power users
Lernpfad]

    classDef q fill:#e3f2fd,stroke:#1976d2,stroke-width:1px
    class Q1,Q2,Q3,Q4,Q5 q

Naechste Schritte fuer Power-User

Related pages

Information

Migration footer
Source: FAQ (SharePoint)
Original author: Bukkerji Sreejith
Original last-modified: 2025-10-09
Migration date: 2026-05-24
Migrated by: Dimitri Rupp via ClaudeAI
Notes: EN-Original 1:1 (4 Frage-Antwort-Bloecke: Why Fabric / Data Available / Orchestration Methods / Access); Lakehouse-Liste mit direkten Cross-Links zu den 5 Sub-Lakehouses verlinkt; Decision-Tree-Mermaid + 'Naechste Schritte fuer Power-User' als Navigations-Erweiterung.

Verwandte Themen

Kuratiert — kann direkt im Editor ergänzt werden://

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:IT-Wiki.Makros.Verwandte-Themen.WebHome]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Status: Migriert — Team-Review ausstehend · Owner: (festlegen) · Letzter Review: 2026-06-11