OBLYTECH Logo
OBLYTECH Logo

What’s New in ServiceNow Zurich: Features and Upgrade Notes

ServiceNow Zurich adds new products and applications, and it extends features already running on an instance. The changes that affect upgrade planning sit in AI agent model defaults, security and encryption settings, CMDB role assignments, and several customer service workspace components. Check those areas against your instance before you choose an upgrade date.

What the Zurich release contains

Zurich brings new products and applications, along with new features and fixes for products already in use.

Earlier name Zurich name Where it appears
Ticket status AI agent Request status AI agent AI agents for request handling
Global Graph resource Enterprise Graph Knowledge Graph tool setup
AI Native radio button Premium Chat Manual test playgrounds
Test scenario tab Test AI reasoning AI Agent Studio testing page
Output tab Chat responses AI Agent Studio testing page
Kill Switch Protocol Log Agent containment list AI Control Tower
Security tab under Settings > Integrations Control Enforcement Points Settings > Integrations

AI agents, models and testing

The Orchestrator uses GPT-5.4 as its default model when Azure OpenAI is the selected LLM. Default third-party models for AI agents move from GPT 5.2 to GPT 5.4. A new generative AI Config property records these settings in sys_generative_ai_config and sys_generative_ai_prompt_config. Google Gemini and AWS Claude can now back generative AI skills and AI agents, alongside Now LLM Service and Azure OpenAI.

Agent-to-agent flow actions need one check before cutover. They no longer add an Authorization Bearer header automatically. If an external endpoint expects a Bearer token, type the prefix into the API Key credential value. Check those credential values before the upgrade.

The request status AI agent now writes an AI-generated summary of the most recent comments on a request, and you can ask it follow-up questions about earlier answers.

One property controls whether AI-initiated record updates run UI rule validation, such as required fields. The property glide.ai_record_activity.validation.feature.enabled switches that check on, and related properties decide where it applies. Review those settings if your AI agents write to records with mandatory fields.

Security, identity and encryption

Authentication gains an MFA Dashboard that shows enrolment, privileged administrators who have not opted into MFA, and compliance. The MFA guided setup helps administrators turn on MFA for users who currently sign in with only a user name and password. A FIDO factor policy can require a hardware key or biometric as the second factor.

Access Management adds three controls. Machine identity access controls define which integrations can reach specific data through REST or SOAP endpoints. The Scripting Governance Tool makes scripting deny-by-default unless a user holds the snc_required_script_writer_permission role, which is assigned through the Conditional Script Writer group after an upgrade or zBoot. Datatype ACLs let one access control target the columns of a given data type.

Encryption deserves a careful read before upgrading. The GlideEncrypter API now uses AES256-GCM through the Key Management Framework. Legacy 3DES can still be switched on through the glide.security.3des.encryption.allow system property, so run the pre-change checks for that property before you alter it. The glide.security.glideencrypter.allow property controls whether GlideEncrypter runs. It is unavailable on new Zurich instances, and on upgraded instances a user with the security_admin role can edit it. When the property is false, a GlideEncrypter call shows an ‘Unsupported call to GlideEncrypter’ error and returns null, so check any script whose logic depends on the returned value.

AI Control Tower has its own defaults to review. The post-runtime metric defaults need checking after the upgrade. Review each metric under Settings > Rules and templates > Security. The Security Analyzer agent, which sets event severity, is disabled by default. The default sampling rate is 1 percent, and Excessive Agency is off by default. Upgrades leave existing Detection enabled settings unchanged, so review them under Settings > Rules and templates > Security.

CMDB role changes to check before cutover

The CMDB role change affects administrators directly. The itil role now contains sn_cmdb_user and no longer contains sn_cmdb_editor. Several functions that itil users could reach before now need sn_cmdb_editor. These include the operations behind CMDB 360 queries, the CMDB Retirement Definitions module, and the Create CI quick link on the CMDB Workspace Home view.

The Create configuration item agentic workflow requires sn_cmdb_admin in ServiceNow Otto for CMDB version 2.5, where version 2.4 and earlier required sn_cmdb_editor. Version 3.0 uses sn_cmdb_editor again, so check which Otto for CMDB version your instance runs before you assign roles. On zBooted instances, the itil_admin role also stops holding sn_cmdb_admin. List the people who hold itil and decide, role by role, who needs the editor or admin role on top of it.

A smaller CMDB point: new configuration items no longer have the Operational status attribute set, and the new Operational state attribute is optional.

Customer service and workspace changes

Recommended Actions moves to the first tab of the contextual side panel on the front-line case page, the CSM default record page, the CSM Interaction record page, and the email, voice and centred chat interaction pages. On CSM Configurable Workspace record pages, the Lookup component replaces the older Lookup and Verify component.

Coral is the new default theme for portal, web and mobile experiences when Next Experience or Core UI is enabled, and a dark option is available for web and mobile. Existing customers who upgrade can publish Coral with Theme Builder or add it to the Next Experience UX Parent App Theme table.

Build Agent, DevOps and developer sandboxes

Build Agent in ServiceNow Studio builds apps through a conversation. Its run script and rollback script tools show the generated script, its intent and the target application scope in an approval prompt before anything executes. It records its changes in update sets for rollback, and it can run inside Developer Sandboxes.

Instances on Australia Patch 5 or later, or on Zurich Patch 12 or later, that have Build Agent installed receive automatic upgrades when a new version is published through the ServiceNow Store.

For DevOps connections, Jira supports OAuth 2.0 three-legged authentication. Bitbucket Cloud uses Basic Auth with an API token and scopes, because Bitbucket has deprecated app passwords. JFrog connections support bearer token authentication.

Generative AI defaults to review after the upgrade

Starting with Zurich Patch 5, the Generative AI Controller no longer supports direct action calls. The change supports the requirement that AI capabilities are protected by access control lists. Custom generative AI functionality should be built with AI Skill Kit instead.

Skill activation also changes on upgrade. Customers upgrading from Zurich Patch 4 have any previously unconfigured skill turned on automatically, while a skill that was turned on and then off stays off. Query Generation skills are turned on by default when the AI product that uses them is installed.

AI usage measurement moves to a 365-day burn-down that resets on the contract anniversary, starting with Australia Early Access.

Planning the upgrade

The upgrade and release readiness guides cover the wider planning steps, and how ServiceNow release versions are explained helps when you are still choosing between versions.

Score your customisations early. The planning checklist uses five complexity levels. Low covers form layout changes, added fields or UI policies, simple integrations, and table extensions that add fields only. Low-medium adds some scripting to a table extension. Medium covers a new scoped application. Medium-high covers a new global application. High covers changes to baseline business rules, such as the SLA process, and complex custom integrations.

Testing on a production clone and scheduling

Start with a clone. Create a system clone on production and set the development instance as the target. Clear the Exclude check boxes on the Request Clone form so the clone includes production data. If the two instances are the same size, include the production audit log and attachment data as well.

Before the production run, check the two scheduled jobs that control the upgrade, Check distribution for possible upgrade and Check database for possible upgrade, and record the current and target release versions you will use when you schedule the upgrade in Now Support.

Profile performance before the upgrade with the ServiceNow Performance homepage, so you can tell later whether a slowdown is new. Confirm that the non-production defects are fixed, validated and included in an update set. Schedule the upgrade after hours and 15 to 20 minutes before the Upgrade scheduled job interval, and keep a buffer in the change window for responding to errors.

Single-node instances have a short period of downtime during the upgrade. Multi-node instances have no UI downtime, because the instance runs on several nodes and the UI stays up while nodes restart.

Frequently asked questions

What does Zurich add to an existing instance?
New products and applications, plus new features for products already running on the instance. The sections above list the settings to check.

Will the upgrade take the instance offline?
A single-node instance has a short downtime. A multi-node instance keeps the UI available.

Which roles should I review before upgrading to Zurich?
Review the itil role first. It no longer includes sn_cmdb_editor, and several CMDB functions now need that role. The Create configuration item agentic workflow needs sn_cmdb_admin, so check who holds the admin role too.

Which default settings should I check after upgrading?
Check the Security Analyzer agent, which is disabled by default, and each post-runtime metric. The default sampling rate for all metrics is 1 percent. Check Query Generation skill activation, and confirm that any script calling GlideEncrypter still behaves as expected.

Are Zurich release dates fixed?
Plan the upgrade around the exact version and patch you are targeting, not the release date.