We’re excited to announce that Neo4j Aura will fully transition to our new console experience on the console-preview.neo4j.io domain, on March 17th 2025. This migration will enhance your experience and streamline access to instance and operations management along with graph tools. However, it’s important to review this message and take action if required to ensure a smooth transition.

Whats changing?

• New Console URL: The new console will remain on console-preview.neo4j.io

• New IP Address: A new IP address (34.110.249.124) will be associated with the console-preview.neo4j.io domain 

• Classic Console: The Classic console will be available on console-classic.neo4j.io and console.neo4j.io

• Classic console URL: The Classic console will be on console-classic.neo4j.io and use the existing console IP address (35.241.228.234)

We are planning to transition all customers to the new experience on the console.neo4j.io domain over the next few months. You will receive additional communications with more details ahead of the migration. If there are issues preventing you from using the new console, please reach out to us here.

Actions Required

1. Update SSO Configuration

If you use Single Sign-On (SSO) with Neo4j Aura, please check your Identity Provider (IdP) settings to ensure continued access.

Instructions for Popular IdPs:

Okta

Update the redirect URI (if required) in your Okta admin console.

If your Okta Neo4j application is configured as a single page application, add the following uris to the Sign-in redirect URI’s section in Okta. Replace <sso_config_id> with the ID of your SSO config in Aura:

• https://console-preview.neo4j.io/tools/query?idp_id=<sso_config_id>&auth_flow_step=redirect_uri

• https://console.neo4j.io/tools/query?idp_id=<sso_config_id>&auth_flow_step=redirect_uri

Azure

Update the console URI (if required) in your Azure AD Enterprise Application settings.

If your Azure Entra application has the Single page application platform configured under the Authentication section, then add the following urls to the Single page application redirect URIs section.

Replace <sso_config_id> with the ID of your sso config in Aura:

• https://console-preview.neo4j.io/tools/query?idp_id=<sso_config_id>&auth_flow_step=redirect_uri

• https://console.neo4j.io/tools/query?idp_id=<sso_config_id>&auth_flow_step=redirect_uri

Other identity providers can also be configured for Neo4j Aura. Please reach out to your internal IT teams for guidance on the required steps to update redirect URIs.

2. Allowlist the New IP Address if required [Future guidance]

If your organization restricts outbound traffic by IP, please add the future console IP address (34.110.249.124) to your allowlist. Details of all our IP addresses are available here. Use this guide to determine fixed IP address to provision in Firewall for an AuraDB Virtual Dedicated Cloud instance.

3. Make use of the Aura API and CLI for programmatic access to management functionality

Use the Aura API by creating credentials with the Aura Console. Ensure there are no restrictions on the IP address for api.neo4j.io (34.36.216.162) and then try making API requests with our API specification. API keys are scoped to your console user role. 

Get started with our CLI.

What Happens If You Don’t Make These Changes?

Failure to update your SSO configurations could result in a lack of access to tools/instance level SSO via the new console experience starting 17th March 2025.

All existing surfaces using SSO (workspace, browser, bloom) continue to function as normal, and these can be accessed via the classic console.

If you have any questions or need support, please reach out to our support team at support@neo4j.com.

FAQ:

What happens if I want to go back to the classic console?

You can do this by clicking on the menu bar at the top right and selecting 'Classic experience' within the experience menu item

Which products/tiers are included in the rollout?

AuraDB Free, AuraDB Professional, AuraDS Professional and AuraDB Business Critical tiers already default to the new console at console-preview.neo4j.io. With this rollout to AuraDB Virtual Dedicated Cloud and AuraDS Enterprise, all product tiers will move to the new console at console-preview.neo4j.io.

 

Can I still access Browser by visiting the instance connection URL /browser or browser.neo4j.io?

Yes, but we will not link to this via the new console.

 

Can I still access Workspace?

Yes, while the classic console is available, Workspace can continue to be accessed at workspace-preview.neo4j.io.

Follow these instructions to migrate any Workspace saved Cypher and perspectives to the new console.

 

Can I still access graph tools like Browser and Bloom via Private Link after the console change?

All existing methods of privately connecting to tools will continue to be available. 

 

Why is the new console available on console-preview.neo4j.io?

To ensure support of all existing workflows using Neo4j Aura, we will continue to use the console-preview domain for the new experience. The new console is generally available (GA) and fully supported in line with all other Neo4j features.

 

Are there any changes to neo4j-admin push-to-cloud or neo4j-admin database import?

Neo4j-admin push-to-cloud or neo4j-admin database import will continue to function. A new version of neo4-admin will be released in March (2025.03) and we strongly recommend that customers update to the latest version in preparation for the migration to console.neo4j.io in H2 2025.