This was originally reported as regression in HHH-12871 Closed .

The main problem was any entity-type that was based on a dynamic-map configuration (which all Envers types are) were being treated differently in 5.2+ than they had in 5.1 which created an issue for spring-data and other integrations. What exacerbated the problem was the fact that embeddables owned by the dynamic-map entity-types were not being excluded, so you were effectively getting the metamodel returning part of the dynamic-map model rather than none of it or all of it as you would typically expect.

I'll need to double check but I'm fairly certain enabled was needed as ignoreUnsupported is the default which excluded the dynamic-map types entirely (which I believe are considered non-spec compliant).