When will prebuilt-bankStatement.us become available in other regions, such as EastUs2?

Auri A. Rahimzadeh 1

Following up on this thread: [https://learn.microsoft.com/en-us/answers/questions/1865930/prebuilt-bankstatement-us-inner-error-((modelnotfo](https://learn.microsoft.com/en-us/answers/questions/1865930/prebuilt-bankstatement-us-inner-error-((modelnotfo)

The prebuilt-bankStatement.us was only available in certain regions, such as East US. However, not all those regions have the Free tier, which is what I'm using for dev purposes.

When will this template be rolled out to the other regions, please?

Is my only option to change my endpoint region in the meantime?

Going forward, are there regions the newer templates are always rolled out to first, so I can be prepared?

Thanks!

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-20T21:04:08.96+00:00

Hello @Auri A. Rahimzadeh , Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

1 answer

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-20T17:08:21.6066667+00:00

Hello @Auri A. Rahimzadeh , Thanks for using Microsoft Q&A Platform.

As I mentioned in the previous thread,

Public preview version 2024-07-31-preview is currently only available in the following Azure regions. East US, West US2, West Europe, North Central US

When will this template be rolled out to the other regions?

Unfortunately, we do not have any ETA to share with you at this moment when certain templates will be available in additional regions.

The best way to stay updated on this would be to check the What's New page, which provides information about new features and services.

Is my only option to change my endpoint region in the meantime?

Yes, to use the prebuilt-bankStatement.us model, you will need to change your endpoint region to one where it is available.

You can create a new resource in a supported region and updating your application to use this new resource.

I understand your concern regarding Free tier, in such cases the only option is to upgrade to standard pricing tier.

Going forward, are there regions the newer templates are always rolled out to first, so I can be prepared?

New features and models are typically introduced in selected regions initially. We cannot confirm the specific regions at this time. Based on my observations, the East US region is frequently chosen, but we cannot provide any guarantees at this moment.

I hope this helps.

Regards,

Vasavi

-Please kindly accept the answer and vote 'yes' if you feel helpful to support the community, thanks.
Please sign in to rate this answer.
Auri A. Rahimzadeh 1 Reputation point

2024-11-20T18:44:36.17+00:00

@VasaviLankipalle-MSFT Thank you. I tried used West US 2 as directed - it has a free tier - and I get a 404. To be fair, I'm using the NuGet library. Do I need to change a setting to use the "preview" version of the API? Is this perhaps a limitation of the NuGet package and I need to switch to REST calls? Thanks! And much appreciated for the quick response!

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-20T19:15:49.6833333+00:00

Hello @Auri A. Rahimzadeh , the error 404 Resource not found can occur if the API or model being used is not available.

Try to Install the Azure Document Intelligence client library for .NET with NuGet:

dotnet add package Azure.AI.DocumentIntelligence --prerelease

Note: This version of the client library defaults to the 2024-07-31-preview version of the service.

.NETStandard 2.0
dotnet add package Azure.AI.DocumentIntelligence --version 1.0.0-beta.3

Make sure you add the necessary libraries and try once again.

Here is the documentation you can refer to: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/ai.documentintelligence-readme?view=azure-dotnet-preview&preserve-view=true

Auri A. Rahimzadeh 1 Reputation point

2024-11-20T19:25:03.4466667+00:00

@VasaviLankipalle-MSFT Thank you. I'll check that out. The docs appeared to use the Form Recognizer nuget not the Document Intelligence nuget. I'll go look and let you know. Much appreciated!

Auri A. Rahimzadeh 1 Reputation point

2024-11-20T19:26:01.9033333+00:00

When I would use the endpoint with the Doc Intelligence nuget I would always get a 404. Maybe I need to create a different endpoint? It's not clear which, though, since there's only one endpoint type for Document Intelligence in Azure. At least, from what I'm seeing.

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-20T19:28:26.4033333+00:00

Hello @Auri A. Rahimzadeh, thanks for the response!

Please try this document intelligence document: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/ai.documentintelligence-readme?view=azure-dotnet-preview&preserve-view=true

Please take time in accepting the above answer if you feel helpful. Thanks!

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-20T19:40:20.9166667+00:00

@Auri A. Rahimzadeh , Regarding your query, when I used the endpoint with the Doc Intelligence NuGet, I consistently received a 404 error.

If the issue is specific to this NuGet package, please try installing the latest pre-release version as mentioned above.

Additionally, attempt to access any of the models in the document intelligence studio with this resource to know the exact issue (Nuget Package/resource).

To clarify, yes, there is only one endpoint for the resource. Different endpoint means creating a new resource.

Auri A. Rahimzadeh 1 Reputation point

2024-11-20T21:58:32.08+00:00

@VasaviLankipalle-MSFT It turns out the Doc Intelligence beta NuGet requires an Azure AI API key + endpoint, not a Document Intelligence / Form Recognizer API key + endpoint.

So, for the Form Recognizer documentation, you use a Document Intelligence resource.

And for the Document Intelligence Studio calls, you use an Azure AI multi-service resource. I'm not sure if the Document Intelligence Studio is mixing the two resources together, then not explaining when and why. So I think it may be good to revisit.

VasaviLankipalle-MSFT 18,061 Reputation points

2024-11-21T18:40:29.7366667+00:00

@Auri A. Rahimzadeh , document intelligence does support Azure AI multi-service resource.

We recommend whenever possible to use the Azure AI services resource (where the API kind is AIServices) to access multiple Azure AI services with a single set of credentials.

That's the reason you might observe AI resource credentials in NuGet, but you can use the resource (multi-service/single) of your choice as both are supported.

Regarding DI studio, you can select the resource of your choice under the settings:

Please refer to this documentation:

https://learn.microsoft.com/en-us/azure/ai-services/multi-service-resource?pivots=azportal#create-a-new-azure-ai-services-resource
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

When will prebuilt-bankStatement.us become available in other regions, such as EastUs2?

1 answer

Your answer