To date it is only possible to store geometries OGC compliant in a File Geodatabase. Accordingly ArcGIS Pro provides the Data Management Tools “Check Geometry” and “Repair Geometry” with the Validation Method “OGC”. For Enterprise Geodatabases the Validation Method “OGC” is not available. Geometries can only be checked/repaired/stored according to the “Esri Simplify method” in an Enterprise Geodatabase.
A problem arises with data that contains polygons with holes when migrated from a File Geodatabase into an Enterprise Geodatabase in Microsoft SQL Server: the geometry of the data is converted into a single ring (using a point twice if the hole touches the outer ring). This is then no longer OGC compliant.
A description of the case can be found here (Examples OGC vs. Esri - Case a): What is a simple polygon · Esri/geometry-api-java Wiki · GitHub [github.com]
The problem is also described in the following feed: sql server - Can a self-intersecting banana polygon be made OGC-compliant in an Azure SQL Database using spatial functions? - Geographic Information Systems Stack Exchange.
Please allow for the OGC compliant storage of geometries also in Enterprise Geodatabases for Microsoft SQL Server. This way such geometries can be provided in a standardized way by the Feature Service REST interface and can be further processed by any Third Party products that expect OGC compliance.