Rediscovery occurs when you rerun the same discoveries to update, delete, and import new cloud resources based on discovery tasks you ran before. This is useful when technical or security restrictions prevent you from running visibilty tasks on your cloud infrastructure.
For more details on setting up your system to support rediscovery, see Rediscovery of cloud resources.
Only certain actions are tracked by Azure rediscovery. These actions are as follows:
- Virtual Network/Subnets
- Creating a new Virtual Network/Subnet
- Updating a CIDR of a Virtual Network/Subnet
- Deleting a Virtual Network/Subnet
- Virtual Machines
- Creating a new virtual machine
- Updating a virtual machine state
- Deleting a virtual machine
- Load balancers
- Creating a new load balancer
- Deleting a load balancer
- DNS records
- Creating a new Public or Private
- Creating a new record
- Deleting a zone
- Deleting a record
- Private Endpoint
- A new private endpoint has been created.
- An existing private endpoint has been deleted.
- Kubernetes Cluster:
- Creating a Cluster
- Deleting a Cluster
- Starting a Cluster
- Stopping a Cluster
- Creating a Node Pool of a Kubernetes Cluster
- Deleting a Node Pool of a Kubernetes Cluster
- Scaling a Node Pool of a Kubernetes Cluster
-
Selective Deployment of changes is not supported for rediscovery.
-
If the name or value of a Public or Private DNS Zone record is changed, the record is deleted and reimported into Address Manager as a new record upon rediscovery.