Rayfin

Changelog

What changed in each Rayfin release these docs cover — new features, behavior changes, and step-by-step upgrade instructions, linked to the pages that document them.

Every @microsoft/rayfin-* package — the SDK packages, the connectors, the CLI, and @microsoft/create-rayfin — ships with the same version number. These docs are written against Rayfin 2.0.0.

Version tags

Pages tag anything added or changed after Rayfin 1.35.0. Each tag links back to the release on this page that introduced it.

TagMeaning
New in 2.0Did not exist before that release.
Changed in 2.0Existed, but its behavior, default, or name changed in that release.
Deprecated in 2.0Still works, but has a replacement.
Removed in 2.0No longer works from that release.
PreviewShipped, but its shape may still change.
ExperimentalBehind a feature flag or a gradual rollout.

Untagged content applies to Rayfin 1.35.0 and later. A patch tag such as New in 1.35.1 means the change arrived in that patch release.

Check your version

Every Rayfin package in a project should report the same version:

npm ls --depth=0 | grep @microsoft/
npx rayfin --version

On Windows PowerShell, use npm ls --depth=0 | Select-String '@microsoft/'.

Upgrade to 2.0

Rayfin 2.0 is a major release. The client is now composed with RayfinClient.create, and several 1.x imports, options, and names are gone without compatibility shims, so a 1.x project does not compile against 2.0 packages until you work through these steps. If you are on 1.35 or earlier, complete Upgrade to 1.36 first. Steps 6 through 9 apply only if you use that feature.

  1. Update the packages. Set every @microsoft/rayfin-* dependency — plus @microsoft/fabric-user-data-functions and @microsoft/rayfin-local-dev — to 2.0.0 in each package.json, including the functions package's own. The 2.0 client depends only on @microsoft/rayfin-lib, so add @microsoft/rayfin-auth and @microsoft/rayfin-data — and @microsoft/rayfin-functions, @microsoft/rayfin-connectors, or @microsoft/rayfin-storage if you use them — to the package that builds the client. Replace @microsoft/rayfin-connector-kusto with @microsoft/rayfin-connector-eventhouse. Then run npm install.
  2. Check TypeScript. The package that holds your schema needs TypeScript ^5.7.2 or ^6.0.2. If schema compilation reports a schema file outside a "type": "module" scope, create rayfin/package.json containing {"type": "module"}, or set "type": "module" in the app's package.json, as the message suggests.
  3. Rebuild the client. Replace new RayfinClient(...), ConnectorsRayfinClient, ExtendableRayfinClient, and RayfinServerClient with RayfinClient.create. Pass browserSession() — or suppliedToken() in Node.js — as auth, and register dataService(), functionsService(), connectorsService(), and storageService() as needed. Move authStorage and the other session options into browserSession(), replace useProxy with baseUrl: '', and derive the client type with ReturnType<typeof createClient>. See Migrate from 1.x.
  4. Fix imports. Import storage declarations and claims types from @microsoft/rayfin-core instead of @microsoft/rayfin-core/experimental, and schema types from their owning packages — @microsoft/rayfin-data, @microsoft/rayfin-functions, @microsoft/rayfin-connectors — instead of @microsoft/rayfin-client. Remove imports from any dist/ path. See Deprecations.
  5. Fix data queries. Run the type-check: results now contain only the fields you select. Add .select([...]) wherever code reads fields from findById, findMany, or findFirst, and add the [] marker to to-many relationship paths ('notes[].title'). The client no longer turns date- and boolean-looking strings into Date objects and booleans for you, so convert selected dates and booleans explicitly. See Querying.
  6. Functions. Install @microsoft/fabric-user-data-functions@2.0.0 in the functions project; the CLI refuses to generate types or deploy with an older worker. Keep the local host.json extension bundle at [4.49.0, 5.0.0). See Run functions locally.
  7. Storage. Remove storage from RAYFIN_FEATURE_FLAGS, register storageService() on the client, and replace prefix options with full object paths. See Storage.
  8. Connectors. Register connectors with connectorsService(). Change type: kusto to type: eventhouse with auth.type: application, and move its queries into additionalPayload — see Eventhouse. Node.js scripts that relied on the CLI connector middleware must pass host: { type: 'cli' }.
  9. Frontend build. If frontend code imports entity classes as values and the app uses @vitejs/plugin-react-swc, enable Stage 3 decorators in the plugin. See Project structure.
  10. Verify. Run the type-check, tests, and production build — including the functions project — then npx rayfin up --dry-run, npx rayfin up, and npx rayfin up status.
PromptUpgrade my Rayfin project to 2.0.0
Upgrade my Rayfin project to Rayfin 2.0.0. Read https://rayfin.ai/docs/reference/changelog.md and https://rayfin.ai/docs/reference/sdk/rayfin-client.md first. 1. Set every @microsoft/rayfin-* dependency, plus @microsoft/fabric-user-data-functions and @microsoft/rayfin-local-dev where present, to exactly 2.0.0 in every package.json (including the functions package). Add @microsoft/rayfin-auth and @microsoft/rayfin-data — and @microsoft/rayfin-functions, -connectors, or -storage if the app uses them — to the package that creates the client. Replace @microsoft/rayfin-connector-kusto with @microsoft/rayfin-connector-eventhouse. Ensure the schema package uses TypeScript ^5.7.2 or ^6.0.2. Run npm install. 2. Replace every `new RayfinClient(`, `new ConnectorsRayfinClient(`, `new RayfinServerClient(`, and `ExtendableRayfinClient` with a synchronous factory that calls RayfinClient.create: browserSession() from @microsoft/rayfin-auth in browser code (move authStorage to `storage`), suppliedToken({ accessToken }) in Node.js code, and register only the services the app uses with dataService, functionsService, connectorsService({ configs, runtime }), and storageService. Replace useProxy with baseUrl: ''. Export `type AppClient = ReturnType<typeof createClient>`. 3. Move imports from @microsoft/rayfin-core/experimental to @microsoft/rayfin-core, import EntitySchema, FunctionsSchema, and connector types from their owning packages, and remove any import from a dist/ path. 4. Run the type-check. Where code reads fields from findById, findMany, or findFirst, select them explicitly with .select([...]); add [] to to-many relationship selections such as 'notes[].title'; convert selected Date and boolean values explicitly. 5. If a connector in rayfin/rayfin.yml has `type: kusto`, stop and list it for me: it must move to `type: eventhouse`, `auth.type: application`, and saved queries in additionalPayload as described at https://rayfin.ai/docs/connectors/eventhouse.md. 6. Remove `storage` from RAYFIN_FEATURE_FLAGS and replace Storage `prefix` options with full object paths. 7. Run the type-check, tests, and build for every workspace including functions, then run npx rayfin up --dry-run and report the result before deploying.

Rayfin 2.0

Released 2026-11-12. The headline changes:

  • One composed client. RayfinClient.create, with an explicit auth adapter and only the services you register, replaces the 1.x client classes. Breaking.
  • Results typed by what you select. Query and mutation results contain only the fields you request, and to-many selections use a [] marker. Breaking for code that read unselected fields.
  • Storage is generally available, with rayfin storage init to add it to an app.
  • Dynamic auth claims mint app-defined claims into tokens from a udf.authClaims function.
  • Connectors. Kusto is now Eventhouse and runs saved queries; the new Fabric IQ connector answers natural-language questions over Power BI data.
  • Functions. Custom audiences, ctx.user.id for owner stamping, and experimental raw SQL.
  • Observability (experimental) allocates an Application Insights resource per app and queries it with rayfin telemetry.
  • TypeScript 6 is supported for schema compilation.

Rayfin 2.0.0

Released 2026-11-12.

Client and SDK

  • RayfinClient.create({ baseUrl, publishableKey, auth, services }) replaces new RayfinClient(), ConnectorsRayfinClient, ExtendableRayfinClient, RayfinServerClient, and the default export. Authentication is an explicit adapter — browserSession() or suppliedToken() — and client.data, client.functions, client.connectors, and client.storage exist only when you register their adapters. @microsoft/rayfin-client
  • @microsoft/rayfin-client depends only on @microsoft/rayfin-lib; apps declare the adapter packages they use, and import schema types from the owning packages. Install the packages your client uses
  • client.dispose() releases a client's resources; construction failures use ClientCompositionError codes; AuthError is one class shared by every package. Client errors
  • Every package declares an exports map. @microsoft/rayfin-core/experimental, @microsoft/rayfin-core/decorators, @microsoft/rayfin-client/experimental, and deep dist/ imports no longer resolve. Package entry points
  • NetworkError carries serverErrorCode, retryAfterSeconds, and consentUrl, and access-token callbacks can be asynchronous. @microsoft/rayfin-lib
  • RayfinRuntimeConfig adds applicationInsightsConnectionString. @microsoft/rayfin-client

Data

  • Result types follow the selection. Queries without .select() — including findById, findMany, and findFirst — return the primary key only. Querying
  • The data client no longer converts date- and boolean-looking strings by inspecting their values, so selected dates are typed Date | string and booleans boolean | 'true' | 'false', in row and aggregation results. Convert them explicitly. Field types
  • To-many relationship selections need the [] marker, such as 'notes[].title'; malformed or conflicting paths fail before the request is sent. Querying
  • Mutation results contain the primary key plus the fields you sent, delete returns the key only, and a relationship can be set with its object or its foreign key. Mutations
  • dataService<AppSchema>() registers client.data; EntitySchema and TypedDataClients come from @microsoft/rayfin-data. Data
  • Schema compilation supports TypeScript 6 and requires ^5.7.2 || ^6.0.2. Modeling entities
  • rayfin init writes NodeNext schema settings with ESNext.Decorators and Node types, adds @types/node, and adds rayfin/package.json to apps that are not ES modules, which makes rayfin/ its own package boundary. Project structure, Modeling entities
  • The CLI rejects entity property names that are not valid GraphQL field names before anything is applied; map odd column names with { column: '...' }. Modeling entities
  • Storage declarations and claims types are exported from the @microsoft/rayfin-core root, and the /experimental, /decorators, /analysis, and /schema entry points are removed. @microsoft/rayfin-core
  • Functions can stamp owner fields with ctx.user.id, and policies can compare dynamic claims. Permissions
  • @vitejs/plugin-react-swc compiles entity classes once Stage 3 decorators are enabled, and the templates enable them. Form validation

Auth

  • browserSession() from @microsoft/rayfin-auth provides client.auth; the 1.x top-level client options authStorage, persistSession, autoRefreshToken, and multiTabSync move into it, and apps install @microsoft/rayfin-auth themselves. Sessions
  • Dynamic auth claims: declare services.auth.dynamicClaims, write one udf.authClaims provider, filter on the claims in policies, and read them with client.auth.getClaims() and ctx.getClaims(). Dynamic auth claims
  • isAuthenticated is false while the access token is expired. Sessions refresh shortly before expiry and retry transient failures, signOut() renews a lapsed token before revoking it, and concurrent refreshes no longer replay a rotated refresh token. Sessions
  • client.dispose() releases auth timers and listeners without signing out; new and queued refreshes then reject with AUTH_DESTROYED. Sessions
  • Fabric sign-in rejects with FABRIC_AUTH_POPUP_CLOSED about a second after the user closes the sign-in window instead of waiting five minutes, and the Fabric SSO docs list every sign-in error code. Fabric SSO
  • FabricAuthOptions.tenantId, sent to the portal as ctid, skips home-tenant discovery. Fabric SSO
  • Fabric embedded hints take precedence over external embed host discovery. Embed in your own portal
  • signInWithEntraToken() reports SIGN_IN_DENIED and AUTH_CLAIMS_* codes, and takes a browser-session client's auth or a standalone Auth. Sign in with an Entra token
  • rayfin login checks that Microsoft Entra ID is reachable before opening the browser, ends network failures with recovery steps — including a WSL2 fix — and writes device-code prompts to stderr so --json output stays one object. rayfin login

Functions

  • Register functionsService<AppFunctionsSchema>() from @microsoft/rayfin-functions, install that package directly, and import FunctionsSchema from it. Calling functions
  • Functions packages must use @microsoft/fabric-user-data-functions@2.0.0. The CLI writes runtime metadata schema 3.0, blocks an older worker, and prints the npm install command that fixes it. Functions
  • ctx.user.id exposes the caller's subject ID for owner stamping. Writing functions
  • Custom audiences: declare an application ID or an https:// or api:// resource URI and read its token from ctx.Tokens; rayfin up rejects an invalid audience before it deploys. Connections
  • Raw SQL against the app database with RayfinContext & WithSql and ctx.sql. Experimental Raw SQL
  • The Vite adapter forwards function calls to the deployed backend when no local Functions host is configured. Calling functions
  • rayfin dev warns when host.json allows an old Preview extension bundle, and when the local Functions host cannot sign in without a terminal window, rayfin dev prints the host.json fix instead of a generic hint. Run functions locally
  • rayfin secret set --env-file records every name in rayfin.yml and regenerates the secret types, and deployed functions can cache a secret value for a few minutes after you rotate it. Secrets
  • rayfin up functions deploy explains a 404, and a project whose only function is udf.authClaims deploys. Deploying functions
  • A guide to CSV bulk import functions with row-level validation. Bulk import

Storage

  • Storage is generally available, needs no feature flag, and is remote-only. Storage
  • rayfin storage init sets Storage up in local project files without deploying. rayfin storage
  • rayfin up storage apply and rayfin dev storage apply are always available, and a Fabric-backed rayfin dev applies folder declarations to the remote backend. Apply Storage configuration
  • Folder declarations import from @microsoft/rayfin-core; the @microsoft/rayfin-core/experimental path is removed. Migrate from 1.36 Storage
  • storageService() registers Storage on RayfinClient.create; createStorageClient stays public. @microsoft/rayfin-storage
  • Operations take complete object paths, the prefix option is removed, and invalid paths throw InvalidName. Upload and download files
  • Removing a folder declaration permanently deletes its objects, and removing a non-empty folder needs --force. Remove a folder

Connectors

  • The Kusto connector is renamed Eventhouse — type, package, runtime, and types. It accepts only application auth, where 1.36 kusto accepted only delegated, and runs only queries saved in additionalPayload, called by queryId. New Eventhouse connectors are still held back. Eventhouse
  • The Fabric IQ connector (fabriciqmcp) asks natural-language questions over Power BI data through MCP. Fabric IQ
  • Category B connectors accept additionalPayload: kept verbatim, at most 64 KiB and 32 levels deep, rejected on Category A types, and never a place for secrets. Save queries in additionalPayload
  • connectorsService() from @microsoft/rayfin-connectors, which apps now install directly, replaces ConnectorsRayfinClient. Its host defaults to standalone, including in Node.js, and each config is checked against its connector's marker type. Client setup
  • Generated src/lib/connectors.ts files declare their configs with satisfies ConnectorConfigs<…>; update files generated by 1.36. Client setup
  • Connector names are case-insensitive: client.connectors.<name> throws AMBIGUOUS_CONNECTOR when two keys differ only by case, and connector invoke --json lists the candidates. Client setup
  • rayfin connector add --auth sets the identity at add time, connector remove keeps the connector's files, and a connector that points at the app's own database is rejected. Adding a connector
  • Function-bridge calls wait up to five minutes, with a per-call timeoutMs. Semantic models
  • Direct semantic-model rayfin connector invoke calls need Read and Build permissions on the model instead of write access to the workspace. Semantic models
  • SQL connector read results are typed by the fields you select, and SQL Database write results type their columns as optional. SQL sources
  • Connector @role() include and exclude lists are emitted as backing column names, so fields mapped with column: match. Entity generation

Observability

  • rayfin telemetry enable, disable, and query and services.telemetry give a deployed app its own Application Insights resource. Experimental Observability
  • initTelemetry() from @microsoft/rayfin-telemetry/browser sends browser telemetry to that resource, with pinned OpenTelemetry peer dependencies. @microsoft/rayfin-telemetry
  • Rayfin CLI usage telemetry — separate from app Observability — labels runs from coding agents such as GitHub Copilot CLI, and npm create @microsoft/rayfin records how long each scaffold step took. Telemetry

CLI and deployment

  • rayfin up skips the static upload when nothing changed since the last successful deploy; --force-static-deploy uploads anyway. Skip unchanged static content
  • rayfin up checks connector additionalPayload, custom audiences, and the dynamic claims contract before any remote call, and sends the claims contract after Functions deploy. What rayfin up does
  • rayfin init --services accepts storage, which requires data. rayfin init
  • rayfin init on an existing project moves its dev script to dev:frontend and points dev at rayfin dev. Existing dev script, Switch an existing project to rayfin dev
  • rayfin dev applies Storage declarations to its Fabric backend, and the Vite adapter proxies the backend's /.well-known routes so client.auth.getClaims() can validate tokens during development. Route SDK calls through the Vite adapter
  • rayfin dev warns when host.json allows a Preview extension bundle older than 4.49.0. Extension bundle warning
  • rayfin up db apply adds --drift-file, --overwrite, and --skip-drift-check. up db apply
  • rayfin init --list-templates -t <git-url> lists the templates in a git source. List templates
  • rayfin init ai-files adds the rayfin-auth-claims and rayfin-schema-drift skills and installs the Storage skill by default. Managed items in 2.0.0
  • rayfin docs serves the guides installed with the CLI when the project has no @microsoft/rayfin-guide package. Guide fallback
  • Templates create the client with RayfinClient.create, declare the 2.0 adapter packages, and enable Stage 3 decorators for the SWC plugin. Build a todo app, Templates
  • The Universal App requires Node.js 22.13 or later, follows the system light or dark theme, and adds a storage capability pack. Universal App workspace

Upgrade to 1.36

Upgrade every Rayfin package together, then work through the changes that apply to your project. Steps 3 through 6 apply only if you use that feature.

  1. Update the packages. Set every @microsoft/rayfin-* dependency — plus @microsoft/fabric-user-data-functions and @microsoft/rayfin-local-dev if you use them — to 1.36.2 in each package.json, including the functions package's own package.json, then run npm install.
  2. Fix moved imports. Import entity and the field decorators from @microsoft/rayfin-core, not @microsoft/rayfin-core/experimental (only blob and the storage helpers remain there). Import Source and AutoGenerated from @microsoft/rayfin-connectors, and ConnectorsRayfinClient from @microsoft/rayfin-client. See Deprecations.
  3. Functions. Add services.functions.auth.type: application to rayfin.yml. Function connections now run as the app identity, so grant it access to every resource your functions call. Replace ctx.getToken(...) with ctx.Tokens.<Audience> and ctx.getSecret(...) with ctx.Secrets.<NAME>. Remove audiences that no longer exist (CosmosDB, KeyVault, EventGrid, Kusto, WorkIQ). Set extensionBundle.version in the functions package's host.json to [4.49.0, 5.0.0) — existing projects are not migrated automatically. See Run functions locally.
  4. Connectors. Remove RAYFIN_FEATURE_FLAGS=connectors and services.connectors.enabled. Existing entries keep the auth.type in rayfin.yml, but rayfin connector add now writes application for SQL connectors — set delegated again after re-adding if users should see only their own data. See Connectors.
  5. Feature flags. Remove functions and connectors from RAYFIN_FEATURE_FLAGS; only experimental storage still uses the variable.
  6. Storage (experimental). Remove per-call options and exports that 1.36 dropped. See Storage.
  7. Verify. Run npx rayfin up --dry-run, then npx rayfin up and npx rayfin up status.
PromptUpgrade my Rayfin project to 1.36.2
Upgrade my Rayfin project to Rayfin 1.36.2. Read https://rayfin.ai/docs/reference/changelog.md first. 1. Set every @microsoft/rayfin-* dependency, plus @microsoft/fabric-user-data-functions and @microsoft/rayfin-local-dev where present, to exactly 1.36.2 in every package.json (including rayfin/functions/package.json or the path in services.functions.path), then run npm install. 2. Move imports: decorators from @microsoft/rayfin-core instead of @microsoft/rayfin-core/experimental (except blob), Source and AutoGenerated from @microsoft/rayfin-connectors, ConnectorsRayfinClient from @microsoft/rayfin-client. 3. If services.functions.enabled is true: add services.functions.auth.type: application, replace ctx.getToken(AudienceType.X) with ctx.Tokens.X (declaring the audience on RayfinContext) and ctx.getSecret('N') with ctx.Secrets.N, remove CosmosDB, KeyVault, EventGrid, Kusto and WorkIQ audiences, and set extensionBundle.version in the functions host.json to [4.49.0, 5.0.0). List which resources the app identity now needs access to. 4. Remove functions and connectors from RAYFIN_FEATURE_FLAGS and remove services.connectors.enabled from rayfin.yml. 5. Run npx rayfin up --dry-run and report the result before deploying.

Rayfin 1.36

Released 2026-09-29. The headline changes:

  • Functions are generally available. No feature flag, application authentication required, typed ctx.Secrets and ctx.Tokens.
  • Connectors are generally available. No feature flag; SQL connectors default to the app identity; new Kusto connectors are held back.
  • Two new Entra sign-in paths. Direct Entra token sign-in and an external embed host.
  • New default template. blankapp now scaffolds the Universal App.
  • Capacity readiness on first deploy, plus --item-name and --capacity-id.

Rayfin 1.36.2

Released 2026-10-02.

  • Functions — new functions scaffolds pin the local Azure Functions extension bundle to [4.49.0, 5.0.0). That bundle fixes local Functions sign-in on macOS with .NET 10 and on Windows when an agent starts Core Tools without a console window. Existing projects must update host.json themselves; deployments are unaffected. Run functions locally

Rayfin 1.36.1

Released 2026-09-29.

  • Functions — the local extension bundle floor rose to [4.45.0, 5.0.0) for the binding support 1.36 connections need (superseded by 1.36.2). Run functions locally
  • Functions — rayfin dev condenses Functions host restarts to a single Functions host restarted. line, and keeps an existing Functions: Attach launch configuration on the inspector's current port. Run functions locally
  • Connectors — semantic model results with Variant columns (most measures) decode correctly instead of failing with Cannot read properties of undefined (reading '0'). Semantic models

Rayfin 1.36.0

Released 2026-09-29.

Functions

  • Functions are generally available: the functions feature flag is gone, and the rayfin functions, rayfin dev functions apply, and rayfin up functions deploy commands are always visible. Functions are not available in every Fabric region or tenant. Functions
  • Enabled Functions must declare services.functions.auth.type: application; rayfin init and rayfin functions init scaffold it. Configuration
  • Function connections run as the app identity — the owner of the Fabric app item — not as the signed-in user. Rayfin data access through ctx.getDataClient() stays caller-scoped. Delegated and application access
  • Typed ctx.Tokens.<Audience> replaces ctx.getToken(), and typed ctx.Secrets.<NAME> replaces ctx.getSecret(). Connections, Secrets in functions
  • AudienceType has five members: Sql, Storage, Fabric, AzureAI, ADO. CosmosDB, KeyVault, EventGrid, Kusto, and WorkIQ were removed. Connections
  • rayfin functions init --path saves a custom functions package location, and rayfin up --exclude-services functions skips the Functions deploy phase. rayfin functions
  • Functions are bundled with esbuild, so dependencies hoisted into an npm workspace ship with the deployment. Deploying functions

Secrets

  • rayfin secret is always visible, and rayfin secret set --describe records each secret's description in rayfin.yml, which drives the generated secrets.generated.ts types. Secrets, rayfin secret

Connectors

  • Connectors are generally available: the connectors feature flag is gone, rayfin connector is always registered, and services.connectors.enabled is a no-op. rayfin up connector apply remains Preview. Connectors
  • rayfin connector add writes auth.type: application for fabric-sqlanalytics, fabric-warehouse, and fabric-sqldatabase, and lowercases connector names. Connector authentication
  • New Kusto (Eventhouse) connectors cannot be added; existing ones keep working. 2.0 renamed the type to eventhouse. Eventhouse
  • Source and AutoGenerated moved to @microsoft/rayfin-connectors, and ConnectorsRayfinClient is exported from the stable @microsoft/rayfin-client entry. Client setup
  • rayfin connector invoke gains --transport, --output-file, and --max-inline-bytes (large results spill to a file). rayfin connector
  • rayfin connector add keeps src/lib/connectors.ts wired as connectors are added. Adding a connector

Auth

  • Direct Entra token sign-in: signInWithEntraToken() exchanges a delegated Entra token you already hold for a Rayfin session, in the browser or Node.js. Sign in with an Entra token
  • External embed host: @microsoft/rayfin-embed-host lets your own portal embed a Rayfin app and sign it in with the portal's Entra token. Embed in your own portal
  • Embedded startup first checks for an external embed host before the Fabric embedded flow. Fabric SSO

Development loop

  • Local automatic sign-in: when assetAccess is protected and externalEntraExchange is enabled, the Vite adapter signs the app in with your rayfin login session. Develop locally
  • rayfin dev --capacity-id assigns a capacity to a first-run workspace that has none. rayfin dev

Deploy and hosting

  • First deploys check workspace capacity and can assign an existing capacity or provision a trial, with consent. Deploying with rayfin up
  • rayfin up --item-name names the Fabric item; --capacity-id picks the capacity. rayfin up
  • rayfin up --dry-run validates local inputs and resolves the workspace without changing anything. rayfin up

Data and storage

  • The CLI rejects entity names that collide with GraphQL built-in types, such as Date, with an actionable message. Known limitations
  • The field decorators exported from @microsoft/rayfin-core accept column, which sets the SQL column name independently of the property name. In 1.35 it existed only on the experimental decorators. Field types
  • rayfin up db apply retries transient database failures. Migrations
  • Storage remained Experimental in 1.36; its client dropped unsupported per-call options and exports. It became generally available in 2.0. Storage

Templates, SDK, and agent files

  • blankapp, the default template, now scaffolds the Universal App — a React + Vite workspace that adds data, functions, connectors, and visuals as you ask for them. Templates
  • ApiClient accepts a custom fetch. @microsoft/rayfin-lib
  • rayfin init ai-files installs a storage skill when storage is enabled. rayfin init ai-files

Rayfin 1.35

Released 2026-09-09. If you are upgrading from 1.34, these are the changes to plan for.

Rayfin 1.35.1

Released 2026-09-17.

  • Static hosting access posture. services.staticHosting.assetAccess (protected or public) replaces anonymousAccess. New projects scaffold protected, and a non-interactive rayfin up writes protected when the value is missing. Hosting
  • Package versions on deploy. rayfin up records packageVersions and upgrades an installed @microsoft/rayfin-auth older than 1.35 before publishing a static app. Hosting

Rayfin 1.35.0

  • rayfin dev is the development loop: it provisions or reuses the backend in Fabric, applies the schema, and runs the frontend and Functions locally. Every template's npm run dev now runs it, with dev:frontend starting the frontend. When you migrate an existing project to "dev": "rayfin dev", add "dev:frontend": "vite". Develop locally
  • Aggregations — groupBy with sum, avg, min, max, and count in @microsoft/rayfin-data. Aggregations
  • Runtime config — resolveRayfinConfig() and a deployed rayfin.config.json let one built bundle move between environments. Deployment pipelines
  • Deep linking — @microsoft/rayfin-app-state-fabric makes app views shareable through the Fabric portal URL. Deep linking
  • rayfin up status reports the static app's hosting URL. Deploying with rayfin up
  • Anonymous data access — @anonymous() is exported from @microsoft/rayfin-core; a tenant administrator must allow anonymous access. Permissions
  • Function invocations default to a 250-second timeout, with a per-call timeoutMs. Calling functions
  • @blob() moved to @microsoft/rayfin-core/experimental, and rayfin init no longer offers storage. Storage
  • Telemetry — rayfin/.project.json, RAYFIN_TELEMETRY_ENV, and ~/.rayfin/dev-device-id. Telemetry
  • Functions, secrets, and connectors shipped behind feature flags in 1.35; they became generally available in 1.36.

Feature status

FeatureStatusNotes
Data, permissions, querying, aggregationsGenerally availableAnonymous permissions need the Fabric tenant setting Enable anonymous data access for Fabric Apps (Preview).
Fabric SSOGenerally availableThe popup flow works from any origin in allowedRedirectUris, including localhost.
Direct Entra token sign-inAvailable since 1.36Requires services.auth.fabric.externalEntraExchange: true and the exchange in your Fabric environment.
External embed hostAvailable since 1.36Requires externalEntraExchange: true on the embedded app.
Dynamic auth claimsGenerally available since 2.0The backend must have it enabled for the workspace's region.
FunctionsGenerally available since 1.36Not available in every Fabric region or tenant.
Raw SQL in functions (& WithSql)ExperimentalNew in 2.0. The service enables it per tenant; deployed functions only.
Connectors — SQL and semantic modelGenerally available since 1.36
Connectors — Fabric IQAvailable since 2.0Authoring is released; the backend adapter may not be enabled in every Fabric environment.
rayfin up connector applyPreview
Connectors — Eventhouse (formerly Kusto)Experimental, heldExisting connectors keep working once migrated to type: eventhouse; new ones cannot be added.
StorageGenerally available since 2.0Remote-only; no feature flag. Experimental in 1.35 and 1.36.
Observability (rayfin telemetry)ExperimentalNew in 2.0. Needs Fabric service-side enablement for the workspace.
Deep linkingRolling out per tenantCheck isSupported() before relying on it.
Something wrong on this page?Report an issueEdit this page

On this page