Field note / cloud and virtualization

A workload does not migrate itself because a monthly band exists.

Azure administration, on-premises virtualization, and cloud-migration projects raise their own questions - workload dependencies, licensing, downtime tolerance - that a per-user monthly reference band was never built to answer. This is qualified as its own lane, the same way a project or a backup commitment is.

Two different jobs, often confused

Ongoing administration is recurring. Moving a workload is a project.

Azure and virtualization work splits cleanly into two categories once you separate them: recurring administration of an environment that already exists - patching a Hyper-V host, reviewing Azure cost and access, keeping a virtual server fleet current - and a migration or build project with a defined start and finish, such as moving an on-premises server into Azure or consolidating a VMware estate. The first can potentially fit a qualified recurring lane once the environment is documented; the second follows the same project logic as an office move or rollout.

Compare this with the general project lane →

Environment state

Azure tenant already in use

A subscription and workloads already exist and need ongoing attention.

Included pattern: Recurring administration - access review, cost visibility, and routine configuration follow-up - once the tenant's shape is documented.
Required inputs: Subscription structure, current admin roles, and what already runs there.
Explicit exclusions: Architecture decisions or cost commitments made without the client's own sign-off.

Environment state

On-premises virtualization

A Hyper-V or VMware environment already runs the client's servers.

Included pattern: Routine host and guest administration within an agreed platform and support boundary.
Required inputs: Host count, hypervisor version, and current licensing status.
Explicit exclusions: Supporting an unsupported or end-of-life hypervisor version without a named exception.

Environment state

A migration project

Something is moving from on-premises to cloud, or from one platform to another.

Included pattern: A scoped project - inventory, dependency mapping, cutover plan, and validation - priced and timed on its own.
Required inputs: What is moving, acceptable downtime, and a target date.
Explicit exclusions: A fixed price or date before the workload inventory is reviewed.

Environment state

Licensing and cost decisions

Cloud and virtualization licensing sits behind every environment above.

Included pattern: Surfacing licensing and consumption-cost observations as part of the recurring or project record.
Required inputs: Current licensing agreements and who holds the purchasing relationship.
Explicit exclusions: The purchasing decision itself, which stays with the partner or client.

Boundary table

Four questions that belong to qualification, not the public offer.

Question	Why the public bands cannot answer it	Where it gets answered
How much downtime will this need?	Depends entirely on the workload, its dependencies, and what the business can tolerate.	Confirmed during the migration plan, not assumed from a reference band.
What does a migration cost?	Cost depends on workload count, complexity, and data volume - a monthly band cannot price a one-time move.	A separate project quote, following the same logic as any other project.
Whose licence is it?	Cloud and virtualization licensing is a purchasing relationship, and purchasing stays a partner or client decision.	Named in the access and licensing record before administration begins.
What happens if something does not migrate cleanly?	Rollback and contingency planning depend on what the workload actually is.	Written into the migration plan before cutover, not improvised during it.

What not to promise yet

Keep the offer honest until the workload is reviewed.

A zero-downtime guarantee before the workload is reviewed
A migration timeline before dependencies are mapped
Cost savings from moving to the cloud without reviewing current spend
Support for a hypervisor or cloud service the environment does not actually use
A licensing recommendation before purchasing ownership is named

Related decision

A migrated workload still needs a network to reach it.

Firewall, VPN, and connectivity administration are qualified as their own lane, separate from the workload itself.

Review network and connectivity scope

Bring the workload list, not a migration date.

A plain inventory of what runs where is enough to start a fit conversation about the environment.

Discuss a cloud or virtualization lane