Input is malformed. Reason: Could not get entity details for [MANAGE IDENTITIES HERE]. If this entity is a linked service, please ensure it has been published before using in debug runs.

Dalila Di Lazzaro 10 Reputation points
2023-07-21T17:48:29.6266667+00:00

I'm having problems for a few days, I'm using Azure Synapse Analytcs, and I've also tried using Azure SQL. It's a SAS connection that uses Managed Identities, it says the service is unpublished. So we uploaded the linked service on the DEV - Staging - PROD trail, I updated my branch, but the error persists.

Can you help me?

I can preview normally, and perform the query in ingest, it just doesn't run, neither in Data Flow nor with Copy Data.

Azure SQL Database
Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,137 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,129 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Dalila Di Lazzaro 10 Reputation points
    2023-07-25T16:50:30.1266667+00:00

    Hello Oury! :)

    I'm trying to access files through managed identities. They are .xel files, accessed by a query ex:' SELECT * FROM table ('https://...', default, default)"

    I created a Data flow and a copy data to access the SAS database through a linked server Azure Synapse Analytcs, and Azure SQL Server.

    But when I press "Debug", it doesn't run and it already shows a direct error "Input is malformed. Reason: Could not get entity details for [MANAGE IDENTITIES]. If this entity is a linked service, please ensure it has been published before using in debug runs.", informing that our linked service was not published.

    I created a branch to be able to access it, and made the pull request, and opened the release to go up to production. And even the linked service in production, the error persists stating that it was not published.

    Could it be a microsoft error, or a linked service error?

    The Linked Service is accessing the SAS through a Key Vault, and there I can successfully test it, and give a data preview in the data set.


  2. Oury Ba-MSFT 15,116 Reputation points Microsoft Employee
    2023-08-04T23:13:56.2933333+00:00

    @Dalila Di Lazzaro Thank you for getting back and sorry for the delay in answering your question.

    Same question was asked here. https://learn.microsoft.com/en-us/answers/questions/792062/input-is-malformed-reason-could-not-get-entity-det

    User was able to get the issue fixed by saving the account in the key vault.

    Regards,

    Oury

    0 comments No comments