Migrating Practice Management Software To Azure Virtual Desktop
Summary
This guide helps you troubleshoot and resolve: Migrating Practice Management Software To Azure Virtual Desktop. Follow the steps below to fix the issue.
Common Causes
Migrating Practice Management Software to Azure Virtual Desktop
Moving practice management software to Azure Virtual Desktop centralises the clinical environment, simplifies patching, and ensures staff access a consistent session from the surgery, home, or temporary locations without duplicating sensitive patient files on local endpoints. This guide covers the migration process for Australian dental and medical practices, including compatibility considerations for common practice management software, bandwidth requirements, FSLogix configuration, and clinical device redirection.
Why Migrate from On-Premises Hardware?
Many dental and medical practices operate their practice management software from a physical server located in a cupboard or small office room. While this setup may have worked for years, it introduces ongoing costs and risks that cloud migration can eliminate.
Hidden Costs of On-Premises Hardware
- Air conditioning and ventilation to keep server room temperatures stable
- Uninterruptible Power Supply (UPS) units and regular battery replacements
- Replacement parts such as hard drives, power supplies, and cooling fans
- Hardware warranty renewals and extended support contracts
- Physical security and access controls for the server location
- Electricity costs for running hardware 24 hours a day, seven days a week
By migrating files, identity, and applications to Microsoft 365 and Azure cloud tiers, your organisation shifts from unpredictable capital expenditure to a predictable operational model. Microsoft manages the underlying hardware, power, cooling, and physical security, allowing your practice to focus on patient care rather than server maintenance.
Practice Management Software Compatibility
Common Australian practice management applications, including Best Practice Software and MedicalDirector, can be hosted on Azure Virtual Desktop. Before beginning migration, verify the specific version requirements with your software vendor.
Best Practice Software
Best Practice typically runs on Windows Server with a SQL backend. On Azure Virtual Desktop, install the application on a session host image and publish it as a RemoteApp. Ensure the SQL connection string points to the Azure-hosted database or an Azure SQL Managed Instance. Test patient record loading and billing functions during the pilot phase.
MedicalDirector
MedicalDirector Clinical and Practice Manager often rely on local drive mappings and specific printer configurations. When deploying on Azure Virtual Desktop, test the Helix and Classic interfaces within a virtual session. Confirm that clinical document scanning and electronic prescribing integrations function correctly before cutover.
Network and Bandwidth Requirements
Azure Virtual Desktop performance depends on stable internet connectivity at each surgery location. Use the following guidelines when assessing your network:
- Minimum bandwidth: 5 Mbps download and 2 Mbps upload per concurrent session
- Recommended bandwidth: 10 Mbps download and 5 Mbps upload per concurrent session
- Latency: Round-trip latency to the Azure region should remain under 150 milliseconds for acceptable clinical application responsiveness
- Jitter: Keep network jitter below 30 milliseconds to prevent session disconnections
Run speed tests from each surgery location during peak clinic hours to confirm sustained performance. If latency exceeds acceptable thresholds, consider deploying session hosts in the Azure region closest to your practice (typically Australia East or Australia Southeast).
Migration Overview
Moving to Azure Virtual Desktop involves several key stages. Each stage should be planned carefully to minimise disruption to clinical operations.
Phase 1: Assessment and Planning
- Audit your current practice management software to confirm compatibility with Azure Virtual Desktop. Contact your software vendor to verify support for virtualised environments.
- Identify all user roles and the applications they require within their virtual session, including clinical, reception, and billing staff.
- Assess your internet connection at each surgery location using the bandwidth and latency requirements listed above.
- Document existing file shares, permissions, and folder structures used by clinical and administrative staff.
- Plan your identity strategy by syncing on-premises Active Directory with Microsoft Entra ID (formerly Azure Active Directory) using Microsoft Entra Connect.
Phase 2: Azure Environment Setup
- Provision an Azure subscription and create a resource group for your virtual desktop infrastructure.
- Deploy a virtual network that connects securely to your practice via site-to-site VPN or ExpressRoute.
- Create a host pool in Azure Virtual Desktop. In the Azure portal, navigate to Azure Virtual Desktop > Host pools > Create, and configure session hosts based on your user capacity requirements.
- Set up FSLogix profile containers. In the Azure portal, navigate to Azure Virtual Desktop > Host pools > [Your host pool] > FSLogix settings. Configure an Azure Files share for profile storage and set the
VHDLocationsregistry key or Group Policy Object to point to the Azure Files path. EnableSizeInMBquotas to prevent uncontrolled profile growth. - Configure Azure Files or Azure NetApp Files for shared practice data that multiple users need to access simultaneously.
Phase 3: Application Installation and Testing
- Install your practice management software on a golden image within the Azure environment. Use Sysprep to generalise the image before capturing it.
- Configure application shortcuts and published applications. In the Azure portal, navigate to Azure Virtual Desktop > Application groups > Add applications and publish the practice management executable so staff can launch it directly from the Azure Virtual Desktop client.
- Test printing from the virtual session to network printers located in the surgery. Enable printer redirection in the RDP properties and verify that clinical labels, referral letters, and prescriptions print to the correct tray.
- Verify that scanning and document import functions work correctly within the virtual environment. Configure scanner redirection or use TWAIN-compatible scanning through the Azure Virtual Desktop client.
- Conduct user acceptance testing with a small group of clinicians and administrative staff before full rollout.
Phase 4: User Migration and Cutover
- Assign users to the appropriate host pool and application groups in Azure Virtual Desktop.
- Install the Azure Virtual Desktop client on staff endpoints, or use the web client via a browser at
https://rdweb.microsoft.com. - Migrate user data from local file servers to Azure cloud storage, maintaining existing permissions where possible using Azure Storage Explorer or AzCopy.
- Schedule the final cutover outside of peak clinic hours to minimise impact on patient appointments.
- Decommission the physical server only after confirming all users can access applications and data successfully.
Printer and Scanner Redirection for Clinical Devices
Clinical environments often rely on specific printers for prescriptions, referral letters, and patient labels. Configure device redirection carefully to avoid workflow interruptions.
Printer Redirection Steps
- In the Azure portal, navigate to Azure Virtual Desktop > Host pools > [Your host pool] > RDP properties.
- Ensure
redirectprinters:i:1is enabled to allow local printers to appear in the virtual session. - Install the correct printer drivers on the Azure session host. Download manufacturer drivers for your clinical label printers and network multifunction devices.
- Test printing from the published practice management application to each physical printer in the surgery.
- Verify default printer selection persists between sessions for clinical staff.
Scanner Redirection Steps
- Connect the scanner to the staff endpoint via USB.
- In the Azure Virtual Desktop client, enable local device redirection before connecting to the session.
- Test document import directly from the scanner into the practice management software.
- If direct scanner redirection fails, scan to a network folder or Azure Files share and import the document from within the virtual session.
Security and Compliance Considerations
Patient health information is sensitive and subject to strict privacy obligations under the Australian Privacy Act and the Notifiable Data Breaches scheme. Azure Virtual Desktop helps your practice meet these requirements by keeping data within the datacentre rather than on local endpoints.
- Enable multi-factor authentication for all users accessing virtual desktops.
- Use conditional access policies to restrict sign-ins to approved locations and compliant devices.
- Encrypt data at rest and in transit using Azure Storage Service Encryption and TLS.
- Implement role-based access control so staff only access the data and applications relevant to their role.
- Enable Azure Monitor and Microsoft Defender for cloud to detect and respond to potential security threats.
Ongoing Management
Once your physical server is retired, your IT partner manages patching, updates, and infrastructure maintenance through the Azure portal. Your practice no longer needs to worry about hardware failure, warranty expirations, or server room environmental controls.
If you need assistance planning or executing your migration to Azure Virtual Desktop, Open a Ticket.
Related guides:
- Installing the Azure Virtual Desktop client
- FSLogix profile container configuration
- Printer redirection in Azure Virtual Desktop
- Hybrid join with Microsoft Entra ID
- Bandwidth and latency testing for virtual desktops
Still Having Issues?
💻 Open a Ticket