High severityconfiguration
Power BI Refresh Error:
SSO_INTEGRATION_NOT_FOUND
What does this error mean?
Snowflake cannot find the SAML security integration referenced during SSO login, usually because it was dropped, the integration name changed, or the user is connecting to the wrong account URL.
Common causes
- 1The SAML2 security integration was dropped or renamed in Snowflake
- 2The user is attempting SSO login through a Snowflake account URL that does not match the integration's configured account
- 3The identity provider was reconfigured and the issuer URL no longer matches the Snowflake integration
- 4The integration was created in a different Snowflake virtual warehouse environment
How to fix it
- 1Step 1: Run SHOW INTEGRATIONS in Snowflake to list all security integrations and confirm the SAML2 integration exists.
- 2Step 2: Check the integration details with DESC INTEGRATION <name> — verify the issuer, SSO URL, and certificate.
- 3Step 3: Confirm the user is logging in through the correct Snowflake account URL — SSO integrations are account-specific.
- 4Step 4: Recreate the SAML2 integration if it was dropped: CREATE OR REPLACE SECURITY INTEGRATION with the correct IdP metadata.
- 5Step 5: After recreating, update the IdP application with the new Snowflake assertion consumer service URL.