VMware did remove the two-year recertification requirement for VMware Certified Professional (VCP) credentials in 2019. That was a meaningful change for people who had already earned a VCP. It did not, however, establish a permanent rule that every later VMware credential would be valid without renewal. In July 2025, VMware Cloud Foundation (VCF) announced a different policy: its new certifications carry an expiration date with a 36-month renewal window. Readers comparing an older VCP certificate with a current VCF examination therefore need to distinguish the date and program of the credential before deciding whether renewal is required.
This distinction matters more than the slogan “no more cert expirations.” A person can legitimately hold an older VCP that no longer has the original two-year recertification requirement while someone pursuing a newer VCF credential must work within a time-limited lifecycle. Neither rule, by itself, proves how recently a person has operated vSphere, designed private cloud infrastructure, or responded to a production failure. Certification policy and engineering currency are related but different questions.
What VMware changed for VCP holders in 2019
In February 2019, VMware announced the removal of its two-year VCP recertification requirement. Its published explanation said that VCP expiration dates would be removed in Certification Manager, with certain credentials that had expired under the previous policy returning to active status. The practical intention was to stop requiring an otherwise certified professional to renew the same credential simply because two years had elapsed. That is the historical event to which this article’s original title refers.
The policy was not a promise that every training program, exam code, or version would remain available for future candidates. VMware continued to retire earlier exams and their associated credential versions as products evolved. A credential’s status in a professional’s record and the ability of a new candidate to schedule its old exam are separate matters. For example, the historical vSphere 6 Foundations exam 2V0-620 was retired in 2019. An archived guide to that exam can still explain how the earlier platform worked, but it must not be mistaken for a booking guide.
VMware’s 2019 VCP recertification announcement provides the historical policy evidence. The 2019 exam-retirement notice illustrates the different issue of examinations being withdrawn. Holding a credential, refreshing current technical knowledge and qualifying for a later credential may each follow different rules.
Why VMware Cloud Foundation changed the renewal picture in 2025
On July 29, 2025, the VMware Cloud Foundation certification program announced a new lifecycle. Under that policy, VCF certifications have expiration dates and a 36-month renewal window. VMware described this as a way to connect certification to current private cloud expertise, rather than treating the 2019 no-expiration statement as the final policy for every new certificate. It also stated that passing the relevant exam is sufficient to earn or renew a covered VCF certification, without a separate training-based upgrade path.
The official VCF certification update also explains two limitations that can be easy to miss in an older study article. First, examinations taken under the former structure cannot simply be carried forward as passes for the newly structured certifications. Second, the 36-month renewal approach applies to the VCF certification program; Broadcom Software certifications have a distinct policy. A candidate should not assume one universal expiry rule across products or programs that happen to share corporate ownership.
For current candidates, the policy question is therefore not merely “Does VMware certification expire?” A more useful question is: Which credential, issued under which program and on which date, am I actually discussing? A historical VCP and a newly earned VCF credential may both be genuine achievements without having identical renewal obligations. Employers and candidates who preserve that distinction avoid treating an old badge label as either permanently current or automatically invalid.
Expiration, retirement and technical relevance are different concepts
An expiration date defines how long a certification remains current under the issuer’s rules. Exam retirement means the issuer no longer offers a particular examination to new candidates. Product retirement means a software release has reached a defined lifecycle stage. These events may be connected, but they are not interchangeable. A certification record might remain verifiable even when the exam used to earn it is no longer offered; an active exam can also be based on products that have changed since a professional last used them.
Consider a long-time vSphere administrator who earned a VCP on an earlier platform version. Their experience may include sound practices for host networking, shared storage, cluster capacity, backups and change control. Yet the administrator still needs to verify which features and licensing entitlements are supported on the environment being operated today. A qualification in an old version is evidence of prior learning and assessment, not evidence that every current deployment or upgrade decision is safe.
The reverse is also true. A recently passed certification exam cannot establish that its holder has performed a production recovery, planned a non-disruptive migration or diagnosed an intermittent storage path issue. Those are engineering activities that require operational evidence. Credential dates help frame the conversation; they are not substitutes for the conversation itself.
What the newer VCF credentials actually assess
The VMware Cloud Foundation program has moved toward role-based certification for private cloud operations and architecture. Administrators work with provisioning, lifecycle operations, troubleshooting and managing VCF services; architects must justify design choices around availability, performance, security, recovery, capacity and migration. The two roles overlap technically but ask different questions. An administrator may be asked to restore a failed management workflow, while an architect must explain the failure domain and recovery assumptions that made that workflow necessary.
Broadcom publishes a current guide for VMware Cloud Foundation 9.0 Architect, associated with the VMware 2V0-13.25 exam. Someone evaluating that architecture credential should consult the VMware 2V0-13.25 exam objectives rather than assuming an older VCP syllabus covers the current design work. The same principle applies to the current Administrator program: verify its published exam guide and qualification requirements directly.
These are substantive distinctions, not reasons to collect unrelated badges. If a role focuses on operating ESXi hosts, vCenter and cluster services, administration depth and fault isolation may matter first. A position accountable for resilient cross-domain design needs capacity modelling, failure testing, security boundaries and recovery objectives. The most relevant exam is the one whose defined tasks closely match the decisions the professional must make.
How to verify a credential without overstating it
When reviewing a resume, training record or certification claim, start with the exact issuer-recognized title and the year or date on which it was earned. Ask which specific examination or program structure applied and whether the issuer still recognizes the credential under its current rules. For a current VCF credential, check the 36-month renewal arrangement. For an older VCP, check the historical record rather than projecting the current VCF policy backward.
Next, ask for evidence appropriate to the proposed job. An operations candidate might explain how they detect a failed ESXi host, establish which workloads are affected, verify capacity on surviving hosts and confirm that backups can actually be restored. A design candidate might walk through the consequences of losing an availability zone or management component, including recovery-time targets and which dependencies must remain reachable. The aim is to discover whether the person can reason about the environment, not to penalize someone for holding an older credential.
Hiring teams should also avoid inferring that the absence of a recent exam date means that an experienced professional has ceased learning. Some administrators gain current skills through supported upgrades, operational responsibility, formal training or documented production work. Conversely, a newly awarded certificate should prompt a discussion of hands-on limits rather than a presumption of expert production capability. A fair evaluation combines issuer records, demonstrated skills and the operational responsibilities of the role.
Practical decisions for holders and new candidates
If you already hold a VCP from the earlier no-expiration era, retain the exact credential designation in your records and check your issuer account for its current status. Keep a separate record of the vSphere or VCF releases you have worked with, the systems you have managed and the recovery exercises you have completed. That record prevents an old qualification from becoming a misleading claim of proficiency on a new platform.
If you are considering a new VCF certification, confirm the current exam code, published blueprint, renewal rule and eligibility directly from the issuer before buying a course or paying an exam fee. Make a short task-based gap assessment: can you explain private cloud networking paths, identity and privileges, upgrade dependencies, backup boundaries and fault recovery relevant to your chosen role? Then select lab exercises or training that close those gaps. Changes to course requirements or exam versions should be confirmed at registration, not inferred from an archive.
For professionals advising teams, the most useful policy summary is precise: VMware removed the two-year VCP recertification requirement in 2019, but the VCF certification program established a 36-month renewal model in 2025. The original “no more expirations” headline records a real historical change; it must not be read as today’s blanket rule. A sound professional-development plan respects both the issuer’s credential lifecycle and the more demanding task of keeping hands-on infrastructure skills current.
