The ID property which was till now being displayed caused this overlapping. The Azure's vm id is too long to be contained within the vm details column. Upon investigating around other compute resources, it's notable that ID is usually not shown in the hosts or vm details page. Hence, removing the ID and instead adding relevant fields like public_ip_address and private_ip_address as shown by other CRs too.
ShimShtein
commented
4 years ago
The ID property which was till now being displayed caused this overlapping. The Azure's vm id is too long to be contained within the vm details column. Upon investigating around other compute resources, it's notable that ID is usually not shown in the hosts or vm details page. Hence, removing the ID and instead adding relevant fields like
public_ip_addressandprivate_ip_addressas shown by other CRs too.