Error 80045C17 when trying to login at Azure to manage account - azure

Everytime I try to login im my azure account (http://manage.windowsazure.com/), I keep receiving the same error 80045C17, and the error message says nothing more then ask my to try later.
I Tried Every possible browser and the same result comes everytime!
I use the same username to log at every microsoft service.
I can't even stop my sites!
How to fix this?

I was able to fix this by first signing in to http://msdn.microsoft.com and then go to https://manage.windowsazure.com . It is using your Microsoft Live login session anyway so you have to log in to anything Microsoft. For example login.live.com
I think it happened to me because the azure portal was currently opened on another machine with the same account. Make sure you always sign out when you end using the Azure portal.
Thanks,
Alex Vezenkov

Related

Publish Azure Function

When I attempt to publish to Azure, a durable function, I am asked for credentials.
When I enter the credentials correctly the login screen disappears but the publish page does not advance and still requires me to log in.
I know my user ID and password are correct but just to be sure I used the wrong password and the screen says I've used the wrong password.
So I know I'm logging in correctly.
Is there any way to get other log information to see why I'm unable to publish my function to azure?
Also, in the upper right side of the dialog it does show that I am logged into Azure so I'm not sure why the additional login attempt is required.
If you are using Visual Studio code, you can publish your project directly from there. Just got to add the Azure extension and login in. Maybe try that

Azure Application Insight Work items authorization error

My purpose is to create bug in Azure DevOps directly from Azure Application Insight, I am doing to attach the work item (bug) feature available in Azure Application Insight but on clicking Authorize button it give me following error
Authorization token provided through OAuth does not have access to read/write work items for requested uri/project collection/project
for reference please find the below image.
Updates:
I didnt understand what you meant by private browser, and I have full admin access over Azure Portal.
basically I have the https://dev.azure.com/HealthTechnologies/ReportItNow link in which
https://dev.azure.com is the devop url
HealthTechnologies is the organization
ReportItNow is the Project
so in Azure insight workitem section, URL I am putting https://dev.azure.com/HealthTechnologies/ and in project I am putting ReportItNow, I dont know what i am doing wrong.
Still waiting for this glitch to solve.
Oky let me make it more simple, if I want to automatically create bug in Azure DevOps when ever any new exception came in to the Azure
Application Insight How I can get this into real practical.
I solve this when I took a detailed look at the error message url. It's saying that the missing authorization is for https://uri/Project Collection/Project. Based on that, I changed my url from https://dev.azure.com/organization to https://dev.azure.com/ and it worked,

Unable to add permissions to App on Azure Portal

I have created an app on Azure Portal to access some information via Microsoft Graph API but I am not able to add any permissions to it. It was working earlier but not any more. I also tried to register a new app, the app gets register but yet again the permissions could not be added.
As soon as I press the button to add the selected permissions these two popup notifications come up ..
1. Your session will end in a few minutes. You will have to refresh your browser to start a new session.
2. The portal is having issues getting an authentication token. The experience rendered may be degraded.
Additional information from the call to get a token:
Extension: Microsoft_AAD_RegisteredApps
This is happening since last 3 days now. I also searched on Google and found that people had similar issues earlier as well. Though I have raised a ticket on the portal for this but haven't received any reply yet.
Any help here would be very much appreciated. Also is there any way to check any logs on the portal itself. I did try to check the network logs via browser developer tools but they aren't much help.
It seems to be an issue with the Azure Portal for your region.
As #Hury Shen suggested, you should contact Azure Support for further investigation.
See how to open a support ticket on Azure portal.
Seems like there was an issue with my account address. I changed the address to one of US and it worked for me.
#Allen Wu Thanks for the suggestions. I had already asked them about it but no one replied.

Issue in creating bot service in Azure- Error while creating microsoft App id and password

I am trying to create a bot service using Free Trail Subscription in Azure Portal. While clicking on create Microsoft Appid and Password button, it directs to a page. Instead of showing me up with name and id in Generate App ID and password page,I get the below error as
"There's a temporary problem with the service. Please try again. If you continue to get this message, try again later"
Could anyone help me out to resolve this error. Also can you confirm if this is due to when a service is down or issue with the browser.
Thanks
I got the issue rectified by creating a separate Microsoft account id and by logging in using that I was able to generate appid and password successfully.

Azure Powershell cannot login

I am trying to log into Azure from PowerShell using the command
Login-AzureRmAccount
And it opens a popup window where I enter my email, then click personal account and then I get the error
"Because you're accessing sensitive info, you need to verify your password."
But then there is no action to perform. There's no button to click or anything. I'm logged into Azure in both Chrome and Edge. What is going on here? This seems like a bug with the Azure website. Please help! Thanks!
I think something was broken with their site. I was also using a third party console, cmder. When I used the built-in PowerShell console, I was able to login. Also, I can no longer reproduce the issue, so it seems like they fixed the issue.

Resources