The Brazil Release This is the ServiceNow release family that, in ITOM and CMDB, moves the legacy experience platform to unified workspaces and opens IT operations to artificial intelligence clients via the Model Context Protocol. Early availability occurred on September 24, 2026, and general availability is listed as the fourth quarter of 2026 in the official release notes.
For those operating ServiceNow in a corporate environment, the relevant reading of the Brazil Release is not the list of new features. It's the list of deprecations and changes to default behavior, because these are what require validation before any production upgrade. In CMDB, the release consolidates two workspaces into one and prepares three classic experiences for future deprecation. In ITOM, it expands Discovery coverage, replaces the classic Dynatrace connector, and introduces a dedicated MCP console.
This article organizes what has changed in each area, separates what is new in the Brazil Release from what has simply become standard, and concludes with the sub-production validation checklist that 4MATT applies to upgrade projects. The basis is the public ServiceNow documentation; the availability of each feature depends on the instance version, plugins, licensing, and ServiceNow Store applications.
What changes in CMDB with the Brazil Release?
The CMDB changes focus on three areas: interface consolidation, identification of configuration items, and permissions model. None of them are cosmetic, and two require action before the upgrade.
Service Graph Workspace is deprecated and absorbed by CMDB Workspace.
Starting with this release, ServiceNow has deprecated the Service Graph Workspace and transferred its capabilities to the CMDB Workspace. In practice, connectors, ingestion, and data health are now managed in a single interface. The operational consequence is straightforward: favorites, navigation modules, and runbooks that point to the Service Graph Workspace need to be updated, and any customization built on top of that workspace needs to be revalidated.
The release already includes a CMDB Workspace installation, but the documentation recommends downloading the latest version of the application from the ServiceNow Store to access current features.
Dynamic IRE becomes the default in new instances.
Here it's important to distinguish between new features and a change in the standard. Dynamic IRE wasn't born in the Brazil Release: it was introduced in the previous cycle and retroactively ported, and has been enabled by default in newly initialized instances since Zurich Patch 11. What the Brazil Release notes is that zBooted instances already come with Dynamic IRE active, while updated instances using Static IRE can migrate optionally.
Two caveats weigh on the decision. The first is scope: Dynamic IRE applies to the Hardware class and its descendants, and outside of them, Static IRE remains active. The second is methodological: ServiceNow recommends first running the simulation mode on a non-production instance, comparing the two engines on the same payloads, and evaluating the parity score before making any decision. Those evaluating the migration can find details of the engine, parity score, and five-step plan in the article about it. Healthy CMDB with Success Advisor and Dynamic IRE.
ServiceNow Otto will now name its AI-assisted experiences.
The CMDB release notes indicate that the Now Assist and Moveworks experiences will now be called ServiceNow Otto. The first item renamed in this scope is the Duplicate CI Remediator, which analyzes duplicate configuration items and recommends merging them. The change is in nomenclature and positioning, not capability, but it affects internal documentation, training materials, and any procedures that mention the old name.
Permissions: the itil role exits app_service_admin
The Brazil Release introduces a new CMDB role plugin and reorganizes access to Service Instance records. The app_service_owner role now includes the app_service_user role, allowing the creation, reading, updating, and deletion of these records without granting the broader itil role. Conversely, the sn_cmdb_editor and app_service_user roles replace itil within app_service_admin. Note the side effect: viewing items related to a configuration item, such as linked incidents and changes, still requires the itil role.
What goes into the depreciation queue?
| Item | Situation in Brazil Release | Recommended path |
|---|---|---|
| Service Graph Workspace | Deprecated in this release | CMDB Workspace |
| CMDB Baseline | Prepared for future deprecation. It is hidden and no longer activated in new instances, but remains supported. | Unified Map |
| Dependency Views and CMDB Relationship Editor | Prepared for future depreciation. | Unified Map |
| Database view sn_getwell_cis_processed_via_ire | Depreciated | Review reports, indicators, and integrations that reference it. |
| findOrCreateRelationshipType function | Deprecated. No longer creates relationship types between configuration items and returns an error when the type does not exist. | Replace with findCIRelationshipType in custom scripts |
The last line in this table is the one that generates the most post-upgrade incidents because it affects custom code in Discovery patterns, sensors, and post-processing scripts. Auditing this point is not optional.
What changes in ITOM with the Brazil Release?
In ITOM, the release acts in two simultaneous directions: it expands Discovery's coverage and tolerance in challenging environments, and increases the transparency of decisions made by AI mechanisms regarding alerts.
Discovery: PowerShell 7, credentialless scanning, and consolidated workspace.
Discovery feeds the CMDB with the configuration items that all other capabilities consume, as explained in the 4MATT guide on... ServiceNow Discovery and CMDB. The changes implemented by Brazil Release address precisely the areas where data collection typically fails.
- PowerShell 7. Two MID Server configuration parameters now allow you to prefer PowerShell 7 over PowerShell 5, both on the MID Server and on the target Windows hosts, for File-based Discovery and Windows ADME.
- Sweep without credentials expanded. Credentialless discovery then checks UDP ports and infers the host's operating system when it cannot confirm an exact match. Both options are disabled by default and are enabled by MID Server properties: mid.discovery.credentialless.include_udp_scan and mid.discovery.credentialless.include_os_scan_guess.
- Performance in software discovery. The default value of the com.glide.ensurer.partitions.cmdb_ci_spkg property automatically increases from 64 to 128 upon upgrade, which improves software discovery on instances with a high volume of installations and without Software Asset Management installed.
- Discovery Admin Workspace. It centralizes certificate discovery configuration, Kubernetes resource visibility in a dedicated explorer, and Shazam insights within the IP inventory.
- Performance snapshots. Daily captures are now recorded for slow pattern tables, providing a historical basis for diagnosing degradation in Discovery patterns.
Event Management and AIOps: Dynatrace Grail and decision traceability
The most significant change for those already integrating observability is the connector replacement: the new Dynatrace Grail connector creates ServiceNow alerts from problem events, already including the root cause entity, the affected configuration items, the corresponding severity, and the current lifecycle state of the problem. This connector replaces the classic Dynatrace event integration., This makes the migration assessment mandatory for those using the old integration.
In the area of automation governance, the Brazil Release provides visibility into the execution of agentic workflows, with accessible state, steps, and reasoning, and allows human intervention when necessary. Automatic alert closure exposes decisions, reasoning, and supporting evidence, including execution traces. This is the difference between trusting the result and being able to audit it, and it's what enables automation in a regulated environment. The configuration of connectors such as vCenter, NagiosXI, SolarWinds, SCOM, and Zabbix becomes possible conversationally through ServiceNow Otto.
Anyone structuring indicators for this area can find the breakdown of correlation, noise, and resolution time in the article about... AIOps and ITOM applied to MTTR reduction.
Health Log Analytics, Synthetic Monitoring and Agent Client Collector
| Capability | What changes | Operational effect |
|---|---|---|
| Health Log Analytics | Criteria based on anomaly persistence and greater visibility into the Smart Parser Gen AI processing, with a complete parsing workflow and alert generation. | Less transient peak alerts during predictable windows, such as nighttime batch processing. |
| Synthetic Monitoring | A single HTTP endpoint or discovered API can be associated with multiple application services, preserving the relationships in the CMDB. | End of duplicate synthetic verification and correct representation of shared dependency. |
| Synthetic Monitoring | Scheduled routine for cleaning the ECC Queue and HTTP checks of the MID Server that report a status response in the presence of valid error codes. | Queue under control and fewer false negatives regarding availability. |
| Agent Client Collector | Support for non-persistent Windows VDI, automatic categorization of software and browser extensions, filter rules for SAM, license key discovery, and maintenance token protection against unauthorized uninstallation. | More comprehensive inventory in ephemeral environments and less noise in SAM inventory. |
The Synthetic Monitoring item deserves highlighting because it solves a modeling problem, not a monitoring problem. An authentication API used by a portal, application, and partner platform no longer requires three independent verifications and is instead represented as the shared dependency that it truly is.
ITOM MCP Server Console: the new Brazil Release interface
The ITOM MCP Server Console allows agents to retrieve ITOM data and perform actions through an MCP-enabled AI client, in natural language, outside of the ServiceNow interface. It is distributed through the ServiceNow Store and brings together AIOps, Service Reliability Management, and LEAP tools.
The documented capabilities include assigning, closing, reopening, acknowledging, and annotating alerts, including in groups when the request applies to multiple related alerts; assessing the reliability status of a configuration item, its topology, and the impact of incidents, with the creation and monitoring of service level objectives; requesting remediation suggestions built upon existing workflows and knowledge articles; and configuring log ingestion integrations without MID Server for Health Log Analytics, with token creation, activation, renaming, and rotation via prompt.
What MCP doesn't do is replace fundamentals. The remediation suggestion depends on the workflows and knowledge base that the organization already maintains, and the impact assessment depends on a correct CMDB topology aligned with... CSDM. An incomplete topology produces incomplete analysis, whether queried by a traditional screen or an AI agent. For enterprise adoption, the minimum definition involves client authentication and authorization, segregation between query and execution permissions, auditing of actions, and human approval for critical operations.
What to validate in sub-production before moving to production.
This is the checklist that 4MATT uses when evaluating an upgrade to the Brazil Release in mature ITOM and CMDB environments. Each line corresponds to a change in standard behavior or a deprecation recorded in the documentation.
| Front | What has changed? | Validation action |
|---|---|---|
| Identification engine | Standard Dynamic IRE on zBooted instances; optional migration on upgraded instances. | Run the simulation mode with real Discovery and Service Graph Connector payloads, evaluate the parity score, and confirm the hardware scope before committing. |
| Workspaces | Service Graph Workspace has been deprecated and merged into CMDB Workspace. | Update favorites, navigation modules, and runbooks; revalidate customizations from the old workspace. |
| Custom scripts | findOrCreateRelationshipType stops creating relationship types. | Audit Discovery patterns, sensors, and post-processing scripts; replace with findCIRelationshipType |
| Reports and integrations | Removal of the view sn_getwell_cis_processed_via_ire | Check reports, Performance Analytics indicators, and integrations that reference it. |
| Access control | app_service_owner contains app_service_user; itil removed from app_service_admin | Test permissions on Service Instance for service owners without the ITIL role and confirm what still requires ITIL. |
| Observability | The Dynatrace Grail connector replaces the classic event integration. | Plan the connector migration and revalidate correlation and alert rules. |
| Classic experiences | CMDB Baseline, Dependency Views, and CMDB Relationship Editor are in the deprecation queue. | Map current usage and plan the transition to Unified Map. |
It's important to note the scope: some of the capabilities described are achieved through ServiceNow Store applications and specific availability programs, not through family upgrades. Each feature needs to be confirmed according to the instance version, installed plugins, and contracted licensing.
From observability to agent-assisted operations
Reading both aspects together, the direction of the release becomes clear. In CMDB, the platform concentrates governance, ingestion, and data health in a single workspace and retires legacy graphical experiences. In ITOM, it expands data collection where it usually fails, makes AI decisions based on alerts auditable, and opens an agent interface to operational capabilities.
The order of causality hasn't changed. The journey to more autonomous operations doesn't begin with the activation of agents, but rather with reliable visibility into components, consistent service modeling, and defined data responsibility. The MCP console expands the reach of those who already have this foundation and equally expands the reach of those who don't. Organizations that address the CMDB implementation in ServiceNow As a prerequisite, and not as a parallel step, they arrive at Brazil Release able to use what it offers that's new.
4MATT is a ServiceNow Elite Partner in Brazil, with over 180 certified specialists, and operates in maturity assessment., structuring of CMDB and ITOM services, with data architecture as the starting point for each project.
Frequently asked questions about the Brazil Release in ITOM and CMDB
When will the Brazil Release be available?
Early availability occurred on September 24, 2026. Official release notes list general availability as the fourth quarter of 2026, without an exact date published at the time of writing. Secondary sources differ on the day; it is recommended to confirm with your ServiceNow account team before formally planning the upgrade. The naming history and release schedule are compiled in the 4MATT article on the subject. ServiceNow Release Brazil.
Is Dynamic IRE a new feature from Brazil Release?
No. Dynamic IRE was introduced in a previous cycle and has been enabled by default on newly initialized instances since Zurich Patch 11. The release indicates that zBooted instances already come with it active and that instances updated in Static IRE can migrate optionally. The scope remains the Hardware class and its descendants.
Do I need to migrate from Static IRE to Dynamic IRE during the upgrade?
It is not mandatory in updated instances. The documented recommendation is to test beforehand in a simulation, on a non-production instance, with both engines processing the same payloads, and evaluate the parity score before deciding. In mature Static IRE implementations, a high parity score is expected, and it is possible to revert to Static IRE after adoption.
What happens to those who use the Service Graph Workspace?
The Service Graph Workspace has been deprecated and its capabilities have been incorporated into the CMDB Workspace. Favorites, navigation modules, and operational procedures need to point to the CMDB Workspace, and customizations built on top of the old workspace need to be revalidated.
Does Brazil Release replace monitoring tools like Dynatrace and Zabbix?
No. ITOM integrates information from different observability tools and delivers correlation, service context, and operational workflow based on them. What has changed is the integration path with Dynatrace: the Grail connector replaces the classic event integration, which requires migration planning.
Is a structured CMDB necessary to use Brazil Release's AI capabilities?
The quality of the CMDB determines the accuracy of event correlation, impact analysis, and remediation suggestions, including when consulted by an MCP client. A duplicate or unattributed configuration item produces incorrect routing and conclusions that no one can audit, regardless of the interface used to consult it.
Are all features available immediately after the upgrade?
No. Some of them depend on plugins, ServiceNow Store applications, activation, licensing, and specific availability conditions. The ITOM MCP Server Console, for example, is distributed through the Store and needs to be requested.
Official sources consulted: release notes from the Brazil family, Discovery release notes, Service Mapping release notes and release notes on the platform's capabilities, which compile the CMDB notes. Independent editorial analysis by 4MATT. The actual availability of each capability must be verified in the corresponding documentation and validated at the instance itself.