Blog/Technology

ServiceNow Brazil release: what's new, what's going away and how to upgrade.

ServiceNow Brazil release guide: dates and GA status, what changes automatically on upgrade, new features, deprecations and an 8-step upgrade checklist.

Rio de Janeiro's Museum of Tomorrow at dusk with the headline "Upgrade to Brazil." and the ServiceNow logo

Photo: Bruno Tamm Rabello / Wikimedia Commons, CC BY-SA 4.0 (modified). ServiceNow logo is a trademark of ServiceNow, Inc.

The ServiceNow Brazil release is the family release after Australia, generally available since 5 November 2026 after early availability opened on 24 September. As of 13 November 2026, upgrading to Brazil switches on new ITSM security rules, changes how incidents close and marks dozens of older features as deprecated or being prepared for deprecation. This guide covers the dates, the upgrade changes, the new features and a checklist for upgrade surprises.

  • Automatic on upgrade: the ITSM Enhanced Security Features plugin and the Change Management - Collision Detector plugin both activate when you upgrade to Brazil.
  • Being prepared for deprecation: inbound Basic Auth and Virtual Agent for NLU sit on a cumulative Brazil deprecation summary of more than 50 items.
  • Upgrade path: Zurich and Australia instances can upgrade directly to Brazil, and ATF regression testing belongs on sub-production instances.

When is the ServiceNow Brazil release date?

ServiceNow released Brazil to early availability customers on 24 September 2026 and to general availability on 5 November 2026. Brazil Patch 2, released the same day, is the build available to all customers. Patch 1 shipped on 8 October 2026, and Patch 1 Hotfix 1 followed on 15 October for early availability customers.

Brazil buildReleasedAvailability on 13 November 2026
Feature Early Availability24 September 2026Unavailable
Patch 18 October 2026Unavailable
Patch 1 Hotfix 115 October 2026Available to Early Availability customers
Brazil Patch 25 November 2026Available

Availability comes from the Brazil available versions page, which separates "Available" builds, which any customer can schedule, from builds that need approval from Customer Service and Support. Check the Instance Upgrade Management dashboard for the current Brazil build before you book a production window, and target the latest patch. ServiceNow employee Mike Scully's Brazil release guide also lists GA as 5 November 2026.

Which releases can upgrade to Brazil?

ServiceNow's upgrade guidance says: "You can upgrade directly to the latest release family." It publishes curated Brazil release notes for upgrades from Australia, Zurich and Yokohama, and the same guidance tells you to read the notes for every version between your current release and the target. Yokohama, Zurich and Australia all still had patch targets in Q4 2026 on the available-versions page.

What changes when you upgrade to Brazil?

Two ITSM plugins activate automatically when you upgrade to Brazil, and upgrading Service Operations Workspace for ITSM from the ServiceNow Store installs version 9.5. Three more changes, business-day auto-close, the TinyMCE editor upgrade and stronger getRefRecord() cross-scope security, are not limited to new instances in the notes, so plan to test them on upgrade too.

ChangeWhat the notes sayWhat to test
ITSM Enhanced Security Features pluginActivates automatically on upgrade to Brazil and adds "deny unless authenticated" ACLs to several ITSM tables, per the Brazil incident release notesPortals, public pages and integrations that read ITSM data
Change Management - Collision Detector plugin (com.snc.change.collision)Activates automatically on upgrade to Brazil; the new Change lockdown feature depends on itChange scheduling and conflict settings
Incident auto-closeResolved incidents close after a number of business days instead of calendar days; not limited to new instancesClose timing, and SLAs or reports that may assume calendar days
HTML editorTinyMCE is upgraded from 6.8.2 to 8.3.0 in Core UI and configurable workspaces, per the Brazil platform core notesKnowledge articles, email templates and custom editor plugins
Cross-scope security for getRefRecord()The cross-scope security mechanism "has been strengthened" (KB3142985), and Patch 2 lists a system property "used to enhance cross-scope access controls" for this methodScoped apps that read referenced records across scopes
Service Operations Workspace for ITSMUpgrading from any previous release to Brazil from the ServiceNow Store installs version 9.5, per the SOW for ITSM release notesWorkspace customizations and related lists

We'd test the ITSM Enhanced Security Features plugin first. The incident notes say the plugin "is now activated automatically when you upgrade to the Brazil release", and ServiceNow Support provides the list of ACLs to deactivate if you need to reverse it. The Change Management notes carry the same sentence for Zurich and Australia upgrades, so instances already on those releases may have the plugin active, which is worth checking before you plan. Anything that reads ITSM data without an authenticated session needs a test pass on sub-production.

Which Brazil changes apply only to new instances?

Three Brazil behaviors apply only to newly provisioned (zBoot) instances: auto-resolving incidents on hold for caller information, replacing itil with incident_write in the incident manager role ("applicable only for the zboot instances") and batch-installing entitled apps. Basic Auth is restricted by default on new instances, while on upgraded instances it "may continue to function under certain conditions" and restrictions "may be applied gradually depending on patch or upgrade level". For the major incident manager and communication plan manager roles, the incident notes state that "For the upgrade instances, the itil role remains inherited", so a newly provisioned instance can behave differently from your upgraded production instance.

Are there known issues after the Brazil upgrade?

Customers reported a cross-scope error from the Field Encryption Starter application on the Brazil early availability build and on Patch 1, tracked as PRB2078372. Brazil Patch 2 lists PRB2078372 as fixed. Before Patch 2, the original poster and a ServiceNow employee in a Brazil upgrade Community thread reported that repairing the application cleared the error, and the original poster asked ServiceNow whether that was a permanent fix. Download the personalized PRB list for your source and target versions to see every fixed problem on your path.

What's new in the ServiceNow Brazil release?

Brazil's new features cover Workflow Studio, Change Management, authentication, cloning and developer tooling, plus AI Agent Studio and AI Control Tower changes for teams running AI agents. The features below come from the Zurich-to-Brazil notes, so each is new relative to Zurich. Several also reached Zurich or Australia patches, and those are marked.

Workflow Studio and flow debugging.

Brazil introduces an enhanced Workflow Studio flow designer and a Flow troubleshooting agent that lets developers "Diagnose and resolve flow errors from a conversation." Developers can also modify input values while debugging a flow, and a flow can publish a system event when it enters the error, cancelled or presumed interrupted state. Flow Designer inside Workflow Studio is a different product from the standalone service desk covered in Flow by ServiceNow vs Flow Designer.

Incident and change management.

Change lockdown "allows change managers to pause all or a subset of in-flight change requests" during major unplanned IT, critical or financial events, and lockdown conflict detection flags requests that overlap an active lockdown. Scaled change coordinates child change records per affected CI, and state field policies make change fields mandatory or read-only at each state of a change model.

Incident Management changes the auto-close rule to business days, controlled by the glide.ui.autoclose.time property, where 0 disables it. On-Call Scheduling adds delivery status tracking for escalation notifications from dispatch to acknowledgment. Service Catalog now lets admins control whether service subscriptions bypass "Available for" user criteria on catalog items.

Platform, security and cloning.

The Brazil authentication notes add a Basic Auth Restriction page, identifier-first login policies in the Authentication Console, home-page banners before SAML certificates expire, and Workload Identity Federation for outbound connections to Microsoft Azure and Google Cloud Platform. Identifier-first login also reaches Service Portal.

The Clone Admin Console offers OAuth 2.0 authentication to clone targets "without requiring local admin credentials", plus JWT certificate authentication, a Multi-Instance View and a clone summary. These also appear in the Australia rows, where OAuth targets need Australia Patch 5 or later. For Multi-Instance View, the notes give Australia Patch 2 in the feature rows and Australia Patch 5 under additional requirements, so plan for Patch 5. Core UI lists now show an AI indicator on rows "created or modified by an AI agent". Platform Analytics lets admins share a dashboard with all internal users, and Mobile adds voice to form, which fills an entire mobile form from speech.

Developer tooling.

ServiceNow Studio moves to an "agentic-first" interface with pro, vibe and custom layouts. Build Agent (Trial) "is available by default on all instances, without requiring installation", with a limit of 100 prompts per instance per 30-day cycle and 25 on personal developer instances. Autonomous Engineer, also in the Australia notes, generates an implementation plan from requirements. It needs installing and depends on Build Agent, which depends on ServiceNow Otto for Creator. Test Agent creates ATF tests from that plan.

Every non-production instance gets four free Developer Sandboxes, and update sets move between production and sandbox instances without manual configuration. From Brazil Patch 2, installing the com.glide.dsb plugin no longer enables sandboxes automatically, so admins set glide.dev_sandbox.enabled to true before adding the plugin. For how AI fits into test work more broadly, see using AI to cut ATF test creation time.

CMDB and service mapping.

The Brazil CMDB notes state: "Service Graph Workspace is deprecated as of this release." Its features merge into CMDB Workspace. Dynamic IRE is enabled by default on new instances, and upgraded instances on Static IRE can switch to it. Service Mapping adds MCP tools that expose live application service data and a Lightweight Service Model in Service Mapping Plus 1.24.4. For the data model behind all of this, see CSDM 5.0 and CMDB readiness for AI agents.

AI agents and governance.

Most AI governance items in the Brazil notes also shipped in Zurich or Australia patches, so teams on recent patches may have them already. The redesigned AI Agent Studio, listed in the highlights at Zurich Patch 12 and Australia Patch 5, adds built-in automated evaluations, security controls for MCP servers and a "Test access to an AI asset" check. On newly activated instances it enforces "deny-by-default access control for agentic AI record types", which the Zurich rows also list.

The Zurich, Australia and Brazil rows of the AI Control Tower notes all list department-scoped block policies, an AI Security Operator role that can run the agent kill switch, and an Azure AI Foundry connection. On ServiceNow's product site, AI Control Tower now appears as Super Intelligence Control Tower, though the Brazil release notes still use the old name. It is covered with ServiceNow's personal agent in what ServiceNow Arc is.

ServiceNow Otto for ITSM has AI agents that create change requests from conversation, draft change plan fields and populate the primary and affected CIs, also listed in the Australia notes. In Virtual Agent, existing and new assistants "now run on the latest version of Agentic Orchestrator (v2)". For eligible new customers, premium chat is "the default and the only available chat experience", as in Australia, and it isn't available when an assistant uses the Now LLM Service provider.

What is deprecated or going away in the ServiceNow Brazil release?

ServiceNow's cumulative deprecation summary for Brazil lists more than 50 items, some from earlier releases. Inbound Basic Auth and Virtual Agent for NLU are being prepared for deprecation, while Service Creator, older Studio versions and Service Graph Workspace are deprecated. Prepared items "will eventually be hidden and no longer activated on new instances but will continue to be supported."

FeatureBrazil statusWhat to do
Basic Auth for inbound REST and SOAPBeing prepared for future deprecation; supported until a future release; restricted by default on new instancesInventory Basic Auth accounts and move integrations to OAuth 2.0 or mTLS
Virtual Agent for NLU and Virtual Agent LiteBeing prepared for future deprecationPlan the move to LLM topics
Virtual Agent channels for Alexa, Amazon Connect IVR and IBM Watson Assistant conversationsBeing prepared for future deprecationFlag these channel integrations for replacement
Service CreatorNo longer deployed, enhanced or supportedMove to Creator Studio, which ServiceNow says provides the latest experience
ServiceNow Studio versions before the replatformDeprecated; experience switcher, Tools tab and top-right Create menu removedRetrain developers on the current Studio
App Engine Studio PDF ExtractorDeprecated; apps can be migrated to Build AgentPlan the migration of PDF-to-table apps
Service Graph WorkspaceDeprecated; features merged into CMDB WorkspaceMove users to CMDB Workspace
CMDB BaselineBeing prepared for future deprecationReview baseline use cases against Unified Map
Performance Analytics KPI ComposerDeprecated; "Removal is expected in the D release, and no replacement is planned"Rebuild KPIs elsewhere before the D release
PPM Planning consoleDeprecated and no longer supported; Project Workspace is the replacementMove project managers
Classic Dynatrace event integrationReplaced by the Dynatrace Grail connectorMigrate the integration
Developer Sandboxes data generationRemoved as of Brazil, as announced in the Australia notes; records deleted on upgradeUse the AI Data Kit (formerly Now Assist Data Kit) instead

Two Brazil changes alter access for existing users. The catalog role and catalog admin role no longer grant access through the request-management ACLs the catalog team owns, per the Brazil Service Catalog notes. Inside app_service_admin, the sn_cmdb_editor and app_service_user roles replace itil. One script behavior also changes: Discovery's findOrCreateRelationshipType "no longer creates CI relationship types", so custom scripts should call findCIRelationshipType. That change started at Zurich Patch 10, Australia Patch 2 Hotfix 2a and Australia Patch 3.

Basic Auth needs the longest runway. The Basic Auth Restriction feature has a tracking mode, in which "accounts using basic authentication are recorded but no requests are blocked", and an enforcing mode that blocks Basic Auth except for allow-listed accounts. Web Services Access Only accounts, accounts with a valid MFA one-time password and accounts with the snc_basic_auth_api_access role are exempt.

While glide.authenticate.basic_auth.allow_snc_external stays at its default of true, every snc_external user bypasses the restriction without being logged, so tracking mode misses them. ServiceNow's hardening guidance says to migrate accounts that depend on the external role first, then set the property to false before enforcing. SAP teams will recognize the pattern from SAP's Basic Auth retirement for SuccessFactors APIs.

For Virtual Agent, ServiceNow employee Victor Chen's NLU deprecation post gives the timeline: NLU deprecation is "enforced for new customers at Canada release", with "end-of-support at Denmark (H2 2027)". The move itself is covered in moving Virtual Agent from NLU to LLM topics.

Should you skip Australia and upgrade from Zurich to Brazil?

A Zurich-to-Brazil upgrade brings Australia's changes that apply to upgraded instances as well as Brazil's. Australia deprecated the UI11 and UI15 interfaces and ended clone requests from lists and forms. Its notes also describe secure-by-default glide properties (KB1982254) and cmdb_ci table changes that can increase upgrade time (KB2588894), so check both KBs for how they affect an upgraded instance.

The Australia Next Experience notes say UI11 and UI15 "no longer receive enhancements, defect fixes, and will no longer be supported." The Clone Admin Console notes add that in Brazil "The clone_admin role is required to request, cancel, or schedule clones." Zurich teams on ITSM Agent Workspace face a separate deprecation, covered in moving from Agent Workspace to Service Operations Workspace.

What is the ServiceNow Brazil upgrade checklist?

A Brazil upgrade checklist covers the build you target, the release notes for your upgrade path, the ITSM and change plugins, Basic Auth, role and ACL changes, a code and integration sweep, and ServiceNow's standard upgrade mechanics. ServiceNow's upgrade guidance sets the order: development first, then test, then production.

  1. Confirm: the current Brazil build on the Instance Upgrade Management dashboard and target its latest patch.
  2. Read: the curated release notes for your path, from Australia, Zurich or Yokohama.
  3. Test: unauthenticated, portal and integration access to ITSM data once the Enhanced Security plugin is active.
  4. Track: Basic Auth accounts in tracking mode, migrate external-role accounts, then plan each move to OAuth 2.0 or mTLS.
  5. Retest: change scheduling with the Collision Detector plugin and incident auto-close on business days.
  6. Audit: catalog-only roles on request tables, app_service_admin users and Clone Admin Console roles.
  7. Sweep: scripts calling findOrCreateRelationshipType or cross-scope getRefRecord(), TinyMCE customizations and classic Dynatrace.
  8. Run: ATF and quick start tests on sub-production, work through skipped records, then download your PRB list.

Plan for one constraint: ServiceNow "does not provide a universal rollback option". Rollbacks are available for updates, such as Brazil patch-to-patch, so plan on no rollback for a family upgrade, where restoring production from backup is the final option. The skipped records guidance gives five options per record: retain, merge, revert, mark reviewed or leave it on the list for a later decision. Keep a record of each decision, the habit covered in why ServiceNow documentation goes stale, and staff the first weeks after production as hypercare after go-live.

Is Now Assist now called ServiceNow Otto?

Mostly, and the change started before Brazil. The Zurich-to-Brazil notes state: "Starting with Zurich Patch 12, Now Assist is now ServiceNow Otto." They add that "Your product entitlements remain unchanged." Product apps carry names such as ServiceNow Otto for ITSM, but some Brazil notes still say Now Assist, such as the license requirement for the Clone FAQ Agent.

The MCP Server Console notes also say the console "is available with activation of a Now Assist application." Otto is broader than a rename: ServiceNow announced it at Knowledge 2026 as a unified AI experience that combines the intelligence of Now Assist, Moveworks and AI Experience. How the Moveworks side fits is covered in how ServiceNow merged Moveworks and Now Assist.

Frequently asked questions.

What is the ServiceNow Brazil GA date?

ServiceNow made Brazil generally available on 5 November 2026, per its release notes landing page. Early availability began on 24 September 2026. Brazil Patch 2, released on GA day, is marked "Available" to any customer, so it appears on the Instance Upgrade Management dashboard without an approval request.

Can I upgrade from Zurich directly to Brazil?

Yes. ServiceNow's upgrade guidance says you can upgrade directly to the latest release family, and it publishes curated Brazil release notes for upgrades from Zurich, Australia and Yokohama. A Zurich-to-Brazil upgrade includes Australia's changes that apply to upgraded instances, so read the release notes for upgrading from Zurich in full before planning the project.

What is ServiceNow Brazil Patch 1?

Brazil Patch 1 is the first patch of the Brazil family, released on 8 October 2026 and now shown as unavailable. Patch 1 Hotfix 1 followed on 15 October and remains available to early availability customers. Brazil Patch 2, released on 5 November 2026, is the build available to all customers, so target it or a later patch.

Does the Brazil release deprecate Agent Workspace or UI16?

Brazil's release notes list no new deprecation for Agent Workspace or UI16. ITSM Agent Workspace was deprecated earlier, starting with the Washington DC release, and Australia deprecated UI11 and UI15. The Brazil deprecation summary covers most items, and some, such as Service Creator and Service Graph Workspace, appear only on product release notes.

Is Build Agent free in the Brazil release?

Build Agent (Trial) is available by default on all Brazil instances without installation, limited to 100 prompts per instance per 30-day cycle and 25 on personal developer instances. Autonomous Engineer needs installing and depends on Build Agent, which depends on ServiceNow Otto for Creator, per the Build Agent release notes. Confirm entitlement and cost with your account team.

Can I roll back a Brazil upgrade?

Plan on no. ServiceNow "does not provide a universal rollback option", and rollbacks are available for updates such as Brazil patch-to-patch. For a family upgrade from Zurich or Australia to Brazil, restoring production from backup is the final option. Upgrade development first, then test, then production, and run ATF on sub-production instances before production goes ahead.

Which Brazil changes affect ITSM first?

The ITSM Enhanced Security Features plugin activates on upgrade and adds deny-unless-authenticated ACLs to several ITSM tables, and resolved incidents auto-close on business days, per the Brazil incident release notes. The Change Management - Collision Detector plugin also activates to support Change lockdown, per the Brazil change release notes.

Echelon is the AI workforce for ServiceNow delivery. Its agents read the instance before they build, then build, test and document changes in sub-production behind approval gates, which suits the regression work a family upgrade needs. For the test suite itself, see ATF practices that scale test coverage.

To plan your Brazil upgrade with Echelon, book a scoping call.

Written By

Anav Mohan

Get Started

See Echelon build in your instance.