The Fabric community is upgrading!
We're excited to announce that the Microsoft Fabric Community will move to an upgraded platform experience beginning August 14, 2026. This upgrade is a major milestone that gives us a more modern, scalable foundation while enabling faster innovation and a better overall community experience. Most importantly, it positions us to respond quicker to feedback and continue improving the community over time. Why We're Upgrading The current platform has served us well, but it's built on an older architecture that makes it difficult to take advantage of modern technologies and deliver improvements at the pace we'd like. By upgrading to the latest platform, we're creating a more flexible, future-ready foundation that will allow us to: Deliver updates and enhancements faster Improve reliability and maintainability Respond more quickly to community needs Continue evolving the experience based on feedback What Members Can Expect The majority of the community experiences you use today will continue to be available after the upgrade, along with several improvements, including: A more modern and intuitive user experience Improved navigation and accessibility Enhanced filtering and content discovery Continued investments in performance and usability Updated Ideas statuses that provide clearer visibility into suggestion progress While a small number of enhancements will follow shortly after launch, this upgrade establishes the foundation for ongoing innovation and future improvements. RSS Feeds RSS feeds will continue to be available after the upgrade. As part of the upgrade, RSS feed URLs will change. RSS feed URLs are configured to automatically redirect to the new RSS feed URLs, so subscribers should continue to receive updates without interruption. Will my existing RSS subscriptions stop working? No. Exisitng RSS feed URLs will automatically redirect to the new URLs. Most users should not need to take any action. If you maintain custom automations or integrations that reference RSS feed URLs directly. Upgrade Timeline August 13, 2026 In preparation for the upgrade, any new support requests that the community managers need to process, such as username changes, email mappings, etc, will be paused started August 13th until after August 16th. August 14, 2026 | 7:00 PM PST Upgrade Begins The community will enter read-only mode while the upgrade is performed. During this time: Existing content will remain viewable New posts, replies, and content creation will be temporarily unavailable A maintenance page may be displayed during portions of the upgrade August 15, 2026 Validation & Stabilization Our team will validate key experiences, monitor platform health, and address any necessary stabilization work before reopening the community. August 16, 2026 Community Returns to Full Operation The upgraded Microsoft Fabric Community will be fully available to all members. Looking Ahead This upgrade is about more than technology. It's about creating a stronger foundation that allows us to move faster, deliver improvements more consistently, and build a better community experience for everyone. Thank you for your patience, support, and contributions to the Microsoft Fabric Community. We're excited for the future of Fabric and Power BI and look forward to building the next generation of the community together. Known Issues Post Upgrade We are aware there are a few minor issues after the upgrade. The team is actively investigating and working on fixes.
I can't Activate my 60 days free fabric trial
I am unable to activate the 60-day Microsoft Fabric trial. Although my 60-day Power BI trial has been activated successfully, the Fabric trial is not available for my account. Whenever I try to activate it, I receive the message: “Your free Power BI trial gives you 60-day access to Power BI paid features. A Fabric trial isn't available for your account.” I have already created a Microsoft Entra ID tenant and am using an @onmicrosoft.com organizational account, but I am still unable to access the Fabric trial.
How to deploy OrgApp and OrgAppAudience from one workspace to another workspace using GitHub Actions
Hi Team - I was looking to achieve the CI/CD for OrgApp and OrgAppAudience. I have a workspace-Dev which is Git Integrated and has the OrgApp and OrgAppAudience in below structure format. Sales Results.OrgApp ├── .platform ├── definition └── .children └── Sales Results.OrgAppAudience ├── .platform └── definition I'm trying with to achieve this deployment automation with GitHub actions. Steps performed are 1. Install fabric-cli 2. Login using Managed Identoty to fabric CLI 3. Deploy using fab deploy with config file with Items in scope as "OrgApp" and "OrgAppAudience" Observation Error - It looks the Fabcric CLI does not support this type of deployment. Please let me know the possibilities to achieve this deployment using GitHub actions only. FAQ on the Fabric User Groups
Azure Artifact Feed - Connection string not supported
Hi everyone, I'm trying to create a new Azure Artifact Feed (Preview) connection in Microsoft Fabric, but I'm consistently getting the following error: Unable to create connection for the following reason: Connection string is not supported. Details: Query contains unsupported function. Function name: AzureArtifactFeed.Contents Environment Microsoft Fabric Connection Type: Azure Artifact Feed (Preview) PyPi Feed URL format: https://pkgs.dev.azure.com/<organization>/_packaging/<feed>/... Creating the connection from Manage Connections and Gateways > New Connection > Cloud Questions Has anyone successfully configured an Azure Artifact Feed connection in Fabric recently? Could this be related to the note displayed in the UI indicating that some cloud connections are not supported by Dataflows Gen1 and Datamarts? Any insights or confirmation that this is a known issue would be greatly appreciated. Thanks!
Cancel Dataflow Transaction API returns 403 Unauthorized — worked fine, stopped suddenly (PPU)
Hi all, We're hitting a persistent 403 Forbidden error when calling the Cancel Dataflow Transaction REST API, and we've exhausted every configuration check we can think of. Posting here in case others have seen this or a Microsoft employee can point us in the right direction. Endpoint: POST https://api.powerbi.com/v1.0/myorg/groups/{groupId}/dataflows/transactions/{transactionId}/cancel Error returned: json {"error":{"code":"Unauthorized","message":"User is not authorized"}} Important context: This was working normally until recently and then stopped from one day to the next, with no changes made on our side to the app registration, tenant settings, or workspace roles. Environment: Workspace capacity: Premium/PPU Auth method: Service principal via client_credentials (Azure AD), resource https://analysis.windows.net/powerbi/api App permission: Dataflow.ReadWrite.All (Delegated), with admin consent granted Service principal's role in the workspace: Admin Tenant setting "Service principals can call Fabric public APIs": Enabled for the whole organization Calling this via an n8n HTTP Request node, though we've also reproduced it outside that tool (see below) Troubleshooting steps already completed: GET Dataflow Transactions works fine with the exact same app/token — this rules out a token, scope, or workspace-role problem, since both endpoints require the same permission level. Tested with a brand-new transaction, triggering a fresh refresh and calling cancel immediately while the transaction was still InProgress. Same 403 — rules out a stale/already-concluded transaction as the cause. Reproduced the same 403 using the official "Try It" tool on the Microsoft Learn documentation page for this API, authenticated interactively as a real Power BI/tenant admin user — not via the service principal at all. This strongly suggests the issue isn't specific to our app or service principal setup. Confirmed workspace capacity is Premium/PPU, not Pro — ruling out a licensing/capacity limitation on write operations for dataflows. Confirmed the Fabric admin tenant setting for service principals calling public APIs is enabled org-wide, and separately confirmed this setting is unrelated to the endpoint in question (it's not an /admin/* API). Expected behavior: A 200 OK response with the cancellation status (e.g. SuccessfullyMarked), consistent with the documentation, since every permission/role/capacity prerequisite checks out and the read operation on the same resource succeeds without issue. Transaction IDs used in testing (for internal log tracing): 2026-08-07T19:59:34.4770000Z@50b2c2ee-1ed0-4321-8d54-b7ef6c40f795$224523402 [add the new transaction ID you tested] Question for the community: Has anyone else seen the Cancel Dataflow Transaction endpoint suddenly start returning 403 without any configuration changes? Is there a known service-side issue or recent regression affecting this specific endpoint? Any pointers on what else to check, or whether this needs a formal support ticket, would be very welcome. Thanks in advance!An introduction to Fabric Apps
One of the shiny new items in Microsoft Fabric is Fabric Apps, and these open up a bunch of possibilities for what is possible in Fabric. Fabric Apps enabled functionality that previously would have needed to be custom workloads, which are a lot more complex to get up and running than Fabric Apps. What is a Fabric App? A Fabric app (built on the Rayfin SDK) is a Fabric item with two components, a backend service for data access and authentication, and a front end web app. When a Fabric App is created, Fabric automatically creates a SQL Database, an authentication server, and static content hosting for the front end web app. You provide data models for your application in TypeScript and Fabric Apps automatically creates a database schema and type-safe GraphQL API. Before you can create one, a tenant admin has to enable it. It's still in preview, so it needs to be explicitly enabled, and Fabric Apps are not available in all regions. Fabric Apps are currently available in the following regions (As of August 18th, 2026): US - Central US US - North Central US US - West US US - West US 2 Europe - West Europe France Central Italy North Norway East Switzerland North UAE North South Africa North Asia - East Asia Asia - Southeast Asia Australia East India - Central India Japan East Korea Central To enable the preview in your tenant: 1. Sign in to the Fabric admin portal (https://app.fabric.microsoft.com/admin-portal). 2. Go to Tenant settings. 3. Under Enable Fabric App Items (preview), toggle it to Enabled, scoped to your whole org or specific security groups. 4. Select Apply. Give it a few minutes to propagate. If you don't see App (preview) in your New item list, either this is why or your capacity is in an unsupported region. Part 1: Create and Deploy the Sample App Create the item in Fabric Creating the item itself is the same as any other Fabric item: 1. Open a workspace where you have contributor or higher access. 2. Select New item. 3. Search for App (preview), select it, give it a name, and select Create. This creates the item, and all the backend services I mentioned before. From here, you can select a blank app, or start with a sample To-Do App, or a sample Data App. For the sake of this post, I am going to select the To-Do App. Once selected, Fabric will start to deploy your app and present you with some instructions for getting the Rayfin CLI up and running. Create the project with npm From a terminal, run the command shown in the Fabric App: npm create Microsoft/rayfin@latest -- "<appitemname>" --template todoapp --workspace <workspacename> That one command creates a full project from the `todoapp` template and wires it to the workspace and item you just created, using the Rayfin CLI. Then change your working directory to the project directory that was just created cd <your project directory> Run it locally npm run dev This spins up the frontend and backend together against your Fabric backend, so you can test changes before anything goes live. By default it runs at `http://localhost:5173`. Deploy with npx npx rayfin up Under the hood, `rayfin up` does six things in order: 1. It creates (or reuses) the Fabric App item 2. It retrieves the publishable key 3. It syncs your `rayfin.yml` settings 4. It applies the database schema from your TypeScript models 5. It builds and deploys static content, 6. Finally, it writes the deployment details back to `rayfin.yml` and a `.env.fabric-<workspacename>` file. When it finishes, you get a live hosting URL, a Fabric portal link, and a deployment ID. Tip: Want to check what a deploy will do without actually running it? Use `npx rayfin up --dry-run`. To check current deployment state at any time, use `npx rayfin up status`. Part 2: The Database Objects Here's the part that surprised me the most coming from a data background: there's no SQL to write, and no separate database designer to open. Your data models are TypeScript classes, and Fabric Apps turns them directly into database tables. Defining an entity Entities or tables live in `rayfin/data/` and use the `@entity()` decorator from `@microsoft/rayfin-core`, as well as field decorators for each column: Each table needs to be defined in it's own typescript file. import { entity, uuid, text, boolean, date } from '@microsoft/rayfin-core'; @entity() export class Todo { @uuid() id!: string; text() title!: string; text({ optional: true }) description?: string; @boolean({ default: false }) isComplete!: boolean; date() createdAt!: Date; date() updatedAt!: Date; } Every entity gets a UUID `id` primary key. If you don't include it in your entity definition, Fabric will automatically add it. When records are inserted into your table, Fabric will generated a UUID server-side unless you supply your own. Composite keys and custom key names aren't supported. The full set of field decorators: `@uuid()`, `@text()`, `@int()`, `@decimal()`, `@boolean()`, `@date()`, `@email()`, and `@set()` for enumerated strings. Modifiers like `{ optional: true }`, `{ unique: true }`, `{ default: value }`, and `{ min, max }` add constraints to the columns. Note: The TypeScript `?` optional marker only affects the compile-time type. To actually make a database column nullable, you need `{ optional: true }` in the decorator itself. Relationships If your app has more than one table, use `@one()` and `@many()` to define relationships, and Fabric auto-generates the foreign key column for you following a `{property}_id` convention. One-to-many and many-to-one are supported; many-to-many is not, so model it with an explicit join table instead. Registering the schema Once every entity has been created, they then need to be added to `rayfin/data/schema.ts`: import { Todo } from './Todo.js'; export type TodoAppSchema = { Todo: Todo; }; export const schema = [Todo]; Applying schema changes Whenever you add or edit an entity: npx rayfin up db apply If a change would drop a column or rename a table, the CLI blocks it and warns you first. You can override with `--force`, but know that as soon as you add --force, you will be making a destructive change that cannot be undone. Warning: Using `--force` on a schema apply can cause data loss and cannot be undone. After being deployed, you are able to see the database in your workspace under the Fabric App. The SQL Database child item will allow you to access the Fabric SQL query editor where you can run SQL queries to read data. Don't change things in SQL here, as anything you change will be overwritten the next time you deploy the schema. Wrapping Up This post covers creating the sample app, deploying it, and how the database objects work. The full version, including how authentication (local email/password vs. Fabric SSO) and the front end (the RayfinClient data calls) work, is on the blog, linked below. Microsoft Learn references: Create your first Fabric app (https://learn.microsoft.com/en-us/fabric/apps/create-app) | Fabric Apps project structure (https://learn.microsoft.com/en-us/fabric/apps/project-structure) | Define data models for Fabric Apps (https://learn.microsoft.com/en-us/fabric/apps/data-models) | Deploy a Fabric app to Fabric (https://learn.microsoft.com/en-us/fabric/apps/deploy-app) Read more: Read the full post, including the Authentication and Front End sections, on the Fabric Field Notes blog: https://www.fabricfieldnotes.ca/blog/2026/08/18/an-introduction-to-fabric-apps
Need help activating Fabric Trial
As far as I know I have met all the conditions for a fabric trial eligibility, I have a organization email address and everything but it still says that I'm not eligible for it. I was able to activate the PowerBI trial. I am the tenant and the admin for the organization. Also I am not able to create a support ticket to microsoft.
I can't see my synapse link configuration
In June/July Microsoft moved the Synapse Link configuration page in Power Apps, I was able to find it after a quick internal pow-wow, this morning I get an error on all of my configurations, the ambiguous 'Something went wrong'. These are Dynamics F&O synapse link configs, the data is flowing, I can't see or mange the tables. Is anyone else seeing this? Options short of unlinking and re-linking? I've tried incognito mode restarting all the usual, I'm convinced it's not me 😁I checked Power Apps open bugs nothing jumps out at me...
Upstream and Downstream relations not coming through fabric rest api
Hi all, We are currently using the Fabric REST APIs to retrieve lineage relationships. However, the API is not returning the expected upstream and downstream relationships.The lineage is visible in the Microsoft Fabric UI for the same item, but the REST API response does not contain the corresponding upstream/downstream relationships.For example We have a Fabric workspace containing a chain similar to: Source → Dataflow → Lakehouse → Semantic Model → Power BI Report The Fabric UI shows the lineage between these items. However, when we query the corresponding item through the Fabric REST API, the upstream/downstream relationships are totally blank. If the REST API does not currently provide complete lineage, what is the recommended Microsoft-supported API for extracting complete upstream and downstream lineage across an entire Fabric tenant? Is the Fabric REST API expected to return the same upstream/downstream lineage that is displayed in the Fabric UI? Are there limitations on which Fabric item types support upstream/downstream lineage through the REST API?
