Grab a spot →
Skip to main content

Authentication

Connect docs via MCP

This FAQ covers common questions about the authentication step when setting up or updating a Power BI connection in Atlan.

What does Test Authentication actually validate?

Test Authentication proves that Microsoft Entra ID issued a token (Layer 1 — credentials are valid). It does not prove the service principal can read your Power BI content. Whether the SP can access workspaces and metadata depends on Power BI tenant settings and workspace access (Layer 2), which the preflight checks validate. See The two permission layers.

Why does the client secret field always appear empty after saving?

Secrets are write-only by design — Atlan does not display stored secret values. An empty field does not mean the credential was lost.

If you suspect a secret update did not persist, check that your Atlan user has permission to update workflow credentials. An update attempted by an under-privileged user can silently fail, leaving the workflow running on the old secret while Test Authentication passes on the new one.