Upgrading API Version breaking Container URLs

Porter, Cody 45 Reputation points
2025-01-17T17:40:54.02+00:00

We upgraded one of our projects from API version 2024-07-31-preview to 2024-11-30. The person who did the upgrade is able to access the project just fine but when others go to access the project they are receiving a container access error.

We used the interface/wizard in document intelligence studio to perform the upgrade.

User's image

Upon inspection of the projects settings it doesn't appear the container name is getting prefixed to the blob container url.

Blob container url is missing the domain of the container resource name (EX: anbstoragediprd).The person who did the upgrade it does appear correctly.

Incorrect Blob container URL:

User's image

Correct Blob Container URL: (Person who performed the upgrade it works fine)

User's image

Is there something we can do here to fix this for people who didn't do the upgrade to access the project?

Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
1,909 questions
{count} votes

Accepted answer
  1. Sina Salam 17,176 Reputation points
    2025-01-22T15:01:00.2233333+00:00

    Hello Porter, Cody,

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

    Issue: Upgrading API Version breaking Container URLs

    Error Message:

    Blob container url is missing the domain of the container resource name (EX: anbstoragediprd).

    Solution: <as stated in the comment>

    The best strategy Porter, Cody developed for his team to resume sharing projects while transitioning to "All Projects" involves the following steps:

    1. Upgrade the project in place; select "skip" in the upgrade wizard. User's image Confirm that the *.ocr.json and *labels.json files within your containers are updated (Modified Date: 1/22/2025). User's image
    2. Create a new project, selecting the same container as the project you just upgraded, from "My Projects".
    3. Delete the old project
      1. Verify it is removed from "My Projects"
      2. Verify it is removed from "All Projects"
    4. Verify that everyone can access the newly created project through "All Projects"
      1. Check that users can access label dataset without errors
      2. Ensure users can perform their job functions within the label dataset
    5. Train new model using the new API version 2024-11-30

    This process ensures a successful upgrade and transitions your team to using the "All Projects" feature effectively.

    User's image

    0 votes Report a concern

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Sina Salam 17,176 Reputation points
    2025-01-18T18:48:17.5833333+00:00

    Hello Porter, Cody,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    Regarding your explanations, four things to take note are:

    • The project was upgraded from API version 2024-07-31-preview to 2024-11-30.
    • The person who performed the upgrade can access the project without issues.
    • Other users are receiving a container access error.
    • The blob container URL is missing the domain of the container resource name for users who didn't perform the upgrade.

    This is not a mystery but check the followings to resolve the issue:

    • Ask all affected users to clear their browser cache and cookies. Sometimes, old cached data can cause issues with accessing updated resources.
    • Check the configuration files for the project are correctly updated to include the domain of the container resource name. Compare the configuration files of the user who performed the upgrade with those of the affected users.
    • Check that all environment variables related to the blob container URL are correctly set for all users. Ensure that the domain of the container resource name is included in these variables.
    • Check the application code to ensure that the blob container URL is being constructed correctly. Look for any code that might be omitting the domain of the container resource name.
    • Check any deployment scripts or automation tools used during the upgrade process. Ensure that these scripts are correctly setting the blob container URL for all users.
    • Check the API documentation for version 2024-11-30 to see if there are any changes related to how the blob container URL should be specified. Ensure that the project is compliant with these changes.
    • Finally, check if there are any user-specific settings or profiles that might be affecting the blob container URL. Ensure that all users have consistent settings.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions.


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    0 comments No comments

Your answer

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