EnableNow Emblem
ServiceNow Brazil Release
Rizwan Z.

Rizwan Z. | Nov 05, 2026 | 10 min

What to know before upgrading to the ServiceNow Brazil release


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.

ServiceNow Brazil release dates

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.

Planning the upgrade around a Q4 release

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:

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.

Data residency and sovereign cloud

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:

Change management for regulated industries

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.

AI governance and security

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:

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:

What Brazil adds for builders

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.

MCP across the platform

Model Context Protocol (MCP) lets external AI tools work with ServiceNow data. Brazil extends it to more of the platform:

What to check before you upgrade

ServiceNow's deprecation summary and the combined release notes for your upgrade path are the authoritative lists. These items are worth checking early:

A sensible order of work:

  1. Run the upgrade readiness pre-check.

  2. Start the Basic Authentication tracking period.

  3. Read the combined release notes for your path.

  4. Upgrade a development instance and test your customisations, especially in Change Management and integrations.

  5. Repeat on your other non-production instances.

  6. Then book the production date.

FAQs

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.

RECENT BLOGS

Flow by ServiceNow

Rizwan Z. • Nov 18, 2026 • 8 min

Flow by ServiceNow runs a service desk inside the conversation

Read full article→

Agentic AI governance is only as strong as the evidence behind it

Rizwan Z. • Nov 12, 2026 • 8 min

Agentic AI governance is only as strong as the evidence behind it

Read full article→

What is ServiceNow ITSM and why does your business need it?

Rizwan Z. • Oct 21, 2026 • 10 min

What is ServiceNow ITSM and why does your business need it?

Read full article→

Impact begins with
decisive action.

Let EnableNow help you modernize workflows, strengthen performance, and unlock measurable value across your ServiceNow platform.