How would I access Microsoft Azure Lakehouse tag structure through an OBDC Client connection using PTC Kepserver?

Question

How would I access Microsoft Azure Lakehouse tag structure through an OBDC Client connection using PTC Kepserver?

Mark Yeomans 0

Currently PTC Kepserver EX Version 7 connects to MS Azure Lakehouse SQL database and can access the correct tables.

Issue: Cannot autogenerate tags in Kepserver Version 7 to understand structure to access table row, column data.

Anonymous

2025-12-16T15:38:35.29+00:00
Hi Mark Yeomans,

Based on your feedback, I understand that basic SQL queries are executing successfully, which confirms connectivity to the Azure Lakehouse SQL database is fine. Since tags are not auto‑generating in Kepserver, I’d like to confirm a few Azure‑side details to rule out any permission or metadata exposure issues:

Authentication method: Are you connecting with Azure AD (Entra ID) authentication or SQL authentication?

Permissions: Does the identity being used have metadata read permissions (for example, VIEW DEFINITION) on the database and tables?

Schema visibility: If you run a query such as SELECT * FROM INFORMATION_SCHEMA.COLUMNS or INFORMATION_SCHEMA.TABLES from Azure Data Studio or SSMS, are you able to see the table and column definitions?

Driver/Connectivity: Which ODBC driver version is being used for the connection? Have you tested schema discovery from another SQL client to confirm metadata access?

Networking: Is the Lakehouse SQL endpoint behind private networking or firewall rules that could affect schema discovery differently than row‑level queries?

Could you please help clarify the above points so that we can better understand your scenario and guide you accordingly?

Thanks!

Kalyani
Anonymous

2025-12-17T08:54:55.1033333+00:00

Hi Mark Yeomans,

Just checking in could you please confirm the details requested in the comments section? This will help us better understand your scenario and provide the most appropriate solution for your issue.

2 answers

Your answer

Anonymous

2025-12-16T15:38:35.29+00:00

Hi Mark Yeomans,

Based on your feedback, I understand that basic SQL queries are executing successfully, which confirms connectivity to the Azure Lakehouse SQL database is fine. Since tags are not auto‑generating in Kepserver, I’d like to confirm a few Azure‑side details to rule out any permission or metadata exposure issues:

Authentication method: Are you connecting with Azure AD (Entra ID) authentication or SQL authentication?

Permissions: Does the identity being used have metadata read permissions (for example, VIEW DEFINITION) on the database and tables?

Schema visibility: If you run a query such as SELECT * FROM INFORMATION_SCHEMA.COLUMNS or INFORMATION_SCHEMA.TABLES from Azure Data Studio or SSMS, are you able to see the table and column definitions?

Driver/Connectivity: Which ODBC driver version is being used for the connection? Have you tested schema discovery from another SQL client to confirm metadata access?

Networking: Is the Lakehouse SQL endpoint behind private networking or firewall rules that could affect schema discovery differently than row‑level queries?

Could you please help clarify the above points so that we can better understand your scenario and guide you accordingly?

Thanks!

Kalyani
Anonymous

2025-12-17T08:54:55.1033333+00:00

Hi Mark Yeomans,

Just checking in could you please confirm the details requested in the comments section? This will help us better understand your scenario and provide the most appropriate solution for your issue.

Answer 1

Mark Yeomans 0

Kalyani,

Connection setup is correct and connected which allows proper authentication through the Entra ID case for Azure utilizing OBDC Version 18
Currently the Lakehouse definitions are not viewable [setup as]
Schema visibility is setup and will return the proper scheme from the lakehouse db running the query.
Firewall rules are a non issue as I can get to the database. If the Lakehouse definitions are not viewable from an OPC server via Kepserver then the autotag creation couldn't happen based on the restrictions correct?

Anonymous

2025-12-17T16:09:26.4466667+00:00

Hi Mark Yeomans,

thank you for the response.

Your Azure Lakehouse connection is working correctly, authentication, schema visibility, and firewall rules are all fine. The reason you cannot view Lakehouse definitions in Kepserver is due to how the OPC driver handles schema browsing. Since autotag creation requires the OPC server to expose those definitions, this limitation is on the Kepserver side. We recommend engaging with PTC Kepserver support for guidance, as Azure services are functioning as expected.

You can refer the following document and carefully read n\Note section and check from your side

https://support.ptc.com/help/kepware/drivers/en/index.html#page/kepware/drivers/Device_Properties_tag_generation.html

Thanks!
Mark Yeomans 0 Reputation points

2025-12-17T16:13:24.3633333+00:00

I believe in the Lakehouse configuration the definition creation is setup to non-viewable which is creating the issue correct? Azure is functioning correctly as setup for all intended purposes but if the database table definitions are not setup to view then PTC Kepserver cannot auto generate the tags.
Anonymous

2025-12-18T09:25:15.4466667+00:00
Hi Mark Yeomans,

Permissions:

Ensure that the identity you're using has the necessary permissions. Specifically, check for VIEW DEFINITION permissions on the database and tables.

Schema Visibility:

Run the following SQL query using Azure Data Studio or SQL Management Studio to see if you can access the schema information:
SELECT * FROM INFORMATION_SCHEMA.COLUMNS;

This should list down all columns in the available tables. If not visible, it indicates permission or configuration issues.

Additionally, could you verify if the account can successfully browse the table list using a tool like Azure Data Studio? This will help us determine if the issue is a permission restriction or a schema visibility setting in the Lakehouse configuration

Answer 2

Hey Mark Yeomans,

It sounds like you're having a bit of trouble automating the tag creation in PTC Kepserver to work with your Azure Lakehouse SQL database. The fact that you can connect and access the tables is great, but the auto-generating tags issue can be a bit tricky.

Here’s what you might consider trying:

Verify Connection Setup: Ensure that your ODBC connection to the Azure Lakehouse SQL database is properly configured. This includes checking any necessary drivers and the connection string parameters.
Review Unity Catalog Requirements: Since Lakehouse Federation requires the workspace to be enabled for Unity Catalog, make sure that your environment supports this. If not, you might consider using legacy query federation to continue your operations. Check the prerequisites for Lakehouse Federation here.
Enable Automatic Tag Discovery: Confirm that your Kepserver setup is configured to allow for automatic tag discovery from your database schema. You may need to refer to Kepserver documentation for specifics on enabling and configuring this feature.
Feedback from Service Diagnostics: Run service diagnostics in Databricks SQL to identify any possible underlying issues that might be affecting the operational capabilities. More information can be found in the Explore Databricks SQL integration with external data sources guide.
Testing Simple Queries: Try executing basic SQL queries through Kepserver to see if you can manually access the data you need. This can help isolate whether the issue is in the tag generation process or in accessing the data itself.

Hope this helps you get closer to resolving the issue! Let me know if you have any other questions or need further assistance.

Reference documents:

How-to: Integrate external data sources in Databricks SQL - Lakehouse Federation

Thanks!

Kalyani

Share via

How would I access Microsoft Azure Lakehouse tag structure through an OBDC Client connection using PTC Kepserver?

2 answers

Your answer