?
Azure Automation Authentication: User name and password
?
If you use PowerShell in Azure Automation to manage resources for your current subscription or manage resources for different subscriptions, then the question is, how is security guaranteed? Azure's automation, like other clients using or managing Azure, requires authentication for any azure that needs to be managed, with two basic authentication methods, one based on the user name password for the subscription and one based on the certificate, and this section describes the password based on the user name.
?
- It is not recommended to use the OrgID and password of the account currently managing production subscriptions directly in automation, it is recommended to create a user name for automation separately, first, login to the Azure management interface and open active Directory:
- Choose your current directory name, go to the main interface, you can see there are users, applications and so on, then we need to add a new user, select the bottom of the Add User:
?
?
- Enter information about the user, select a new user in your organization, enter a user name, such as Automationuser in the example, and choose Next:
- Enter the user's profile, alternate mail address, and so on, please do not choose to enable multi-factor authentication:
?
- Stand-alone creation, after the system will give you a temporary password, you need to use the new user login system, modify the temporary password to use:
- After the user is created, you must add the user to the co-administrator and assign the subscription you want to manage to use:
?
- Keep in mind that the Automation user name and password created in this section are used in subsequent creation of automation scripts.
- A little and a few drawbacks of automating script authentication with usernames and passwords:
- Advantages: Simple and convenient, intuitive
- Cons: Because Azure enforces passwords for 3 months, many users run automation scripts that way, password expiration is not updated in a timely manner and is not known, resulting in long maintenance interruptions
?
?
Automate cloud operations with Azure automation (2)
