If you've ever thought... "hmm, I wonder why they've designed this feature like this?!" - this post is for you. This is a cool opportunity to help shape the future of Microsoft Fabric. You can sign up via this link to join the Fabric User Panel: aka.ms/JoinFabricUserPanel In the Panel, you'll work directly with the Fabric Product Team and provide feedback on the product, including new features that are currently private (you'll need to sign an NDA to join the panel!). You feedback will help shape the future strategic direction for the product - nice. So if you want to provide feedback to Microsoft, to help shape it into a better product, then sign up to the Fabric User Panel today 😀 PS, if you sign up, you can leave at any time. Let me know if you're thinking about joining, or if you have any questions about it!

Wow! This one's a pretty big shift. See the full blog for more details. TLDR is that from end of January, in the Capacity Settings for a given capacity, you will be able to designate the capacity as a 'Fabric Copilot Capacity (FCC)', then you will need to assign Copilot users to this capacity (see images). Importantly, this means that users assigned to an FCC can use Copilot in these scenarios: - Power BI reports on (1) a Pro workspace or (2) a Fabric workspace smaller than F64. - Fabric Copilot scenarios on a Fabric workspace smaller than F64.

Benny Austin, Partner Solution Architect at Microsoft, has released some resources to a GitHub repository, alongside some explanatory wiki text explaining the solution. From the repo: "This accelerator will help you build a modern data platform end-to-end with Microsoft Fabric." The architecture can be seen below. 👉 Links: - LinkedIn article - GitHub Wiki - GitHub repo Key Features: - Medallion architecture 1 - Metadata-driven orchestration using ELT Framework 2 - Resusable Data Factory Pipelines that can be readily deployed with configuration changes 3 - Reusable Spark notebooks for common transformations 4 - Automated monitoring and optimization of Lakehouses 5 - Real-time Insights into batch jobs 6 - Infrastructure as Code (IaC) Bicep for provisioning cloud resources 7 - Comprehensive documentation to assist your implementation.

This is a pretty big one. No official announcement yet, perhaps they will announce formally at next week's conference... But if you take a look at some of the REST API endpoint documentation (e.g. this Create Lakehouse endpoint), you will notice a small, but impactful change (see image). You will see that you can now create items from a Service Principal account (which was previously not supported). What does this mean, you might be asking? Well, traditionally, when you create things like a Lakehouse in Fabric, you become the owner. A Service Principal (which can be created and managed in Azure Entra ID) is a generic user account, that can be now used to create these items. This makes it easier to automate creation of new items at different stages in a CI/CD pipeline. And means the 'Owner' is the Service Principal, not an individual. Is this something that you've been waiting for? Let me know how you'll be using it below 👇

Welcome to all new members, here's some links and information to help you get started! 𝗤𝘂𝗶𝗰𝗸 𝗟𝗶𝗻𝗸𝘀 𝘁𝗼 𝗴𝗲𝘁 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 - For an introduction to this community → Explore the Welcome Pack - New-ish to Fabric? → Check out our Fabric Foundation module - Studying for the DP-600? → Check out the DP-600 Module and the DP-600 category - Studying for the DP-700? → Check out the DP-700 Module and the DP-700 category - Want to get hands-on? → Check out Fabric Dojo 𝗛𝗼𝘄 𝘁𝗼 𝗲𝗻𝗴𝗮𝗴𝗲 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆? - Share your knowledge and experience! Even if you're relatively new to Fabric, or the community, your opinion and experiences are valued here! A great way to earn your first point(s) is to introduce yourself in the thread below 👇😀 Thank you for engaging and joining us on this exciting learning journey! 🙏 Will