r/MicrosoftFabric • • Nov 13 '25

Discussion This is the FUCKING WORST Platform

0 Upvotes

I don't know what shit has gotten you all. But I'm fucking over it. 6 months of my life wasted, because I don't want this crap on my resume. I never want to see this technology in my life ever again. I plan to just write databricks, and make sure I understand the differences.

As a side meta discussion. Add a Rant Tag. because topics like mine are all-too-common because of the god-forsaken design on this ass technology.


r/MicrosoftFabric • • Mar 10 '25

Administration & Governance Fabric Git integration

3 Upvotes

The latest attack and misinformation on Fabric is that it doesn't have Git integration - so just posting this for reference. (Earlier today another guy also attacked Fabric because it "didn't have Data Factory" 🄱) https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration


r/MicrosoftFabric • • Nov 07 '25

Community Share Vibe coding in Microsoft Fabric

2 Upvotes

With all the hype around vibe coding, I thought to record a video of me vibe coding a data solution in Fabric.

Conclusion, AI WILL TAKE OUR JOBS we still have to learn best practices, the platform, the coding, etc :-)

Check the video here: https://www.youtube.com/watch?v=bh_zioFeCqg


r/MicrosoftFabric • • Apr 28 '26

Discussion Got a job saying i know fabric, which i don't... help

4 Upvotes

I worked as a BI developer mostly with power BI,dax,PQ, SQL. They use fabric, they have pipelines, notebooks the whole package which i have zero clue. Any crash course i can do to save my career? TY


r/MicrosoftFabric • • Aug 22 '26

Certification DP 700 strikes off my to do list.

0 Upvotes

Completed DP 700 second attempt.. scored 836.


r/MicrosoftFabric • • Oct 17 '25

Data Science Hit me with all the AI in Fabric

1 Upvotes

In 2 days I gotta hold a 5 minute presentation on AI in Fabric, preferably including also with a demo. I need all the ideas! My audience will be mixed, some people have used Fabric and Power BI, some have never seen it, some are developers in other technologies, some are business leaders. What’s all the AI-stuff in Fabric first of all? What should I say? What should I show? Hit me with all your ideas and links, I need all the help!


r/MicrosoftFabric • • Sep 12 '26

Certification Just passed the DP-600 with an 815/1000!

0 Upvotes

It took genuine effort and a few sleepless nights, but focusing on the core concepts really paid off.

Resources that helped:

  • Microsoft Official Learn (great foundational prep)

  • Online video courses and tutorials

These resources were solid for grasping tricky concepts, but direct hands-on practice in Fabric was what truly tied everything together.

Thanks to this community for all the constant insights!


r/MicrosoftFabric • • Jul 20 '26

Certification Certification regarding DP-800

1 Upvotes

If I don't pass the DP-800 exam, will I still receive any certificate for attempting it, or is it awarded only to candidates who pass the exam?


r/MicrosoftFabric • • Jun 19 '25

Discussion Job Opportunity: Fabric Architect

2 Upvotes

Company based in Arizona, but it’s a fully remote position within the United States

As a Sr. Data Architect/Consultant at MicroAge, you’ll serve as a subject matter expert across Microsoft Fabric and Azure data platform technologies, supporting both client solutions and internal architecture needs. This role blends strategic advisory with hands-on execution by guiding platform design, shaping solution planning, and building secure, scalable, and compliant data systems.

What You’ll Do: -Design modern data platforms using Microsoft Fabric and Medallion architecture principles. -Lead technical discovery, pre-sales strategy, and solution planning. Implement cloud-native data pipelines using Azure Data Factory, Synapse, -Databricks, and more. -Enable DevOps and CI/CD practices with Azure DevOps or GitHub Actions. -Ensure compliance with HIPAA, GDPR, and other standards. -Champion DataOps, performance tuning, and BI strategy with Power BI and DAX. -Act as an internal SME and mentor for MicroAge’s data platform evolution.

What You Bring: 7+ years in Azure data architecture or analytics engineering Expertise in Microsoft Fabric, Synapse, Data Factory, Databricks, and Power BI Proficiency in SQL, Python, and PySpark Strong communication and collaboration skills

Check out this job at MicroAge:

https://www.linkedin.com/jobs/view/4250742539


r/MicrosoftFabric • • Jul 13 '26

Community Share Meme Monday: Dashboard Deluge

Post image
6 Upvotes

The most dangerous meeting question: ā€œCan someone explain why all these numbers are different?" At the Microsoft Fabric + SQL Community Conference, you'll learn how teams are unifying data, eliminating dashboard chaos, and finally trusting the numbers.

Save your seat for FabCon Barcelona today.

#MSFTAdvocate | AI-generated actors


r/MicrosoftFabric • • Nov 14 '25

Discussion Newbie & ready to be that BITCH

0 Upvotes

Hey yall so I am about 4 months in to my Senior Business Data Analyst role. I have 0 background in any of this other than my one month HIM internship where I kinda learned what SQL and Power BI was and the bare minimum of how data analytics works In healthcare.

Long story short, they ended up hiring me after an extensive interview process where I basically showed them what I learned from getting the Google Data Analytics cert and how much I retained from the internship. It obviously impressed them because I’m now in a corner office doing my best lol

I don’t feel like I’m in over my head. I’m confident and know I just need to be a forever student. I’m taking the Fabric DP600 tomorrow and expect to pass. Upon hire, I was told I will become the Power Automate and Fabric expert. We have not implemented Fabric yet but plan to soon. Currently, I’m working with my mentor on ingesting data into Databricks and I’m learning ALL the languages along the way.

My question is what do I need to do to continue being an asset in this field? I want to make $$$$ and I want to make a name for myself sooner rather than later. I’m starting my MS IT Management in the spring and expect that to be a taxing journey.

Any and all advice is welcome and encouraged. I’m ready to make moves and be a data engineer/analyst/solutionist/ bad ass bitch.


r/MicrosoftFabric • • Aug 06 '25

Certification How Can I Pass the DP-700 Exam as a Fresher Without Prior Azure Certification or Fabric Experience?

0 Upvotes

Hey everyone,

I’m a recent engineering graduate and currently exploring the Azure ecosystem. I'm planning to take the DP-700: Designing and Implementing Data Solutions on Microsoft Azure exam. However, I could really use some guidance.

Here’s my current situation:

  • I’m a fresher with no prior work experience.

  • I haven’t done any other Azure certifications before.

  • I’ve been learning Microsoft Fabric tools (like Dataflows, Lakehouses, Pipelines, Notebooks, etc.) and I know how to use them.

  • BUT when it comes to scenario-based or business-context questions, I get confused due to a lack of real-world experience.

I’d love to know from anyone who has passed this exam or is preparing for it:

What resources did you find most useful (free or paid)?
How did you get better at handling scenario-based questions?
Are there any mock tests or case-study-based materials you’d recommend?
Should I go through the learning paths on Microsoft Learn alone or combine it with something else?

Any advice for someone in my position would mean a lot.
Thanks in advance!


r/MicrosoftFabric • • Dec 16 '25

Solved I have started my course on fabric today,while starting I am unable to create workspace

Post image
0 Upvotes

r/MicrosoftFabric • • Nov 26 '25

Discussion With the introduction of Microsoft Fabric, how will my role as a Power BI Administrator expand, and what new responsibilities or skill areas should I expect to take on?

0 Upvotes

Hi Microsoft Fabric team and community,

I am currently working as a Power BI Administrator, with key responsibilities in the following areas:

Essential Skills and Responsibilities

  • User and Access Management: Reduce over-privileging (e.g., too many workspace admins) and create new AD groups for new projects.

  • Workspace Management: Take over and manage workspaces directly from the workspace view, and create new workspaces for new projects.

  • Capacity Monitoring and Performance Tuning: Monitor capacity usage and perform performance tuning as needed.

  • Security and Compliance: Manage users through security groups rather than individual assignments.

  • Data Governance: Implement content lifecycle management to reduce the overall governance risk surface.

With the introduction of Microsoft Fabric, how does my role expand, and what new responsibilities or skill areas should I expect to take on?


r/MicrosoftFabric • • Oct 10 '26

Power BI Get report name

0 Upvotes

Need to run tests in pandas for 700 reports 200 pbi files / models.

Have the data but I don’t have report / tab name

Can I get that from API


r/MicrosoftFabric • • Jul 09 '25

Certification Should tests encourage and permit the use of AI

0 Upvotes

Hot take. If we are so heavily promoting the use of AI tools for development, why not allow their use during DP600 and 700?


r/MicrosoftFabric • • Jan 14 '26

Certification Successfully renewed my Fabric Data Engineer certification — wanted to share with fellow Redditors!

0 Upvotes

I highly recommend taking this certification as soon as you’re eligible. It’s a great way to validate your skills and stay up-to-date with the latest in Fabric.


r/MicrosoftFabric • • Sep 04 '26

Discussion Microsoft keeps making things I like unnecessarily difficult to love

0 Upvotes

Disclaimer: AI helped with the English translation and syntax checks. The ideas, structure, text, and occasional weirdness are mine, for better or worse.

Today feels like a good day to publish some of my scribbles about working with Microsoft Fabric and the ecosystem built around it, all designed to make our lives ā€œeasier.ā€

I genuinely like GitHub Copilot.

Especially when working with Microsoft Fabric and Data Engineering.

It helps me focus on architecture, business logic, data models, SQL, notebooks, pipelines, and all those wonderfully specific problems that usually appear shortly after somebody says: ā€œThis should be quite simple.ā€

Before Copilot, snippets in DataGrip and Redgate SQL Toolbelt were my heroes. Like, for real.

I built templates with variables and placeholders for recurring SQL patterns. I collected useful fragments, copied them into the next project, and carefully replaced everything that belonged to the previous customer. They felt incredibly efficient.

Today, I look back and wonder how I managed to live with such antiquated technology.

Then, somewhere deep inside, my subconscious starts knocking. It reminds me that I had to walk through the valley of tears called learning. I had to write things myself, get them wrong, understand why they were wrong, improve them, and eventually build those snippets because I understood exactly which repetitive work I wanted to avoid.

Without that journey, I would not be where I am today.

And somewhere further back, another thought quietly asks:

What about future Data Engineers? Will they understand what the machine produces for them? Will they understand the difference between SQL that runs and SQL that belongs in a maintainable data platform?

Will they recognize a good data model, a bad data model, and a beautifully generated solution to the wrong problem?

Will they understand why Fabric code works in one workspace and fails in another?

Or will understanding slowly become optional as long as the notebook completes, the pipeline turns green, and the tests remain sufficiently optimistic?

I do not have a final answer.

For now, Copilot is very good at taking repetitive work away from me. It can help with SQL patterns, notebook structures, documentation, metadata-driven development, variable libraries, naming conventions, and the small adjustments that used to consume a surprising amount of time.

This gives me more time to think about the actual platform.

  • Where should business logic live?

  • Which part belongs in Silver and which belongs in Gold?

  • Which objects should be reusable?

  • Which dependencies have we created?

  • What will happen when the solution moves into another workspace, tenant, or environment?

And, perhaps most importantly:

  • Will anybody still understand this architecture six months from now?

We use repository context, documentation, custom instructions, and the other mechanisms available to help the model understand what we are building.

Errors still happen.

That is understandable. It is an LLM, not an Oracle (no pun intended).

Although both have historically produced confident answers based on incomplete context.

My issue starts somewhere else. I want to understand what Copilot is doing. When "Auto" selects a model, I want to see which model was selected. I want to understand why it was selected and what that decision means for quality, latency, and cost.

Right now, Auto looks like a harmless and convenient option in a dropdown. Behind that dropdown, a technical and economic decision is being made on my behalf.

That decision should be visible while I am working.

  • Show me the selected model.

  • Show me why it fits the task.

  • Show me the expected cost category.

  • Show me when a small and efficient coding model is enough.

  • Tell me when the task really needs something larger.

We already have models such as MAI-Code-1.1-Flash. It is fast, surprisingly capable, and affordable enough for many everyday development tasks.

That is exactly the kind of model I want Fabric developers to understand. Every task has a different shape. Generating a familiar SQL pattern is different from reviewing the architecture of a metadata-driven ingestion framework. Explaining a notebook cell is different from analysing dependencies across workspaces.

Creating documentation from an existing structure is different from designing the structure itself.

The same model does not have to be the best economic and technical answer to every one of these tasks.

Developers should understand this without studying model documentation, request multipliers, context windows, editor modes, policy settings, and the financial personality of every option in the model picker.

The way Copilot is used matters as well.

Inline suggestions, chat, agents, editor windows, programming languages, and task types create different situations. A specific model may be the better choice. A particular editor context may matter. Auto may make a perfectly good decision.

The interface rarely tells me enough about it. This feels familiar. I had a similar discussion when Capacity Unit licensing appeared in Microsoft Fabric. The technology was powerful. The possibilities were exciting. The concept made sense. Understanding which workload consumed capacity, when it consumed capacity, and how an architectural decision affected the bill was considerably less exciting.

A notebook, pipeline, Warehouse query, semantic model, or enthusiastic experiment could suddenly turn into an educational experience for the finance department.

And here we are again.

As an Xbox player who is now rather pleased to have bought one on day one after seeing last week’s prices, another question comes to mind:

  • While we are all asking for more efficiency, are we repeating the old ā€œmore ironā€ mistake from the server-farm era?

  • Demand increased, so we added more hardware.

  • More servers.

  • More memory.

  • More capacity.

At some point, infrastructure growth became the answer to problems that might also have deserved better architecture.

Fabric should already have taught us something here.

  • Scaling capacity is useful.

  • Understanding workload behaviour is useful.

  • Designing an efficient platform is even more useful.

The same principle should apply to AI models.

Efficient model selection should lead to efficient use of compute and memory. And by memory, I mean RAM, before my subconscious starts knocking again.

Using the right model for the task should result in better prices, more available performance, or simply more useful work from the same infrastructure.

A large reasoning model for every task may feel powerful. Adding another server to the rack did too, though.

Increasing a Fabric capacity can create a similar feeling. The problem disappears.

At least until somebody looks at the utilisation, the electricity bill, the Azure invoice, or the next capacity size.

Auto could help us avoid repeating the same pattern with AI. It could select a model that solves the problem well while using the resources the task actually requires. A small model for familiar and repetitive coding tasks. A stronger model for complex reasoning, architecture, and unfamiliar problems. More expensive machinery where it creates more value. Less expensive machinery where it already does the job well.

I simply want to see that happening. Because transparency would help us learn.

  • It would help developers understand which models work well for SQL, notebooks, Fabric artefacts, documentation, reviews, and architectural reasoning.

  • It would help teams create sensible guidelines.

  • And it would help us improve those guidelines when the technology changes again, which it certainly will, probably shortly after we finish documenting it.

GitHub Copilot can make Fabric and Data Engineering work significantly more efficient. Many things work extremely well. I enjoy working with it, and I want my engineers to use it intelligently and confidently.

Microsoft has built something I genuinely like. It could be something I love. Somehow, Microsoft keeps making that unnecessarily difficult.

Innovation belongs at the forefront. As a developer and architect, I enjoy trying things before most other people do. Exploring new approaches is part of my work and, quite often, part of the fun.

But that willingness is not universal.

Many developers simply want reliable tools that help them build reliable data platforms.

End users want the same.

They did not volunteer to become beta testers, model-routing experts, Capacity Unit analysts, or part-time researchers into token economics. And unfortunately, GA does not always mean gold. More options are usually better. Intelligent automation can be even better.

Transparency makes both understandable, trustworthy, and efficient.

Without it, Auto becomes another workload wandering around the Fabric capacity while everyone is being assured that the platform is working as designed.

Somewhere inside Microsoft, I assume, there may even be a semantic model explaining it.

Auto may select it.


r/MicrosoftFabric • • May 23 '25

Discussion Just a meme 😜

Post image
9 Upvotes

r/MicrosoftFabric • • Jan 25 '25

Certification I just failed DP-600 because the CASE STUDY moved to the end of exam and there is no reminder of it.

3 Upvotes

I get a score of 688/700. I have about 30 mins left to review. Submit before 2 minutes just find the case study. I have out of time to finish it. It's really misleading and likes an ambush.


r/MicrosoftFabric • • Sep 08 '26

Community Share Ever tried to quickly upload a file to a Fabric Lakehouse?

3 Upvotes

If I’m not the only one standing in the Fabric GUI like John Travolta in Pulp Fiction, wondering where to quickly upload a file or create a folder, please support my Fabric Idea. šŸ˜…

New folder, Upload file, and drag-and-drop directly in the Lakehouse file explorer.

Somehow ist marked as my first idea, and I don't know why, hopefully it appears soon.

Reduce clicks for file upload


r/MicrosoftFabric • • Dec 19 '25

Discussion Just became a Fabric featured partner - AMA

3 Upvotes

Got featured partner status with Fabric. Happy to share insights about the platform, integration process, or answer any questions you have.


r/MicrosoftFabric • • Feb 16 '26

Community Share I Fabric like this. How about you? What's your Job title?

Thumbnail linkedin.com
0 Upvotes

r/MicrosoftFabric • • Aug 13 '26

Discussion Am I missing something simple?

0 Upvotes

I’ve been a PBI Developer for 9 years, but relatively new to Fabric. I’ve taken a few classes, but I feel like I’m missing something obvious.

I converted my gen1 dataflows to gen2.

I set up a warehouse to copy them to. However, ever text field (e.g. name, email, status) is automatically set to 8000 characters. Rows with data in multiple fields are being silently dropped.

I can do a multi step process to create new fields with shorter lengths and drop the old fields then rename but this doesn’t feel right.

I’m missing an easy button right?