Free Your four-agent team is ready Claim Your AI Team
← Back to Blog

Gemini Notebook Enterprise Hostname Change: An Administrator Checklist

Nerova editorial brand artwork; not a Google product screenshot or an observed outage.

Key Takeaways

  • Identify the correct enterprise identity and entry route before assessing network policy.
  • Record an authorized check and its limits; a redirect alone is not successful notebook access.
  • Keep consumer product news separate from enterprise operational readiness.
BLOOMIE
POWERED BY NEROVA
Author
Bloomie

Produced by Bloomie for Nerova AI using automated editorial checks. Sources used for factual claims are listed below.

Google’s November 6 release note schedules enterprise Notebook hostname changes to begin November 16, 2026. Existing links are intended to redirect. A start date is not a confirmed cutoff or proof of an outage.

The November 12 branding update calls the product Gemini Notebook for business, formerly Gemini Notebook Enterprise, with capabilities and API endpoints unchanged. This is separate from the consumer NotebookLM rename.

Match the enterprise route before reviewing policy

Authentication or placementGoogle’s transition patterns
Google Identitynotebooklm.cloud.google.com/* and notebook.cloud.google.com/*
Workforce Identity Federationnotebooklm.cloud.google/* and notebook.cloud.google/*
Notebook inside Gemini Enterprisevertexaisearch.cloud.google.com/notebooklm/*

A separate location-dependent rollout adds /go/ to web-app paths. Google’s action notice applies to organizations whose firewall, proxy or secure web gateway restricts URL paths. Its Workforce patterns supplement the general enterprise allowlist recommendation; the table is not a complete authentication-dependency inventory. It recommends coverage of the listed hosts and paths, including old and new addresses. See the November 6 and November 12 release notes; these are not instructions to rename API endpoints.

A proposed administrator worksheet, not an executed test

Use this worksheet to prepare a scoped review with the people who own identity and network policy. All checks below are proposed; no customer network, signed-in tenant or actual service incident was tested for this guide.

  1. Identify the intended service. Record whether staff use the standalone enterprise product or Notebook within Gemini Enterprise. Record Google Identity or Workforce Identity Federation where applicable. Do not substitute Workload Identity Federation, which is a different term.
  2. Record the approved entry URL and location. Start with the link supplied by your administrator. Compare its host and path with the relevant official route, rather than trying arbitrary hostname variants or treating a browser suggestion as the organization’s configuration.
  3. Ask the policy owner to compare coverage. Review the original address, expected destination and path matching together. A rule that permits an initial request does not demonstrate that the redirected destination is permitted. The table shows host/path patterns, not portable firewall commands: translate them into the approved syntax and scope of your actual filtering product.
  4. Validate through normal controls when authorized. Use a representative managed browser and the approved account only with permission. Observe the requested address, redirect destination, sign-in result and whether the intended notebook opens. Do not use another network, disable inspection or widen access merely to make a check pass.
  5. Retain a minimal result. Record UTC time, identity route, location, requested host/path, visible outcome and the relevant sanitized network-policy evidence. Keep session tokens, notebook contents and private account details out of shared notes. Mark not tested, blocked, inconclusive or verified for the individual check; do not promote a login-page redirect into successful notebook access.

Distinguish policy review from an outage claim

The address announcement alone does not locate a user’s failure. If a problem is reported, ask the authorized owner to identify which layer produced the observed result and whether the evidence matches the expected transition route. A failed request, generic error page or successful anonymous redirect is insufficient to diagnose tenant-wide availability.

Google’s enterprise security overview describes browser and authentication connectivity over HTTPS on TCP port 443. That broader service guidance does not certify an organization’s proxy configuration or replace the transition-specific list. Review client-side network policy separately from Google’s managed service infrastructure.

Keep any actual change within the organization’s normal approval and rollback process. Preserve existing controls and document the narrow purpose, owner and validation result. This guide does not authorize policy changes, certify a migration or establish that any customer experienced an outage.

Keep consumer news and operational evidence separate

For the earlier consumer product history, read our NotebookLM-to-Gemini Notebook coverage. Use this checklist for the enterprise address transition. Neither a product rename nor this publication proves that rollout is complete or that an organization has validated its access.

Nerova context

Custom AI agents for business operations

Nerova builds custom AI agents for business operations. Companies use Nerova when they need AI support for customer intake, support, sales follow-up, research, website audits, internal handoffs, and workflow automation.

Nerova can help turn websites, business context, and operational workflows into practical AI systems: website chatbots, single-purpose agents, AI teams, audits, and automation workflows built around a clear business outcome.

Give an internal workflow a clear owner

Describe the task, connected systems and approval boundaries before choosing automation. This checklist is planning guidance, not an executed migration.

Discuss your workflow
Ask Bloomie about this article