Computer Vision API - OCR to Json V1 and V3 action never returns valid results

Omokhoa Agbagbara 95 Reputation points
2025-07-13T11:00:27.82+00:00

I have been working with some OCR integrations and came upon the Computer Vision Api connector with the OCR to Json V1 and V3 actions.

However, the actions do not return any valid result.

output

With this input or any other input which I have tried.

11104-035-Cropped - 20

However, if a function app is used as a proxy to call the imageAnalysisClient. The results are different, and I have summarized the response below.

output-01

Is this a known bug which will be fixed or is there an extra parameter to be sent in the request.

Below is the setup for the action.

config

Best Regards

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
{count} votes

1 answer

Sort by: Most helpful
  1. Michael Madrid 0 Reputation points
    2025-07-25T12:05:52.36+00:00

    It really does seem like the issue lies in how the built-in OCR to JSON actions are implemented within Logic Apps. I’ve run into the same behavior — calling the Image Analysis API directly via an HTTP request works just fine and returns valid OCR results. But when using the official V1 or V3 OCR to JSON actions, the output is either empty or completely invalid.
    At this point, the more reliable workaround might be to bypass the built-in actions altogether and call the REST API directly using an HTTP action or route the request through an Azure Function as a proxy. It’s a bit more setup, but at least you get consistent results.
    Would definitely be helpful if Microsoft could confirm whether this is a known issue or if there’s something missing in how the actions are configured under the hood.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.