Cross-Tenant VNet Peering with VNet Data Gateway
I am considering the following architecture: Microsoft Fabric → VNet Data Gateway → Tenant A VNet → Cross-Tenant VNet Peering → Tenant B VNet → Private Endpoint → Azure Database for PostgreSQL Flexible Server The VNet Data Gateway is deployed in the same tenant as Microsoft Fabric (Tenant A). PostgreSQL Flexible Server and its Private Endpoint are in Tenant B. Is this architecture supported by Microsoft Fabric? I am especially interested in: Private DNS configuration across the two VNets Cross-tenant VNet peering configuration VNet Data Gateway configuration PostgreSQL Private Endpoint configuration Has anyone implemented this architecture in a PoC or production environment? If so, I would appreciate any configuration examples or screenshots from Azure Portal or Fabric Portal.
Can't create DataFlowGen2 (Policy Allows)
Hi, we've got a perfect scenario for the new Policy item where we need a user to be able to develop and migrate his personal Dataflow Gen1 to Dataflow Gen2, and we need to enable him to do so. So we've enabled him to Fabric, defined a specific security group for the policy which we've configured in this way: We've tried with him and he isn't able to create other items like notebooks (good), but it fails with a generic error when he tries to create a DataFlow Gen2: He's even Administrator in some workspace, so it's not a problem of the workspace role. There are no additional messages. Any help will be appreciated Daniele TilesTalk to Your Insurance Data: Better Answers Start with the Semantic Model
News and Announcements Jenn and Dean will begin with news and exciting announcements from FabCon handing it over to the guest speaker. Spotlight Content What if exploring data and building reports could start with a conversation? Generative AI can only be as effective as the data foundation behind it. In this session, we'll explore how semantic models influence the quality, accuracy, and business relevance of the answers users receive from conversational AI experiences across Power BI and Microsoft 365 Copilot. Using a client-neutral auto insurance claims semantic model, we'll compare how the same questions are interpreted and answered in Power BI reports, the Power BI service, and Microsoft 365 Copilot. You'll see firsthand why context matters, what drives trustworthy responses, and how semantic model design directly impacts the end-user experience. Next, we'll introduce an AI-powered semantic model assessment scorecard that evaluates AI readiness and identifies opportunities to improve terminology, business definitions, measures, and contextual metadata. Together, we'll review the findings, prioritize enhancements, and then use an AI agent to help implement those improvements within the model. Finally, we'll return to the original business questions and measure the impact of those enhancements, demonstrating how targeted semantic model improvements can significantly improve answer quality and user trust. Whether you're building semantic models, supporting analytics teams, or preparing your organization for AI-powered analytics, you'll leave with a practical framework to assess, improve, and accelerate AI readiness using agentic tools and modern data modeling practices. Key Takeaways Understand how conversational experiences differ across Power BI and Microsoft 365 Copilot. Learn what factors influence the quality and accuracy of AI-generated answers. Evaluate semantic models using an AI-readiness scorecard. Identify high-impact improvements to measures, terminology, and business context. Use AI agents to streamline semantic model optimization. Build semantic models that deliver more reliable, business-friendly AI experiences. Guest Speaker Amol Manocha Microsoft | Data, Analytics, and AI Amol Manocha is a Senior Data & AI Solution Engineer at Microsoft, helping insurance organizations turn complex data challenges into practical, AI-powered solutions. His work spans Microsoft Fabric, Power BI, Copilot, and agentic analytics, with a focus on making data easier to explore, understand, and act on. Drawing from real-world customer scenarios, Amol brings a practical perspective on how AI is reshaping business intelligence, from conversational analytics to building trusted, intelligent data experiences. User Group Leaders
SCADA and SAP silos to operational intelligence with Microsoft Fabric
One pattern I keep seeing in industrial analytics is that the hardest part isn't building another dashboard. It's getting production, maintenance, and financial data to align. In a recent engagement with an oil & gas client, my team at DataToBiz worked with an operator managing 6+ oil fields and 800+ production assets. Data was spread across SCADA, SAP, maintenance systems, and field spreadsheets. Production reporting could also lag by 24 to 48 hours. The architecture was built around Microsoft Fabric: Data Pipelines and Event Streams handled batch and near real-time ingestion from operational and enterprise sources. OneLake + Fabric Lakehouse provided the centralized data layer, with Bronze, Silver, and Gold Delta tables. Fabric Notebooks with Apache Spark handled transformation, cleansing, and KPI standardization. Power BI semantic models provided the governed business layer, with DAX measures and RLS for role-based access. Power BI dashboards brought production, maintenance, downtime, and executive views into a common reporting environment. Fabric Data Science with Python supported predictive maintenance and anomaly-detection use cases. The important design decision was separating ingestion, transformation, and the semantic layer instead of pushing all the logic into Power BI. That became particularly important for production KPIs. Different operational systems can represent the same metric differently, and simply centralizing the data doesn't solve that problem. The implementation automated 20+ recurring reports and enabled dashboards for 75+ business users across operations, engineering, finance, and leadership. For teams implementing Fabric in industrial environments, how are you handling KPI definitions across SCADA, ERP, maintenance, and field systems? Do you maintain the business definitions in metadata, enforce them in the transformation layer, or manage them primarily through the semantic model?Is VNet Data Gateway → Cross-Tenant VNet Peering → PostgreSQL Private Endpoint supported?
Is VNet Data Gateway → Cross-Tenant VNet Peering → PostgreSQL Private Endpoint supported in Microsoft Fabric? I am designing an architecture where Microsoft Fabric connects to an Azure Database for PostgreSQL Flexible Server located in a different Microsoft Entra ID tenant, without using any public network connectivity. The proposed architecture is : Microsoft Fabric → VNet Data Gateway → Tenant A VNet → Cross-Tenant VNet Peering → Tenant B VNet → Private Endpoint → Azure Database for PostgreSQL Flexible Server The VNet Data Gateway will be created in Tenant A, which is the same tenant as Microsoft Fabric. The PostgreSQL Flexible Server is located in Tenant B. Public access will be disabled, and the server should only be accessible through a Private Endpoint. We plan to configure cross-tenant VNet peering between VNet A in Tenant A and VNet B in Tenant B. We also plan to configure Private DNS so that the PostgreSQL FQDN can be correctly resolved to the private IP address of the Private Endpoint from the VNet Data Gateway side. I would like to confirm the following: Is it supported for a VNet Data Gateway to connect to a Private Endpoint located in a VNet belonging to another Microsoft Entra ID tenant through cross-tenant VNet peering? Is this architecture also supported when the resource behind the Private Endpoint is Azure Database for PostgreSQL Flexible Server? Has anyone implemented this architecture in a PoC or production environment? If you have implemented a similar architecture, I would greatly appreciate details about the actual configuration, particularly: VNet Data Gateway subnet configuration Cross-tenant VNet peering configuration PostgreSQL Private Endpoint configuration Private DNS Zone and VNet Link configuration DNS resolution from Tenant A to the PostgreSQL Private Endpoint in Tenant B NSG and routing configuration Azure RBAC permissions required in each tenant Fabric Connection / Gateway configuration PostgreSQL connector configuration If possible, I would also appreciate screenshots or examples of the actual Azure Portal and Microsoft Fabric Portal configuration, as well as ARM/Bicep/Terraform/CLI configuration examples. Are there any cross-tenant-specific limitations or considerations that would not normally apply to VNet peering within the same tenant? I found the following related discussion in the Microsoft Fabric Community: “3 Azure Databricks instances in 3 tenants - 1 VNET Data Gateway to connect from Power BI Service” In that discussion, an architecture is proposed where the VNet Data Gateway is deployed in the same tenant as Power BI Service, and it connects through cross-tenant VNet peering to Private Endpoints for Azure Databricks located in other tenants. I also found another implementation example using the following architecture: Power BI → VNet Data Gateway → VNet Peering → Azure Database for PostgreSQL Flexible Server What I would like to validate is essentially a combination of these two scenarios: Microsoft Fabric → VNet Data Gateway → Tenant A VNet → Cross-Tenant VNet Peering → Tenant B VNet → Private Endpoint → Azure Database for PostgreSQL Flexible Server I am particularly interested not only in whether this is technically possible or supported, but also in real-world implementation experience and configuration-level details. In particular, I would like to understand how Private DNS was configured across the tenant boundary and how DNS resolution and routing were implemented from the VNet Data Gateway subnet in Tenant A to the PostgreSQL Private Endpoint in Tenant B. If anyone has implemented this architecture, I would greatly appreciate screenshots, step-by-step configuration details, lessons learned, or any issues encountered during implementation. Microsoft documentation, reference architectures, technical blogs, GitHub examples, and PoC or production implementation examples would also be very helpful.
Is VNet Data Gateway → Cross-Tenant VNet Peering → PostgreSQL Private Endpoint supported?
Is VNet Data Gateway → Cross-Tenant VNet Peering → PostgreSQL Private Endpoint supported in Microsoft Fabric? I am designing an architecture where Microsoft Fabric connects to an Azure Database for PostgreSQL Flexible Server located in a different Microsoft Entra ID tenant, without using any public network connectivity. The proposed architecture is : The VNet Data Gateway will be created in Tenant A, which is the same tenant as Microsoft Fabric. The PostgreSQL Flexible Server is located in Tenant B. Public access will be disabled, and the server should only be accessible through a Private Endpoint. We plan to configure cross-tenant VNet peering between VNet A in Tenant A and VNet B in Tenant B. We also plan to configure Private DNS so that the PostgreSQL FQDN can be correctly resolved to the private IP address of the Private Endpoint from the VNet Data Gateway side. I would like to confirm the following: Is it supported for a VNet Data Gateway to connect to a Private Endpoint located in a VNet belonging to another Microsoft Entra ID tenant through cross-tenant VNet peering? Is this architecture also supported when the resource behind the Private Endpoint is Azure Database for PostgreSQL Flexible Server? Has anyone implemented this architecture in a PoC or production environment? If you have implemented a similar architecture, I would greatly appreciate details about the actual configuration, particularly: VNet Data Gateway subnet configuration Cross-tenant VNet peering configuration PostgreSQL Private Endpoint configuration Private DNS Zone and VNet Link configuration DNS resolution from Tenant A to the PostgreSQL Private Endpoint in Tenant B NSG and routing configuration Azure RBAC permissions required in each tenant Fabric Connection / Gateway configuration PostgreSQL connector configuration If possible, I would also appreciate screenshots or examples of the actual Azure Portal and Microsoft Fabric Portal configuration, as well as ARM/Bicep/Terraform/CLI configuration examples. Are there any cross-tenant-specific limitations or considerations that would not normally apply to VNet peering within the same tenant? I found the following related discussion in the Microsoft Fabric Community: “3 Azure Databricks instances in 3 tenants - 1 VNET Data Gateway to connect from Power BI Service” In that discussion, an architecture is proposed where the VNet Data Gateway is deployed in the same tenant as Power BI Service, and it connects through cross-tenant VNet peering to Private Endpoints for Azure Databricks located in other tenants. I also found another implementation example using the following architecture: Power BI → VNet Data Gateway → VNet Peering → Azure Database for PostgreSQL Flexible Server What I would like to validate is essentially a combination of these two scenarios: Microsoft Fabric → VNet Data Gateway → Tenant A VNet → Cross-Tenant VNet Peering → Tenant B VNet → Private Endpoint → Azure Database for PostgreSQL Flexible Server I am particularly interested not only in whether this is technically possible or supported, but also in real-world implementation experience and configuration-level details. In particular, I would like to understand how Private DNS was configured across the tenant boundary and how DNS resolution and routing were implemented from the VNet Data Gateway subnet in Tenant A to the PostgreSQL Private Endpoint in Tenant B. If anyone has implemented this architecture, I would greatly appreciate screenshots, step-by-step configuration details, lessons learned, or any issues encountered during implementation. Microsoft documentation, reference architectures, technical blogs, GitHub examples, and PoC or production implementation examples would also be very helpful.
Co-pilot usage Admin portal settings
Hello Community, We have a Fabric capacity in UK South.. So with the highlighted settings enabled; which regions would the data move across. Would it be bound to the Geo like Europe or there can be a possibility of it moving in any Geo (US /Asia) based on availability. I'm reffering Link for Enabling Highlighted Setting
