You need to implement a table projection to generate a physical expression of an Azure...

For a table projection in a knowledge store (skillset definition), the table node must define:

tableName : the table to project into (physical expression).

generatedKeyName : the name of the system-generated key column.

source : an object-shaping expression (projection path) describing what document content flows into the table.

dataSource/dataSourceConnection are service-level objects used by the indexer, not properties of a table projection node.

References

Knowledge store and projections schema: table projections require tableName, generatedKeyName, and source in the skillset JSON.