Remote functions deploy (`rayfin up functions deploy`) returns 404 "Endpoint not found", is remote functions hosting supported in the current preview?
@mksuni is already working on this.
Since Jun 11, 2026.
- Dominant language
- No language data
- Stars
- 610
- Forks
- 62
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
Summary
rayfin up functions deploy consistently fails with a 404 at the deploy endpoint. Before assuming a bug, I want to confirm whether remote functions deployment to a Fabric data app is actually supported in the current preview, or whether functions are local-host-only for now. The CLI labels the command [EXPERIMENTAL], which makes me suspect the latter.
Environment
@microsoft/rayfin-cli1.33.1- Deploying to a Fabric workspace on a Fabric Trial capacity (Australia East)
- WSL2 Ubuntu,
- Tenant has "Fabric Apps (preview)" enabled
What works
The rest of the deploy is fully successful:
- Rayfin item created, runtime settings applied (auth, data, storage)
- Database configuration generated and applied (13 entities, all tables created)
- Static content built and deployed, app is live and reachable
- Functions build, typecheck, and package correctly (
14 function(s), 11 files)
What fails
rayfin up functions deploy (and the functions step of rayfin up) fails after packaging:
🚀 Deploying functions...
⏳ Deploy endpoint not ready (404), retrying in 2s... (1/5)
... (retries 4s, 8s, 16s) ...
❌ Functions deploy failed (404): {"code":"InternalError", ... "Response Content = '{\"error\":\"Endpoint not found\"}'", "httpStatusCode":404 ...}
Target endpoint:
https://api.fabric.microsoft.com/v1/workspaces/<ws>/appBackends/<item>/__private/functions/deploy
What I've ruled out
- Not provisioning lag: identical 404 across attempts spanning ~1 hour.
- Not a packaging/build problem: packaging reports success (14 functions) before the deploy call.
- Not the missing runtime package:
@microsoft/fabric-user-data-functionsresolves from the bundled.tgzafterfunctions init --force; TypeScript compilation succeeds. - Not auth: the step authenticates successfully before the 404.
- The
__private/path segment and the[EXPERIMENTAL]label onrayfin up functionsboth suggest this endpoint may not be generally available yet.
Questions
- Is remote functions deployment to a Fabric data app supported in the current preview, or are functions intended to run only via the local host (
rayfin dev functions apply) for now? - If supported, is there a prerequisite I've missed, e.g. a tenant/capacity setting, or a capability that requires paid Fabric capacity rather than a trial?
- Is the
__private/functions/deployendpoint expected to exist on a freshly deployed item, and if so, is there a way to verify/trigger its provisioning?
Happy to provide full verbose logs or the RootActivityId values from the failures.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.