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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - australia Combined Product Files

ft:clusterId :

    - delta3ax

bundleId :

    - delta3ax


---

# Combined Service Exchange release notes for upgrades from Xanadu to Australia

# Combined Service Exchange release notes for upgrades from Xanadu to Australia {#ariaid-title1}

Release version: Australia  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Service Exchange Release Notes for Upgrades from Xanadu to Australia

This consolidated guide assists ServiceNow customers in preparing for and executing upgrades of Service Exchange from the Xanadu release family through to Australia.
It combines key release notes, upgrade requirements, new features, and important compatibility information to ensure a smooth transition and continuous interoperability between provider and consumer instances.
Show full answer Show less  

## Upgrade Preparation and Compatibility

* **Legacy Migration:** Service Exchange (Legacy) versions are not supported for direct upgrade to Xanadu or later releases. Customers must use migration utilities documented in KB1499823 to migrate configuration data before upgrading.
* **Version 1.x.x Upgrades:** Customers upgrading from Service Exchange 1.x.x should follow the step-by-step migration process in KB1700387 to move to version 2.x.x releases.
* **Mismatched Version Support:** Starting with the Xanadu release, providers and consumers can operate different versions of Service Exchange simultaneously, allowing providers to adopt new features independently without disrupting consumers. However, new entitlements cannot be activated until both sides upgrade to compatible versions.
* **Simultaneous Upgrades:** When using Service Exchange for both Providers and Consumers in one instance, upgrading both applications to the same version concurrently is mandatory to maintain compatibility.
* **Post-Upgrade Tasks:** For certain releases like Yokohama and Zurich, customers must perform a "Repair" action after upgrading to install new Deny ACLs, especially if upgrading the Sales Customer Relationship Management plug-in beforehand.

## New Features Introduced Between Xanadu and Australia

* **Mismatched Version Support:** Allows providers and consumers to run different Service Exchange versions without interrupting data exchange.
* **Configuration Revisions:** Providers can deploy updated entitlements to consumers selectively, enabling consumers to continue using older revisions or adopt new functionality as needed.
* **Consumer Pre-Flows:** Consumers can attach flows to remote record producers to trigger consumer-specific processes (e.g., approvals) before synchronizing tasks with providers.
* **Sales Customer Relationship Management Integration:** Providers can publish Sales CRM offerings as remote record producers, enabling consumers to order these directly from their service catalogs.

## Deprecations and Removed Features

* The Service Exchange (Legacy) applications for both Providers and Consumers are deprecated and no longer supported or available for new activation. Customers should migrate to the latest Service Exchange applications as outlined in KB1499823.
* No other features were removed or deprecated between Xanadu and Australia.

## Application Installation and Activation

* Service Exchange is available for installation through the ServiceNow Store across all relevant releases (Xanadu, Yokohama, Zurich).
* Customers should request installation from the ServiceNow Store and can review cumulative release notes and version history there.

## Additional Technical Information

* The Service Exchange Global Script Include is automatically installed or updated during app installation on platform versions including Washington DC Patch 9, Xanadu Patch 4, Yokohama, Zurich, and Australia.
* No changes to browser requirements, localization, or accessibility (other than the introduction of a dark theme option in Zurich) affect Service Exchange between Xanadu and Australia.

## Practical Benefits for ServiceNow Customers

* Upgrading to newer Service Exchange versions enables flexible version management between providers and consumers, reducing coordination overhead.
* Enhanced entitlement management and consumer pre-flows improve control over synchronized data and workflows.
* Integration with Sales Customer Relationship Management streamlines ordering and fulfillment of catalog offerings.
* Clear migration paths and upgrade guidelines minimize disruption and ensure continuity of service.  
Consolidated page of all release notes for Service Exchange from Xanadu to Australia.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family Service Exchange release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Australia.  
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 Service Exchange to Australia

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

| Release | Release notes |
|-|-|
| Xanadu | * Service Exchange 2.x.x that is being released with the Xanadu release does not support migration of the Service Exchange (Legacy) versions. If you are using a Service Exchange (Legacy) version, before you upgrade to the Xanadu release, you must follow instructions in the [Service Exchange for Providers (Legacy) - Migration Utility (KB1499823)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * If you are upgrading from version 1.x.x of Service Exchange, follow the steps listed in [Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release - KB1700387)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) to migrate your Service Exchange applications. * Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to the Xanadu release. Older active entitlements will continue to work but new ones cannot be activated. |
| Yokohama | Upgrade information : * When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility. * The Service Exchange Global Script Include is automatically installed or updated when you install the Service Exchange application on the following platform versions: * Washington DC Patch 9 * Xanadu Patch 4 * Yokohama * Service Exchange 2.x.x, which was first released with the Xanadu release, does not support migration of Service Exchange (Legacy) versions. If you are using a Service Exchange (Legacy) version, before you upgrade to the Yokohama release, you must follow instructions in the [Service Exchange for Providers (Legacy) - Migration Utility \[KB1499823\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * If you are upgrading from Service Exchange version 1.x.x, follow the steps in [Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release) \[KB1700387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) to migrate your Service Exchange applications. * Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements will continue to work but new ones cannot be activated. * If you upgrade to Service Exchange version 2.0.55 with Sales Customer Relationship Management plug-in version 1.0.4 before upgrading the platform to the Yokohama release, the new Deny ACLs will not be installed. To ensure the Deny ACLs get installed, after upgrading to Yokohama, you must click Repair to reinstall the Service Exchange application. |
| Zurich | Upgrade information : * Service Exchange version 2.x.x: Which was first released with the Xanadu release, doesn't support migration of Service Exchange (Legacy) versions. Service Exchange (Legacy) version: Before you upgrade to the Zurich release, follow instructions in the [Service Bridge for Providers (Legacy) - Migration Utility \[KB1499823\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * Service Exchange version 1.x.x: When upgrading, follow the steps in the [Upgrade Guide - Service Bridge for Providers and Consumers application (v2.x.x release) \[KB1700387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) article in the Now Support Knowledge Base to migrate your Service Exchange applications. * Service Exchange version 2.x.x: Due to the introduction of mismatched version support, new entitlements can't be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements continue to work but new ones can't be activated. * When you upgrade to Service Exchange version 2.0.55 with Sales Customer Relationship Management plug-in version 1.0.4, before upgrading the platform to the Zurich release, new Deny ACLs aren't installed. To ensure the Deny ACLs get installed, after upgrading to Zurich, select Repair to reinstall the Service Exchange application. * When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility. * When you install the Service Exchange application, the Service Exchange Global Script Include is automatically installed or updated on the following platform versions: * Washington DC patch 9 * Xanadu patch 4 * Yokohama * Zurich |
| Australia | No updates for this release. |
[ ]

## New features

Between your current release family and Australia, new features were introduced for Service Exchange.  
{#dfrn3-serviceexchange-summary__entry__12}

| Release | Release notes |
|-|-|
| Xanadu | [Service Exchange mismatched version support](https://www.servicenow.com/docs/access?context=service-bridge-v2-mismatch-version&family=xanadu&ft:locale=en-US) :   Providers and consumers can run different versions of the Service Exchange applications without affecting their ability to exchange data. Providers can adopt new features without coordinating their application upgrades with their consumers. [Configuration revisions](https://www.servicenow.com/docs/access?context=service-bridge-v2-config-revision&family=xanadu&ft:locale=en-US) :   Providers can develop and deploy new versions or revisions of entitlements with updated functionality to compatible consumers without affecting consumers who have not updated their application. Consumers can therefore use older revisions of entitlements including remote task definitions, remote record producers, and foundation data sync offerings while deploying new revisions. [Consumer pre-flows](https://www.servicenow.com/docs/access?context=service-bridge-v2-conf-consumer-flow&family=xanadu&ft:locale=en-US) :   Consumers can control data synchronization with their providers by associating a flow with a Service Exchange remote record producer and run consumer-defined processes, such as approvals, before a task is synchronized to their provider. [Integration with Sales Customer Relationship Management](https://www.servicenow.com/docs/access?context=service-bridge-v2-omt-intg&family=xanadu&ft:locale=en-US) :   Providers can enable customers to quickly order entitled Sales Customer Relationship Management product offerings from their service catalog by publishing them as remote record producers on consumer instances. |
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
[ ]

## Changes

Between your current release family and Australia, some changes were made to existing Service Exchange features.  
{#dfrn3-serviceexchange-summary__entry__22}

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

## Removed

Between your current release family and Australia, some Service Exchange features or functionality were removed.  
{#dfrn3-serviceexchange-summary__entry__32}

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

## Deprecations

Between your current release family and Australia, some Service Exchange features or functionality were deprecated.  
{#dfrn3-serviceexchange-summary__entry__42}

| Release | Release notes |
|-|-|
| Xanadu | * Service Exchange (legacy) application is now deprecated and no longer supported or available for new activation. The Service Exchange for Consumers application provides the latest experience for this functionality. * Service Exchange for Providers (legacy) application is now deprecated and no longer supported or available for new activation. The Service Exchange for Providers application provides the latest experience for this functionality. See [KB1499823](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) for details on migrating from the legacy version. |
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
[ ]

## Activation information

Review information on how to activate Service Exchange.  
{#dfrn3-serviceexchange-summary__entry__52}

| Release | Release notes |
|-|-|
| Xanadu | Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=xanadu&ft:locale=en-US). |
| Yokohama | Activation information :   Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Service Exchange is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. |
| Zurich | Activation information :   Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: Service Exchange is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. |
| Australia | No updates for this release. |
[ ]

## Additional requirements

If any additional requirements were introduced or changed for Service Exchange we have noted them here.  
{#dfrn3-serviceexchange-summary__entry__62}

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

## Browser requirements

If any specific browser requirements were introduced or changed for Service Exchange we have noted them here.  
{#dfrn3-serviceexchange-summary__entry__72}

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

## Accessibility information

Review details on accessibility information for Service Exchange, such as specific requirements or compliance levels.  
{#dfrn3-serviceexchange-summary__entry__82}

| Release | Release notes |
|-|-|
| Xanadu | No updates for this release. |
| Yokohama | No updates for this release. |
| Zurich | Accessibility information : Dark theme :   The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. |
| Australia | No updates for this release. |
[ ]

## Localization information

If there are specific localization considerations for Service Exchange we have noted them here.  
{#dfrn3-serviceexchange-summary__entry__92}

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

## Highlight information

If there are specific highlight considerations for Service Exchange we have noted them here.  
{#dfrn3-serviceexchange-summary__entry__102}

| Release | Release notes |
|-|-|
| Xanadu | * Enable providers to adopt new features and provide uninterrupted service to their consumers who have not upgraded. * Assess entitlements for compatibility before syncing them to consumers. * Enable consumers to run specific processes such as approvals before synchronizing tasks with their providers. * Support automated synchronization of configuration data between provider and consumer instances. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=xanadu&ft:locale=en-US) for more information. |
| Yokohama | * Providers can now include client and UI policy scripts in remote record producers, which consumers can review and approve. * Providers can now copy local catalog items to Service Exchange as remote record producers either in bulk or individually. * Providers can simplify and streamline choice-based transform mapping with ServiceNow Now Assist. * Consumers can now add variables to remote record producers for use in consumer pre-flows. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=yokohama&ft:locale=en-US) for more information. |
| Zurich | * Streamline data replication from provider to consumer instances with foundation data sync. * Enable seamless collaboration between provider and consumer with enhanced journal entry support. * Enable consumer users to access linked resources in the provider instance using magic links. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=zurich&ft:locale=en-US) for more information. |
| Australia | No updates for this release. |
[ ]


