Forum Discussion
SSO Checkmark keeps turning itself off in Data Source Credentials
I have a dataset that uses tables in Snowflake. We use the Single Sign On setting to ensure proper authorisation within Snowflake.
However, I have one dataset where this checkmark keeps turning itself off. I turn it back on and log in, make sure I exit correctly, but then one or two days later this checkmark is turned off again. I am the only person accessing these settings.
What is going on?
Hi Mnie ,
Thanks for reaching out and sharing your issue with the SSO setting for your Snowflake dataset in Microsoft Fabric. It sounds like the SSO setting keeps reverting unexpectedly, and this could be happening for a few reasons
- A scheduled refresh or gateway configuration might be resetting the setting if the credentials aren’t aligned.
- There could be a mismatch in the SSO configuration between Fabric and Snowflake.
- It’s possible there a service side issue or bug in Fabric causing the setting to revert.
Consider the following checks
1. Sign in with your SSO credentials to confirm the setting is applied.
Configure credentials for data sources - Power BI | Microsoft Learn
2. If you're using an On premises Data Gateway, ensure SSO with Azure AD is enabled and the gateway is up to date.
If issues persist, re add the Snowflake data source with SSO and reconnect your dataset.Use a data gateway for cloud connections - Power BI | Microsoft Learn
3. Try disabling the scheduled refresh temporarily, then re enable SSO and monitor if the issue returns over the next couple of days.
Configure scheduled refresh - Power BI | Microsoft Learn
4. Since the SSO setting continues to revert automatically, it could be related to a service side issue in Microsoft Fabric. I recommend checking the Microsoft 365 Service Health Dashboard for any ongoing incidents impacting Power BI or data source settings.
Check service health - Microsoft 365 admin | Microsoft Learn
If my response solved your query, please mark it as the Accepted solution to help others find it easily. And if my answer was helpful, I'd really appreciate a 'Kudos'.
3 Replies
Go to Manage Gateways > Data Source Settings.
Ensure all datasets using this Snowflake source have the same SSO and OAuth2 settings.
Re-check the SSO box, sign in, wait 5+ minutes, and re-publish the dataset.
Hi Mnie ,
Thanks for reaching out and sharing your issue with the SSO setting for your Snowflake dataset in Microsoft Fabric. It sounds like the SSO setting keeps reverting unexpectedly, and this could be happening for a few reasons
- A scheduled refresh or gateway configuration might be resetting the setting if the credentials aren’t aligned.
- There could be a mismatch in the SSO configuration between Fabric and Snowflake.
- It’s possible there a service side issue or bug in Fabric causing the setting to revert.
Consider the following checks
1. Sign in with your SSO credentials to confirm the setting is applied.
Configure credentials for data sources - Power BI | Microsoft Learn
2. If you're using an On premises Data Gateway, ensure SSO with Azure AD is enabled and the gateway is up to date.
If issues persist, re add the Snowflake data source with SSO and reconnect your dataset.Use a data gateway for cloud connections - Power BI | Microsoft Learn
3. Try disabling the scheduled refresh temporarily, then re enable SSO and monitor if the issue returns over the next couple of days.
Configure scheduled refresh - Power BI | Microsoft Learn
4. Since the SSO setting continues to revert automatically, it could be related to a service side issue in Microsoft Fabric. I recommend checking the Microsoft 365 Service Health Dashboard for any ongoing incidents impacting Power BI or data source settings.
Check service health - Microsoft 365 admin | Microsoft Learn
If my response solved your query, please mark it as the Accepted solution to help others find it easily. And if my answer was helpful, I'd really appreciate a 'Kudos'.
Hi Mnie ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
