Platform Updates

ServiceNow Australia Release: What Developers and Admins Need to Know

The Australia release is the platform version that delivers the Knowledge 2026 announcements — Action Fabric with MCP Server GA, the expanded AI Control Tower, Autonomous Workforce expansion, and more. Here is what is new, what changed, and what practitioners need to focus on when upgrading.

ServiceNow follows an alphabetical naming convention for major releases — Xanadu, Vancouver, Washington, and now Australia. Each release is a significant platform update that introduces new capabilities, changes existing behaviours, and deprecates older patterns. Australia is particularly significant because it is the release that makes the KN26 announcements real and deployable.

Why Australia is Different From Previous Releases

Previous releases focused primarily on expanding the feature set — new APIs, new Flow Designer capabilities, new Now Assist features. Australia does that, but it also makes a more fundamental architectural change: it establishes the agentic AI infrastructure as a first-class platform component.

Action Fabric with MCP Server, AI Control Tower built into every product SKU, and the Autonomous Workforce expansion are all delivered through Australia. This is not a feature release — it is a platform architecture shift. The upgrade considerations are different as a result.

Key Deliverables in the Australia Release

Action Fabric and MCP Server — Generally Available

The most architecturally significant item in Australia. The Action Fabric MCP Server is generally available in every Now Assist and AI Native SKU. This means:

  • Any MCP-compatible AI agent can now discover and execute governed ServiceNow actions
  • Anthropic Claude integration is live — Claude can trigger workflows, catalog actions, and approvals through the MCP Server
  • Additional Action Fabric features are planned for H2 2026

For most organisations, this does not require immediate action — but developers and architects should understand the capability and begin thinking about which workflows should be exposed through Action Fabric and under what governance policies.

AI Control Tower — Included in All Product Packages

AI Control Tower is no longer a separate SKU. It is built into every ServiceNow product package in the Australia release. If your organisation is on a current Now Assist or AI Native SKU, you have access to AI Control Tower.

The Australia release delivers the expanded version announced at KN26 — Discover, Govern, Observe, Secure, and Measure — with the 30+ enterprise integrations for AWS, Azure, Google Cloud, SAP, Oracle, and Workday.

Autonomous Workforce Expansion

The L1 IT Service Desk AI Specialist, CRM Specialists, and Employee Service Specialists are generally available in Australia. The IT Operations Specialists follow in June; Security and Risk Specialists in September.

Autonomous Security and Risk

The integrated Armis and Veza capabilities are delivered through Australia, providing the unified asset visibility and identity governance layer for AI and human identities.

What to Review Before Upgrading to Australia

Every ServiceNow upgrade requires testing, but Australia has some specific areas that warrant extra attention given the architectural changes.

Now Assist Configurations

If your instance has Now Assist activated, review your current configuration before upgrading. Australia changes the underlying AI architecture in ways that may affect how existing Now Assist capabilities behave. Test summarisation, search, and code generation in a sub-production environment before promoting to production.

Flow Designer Flows

Australia introduces changes to how flows are exposed through Action Fabric. While this should not break existing flows, review any flows that use external REST calls or complex data transformations — these are the most likely areas to see behavioural differences after upgrade.

Integration Connections

As with previous releases, IntegrationHub connections should be tested after upgrade. Pay particular attention to OAuth 2.0 connections and MID Server configurations — these areas have seen changes across recent releases and Australia is no exception.

ACL and Security Policies

With AI Control Tower now active by default, review your ACL configurations and role assignments. AI agents operating through Action Fabric will run under defined identities with defined permissions — if your ACLs have gaps or inconsistencies, they will surface more visibly when agents start executing automated actions.

CMDB Data Quality

Australia makes the CMDB more central than it has ever been — it is the data source that grounds every AI agent's understanding of the enterprise environment. Before upgrading, audit your CMDB data quality. Stale, incomplete, or incorrect CI data will directly impact the quality of AI agent behaviour in Australia and beyond.

New Developer Capabilities in Australia

MCP Server API

Developers can now build MCP-compatible clients that connect to the ServiceNow MCP Server and call exposed actions programmatically. The API documentation covers how to authenticate, discover available actions, call them with typed parameters, and handle responses and errors.

Action Fabric Configuration

A new configuration surface in Studio allows developers to define which flows, catalog items, and scripted REST APIs are exposed through Action Fabric, what parameters they accept, and what governance policies apply to each. Think of it as publishing your flows as tools that external agents can discover and call.

AI Control Tower API

AI Control Tower exposes APIs for programmatic governance policy management — creating policies, assigning them to agents, querying observability data, and managing agent identities. For organisations with complex governance requirements, this enables policy-as-code approaches to AI governance management.

Preparing Your Instance for Australia

The practical preparation steps, in priority order:

  • Run the upgrade scanner — identifies deprecated patterns and compatibility issues before you upgrade
  • Audit CMDB data quality — start with the CI classes most relevant to your AI use cases
  • Review ACL configurations — ensure they are clean and consistent before agents start executing actions
  • Test Now Assist in a sub-production instance — validate that existing AI configurations behave as expected
  • Identify Action Fabric candidates — which flows and catalog items do you want to expose to external agents, and under what governance policies
  • Brief your security team on AI Control Tower — they will want to understand the governance model before production AI agents are active

Key Takeaways

  • Australia is the release that delivers the KN26 announcements as deployable capabilities
  • Action Fabric MCP Server is GA in every Now Assist and AI Native SKU
  • AI Control Tower is now included in every product package — no separate activation needed
  • CMDB data quality is more critical than ever — it grounds every AI agent's decision-making
  • Review ACLs, Now Assist configurations, and Flow Designer flows before upgrading
  • Action Fabric configuration in Studio allows you to publish flows as tools for external AI agents

Australia release in the context of the long-term roadmap

The Australia release sits in ServiceNow's biannual release cadence and carries forward themes established in Xanadu — AI-native development, HTAP database performance via RaptorDB, and expanded Now Assist capabilities. Each release adds refinements to the developer toolset: new GlideQuery features, expanded Flow Designer capabilities, additional IntegrationHub spokes, and platform security improvements. For developers, the upgrade process requires reviewing the release notes for deprecated APIs, running an Instance Scan on a clone post-upgrade to catch upgrade-related issues, and validating critical Business Rules and integrations still function as expected. For admins, post-upgrade tasks include reviewing scheduled job schedules, validating notification configurations, and testing critical user workflows in a cloned sub-production instance before approving production upgrades.

Stay current on releases: Xanadu new features · Knowledge 2026 recap · Update Sets for upgrade preparation

Developer impact summary

For developers on the Australia release, the most important areas to review in the release notes are: scripting API changes (new methods added, any deprecations flagged), Flow Designer capability additions (new trigger types, new action types, changes to existing action behaviour), and Security changes (new ACL evaluation rules, any changes to scoped application access controls). The Australia release continues Xanadu's direction of making GlideRecord patterns more explicit and Flow Designer more capable — with each release, the recommendation to use Flow Designer for new process automation becomes stronger while Business Rules remain appropriate for synchronous, record-level operations.

Admin impact is primarily in two areas: scheduled maintenance and notifications configuration. Each release includes changes to how scheduled jobs are surfaced and managed, and notification engine improvements that affect delivery reliability. Review your Scheduled Jobs list post-upgrade and your notification configurations to catch any behaviour changes introduced by the release. The post-upgrade Instance Scan is essential — it catches upgrade-specific issues that were not present pre-upgrade.

What to prioritise for Australia release preparation

For teams upgrading to Australia, the three highest-priority preparation activities are: first, clone production and upgrade on the clone to identify any issues before scheduling the production upgrade window. Second, run an Instance Scan on both the pre-upgrade and post-upgrade clone to identify issues introduced by the upgrade itself. Third, review the official ServiceNow release notes for deprecation warnings — ServiceNow typically gives two releases of warning before removing deprecated APIs, so anything deprecated in Xanadu is likely removed or further restricted in Australia. Developers should search their codebase for any deprecated API usage and plan remediation. Admins should review scheduled job execution logs in the first week after upgrade to catch any jobs that are failing due to release-related changes. The career path of practitioners who stay current on releases — understanding new features deeply enough to advise clients and colleagues — remains one of the highest-value skills in the ServiceNow ecosystem.

The Australia release continues the direction set in Xanadu — AI-native features, RaptorDB performance improvements, and expanded Flow Designer capabilities. Review the Xanadu guide for foundational context, follow ServiceNow's official release notes for Australia-specific changes, and plan your upgrade cycle with a clone-first approach. The cloning guide covers the pre-upgrade testing workflow that every team should follow before approving production upgrades.

Developer checklist for Australia upgrade

Before approving Australia upgrade in production: run Instance Scan on the pre-upgrade clone to capture the baseline finding list, upgrade a clone, run Instance Scan again and compare findings (new findings likely relate to the upgrade), run your ATF test suite (any failing tests need root cause investigation before production upgrade), review the Australia release notes for deprecated API warnings and search your codebase for any deprecated method usage, and verify all Scheduled Jobs executed correctly in the first 48 hours post-clone-upgrade.

Staying sharp on the platform?

The NowSpectrum Pro Tips and Tricks guide covers 50 battle-tested tips for developers and admins — performance, scripting, Flow Designer, and platform best practices that apply across releases.

Get the Pro Tips Guide →
← Back to all posts