This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 69%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEH%3C/text%3E%3C/svg%3E)
Hello,
We are using v2.1-preview.3 in production, and we have just started to get numerous errors saying it has been deprecated. I am subscribed to the RSS for the "whats new in form recognizer" and other news updates, but I have not seen anything to say that v2.1 would be deprecated. Could you please let me know where it was published that this version would be deprecated so that I can know for future before my production system collapses?
Could you please confirm which is the GA version? In all the documentation it always has v3 alongside the v2.1 and there is nothing on any of the 2.1 documentation that says it has expired. The main form recognizer intro page updated on the 28th of this month says that 2.1 is the GA and 3.0 is preview. So I am curious why, as of just a few moments ago, my 2.1 has stopped working. Is it because I have preview 3 on it? Can I go onto 2.1 not preview? I can only train version 3 in form recognizer studio, so we were planning to go up to the newest version. But I can't push to prod immediately right now because 2.1 suddenly stopped working. https://learn.microsoft.com/en-us/azure/applied-ai-services/form-recognizer/overview?tabs=v2-1
Thanks,
Emily
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 94%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMZ%3C/text%3E%3C/svg%3E)
Hello,
I have the same problem as Emily. The production script fell apart with this message. What is the new GA version?
Thank you.
Michal
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 45%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi, thanks for reaching out. It looks like Microsoft Azure sent an email few weeks back to customers mentioning deprecation of v2.0 preview and v2.1 preview APIs which were retired on Oct 15, 2021. To continue using Form Recognizer, please migrate to v2.1 GA API or latest version. More details are provided in the email, also check out what's new page for updates.
----------
--please don't forget to Accept Answer if the reply is helpful. Thanks.--
Why is the "Whats new" page not updated with this same information? I have real time RSS set up for this and I also check it frequently, but there was no mention. It seems like putting out an announcement on the actual form recognizer documentation pages would be the best place for everyone to see it.
I have no idea who in our organization would have been emailed, but we - the devs - did not receive anything. It may well have been sent to our admins who have no clue about who is using what or what it means for us. Where did you get the email contacts to send it to? Please can you in future post your updates somewhere public that everyone across our organization can see and don't keep it a secret from us.
Secondly, if 2.1 is the GA, why is it not possible to train 2.1 models in Form Recognizer Studio? We were all encouraged to leave FOTT and go to here. I would then have to end up training old models in FOTT with projects there and new in the new studio with projects there and it is a mess. I don't understand why GA 2.1 isn't supported in the new studio, if this is the one we should be using.