An Azure service for ingesting, preparing, and transforming data at scale.
Hi ,
Thanks for reaching out to Microsoft Q&A.
This is not an ADF issue; it is a cross-tenant Azure Data Explorer (Kusto) permission + token context problem.
Your SPN being multi-tenant and existing in both AME and CORP is not sufficient. ADF authenticates in the home tenant (AME) and gets a token for Kusto, but Kusto (in CORP) will only allow access if that exact service principal (object ID from CORP tenant) is granted permissions on the cluster/database.
What to check/fix (in order):
- In CORP tenant -> Kusto cluster -> Permissions (IAM / db permissions), explicitly add the spn (enterprise app in CORP) and assign at least Viewer/User role (or higher as needed).
- Ensure you are using the correct tenantID (CORP tenant) in the Linked Service, not AME.
Verify the SPN object ID used in Kusto is from CORP tenant, not the AME app registration object ID.
- If using database-level access, run:
.add database <db> users ('aadapp=<appId>')(or via portal permissions)
I know ADF can auth, but Kusto is denying authorization because the SPN is not granted access in the CORP tenant context. Once the SPN (enterprise app in CORP) is added to Kusto with proper role, the Linked Service will work.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.