Update 3/17 - for a VM to have encountered this issue, among other factors, it would have had to have been created sometime between 2/27 and 3/9. As of 3/10, newly created VMs could've no longer seen this issue since an updated VM agent was being deployed during provisioning after that date.
If you encountered the issue on a VM and disabled the RdAgent service as a workaround, you should leave RdAgent disabled until the Windows Installer package (.MSI) is released and you can manually install the agent MSI package to resolve the issue overall for that VM.
-----------------
We are currently investigating an issue where the WaAppAgent.exe process spikes at 100% CPU. WaAppAgent.exe is the process for theRdAgent service, which is part of the VM Agent for Windows Azure Virtual Machines.
If you encounter this issue, you can change the Startup type for the RdAgent service to Disabled, clickApply, then click Stop to stop the service.
If the WaAppAgent.exe process is still running, right-click it inTask Manager and select End Process.
We are continuing to investigate the issue and will provide more information as it becomes available.
Thanks,
Craig