Mogo Azure eliminates the need for a local server by moving patient data to Microsoft Azure infrastructure. But it introduces a new dependency that many practices underestimate before they switch. Your internet connection becomes the most critical piece of infrastructure in the office, and your workstations need to meet spec before performance will be reliable.
Here is what your practice needs to run Mogo Azure correctly in 2026, with IT guidance for practices evaluating the platform or already running it.
Mogo Azure eliminates the local server requirement but makes your internet connection the most critical piece of infrastructure in the office.
Practices that switch from Mogo’s server-based version to Mogo Azure without upgrading their internet connection often experience slowdowns that get attributed to the software. The actual cause is insufficient bandwidth for cloud-based access. Upgrading workstations and internet before go-live is not optional.
Because Mogo Azure runs entirely in a browser, workstation requirements focus on processing power, RAM, and display rather than local storage.
Windows 11 Pro recommended. Windows 10 reached end of life in October 2025.
Windows 10 is no longer a compliant choice for a healthcare environment. Windows 11 Pro is the correct platform for any new workstation purchase in 2026. Mogo has historically supported Windows 10 but practices still running it should have an upgrade path in place.
Intel Core i5 or AMD Ryzen 5 for standard workstations. Core i7 for imaging stations.
A current-generation i5 or Ryzen 5 is sufficient for scheduling and billing workstations. Any workstation running Mogo alongside imaging software simultaneously should have a Core i7.
16GB minimum. Do not run Mogo Azure on 8GB RAM.
Mogo’s cloud interface runs in a browser, and browser-based platforms are memory-intensive. Running Mogo alongside imaging software and email on 8GB RAM will cause slowdowns. 16GB is the floor for any workstation in a cloud-first environment.
256GB SSD minimum.
Local storage requirements are low since patient data lives in Mogo’s Azure-hosted environment. A 256GB SSD covers imaging cache and operating system files without issue.
1280×1024 minimum per Mogo spec. 1920×1080 recommended.
1920×1080 is the practical standard for comfortable daily use of the scheduling and charting interfaces. 1280×1024 will work but is tight on the charting views.
Microsoft Edge or Google Chrome with automatic updates enabled.
Internet Explorer has been deprecated. Mogo Azure must be accessed through Edge or Chrome, both kept current. Disable browser update restrictions if any are applied by group policy.
Workstation specs alone do not determine Mogo Azure performance. Adequate internet bandwidth must be in place before the specs above will deliver reliable performance. See the internet requirements section below.
20 Mbps download and 10 Mbps upload per active workstation
A practice with six active workstations needs at least 120 Mbps download and 60 Mbps upload. Fiber is preferred for upload speed consistency.
Consistent speed matters more than peak speed
Mogo Azure on a stable 30 Mbps connection performs better than on a 100 Mbps cable connection that fluctuates under load.
An LTE failover device is essential for any cloud-based practice
Without a backup connection, an internet outage takes scheduling, billing, and patient records offline simultaneously.
Enterprise-grade cloud infrastructure with encryption, redundancy, and compliance certifications
Mogo Azure is built on Microsoft Azure and signs a Business Associate Agreement with covered entities as part of their standard service agreement. Platform-level encryption and redundancy are handled by the vendor.
Workstation encryption, MFA on all Mogo accounts, and documented network-level safeguards
Workstation-level and network-level technical safeguards remain the practice's responsibility. Your IT provider must configure encryption on every workstation, enable MFA on all Mogo user accounts, and document these controls for your HIPAA Security Risk Assessment.
Using a HIPAA-compliant cloud platform does not transfer your compliance obligations to the vendor. Your IT provider must configure and document workstation and network controls regardless of where patient data is hosted. If these controls are not in your current HIPAA Security Risk Assessment, they need to be added before your next audit or assessment.
Practices still running the server-based version of Mogo Windows require a dedicated server and should be working with their IT provider on a transition timeline.
Dedicated Windows Server required
The server must run Windows Server and cannot be used as a workstation. Your IT provider should confirm the installed version is still within Microsoft's support lifecycle.
Wired to the network (required)
The server must be hardwired to your office network. Wireless server connections are not supported and create reliability and security problems.
Current specs must be verified by your IT provider
If your practice is still running Mogo Windows on a server, your IT provider should confirm that hardware meets current specifications before assuming it is adequate for continued use.
Your IT provider should begin building a transition timeline to Mogo Azure where appropriate.
Audit server hardware and software. Confirm current specs and whether the installed Windows Server version is still supported before committing to a migration window.
Upgrade internet and workstations first. Mogo Azure requires fiber-grade internet and 16GB RAM workstations running Windows 11 Pro. Do not migrate until both are in place.
Install LTE failover before go-live. A backup internet connection is essential before cutting over to any cloud-based practice management platform.
Ekim IT Solutions works exclusively with dental practices. We serve New England and New York with on-site support and dental practices nationwide with remote support. We check your workstations, network configuration, and connectivity against Mogo's 2026 specifications and tell you exactly what needs attention before performance or compliance becomes a problem.