Skip to content

docs: Add Fabric cloud integration content#2170

Open
devin-ai-integration[bot] wants to merge 2 commits intodocsfrom
devin/1774320697-fabric-cloud-docs
Open

docs: Add Fabric cloud integration content#2170
devin-ai-integration[bot] wants to merge 2 commits intodocsfrom
devin/1774320697-fabric-cloud-docs

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Mar 24, 2026

docs: Add Fabric cloud integration guide (replace Coming soon)

Summary

Replaces the "Coming soon" placeholder card on the Fabric cloud integration page with full onboarding documentation, following the same snippet pattern used by Snowflake, Postgres, Databricks, etc.

Changes:

  • docs/cloud/integrations/dwh/fabric.mdx — Replaced the <Card> "Coming soon" placeholder (which linked to a Tally interest form) with the standard snippet-based layout (<Fabric /> + <OnboardingHelp />).
  • docs/snippets/cloud/integrations/fabric.mdx (new) — Integration guide covering prerequisites, Azure AD service principal setup, connection form fields (server, port, tenant ID, client ID, client secret, database, schema), and IP allowlist.

Companion to elementary-internal#5392 which adds the actual Fabric support to Elementary Cloud.

Review & Testing Checklist for Human

  • Verify content accuracy against the actual UI form — Confirm the listed fields (Server, Port, Tenant ID, Client ID, Client Secret, Database, Schema) match what the Fabric environment form in elementary-internal actually collects. The database/schema fields are described as per-dbt-project — verify this matches the implementation.
  • Verify the Tally form removal is intentional — The old page linked to https://tally.so/r/3N6DlW?integration=Fabric for interest signups. This PR removes that link entirely, assuming Fabric cloud support is shipping. Confirm this is the desired timing.
  • Preview the rendered page — Run the docs locally or use a preview deployment to confirm the page renders correctly (snippet imports resolve, formatting looks right, IP allowlist snippet renders).

Notes

Co-Authored-By: Itamar Hartstein <haritamar@gmail.com>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@mintlify
Copy link

mintlify bot commented Mar 24, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
elementary 🟢 Ready View Preview Mar 24, 2026, 2:54 AM

@coderabbitai
Copy link

coderabbitai bot commented Mar 24, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8cf3c6af-1a4e-434c-9b4d-076ef55c5f1d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch devin/1774320697-fabric-cloud-docs

Comment @coderabbitai help to get the list of available commands and usage tips.

2. Give it a name (e.g. `elementary-fabric`) and register it.
3. Note the **Application (client) ID** and **Directory (tenant) ID**.
4. Go to **Certificates & secrets** > **New client secret**, create a secret, and copy the **Value**.
5. In your Fabric workspace, grant the service principal access (e.g. add it as a **Contributor** or **Member** in the workspace settings).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something we put emphasis on with other adapters is to ask for minimal permissions - in this case - we want read access only to the elementary schema + metadata access (e.g query history/information schema)

Can you adapt accordingly? If we can provide GRANT statements I think that's best.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! Updated in 1629b2f2:

  1. Changed workspace role from Contributor/MemberViewer (minimum needed for connectivity)
  2. Added a new "Grant minimal permissions" section with SQL GRANT statements:
    • GRANT SELECT ON SCHEMA for read-only access to the elementary schema
    • GRANT VIEW DEFINITION ON SCHEMA for metadata access (table definitions, columns)
  3. Imported and included the shared PermissionsAndSecurity snippet (same pattern as other adapters)

- Changed workspace role from Contributor/Member to Viewer (minimum needed)
- Added 'Grant minimal permissions' section with SQL GRANT statements
- Imported and included PermissionsAndSecurity snippet
- Follows the same minimal-permissions pattern as other adapters

Co-Authored-By: Itamar Hartstein <haritamar@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant