Azure Virtual Desktop or On-Premises Infrastructure: The Direct Answer
Architecture firms should consider Azure Virtual Desktop when remote access, multiple offices, centralized security, rapid onboarding, or flexible computing capacity are major priorities. Firms should generally keep high-performance Revit workstations and supporting infrastructure on-premises when most employees work from one office, local performance is excellent, internet connectivity is limited, or predictable ownership costs matter more than cloud flexibility.
For many 25–50 person firms, the best answer is not fully cloud or fully on-premises. A hybrid architecture often provides the strongest balance: physical workstations for full-time office users, cloud-hosted desktops for remote employees and contractors, centralized identity through Microsoft 365, and an approved BIM collaboration platform for shared Revit models.
The correct decision should be based on five factors:
- User location and work patterns
- Revit and visualization performance requirements
- Monthly cloud cost versus hardware lifecycle cost
- Cybersecurity and business continuity requirements
- Internal or outsourced IT management capacity
The Four Main Revit Infrastructure Options
| Option | Best Fit | Main Advantage | Main Limitation |
|---|---|---|---|
| Physical workstations with local infrastructure | Employees working primarily from one office | Strong performance and predictable hardware ownership | Remote access and disaster recovery require additional planning |
| Azure Virtual Desktop | Remote teams, multiple offices, contractors, and centralized management | Applications and data can remain in a controlled cloud environment | Ongoing Azure cost and design complexity |
| Cloud workstations | Individual remote power users or temporary employees | Fast deployment without purchasing a physical workstation | Recurring cost can exceed physical hardware over time |
| Hybrid infrastructure | Firms with mixed office, remote, and project requirements | Each employee receives the environment that fits the workload | Requires clear standards and more deliberate management |
What Is Azure Virtual Desktop?
Azure Virtual Desktop is a Microsoft service that allows businesses to run Windows desktops and applications in Azure. Instead of running Revit entirely on a computer beneath an employee's desk, the application can run on a cloud-hosted virtual machine. The employee connects to that environment from an office computer, laptop, thin client, or approved personal device.
The actual Revit processing occurs in Azure. The user's screen, keyboard, mouse, and other approved inputs are transmitted through the remote session.
A properly designed environment may include:
- GPU-enabled Azure virtual machines
- Microsoft Entra ID authentication
- Multi-factor authentication
- Conditional Access policies
- Centralized user profiles
- Application deployment and patching
- Cloud file storage or BIM collaboration platforms
- Endpoint security and centralized monitoring
- Automated startup and shutdown schedules
- Backup and disaster recovery procedures
911 IT supports cloud adoption, virtual desktops, Microsoft 365, secure remote access, and cloud infrastructure through its cloud services.
The Five-Step Revit Infrastructure Decision Framework
1. Map Where Employees Actually Work
Begin with employee behavior rather than technology preferences.
Document how many employees work:
- Full time from the main office
- From a second or third office
- From home several days per week
- Fully remote
- From project sites
- As temporary contractors
- Across different states or countries
A firm with 40 employees working from one office has a different business case from a 40-person firm distributed across three offices and 15 home locations.
Physical workstations often remain the simplest solution for employees who work in one office every day. Azure Virtual Desktop becomes more attractive as the number of locations, remote users, contractors, and shared resources increases.
2. Categorize Revit and Visualization Workloads
Not every employee requires the same virtual machine or workstation. Assign users to workload tiers before estimating cost.
| Workload | Typical Activities | Infrastructure Considerations |
|---|---|---|
| Light | Model review, markups, documentation, meetings, and occasional Revit use | May work well on a moderately sized virtual desktop |
| Standard production | Daily Revit modeling, documentation, AutoCAD, Bluebeam, Teams, and web applications | Requires strong processor performance, adequate memory, and a capable GPU |
| Advanced BIM | Large linked models, point clouds, coordination, worksets, and multiple Revit versions | Requires higher memory, storage performance, and careful testing |
| Visualization | Enscape, Twinmotion, Lumion, 3ds Max, rendering, and virtual reality | Requires substantial GPU resources and may be expensive in the cloud |
| BIM management | Auditing, troubleshooting, standards, coordination, and application administration | Requires flexibility, multiple applications, and access to representative project data |
Standard Revit production can work well in a properly configured Azure environment. Heavy visualization and rendering can also work, but GPU-enabled cloud computing may create high recurring costs. Test representative models and rendering tools before committing to a broad migration.
3. Compare Total Cost Over Three to Five Years
Do not compare only the purchase price of a physical workstation with one month of Azure service. Build a three-to-five-year total cost of ownership model.
For physical workstations, include:
- Computer purchase
- Monitors and peripherals
- Warranty
- Deployment labor
- Replacement cycle
- Office power and cooling
- Repairs and spare equipment
- Server and network infrastructure
- Backup and disaster recovery
- Remote-access tools
For Azure Virtual Desktop, include:
- Virtual machine compute
- GPU resources
- Managed disks and profile storage
- Network traffic
- Backup
- Security and monitoring
- Microsoft licensing
- Implementation
- Ongoing administration
- After-hours or full-time machine availability
- Reserved capacity or savings plans when appropriate
A physical Revit workstation may cost several thousand dollars upfront but remain useful for four or five years. A cloud workstation avoids a large initial purchase but creates a monthly expense that continues as long as the resource exists.
The cloud can be financially attractive when virtual machines are automatically shut down outside working hours, temporary users need access for limited periods, or capacity changes frequently. It can become expensive when high-performance GPU systems run continuously.
4. Evaluate Security and Recovery Requirements
Azure Virtual Desktop can improve security by keeping applications and project information inside a managed cloud environment. However, moving to Azure does not make the firm secure automatically.
A secure deployment should include:
- Multi-factor authentication
- Conditional Access
- Separate administrator accounts
- Endpoint detection and response
- Device compliance policies
- Controlled clipboard, drive, and printer redirection
- Encryption
- Centralized logging
- Vulnerability and patch management
- Backup and recovery testing
- Documented incident response
The firm must also secure the device used to access the virtual desktop. A compromised home computer can still expose credentials, screenshots, downloads, or active sessions.
911 IT helps businesses strengthen identity, endpoints, email, networks, and cloud systems through its cybersecurity services.
5. Measure Management Complexity
Azure Virtual Desktop is not a product that should be configured once and ignored. It requires ongoing management.
Typical responsibilities include:
- Monitoring performance and cost
- Updating applications
- Managing user profiles
- Maintaining virtual machine images
- Assigning users to appropriate resources
- Reviewing storage growth
- Managing Autodesk and Microsoft licensing
- Investigating session problems
- Testing backups
- Maintaining security policies
- Adjusting capacity
A firm with limited internal cloud expertise should include managed administration in its cost and implementation plan. 911 IT's managed IT services can provide ongoing monitoring, support, security, technology management, and strategic planning.
Azure Virtual Desktop Advantages for Architecture Firms
Centralized Applications and Data
Applications, user profiles, and supporting data can be managed centrally. This can reduce the need to store project information on remote laptops and simplify application deployment.
Faster Onboarding for Remote Employees
A virtual desktop can be assigned without shipping a high-performance workstation to every temporary employee or contractor. Access can also be removed centrally when the engagement ends.
Support for Multiple Offices
When users connect to the same Azure environment, the firm can reduce its dependence on transferring large files between office locations.
Flexible Capacity
Virtual machines can be resized or added as workloads change. This can be useful for rapid hiring, short-term projects, acquisitions, and seasonal demand.
Business Continuity
Employees may be able to connect from another approved device when an office is unavailable. This can support continuity during hardware failures, office closures, or localized disruptions.
Centralized Security Controls
Identity, access, patching, monitoring, and application policies can be managed consistently. The firm can also limit which information is copied to local devices.
Azure Virtual Desktop Limitations
Internet Dependency
Users need a reliable connection with adequate bandwidth, low latency, and limited packet loss. A virtual desktop may feel unresponsive even when the Azure resources are powerful if the employee's connection is poor.
Recurring Cloud Cost
High-performance virtual machines with GPU resources can be expensive, especially when they run continuously. Cost controls and automated shutdown schedules are essential.
Design Complexity
User profiles, storage, virtual networks, security, application images, scaling, monitoring, and backup must work together. A poor design can create login delays, application problems, and unpredictable expenses.
Peripheral and Display Requirements
Plotters, scanners, specialized mice, 3D controllers, cameras, multiple high-resolution displays, USB devices, and other peripherals must be tested.
Visualization Performance
Real-time rendering and virtual reality can require powerful GPU resources. Some visualization workflows may perform better or cost less on a dedicated physical workstation.
Licensing
Microsoft, Autodesk, rendering, plug-in, and third-party application licenses must permit the intended virtual environment. Licensing assumptions should be verified before implementation.
Advantages of On-Premises Revit Workstations
- Strong local performance
- Low latency between user and workstation
- Predictable hardware cost
- No cloud compute charge while the employee works
- Better support for specialized peripherals
- Simpler ownership model for a single-office firm
- Potentially stronger performance for rendering and visualization
- Continued local work during some internet outages
Physical workstations remain an excellent solution when employees work primarily from a well-designed office with fast networking, stable power, reliable storage, and a tested recovery plan.
Limitations of On-Premises Infrastructure
- Large upfront hardware purchases
- Workstations must be replaced every few years
- Remote access requires additional tools and security
- Hardware failures can interrupt an employee until repair or replacement
- Multiple offices may duplicate infrastructure
- Servers, storage, networking, and backup require management
- Office disruptions can affect local equipment
- Temporary users may require additional hardware
On-premises does not mean outdated. A modern local environment can include cloud identity, Microsoft 365, Autodesk cloud collaboration, managed security, cloud backup, and remote support while retaining physical Revit workstations.
Azure Virtual Desktop Versus Physical Workstations
| Decision Factor | Azure Virtual Desktop | Physical Workstations |
|---|---|---|
| Initial cost | Usually lower hardware investment | Higher upfront purchase |
| Ongoing cost | Recurring compute, storage, and management | Lower recurring compute cost after purchase |
| Remote work | Strong when properly designed | Requires VPN, remote desktop, cloud collaboration, or other access |
| Office performance | Depends on internet and session design | Strong local response |
| Scaling | Resources can be added or resized | Requires purchasing and deploying hardware |
| Temporary employees | Good fit for rapid provisioning | May require purchasing or maintaining spare equipment |
| Rendering | Possible but can be costly | Often strong value for regular heavy rendering |
| Centralized management | Applications and desktops can be centrally administered | Requires endpoint management across individual systems |
| Internet outage | Users may lose access | Some local work can continue |
| Hardware lifecycle | Azure resources can be changed without replacing a user workstation | Systems require planned replacement |
When Azure Virtual Desktop Is Usually the Better Choice
Azure Virtual Desktop should receive serious consideration when several of the following are true:
- More than one-third of employees work remotely
- The firm operates multiple offices
- Project information must remain in a centrally controlled environment
- The firm frequently hires temporary employees or contractors
- Hardware shipping and remote setup create delays
- Employees need secure access from different approved devices
- The organization already uses Microsoft 365 and Azure services
- Business continuity is a high priority
- Workload demand changes significantly by project
- The firm has access to experienced Azure management
When Physical Workstations Are Usually the Better Choice
Physical workstations may be the better option when several of the following are true:
- Most employees work from one office
- The office has reliable local infrastructure
- Users perform heavy rendering or visualization every day
- Internet service is unreliable or high-latency
- Specialized peripherals are essential
- The firm prefers predictable capital purchases
- Existing workstations are modern and productive
- The organization lacks the resources to manage Azure properly
- Cloud operating costs would exceed the value of added flexibility
When a Hybrid Model Is the Best Answer
A hybrid model allows the firm to match technology to each employee and project.
For example:
- Office-based production architects use physical Revit workstations
- Remote employees use Azure Virtual Desktop
- Temporary consultants receive time-limited cloud desktops
- Visualization specialists use high-end local workstations
- Revit models are managed through Autodesk cloud collaboration
- Microsoft Entra ID controls access
- Microsoft 365 supports communication and business documents
- Cloud backup protects critical systems
This approach can reduce unnecessary Azure spending while preserving centralized access for users who benefit from it.
A Six-Step Azure Virtual Desktop Migration Plan
Step 1: Complete a Workload Assessment
Inventory employees, devices, applications, plug-ins, model sizes, locations, peripherals, security requirements, and support needs.
Step 2: Build a Cost Model
Estimate compute, storage, licensing, network, backup, security, implementation, and ongoing management. Compare the total against physical workstation replacement and local infrastructure costs.
Step 3: Design the Environment
Select virtual machine types, GPU resources, profile storage, network architecture, authentication, security controls, backup, scaling, and monitoring.
Step 4: Run a Pilot
Begin with three to five representative employees rather than migrating the entire firm at once. Include at least one standard Revit user, one advanced user, and one remote employee.
Step 5: Measure Results
Compare model opening, synchronization, navigation, printing, rendering, login time, user satisfaction, support incidents, and actual Azure spending.
Step 6: Expand in Controlled Groups
Resolve pilot issues before moving additional users. Maintain a rollback plan until the new environment is proven.
What to Test During an Azure Virtual Desktop Pilot
- Login time
- Revit launch time
- Model opening time
- Synchronization performance
- Linked-model performance
- Point-cloud performance
- Rendering speed
- Multi-monitor behavior
- Plotter and printer access
- Bluebeam and PDF workflows
- Autodesk licensing
- Application plug-ins
- Teams calls and audio
- File uploads and downloads
- Profile reliability
- Actual cost per user
- Performance from each employee location
Use real project files rather than a small demonstration model. A test that ignores the firm's largest active project will not produce a reliable decision.
Common Azure Virtual Desktop Mistakes
Choosing the Smallest Virtual Machine to Save Money
Undersized resources create poor performance, employee frustration, and failed adoption. Start with realistic workload requirements and optimize after collecting data.
Leaving Every Virtual Machine Running All Day and Night
Azure costs continue while resources run. Use scaling plans, automated shutdown, and usage monitoring where appropriate.
Using One Configuration for Every Employee
Light users, production architects, BIM managers, and visualization specialists require different resources. Create approved performance tiers.
Ignoring Profile and Storage Design
Slow or unreliable profiles can make an otherwise powerful virtual machine feel unusable. Profile storage and application caches must be designed for the workload.
Assuming Internet Speed Is the Only Network Metric
Latency, packet loss, Wi-Fi quality, and connection consistency can matter as much as advertised download speed.
Skipping Application and Plug-In Testing
Revit add-ins, rendering software, licensing systems, printers, and specialty devices may behave differently in a virtual environment.
Failing to Monitor Cost
Cloud bills can grow through oversized machines, unused disks, snapshots, backups, data transfer, and resources left running.
Moving Every User at Once
A staged pilot reduces risk and provides real performance and cost information before the firm commits broadly.
Cybersecurity Requirements for Virtual Revit Environments
| Security Area | Recommended Control |
|---|---|
| Authentication | Multi-factor authentication and Conditional Access |
| Administration | Separate administrator accounts and least-privilege access |
| Endpoints | Managed devices, encryption, endpoint detection and response, and patching |
| Sessions | Controlled clipboard, local drive, USB, and printer redirection |
| Network | Restricted access paths, monitored traffic, and secure virtual networks |
| Data | Role-based access, backup, retention, and recovery testing |
| Logging | Centralized sign-in, administrative, security, and resource logs |
| Incident response | Documented procedures for compromised accounts, ransomware, and data exposure |
Business Continuity Questions to Answer
- What happens if the main office loses internet access?
- What happens if Azure experiences a service interruption?
- Can users connect from another approved device?
- How are user profiles and project files backed up?
- How quickly can a failed virtual machine be replaced?
- Which systems can continue operating without Azure?
- What is the recovery time objective?
- What is the acceptable amount of data loss?
- Who manages an after-hours outage?
- When was the recovery plan last tested?
A cloud platform can improve resilience, but only when the surrounding architecture, backup, and operating procedures are designed and tested. Learn more about recovery planning through 911 IT's business continuity services.
Example: A 35-Person Architecture Firm
Consider a 35-person architecture firm with 20 employees in its Salt Lake City office, 8 hybrid employees, 4 fully remote employees, and 3 visualization specialists.
A practical hybrid design could include:
- Physical Revit workstations for the 20 primarily office-based employees
- Azure Virtual Desktop for the 4 fully remote employees
- A choice of managed laptops or virtual desktops for the 8 hybrid employees based on their workload
- High-end local workstations for the 3 visualization specialists
- Autodesk cloud collaboration for active Revit models
- Microsoft Entra ID and multi-factor authentication for identity security
- Managed endpoint protection on office and remote devices
- Automated Azure shutdown outside approved hours
- Monthly review of performance and cloud spending
- Tested backup and recovery procedures
This model avoids paying for high-performance cloud GPU resources for every employee while providing secure, centralized access to users who benefit most.
An Infrastructure Decision Scorecard
Score each category from one to five. A higher Azure score supports virtual desktops. A higher physical-workstation score supports local infrastructure.
| Category | Azure Virtual Desktop Scores Higher When | Physical Workstations Score Higher When |
|---|---|---|
| User location | Employees are distributed | Employees work mainly from one office |
| Workload | Work is standardized and suitable for available Azure resources | Heavy visualization or specialized peripherals dominate |
| Internet | Connections are reliable and low-latency | Internet is inconsistent or unavailable |
| Growth | Headcount changes quickly | Staffing is stable |
| Contractors | Temporary access is common | Nearly all users are long-term employees |
| Budget preference | Recurring operational spending is preferred | Capital purchases and predictable ownership are preferred |
| Security | Centralized sessions and restricted local data are priorities | Local systems are already strongly managed |
| Management | Experienced Azure support is available | The firm has stronger endpoint and local infrastructure expertise |
Questions to Ask an Azure or IT Provider
- Which users should move to Azure Virtual Desktop, and which should remain on physical workstations?
- Which Azure virtual machine types are recommended for each workload?
- How much memory and GPU capacity will each user receive?
- Will users share a session host or receive dedicated virtual machines?
- How will Revit profiles, caches, add-ins, and settings be managed?
- Where will active models and supporting project files be stored?
- How will Autodesk and Microsoft licensing work?
- What is the estimated monthly cost per user?
- What assumptions were used to calculate the estimate?
- How will machines be shut down or scaled outside working hours?
- How will cost overruns be detected?
- Which security controls are included?
- How will remote endpoints be protected?
- How are profiles, data, and virtual machines backed up?
- What happens during an Azure or internet outage?
- How will printers, plotters, scanners, and 3D devices work?
- What performance tests will be included in the pilot?
- Who provides support after deployment?
- What is the rollback plan?
- Can the provider show actual experience supporting BIM or engineering workloads?
Frequently Asked Questions
Can Autodesk Revit run on Azure Virtual Desktop?
Yes. Revit can run in a properly designed Azure virtual desktop environment with suitable processor, memory, GPU, storage, networking, operating system, and licensing. The complete application workflow should be tested before broad deployment.
Is Azure Virtual Desktop faster than a physical workstation?
It can be, but it is not automatically faster. Performance depends on the Azure virtual machine, GPU, storage, user profile, model location, internet connection, latency, and application configuration. A high-end physical workstation may outperform a cost-constrained virtual desktop.
Is Azure Virtual Desktop cheaper than buying computers?
Sometimes. It can be cost-effective for temporary users, variable workloads, remote employees, and machines that shut down when unused. Continuous high-performance GPU usage may cost more than purchasing a physical workstation over several years.
Does Azure Virtual Desktop eliminate the need for employee computers?
No. Employees still need a device, monitors, keyboard, mouse, webcam, and network connection. The access device may be less powerful than a full Revit workstation, but it must still be secure, reliable, and support the required peripherals.
Can employees use personal computers to access Azure Virtual Desktop?
Technically they may be able to, but firms should define device and security requirements. Sensitive projects may require company-managed devices, device compliance, restricted downloads, and Conditional Access.
How much internet bandwidth does each user need?
There is no universal number. Requirements depend on screen resolution, number of monitors, video, audio, application behavior, and other traffic. Low latency, minimal packet loss, and stable connectivity are as important as raw bandwidth.
Should rendering be performed in Azure?
Azure can support rendering, but the financial case depends on GPU size, rendering duration, frequency, and shutdown controls. Firms with constant heavy rendering may receive better long-term value from dedicated physical workstations or a separate rendering strategy.
Can Azure Virtual Desktop support multiple monitors?
Yes, but the user experience depends on the endpoint, client software, connection quality, display resolution, GPU resources, and session configuration. Test the firm's actual monitor standard during the pilot.
Does Azure Virtual Desktop replace Autodesk Construction Cloud?
No. They solve different problems. Azure Virtual Desktop provides a hosted Windows environment. Autodesk Construction Cloud and BIM Collaborate Pro support project and model collaboration. A firm may use both together.
Should every employee move to Azure at the same time?
No. Begin with a pilot of representative users, validate performance and cost, correct problems, and expand in controlled groups.
How to Make the Decision in the Next 30 Days
- List every Revit user, location, role, and application.
- Group users into light, standard, advanced BIM, and visualization tiers.
- Document workstation ages and planned replacement dates.
- Measure internet performance from every office and remote location.
- Calculate three-to-five-year physical workstation costs.
- Build a complete Azure estimate including compute, storage, licensing, backup, security, and management.
- Select three to five employees for a pilot.
- Test representative models, plug-ins, printers, monitors, and rendering tools.
- Compare performance, support effort, user satisfaction, and actual cost.
- Choose physical, virtual, or hybrid standards for each user tier.
Build a Revit Infrastructure Plan That Fits the Firm
The decision between Azure Virtual Desktop and on-premises infrastructure should not be based on a general preference for cloud or physical hardware. It should be based on measurable performance, complete costs, security, employee location, support requirements, and business risk.
911 IT helps architecture and engineering firms evaluate Revit workstations, Azure environments, remote access, Microsoft 365, cybersecurity, networking, and business continuity as one connected strategy. Relevant services include cloud services, managed IT services, cybersecurity services, and IT support for engineering firms.
Schedule a 10-minute discovery call to compare physical workstations, Azure Virtual Desktop, and hybrid infrastructure for your firm's actual Revit workloads.
