When it comes to scaling tenant-ready automation on VMware Cloud Foundation, every infrastructure team hits the same wall: onboarding new tenants is either too manual or too brittle. We built the Tenant Onboarding Workflow Builder to change that.

This drag-and-drop simulation tool lets you rapidly prototype and export tenant onboarding workflows—no PowerCLI experience or YAML syntax memorization required. Whether you're provisioning a namespace, configuring NSX segments, or triggering an ArgoCD sync, this tool helps you visualize the automation flow and export it into formats that plug directly into your GitOps pipelines.

This tool ties directly into the topics we’ve covered in the VCF Automation Blog Series, especially around:

• GitOps-based lifecycle automation
• Role-based access control for multitenant environments
• DevSecOps-ready onboarding blueprints for your platform team

​Let’s walk through how it works—and how it can help you simplify tenant activation, reduce manual error, and enforce governance from day one.

VCF Automation Series:

• This Is the Missing Piece in Your VCF 9.0 Automation Strategy: Red Hat Ansible
• STOP Deploying VCF Wrong: Unlocking Tenant-Ready Workflows with GitOps & CI/CD
• STOP! Your VCF Automation Is a Security Time Bomb (Unless You Do THIS)

Part 3 of our VCF 9.0 Automation Series

VMware Cloud Foundation (VCF) 9.0 has redefined private cloud automation. With full-stack automation powered by Ansible and orchestrated through vRealize Orchestrator (vRO), and version-controlled deployments driven by GitOps and CI/CD pipelines, teams can build infrastructure faster than ever.

Enter RBAC and policy enforcement.
This third and final installment in our automation series focuses on how to secure and govern multi-tenant environments in VCF 9.0 with role-based access control (RBAC) and layered identity management.

VCF 9.0 Automation gives us a powerful foundation for multi-tenant self-service infrastructure. But to operate like a true internal platform-as-a-service, we need:

• Version control of blueprints and workflows
• Consistent deployment across environments
• Integrated approval and testing processes

This is where GitOps and CI/CD pipelines come in. By storing VCF Automation blueprints, Aria Orchestrator workflows, and even Ansible playbooks in Git—and connecting them to your CI/CD tooling—you bring repeatability, collaboration, and traceability into the heart of your private cloud.

​Part of the VCF Automation Series: Tenant-Ready Workflows at Scale

VMware Cloud Foundation 9.0 marks a major leap toward a true private cloud platform—with built-in multi-tenancy, automated provisioning, and extensible workflows via external Orchestrator instances. But there's still one critical gap many platform teams face:

That’s where Red Hat Ansible becomes the missing piece.
This post shows how to integrate Ansible with VCF 9.0 Automation to deliver:

• Full-stack automation from VM to application
• Tenant-scoped workflows via external vRO instances
• Post-deployment actions like patching, agent installation, and OS hardening
• GitOps-friendly, repeatable playbook execution
• RBAC and policy enforcement across tenants

If you're building a cloud platform on VCF 9.0, this integration is not just nice-to-have—it's essential.

In any VMware environment, snapshots are powerful but risky tools. They're great for backups or quick rollback points during updates, but leaving them for too long can seriously degrade performance, consume excessive datastore space, and even cause backup failures.

Tools like RVTools give you visibility into your snapshots, but wouldn’t it be better if you could automate the process and be proactively alerted when snapshots become a problem?

​That’s exactly what we’ll do in this blog—let’s build a PowerCLI script that checks for old snapshots and alerts you automatically.

Snapshots are meant to be temporary. VMware recommends deleting them within 24–72 hours in most production environments. However, admins often forget to clean them up—especially in environments with multiple teams or large numbers of VMs.

Leaving snapshots too long can result in:

• Slower VM performance
• Datastores filling up unexpectedly
• Failed backup jobs
• Risky system state assumptions