Cloud Connection change from Personal Cloud Connection to Default (SSO)

[tday92]

This week I've seen many issues on semantic models that are using cloud connections. My old reports have a connection option that is Personal Cloud Connection and they continue to work fine. My new reports have this new Default Single Sign On connection and it breaks the report. What I've done is create a new Cloud connection and that has enabled my report to function fine. However, I have had to create multiple of the same Cloud Connection with different names for several new reports. Is it possible to just create one Cloud Connection and reuse it. I don't want to end up with hundreds of the same Cloud Connection just different names. Is anyone seeing this same issue? 

[Anonymous]

Hi @tday92 

What's the data source of the shared Cloud Connection? To my knowledge, it is indeed possible to create a single Cloud Connection and reuse it across multiple reports.

• If the existing Cloud Connection supports multiple authentication methods, you can go to its Settings page and switch to another authentication method with valid credentials.

• If a new report's data source wants to use an existing Cloud Connection, go to the semantic model's Settings page, map the data source to an exsiting Cloud Connection instead of creating a new one. 

Hope this would be helpful. 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

[tday92]

It is a Fabric Lakehouse SQL endpoint. When I created the first cloud connection I set it up with Oauth 2.0 and then tried using it again for another report but it was unavailble.

[Anonymous]

Hi @tday92 

Sorry for the late reply. May I know how you created a new report and how you tried using the cloud connection for another report? 

Below is what I have tested, which allows me to reuse the cloud connection. Hope this would be helpful:

1. Create the first report in Power BI Desktop. Connect to the SQL endpoint of a lakehouse, select necessary tables and choose Import mode. (I think DirectQuery mode should work too, but I haven't tested it yet.)
2. Publish the first report to Power BI Service. In the workspace, you will see a new report and a semantic model, both share the same name. 
3. Go to Settings page of the semantic model, expand Gateway and cloud connections, the data source now maps to Default: Single Sign-On. 
4. Click Create a connection to add this connection. I choose OAuth 2.0 too. 
5. After creating the connection, go back to the Settings page of the first semantic model, you should be able to map the data source to the new connection. 
6. Now open Power BI Desktop again, create a new report (the second report). Connect to the same SQL endpoint of the lakehouse. I choose Import too. Publish the report to Power BI Service. 
7.  You will see a new report and a new semantic model for the second report in the workspace. Go to Settings page of the second semantic model, now you should be able to map the data source to the cloud connection created in Step 4. 

Both reports are created in Power BI Desktop. After publishing them to Power BI Service, I have two semantic models. I can set up their cloud connections then. 

Is your process similar to mine?

Best Regards,
Jing