Data Zone Standard (EU) availability for Cohere Embed v5 / Rerank v5 in Foundry

Question

Data Zone Standard (EU) availability for Cohere Embed v5 / Rerank v5 in Foundry

Luca Colombo 20

We're an EU company building a RAG platform with EU-only data processing requirements (GDPR). On Microsoft Foundry, Cohere-rerank-v4.0-pro/fast are available as Data Zone Standard (EU), but Cohere-Embed-V5-Pro/Fast and Cohere-rerank-v5-pro/fast are Global Standard only, so we can't use them.

Is Data Zone Standard (EU) planned for Embed v5 and Rerank v5, and is there an expected timeline? We'd adopt them as soon as EU processing is available.

Sairam Reddy Rajamuri 0 Reputation points Microsoft External Staff Moderator

2026-10-23T07:37:27.18+00:00
Hello Luca,

Currently, Microsoft’s published availability documentation does not list Cohere Embed v5 Pro/Fast or Cohere Rerank v5 Pro/Fast for Data Zone Standard in the EU. It lists Cohere Rerank v4.0 Pro/Fast for that deployment type.

Microsoft documents the processing boundary as follows:

Global Standard: inference data may be processed in any Azure region where the model is deployed.

Data Zone Standard: inference data is processed only within the selected Microsoft-defined data zone, such as the EU.

Therefore, Global Standard should not be treated as meeting an EU-only inference-processing requirement.

Microsoft generally releases deployment options in the order Global, then Data Zone, then geography-based. However, this is a general rollout sequence and does not confirm that EU Data Zone support is planned for these specific Cohere v5 models. Microsoft has not published a release date or expected timeline for their EU Data Zone availability.

For now, continue using a model currently documented for EU Data Zone Standard, such as Cohere Rerank v4.0 Pro/Fast, where it meets your technical requirements. Monitor the Foundry model availability documentation for updates.

Thank You!
Luca Colombo 20 Reputation points

2026-10-23T07:51:45.4933333+00:00

Hello Sairam,

Thank you for the answer and for confirming the EU Data Zone Standard availability of Cohere Rerank v4.0 Pro/Fast.

I'd like to understand the underlying issue more directly. Most of the models sold by Azure, including Cohere Embed v5 Pro/Fast, can be deployed in several EU regions (e.g. Sweden Central, Germany West Central, France Central), yet are offered only as Global Standard, with no Data Zone Standard or regional Standard option. Why is that? If the model is already deployable in EU regions, what prevents Azure from offering EU-bounded processing for it?

For comparison, AWS Bedrock offers in-region or EU geo-scoped inference for most of its catalog, including Cohere Embed v4 through an EU-only inference profile. As things stand, a strict EU-only processing requirement leaves us a much narrower model choice on Azure than on other clouds.

Finally, is there an official channel to formally request EU Data Zone Standard support for specific models, starting with Cohere-Embed-V5-Pro / Cohere-Embed-V5-Fast, so that our demand is recorded with the product team?

Thanks
Sairam Reddy Rajamuri 0 Reputation points Microsoft External Staff Moderator

2026-10-23T08:04:03.21+00:00

Hello Luca,

The Azure region where a Global Standard deployment is created does not define its inference-processing boundary. Microsoft documents that Global Standard requests may be processed in any Azure region where the model is deployed, while Data Zone Standard constrains processing to the selected zone, such as the EU. Therefore, deploying Cohere Embed v5 through an EU resource region does not itself provide EU-bounded inference processing.

Microsoft’s published documentation does not explain the model-specific technical or commercial reason why Cohere Embed v5 and Rerank v5 currently lack Data Zone Standard or regional Standard options. It states only that model availability depends on the provider and deployment type and can vary by region.

Microsoft generally introduces deployment types in the following order: Global, Data Zone, and then geography-based. However, this sequence is not a commitment that every model will receive each deployment type, and no availability date is guaranteed.

To formally record the requirement, submit a feature request through the Azure Feedback portal. Include the exact model names, required EU Data Zone deployment type, expected workload, projected usage, preferred EU regions, and the business impact of the current limitation. The portal specifically recommends describing how the requested change would enable or unblock the scenario.

Until the availability documentation lists Cohere Embed v5 or Rerank v5 under EU Data Zone Standard, Global Standard should not be treated as meeting a strict EU-only inference-processing requirement.

Thank You!

Answer accepted by question author

0 additional answers

Your answer

Sairam Reddy Rajamuri 0 Reputation points Microsoft External Staff Moderator

2026-10-23T07:37:27.18+00:00

Hello Luca,

Currently, Microsoft’s published availability documentation does not list Cohere Embed v5 Pro/Fast or Cohere Rerank v5 Pro/Fast for Data Zone Standard in the EU. It lists Cohere Rerank v4.0 Pro/Fast for that deployment type.

Microsoft documents the processing boundary as follows:

Global Standard: inference data may be processed in any Azure region where the model is deployed.

Data Zone Standard: inference data is processed only within the selected Microsoft-defined data zone, such as the EU.

Therefore, Global Standard should not be treated as meeting an EU-only inference-processing requirement.

Microsoft generally releases deployment options in the order Global, then Data Zone, then geography-based. However, this is a general rollout sequence and does not confirm that EU Data Zone support is planned for these specific Cohere v5 models. Microsoft has not published a release date or expected timeline for their EU Data Zone availability.

For now, continue using a model currently documented for EU Data Zone Standard, such as Cohere Rerank v4.0 Pro/Fast, where it meets your technical requirements. Monitor the Foundry model availability documentation for updates.

Thank You!
Luca Colombo 20 Reputation points

2026-10-23T07:51:45.4933333+00:00

Hello Sairam,

Thank you for the answer and for confirming the EU Data Zone Standard availability of Cohere Rerank v4.0 Pro/Fast.

I'd like to understand the underlying issue more directly. Most of the models sold by Azure, including Cohere Embed v5 Pro/Fast, can be deployed in several EU regions (e.g. Sweden Central, Germany West Central, France Central), yet are offered only as Global Standard, with no Data Zone Standard or regional Standard option. Why is that? If the model is already deployable in EU regions, what prevents Azure from offering EU-bounded processing for it?

For comparison, AWS Bedrock offers in-region or EU geo-scoped inference for most of its catalog, including Cohere Embed v4 through an EU-only inference profile. As things stand, a strict EU-only processing requirement leaves us a much narrower model choice on Azure than on other clouds.

Finally, is there an official channel to formally request EU Data Zone Standard support for specific models, starting with Cohere-Embed-V5-Pro / Cohere-Embed-V5-Fast, so that our demand is recorded with the product team?

Thanks
Sairam Reddy Rajamuri 0 Reputation points Microsoft External Staff Moderator

2026-10-23T08:04:03.21+00:00

Hello Luca,

The Azure region where a Global Standard deployment is created does not define its inference-processing boundary. Microsoft documents that Global Standard requests may be processed in any Azure region where the model is deployed, while Data Zone Standard constrains processing to the selected zone, such as the EU. Therefore, deploying Cohere Embed v5 through an EU resource region does not itself provide EU-bounded inference processing.

Microsoft’s published documentation does not explain the model-specific technical or commercial reason why Cohere Embed v5 and Rerank v5 currently lack Data Zone Standard or regional Standard options. It states only that model availability depends on the provider and deployment type and can vary by region.

Microsoft generally introduces deployment types in the following order: Global, Data Zone, and then geography-based. However, this sequence is not a commitment that every model will receive each deployment type, and no availability date is guaranteed.

To formally record the requirement, submit a feature request through the Azure Feedback portal. Include the exact model names, required EU Data Zone deployment type, expected workload, projected usage, preferred EU regions, and the business impact of the current limitation. The portal specifically recommends describing how the requested change would enable or unblock the scenario.

Until the availability documentation lists Cohere Embed v5 or Rerank v5 under EU Data Zone Standard, Global Standard should not be treated as meeting a strict EU-only inference-processing requirement.

Thank You!

Answer 1

Hi Luca Colombo & thx for join me at Q&A platform,

ur understanding is correct. Based on the currently published Microsoft Foundry model availability information, Cohere Embed v5 Pro/Fast and Rerank v5 Pro/Fast aren't listed for Data Zone Standard (EU). Rerank v4.0 Pro/Fast is available, but there's no publicly confirmed release date or commitment to add EU Data Zone support for the v5 models.

One important distinction is that deploying a Global Standard model in an EU Azure region doesn't guarantee that inference processing stays in the EU. The selected region determines where the deployment resource is created, but Global Standard can route inference requests to infrastructure in other geographies. So choosing Sweden Central, Germany West Central, or France Central doesn't change that processing boundary.

Microsoft generally introduces new models through Global Standard first, followed by additional deployment types where supported. However, that doesn't guarantee every model will eventually receive Data Zone Standard support. The exact reason Cohere v5 isn't available with EU-bounded processing hasn't been publicly confirmed. It could involve capacity, deployment architecture, or product rollout decisions, but only the Foundry product team can clarify that.

For a production RAG platform with strict EU processing requirements, I wouldn't use Global Standard and assume the deployment region provides the necessary residency guarantees. I'd continue with an EU Data Zone-supported reranking model and evaluate an EU-compliant embedding alternative, or consider self-hosting an appropriate embedding model on Azure compute located within the required geography.

One additional detail worth checking with ur compliance team: Microsoft's EU Data Zone documentation refers to the Azure EU Data Boundary, which may include EFTA locations such as Norway and Switzerland. If ur requirement literally means processing only within EU member states, that distinction matters too.

Regarding the roadmap, I'd recommend raising a formal feature request through ur Microsoft account team or Azure support, specifically requesting DataZoneStandard for Cohere Embed v5 Pro/Fast and Rerank v5 Pro/Fast. Include the expected request volume, target EU regions, production timeline, and data residency requirements. That gives the product team useful information for prioritization.

I'd also ask a Microsoft Foundry moderator to forward this question to the model deployment product team for clarification.

The two questions I'd want Microsoft to answer are whether EU Data Zone support for Cohere v5 is actually on the roadmap, and, if so, whether there's even a tentative availability window.

Without that confirmation, I wouldn't design a production migration around an assumed future release.

rgds,

Alex

p.s. if my answer is help - pls mark it as an answer

Luca Colombo 20 Reputation points

2026-10-23T13:10:25.8766667+00:00

Thanks Alex, very helpful. On the EU Data Boundary point: processing anywhere in Europe (including EFTA locations such as Norway and Switzerland) is fine for our requirement. What we need to avoid is routing outside Europe, which is why Global Standard doesn't work for us.

I've submitted the formal feature request here:

https://feedback.azure.com/d365community/idea/a1675271-bace-f111-aad1-6045bdb3d415

I'd appreciate it if a Foundry moderator could forward the roadmap question for Cohere Embed v5 / Rerank v5 EU Data Zone support to the product team.