Rayfin up throws a 500 error when SQL databases are not supported in the Workspace
@cpeth is already working on this.
Since Jul 29, 2026.
- Dominant language
- No language data
- Stars
- 610
- Forks
- 62
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
What happened?
If a Fabric Apps template is used where a SQL Database should be deployed (or the settings are set in the rayfin config) while workspace-level private links are available, a 500 internal server error is thrown while deploying the app.
See the documentation
Tenant-level private links are available for SQL database, but currently, workspace-level private links are not available in SQL database.
Workaround: Try to use localStorage where data is kept on the server. This is kept outside EntraID so not great for sensitive data!
Steps to reproduce
- Create a separate SQL database in your Fabric workspace
- If you get this error, Fabric Apps cannot make use of a SQL Database:
- Generate a Rayfin app using a template that wants to roll out a SQL database
- 'up' the Rayfin app
- A generic 500 error occurs in your command prompt
Environment
- Generic issue
Logs or screenshots
See steps to reproduce.
The roll-out should be able to handle this situation, preventing the 500. Having SQL databases supporting these private endpoints would be great!
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.