Skip to content
EOL Watch
Search itemsOpen menu

GCPBreaking change

Gemini Enterprise: Gemini Notebook Enterprise web address change

Google adds go/ to the URL path of the Gemini Notebook Enterprise web app and, from 16 Nov 2026, removes lm from its hostname. Existing links redirect automatically. Action is required if your organization uses a firewall, proxy, or secure web gateway that allows access to Gemini Notebook by a specific URL path.

Breaking from , 16 Nov 2026

What breaks

From 16 Nov 2026, Google removes lm from the hostname of the Gemini Notebook Enterprise web app. For Gemini Notebook Enterprise authenticated with Google Identity, notebooklm.cloud.google.com changes to notebook.cloud.google.com. For Gemini Notebook Enterprise authenticated with Workforce Identity Federation, notebooklm.cloud.google changes to notebook.cloud.google. The other change adds go/ to the URL path of the web app. Google's dates for the go/ path change give a start of 9 Nov 2026 for "All other locations". In both cases, existing links redirect automatically. Action is required if your organization uses a firewall, proxy, or secure web gateway that allows access to Gemini Notebook by a specific URL path. A Google release note of 12 Nov 2026 states that Gemini Notebook Enterprise is renamed to Gemini Notebook for business.

What to do

If your organization uses a firewall, proxy, or secure web gateway that allows access to Gemini Notebook by a specific URL path, Google recommends that you add these URLs to your allowlist:

  1. Allowlist notebooklm.cloud.google.com/* and notebook.cloud.google.com/*.
  2. If you use Workforce Identity Federation, allowlist notebooklm.cloud.google/* and notebook.cloud.google/*.
  3. If you use Gemini Notebook within Gemini Enterprise, allowlist vertexaisearch.cloud.google.com/notebooklm/*.

Google recommends allowing entire domains (/*) so that future path changes do not require additional updates. If you do not allow /*, you must allow both /REGION and /go/REGION, where REGION is your location value. If your firewall blocks users before you update your allowlist, users can access the original URLs by removing /go from the URL and adding version=legacy. Google states that this workaround will fail when it sunsets the legacy version.

Replacement

Not stated by vendor.

Sources

Last checked against the first source in this list on .

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item