We have OpenAPI Spec OAS 3.0.0 contains complexities like AllOf, AnyOff, #ref OneOf and want to valicate-contnent for request and response Its not working

Question

We have OpenAPI Spec OAS 3.0.0 contains complexities like AllOf, AnyOff, #ref OneOf and want to valicate-contnent for request and response Its not working

Kambar, Praveen kumar N 0

We have OpenAPI Spec OAS 3.0.0 contains complexities like AllOf, AnyOff, #ref OneOf and want to valicate-contnent for request and response Its not working. and says complex things like AllOf, AnyOff, #ref OneOf doesn't work in validate-content APIM policy. we need to use simplified flattened API spec doc

Kambar, Praveen kumar N 0 Reputation points

2026-07-01T08:36:28.3666667+00:00
This is what I am getting in search
Azure APIM validate-content does not fully support complex OpenAPI composition.

Especially

❌ deep allOf

❌ nested anyOf

❌ oneOf

❌ polymorphism/discriminator

Therefore importing succeeds, but runtime validation may not.
Anshika Varshney 15,455 Reputation points Microsoft External Staff Moderator

2026-07-05T11:50:49.85+00:00

Hello @Kambar, Praveen kumar N

Just checking back to see if you’re still facing the same issue. If the problem persists, please share a few more details and we’ll be happy to help you further.

Thankyou!
Kambar, Praveen kumar N 0 Reputation points

2026-07-06T08:26:08.9133333+00:00

let me share the details
Anshika Varshney 15,455 Reputation points Microsoft External Staff Moderator

2026-07-07T19:52:51.04+00:00

Hello @Kambar, Praveen kumar N

Please let me know if the issue persists after these checks. If you have any remaining questions or need additional details, I’ll be glad to provide further clarification or guidance.

If the above steps resolve your issue, please mark this answer as Accepted so others can easily find the solution.

Thankyou!

1 answer

Your answer

Kambar, Praveen kumar N 0 Reputation points

2026-07-01T08:36:28.3666667+00:00

This is what I am getting in search
Azure APIM validate-content does not fully support complex OpenAPI composition.

Especially

❌ deep allOf

❌ nested anyOf

❌ oneOf

❌ polymorphism/discriminator

Therefore importing succeeds, but runtime validation may not.
Anshika Varshney 15,455 Reputation points Microsoft External Staff Moderator

2026-07-05T11:50:49.85+00:00

Hello @Kambar, Praveen kumar N

Just checking back to see if you’re still facing the same issue. If the problem persists, please share a few more details and we’ll be happy to help you further.

Thankyou!
Kambar, Praveen kumar N 0 Reputation points

2026-07-06T08:26:08.9133333+00:00

let me share the details
Anshika Varshney 15,455 Reputation points Microsoft External Staff Moderator

2026-07-07T19:52:51.04+00:00

Hello @Kambar, Praveen kumar N

Please let me know if the issue persists after these checks. If you have any remaining questions or need additional details, I’ll be glad to provide further clarification or guidance.

If the above steps resolve your issue, please mark this answer as Accepted so others can easily find the solution.

Thankyou!

Answer 1

Thank you for reaching out.

To better understand the issue, could you please share:

The service/product where you are using the OpenAPI 3.0 specification.
The exact error message or behavior you are seeing.
Whether the issue occurs during OpenAPI import, schema validation, or runtime request/response validation.
A minimal sample of the OpenAPI definition containing the allOf, anyOf, oneOf, or $ref constructs causing the problem.

OpenAPI composition features such as allOf, anyOf, oneOf, and nested $ref references are not handled consistently across all Microsoft services and tools. Understanding the specific service and error details will help determine whether this is a supported scenario, a known limitation, or a product issue.

We look forward to your response.