- If you need enterprise-grade compliance proof
- If your buyers require SOC 2 Type II reports and/or ISO 27001 certification evidence, Avaza does not publicly document these certifications in sources reviewed (you may need to request privately, but it’s not published). ([avaza.com](https://www.avaza.com/security/?utm_source=openai))
- If you need advanced identity management
- If you require SAML-based SSO across IdPs, SCIM provisioning, or sophisticated login policies, Avaza’s public docs currently emphasize Avaza login + Google SSO and “future” providers. ([intercom.help](https://intercom.help/avaza/en/articles/14650275-single-sign-on-sso-login-enforcement?utm_source=openai))
- If you require robust audit trails/change tracking
- If you must always attribute changes (“who changed what and when”) for compliance, at least some users report inability to track who made changes. ([capterra.com](https://www.capterra.com/p/136096/Avaza/reviews/?utm_source=openai))
- If your PM practice requires deep methodology support or complex portfolio governance
- TrustRadius feature breakdown suggests weaker alignment for Agile/Waterfall support relative to category averages. ([trustradius.com](https://www.trustradius.com/products/avaza/reviews?utm_source=openai))
- If you want a simple per-seat model
- Avaza’s role-based add-ons can be cost-effective but add complexity; some teams prefer clear per-user licensing like Paymo/Scoro.
- Current limitations acknowledged by the vendor
- SSO roadmap: Avaza explicitly says more SSO providers (Microsoft and others) are planned, implying current limitations to supported providers. ([intercom.help](https://intercom.help/avaza/en/articles/14650275-single-sign-on-sso-login-enforcement?utm_source=openai))
- Roadmap signals (not yet available)
- SSO expansion is explicitly “coming next.” ([intercom.help](https://intercom.help/avaza/en/articles/14650275-single-sign-on-sso-login-enforcement?utm_source=openai))
- Scale limitations
- Not clearly documented in official sources reviewed; practical limits may emerge from reporting performance, storage caps, and invoice/bill limits per plan. ([avaza.com](https://www.avaza.com/pricing/?utm_source=openai))
- Security or compliance gaps
- Lack of publicly documented SOC 2 / ISO certifications (as reviewed).
- API limitations or integration constraints
- API exists with OAuth2 and webhooks; no rate limits were found in the sources reviewed.
- Some users cite specific accounting integration mapping limitations (Xero inventory/GL mapping). ([trustradius.com](https://www.trustradius.com/products/avaza/reviews?utm_source=openai))