question

SanthoshPS-2435 avatar image
0 Votes"
SanthoshPS-2435 asked YutongTie-MSFT commented

Azure Form Recognizer Container Billing

We're using azure form recognizer API for trying out the service and now trying to use the container for on-premise analysis to meet data compliance. We're currently waiting for v2 public preview to try running the container on-premise. But going through the documentation of running v1 container I can see that we need cognitive-services-recognize-text container as well to run form recognizer against scanned pdf/images.

If we need computer vision as well as a resource (as per the doc) do we need to pay additional when using containers?

i.e both https://azure.microsoft.com/en-in/services/cognitive-services/computer-vision/#pricing and https://azure.microsoft.com/en-in/pricing/details/form-recognizer/ billing applicable when running container for form-recognizer?


azure-form-recognizer
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,

According to the document, the answer is yes. But there may be change since we have not seen any official document for container v2. I am going to check with the pm of container v2 and will let you know this soon.


Thanks,
Yutong

1 Vote 1 ·

Okay, looking forward for the update on this.

Am curious why do we have this computer vision charges when using container and not there in REST API? really hoping this won't be the case for v2.If this is the case for V2 as well the pricing page of form recogniser should have this information to avoid surprises.

0 Votes 0 ·

1 Answer

YutongTie-MSFT avatar image
0 Votes"
YutongTie-MSFT answered YutongTie-MSFT commented

@SanthoshPS-2435

Hi! Thanks for the patience. I just get confirmation from the pm about the container v2, there are several capabilities being made available in container form: custom model with labels, ID documents, invoices, business cards, and Layout.

There will not be any dependency on computer vision any more for custom model.

Two of the other capabilities – ID and business cards – will in fact ask customers to configure Computer Vision Read API as well, complete with billing endpoint and keys etc, at least for the preview, and charges reconciled in the backend to credit the customer for charges made by Read API in the process of calling ID or business cards.

To be more detailed:

• Layout API container: standalone container
• ID document container: depends on CV Read API container
• Business card container: depends on CV Read API container
• Invoice container: depends on Layout API container and NOT CV Read API container
• Custom model container: depends on Layout API container and NOT CV Read API container


Please looking forward to the new container of Form Recognizer.

Regards,
Yutong


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

One more update here, the plan will not be finished on the public preview. So before that, the container v2 will be the same structure at the beginning around July. I will update more if I can get any date about when the new structure will be implemented.

Thanks.

Regards,
Yutong

0 Votes 0 ·

Thanks for the detailed answer on this, looking forward for the container release.

0 Votes 0 ·

We will definitely post more details in our new document when the new version rolling out. Thank you!

Regards,
Yutong

0 Votes 0 ·