Why this matters: VMware Cloud (running on infrastructure hosted by a public cloud provider) still doesn't show up in a standard cloud cost breakdown the way native cloud services do — it needs its own connection to get counted. Getting that connection and firewall setup right the first time avoids a back-and-forth over network access before data ever starts flowing.
This shows up differently depending on your role:
-
Infrastructure teams handle the appliance deployment, gateway firewall rules, and datacenter onboarding covered in the pages below.
-
FinOps managers use the resulting data to see VMware Cloud spend alongside the rest of cloud spend, instead of as a separate, disconnected number.