There's been a few questions/ discussions about future jobs within Fabric. We're beginning to see companies recruiting for Fabric roles... exciting! Here's a few I found: Lead Data Modeler - Microsoft Fabric Senior Data Engineer (Microsoft Fabric) Data Engineer (Microsoft Fabric) GERMAN Microsoft Fabric Engineer (BELGIUM) Senior Consultant - Databricks and Microsoft Fabric Data & Analytics Engineer Principal and Senior consultant level Microsoft Fabric Data & Analytics Consultants I had the idea to create a video reviewing some of these job ads and picking out the common themes, to help people understand what they might need to focus on to get jobs in the future - what do you think of that concept? What you find that interesting? Let me know!

Apologies for basic question, but when I used the Load to Tables option in the lake house for my source data, it created my table with the "blank" between the two words Test Load (same as the original file.) I saw some discussions on another you tube video/blog video whereby any blanks in table names were replaced by an underscore was used to rename the table before it was loaded. Is there a specific naming convention that should be followed for downstream processing?

In my free trial of Fabric, I have been conceptually modelling how I would set-up the organisation to solve these business problems. 'Keep the data separated by geo/functional areas' 'Across all our geo-regions if this event occurs trigger a power automate flow to initiate a global response' From what I have learned in various videos using domains and workspaces will sub divide the organisation into the various geo-regions or GDPR areas to allow multi-access. Shortcuts can then be used to existing Data/Data Warehouses/Views in those regions in creating a new Fabric DW or an event table. A new reflex can then trigger Data activator into the resulting Power automate flows. (or whatever else is decided to trigger). The questions I have, given the trouble I had with domains and workspaces, Is this a good way to model geo political/GDPR/Cross departmental functions? Have you done this differently? (e.g. Functional verticals then geo/region) Has anybody set-up something similar like this that they would be willing to share here?. Apologies for the simplistic diagram. The assumption here is that the organisation sits on one Fabric instance, and data storage is within the GDPR/country domains as required. Regards Stuart

Hello Everyody, I am Stuart from the UK. I work as a contract Solution/Business Analyst. My goal here is to understand the best way a business can set-up Fabric/Data Activator elements to morph it's existing data structures (cross regional, cross legislation, cross department/cost centre) with least impact, to solve problems and gain strategic advantage. My favourite question is - "Why do you want to do that" - so would be happy to join any of those conversations Looking forward to learning the good, the bad, and the ugly of Fabric from this community. Shout to Will for the intro videos I have already watched - very helpful for those of use that require a slightly lighter view of the subjects. Regards Stuart