Senior IT expertise. Without the full-time hire.
Experienced cloud and infrastructure engineering for the projects your team needs to get done. Project-based work for businesses, IT teams, and MSPs.
Some projects need another engineer. Not another employee.
Defined infrastructure and cloud projects, taken from initial assessment through documented handover.
- The backlog keeps growing. Projects agreed months ago are still waiting behind day-to-day operations.
- A skills gap on one project. Your team is strong, but this one needs deeper Azure, identity, or PKI experience than you have in-house.
- A migration nobody has time to plan. Servers, mailboxes, files, or identity need to move, and doing it safely takes focused engineering time.
Why choose Ops for Hire
An independent senior engineering consultancy with a professional project-delivery process.
-
One experienced engineer
Direct access to the engineer doing the work. No account managers, no hand-offs, no layers.
-
The plan comes first
Scope, risks, validation, and rollback are written down and approved before anything changes.
-
Documented handover
Every project ends with as-built documentation and knowledge transfer to your people.
Services that get projects done
Every engagement starts with a defined objective, scope, and expected outcome.
-
Azure & Cloud
Plan, build, migrate, optimize, and troubleshoot Azure environments.
-
Microsoft 365 & Identity
Improve Microsoft 365, Entra ID, Intune, authentication, and access.
-
Infrastructure
Modernize and troubleshoot Windows, Active Directory, networking, PKI, and hybrid environments.
-
Migrations
Plan and execute infrastructure and cloud migrations with validation and rollback planning.
Who it’s for
-
Businesses
A project done properly, without adding a full-time hire: planned, carried out, and handed back documented.
-
Internal IT teams
Work alongside your existing IT team on a defined initiative, following your change processes and leaving the knowledge with your people.
-
MSPs
Add senior engineering capacity behind your service for customer projects, migrations, and escalations.
How It Works
Assess the environment, build the plan, complete the work, validate it, and document what changed. The same six steps, every engagement.
- 01
Discover
Understand the environment, the goal, and the constraints.
- 02
Assess
Review architecture, dependencies, and risks.
- 03
Plan
Write the plan. Nothing changes until you approve it.
Your approval - 04
Implement
Carry out the approved work in agreed windows.
- 05
Validate
Test against the plan and fix what the tests find.
- 06
Handover
Deliver documentation and transfer the knowledge.
Know the plan before the work starts
This is what you review before anything changes in your environment. Turn the pages: scope, risks, phases, validation, rollback, effort, and what “done” means.
Illustrative sampleA plan for a fictional company. Yours is written for your environment.
Azure Migration: File, Application & Identity Services
| Rev | Description |
|---|---|
| 1.0 | Preliminary plan for customer review |
Contents
Ops for HirePage 1 of 15
1Executive summary
Example Co. is a 60-person professional services firm. Its file server, line-of-business application, and only domain controller run on a single Hyper-V host whose hardware warranty ends this year.
Ops for Hire proposes moving the application and file data into Azure, adding a domain controller in Azure, and connecting the office with a site-to-site VPN. The work runs in six phases, with a pilot before production and a rollback path for every workload.
1.1 Objectives
- Retire the out-of-warranty host without losing any service.
- Users keep the same drives and application, with no new sign-in steps.
- Every migrated system is backed up, monitored, and documented.
- Azure spend is visible, with alerts before it passes the agreed budget.
2Current state → target state
- HV01Hyper-V host, Server 2016
- DC01AD DS, DNS, DHCP
- FS01File shares, about 2.1 TB
- APP01LOB app, SQL Server 2016
- PRN01Print server
- vnet-hubNetwork, VPN gateway
- DC02Domain controller, Server 2022
- APP01Migrated VM, SQL on Azure VM
- FilesAzure Files, AD DS auth
- BackupRecovery Services vault
2.1 Items to confirm
- Vendor support for the application on Azure To confirm
- Firewall supports IPsec site-to-site VPN To confirm
- Current backup platform and retention To confirm
- Business Premium licensing for all users Assumption
3Scope of work
3.1 Included
- Azure subscription and network foundation
- Site-to-site VPN to the office
- Migration of APP01 and file shares
- Domain controller in Azure
- Backup, monitoring, cost alerts
- As-built documentation and handover
3.2 Out of scope
- Application upgrades or vendor work
- End-user device replacement
- Microsoft 365 tenant changes
- Licensing purchases
3.3 Optional
- Replace PRN01 with Universal Print
- Decommission HV01 and DC01 after acceptance
- Conditional Access review
4Assumptions & dependencies
4.1 Assumptions
- Required Azure subscription and licensing will be in place before Phase 2.
- APP01 can run on a supported Windows Server version in Azure.
- Users work from the office or an existing VPN; no new remote-access design.
- Current backups are restorable and can be tested before cutover.
4.2 Customer dependencies
- Global and Azure administrator access
- Firewall administrator or vendor contact
- Application vendor contact for support confirmation
- Approval of maintenance windows
- Five pilot users from one department
- Sending the user notice before cutover
5Discovery questions
- Applications
- Does the vendor support APP01 on Azure, and on which SQL Server versions?
- Applications
- Are there any other applications or scheduled tasks on APP01 or FS01?
- Networking
- What firewall model and firmware is in the office, and who manages it?
- Networking
- Is the office internet connection fast and stable enough for daily file access over VPN?
- Identity
- Are any services still authenticating against DC01 by IP address or legacy protocols?
- Business
- Which days or hours must the application stay available without interruption?
6Implementation phases
- Phase 1Discovery & assessment Validate the current state; confirm vendor support and requirements. Exit: Every “To confirm” item resolved or accepted.
- Phase 2Design & preparation Build the Azure foundation: subscription layout, network, VPN, backup, cost alerts. Exit: VPN stable for seven days. Design approved.
- Phase 3Pilot Move one department’s file share; test the application with a pilot group. Exit: Pilot users sign off. No open critical issues.
- Phase 4Production migration Migrate the application, files, and add DC02 in agreed change windows. Exit: All in-scope workloads running in Azure.
- Phase 5Validation & remediation Run the validation plan and fix what it finds. Exit: Tests pass. Issues resolved or formally accepted.
- Phase 6Documentation & handover Deliver as-built documentation; run a knowledge-transfer session. Exit: Documents delivered. Acceptance confirmed.
7Validation plan
- Users sign in and open mapped drives from the office and over VPN.
- APP01 launches, opens a recent record, and saves a change.
- SQL Server backups complete and a test restore succeeds.
- DC02 replicates with DC01; DNS resolves from both sites.
- Azure Backup completes a full run for every migrated VM.
- A test budget threshold triggers the cost alert.
8Rollback & recovery
| Workload | Kept until | Trigger | How it’s restored |
|---|---|---|---|
| APP01 application | Source VM kept powered off, intact, 14 days | App cannot open or save records | Power the source VM on; revert the DNS record |
| File shares | Source shares read-only, retained 30 days | Missing data or broken permissions | Restore write access; revert drive mappings |
| Domain controller DC02 | DC01 stays primary until handover | Replication or authentication errors | Demote DC02; no user-facing change |
9Risks & mitigations
| Risk | Impact / likelihood | Mitigation |
|---|---|---|
| Vendor does not support the application on Azure, or requires a newer SQL Server version. | High / Medium | Confirm in Discovery, before design. Plan any SQL upgrade as its own phase. |
| Office firewall cannot hold a stable site-to-site VPN. | High / Low | Confirm model and firmware early. Soak-test the tunnel for a week before any workload moves. |
| File permissions do not carry over as expected. | Medium / Medium | Export NTFS permissions, pilot one department, compare access before cutover. |
| Users lose mapped drives or printers after cutover. | Medium / Medium | Update mappings by Group Policy, pilot first, send a one-page user notice. |
10Estimated effort & timeline
| Phase | Hours |
|---|---|
| Discovery & assessment | 6–10 |
| Design & preparation | 10–16 |
| Pilot | 6–10 |
| Production migration | 14–24 |
| Validation & remediation | 6–10 |
| Documentation & handover | 6–10 |
| Total | 48–80 |
| Stage | Target |
|---|---|
| Discovery | Week 1 |
| Foundation, VPN soak test | Weeks 2–3 |
| Pilot | Week 3 |
| Production migration | Week 4 |
| Validation & handover | Week 5 |
Hours are engineering effort, not elapsed time. Vendor confirmation and the VPN soak test can extend the schedule without adding hours.
11Deliverables & completion
11.1 Deliverables
- Implemented Azure environment
- Architecture diagram, as built
- Configuration summary and admin runbook
- Validation results
- Knowledge-transfer session
11.2 Complete when
- All in-scope workloads run in Azure.
- Every validation check passes.
- Open issues are resolved or formally accepted.
- Documentation is delivered.
- Example Co. confirms acceptance.
12Next steps
- Review this plan together and adjust the scope.
- Resolve the items marked “To confirm.”
- Finalize effort, schedule, and pricing.
- Approve the plan in writing.
- Schedule Discovery and the first change window.
Typical engagements
The kinds of projects Ops for Hire plans and delivers. These describe typical scope, not past clients.
-
Azure Cost Optimization
Review Azure resources, find spending you don’t need, and plan the changes by effort and risk.
Discuss a similar project -
Microsoft 365 Security Review
Assess identity, authentication, privileged access, and tenant security, with a remediation plan.
Discuss a similar project -
Azure Migration
Plan and execute the move of existing infrastructure into Azure, with a rollback path for every workload.
Discuss a similar project -
MSP Project Assistance
Senior engineering behind your service, working in your ticket queue and documentation format.
Discuss a similar project
What’s the project your team hasn’t had time to finish?
Describe what’s happening today and what you’re trying to accomplish, and get help working out the technical path forward.
- 1You get a reply by email from the engineer who would do the work.
- 2Follow-up questions cover only what changes the scope.
- 3If it’s a fit, you get a plan to review before any work starts.