---
sourceDocument: brazil Combined Product Files
sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - brazil Combined Product Files

ft:clusterId :

    - delta3by

bundleId :

    - delta3by


---

# Combined MID Server release notes for upgrades from Yokohama to Brazil

# Combined MID Server release notes for upgrades from Yokohama to Brazil {#ariaid-title1}

Release version: Brazil  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Combined MID Server Release Notes for Upgrades from Yokohama to Brazil

This consolidated guide assists ServiceNow customers in preparing for MID Server upgrades from the Yokohama release through to Brazil.
It covers key upgrade information, new features, changes, removals, deprecations, and activation details relevant to the MID Server component.
The Brazil release itself introduces no new updates, focusing instead on cumulative improvements from prior releases.
Show full answer Show less  

## Key Upgrade Considerations

* **Java Runtime Environment (JRE) Requirements:** Starting with Yokohama, MID Server requires a minimum JRE version 17.0.10, with recommended versions varying by release (e.g., 17.0.12 for Yokohama and Zurich, 21.0.7 for Australia). The MID Server installer bundles appropriate JRE versions, but if customers install their own JRE, upgrade processes validate compatibility and warn if unsupported.
* **Windows MID Server Service Limitations:** Only one Windows MID Server service is allowed per executable path. Multiple services pointing to the same installation folder prevent MID Server startup after an upgrade.
* **Network Access Requirements:** MID Server hosts must have access to install.service-now.com to enable automatic upgrades.
* **Pre- and Post-Upgrade Tasks:** Customers should review the MID Server pre-upgrade check and manual upgrade procedures to ensure smooth transitions.

## Key Features Introduced Between Yokohama and Brazil

* **Yokohama:** Support for certificate-based authentication in External Credential Storage and Management when connecting to Azure Key Vault, enhancing security for enterprise environments.
* **Zurich:** Introduction of the ITOM Infra Services Workspace, providing a unified dashboard for real-time MID Server monitoring, alerting, automation, and diagnostics to reduce downtime.
* **Zurich:** MID Guardian Agent, an AI-driven feature offering proactive diagnostics, guided troubleshooting, automated fixes, and predictive insights to improve MID Server reliability and reduce repair times.
* **Australia:** Support for PowerShell 7 alongside backward compatibility with PowerShell 5.1, improving security and deployment flexibility for discovery tasks.
* **Australia:** Addition of a REST-based CyberArk Central Credential Provider (CCP) integration option, complementing the existing AIM SDK method for greater integration flexibility.
* **Australia:** MID Server bundled with Java Runtime Environment 21.0.7, automatically configured by the installer for improved runtime environment.

## Significant Changes to MID Server Functionality

* **Minimum JRE Version Enforcement:** JRE 17 is required starting with Yokohama, ensuring compatibility and security.
* **Improved MID Server Installation on Windows:** Installation can now be performed as a LocalSystem or non-admin user with appropriate permissions, simplifying deployment.
* **Cluster Job Assignment:** Smart Workload Manager evaluates queue size, execution time, CPU usage, and buffer size to distribute jobs across cluster MID Servers evenly, preventing overload.
* **Enhanced Logging and Diagnostics:** MID Server logs now support compressed backups on the local host with options to fetch logs to the instance; Java Flight Recorder (JFR) logs can be enabled and backed up periodically.
* **Performance Improvements:** Reduced performance degradation during heavy discovery loads through optimized script caching and worker thread management.
* **User Experience Updates:** Coral theme introduced as default for portal, web, and mobile interfaces, with a dark theme option available.
* **Storage Requirements:** MID Server hosts must have at least 100MB of free storage to accommodate security logs.

## Deprecations and Removals

* **Security Enhancements:** The 3DES encryption algorithm was permanently removed beginning with Yokohama to improve security.
* **No features were removed or deprecated in releases after Yokohama through Brazil.**

## Activation and Additional Information

* MID Server is an AI Platform feature active by default from Yokohama onward.
* There are no new browser, localization, or accessibility requirements introduced between Yokohama and Brazil.

## Practical Implications for ServiceNow Customers

When upgrading MID Servers, ensure your environment meets the minimum JRE version requirement and verify JRE compatibility if using custom installations. Maintain only one Windows MID Server service per installation folder to avoid startup issues. Take advantage of new security enhancements like certificate-based authentication and REST-based CyberArk integration for better credential management. Utilize the ITOM Infra Services Workspace and MID Guardian Agent for improved monitoring and faster issue resolution. The smart workload manager will help optimize cluster performance, while improved logging aids troubleshooting. Finally, ensure sufficient storage for security logs and consider the updated UI themes for enhanced user experiences.  
Consolidated page of all release notes for MID Server from Yokohama to Brazil.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family MID Server release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Brazil.  
Tip:  
If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

## Important information for upgrading MID Server to Brazil

Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed.  
{#dfrn3-midserver-summary__entry__2}

| Release | Release notes |
|-|-|
| Yokohama | Upgrade information :   For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=yokohama&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US). Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=yokohama&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US): Describes how to upgrade your MID Servers manually. |
| Zurich | Upgrade information :   For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US). Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=zurich&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US): Describes how to upgrade your MID Servers manually. |
| Australia | Upgrade information :   For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 21.0.7. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=australia&ft:locale=en-US). Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=australia&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=australia&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=australia&ft:locale=en-US): Describes how to upgrade your MID Servers manually. |
| Brazil | No updates for this release. |
[ ]

## New features

Between your current release family and Brazil, new features were introduced for MID Server.  
{#dfrn3-midserver-summary__entry__12}

| Release | Release notes |
|-|-|
| Yokohama | [External Credential Storage and Management supports certificate-based authentication for Azure Key Vault](https://www.servicenow.com/docs/access?context=mid-azure-key-vault-integration&family=yokohama&ft:locale=en-US) :   The External Credential Storage and Management added support for certificate-based authentication when connecting to Azure Key Vault. This provides a more secure and flexible way to authenticate, especially for enterprise environments that prefer certificate credentials over client secrets. |
| Zurich | [ITOM Infra Services Workspace](https://www.servicenow.com/docs/access?context=itom-infra-srv-wrksp-mid&family=zurich&ft:locale=en-US) :   The ITOM Infra Services Workspace provides a concise overview of MID Server activity. The dashboard integrates several previously disparate tables so that issues can be monitored and resolved. The workspace provides real-time monitoring, proactive alerts, automation of common tasks, and centralized diagnostics to reduce downtime and support tickets. [MID Guardian Agent](https://www.servicenow.com/docs/access?context=mid-guardian&family=zurich&ft:locale=en-US) :   The MID Guardian Agent is an advanced AI feature within the MID Server ecosystem/ITOM Infra Services workspace, designed to proactively assist users in diagnosing and resolving issues related to configuration, connectivity, upgrades, and operations. By intelligently analyzing logs, signals, and runtime behaviors, it offers guided troubleshooting steps, automated fixes, and predictive insights. This significantly reduces Mean Time to Repair (MTTR) and enhances the reliability and operational efficiency of the MID server. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Changes

Between your current release family and Brazil, some changes were made to existing MID Server features.  
{#dfrn3-midserver-summary__entry__22}

| Release | Release notes |
|-|-|
| Yokohama | [MID Server supports and requires a minimum JRE version 17](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=yokohama&ft:locale=en-US) :   The MID Server is compiled using Java 17 and is incompatible with any Java version below 17 for runtime execution. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. See the [MID Server JRE Minimum Version Requirement Update to JRE 17 Starting from Yokohama Release \[KB1704368\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704368) article in the Now Support Knowledge Base for information about required procedures before upgrading the instance. [Improvements when manually installing a MID Server on Windows](https://www.servicenow.com/docs/access?context=mid-server-install-prereqs&family=yokohama&ft:locale=en-US) :   The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions. |
| Zurich | [MID Server security logs require 100MB of storage](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US) :   To store the security logs, MID Servers must be installed on a host with at least 100MB of storage capacity. [Smart Workload Manager in clusters](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&family=zurich&ft:locale=en-US) :   MID Servers in a cluster now assign jobs based on the true load, using a variety of criteria. The smart workload manager continuously evaluates the queue size, execution time, CPU usage, and buffer size. The manager then assigns tasks to ensure that no server is overloaded. [Enhancements to MID Server logging and JFR](https://www.servicenow.com/docs/access?context=r_MIDServerTroubleshooting&family=zurich&ft:locale=en-US) :   MID Server logging has been improved with log backups that are preserved in a compressed format on local host with option to fetch to the instance. You can enable JFR logs every four hours and backup JFR files for a set time. [MID Server has improved performance during heavy discovery load](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US) :   MID Servers no longer have performance degradation due to script include cache misses when using large amounts of worker threads. Coral theme :   Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. |
| Australia | [MID Server security logs require 100MB of storage](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US) :   To store the security logs, MID Servers must be installed on a host with at least 100MB of storage capacity. [MID Server supports PowerShell 7 for Discovery](https://www.servicenow.com/docs/access?context=powershell-remoting&family=australia&ft:locale=en-US) :   MID Server now supports PowerShell 7, while maintaining backward compatibility with PowerShell 5.1. This update enhances security, accelerates onboarding, and reduces deployment blockers through improved runtime detection and comprehensive test coverage. [Configure the MID Server for CyberArk CCP](https://www.servicenow.com/docs/access?context=t_ConfigureTheMIDServerForCyberArkCCP&family=australia&ft:locale=en-US) :   MID Server's CyberArk integration adds a REST-based CCP option alongside the existing AIM SDK method, providing flexible, interchangeable integration choices. This additional option can reduce dependency overhead and enables you to choose between the AIM SDK and REST-based approaches according to your requirements. [Smart Workload Manager in clusters](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&family=australia&ft:locale=en-US) :   MID Servers in a cluster now assign jobs based on the true load, using a variety of criteria. The smart workload manager continuously evaluates the queue size, execution time, CPU usage, and buffer size. The manager then assigns tasks to ensure that no server is overloaded. [MID Server is bundled with Java Runtime Environment 21](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US) :   MID Server comes bundled with Java Runtime Environment version 21.0.7 and requires a minimum JRE version 17.0.10. The installer automatically configures Java 21.0.7 to run in your environment. If you have installed your own JRE, see the Important information for upgrading MID Server to Australia section to ensure your JRE is compatible. |
| Brazil | No updates for this release. |
[ ]

## Removed

Between your current release family and Brazil, some MID Server features or functionality were removed.  
{#dfrn3-midserver-summary__entry__32}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Deprecations

Between your current release family and Brazil, some MID Server features or functionality were deprecated.  
{#dfrn3-midserver-summary__entry__42}

| Release | Release notes |
|-|-|
| Yokohama | * When upgrading to the Yokohama release, 3DES will be permanently removed from MID Server to improve security. See [++3DES deprecation in SSH from Xanadu \[KB1644950\]++](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644950) for more information. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Activation information

Review information on how to activate MID Server.  
{#dfrn3-midserver-summary__entry__52}

| Release | Release notes |
|-|-|
| Yokohama | Activation information :   MID Server is a ServiceNow AI Platform feature that is active by default. |
| Zurich | Activation information :   MID Server is a ServiceNow AI Platform feature that is active by default. |
| Australia | Activation information :   MID Server is a ServiceNow AI Platform feature that is active by default. |
| Brazil | No updates for this release. |
[ ]

## Additional requirements

If any additional requirements were introduced or changed for MID Server we have noted them here.  
{#dfrn3-midserver-summary__entry__62}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Browser requirements

If any specific browser requirements were introduced or changed for MID Server we have noted them here.  
{#dfrn3-midserver-summary__entry__72}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Accessibility information

Review details on accessibility information for MID Server, such as specific requirements or compliance levels.  
{#dfrn3-midserver-summary__entry__82}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Localization information

If there are specific localization considerations for MID Server we have noted them here.  
{#dfrn3-midserver-summary__entry__92}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Highlight information

If there are specific highlight considerations for MID Server we have noted them here.  
{#dfrn3-midserver-summary__entry__102}

| Release | Release notes |
|-|-|
| Yokohama | * MID Server supports and requires a minimum JRE version 17. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. * The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=yokohama&ft:locale=en-US) for more information. |
| Zurich | * MID Server smart workload manager continuously evaluates load and assigns jobs in a cluster to ensure that no server is overloaded. * MID Server logging has been improved with log backups that are preserved in a compressed format on a local host with an option to fetch to the instance. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=zurich&ft:locale=en-US) for more information. |
| Australia | * MID Server comes bundled with Java Runtime Environment version 21.0.7 and requires a minimum JRE version 17.0.10. * MID Server's CyberArk integration adds a REST-based CCP option alongside the existing AIM SDK method, providing flexible, interchangeable integration choices. * MID Server smart workload manager continuously evaluates load and assigns jobs in a cluster to ensure that no server is overloaded. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=australia&ft:locale=en-US) for more information. |
| Brazil | No updates for this release. |
[ ]