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.
| Tag | Meaning |
|---|---|
| New in 2.0 | Did not exist before that release. |
| Changed in 2.0 | Existed, but its behavior, default, or name changed in that release. |
| Deprecated in 2.0 | Still works, but has a replacement. |
| Removed in 2.0 | No longer works from that release. |
| Preview | Shipped, but its shape may still change. |
| Experimental | Behind 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 --versionOn 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.
- Update the packages. Set every
@microsoft/rayfin-*dependency — plus@microsoft/fabric-user-data-functionsand@microsoft/rayfin-local-dev— to2.0.0in eachpackage.json, including the functions package's own. The 2.0 client depends only on@microsoft/rayfin-lib, so add@microsoft/rayfin-authand@microsoft/rayfin-data— and@microsoft/rayfin-functions,@microsoft/rayfin-connectors, or@microsoft/rayfin-storageif you use them — to the package that builds the client. Replace@microsoft/rayfin-connector-kustowith@microsoft/rayfin-connector-eventhouse. Then runnpm install. - Check TypeScript. The package that holds your schema needs TypeScript
^5.7.2or^6.0.2. If schema compilation reports a schema file outside a"type": "module"scope, createrayfin/package.jsoncontaining{"type": "module"}, or set"type": "module"in the app'spackage.json, as the message suggests. - Rebuild the client. Replace
new RayfinClient(...),ConnectorsRayfinClient,ExtendableRayfinClient, andRayfinServerClientwithRayfinClient.create. PassbrowserSession()— orsuppliedToken()in Node.js — asauth, and registerdataService(),functionsService(),connectorsService(), andstorageService()as needed. MoveauthStorageand the other session options intobrowserSession(), replaceuseProxywithbaseUrl: '', and derive the client type withReturnType<typeof createClient>. See Migrate from 1.x. - Fix imports. Import storage declarations and claims types from
@microsoft/rayfin-coreinstead 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 anydist/path. See Deprecations. - Fix data queries. Run the type-check: results now contain only the fields you
select. Add
.select([...])wherever code reads fields fromfindById,findMany, orfindFirst, and add the[]marker to to-many relationship paths ('notes[].title'). The client no longer turns date- and boolean-looking strings intoDateobjects and booleans for you, so convert selected dates and booleans explicitly. See Querying. - Functions. Install
@microsoft/fabric-user-data-functions@2.0.0in the functions project; the CLI refuses to generate types or deploy with an older worker. Keep the localhost.jsonextension bundle at[4.49.0, 5.0.0). See Run functions locally. - Storage. Remove
storagefromRAYFIN_FEATURE_FLAGS, registerstorageService()on the client, and replaceprefixoptions with full object paths. See Storage. - Connectors. Register connectors with
connectorsService(). Changetype: kustototype: eventhousewithauth.type: application, and move its queries intoadditionalPayload— see Eventhouse. Node.js scripts that relied on the CLI connector middleware must passhost: { type: 'cli' }. - 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. - Verify. Run the type-check, tests, and production build — including the functions
project — then
npx rayfin up --dry-run,npx rayfin up, andnpx rayfin up status.
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 initto add it to an app. - Dynamic auth claims mint app-defined claims into tokens from a
udf.authClaimsfunction. - 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.idfor 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 })replacesnew RayfinClient(),ConnectorsRayfinClient,ExtendableRayfinClient,RayfinServerClient, and the default export. Authentication is an explicit adapter —browserSession()orsuppliedToken()— andclient.data,client.functions,client.connectors, andclient.storageexist only when you register their adapters.@microsoft/rayfin-client@microsoft/rayfin-clientdepends 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 usesclient.dispose()releases a client's resources; construction failures useClientCompositionErrorcodes;AuthErroris one class shared by every package. Client errors- Every package declares an
exportsmap.@microsoft/rayfin-core/experimental,@microsoft/rayfin-core/decorators,@microsoft/rayfin-client/experimental, and deepdist/imports no longer resolve. Package entry points NetworkErrorcarriesserverErrorCode,retryAfterSeconds, andconsentUrl, and access-token callbacks can be asynchronous.@microsoft/rayfin-libRayfinRuntimeConfigaddsapplicationInsightsConnectionString.@microsoft/rayfin-client
Data
- Result types follow the selection. Queries without
.select()— includingfindById,findMany, andfindFirst— 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 | stringand booleansboolean | '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,
deletereturns the key only, and a relationship can be set with its object or its foreign key. Mutations dataService<AppSchema>()registersclient.data;EntitySchemaandTypedDataClientscome from@microsoft/rayfin-data. Data- Schema compilation supports TypeScript 6 and requires
^5.7.2 || ^6.0.2. Modeling entities rayfin initwrites NodeNext schema settings withESNext.Decoratorsand Node types, adds@types/node, and addsrayfin/package.jsonto apps that are not ES modules, which makesrayfin/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-coreroot, and the/experimental,/decorators,/analysis, and/schemaentry 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-swccompiles entity classes once Stage 3 decorators are enabled, and the templates enable them. Form validation
Auth
browserSession()from@microsoft/rayfin-authprovidesclient.auth; the 1.x top-level client optionsauthStorage,persistSession,autoRefreshToken, andmultiTabSyncmove into it, and apps install@microsoft/rayfin-auththemselves. Sessions- Dynamic auth claims: declare
services.auth.dynamicClaims, write oneudf.authClaimsprovider, filter on the claims in policies, and read them withclient.auth.getClaims()andctx.getClaims(). Dynamic auth claims isAuthenticatedisfalsewhile 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. Sessionsclient.dispose()releases auth timers and listeners without signing out; new and queued refreshes then reject withAUTH_DESTROYED. Sessions- Fabric sign-in rejects with
FABRIC_AUTH_POPUP_CLOSEDabout 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 asctid, skips home-tenant discovery. Fabric SSO- Fabric embedded hints take precedence over external embed host discovery. Embed in your own portal
signInWithEntraToken()reportsSIGN_IN_DENIEDandAUTH_CLAIMS_*codes, and takes a browser-session client'sauthor a standaloneAuth. Sign in with an Entra tokenrayfin loginchecks 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--jsonoutput stays one object.rayfin login
Functions
- Register
functionsService<AppFunctionsSchema>()from@microsoft/rayfin-functions, install that package directly, and importFunctionsSchemafrom 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 thenpm installcommand that fixes it. Functions ctx.user.idexposes the caller's subject ID for owner stamping. Writing functions- Custom audiences: declare an application ID or an
https://orapi://resource URI and read its token fromctx.Tokens;rayfin uprejects an invalid audience before it deploys. Connections - Raw SQL against the app database with
RayfinContext & WithSqlandctx.sql. Experimental Raw SQL - The Vite adapter forwards function calls to the deployed backend when no local Functions host is configured. Calling functions
rayfin devwarns whenhost.jsonallows an old Preview extension bundle, and when the local Functions host cannot sign in without a terminal window,rayfin devprints thehost.jsonfix instead of a generic hint. Run functions locallyrayfin secret set --env-filerecords every name inrayfin.ymland regenerates the secret types, and deployed functions can cache a secret value for a few minutes after you rotate it. Secretsrayfin up functions deployexplains a 404, and a project whose only function isudf.authClaimsdeploys. 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 initsets Storage up in local project files without deploying.rayfin storagerayfin up storage applyandrayfin dev storage applyare always available, and a Fabric-backedrayfin devapplies folder declarations to the remote backend. Apply Storage configuration- Folder declarations import from
@microsoft/rayfin-core; the@microsoft/rayfin-core/experimentalpath is removed. Migrate from 1.36 Storage storageService()registers Storage onRayfinClient.create;createStorageClientstays public.@microsoft/rayfin-storage- Operations take complete object paths, the
prefixoption is removed, and invalid paths throwInvalidName. 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
kustoaccepted only delegated, and runs only queries saved inadditionalPayload, called byqueryId. 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 inadditionalPayload connectorsService()from@microsoft/rayfin-connectors, which apps now install directly, replacesConnectorsRayfinClient. 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.tsfiles declare their configs withsatisfies ConnectorConfigs<…>; update files generated by 1.36. Client setup - Connector names are case-insensitive:
client.connectors.<name>throwsAMBIGUOUS_CONNECTORwhen two keys differ only by case, andconnector invoke --jsonlists thecandidates. Client setup rayfin connector add --authsets the identity at add time,connector removekeeps 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 invokecalls 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()includeandexcludelists are emitted as backing column names, so fields mapped withcolumn:match. Entity generation
Observability
rayfin telemetry enable,disable, andqueryandservices.telemetrygive a deployed app its own Application Insights resource. Experimental ObservabilityinitTelemetry()from@microsoft/rayfin-telemetry/browsersends 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/rayfinrecords how long each scaffold step took. Telemetry
CLI and deployment
rayfin upskips the static upload when nothing changed since the last successful deploy;--force-static-deployuploads anyway. Skip unchanged static contentrayfin upchecks connectoradditionalPayload, custom audiences, and the dynamic claims contract before any remote call, and sends the claims contract after Functions deploy. Whatrayfin updoesrayfin init --servicesacceptsstorage, which requiresdata.rayfin initrayfin initon an existing project moves itsdevscript todev:frontendand pointsdevatrayfin dev. Existingdevscript, Switch an existing project torayfin devrayfin devapplies Storage declarations to its Fabric backend, and the Vite adapter proxies the backend's/.well-knownroutes soclient.auth.getClaims()can validate tokens during development. Route SDK calls through the Vite adapterrayfin devwarns whenhost.jsonallows a Preview extension bundle older than 4.49.0. Extension bundle warningrayfin up db applyadds--drift-file,--overwrite, and--skip-drift-check.up db applyrayfin init --list-templates -t <git-url>lists the templates in a git source. List templatesrayfin init ai-filesadds therayfin-auth-claimsandrayfin-schema-driftskills and installs the Storage skill by default. Managed items in 2.0.0rayfin docsserves the guides installed with the CLI when the project has no@microsoft/rayfin-guidepackage. 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
storagecapability 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.
- Update the packages. Set every
@microsoft/rayfin-*dependency — plus@microsoft/fabric-user-data-functionsand@microsoft/rayfin-local-devif you use them — to1.36.2in eachpackage.json, including the functions package's ownpackage.json, then runnpm install. - Fix moved imports. Import
entityand the field decorators from@microsoft/rayfin-core, not@microsoft/rayfin-core/experimental(onlybloband the storage helpers remain there). ImportSourceandAutoGeneratedfrom@microsoft/rayfin-connectors, andConnectorsRayfinClientfrom@microsoft/rayfin-client. See Deprecations. - Functions. Add
services.functions.auth.type: applicationtorayfin.yml. Function connections now run as the app identity, so grant it access to every resource your functions call. Replacectx.getToken(...)withctx.Tokens.<Audience>andctx.getSecret(...)withctx.Secrets.<NAME>. Remove audiences that no longer exist (CosmosDB,KeyVault,EventGrid,Kusto,WorkIQ). SetextensionBundle.versionin the functions package'shost.jsonto[4.49.0, 5.0.0)— existing projects are not migrated automatically. See Run functions locally. - Connectors. Remove
RAYFIN_FEATURE_FLAGS=connectorsandservices.connectors.enabled. Existing entries keep theauth.typeinrayfin.yml, butrayfin connector addnow writesapplicationfor SQL connectors — setdelegatedagain after re-adding if users should see only their own data. See Connectors. - Feature flags. Remove
functionsandconnectorsfromRAYFIN_FEATURE_FLAGS; only experimental storage still uses the variable. - Storage (experimental). Remove per-call options and exports that 1.36 dropped. See Storage.
- Verify. Run
npx rayfin up --dry-run, thennpx rayfin upandnpx rayfin up status.
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.Secretsandctx.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.
blankappnow scaffolds the Universal App. - Capacity readiness on first deploy, plus
--item-nameand--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 updatehost.jsonthemselves; 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 devcondenses Functions host restarts to a singleFunctions 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
functionsfeature flag is gone, and therayfin functions,rayfin dev functions apply, andrayfin up functions deploycommands are always visible. Functions are not available in every Fabric region or tenant. Functions - Enabled Functions must declare
services.functions.auth.type: application;rayfin initandrayfin functions initscaffold 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>replacesctx.getToken(), and typedctx.Secrets.<NAME>replacesctx.getSecret(). Connections, Secrets in functions AudienceTypehas five members:Sql,Storage,Fabric,AzureAI,ADO.CosmosDB,KeyVault,EventGrid,Kusto, andWorkIQwere removed. Connectionsrayfin functions init --pathsaves a custom functions package location, andrayfin up --exclude-services functionsskips 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 secretis always visible, andrayfin secret set --describerecords each secret's description inrayfin.yml, which drives the generatedsecrets.generated.tstypes. Secrets,rayfin secret
Connectors
- Connectors are generally available: the
connectorsfeature flag is gone,rayfin connectoris always registered, andservices.connectors.enabledis a no-op.rayfin up connector applyremains Preview. Connectors rayfin connector addwritesauth.type: applicationforfabric-sqlanalytics,fabric-warehouse, andfabric-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 SourceandAutoGeneratedmoved to@microsoft/rayfin-connectors, andConnectorsRayfinClientis exported from the stable@microsoft/rayfin-cliententry. Client setuprayfin connector invokegains--transport,--output-file, and--max-inline-bytes(large results spill to a file).rayfin connectorrayfin connector addkeepssrc/lib/connectors.tswired 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-hostlets 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
assetAccessisprotectedandexternalEntraExchangeis enabled, the Vite adapter signs the app in with yourrayfin loginsession. Develop locally rayfin dev --capacity-idassigns 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-namenames the Fabric item;--capacity-idpicks the capacity.rayfin uprayfin up --dry-runvalidates 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-coreacceptcolumn, 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 applyretries 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. TemplatesApiClientaccepts a customfetch.@microsoft/rayfin-librayfin init ai-filesinstalls 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(protectedorpublic) replacesanonymousAccess. New projects scaffoldprotected, and a non-interactiverayfin upwritesprotectedwhen the value is missing. Hosting - Package versions on deploy.
rayfin uprecordspackageVersionsand upgrades an installed@microsoft/rayfin-autholder than 1.35 before publishing a static app. Hosting
Rayfin 1.35.0
rayfin devis the development loop: it provisions or reuses the backend in Fabric, applies the schema, and runs the frontend and Functions locally. Every template'snpm run devnow runs it, withdev:frontendstarting the frontend. When you migrate an existing project to"dev": "rayfin dev", add"dev:frontend": "vite". Develop locally- Aggregations —
groupBywithsum,avg,min,max, andcountin@microsoft/rayfin-data. Aggregations - Runtime config —
resolveRayfinConfig()and a deployedrayfin.config.jsonlet one built bundle move between environments. Deployment pipelines - Deep linking —
@microsoft/rayfin-app-state-fabricmakes app views shareable through the Fabric portal URL. Deep linking rayfin up statusreports 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, andrayfin initno 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
| Feature | Status | Notes |
|---|---|---|
| Data, permissions, querying, aggregations | Generally available | Anonymous permissions need the Fabric tenant setting Enable anonymous data access for Fabric Apps (Preview). |
| Fabric SSO | Generally available | The popup flow works from any origin in allowedRedirectUris, including localhost. |
| Direct Entra token sign-in | Available since 1.36 | Requires services.auth.fabric.externalEntraExchange: true and the exchange in your Fabric environment. |
| External embed host | Available since 1.36 | Requires externalEntraExchange: true on the embedded app. |
| Dynamic auth claims | Generally available since 2.0 | The backend must have it enabled for the workspace's region. |
| Functions | Generally available since 1.36 | Not available in every Fabric region or tenant. |
Raw SQL in functions (& WithSql) | Experimental | New in 2.0. The service enables it per tenant; deployed functions only. |
| Connectors — SQL and semantic model | Generally available since 1.36 | |
| Connectors — Fabric IQ | Available since 2.0 | Authoring is released; the backend adapter may not be enabled in every Fabric environment. |
rayfin up connector apply | Preview | |
| Connectors — Eventhouse (formerly Kusto) | Experimental, held | Existing connectors keep working once migrated to type: eventhouse; new ones cannot be added. |
| Storage | Generally available since 2.0 | Remote-only; no feature flag. Experimental in 1.35 and 1.36. |
Observability (rayfin telemetry) | Experimental | New in 2.0. Needs Fabric service-side enablement for the workspace. |
| Deep linking | Rolling out per tenant | Check isSupported() before relying on it. |
Reference overview
Landing page for the complete Rayfin reference — CLI commands, configuration schema, SDK packages, rules for coding agents, known limitations, deprecations, and troubleshooting.
CLI
Overview of the rayfin CLI — root options, the Fabric development workflow, and links to every visible command in Rayfin 2.0.0.