If you have been following my blog you might have read this blog post I wrote back in September 2012 about a test drive I performed running a VDI Session-Based Desktop deployment on Windows Azure. Read it here: Running a Windows Server 2012 Remote Desktop Services environment on Azure.
Back then running Remote Desktop Services roles on Windows Azure was not officially supported (yet). Microsoft has recently changed their support statement on this, and therefore running a Session-Based Desktop Deployment on Windows Azure is now officially supported by Microsoft but can however only be licensed using SPLA. The PUR of July 2013 has been updated with the following statement;
Remote Desktop Services. Remote Desktop Services (RDS) Subscriber Access Licenses (SALs) purchased through the Microsoft Service Provider Licensing Agreement (SPLA) may be used to deliver graphical user interface functionality on Windows Azure virtual machines. RDS Client Access Licenses (CALs) purchased through other Volume Licensing programs including the Enterprise Agreement may not be used with Windows Azure virtual machines. Virtual Desktop Infrastructure functionality may not be used on Windows Azure virtual machines.
Link to the PUR: http://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=1
Looks like this may have changed over time.
ReplyDelete4.3 Remote Desktop Services (“RDS”) User CAL and User SL – Extended Rights
Customer may use its RDS User CALs and User SLs with Windows Server software running in OSEs dedicated to its internal use on either Microsoft Azure Platform Services or the shared servers of a License Mobility through Software Assurance Partner for which it has completed and submitted the License Mobility Validation form. Other than administrative access by Customer’s License Mobility through Software Assurance Partner, no other party may access the OSE(s). For any CAL or User SL Customer has used in this manner, it may later move to Microsoft Azure Platform Services or a new License Mobility through Software Assurance Partner, but not sooner than 90 days after it initiated use in the environment it is leaving.