- When the primary requirement is multi-cloud plus internet/SaaS dependency monitoring
- Dedicated DEM and internet monitoring tools are typically better suited for cross-domain and cross-provider visibility.
- When troubleshooting requires visibility inside cloud-provider-managed service internals
- Connectivity Tests may provide overall reachability results for provider-managed services but not internal resource-level traces due to permission boundaries.
- When procurement requires extensive third-party review coverage prior to purchase
- Public review coverage for NIC on major platforms is limited in the sources reviewed, and some review platforms' texts were not accessible for direct citation in this analysis.
- When billing ambiguity is unacceptable
- Metered-but-discounted billing entries and add-on activation risks may be unsuitable for organizations that require simple, predictable licensing semantics.
- Limited internal visibility for Google-managed services
- Connectivity Tests provide reachability outcomes but do not provide internal step-by-step traces for resources within Google-owned projects due to permission boundaries.
- Unsupported configuration elements
- Documentation lists unsupported scenarios and features, such as certain firewall policy elements that include threat intelligence data or FQDN objects.
- Billing and enablement ambiguity
- Modules may be metered and shown in billing even when discounted; add-ons can add costs. Community reports indicate instances of unexpected charges in practice.
- Roadmap and feature timing
- No explicit product roadmap or dated commitments were captured in the sources reviewed for this analysis.