When I click on connect button in Azure Portal, the RDP file is opened and it asks for credential,. not sure what credentials to give. Is it my login to azure portal or something else?
The RDP login prompt shows "MicrsoftAccount\PortalLoginUserName" as user name.What should be typed in password? Is it the portal password? If i try that it does not work.
When creating VM i have provided new username and new password is that what i need to use? if this what i need to use what would be domain?
You need to use the username and password you used when provisioning the VM. These credentials are not the same as your Azure account credentials. And every VM may have its own unique credentials.
When entering your username in the RDP client, either enter \username or localhost\username.
Related
My domain account is locked out and I can't get access to any VM, including our domain controller. I still have full access to our portal. Is there any way that I can reset my domain account password via the Azure portal?
I was able to unlock my account using the following powershell command
Unlock-ADAccount -Identity username
(Where 'username' is the user name of the AD account.)
I have an Office 365 account where I am admin. I used that same account to create an Azure space or account, where I "believe" or "should" be admin as well. In both cases, I am the only user. Both work fine and I can log into both with same user name and password. I created an RDP connection to a VM that I create in Azure. The only user name and password that I would know of to use is the same one that I log into Azure with, but it never works. Seems to be connecting but just rejecting credentials. What username should I use? I can't use one that I create on the VM because I can't get on there yet.
When you create a VM you need to give it admin username and password. And you would use those to login, so check what you did input and use that.
You can reset the existing user password or create the new user/password from the 'Reset Password' option from the Azure Portal as well.
I needed to use the name of the domain of the VM in front of my username to get in.
I have just opened a free trial account for Azure and I am experiencing some very strange behavior trying to install the Azure CLI on a fresh Ubuntu VM....I am printing the steps I am trying below 1 by 1 in case anyone else has experienced this.
Start up a Ubuntu virtual machine, install the Azure CLI tool, and run "az login". It will display a web address plus code to authenticate.
Open Edge and clear all browsing data (this includes cookies). Close Edge and re-open.
Go to portal.azure.com and verify that I am not signed in. It displays a login prompt (specifically, it says "Work or school, or personal Microsoft account"). Leave this tab open for now.
In a new tab, go to aka.ms/devicelogin, put in my authentication code, and click "Continue". It will redirect to the same Microsoft login prompt as above ("Work or school, or personal Microsoft account")
Enter the Outlook.com email address associated with my free trial. When I tab into the password entry, it will redirect me to a different Microsoft login screen for me to enter my password.
When I type in the (correct) password, it will tell me "We don't recognize this user ID and password". There is no chance the user ID or password is wrong. This can be verified by immediately refreshing the still open tab from Step #3 (to portal.azure.com) and discovering it is now logged into the Azure portal. So I am definitely entering the correct ID/password, but for some reason the aka.ms/devicelogin is telling me it is incorrect. My other tab is recognizing I am now logged in.
Has anyone else experienced this? I was thinking it might have to do with the fact that I have a personal (#Outlook.com) Azure account as well as a work (#WorkDomain.com) account, but I've cleared cookies as well as deleted all Windows/Web Credentials in Credential Manager as indicated in this link: Error: We don't have a valid access azure with Azure CLI
install the Azure CLI on a fresh Ubuntu VM
Do you open browser on this VM or open browser on your local PC?
I had test in my lab, use outlook.com account to test, when I use Linux VM CLI 2.0 to login Azure, then use my local windows IE browser to open https://aka.ms/devicelogin and type code, then get the same error message as you.
But when I use my windows PC CLI 2.0 to login Azure, and use windows IE to open that page, works fine.
But when I use Linux VM CLI 2.0 to login Azure with hotmail.com, then use my local windows IE to login it, works find.
It seems that outlook account is Microsoft account, it need sign-in verify.
As a workaround, we can use CLI 2.0 to login Azure whit this command:
az login -u xxx#outlook.com
Then type the password, we will login to Azure.
Update:
As a workaround, we can create service principal to login CLI:
About create service principal, we can use this command :
az ad sp create-for-rbac:
About login CLI:
az login --service-principal -u a487e0c1-82af-47d9-9a0b-af184eb87646d --password {password} --tenant {tenant}
More information about service principal, please refer to this link.
Run below command to login azure on virtual machine.Instead of app-url use name which u generated from below steps
az login --service-principal -u *app-url* -p *password-or-cert* --tenant *tenant*
Follow below steps to generate client-id(app-id) and secret
az account show --query "{subscriptionId:id, tenantId:tenantId}"
az account set --subscription="${SUBSCRIPTION_ID}"
az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/${SUBSCRIPTION_ID}"
Your appId, password, sp_name, and tenant are returned. Make a note of the appId and password.
I have created a Windows Server 12 VM on Azure platform. And I created Ftp server on IIS server in the VM. The Ftp server is publically accessible using all users accounts. Currently I have only admin user account. I am trying to create couple of more user accounts & Ftp servers and assign each user to specific Ftp server.
I tried to create user account via Control Panel\All Control Panel Items\Administrative Tools->Local Users and Group->New User, but it does not allow me to progress. It just throws unknown error.
Any idea over how shall I create new user account so that it can be publically used for Ftp service authentication?
I finally managed to create new user from Control Panel\All Control Panel Items\Administrative Tools->Local Users and Group->New User.
The unknown error was thrown because of password was not strong and entered invalid chars in Description, Full name textboxes. The error message from Win Server did not help at all.
I had to change the admin password as it had expired via RDP. The server was working fine after the change.
Later I disconnected the session, and started it again, now we are getting the following error message:
An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote computer: **.cloudapp.net
This same error keeps coming up even after 2 server restarts. The password is defiantly correct as typing a different password gives a "Password Incorrect" error.
There is no other way for us to access this server.
I found the answer here.
Your machine should still have a local administrator account (e.g. MachineName\Administrator), in which case you can login with the administrator account. In the RDP login prompt, you'll need to put the full user account (e.g., "MachineName\Administrator" where MachineName is your computer's name, otherwise it will default to "PreviousDomainUsed\Administrator").
This happened to me with an Azure VM because the domain administrator account I was using had an expired password and the Azure VMs enforce Network Level Authentication, which prevents you from changing the password through RDP. I was able to update the password by logging into the domain controller's VM, but the VM I couldn't log into didn't receive the update because the DNS settings were incorrect. I RDP'd into the faulty VM with the local administrator account, updated the DNS settings and ran "gpupdate" in a Powershell command prompt and everything began working again.
Hope this helps.
I had same issue with local admin account and specifying user account as "machine name\Administrator" still did not work. There was only local admin account in Azure VM so I needed to solve this issue for local admin account.
I could reset password for local admin account by following step then now I can log in to Azure VM by local admin account.
Open Azure Portal web site.
Click "Virtual Machine" then click virtual machine name which issue having in the list.
Dash board for selected virtual machine is shown. Then click "Reset Password".
Following screen is displayed so specify local admin account name nand password, then click Update.
This uses the VMAccess extension to reset the built-in administrator account and reset the Remote Desktop service configuration. Learn more
Mode
You can perform a password reset, which will also reset the Remote Desktop service configuration, or choose to reset the configuration only.
Reset password
User name:
If you provide a different user name, then the built-in administrator account with be renamed. Also, the account will be enabled if it's currently disabled. (The name of local admin account is shown as default)
Password
Confirm password
here is an answer if you need it yet.
http://social.technet.microsoft.com/wiki/contents/articles/18710.troubleshoot-azure-vm-by-attaching-os-disk-to-another-azure-vm.aspx