What happened?
I tried several options to get a connection stirng that would connect me to a Warehouse SQL Fabric endpoint from a container running in a Container Application Environment
I tried using a service principal:
"Server=<<ID>>.fabric.microsoft.com;Initial Catalog=DWH;Authentication=Active Directory Service Principal;Persist Security Info=False;User ID=<<client>>@<<tenant>>;Password=<<secret>>",
(with or without the @ tenantId section
I tried a user assigned managed identity:
Server=<<ID>>.datawarehouse.fabric.microsoft.com;Initial Catalog=DWH;Authentication=ActiveDirectoryIntegrated;Trusted_Connection=NO
The container id evidently running with this identiry, and the identiry has access to the SQL Endpoint and the Workspace in Fabric
The interesting part is that it works just fine from my local PC if I clone the repo, and run it from Visual Studio, using the Service Principal approach.
I'm fresh out of ideas here ... so any suggestions?
Greets
Kobe
Version
1.2.9-rc
What database are you using?
Azure SQL
What hosting model are you using?
Container Apps
Which API approach are you accessing DAB through?
REST
Relevant log output
Azure.DataApiBuilder.Service.Startup[0]
Unable to complete runtime initialization. Refer to exception for error details.
Azure.DataApiBuilder.Service.Exceptions.DataApiBuilderException: Cannot obtain Schema for entity ports with underlying database object source: gold_ops.ops_dim_port due to: 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: 26 - Error Locating Server/Instance Specified)
at Azure.DataApiBuilder.Core.Services.SqlMetadataProvider`3.HandleOrRecordException(Exception e) in /_/src/Core/Services/MetadataProviders/SqlMetadataProvider.cs:line 100
at Azure.DataApiBuilder.Core.Services.SqlMetadataProvider`3.PopulateObjectDefinitionForEntity(String entityName, Entity entity) in /_/src/Core/Services/MetadataProviders/SqlMetadataProvider.cs:line 1116
at Azure.DataApiBuilder.Core.Services.SqlMetadataProvider`3.PopulateObjectDefinitionForEntities() in /_/src/Core/Services/MetadataProviders/SqlMetadataProvider.cs:line 1054
at Azure.DataApiBuilder.Core.Services.SqlMetadataProvider`3.InitializeAsync() in /_/src/Core/Services/MetadataProviders/SqlMetadataProvider.cs:line 289
at Azure.DataApiBuilder.Core.Services.MetadataProviders.MetadataProviderFactory.InitializeAsync() in /_/src/Core/Services/MetadataProviders/MetadataProviderFactory.cs:line 65
at Azure.DataApiBuilder.Service.Startup.PerformOnConfigChangeAsync(IApplicationBuilder app) in /_/src/Service/Startup.cs:line 625
Code of Conduct
What happened?
I tried several options to get a connection stirng that would connect me to a Warehouse SQL Fabric endpoint from a container running in a Container Application Environment
I tried using a service principal:
"Server=<<ID>>.fabric.microsoft.com;Initial Catalog=DWH;Authentication=Active Directory Service Principal;Persist Security Info=False;User ID=<<client>>@<<tenant>>;Password=<<secret>>",(with or without the @ tenantId section
I tried a user assigned managed identity:
Server=<<ID>>.datawarehouse.fabric.microsoft.com;Initial Catalog=DWH;Authentication=ActiveDirectoryIntegrated;Trusted_Connection=NOThe container id evidently running with this identiry, and the identiry has access to the SQL Endpoint and the Workspace in Fabric
The interesting part is that it works just fine from my local PC if I clone the repo, and run it from Visual Studio, using the Service Principal approach.
I'm fresh out of ideas here ... so any suggestions?
Greets
Kobe
Version
1.2.9-rc
What database are you using?
Azure SQL
What hosting model are you using?
Container Apps
Which API approach are you accessing DAB through?
REST
Relevant log output
Code of Conduct