Forum Discussion
Self Service Platform inside Fabric
- 1 year ago
Hi ObungiNiels,
Thank you for your detailed query and for sharing your architecture. It's great to see such an interesting discussion taking place!
The answer provided by nilendraFabric was indeed correct. Additionally, I am including some more points to make it easier for you.
- Which Layers of Data to Provide in the Self-Service Space?
- Platinum Layer (Gold Shortcuts): As mentioned, providing access to the platinum layer ensures analysts work with clean, reliable data. This approach minimizes the risk of disrupting ETL processes.
- Silver Layer (Optional): If you decide to provide access to the silver layer, ensure you have robust governance policies in place to prevent misuse or misinterpretation of semi-processed data.
- Bronze Layer: Avoid exposing raw data to maintain data quality and consistency.
- How Should Data Be Made Available?
- One Lake Shortcuts: This method is efficient and cost-effective, ensuring centralized governance and performance.
- Direct Lake Mode: Utilizing Direct Lake mode for Power BI can provide real-time analytics, ensuring up-to-date insights for your analysts.
- Implement role-based access controls (RBAC) to ensure users only access authorized datasets.
- Use Microsoft Purview for data cataloging, lineage tracking, and sensitivity labelling to maintain compliance and transparency.
- Should Version Control Be Provided for the Self-Service Space?
- Yes: Version control is essential for accountability and traceability. Using Git-based workflows within Fabric notebooks or pipelines allows analysts to experiment safely while preserving rollback options.
- Encourage analysts to create composite models when augmenting existing semantic models with departmental data. This balances self-service flexibility with centralized governance.
- Maintain a clear distinction between production datasets (certified) and experimental ones (endorsed) using Fabric’s endorsement features.
- How Can Domains/Domain Controllers Be Used for Administration?
- Domain Ownership: Align datasets with business domains (e.g; finance, marketing) following a Data Mesh-inspired approach. Each domain team should manage its own data products while adhering to global governance policies.
I hope these additional points help you in conceptualizing your self-service platform. If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Thank you.
Hi ObungiNiels,
Thank you for your detailed query and for sharing your architecture. It's great to see such an interesting discussion taking place!
The answer provided by nilendraFabric was indeed correct. Additionally, I am including some more points to make it easier for you.
- Which Layers of Data to Provide in the Self-Service Space?
- Platinum Layer (Gold Shortcuts): As mentioned, providing access to the platinum layer ensures analysts work with clean, reliable data. This approach minimizes the risk of disrupting ETL processes.
- Silver Layer (Optional): If you decide to provide access to the silver layer, ensure you have robust governance policies in place to prevent misuse or misinterpretation of semi-processed data.
- Bronze Layer: Avoid exposing raw data to maintain data quality and consistency.
- How Should Data Be Made Available?
- One Lake Shortcuts: This method is efficient and cost-effective, ensuring centralized governance and performance.
- Direct Lake Mode: Utilizing Direct Lake mode for Power BI can provide real-time analytics, ensuring up-to-date insights for your analysts.
- Implement role-based access controls (RBAC) to ensure users only access authorized datasets.
- Use Microsoft Purview for data cataloging, lineage tracking, and sensitivity labelling to maintain compliance and transparency.
- Should Version Control Be Provided for the Self-Service Space?
- Yes: Version control is essential for accountability and traceability. Using Git-based workflows within Fabric notebooks or pipelines allows analysts to experiment safely while preserving rollback options.
- Encourage analysts to create composite models when augmenting existing semantic models with departmental data. This balances self-service flexibility with centralized governance.
- Maintain a clear distinction between production datasets (certified) and experimental ones (endorsed) using Fabric’s endorsement features.
- How Can Domains/Domain Controllers Be Used for Administration?
- Domain Ownership: Align datasets with business domains (e.g; finance, marketing) following a Data Mesh-inspired approach. Each domain team should manage its own data products while adhering to global governance policies.
I hope these additional points help you in conceptualizing your self-service platform. If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Thank you.