I was born in a small city in Minas Gerais, Brazil, and I currently live in Portugal. With over 5 years of experience in the Business Intelligence field, I've developed a strong foundation in Power BI and have built a deep passion for data modeling and analytics.
As a Microsoft Certified Trainer, I enjoy not only learning but also teaching others about the latest technologies. Since the launch of Microsoft Fabric, I've been diving into its capabilities and helping others make the most of its new features. My commitment to continuous learning is reflected in the 10 Microsoft certifications I've earned, including all the certifications available for Power BI and Fabric.
Currently, I work at Capgemini in the Business Intelligence area, where my focus is on data modeling, DAX, reporting and leveraging the power of Azure and Power Plataform technologies. I'm passionate about exploring new ways to integrate data solutions, optimize workflows, and deliver insights. Whether through mentoring, workshops, or contributing to the community, I strive to share my knowledge and help others stay at the forefront of BI development.
Nothing here yet.
No blogs yet.
If I understood correctly, these costs should incur only when using cross region shortcuts, right? If I use the same strategy to segregate different capacities on different workspaces and connect then by a shortcut, should I expect bandwith costs even if the 2 capacities are on the same region? Since is the same data, on the same one lake on the same region, I expect that the answer is no.