ADF - Support for Federated Identity Credentials

Short answer: ADF does not currently expose native workload identity federation for an App Registration in an Azure Data Explorer linked service. The current connector schema supports service principal authentication with a key, or system-/user-assigned managed identity; it has no issuer, subject, audience, or client-assertion fields needed for FIC.

I also cannot find a published Microsoft roadmap or timeline for this. The cleanest passwordless option today is to attach a user-assigned managed identity to the factory, create an ADF credential for it, and grant that identity the existing Kusto/database permissions. If retaining the current app registration is mandatory, the workaround is to place an Azure Function or Container Apps endpoint in front of the Kusto call and let that workload obtain the federated token, then invoke it from ADF—but that adds another component. I would open a support request or feature request for roadmap confirmation rather than design around an unpublished date.