Document intelligence Layout : Connected container getting Invalid Billing Endpoint URI

Nilaan 0 Reputation points
2025-02-25T16:29:39.32+00:00

Affected Service : Azure document intelligent : connected container ( layout 3.1 mode)

Followed tutorial : https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/containers/configuration?view=doc-intel-3.1.0&preserve-view=true

environment : Windows 11

i have enable Commitment plans for above, but now i cant connect to the service from the container , i have given the billing (URL) and ApiKey correctly.

i am getting Invalid Billing Endpoint URI.

NOTE :

  1. For the same Endpoint and KEY 1 of the same Document intelligence resource i can use the service with npm package / SDK.
  2. Further with another Document Intelligence resource in the same subscription and without a Commitment plans container is working fine without the error ( can connect) .

docker error

azure screenshot

User's image

docker-compose :

services:
  azure-form-recognizer-layout:
    container_name: azure-form-recognizer-layout
    image: mcr.microsoft.com/azure-cognitive-services/form-recognizer/layout-3.1
    environment:
      - EULA=accept
      - Logging:Console:LogLevel:Default=Debug
      - billing=${FORM_RECOGNIZER_ENDPOINT_URI} //https://cu.cognitiveservices.azure.com/
      - apiKey=${FORM_RECOGNIZER_KEY}
      - SharedRootFolder = /share
      - Mounts:Shared = /share
      - Mounts:Output = /logs
    volumes:
      - type: bind
        source: ${SHARED_MOUNT_PATH}
        target: /share
      - type: bind
        source: ${OUTPUT_MOUNT_PATH}
        target: /logs
    ports:
      - "5000:5000"
    networks:
      - ocrvnet
    expose:
      - "5000"
networks:
  ocrvnet:
    driver: bridge
Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
1,946 questions
{count} votes

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.