Home › Knowledgebase › KB-1131

Stop the VPN Lag: Replacing Slow Remote Desktop Connections with Cloud-Native Access

Summary

This guide helps you troubleshoot and resolve: Stop the VPN Lag: Replacing Slow Remote Desktop Connections with Cloud-Native Access. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Replacing VPN and Remote Desktop Connections with Cloud-Native Access

Many Australian small businesses rely on traditional Virtual Private Networks (VPNs) and Remote Desktop Protocol (RDP) to connect remote staff to office servers. While these tools were once the industry standard, they frequently introduce significant latency, connection drops, and security vulnerabilities. Cloud-native access removes the need for a central server tunnel, allowing your team to access applications and data directly and securely from anywhere with an internet connection.

Pre-Migration Checklist

Before decommissioning your VPN and moving to a cloud-native environment, complete the following prerequisites to ensure a smooth transition and compliance with Australian regulations.

1. Internet Bandwidth Requirements

2. Licensing and Subscription Planning

3. Entra ID Planning

4. Data Sovereignty and Privacy

Australian Data Sovereignty: Australian small businesses must consider where their data is stored to meet obligations under the Australian Privacy Act 1988. When using Microsoft Azure or Microsoft 365, verify that your tenant is configured to store data in Australian regions (such as Australia East or Australia Southeast) if required by your industry or client contracts. Review your service provider's terms to ensure data residency aligns with your privacy obligations.

Transitioning to Cloud-Native Access

Cloud-native access typically involves moving file shares and applications to a cloud environment, such as Microsoft 365, Azure Virtual Desktop, Google Workspace, or AWS WorkSpaces, eliminating the need for a constant VPN tunnel.

  1. Audit on-premise resources: Identify which applications, file shares, and databases must be migrated to the cloud.
  2. Migrate file shares: Move data from local servers to OneDrive for Business or SharePoint Online using the SharePoint Migration Tool or a third-party migration utility.
  3. Configure Entra ID: Sign in to the Entra admin center (entra.microsoft.com), navigate to Users, and synchronize or create user accounts for single sign-on access.
  4. Provision virtual desktops (optional): In the Azure portal (portal.azure.com), deploy Azure Virtual Desktop session hosts and assign users to the appropriate application groups.
  5. Install client applications: Deploy the Microsoft Remote Desktop app from the Microsoft Store or Apple App Store for cloud session handling, or use web-based portals for Google Workspace and AWS WorkSpaces.
  6. Verify access: Test cloud access from a remote device before removing legacy VPN clients.
  7. Decommission VPN: Remove the legacy VPN client from end-user devices once cloud access is verified and secure.

Critical Security: Protecting Cloud Access Before VPN Removal

Security Warning: Do not remove your VPN or expose cloud resources to the internet until you have secured your identity provider. Without Conditional Access and Multi-Factor Authentication (MFA), your cloud environment is vulnerable to credential stuffing and unauthorized access.

Before decommissioning your VPN, implement the following security controls in the Entra admin center:

  1. Enforce Multi-Factor Authentication: Navigate to Protection > Multifactor authentication and enable MFA for all user accounts.
  2. Configure Conditional Access policies: Navigate to Protection > Conditional Access. Create policies that require compliant devices, block sign-ins from high-risk locations, and enforce MFA for cloud applications.
  3. Implement device compliance: Use Microsoft Intune or a similar mobile device management solution to ensure only managed and compliant devices can access corporate resources.
  4. Review sign-in logs: Regularly monitor Monitoring > Sign-in logs in the Entra admin center for suspicious authentication attempts.

Temporary RDP Optimization During Transition

If you must continue using Remote Desktop during the migration period, adjust these settings to reduce lag. These steps are intended as a temporary measure only.

  1. Open the Remote Desktop Connection app on your Windows device.
  2. Click Show Options to expand the connection settings.
  3. Navigate to the Experience tab.
  4. Select Low-speed broadband from the drop-down menu. This disables visual effects such as desktop background, window contents dragging, and menu animations.
  5. Clear the following visual effect checkboxes if they remain enabled: Desktop background, Show contents of window while dragging, Menu and window animation, and Themes.
  6. Go to the Display tab and reduce the screen resolution and colour depth to lower the bandwidth requirement.
  7. Click Connect to apply the settings.

Important: Do not select the outdated Modem (56 Kbps) setting. This extreme option severely degrades the user experience and is unsuitable for modern business applications.

Troubleshooting Cloud-Native Access

Entra ID Sign-In Failures

Azure Virtual Desktop Connectivity

OneDrive and SharePoint Sync Conflicts

Tip: Encourage staff to use web-based versions of Office apps (Office.com) whenever possible. This removes the need for a remote desktop session entirely for document editing.

Caution: Do not open RDP ports (port 3389) on your firewall to allow remote access. This exposes your organisation to brute-force attacks and ransomware. Always use a secure gateway or cloud-native access method.

If you require assistance planning your migration to cloud-native access or need help configuring secure remote connections for your team, please Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket