Add: japaneast for latest api version available list

[ry0y4n]

I have a Document Intelligence resource located in "japaneast". And now, I confirmed that I can use the latest API version (2024-07-31-preview) on my code (Python). I don't know whether other regions can use, but I confirmed that "japaneast" is supported now. So add "japaneast" to the list of regions that helps users to know where they can use the latest API version.

My environment:

• Document Intelligence
  • location: japaneast
  • plan: free
• Development environment
  • azure-ai-documentintelligence==1.0.0b4

My code

from azure.core.credentials import AzureKeyCredential
from azure.ai.documentintelligence import DocumentIntelligenceClient
from azure.ai.documentintelligence.models import AnalyzeResult
import os
from dotenv import load_dotenv
load_dotenv('.env')

endpoint = os.environ["FORM_RECOGNIZER_ENDPOINT"]
key = os.environ["FORM_RECOGNIZER_KEY"]
path_to_sample_documents ="sample-layout.xlsx"
# path_to_sample_documents = "sample-layout.docx"

document_analysis_client = DocumentIntelligenceClient(
    endpoint=endpoint, credential=AzureKeyCredential(key)
)

with open(path_to_sample_documents, "rb") as f:
    poller = document_analysis_client.begin_analyze_document(
        "prebuilt-layout", analyze_request=f, content_type="application/octet-stream"
    )

result: AnalyzeResult = poller.result()
print("modelId: {}".format(result.model_id))
print("apiVersion: {}".format(result.api_version))
print("content: {}".format(result.content))

The output is here:

$ uv run layout-test.py 
modelId: prebuilt-layout
apiVersion: 2024-07-31-preview ←-- HERE
content: Sheet1 
page1
Sheet2
page2

[prmerger-automator]

@ry0y4n : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 44a91e5:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/ai-services/document-intelligence/includes/preview-notice.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ttorble]

@laujan

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

[ry0y4n]

Hi @laujan & @ttorble ,

Is there any updates?

[v-dirichards]

@laujan for review. Thanks.

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict