
Rizwan Z. | Nov 05, 2026 | 10 min
The Brazil release has plenty of AI headlines, but the changes most platform teams will feel are elsewhere: where AI-assisted development is processed, how changes are paused during a critical event, how AI agents are governed, and how outdated authentication is retired. For organisations working under strict data protection and operational resilience rules, those changes will shape the upgrade more than any new assistant.
Early availability: September 24, 2026.
General availability: Q4 2026. ServiceNow hasn't published an exact date, so check the release notes before you fix a production date.
Upgrade paths: ServiceNow publishes separate release notes for upgrading to Brazil from Australia, Zurich and Yokohama. It recommends reading the notes from your current version first, because they cover new features, notable changes, fixes, and whether anything you customised will be upgraded.
Brazil follows Australia. After 14 years of alphabetical city names from Aspen to Zurich, ServiceNow switched to country names with Australia, and Brazil is the second. Australia's early availability began on March 12, 2026.
Upgrades can be significant projects, and that the impact of new functionality on an instance always needs considering. A Q4 general availability makes that harder. Many organisations freeze changes at year-end, and the weeks between GA and the freeze are rarely enough for an instance with heavy customisation or several business units to test.
For most teams, the practical choice is between two paths:
Upgrade in Q4. This suits instances close to out-of-the-box that can finish testing before the freeze.
Prepare in Q4, upgrade early next year. This suits instances with complex Change Management, integrations or multiple regions. Use the remaining weeks of the year to read the release notes, run the readiness checks and fix what they find.
Brazil adds a tool to help with that decision. AI Admin Center now includes an upgrade readiness pre-check that helps you plan and prepare an instance for a chosen release and reduce the fixes needed after the upgrade.
The biggest change for regulated organisations is in AI-assisted development. Build Agent and Autonomous Engineer now support regulated markets through the ServiceNow Protected Platform for Australia, the EU and Singapore. That cloud offering stores and processes all customer data in-country on Microsoft Azure.
That matters because AI development tools are often among the hardest features to approve under a data residency policy. With Brazil, organisations on the Protected Platform in those regions can give their developers agentic build tools while keeping data in-country.
Three smaller changes support the same goal:
UK sovereign cloud. Discovery can now find Oracle OCI UK Sovereign Cloud accounts once you configure a UK Sovereign Cloud datacenter URL.
Source code residency. DevOps Change Velocity can connect to GitHub Enterprise Server with data residency controls, keeping code and data in your chosen location.
Cloud authentication. Outbound connections to Microsoft Azure and Google Cloud Platform can now use federated identity. That reduces the number of long-lived secrets your security team manages.
Brazil's Change Management updates are aimed at organisations that have to prove how changes are controlled. In EU financial services, for example, the Digital Operational Resilience Act (DORA) has applied since 17 January 2025, covering ICT risk management, resilience testing and third-party risk. Similar expectations apply in other regulated sectors and countries.
Compliance dynamic schema. Risk and compliance details can now be stored on a change request without adding columns to the change table. ServiceNow gives examples such as whether a change handles personal data, whether an audit trail is required, and how long a rollback takes. The base system includes example categories that you can switch off and replace with your own.
Change lockdown. Change managers can pause all or some in-flight changes during major unplanned IT, critical or financial events. Any change that overlaps an active lockdown is flagged as a conflict and put on hold until it is rescheduled.
Scaled Change. A single scaled change creates and coordinates child change records for every affected configuration item, using scheduling, conflict detection and approvals.
State field policies. Fields on a change request can now be made mandatory or read-only at each state in a change model.
None of these makes an organisation compliant on its own. What they do is replace the custom fields, scripts and manual freezes many regulated customers have built themselves, which makes the evidence clearer for auditors.
Safer defaults for AI agents. On newly activated instances, access to AI agents, agentic workflows, skills, flows and flow actions is now denied by default. In earlier releases it was allowed by default. Existing instances aren't switched over automatically, so review your own access rules during the upgrade.
AI Control Tower adds four controls:
Blocking a specific AI agent, model or domain for everyone in a department.
A new AI Security Operator role that can shut down an AI agent without full AI Steward access.
A retention setting that keeps session and trace data for scoring for up to 30 days, or discards it to save storage. Quality and safety scores stay available either way. Discuss this setting with your data protection lead, because it is the first direct control over how long AI interaction traces are stored.
A connection to Azure AI Foundry, so your policies and kill switch also reach agents running there.
Assist consumption. AI Admin Center can now show total Assist usage by asset, asset type, user and department. That helps organisations that recharge platform costs to business units.
Authentication changes worth planning for:
Basic Authentication. A new restriction page limits Basic Authentication to an allowlist. You run a tracking period first to see who still relies on it, then switch on enforcement. Start the tracking period well before the upgrade so broken integrations don't come as a surprise.
SAML certificates. Banner alerts now warn when SAML signing or encryption certificates are about to expire.
AI voice agents. Callers can be asked for an extra check, such as an Okta Verify push, an SMS code or an authenticator app code, before an AI voice agent handles a sensitive request like a password reset.
Autonomous Engineer. You provide requirements as a prompt or a file. It asks questions to resolve anything ambiguous, checks your instance for existing tables, roles and catalog items, and produces a plan of work items with acceptance criteria. After you approve the plan, it builds the work items in parallel, generates and runs ATF tests, flags anything that needs a person, and produces an update set to deploy to UAT or production.
Build Agent. Build Agent (Trial) is now available by default on every instance, with no installation needed. Instances on Australia Patch 5 or later, or Zurich Patch 12 or later, also receive new Build Agent versions automatically. Platform owners who control releases tightly should know this application now updates itself.
Developer Sandboxes. Every non-production instance now gets four free sandboxes, and purchased packs add 10 each, up to three packs per instance. Sandboxes come from a pre-built pool that refreshes every 24 hours, so a new one can be slightly behind the base instance. Sandbox URLs are now random strings rather than the display name.
Fluent and domain separation. ServiceNow Fluent, which Build Agent uses to create apps, now supports domain separation on records and APIs. That matters to service providers and to organisations that separate data by entity or country.
Lux. Lux is a new framework for building widget-based interfaces from Lit components. Pages are rendered on the server and streamed to the browser, and they pick up the design system through Tailwind and DaisyUI. Pages load fully rendered, with markup that assistive technology and search engines can read. That helps public sector teams working to accessibility requirements.
Model Context Protocol (MCP) lets external AI tools work with ServiceNow data. Brazil extends it to more of the platform:
ITSM. The ITSM MCP Server connects ITSM to AI-enabled MCP clients such as Moveworks or Claude, covering incident and change management for agents and IT managers, and letting requesters check and manage their own tickets. It requires the ServiceNow Otto for ITSM, Model Context Protocol Server and ITSM MCP Server plugins.
Enterprise Architecture. A new MCP server answers questions about business applications, capability mappings, architecture relationships and rationalisation data from an AI assistant.
Your own identity provider. You can register an external authorisation server as a trusted token issuer, and the MCP Server validates its tokens locally.
Security controls. In AI Agent Studio, you can set access rules for an MCP server before adding it as a tool for an AI agent.
ServiceNow's deprecation summary and the combined release notes for your upgrade path are the authoritative lists. These items are worth checking early:
Data Separation, if you're upgrading from Yokohama. Data Separation has been hidden ahead of deprecation since Yokohama, and ServiceNow points customers to data filters and access controls instead. If you use it to separate entities, plan that migration as part of the upgrade.
Virtual Agent NLU. The Brazil documentation now labels NLU topic discovery in Virtual Agent as Legacy. Treat that as a reason to stop investing in NLU models.
Bitbucket integrations. DevOps Change Velocity now authenticates to Bitbucket Cloud with an email address and API token, because Bitbucket deprecated app passwords.
ServiceNow SDK on Windows. Stored credentials stop working after upgrading to SDK version 4.3 or later on Windows, so developers have to re-authenticate.
Access defaults on new instances. Agentic records are denied by default on newly activated instances, so check that new or rebuilt instances behave the same as production.
Sandbox URLs. Any scripts or documentation that work out a sandbox's URL from its name will need updating.
Now Assist is now Otto in the documentation. Brazil’s release notes use the ServiceNow Otto name across products, for example ServiceNow Otto for IT Service Management. Search for Otto when you look up features you know as Now Assist, and update internal guides, training material and knowledge articles that use the old name.
A sensible order of work:
Run the upgrade readiness pre-check.
Start the Basic Authentication tracking period.
Read the combined release notes for your path.
Upgrade a development instance and test your customisations, especially in Change Management and integrations.
Repeat on your other non-production instances.
Then book the production date.
When is the ServiceNow Brazil release generally available?
ServiceNow lists general availability as Q4 2026. Early availability began on September 24, 2026.
Can I upgrade to Brazil from Zurich or Yokohama?
Yes. ServiceNow publishes Brazil release notes for upgrades from Australia, Zurich and Yokohama.
Does Brazil support in-country data residency for AI development?
Yes, for the ServiceNow Protected Platform in Australia, the EU and Singapore. Build Agent and Autonomous Engineer now support it, and it stores and processes customer data in-country on Microsoft Azure.
What changes for AI governance in Brazil?
New instances deny access to agentic records by default. AI Control Tower can block AI agents, models or domains by department, has a dedicated role for shutting down agents, and lets you set how long AI trace data is kept.
What new Change Management features does Brazil include?
Compliance dynamic schema, change lockdown with conflict detection, Scaled Change for changes that affect many configuration items, and state field policies for change models.
What is the ITSM MCP Server?
It connects ServiceNow ITSM to AI tools that support Model Context Protocol, such as Moveworks or Claude, so agents and requesters can work with incidents, change requests and their own tickets from those tools.
Why does the Brazil documentation refer to Otto instead of Now Assist?
ServiceNow Otto is the new name for ServiceNow's AI experience, and the Brazil documentation uses it across products.
EnableNow works with organisations planning ServiceNow upgrades around the things that make them complicated: freeze calendars, data residency, governance policies and instances shared across several countries. If Brazil is on your roadmap, we’re happy to talk it through with your team.

Rizwan Z. • Nov 18, 2026 • 8 min
Read full article→

Rizwan Z. • Nov 12, 2026 • 8 min
Read full article→

Rizwan Z. • Oct 21, 2026 • 10 min
Read full article→
Let EnableNow help you modernize workflows, strengthen performance, and unlock measurable value across your ServiceNow platform.