@shanselman @WindowsAzure and its fixed. Gotta love Azure support. Turns out issue with having 2 MSDN subs the way I have