A VCF Operations workflow for adopting a vCenter that is already running, whether or not NSX is present, as a workload domain of a VCF 9.0 instance; every one of its clusters is brought in, and NSX gets deployed or joined where needed. Convergence differs by making an existing environment into a management domain instead.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Import in context, with comparison tables and the common traps.
Terms in this definition
- VCF Operations
VCF's console for running the fleet. It covers alerting, monitoring, capacity, reporting, log analysis and licensing alongside fleet management of identity, passwords, certificates and lifecycle.
- Foundry workflows
Preview Foundry feature that orchestrates agents and logic in a fixed, declarative order, supporting variables, if/else branches and human-in-the-loop steps. Workflows are being retired on 1 December 2026 and Agent Framework replaces them.
- vCenter
Management software for VMs, clusters and ESX hosts. Each domain in VCF gets a dedicated one.
- NSX
Software that handles networking and security across VCF, covering firewalling, load balancing, NAT, VPCs, overlay segments and Tier-0/1 gateways.
- workload domain
Domain in VCF for business applications. It gets a dedicated vCenter and NSX that may be dedicated or shared; the management components live separately in the management domain.
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- Convergence
In VCF 9.0, adopting a vCenter you already run, with its hosts and optionally Aria products, as the management domain of a brand-new fleet or instance; absent pieces are deployed for you. Enhanced Linked Mode setups are excluded.
Related terms
- ADMX
Group Policy settings are defined in these XML files. The settings catalog in Intune already has many settings that depend on them, and you may import up to 20 of your own or third-party ones, at most 1 MB each and in en-us only, along with matching ADML files.
- Auto date/time
With this Power BI Desktop option switched on, each date column in an Import table gets its own concealed date table, unless the column sits on a relationship's many side. That suits basic models, yet it inflates model size and prevents one shared date table from filtering several fact tables.
- Automatic page refresh
A page-level option that makes visuals re-query a DirectQuery source on a timer or whenever a change detection measure's value moves. It isn't available for Import models, and in the service the capacity sets the shortest interval allowed.
- azurevpnconfig.xml
Profile file for the Azure VPN Client, found in the P2S profile package downloaded once the gateway is set up for Entra ID authentication; users import it, or it is pushed out to them.
- BIND zone file
Plain text file in the standard format that lists a DNS zone's records. You can import it with
az network dns zone importin the Azure CLI or through the portal; Azure PowerShell offers no cmdlet for this. - CMDB
External database where IT assets are recorded. If your organisation treats it as authoritative, you can import Business View groups from an exported file instead of building them by hand.
- Compatibility data bundle
Brought in by depot sync or a manual import, this vSphere Lifecycle Manager data set merges the Product Interoperability Matrix with Broadcom's compatibility data, informing image recommendations and checks run before remediation.
- Composite model
A Power BI semantic model whose tables use different storage modes, for example some Import and some DirectQuery, chosen table by table. Tables in Dual mode can work either way, and Power BI picks whichever suits each query best.