Where part of the application estate depends on third-party SaaS platforms, environment management extends beyond infrastructure the organisation directly controls. A few points are worth establishing early in the vendor relationship.
- Sandbox or non-production tenancy availability — confirm the vendor offers a genuinely separate non-production environment, not just a flag within the production tenancy.
- Refresh and reset capability — understand how, and how often, the non-production tenancy can be reset to a known state.
- Integration testing support — clarify whether the vendor’s non-production environment supports the same integrations (authentication, APIs, webhooks) as production, since gaps here are a common source of “it worked in test” failures.
- Change notice — establish how much notice the vendor gives ahead of platform changes that could affect test environments.
These points are worth confirming contractually where possible, rather than assumed — SaaS vendors vary considerably in how seriously they support non-production use, and gaps tend to surface only once they cause a testing problem.