Samu Niemelä
Zure, Data Domain Lead
Zure, Data Domain Lead
Helsinki, Finland
Actions
Samu Niemelä is a seasoned data architect and Domain Lead at Zure, where he helps organizations turn messy data into modern, scalable platforms—mostly on Microsoft Azure, and occasionally with some strong opinions. With over a decade of experience, he’s wrangled technologies like SQL Server, Azure Synapse Analytics, Snowflake, and Microsoft Fabric. Samu lives in the liquorice capital of the world—Kouvola, Finland—with his family, lots of coffee, and surprisingly few debugging regrets.
Yli kymmenen vuoden kokemus dataratkaisuiden ympärillä, pääosin Microsoft teknologioilla.
Area of Expertise
Topics
When Deployment Pipelines Aren’t Enough: CI/CD Patterns for Microsoft Fabric at Scale
Have you ever wondered how to bring proven software development CI/CD methods into Microsoft Fabric without losing governance? In large Fabric environments, the hardest problem is not deploying once—it is letting many teams deploy safely at the same time, with traceability, approvals, and clear ownership.
In this session, you will learn a practical CI/CD model for Fabric built on Azure DevOps, Fabric CLI, and the Fabric Python CI/CD package. We will show a scalable workspace and environment structure, a service principal access pattern based on least privilege, and a release process with gates that platform teams can enforce without slowing delivery. You will leave with a repeatable blueprint: a reference pipeline flow, a recommended repo and branching approach, and a checklist for permissions, promotion, and deployment controls that works across multiple domains and projects.
Drawing the Network Line: Workspace-Level Security in Microsoft Fabric
Microsoft Fabric makes analytics easy to start, but enterprise security teams still ask a simple question: what can connect to this workspace, and from where? This session brings clarity to inbound and outbound network traffic in Microsoft Fabric, using practical platform design patterns.
The session explains what inbound connections mean in a Fabric context, including user access, service APIs, and how clients reach Fabric workspaces. It then covers outbound connections, where Fabric workloads access data sources, Azure services, and external endpoints.
Next, the session introduces a clear environment separation model. Development and test workspaces remain accessible from the public network to support fast iteration and self-service analytics. Production workspaces, however, are isolated using managed networks and private link.
Throughout the session, we show how networking, identity, and workspace configuration must work together. You will leave with a clear understanding of inbound and outbound traffic flows and a practical option for designing secure, environment-aware Fabric platforms that meet both engineering and security requirements.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top