Use this thread to ask any questions you might have about this lesson: #1.4 Sensitivity Labels 👇

(Repost from LinkedIn) I’m happy to share that I passed the DP-600 this morning!! It's really important that everyone on here and in my network knows that I don't think I would've got through this certification without the help of @Will Needham. His knowledge, his tutorials, his Skool communities (both Learn Microsoft Fabric and Fabric Dojo), his YouTube channel, but most of all his commitment to help others learn. The sheer amount of time he takes to create his tutorials and his videos is simply awe-inspiring. They give you hands on experience, but also get you thinking about how you can do it better in the future. I'm privileged and proud to be part of both of his communities. They're a great place to be. This certification isn't just for me, it's for him too. Thanks Will.

Use this thread to ask any questions you might have about this lesson: #Introduction to DP-600 exam (and course) 👇

https://blog.fabric.microsoft.com/en-us/blog/important-billing-update-coming-to-copilot-and-ai-in-fabric/

This post might highlight there is so much to learn, which is why I value any steer from the community. We are invested in using Fabric, but we have lots of 'legacy' Power BI Reports being produced via Power BI Report Server and Power BI Service platforms. We have been testing the 'best way' to migrate a 'legacy' Power BI report into the Fabric ecosystem. So far we have identified to possible approaches: 1) start from scratch but copy the 'transformation steps' of the Power BI report into a dataflow. Modify the source from legacy to an appropriate Fabric Lakehouse that holds the same data. We are pointing the output destination of the dataflow to a 'gold' Lakehouse - which is essentially equivalent to the Tables of the legacy Power BI. We then need to manually recreate relationships and add any measures that existed in the Legacy Power BI Report.. becomes a manual nightmare! 2) we start with the legacy Power BI Report - create a desktop version, modify the source so it points to the relevant Fabric Hosted Lakehouse tables, and then publish it to the relevant Fabric Workspace. This seems to work .. until it doesn't. We get the Semantic Model and Report Fabric Items, the latter has all of the legacy measures but we struggle when we need to fix things, we are currently having to go back to the Desktop report adjust things there and then republish. Option 1 seems a lot of manual work, and option 2 requires a standalone desktop Power BI Report to exist, neither options are therefore sustainable. I am specifically referring to the migration of legacy Power BI Report Server reports, I am assuming Power BI Service hosted reports will be somewhat easier. How on earth do you modify the semantic models within Fabric if you have published the report to Fabric from Power BI Desktop might be the better title for this post :-)