Installing Developer Sandboxes

  • Release version: Zurich
  • Updated August 11, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Installing Developer Sandboxes

    Installing Developer Sandboxes on your ServiceNow instance requires assistance from your ServiceNow account team and is contingent upon entitlement and procurement. This feature is beneficial for developing and testing applications in a controlled environment.

    Show full answer Show less

    Key Features

    • Entitlement Check: Verify your access to Developer Sandboxes based on your entitlements.
    • Installation Case: After confirming entitlement, open a case with Now Support to specify your instance name and the number of sandboxes needed.
    • Environment Consideration: If your instance is in a regulated environment, consult ServiceNow Support regarding Developer Sandboxes.
    • Instance Requirements: Requires a non-production instance on ADCv3 and must be Yokohama or higher.
    • Node Addition: Each sandbox requires its own app-node; for example, 10 sandboxes necessitate 10 additional nodes.
    • Pack Availability: Developer Sandboxes are sold in packs of 10, with a minimum purchase of one pack per instance.
    • SSO Configuration: Access sandboxes using instance credentials or Single Sign-On (SSO) by setting specific properties in the base instance.

    Key Outcomes

    Upon successful installation and configuration of Developer Sandboxes, you can develop and test applications safely in a dedicated environment. The ability to use SSO streamlines access for developers, enhancing user experience. Ensure to coordinate with Now Support for the completion of installation and configuration processes.

    Developer Sandboxes is installed on your instance with assistance from your ServiceNow account team.

    Requesting Developer Sandboxes installation

    Check your entitlements to determine whether you have access to Developer Sandboxes. For more information, see Developer Sandboxes entitlements.

    Developer Sandboxes is a paid feature and is enabled only after procurement is complete. To install Developer Sandboxes once you're entitled, open a case with Now Support specifying the instance name and licensed number of sandboxes.
    Note:
    If your instance is in a regulated environment, check with ServiceNow Support for more information about support for Developer Sandboxes.
    Note:
    The Developer Sandboxes plugin should be installed in your production instance, or any clone source to ensure that cloning a sandbox instance correctly maintains entitlement.

    Prerequisites for installing Developer Sandboxes

    You must have the following to install Developer Sandboxes:
    • A non-production instance
    • The instance is on ADCv3 (Application Delivery Controller version 3)
      Note:
      If the instance is not on ADCv3, it will be moved it as part of the setup.
    • Yokohama or higher

    Instances and sandboxes

    Sandboxes are instance-specific, which means that you can't move a sandbox from one instance to another. If a new instance needs to be sandbox enabled, it will be a net new order.

    Each sandbox is hosted in its own app-node. Therefore, a key part of the setup is adding the required number of additional nodes on the instance. For example, to support 10 sandboxes, 10 new nodes would be added to an instance.

    Developer Sandboxes are available in packs of 10. When you buy two or more packs, you can split the pack between different instances. To do so, open a request with Now Support for each instance.
    Note:
    The minimum is one pack of sandboxes (10) per instance. For example, If you buy two packs, you can't split them 5-15. Each instance must have at least 10 sandboxes.

    Developer Sandboxes does not support self-hosted instances by default, though you can set up your own networking and routing changes to support sandboxes.

    For more information on sandboxes and instances, see General guidelines and use cases for Developer Sandboxes.

    Contact Now Support to finish installation

    The number of available sandboxes on an instance is defined by the number of purchased entitlements. You must contact Now Support to open a case to finish installing and configuring Developer Sandboxes.

    Enabling SSO

    Developers can access sandboxes using instance credentials as well as Single Sign-On (SSO).

    The following properties must be set in the base instance before developers can use SSO to access sandboxes:
    • Disable ACR: sys_property glide.sso.acr.enable=false
    • Enable SSO: glide.authenticate.multisso.enabled = true