GCPBreaking change
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.
Breaking from , 25 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:
- View the required roles to list and create project designations. The designation is made by an IAM principal that has the Cloud Number Registry IPAM Admin role at the organization level.
- List project designations.
- Designate a project.
Replacement
Not stated by vendor.
Sources
- Official sourcedocs.cloud.google.comOfficial
- Additional sourcedocs.cloud.google.comOfficial
Last checked against the first source in this list on .
Related
- , 18 Aug 2026Microsoft Defender for Cloud: retirement in Azure operated by 21VianetSource
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 15 Sep 2026Azure Maps: Gen1 price tier (Standard S0 and S1) retirementSource
- , 15 Sep 2026Azure Monitor: Activity Logs legacy solution retirementSource
- , 15 Sep 2026Compute Engine: NVIDIA P100 GPU shutdownSource
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