---
slug: "gcp-cloud-number-registry-discovery-without-designated-project-breaking-change"
title: "Cloud Number Registry: discovery stops without a designated project"
summary: "From 25 Nov 2026, Cloud Number Registry stops discovering resources if the configuration has no designated project. Existing discovered resources remain but are not updated."
cloud: "gcp"
service: "Cloud Number Registry"
service_slug: "cloud-number-registry"
category: "feature"
type: "breaking_change"
announced_date: null
effective_date: "2026-11-25"
effective_precision: "day"
replacement: null
affected_versions: []
source_url: "https://docs.cloud.google.com/release-notes#October_30_2026"
extra_source_urls: ["https://docs.cloud.google.com/number-registry/overview#project-designation-enforcement"]
vendor_ref: null
last_checked_at: "2026-11-12T09:56:14.506Z"
created_at: "2026-11-13T13:36:44.208Z"
updated_at: "2026-11-13T13:36:44.208Z"
url: "https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change"
short_url: "https://eolwatch.dev/i/2v"
markdown_url: "https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change.md"
json_url: "https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change.json"
---

# Cloud Number Registry: discovery stops without a designated project

From 25 Nov 2026, Cloud Number Registry stops discovering resources if the configuration has no designated project. Existing discovered resources remain but are not updated.

- Effective date: 25 Nov 2026
- Cloud: [GCP](https://eolwatch.dev/cloud/gcp.md)
- Service: [Cloud Number Registry](https://eolwatch.dev/services/gcp/cloud-number-registry.md)
- Type: Breaking change
- Category: [Feature](https://eolwatch.dev/categories/features.md)
- Replacement: Not stated by vendor
- Announced: Not stated by vendor
- Official source: [docs.cloud.google.com](https://docs.cloud.google.com/release-notes#October_30_2026)
- Last checked: 12 Nov 2026

## What breaks

From 25 Nov 2026, Cloud Number Registry stops discovering resources in configurations that have no designated project. Without a designated project, new resources are not discovered, and existing discovered resources remain but are not updated. For example, after a subnet is deleted, its discovered range remains in Cloud Number Registry. Cloud Number Registry is in Preview.

## What to do

To continue discovering and updating resources after the enforcement date, check or configure the designated project for your organization:

1. [View the required roles to list and create project designations](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#required-roles). The designation is made by an IAM principal that has the Cloud Number Registry IPAM Admin role at the organization level.
2. [List project designations](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#view-designated-project).
3. [Designate a project](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#designate-project).

## Replacement

Not stated by vendor.

## Sources

- [Official source](https://docs.cloud.google.com/release-notes#October_30_2026) (docs.cloud.google.com, Official)
- [Additional source](https://docs.cloud.google.com/number-registry/overview#project-designation-enforcement) (docs.cloud.google.com, Official)

Last checked against the first source in this list on 12 Nov 2026.

Page: https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change | JSON: https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change.json

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.