An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
Deployment is still failing with 403 because the issue is with authentication/authorization for the Rayfin CLI, not the tenant toggle itself.
A 401/403 on npx rayfin up is handled as follows:
- Reauthenticate Rayfin CLI
This refreshes the authentication session used by the CLI.npx rayfin login npx rayfin up - Verify minimum permissions on the Fabric app item Contributors who deploy a Fabric app must have at least Edit permission on the Fabric app item in the Fabric workspace. If only Viewer access is granted, deployments will fail.
- Confirm the Fabric app workload is enabled in the correct tenant/workspace
- A Fabric tenant admin must enable Fabric apps (preview) in the Fabric admin portal under Tenant settings → Fabric apps (preview).
- After enabling, ensure the setting scope (entire organization or specific security groups) actually includes the account being used for
npx rayfin login. - Use a workspace where contributor or admin permissions are granted.
- Retry deployment and check status
- Deploy:
npx rayfin up - Check deployment state:
npx rayfin up status - If needed, run a dry run to confirm what will be applied:
npx rayfin up --dry-run
- Deploy:
If 403 persists after npx rayfin login and confirming permissions, the next step is to validate with the Fabric admin that the Fabric apps workload is enabled for the exact user/group and workspace being used.
References: