Episode 44 • 2026-11-06 Duration: 9:22

Purview é uma marca e uma conta — duas compras diferentes. Veja o que um tenant só com Fabric já ganha do Govern, onde a linhagem nativa para, e por que comprar uma conta Purview pra resolver linhagem de Lakehouse não fecha a lacuna.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The concrete recommended architecture
• The architectural principle to take home

Key takeaways

• Em algum canto do seu tenant Fabric tem uma página do Govern que atualiza uma vez por dia, lê metadados que ninguém precisou escanear, e silenciosamente conta o que você tem.
• Uma plataforma, um serviço de metadados. O catálogo lê de onde está.
• E as lacunas de linhagem do lado do Lakehouse não fecham adicionando uma conta Purview.

From the video

• Demo 1: Govern, Seen by Three People
• Demo 2: Lineage Until It Stops
• Architecture film: When you need a purview account
• Architecture film: What you already have

Resources

• Use Microsoft Purview to protect Microsoft Fabric
• Governance overview and guidance
• enable labels
• DLP planning
• DLP get started
• audit solutions
• billing models
• register and scan Fabric
• data governance billing
• free version
• OneLake catalog overview
• Catalog - Search
• item details
• What's new
• Govern your Fabric data estate

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 31 • 2026-07-31 Duration: 9:25

Um scorecard gera seu próprio semantic model no momento em que é criado. Esse segundo armazém é o motivo de metas ficarem defasadas, RLS não funcionar, e a solução nunca estar onde as pessoas procuram.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• The concrete recommended architecture
• Risks of the recommended path
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The architectural principle to take home

Key takeaways

• Em algum lugar agora mesmo, uma nota de check-in diz "pausamos a campanha de propósito.
• Statefulness é a feature. Tudo que a gente discutiu — essa é a conta. Conheça antes de assinar.
• Arquitetura não é religião. Use o scorecard pro que nada mais consegue fazer, e contorne as limitações com o que você já tem.

From the video

• Architecture film: State vs commitment
• Demo 1: Your First Scorecard and a Manual Goal
• Architecture film: Naming minefield
• Architecture film: Refresh chain
• Architecture film: Rollup forward only

Resources

• Get started with goals
• Deprecation of Metric Sets in Power BI
• Fabric Community updates blog
• Create scorecards
• Scorecard subscriptions
• Create subgoals
• Hierarchies in scorecards
• Create connected goals in Power BI
• Stay on top of your goals (check-ins)
• Create automated status rules for goals
• Protect your scorecards with goal-level permissions
• Create linked goals in the Power BI service (preview)
• Refresh goals and scorecards automatically
• Use Power Automate to update goals automatically
• Use Power BI metrics to track goals in Microsoft Teams

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 43 • 2026-10-30 Duration: 9:46

Um rótulo de sensibilidade diz Altamente Confidencial no cabeçalho, mas dentro do Fabric ele nunca decide quem abre o item. Este episódio mostra onde rótulos realmente controlam acesso e onde a aparência de proteção é só uma placa.

What we discuss

• The pattern we keep seeing in the field
• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Agora mesmo, em algum lugar, tem um Lakehouse com Altamente Confidencial no cabeçalho.
• Me mostra o padrão da query. Se o padrão é "restringir quem abre isso", desenhe o workspace. Se o padrão é "proteger o que sai", desenhe o rótulo. Misturar os dois é onde começa cada thread naquele fórum.
• E a política de proteção fica no meio. Pro caso específico onde você não consegue separar itens em workspaces diferentes mas precisa de acesso baseado em rótulo. Saiba o que está comprando: 50 políticas, 24 horas, sem relatórios.

From the video

• Demo 1: The Label Changed Nothing
• Architecture film: Two questions two mechanisms
• Architecture film: Eight routes onto an item
• Architecture film: Where protection starts
• Architecture film: Where label and permission meet

Resources

• Sensitivity labels in Power BI
• Sensitivity labels troubleshooting
• Protected sensitivity labels in Fabric and Power BI
• Roles in workspaces
• Permission model
• Row-level security (RLS) with Power BI
• Information protection in Microsoft Fabric
• Protection policies in Microsoft Fabric
• Restrict access to content by using sensitivity labels to apply encryption
• Export data from a Power BI visualization
• Apply sensitivity labels to Fabric items
• Default label policy for Fabric and Power BI
• Mandatory label policy for Fabric and Power BI
• Domain-level default sensitivity labels
• Information protection tenant settings

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 30 • 2026-07-24 Duration: 9:39

Um relatório Power BI exporta uma página. Um relatório paginado exporta 483. A diferença não é um toggle de feature — é uma decisão de design de vinte anos atrás que não carrega nenhum modelo de dados. Esse único fato explica cada limite, cada timeout e a falha de render que a sua subscription de segunda-feira está prestes a encontrar.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The pattern we keep seeing in the field
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Neste exato momento, uma subscription está prestes a disparar.
• Duas décadas de idade, ainda um item de primeira classe na Fabric REST API.
• O padrão dita a plataforma. O RDL existe porque o papel existe. E o papel não mudou.

From the video

• Demo 1: From Report Builder to a Multi-Page PDF
• Architecture film: Two renderers one platform
• Architecture film: Render pipeline
• Community Q&A
• Architecture film: Delivery surfaces and where they break

Resources

• What are paginated reports in Power BI?
• When to use paginated reports
• Paginated reports in the Power BI service
• Performance and scalability
• FAQ
• Paginated Report definition
• Access the paginated report editor
• SQL Server Reporting Services (Wikipedia)
• RDL Schema Specification
• Plan to migrate .rdl reports
• Supported data sources
• Connect via Power Query
• Create and use the paginated report visual
• Email subscriptions
• Export Power BI paginated reports

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 42 • 2026-10-23 Duration: 11:01

Medallion é a abordagem recomendada para Fabric — e também é um bloco entre cinco, com uma fatura de manutenção que ninguém colocou no diagrama. O que o guardrail de arquivos significa para Direct Lake no OneLake, por que lakehouses com schema não suportam a atividade de manutenção automatizada, e quando o padrão inteiro é exagero.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• The architectural principle to take home

Key takeaways

• Neste momento, tem uma tabela com 4000 arquivos num F64.
• O preço dessa resposta é manutenção. Uma agenda, um monitor, e alguém que sabe onde TABLETRAITS mora.
• Arquitetura não é religião. Medallion responde uma pergunta — pra que cada estágio é confiável — e deixa as outras quatro pros outros quatro blocos.

From the video

• Architecture film: Five building blocks
• Architecture film: Each layer is a contract
• Demo 1: Bronze That Copies Nothing
• Demo 2: Silver as a Contract
• Architecture film: When recipe is wrong

Resources

• Understand medallion architecture for Fabric with OneLake
• OneLake patterns and foundational capabilities
• Common dbt job patterns
• Modern data warehouse medallion architecture in Microsoft Fabric
• What are materialized lake views?
• Spark SQL reference
• Optimal refresh
• Cross-workload table maintenance and optimization
• What's new
• Lakehouse Maintenance activity
• Apache Spark billing and utilization
• extended capabilities
• CDF page
• Data quality in materialized lake views
• Manage materialized lake views lineage

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 29 • 2026-07-17 Duration: 10:11

Três coisas no Fabric se chamam 'dashboard'. Só uma cruza semantic models diferentes — e o preço é perder todo filtro e todo slicer. A arquitetura de tiles, snapshots e três comportamentos de refresh.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• The pattern we keep seeing in the field
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• E ninguém vai perguntar em qual dos três comportamentos de refresh ela está.
• Neste momento, em algum lugar, tem um tile de dashboard mostrando o número de ontem, e a pessoa olhando acha que é o de hoje.
• O padrão define a plataforma. A árvore de decisão do vídeo percorre isso — se a palavra 'filtro' aparece no requisito, é um relatório. Indicadores entre modelos com click-through: aí é dashboard.

From the video

• Demo 1: Pin Across Two Semantic Models
• Demo 2: Pin a Live Report Page (Getting Interactivity Back)
• Architecture film: Tile anatomy
• Architecture film: Refresh three behaviors
• Architecture film: Decision tree

Resources

• Introduction to dashboards for Power BI designers
• Compare Report Server and the Power BI service
• Introduction to dashboard tiles
• Pin Reporting Services items to Power BI dashboards
• Pin an entire report page as a live tile
• Reports in Power BI
• Create a Real-Time Dashboard
• What is Fabric Embed (preview)
• Conduct proof of concept to migrate to Power BI
• mobile-apps-view-dashboard
• service-dashboard-pin-tile-from-excel
• service-pin-tile-to-another-dashboard
• Dashboards for business users
• Create a Power BI dashboard from a report, Considerations and limitations
• Create or edit a dashboard tile

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 41 • 2026-09-18 Duration: 9:32

Databricks e Fabric têm cinco caminhos de integração, não um. Cada caminho move dados. Nenhum move permissões. Analisamos o modelo de credencial única, o delay de uma hora pra revogar acesso e o shortcut ADLS que silenciosamente ignora o row-level security do Unity Catalog.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• The pattern we keep seeing in the field
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The concrete recommended architecture
• The architectural principle to take home

Key takeaways

• Todo caminho entre essas plataformas move dados.
• Neste momento, em algum lugar, um catálogo espelhado tá servindo um workspace que deveria enxergar dois schemas.
• E aceite que "mantenha as configurações de acesso sincronizadas" é documentação pra não existe sincronização.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/RAqhXwSj_HE

From the video

• 13:33 Demo: Direct Lake Over Databricks Data
• 3:17 Demo: Mirror a Catalog from Unity Catalog
• 8:37 Demo: One Credential for Everyone, and a Revoke That Takes an Hour
• 23:49 Who Pays
• 17:02 The Reverse Direction Is Three Different Things

Resources

• Mirroring Azure Databricks Unity Catalog
• Secure Fabric mirrored databases from Azure Databricks
• Tutorial: Configure Microsoft Fabric mirrored databases from Azure Databricks
• Enable external data access to Unity Catalog
• Publish a Unity Catalog catalog to Microsoft Fabric
• Limitations in Microsoft Fabric mirrored databases from Azure Databricks
• Enable OneLake catalog federation
• Integrate OneLake with Azure Databricks
• Connect Azure Databricks to a OneLake external location
• Fabric capacity and OneLake consumption
• OneLake compute and storage consumption
• Understand your Azure bill for a Fabric capacity
• Shortcuts in a lakehouse
• Mirrored Azure Databricks Unity Catalog definition
• OneLake storage tiers

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 37 • 2026-10-16 Duration: 10:24

Fabric não cobra quando o trabalho acontece — distribui o custo por 2.880 intervalos de trinta segundos. Essa frase explica todo comportamento confuso de capacity, inclusive por que surge protection pode rejeitar o SQL que deveria proteger.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• E alguém está prestes a cortar o SKU pela metade porque o gráfico parece calmo.
• O pico que eles veem é um recibo. A linha suavizada é a conta que ainda não chegou.
• Agora mesmo, em algum lugar, tem um gráfico de capacity com uma noite de cara tranquila.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/iE-jdcseCaY

From the video

• 7:42 Demo: Watch One Job Spread
• 9:51 The Throttling Staircase, and Who Skips Steps
• 2:50 Demo: Read the Metrics App
• 12:46 Sizing From the Smoothed Line

Resources

• Fabric capacity throttling policy
• Smoothing and throttling in Fabric Data Warehouse
• Throttle triggers and throttle stages
• Capacity planning guide
• Autoscale Billing for Spark
• Fabric operations: interactive and background
• Understand the metrics app timepoint page
• Understand the metrics app timepoint summary page
• Surge protection
• Capacity and SKUs
• Burstable capacity in Fabric Data Warehouse
• Consumption rates and billing for Copilot in Fabric
• Azure quotas for Fabric capacities

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 28 • 2026-07-10 Duration: 10:12

Cada visual dispara uma consulta DAX. A maioria entra na fila. Matthias e Fabia rastreiam onde o tempo realmente vai quando uma página de relatório Power BI abre no Fabric — e por que o gargalo quase nunca é o que você imagina.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• The concrete recommended architecture
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Em algum lugar agora tem uma página que é lenta por causa de fila, num modelo que silenciosamente caiu pra DirectQuery, num relatório que alguém vai pedir pra exportar como PDF com todas as linhas.
• O relatório é uma janela. Não é onde sua performance mora e não é onde seus dados moram. O modelo decide a velocidade. O tipo de item decide a saída. O SKU decide em qual engine suas consultas realmente rodam.
• Tá, me dá o contra-argumento. Quando é que toda essa separação modelo-relatórios é só... overhead?

From the video

• Architecture film: Page open
• Architecture film: Where the time goes
• Demo 2: Performance Analyzer (Stop Guessing)
• Architecture film: Report vs paginated vs dashboard

Resources

• Power BI reports overview
• Build Power BI reports with Direct Lake tables
• Reports in Power BI - Dashboards versus reports
• When to use paginated reports
• What are paginated reports
• Introduction to dashboards
• Git integration source code format
• Tour the report editor
• Interact with a report in Editing view
• Implementation planning: user tools and devices
• Direct Lake in Power BI Desktop
• Apply data point limits and strategies by visual type
• How Direct Lake works
• Power BI Desktop project report folder
• Connect to semantic models from Power BI Desktop

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 38 • 2026-10-09 Duration: 9:30

Domínios no Fabric parecem fronteiras de governança, mas a documentação diz outra coisa. Exploramos o que um domínio realmente entrega, o mecanismo de domínio padrão que continua rodando no seu tenant, e por que a etiqueta no armário não é a tranca.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• A real Reddit/Microsoft Q&A question unpacked
• Where the obvious answer breaks
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Tem um arquivo de aço em todo escritório com uma etiqueta na frente.
• O padrão dita a plataforma. Se o padrão é "organizar e encontrar," domínio é a ferramenta certa. Se o padrão é "restringir e proteger," você tá na camada errada.
• Então é aqui que eu chego. Um domínio responde "de quem são esses dados." Use pra descoberta e delegação. Construa suas fronteiras reais com papéis de workspace e permissões de item. E audite a lista de domínio padrão trimestralmente,...

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/8wRSvnF_CtQ

From the video

• 7:46 Demo: The Contributor Who Cannot Contribute
• 3:15 Demo: The Filter That Is Not a Fence
• 12:51 Demo: An Assignment Nobody Made
• 14:42 The Sensitivity Label Override Ladder

Resources

• Fabric domains
• Power BI implementation planning: Tenant administration
• Best practices for domains
• Domain-level default sensitivity labels
• Endorsement overview
• OneLake catalog overview
• Scope the catalog to a particular domain
• Governance overview and guidance
• Roles in workspaces
• About tenant settings

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 40 • 2026-09-25 Duration: 10:12

Cosmos DB não tem schema. Tabelas Delta precisam de um. Quando o mirroring conecta os dois, o replicador adivinha — e o chute só alarga. Rastreamos de onde vêm os bytes, por que propriedades renomeadas deixam colunas fantasma cheias de null, e o que stop replication realmente faz.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• A real Reddit/Microsoft Q&A question unpacked
• Where the obvious answer breaks
• Risks of the recommended path
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• The architectural principle to take home

Key takeaways

• Neste momento, em algum lugar, um container Cosmos está recebendo escritas.
• E alinhe a região da sua capacidade Fabric com a conta Cosmos.
• Três perguntas antes de mexer em qualquer coisa.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/KJUBmoNFICo

From the video

• 13:19 The Discovered Schema
• 16:20 Nested Data Arrives as a String
• 18:47 Stop Is Not Pause
• 2:53 Demo: Create the Mirror, Count the Rows

Resources

• Mirroring Azure Cosmos DB
• Cosmos DB mirroring FAQ
• continuous backup
• Cosmos DB mirroring limitations
• Migrate an Azure Cosmos DB account from periodic to continuous backup mode
• Migrate from Azure Synapse Link to Cosmos DB mirroring
• Access mirrored data in Lakehouse and notebooks
• How to: Query nested data
• Configure private networks for Azure Cosmos DB Fabric Mirroring
• tutorial
• Monitor Fabric mirrored database replication
• Mirroring public REST API
• Cost of mirroring
• Mirrored database in Fabric (all sources)
• Cosmos DB in Microsoft Fabric (native item)

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 36 • 2026-10-02 Duration: 8:51

Um workspace carrega quatro fronteiras — segurança, custo, região, ciclo de vida — e você configurou uma delas. Este episódio desmonta o que 'somente leitura' realmente significa no Fabric e por que a segurança do OneLake não consegue conter um Contributor.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• A real Reddit/Microsoft Q&A question unpacked
• Where the obvious answer breaks
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Neste exato momento, alguém está promovendo um colega a Contributor pra corrigir um relatório.
• E confira seus tipos de capacity antes que alguém faça isso por você.
• Me mostra o padrão de consulta. Isso diz se Viewer com OneLake security basta, ou se você precisa dividir.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/tpePwivxtzk

From the video

• 6:25 Demo: Same Table, Two Routes
• 12:28 Demo: Watch the Override
• 14:35 Who Can Claim Your Workspace

Resources

• Roles in workspaces
• Permission model
• Give users access to workspaces
• OneLake security access control model
• Capacity reassignment restrictions
• Understand Fabric licenses and capacity
• Manage workspaces
• What is a lakehouse
• Reassign a workspace to a different capacity
• Create a workspace
• Workspace roles in Fabric Data Warehouse
• Workspace roles in Lakehouse
• Roles in workspaces in Power BI
• Build permission for shared semantic models
• Get started with Microsoft Fabric

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 35 • 2026-08-28 Duration: 9:39

Graph no Fabric materializa uma segunda cópia dos seus dados para travessia. Essa cópia explica a defasagem, o ciclo de rebuild e a fronteira de workspace que decide se graph cabe na sua arquitetura.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• A real Reddit/Microsoft Q&A question unpacked
• Where the obvious answer breaks
• The concrete recommended architecture
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• A pergunta é se alguém verificou o status da resposta.
• E em algum lugar agora, tem um queryset devolvendo um resultado que era verdade ontem.
• Um timeout de query de 20 minutos. Esse é um teto que dá pra planejar.

From the video

• Architecture film: Snapshot not view
• Architecture film: Four ways to ask
• Architecture film: Staleness chain
• Demo 3: Change the Model, Watch the Queryset
• Architecture film: The ceilings

Resources

• How graph in Microsoft Fabric works
• Current limitations of graph in Microsoft Fabric
• Troubleshooting and FAQ for graph
• Quickstart: Create your first graph
• Tutorial: Introduction to graph
• Tutorial: Query the graph by using the query builder
• Example graph datasets
• Optimize GQL query performance
• GQL language guide
• GQL quick reference
• GQL query API (REST)
• Graph data models
• Design a graph schema
• Fabric Data Agent
• OneLake security

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 34 • 2026-08-21 Duration: 9:25

Um diálogo de conectividade na API for GraphQL do Fabric parece só um passo de configuração. Na prática, ele decide quem precisa de permissão onde, se row-level security funciona de verdade, e se sua API de produção vai servir dados de dev depois de cada deploy.

What we discuss

• How it actually works underneath the abstraction
• A real Reddit/Microsoft Q&A question unpacked
• Where the obvious answer breaks
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• O que fica comigo é isso... uma API gerada parece gerenciada. Como se ela estivesse observando sua fonte e se atualizando.
• E a decisão mais importante não é qual fonte conectar.
• O padrão define a plataforma. Se o padrão é um time de aplicação precisando de acesso tipado e autenticado aos dados do Warehouse, essa é a ferramenta certa.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/IuGCxyLWzo0

From the video

• 2:34 Demo: An API in Ninety Seconds
• 19:42 Demo: Schema Drift, Live
• 17:07 What Deployment Actually Does
• 14:48 Demo: Two Sources, One Query

Resources

• Fabric API for GraphQL FAQ
• Limitations of Microsoft Fabric API for GraphQL
• Connect AI Agents to Fabric API for GraphQL with a local MCP server
• What is Microsoft Fabric API for GraphQL?
• Create an API for GraphQL in Fabric and add data
• Connect applications to Fabric API for GraphQL
• Source control and deployment pipelines in API for GraphQL
• Fabric API for GraphQL editor
• Query multiple data sources in Fabric API for GraphQL
• Use service principals with Fabric API for GraphQL
• Expose stored procedures
• Performance best practices
• Create GraphQL API from your SQL database
• Develop GraphQL applications in Visual Studio Code
• Private Links overview

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 33 • 2026-08-14 Duration: 9:07

Um org app é um item do Fabric que gerencia permissões sobre outros itens. Desmontamos o que ele realmente propaga, onde a abstração para, e por que certas concessões sobrevivem à autoridade que as criou.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• Risks of the recommended path
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• The architectural principle to take home

Key takeaways

• Neste momento, em algum lugar, existe um Semantic Model no workspace B com uma entrada de permissão que ninguém no workspace A consegue remover.
• A frase pra dizer antes de construir: o org app cuida DESSAS permissões.
• Um org app é um item que gerencia permissões sobre outros itens.

From the video

• Architecture film: An item not a publication
• Architecture film: Propagation tree
• Demo 2: Grant, Inspect, Revoke
• Architecture film: The hidden content switch

Resources

• Get started with org apps
• Collaborate with Power BI in Teams
• CI/CD for org apps in Fabric
• How to integrate notebooks with Org app
• Share Fabric Maps: Org apps
• Workspace roles in Microsoft Fabric
• Publish an app in Power BI
• Apps in Power BI (consumer view)
• Direct Lake overview – permission requirements
• Email subscriptions for reports
• Get started with Git integration
• Source code format – automatically generated system files
• Focus mode in Fabric
• Fabric preview features
• Power BI add-in for PowerPoint

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 32 • 2026-08-07 Duration: 9:16

Um update de Power BI app funciona perfeitamente e todo consumidor continua vendo o conteúdo antigo. A fronteira de publicação copia mais do que você imagina, concede menos do que você espera e falha sem fazer barulho.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• The concrete recommended architecture
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The architectural principle to take home
• Risks of the recommended path

Key takeaways

• Neste exato momento, um update de app acabou de funcionar.
• O workspace app é construído em torno de uma ideia — publicar cria uma cópia.
• Meu conselho: se você precisa do portão, aceite o que o portão custa.

From the video

• Architecture film: The publish boundary
• Architecture film: Permission arithmetic
• Demo 2: The Hidden-by-Default Trap
• Demo 3: The Pipeline Moves the Content, Not the App

Resources

• Apps in Power BI
• Get started with org apps
• Publish an app in Power BI – Considerations and limitations
• Power BI enhanced report format (PBIR)
• Collaborate with Power BI in Teams
• Workspaces in Power BI
• Create a workspace in Power BI
• End-to-end: From raw data to a shared Power BI app
• The deployment pipelines process
• Best practices for lifecycle management in Fabric
• App tenant settings
• What are Power BI template apps?
• Create a template app in Power BI
• Create your first Fabric app
• Strategy for using groups

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 18 • 2026-05-01 Duration: 10:15

Real-Time Hub coloca os mesmos 25 conectores numa segunda interface que ninguém solicitou. Investigamos por que esse catálogo auto-provisionado se torna crítico quando streams sobrevivem a quem as criou — e a armadilha de custo do Data Activator escondida atrás de cada alerta.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• The concrete recommended architecture
• When the rejected approach is actually right
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Agora mesmo no seu tenant, existe uma stream cuja coluna Item Owner mostra o nome de alguém que saiu dois trimestres atrás.
• Arquitetura não é religião. Pule o que não te serve. Use o que serve.
• O catálogo está rodando desde o primeiro dia.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/tZmw36djm9w

Resources

• managed private endpoint
• Eventstream Overview
• KQL Database
• Activator Overview
• Real-Time Dashboard
• Schema Sets
• Digital Twin Builder
• Real-Time Hub Overview
• Get Started with Real-Time Hub
• Supported Sources
• Add Azure Event Hubs Source
• Add Azure IoT Hub Source
• Get Azure Blob Storage Events
• Create Streams from Workspace Item Events
• Create Streams from OneLake Events

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 9 • 2026-02-27 Duration: 12:13

Warehouse e Lakehouse gravam tabelas Delta no mesmo OneLake, no mesmo formato, mas em caminhos separados. Matthias e Fabia rastreiam a restrição de escritor único que faz o Warehouse compactar sozinho enquanto o Lakehouse acumula arquivos Parquet órfãos — e definem quando cada artefato merece seu lugar.

What we discuss

• How it actually works underneath the abstraction
• The pattern we keep seeing in the field
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The concrete recommended architecture
• Risks of the recommended path
• The architectural principle to take home

Key takeaways

• Neste momento, em algum lugar, uma tabela Lakehouse tem doze mil arquivos Parquet embaixo.
• Não escolha pelo nome. Lakehouse soa abrangente. Warehouse soa como algo que você está migrando pra longe. O que importa de verdade é quem escreve, quem mantém, e o que acontece quando ninguém está de olho na contagem de arquivos.
• Me mostra o padrão de consulta. Se seu time escreve T-SQL e precisa de acesso de escrita, vai de Warehouse — compactação automática e transações multi-tabela vêm junto. Se seu time escreve Spark, vai de Lakehouse e assuma a manutenção. Os...

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/hnADNoZcm14

Resources

• Warehouse in Fabric
• Create Warehouse
• T-SQL surface area
• Performance Guidelines
• Better together: Lakehouse and Warehouse
• Decision Guide: Warehouse vs Lakehouse
• SQL Analytics Endpoint Performance
• Result Set Caching
• Data Clustering
• Zero-Copy Table Clone
• Time Travel
• Transactions
• Migration from Synapse
• Architecture
• Warehouse Team AMA (March 2025)

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 2 • 2026-01-09 Duration: 11:49

Shortcuts do OneLake prometem um namespace unificado sem mover dados. Mas a abstração esconde um modelo de segurança dividido, um caminho de exclusão que atravessa workspaces e uma economia de cache que transfere a conta sem avisar.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• Risks of the recommended path
• The pattern we keep seeing in the field
• The concrete recommended architecture
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The architectural principle to take home

Key takeaways

• E essa pessoa está de férias. Arquitetura não é religião. Até sexta que vem.
• Em algum lugar agora mesmo tem um Lakehouse bronze com quarenta shortcuts.
• Então a lição — shortcuts resolvem o problema de namespace.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/zjhbVF8NhWY

Resources

• OneLake Shortcuts
• Shortcut types
• Where to create shortcuts
• Shortcut authorization
• Shortcut caching
• Limitations
• Shortcut security
• Create OneLake Shortcut
• Create ADLS Gen2 Shortcut
• Create S3 Shortcut
• Create GCS Shortcut
• Shortcuts REST API
• On-premises Shortcuts
• Dataverse Shortcuts
• OneLake Overview

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.

Episode 1 • 2026-01-02 Duration: 10:18

Cada escrita Delta gera arquivos Parquet. No modo Direct Lake recomendado, estourar o guardrail não deixa seu dashboard lento — tira ele do ar. A dívida de manutenção do Lakehouse que ninguém orça.

What we discuss

• How it actually works underneath the abstraction
• Where the obvious answer breaks
• A real Reddit/Microsoft Q&A question unpacked
• The concrete recommended architecture
• The pattern we keep seeing in the field
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• The architectural principle to take home

Key takeaways

• E a menos que alguém esteja monitorando a contagem de arquivos, ninguém vai saber por quê.
• E no modo Direct Lake recomendado, isso não é mais uma dívida de performance.
• Agora mesmo tem uma tabela em algum lugar com quatro mil arquivos.

Watch the episode

The Fabric Friday video on this topic: https://youtu.be/wvKePeQUsIg

From the video

• Demo 1: Create a Lakehouse (video)
• Demo 3: SQL analytics endpoint (video)
• Demo 2: Medallion Architecture in one lakehouse (video)

Resources

• Lakehouse end-to-end scenario
• Tutorial: Create a lakehouse
• Medallion architecture for Fabric
• Tutorial: Ingest data
• SQL analytics endpoint
• Direct Lake overview
• Delta Lake table optimization
• Decision guide: Lakehouse vs Warehouse
• High Concurrency Mode
• Lakehouse overview
• Table maintenance
• Work with Delta Lake tables
• Organize with Medallion architecture
• Use Apache Spark in Fabric
• Greenfield Lakehouse on Fabric

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Este podcast foi gerado por inteligência artificial. As duas vozes são sintéticas: a de Matthias é uma voz clonada e a Fabia é uma co-apresentadora de IA.

Brand design based on fabricperiodictable.com.