Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More

Memberships

Azure Innovation Station

355 members • Free

Learn Microsoft Fabric

12.7k members • Free

3 contributions to Learn Microsoft Fabric
Advice Needed: DP-700 (Power BI) or DP-600 (Fabric)?
Hi eveyone, I’m trying to decide between DP-600 (Fabric Analytics Engineer) and DP-700 (Fabric Data Engineer). My main job is building and maintaining Power BI reports, and I already have solid experience with reporting and visualization. From what I understand: - DP-600 is more focused on end-to-end analytics in Fabric, including Power BI, semantic models, and pipelines. - DP-700 goes deeper into the data engineering side—data ingestion, transformation, orchestration, and monitoring. Given my role in reporting, should I take DP-600, or would DP-700 be better for future growth in Fabric? Thanks for your advice!
Question on Deployment Rules Automation in Microsoft Fabric
I’m working on a Microsoft Fabric setup where I have: - ~400 notebooks attached to 25 lakehouses, 15 warehouses, and 20 semantic models. - Deployment pipelines automated via Azure DevOps PowerShell scripting. The challenge: After deploying from Dev → Test, my Test lakehouse still references the Dev stage. I’d like to fully automate deployment rules using parameters, so the stage references update automatically. Question: Is there a way in Fabric to automate deployment rules in this scenario, or a recommended approach?
3 likes • Aug 16
This is a really challenge in Fabric right now. Deployment rules help with overriding notebook–lakehouse bindings, but unfortunately there isn’t yet a fully automated way to parameterize stage references across lakehouses, warehouses, and semantic models. For now, the best approach is usually a mix of variable libraries for environment values, scripted deployment rules (via API/PowerShell), and some post-deployment adjustments. Full parameterization support is on the roadmap, so hopefully soon we won’t need these workarounds.
Different Environments in Lakehouse in same Workspace in Fabric
Hi , I had question for Fabric Lakehouse. How to create different environments (test/dev/prod) for lakehouse for the same Workspace and how to create different environments for tables (test/dev/prod) for lakehouse-tables.
5 likes • Aug 16
Hi, you can’t directly create “environments” inside one Workspace, but you can simulate them: - Lakehouse level → create 3 Lakehouses in the same Workspace: one for Dev, one for Test, one for Prod. - Table level → if you only want 1 Lakehouse, then separate by naming tables (Customer_Dev, Customer_Test, Customer_Prod) or by schemas (dev.Customer, test.Customer, prod.Customer).
1-3 of 3
Daisy Shan
2
9points to level up
@fangqiang-shan-8338
Hi, I am Daisy Shan. Happy to connect: https://www.linkedin.com/in/daisy-s-06328324a/

Active 5d ago
Joined Nov 22, 2024
Powered by