Checking, as part of design validation, that what was built matches the specification: prerequisites met and configuration in line with the physical design. Validation instead tests against requirements.
In the Ultra Transcenders books
Each book explains Verification in context, with comparison tables and the common traps.
Terms in this definition
- Validation
Testing the delivered solution against stakeholder needs and agreed quality levels (verification, by contrast, checks the build against the design). Its strategy defines measurable acceptance criteria per requirement, test types, entry and exit criteria, roles and sign-off.
- Physical design
The build specification for a VCF deployment, captured in the VCF Planning and Preparation Workbook and consumed by the VCF Installer. It realises the logical design by fixing exact products, versions, hardware and quantities, and values such as VLAN IDs, subnets, IP addresses, DNS names, MTU, certificates, rack placement and appliance sizes.
Related terms
- afdverify
Verification CNAME in Front Door (classic), mapping afdverify.<host> to afdverify.<name>.azurefd.net, which proves ownership of a custom domain while live traffic stays where it is.
- Azure AI Face
Foundry Tool limited to human faces: it detects them, verifies whether two match (1:1) and identifies a person from a group (1:many). Verification and identification are Limited Access features.
- helper appliance
A short-lived VM or cloud instance spun up for particular tasks and deleted when done: restores to Azure or Google Compute Engine, certain Linux verification, and object storage retention and health checks.
- Home Page Dashboard
The landing-page dashboard of the Orchestrator UI. For the chosen scope it charts how plans fare in verification, execution, testing and scanning, and its RPO and RTO panes compare achieved with target figures for as many as 10 plans.
- Limited Access
Under this Microsoft policy, sensitive AI features such as custom neural voice or Face identification and verification can only be used after registering and being approved as a managed customer with an approved use case.
- plan state
The verification status of a plan. NEEDS VERIFIED means it has not been tested or checked since it was created or last edited, NOT VERIFIED means a test, readiness check or malware scan failed, and VERIFIED means one passed; modes like ENABLED or IN-USE are tracked separately.
- SMS
Text-message verification, where a one-time code is sent to a phone for MFA, password reset or sign-in; Microsoft advises organisations to move to stronger options. Microsoft itself stops sending these texts and voice calls from 1 February 2027, or 1 July 2027 for Global Administrators and external users, so anyone still needing them must then bring a telephony provider.
- SureReplica
Extends SureBackup-style verification to vSphere replicas, CDP ones included. A chosen replica restore point boots inside a virtual lab, goes through identical tests and gets reported on, while production carries on undisturbed.