1. The procurement requirement includes robust, "git-like" lifecycle controls for catalog artifacts (strong versioning, environment promotion, deployment management) and the organization cannot accept the maturity gaps reported in reviews.
2. The primary requirement is deep, integrated data-quality management (profiling, rules engines, scorecards) as a core, mature feature rather than a limited capability.
3. The organization requires highly granular, locally managed customization for tags, terminology, or UI text as a non-negotiable need.
4. The procurement process requires full public pricing transparency and instant purchase options; the platform is primarily quoted through vendor sales.
5. The organization prefers a Microsoft-native governance experience tied closely to Azure/Microsoft security and scanning tooling and wishes to avoid third-party governance platforms.