AWS RDS and Microsoft Azure SQL Database are both web services that makes it easy to set up and scale a relational database in the Cloud. They are designed for developers or businesses that want cloud databases. AWS RDS vs Microsoft Azure SQL Database. GigaOm have held a GigaOM Transactional Field Test which aims at comparing the two databases.
Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016
Azure Rds Server
Below are various configurations for deploying Remote Desktop Services to host Windows apps and desktops for end-users.
- Use these steps to create your small-footprint RDS deployment from the Azure Marketplace: Launch the Azure Marketplace RDS deployment: Sign into the Azure portal. Click New to add your deployment. Type 'RDS' in the search field and press Enter. Click Remote Desktop Services (RDS) - Basic - Dev/Test, and then click Create.
- Secure and productive on Azure and Microsoft 365: Deploy a complete, intelligent solution that enhances creativity and collaboration for everyone. Shift to Microsoft 365 and get Office 365, Windows 10, and Enterprise Mobility + Security. RDS on-premises to Windows Virtual Desktop in the cloud goals.
- Installing an RDS on Windows Server appears to take many steps, but in reality is quite easy. I'd assume that you have a Domain Controller and RDS Services up and running on one or more servers. Make sure you fulfill the following requirements before publishing your RDS application to Azure. Your RDS is configured and running the RD roles.
- Windows Virtual Desktop combines the scale, security, and cost benefits of Azure and Microsoft 365 for a secure remote desktop from anywhere.
The architecture diagrams below show using RDS in Azure. However, you can deploy Remote Desktop Services on-premises and on other clouds. These diagrams are primarily intended to illustrate how the RDS roles are colocated and use other services.
Standard RDS deployment architectures
Remote Desktop Services has two standard architectures:
- Basic deployment – This contains the minimum number of servers to create a fully effective RDS environment
- Highly available deployment – This contains all necessary components to have the highest guaranteed uptime for your RDS environment
Highly available deployment
RDS architectures with unique Azure PaaS roles
Azure Rds Cal
Though the standard RDS deployment architectures fit most scenarios, Azure continues to invest in first-party PaaS solutions that drive customer value. Below are some architectures showing how they incorporate with RDS.
RDS deployment with Azure AD Domain Services
The two standard architecture diagrams above are based on a traditional Active Directory (AD) deployed on a Windows Server VM. However, if you don't have a traditional AD and only have an Azure AD tenant—through services like Office365—but still want to leverage RDS, you can use Azure AD Domain Services to create a fully managed domain in your Azure IaaS environment that uses the same users that exist in your Azure AD tenant. This removes the complexity of manually syncing users and managing more virtual machines. Azure AD Domain Services can work in either deployment: basic or highly available.
RDS deployment with Azure AD Application Proxy
Azure Rds Pricing
The two standard architecture diagrams above use the RD Web/Gateway servers as the Internet-facing entry point into the RDS system. For some environments, administrators would prefer to remove their own servers from the perimeter and instead use technologies that also provide additional security through reverse proxy technologies. The Azure AD Application Proxy PaaS role fits nicely with this scenario.
For supported configurations and how to create this setup, see how to publish Remote Desktop with Azure AD Application Proxy.