DataZoneStandard text-embedding-3-small: control plane succeeded, data plane returns 404 DeploymentNotFound (Sweden Central)

Kevin Xie 25 Reputation points
2026-08-24T21:26:12.68+00:00

An embeddings deployment shows status=succeeded on the control plane, but

every inference call returns 404 DeploymentNotFound. This has persisted for

more than 2 hours after creation.

Setup

  • Region: Sweden Central
  • Model: text-embedding-3-small (v1)
  • SKU: DataZoneStandard, capacity 1M TPM
  • Deployment name: text-embedding-3-small
  • Created: 2026-08-24 13:46 UTC, succeeded since

Failing calls — both routes fail identically:

POST /openai/v1/embeddings

  {"model":"text-embedding-3-small", ...}

POST /openai/deployments/text-embedding-3-small/embeddings?api-version=2024-10-21

Sample failure: apim-request-id 6235c334-1db0-4f61-8e2f-5bdba58b64e8

at 2026-08-24T20:59:22Z, x-ms-region: Sweden Central

**Why this looks like a data-plane registration fault rather than a client

issue** (same key and same resource throughout unless noted):

  1. GET /openai/deployments?api-version=2022-12-01 lists the deployment with status=succeeded.
  2. Calling the embeddings route against a DataZoneStandard chat deployment on the same resource returns 400 OperationNotSupported — so the embeddings route's deployment lookup works, and the resource and key are valid.
  3. POST /openai/v1/chat/completions with model=text-embedding-3-small returns "The requested operation is unsupported", not DeploymentNotFound — so the deployment name resolves on the chat route.
  4. Identical deployments (same name, same model) on our Canada East and Japan East resources (Standard SKU) return HTTP 200 with 1536-dim vectors.
  5. Per the region-availability docs (updated 2026-08-21), DataZoneStandard + text-embedding-3-small + swedencentral is listed as a supported combination.

Points 2 and 3 together are the key evidence: the deployment name resolves on

the chat route and the embeddings route resolves other deployments, but this

deployment is invisible specifically to the embeddings route.

Conclusion / ask

It appears this deployment was never registered with the EU data-zone

embeddings inference pool. Can someone from the product group check the

registration for the request ID above and repair it, or tell me what else to

check? Delete-and-recreate is my next step — happy to hold off if the PG wants

the deployment left in its current broken state for diagnosis.

Azure OpenAI in Foundry Models
0 comments
Answer accepted by question author
Allan Solomon Mejia 8,085 Reputation points
2026-08-24T21:58:19.6233333+00:00

Hello @Kevin Xie

Based on the testing you have already done, it seems unlikely that this is a client-side configuration issue.

The key evidence is:

  • The deployment exists and shows it succeeded.
  • The same resource/key works with other deployments.
  • The text-embedding-3-small model provides the embeddings operation.
  • The deployment name is resolved via another route, but the request to/embeddings returns a 404 DeploymentNotFound error.
  • The issue has persisted for over two hours.

This suggests a problem with how the control plane and data plane are being deployed. However, we can't verify from the customer's end whether the issue is specifically due to EU data-zone registration, since Microsoft doesn't make that internal state available.

I won't delete and recreate the deployment at this stage since you already have the request ID and timestamp, which will be useful evidence for Microsoft when tracing the issue.

Request ID: 6235c334-1db0-4f61-8e2f-5bdba58b64e8

Region: Sweden Central

SKU: DataZoneStandard

Model: text-embedding-3-small

Error: 404 DeploymentNotFound

I suggest you take this up with Microsoft Support or the Azure OpenAI product team and ask them to check why the successful deployment isn't available via the embeddings data plane.

Microsoft reference:

Azure OpenAI REST API – Embeddings

Since you have already carried out the isolation, I don't believe that any further troubleshooting on the client side would be of much use until Microsoft looks into the service-side deployment status.

Please "Accept the Answer" if this information helped you. This will help us and others in the community.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

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