A city Carbon Black Cloud org lists only on-premises endpoints. Azure IaaS VMs that run the same line-of-business apps never appear, even though NSX-T Distributed Firewall is healthy in the on-premises SDDC. What should the administrator do?
Select an answer to reveal the explanation.
Short Explanation
Carbon Black only sees machines that actually run a sensor or a supported cloud connector. Azure VMs are not magically inventoried because on-prem NSX already has DFW. Put a workload sensor on those IaaS guests.
Full Explanation
Carbon Black Cloud visibility requires a sensor or a supported cloud/workload integration on each endpoint. On-premises NSX-T groups and Distributed Firewall inventory do not enroll Azure IaaS VMs in a CBC org. Workspace ONE Access and NSX identity firewall are not CBC enrollment paths. Deploy the appropriate CBC sensor or cloud integration on the Azure VMs, assign a policy via sensor groups, and confirm check-in.