microsoft / microsoft/rayfin

Rayfin up throws a 500 error when SQL databases are not supported in the Workspace

Open
#56 0 comments 0 reactions 1 assignee View on GitHub

@cpeth is already working on this.

Since Jul 29, 2026.

bug issue-mapped triaged
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
  1. Create a separate SQL database in your Fabric workspace
  2. If you get this error, Fabric Apps cannot make use of a SQL Database:
Image
  1. Generate a Rayfin app using a template that wants to roll out a SQL database
  2. 'up' the Rayfin app
  3. A generic 500 error occurs in your command prompt
Image
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.