Fabric & Power Platform Engineer topics

Fabric & Power Platform Engineer - Are you using Microsoft Fabric only for analytics — or as a fo

Amby — Fri, 14 Aug 2026 09:37:51 GMT

Are you using Microsoft Fabric only for analytics — or as a foundation for enterprise AI?

Many organizations have built strong data platforms with Power BI, OneLake, Data Factory, and Real-Time Intelligence. The next challenge is turning that data into AI-powered decisions that are trusted, governed, and scalable.

At CoreShift 2026 (free virtual summit, Sept 15–16), industry experts will share practical approaches to:

• Build real-time intelligence with Microsoft Fabric
• Create trusted data foundations for AI
• Connect Fabric, governance, and AI together
• Move from dashboards to AI-driven actions
• Learn from real-world enterprise use cases and live demos

For those working with Fabric today:

What is your biggest challenge — governance, real-time data, OneLake architecture, or scaling AI beyond pilots?

Explore the agenda: Coreshift 2026, A Global Virtual Summit

Fabric & Power Platform Engineer - Title: Unable to Start Microsoft Fabric Trial – "Sorry, we are

HamzaTufail — Wed, 05 Aug 2026 06:06:45 GMT

Title:
Unable to Start Microsoft Fabric Trial – "Sorry, we are unable to start trial at this time"

Body:

Hi Fabric Community,

I'm trying to activate a Microsoft Fabric Trial for learning purposes, but I'm unable to start the trial.

My account details:

Free Microsoft account
Power BI Trial is active (59 days remaining)
Tenant: Default Directory
Region: Pakistan

When I click Start Fabric Trial or try to create a Lakehouse in a new workspace, I receive the following message:

"Sorry, we are unable to start trial at this time."

Here's what I've already verified:

Power BI Trial is active.
I can access both the Fabric Portal and the Admin Portal.
There are no existing Trial Capacities under Admin Portal > Capacity Settings > Trial.
Microsoft Fabric Service Health reports no active outages.
My workspace is empty and not assigned to a Fabric capacity.
I also reviewed the known issues page but couldn't find anything related to trial activation.

Error details:

Activity ID: c08cbfe8-e799-4231-9aa5-758896a5edc7
Request ID: f4127cfb-4030-4a7c-9ef8-e5229bfa61ea
Correlation ID: 979245da-14dc-60d6-0c08-6974031bbd05

Has anyone experienced this issue recently?

I'm wondering:

Is this related to Microsoft Fabric trial eligibility?
Could this be a tenant configuration issue?
Is there a limit on trial provisioning for new tenants?
Has anyone found a solution or workaround?

I'd appreciate any guidance or suggestions. Thank you!

Fabric & Power Platform Engineer - Hello Everyone! Excited to be part of this community! I'm curr

varsithareddy — Fri, 31 Jul 2026 05:09:17 GMT

Hello Everyone!

Excited to be part of this community! I'm currently preparing for the DP-700: Microsoft Fabric Data Engineer certification and would appreciate any exam tips, study resources, or guidance from those who have cleared it. Also looking for a voucher opportunity to support my certification journey. Thanks in advance!

Fabric & Power Platform Engineer - Hello everyone I have a query is anyone get the voucher or the

tanziyaashaq — Sat, 25 Jul 2026 14:57:28 GMT

Hello everyone I have a query is anyone get the voucher or the privete message then plx I want to response

It's humble request

Thanks for your precious time

Fabric & Power Platform Engineer - Has anyone found a scalable workaround for OneLake Security pr

RaghuCharyulu — Sat, 25 Jul 2026 08:37:05 GMT

Has anyone found a scalable workaround for OneLake Security predicate limitations?

Hi Fabric Community,

We're currently evaluating OneLake Security for an enterprise implementation and have run into a challenge with the current RLS model.

We have a centralized entitlement model where access is determined through security groups, country/region mappings, employee assignments, and related business tables. This works well in semantic models using relationship-based RLS, where filters can propagate across related tables.

With OneLake Security, however, predicates appear to be evaluated at the individual table level. This becomes challenging when the security attribute (Country, Region, Business Unit, etc.) doesn't physically exist in every table that needs to be secured.

I'm curious if anyone has encountered a similar challenge and found a scalable solution.

Some questions I'd love to hear feedback on:

Have you added security attributes to every curated/Gold table?
Are you using a centralized entitlement table and materializing security during ETL?
Are you combining OneLake Security with Semantic Model RLS?
Have you implemented a metadata-driven or automated approach that scales across many tables?
Any alternative architectures that worked well in production?

I'm particularly interested in real-world experiences, lessons learned, and trade-offs from organisations that have implemented OneLake Security at scale.

Looking forward to hearing how others have approached this.

#MicrosoftFabric #OneLake #OneLakeSecurity #RLS #DirectLake #DataGovernance #Lakehouse #PowerBI

Fabric & Power Platform Engineer - Hi everyone! 👋 Happy to be part of the community! I’m current

rprakash777 — Thu, 23 Jul 2026 19:03:27 GMT

Hi everyone! 👋

Happy to be part of the community! I’m currently diving deep into Microsoft Fabric while studying for the DP-700 certification, focusing mainly on Lakehouse architecture, PySpark, and Data Factory pipelines.

As I've been building out practice scenarios, I'm curious to hear how everyone here is approaching semantic modeling with Direct Lake mode vs traditional Import mode in real-world projects. Are there specific performance bottlenecks or constraints you ran into when scaling up?

Would love to hear your experiences or any tips! Looking forward to learning and collaborating with you all. 🚀

#MicrosoftFabric #PowerBI #DP700 #DataEngineering

Fabric & Power Platform Engineer - 5 Microsoft Fabric Features Every Beginner Should Know If you

tanziyaashaq — Thu, 23 Jul 2026 06:17:03 GMT

5 Microsoft Fabric Features Every Beginner Should Know
If you're just starting with Microsoft Fabric, the platform can feel overwhelming. Here are five features every beginner should explore first.
1. OneLake – One Place for All Your Data
OneLake is the central storage layer in Microsoft Fabric. Instead of keeping data in multiple places, you can store and access it from a single location.
Why it matters: Easier data management and collaboration.
2. Power BI Integration
Microsoft Fabric works seamlessly with Power BI, allowing you to create interactive dashboards and reports from your data.
Why it matters: Turn raw data into meaningful insights without switching platforms.
3. Data Factory
Data Factory helps you collect, move, and transform data from different sources using a simple visual interface.
Why it matters: Save time by automating data workflows.
4. Lakehouse
The Lakehouse combines the benefits of a data lake and a data warehouse, making it easier to store both structured and unstructured data.
Why it matters: One solution for all types of analytics.
5. Real-Time Analytics
Monitor and analyze streaming data as it arrives, helping you make faster decisions.
Why it matters: Ideal for tracking live events, IoT devices, and business operations.
Final Thoughts
Microsoft Fabric brings data engineering, analytics, and business intelligence together in one platform. Learning these five features is a great first step for anyone beginning their Fabric journey.
Question for the community:
Which Microsoft Fabric feature helped you the most when you started? Share your experience in the comments!

Fabric & Power Platform Engineer - Hi everyone! 👋 I'm Gamage, a Software Engineering student fro

rprakash777 — Wed, 22 Jul 2026 17:39:50 GMT

Hi everyone! 👋

I'm Gamage, a Software Engineering student from Sri Lanka 🇱🇰. Really glad to be part of this community!

I'm currently preparing for the DP-700 exam and diving deep into Microsoft Fabric—especially Lakehouse design, PySpark, and Data Factory pipelines.

Outside of data engineering, I work on full-stack web and mobile development. Happy to connect, collaborate on projects, and learn alongside everyone here! 🚀

#MicrosoftFabric #DataEngineer #DP700

Fabric & Power Platform Engineer - Excited to continue my journey as a Microsoft Fabric Ambassado

tanziyaashaq — Wed, 22 Jul 2026 12:29:10 GMT

Excited to continue my journey as a Microsoft Fabric Ambassador!

Every day I'm learning more about data analytics, Power BI, and Microsoft Fabric. My goal is to share what I learn with the community and help other students get started. Looking forward to creating more tutorials, blogs, and projects!

#MicrosoftFabric #PowerBI #DataAnalytics #Student #MicrosoftCommunity

Fabric & Power Platform Engineer -

sannavajjala — Sat, 18 Jul 2026 00:53:44 GMT

Fabric data agents can now plug into Copilot Studio as connected agents (preview) — thoughts on the compliance boundary tradeoff?

Microsoft just enabled a new pattern worth discussing: a Fabric data agent can now be added to a custom Copilot Studio agent as a connected agent, not just used standalone inside Fabric. In practice, that means a Copilot Studio agent's orchestrator can decide mid-conversation to call out to your Fabric data agent and ground its answer in warehouse, lakehouse, semantic model, KQL, or ontology data.
The part I want to flag for discussion is buried in the prerequisites rather than the headline feature description. Once you connect a Fabric data agent this way, its responses can leave Fabric's compliance boundary and geographic region, and get processed and stored under Copilot Studio's terms instead of Fabric's. Enabling this requires deliberately turning on cross-geo processing and storing for AI at the tenant level. That is not a small toggle for anyone working under data residency requirements.
There is also a channel restriction that seems easy to miss when planning a rollout: this setup is only formally validated for Microsoft Teams right now. It explicitly does not work in Microsoft 365 Copilot, even though that would be the more obvious place a lot of teams expected it to show up first.
A few things I am curious how others are handling:
Is anyone treating the cross-geo AI setting as its own governance gate, separate from the general Fabric data agent rollout, or bundling it into existing DLP and data boundary reviews?
For the authentication choice between user authentication and agent author authentication on the connected agent, which are you defaulting to, and why?
Anyone hit friction with data agent descriptions not being detailed enough for the orchestrator to reliably decide when to call the connected agent?

Fabric & Power Platform Engineer - Fabric data agents can now plug into Copilot Studio as connect

sannavajjala — Sat, 18 Jul 2026 00:50:52 GMT

Fabric data agents can now plug into Copilot Studio as connected agents (preview), thoughts on the compliance boundary tradeoff?

The part I want to flag for discussion is buried in the prerequisites rather than the headline feature description. Once you connect a Fabric data agent this way, its responses can leave Fabric's compliance boundary and geographic region, and get processed and stored under Copilot Studio's terms instead of Fabric's. Enabling this requires deliberately turning on cross-geo processing and storing for AI at the tenant level. That is not a small toggle for anyone working under data residency requirements.

There is also a channel restriction that seems easy to miss when planning a rollout: this setup is only formally validated for Microsoft Teams right now. It explicitly does not work in Microsoft 365 Copilot, even though that would be the more obvious place a lot of teams expected it to show up first.

A few things I am curious how others are handling:

Is anyone treating the cross-geo AI setting as its own governance gate, separate from the general Fabric data agent rollout, or bundling it into existing DLP and data boundary reviews?

For the authentication choice between user authentication and agent author authentication on the connected agent, which are you defaulting to, and why?

Anyone hit friction with data agent descriptions not being detailed enough for the orchestrator to reliably decide when to call the connected agent?

Fabric & Power Platform Engineer - Hello everyone! I am excited to share that I recently complet

kalyan1499 — Thu, 16 Jul 2026 17:40:26 GMT

Hello everyone! I am excited to share that I recently completed my Master’s in Business Analytics.

I have 3+ years of working in Finance and Healthcare Domians non-tech, want to start a career in tech and see myself as Data engineer.

I am looking to connect with professionals, mentors, and fellow tech enthusiasts. If you have any guidance, learning paths, or advice for a transitioning professional, I would highly appreciate your insights!

Fabric & Power Platform Engineer - Hi Everyone! Excited to join the Fabric & Power Platform Engin

rpart001_r — Thu, 16 Jul 2026 06:21:45 GMT

Hi Everyone! Excited to join the Fabric & Power Platform Engineer group

Fabric & Power Platform Engineer - Hi Community, I've been exploring Dataflows Gen2 in Microsoft

sannavajjala — Fri, 03 Jul 2026 02:35:02 GMT

Hi Community,

I've been exploring Dataflows Gen2 in

Microsoft Fabric and would love to hear how others are using them in production.

I'm particularly interested in learning about real-world best practices, such as:

When do you choose Dataflows Gen2 instead of Notebooks, Pipelines, or SQL?

How do you structure large Dataflows for maintainability?

What transformations should stay in Power Query versus downstream in Lakehouse or Warehouse?

How do you handle incremental refresh and large datasets?

What are your recommendations for error handling and monitoring?

Any performance tuning tips that have made a significant difference?

How do you manage development, testing, and deployment across environments?

Are there any common pitfalls or anti-patterns to avoid?

If you've implemented Dataflows Gen2 in production, I'd appreciate hearing what worked well and what you would do differently.

Looking forward to learning from the community!

Fabric & Power Platform Engineer - 🚀 Excited to join the Fabric & Power Platform Engineer group!

Swagath1295 — Thu, 02 Jul 2026 08:10:47 GMT

🚀 Excited to join the Fabric & Power Platform Engineer group!

I'm Sai Swagath Gajula from India 🇮🇳.

Currently working as a Senior BI Analyst at Tiger Analytics, with experience in data analytics, business intelligence, and reporting solutions.

I'm passionate about leveraging Microsoft Fabric, Power BI, and Power Platform to build scalable data solutions and deliver business insights.

Looking to learn: Advanced Microsoft Fabric capabilities, Lakehouse architecture, Data Factory Pipelines, Real-Time Analytics, and Power BI best practices.

Happy to contribute: My experience in BI analytics, dashboard development, data modeling, and lessons learned from working on enterprise-scale analytics projects.

Looking forward to learning, collaborating, and growing together with the community! 🚀📊✨

Fabric & Power Platform Engineer - @pradeepthira Hi Everyone! 👋 Excited to join the Fabric & Pow

Gautam_Kumar01 — Wed, 01 Jul 2026 14:41:59 GMT

pradeepthira Hi Everyone! 👋 Excited to join the Fabric & Power Platform Engineer group

I'm Gautam Kumar from Bihar, India 🇮🇳

Currently Doing BCA & Founder of ResumeCraft - a free ATS Resume Builder for freshers.

Currently learning Microsoft Fabric to become a Data Engineer. Preparing for DP-700 certification.

Looking to learn: Lakehouse, Data Factory Pipelines, Power BI dashboards.

Happy to contribute: My journey as a student founder + helping freshers with tech resumes.

Building in public: resumecraft.online

Let's learn and grow together! 🚀

https://resumecraft.co.in/

#MicrosoftFabric #DataEngineer #BuildInPublic

Fabric & Power Platform Engineer - 👋 Welcome to the Fabric & Power Platform Engineer User Group!

sannavajjala — Tue, 30 Jun 2026 13:53:23 GMT

Welcome to the Fabric & Power Platform Engineer User Group!

Hello everyone, and welcome!

I'm excited to have you as part of the Fabric & Power Platform Engineer community.

This group was created to bring together professionals who are passionate about building, managing, and governing solutions across Microsoft Fabric, Power Platform, Dynamics 365, Microsoft 365, and Enterprise AI.

Whether you're just getting started or have years of experience, this community is a place to learn, collaborate, and share real-world knowledge.

What you can expect from this group

Technical discussions and best practices
Microsoft Fabric administration and governance
Power BI, Semantic Models, and OneLake
Data Engineering and Data Factory
Power Platform architecture and governance
Copilot Studio and AI Agents
Enterprise AI and Microsoft 365 integration
Community events, blogs, and learning resources

I'll be regularly sharing:

Technical articles
Architecture diagrams
Best practices
Microsoft updates
Discussion topics
Conference learnings
Hands-on tips from real-world implementations

Let's get to know each other!

Please introduce yourself in the comments:

Your name
Where you're from
Your role
What you'd like to learn or contribute

Thank you for joining the community! I'm looking forward to learning together and building a valuable space for everyone interested in Microsoft Fabric and the Power Platform.

Welcome aboard!