Windows Azure Portal login to portal and receive error "We are having trouble logging you into the portal"

user2207063 picture user2207063 · Mar 25, 2013 · Viewed 10k times · Source
  1. Open browser
  2. Navigate to http://www.windowsazure.com/en-us/
  3. Select portal top right
  4. login with my email address
  5. Receive the below error

https://manage.windowsazure.com/Error/Login?getsupport=true&f=255&MSPPError=-2147217320

Receive the error " We are having trouble logging you into the portal Please contact Customer Service for assistance."

Using IE or Chrome, incognito or not, cookies cleared or not, cache cleared or not. The problem still exists. Also tried on multiple devices media centre PC, desktop running windows 7, iPhone 5, ipad 3...

Prior to November 2012 I have accessed the windows azure subscription without a problem.

I clicked the customer service link and the australian number is 13 20 58 I have contacted that number explaining that I cannot access my windows azure subscription and each time I login I receive an error. They proceed to redirect me to other support teams where I repeat my details and the problem they either redirect me again or provide a number to call. In one case I was redirected to a number that no longer exists. Another I was told to raise a case on the windows azure portal page the same portal page that I receive an error on when logging in, when I asked for alternative options there were none. So far I've spoke with the msdn support team, windows subscription support, online services, etc and still no resolution. In the latest call to support they have said to raise the issue on the forums so here goes.

Anyways long story short I have probably spent 3+ hours calling Microsoft support explaining the problem, waiting on hold, being redirect, repeating... still I can't access my windows azure subscription

I checked in commerce.microsoft.com and there is a windows azure subscription associated with my email address Subscription-1 Windows Azure MSDN - Visual Studio Premium

Does anyone have any suggestions on how to resolve this issue?

Answer

Biren picture Biren · Oct 31, 2020

Some time it's happened wait for while and retry

or just ask azure support in twitter