User Profile
danjo914
Frequent Visitor
Joined 7 years ago
User Widgets
Contributions
Re: ASAZURE to Fabric Warehouse SQL Endpoint
There are two authentications required, one the authentication to the ASAZURE, which yes, we are using the service principal already, but the second is the authentication to the data source located inside the .bim file. That does not seem to support managed identities nor service principals. We get "This authentication type is not supported". It appears that only OAUTH2 can be used inside the .bim to connect to the sql endpoint inside a Microsoft Fabric Workspace with a token expiry of a single day. It would be great if I am incorrect. Happy to hear of other ways to set up authentication to the datasource.Re: ASAZURE to Fabric Warehouse SQL Endpoint
Hi Xiaoxin, Thank you for your response. My question is specifically about the best authentication method to use when connecting to the SQL endpoint from ASAzure. From my testing, it appears that both Service Principal and Managed Instance authentication methods are not supported, or at least that's the error I’m encountering. For context, we have scripts that successfully use Service Principal credentials to pull data via the SQL endpoint without any issues. This leads me to believe the problem lies with ASAzure, which seems to only accept OAuth2 authentication. Could you confirm if this is the case or suggest a better approach?ASAZURE to Fabric Warehouse SQL Endpoint
What we are trying to do is to set up an ASAZURE model to pull from a warehouse via sqlendpoint from a Microsoft Fabric Workspace. This works fine if I use my own Microsoft Credentials, however, the token only lasts a day. We want to automate this using Microsoft Azure Automation however, it doesn't seem to support Managed Instances or Service Principals and requires us to use a OAUTH2 username/password each time we want to process. Surely that is not intended, does anyone have a work around? I believe the issue the connection ot the Microsoft Fabric Warehouse requiring an OAUTH2 but then how would you go about automating it without embedding usernames and passwords?Re: SQL Analytics Endpoint - RLS for Security Groups
I had to use the Microsoft Graph API to populate a table with Security Groups and Members for applying RLS. Power Query couldn't save a dynamic source to a table, so I used Power Apps to create a table and then Power Query to pull that table into the Warehouse from Power Apps. It was a bit messy but gets the job done and runs quick. Unfortunately I've not seen anyway to implement Entra Security Groups directly.Re: Migrate workspaces to a different region with fabric items removed
Not sure your answer is accurate. If it were true then why would this error message exist when changing the capacity in workspace settings Or the other route through the admin portal. I think you cannot actually migrate fabric workspaces across regions at this stage. Hopefully soon. If anyone knows a workaround other than manually recreating that would be extremely beneficial.Re: SQL Managed Instance - Dataflow Refresh Issue
Thank you for your response. We believe that the issue was caused by the On-Premises Gateway redirecting to the on-premises database, rather than to the Azure SQL MI as specified in the data source , as the tables and datbase name are the same it was rather misleading. When we removed the Gateway from the Power Query, the connection failed. As we intend to move away from the On-Premises Gateway, we'll need to reassess our networking rules.SQL Managed Instance - Dataflow Refresh Issue
We recently transitioned our dataflows to connect to a SQL Managed Instance, moving away from our on-premise gateway setup. While setting up Power Query, I was able to successfully view the data from the new SQL Managed Instance. However, an issue arises when I attempt to refresh the dataflow. Power BI Setting up Dataflow, Power Query shows data but upon refresh receive the following error "Error: Data Source Error : DataSource.Error: Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider error: 0 - An attempt was made to access a socket in a way forbidden by its access permissions.) I find it interesting that our configuration allows Power Query to establish a successful connection with the data source, yet encounters an issue during the refresh process. I am at a loss for what might be causing this. I would appreciate any insights or suggestions on potential problem areas we could investigate, or any steps we could take to diagnose and resolve this issue. Thank you in advance for your assistance.
