Create users in Azure Database for MySQL
APPLIES TO: Azure Database for MySQL - Single Server Azure Database for MySQL - Flexible Server
Azure Database for MySQL - Single Server is on the retirement path. We strongly recommend for you to upgrade to Azure Database for MySQL - Flexible Server. For more information about migrating to Azure Database for MySQL - Flexible Server, see What's happening to Azure Database for MySQL Single Server?
This article describes how to create users for Azure Database for MySQL.
This article references the term slave, which Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
You provided a server admin username and password when creating your Azure Database for MySQL server. For more information, see this Quickstart. You can determine your server admin user name in the Azure portal.
The server admin user has these privileges:
SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER
After you create an Azure Database for the MySQL server, you can use the first server admin account to create more users and grant admin access to them. You can also use the server admin account to create less privileged users with access to individual database schemas.
The SUPER privilege and DBA role aren't supported. Review the privileges in the limitations article to understand what's not supported in the service.
Password plugins like
caching_sha2_password aren't supported by the service.
Create a database
Get the connection information and admin user name.
You need the full server name and admin sign-in credentials to connect to your database server. You can easily find the server name and sign-in information on the server Overview or the Properties page in the Azure portal.
Use the admin account and password to connect to your database server. Use your preferred client tool, MySQL Workbench, mysql.exe, or HeidiSQL.
Edit and run the following SQL code. Replace the placeholder value
db_userwith your intended new user name. Replace the placeholder value
testdbwith your database name.
This SQL code creates a new database named testdb. It then makes a new user in the MySQL service and grants that user all privileges for the new database schema (testdb.*).
CREATE DATABASE testdb;
Create a nonadmin user
Now that you have created the database, you can start by creating a nonadmin user by using the
CREATE USER MySQL statement.
CREATE USER 'db_user'@'%' IDENTIFIED BY 'StrongPassword!'; GRANT ALL PRIVILEGES ON testdb . * TO 'db_user'@'%'; FLUSH PRIVILEGES;
Verify the user permissions
To view the privileges allowed for user db_user on testdb database, run the
SHOW GRANTS MySQL statement.
USE testdb; SHOW GRANTS FOR 'db_user'@'%';
Connect to the database with the new user
Sign in to the server, specifying the designated database and using the new username and password. This example shows the MySQL command line. When you use this command, you're prompted for the user's password. Use your own server name, database name, and user name. See how to connect the single server and the flexible in the following table.
Limit privileges for a user
To restrict the type of operations a user can run on the database, you must explicitly add the operations in the GRANT statement. See the following example:
CREATE USER 'new_master_user'@'%' IDENTIFIED BY 'StrongPassword!'; GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER ON *.* TO 'new_master_user'@'%' WITH GRANT OPTION; FLUSH PRIVILEGES;
All Azure Database for MySQL servers are created with a user called "azure_superuser". Microsoft created a system account to manage the server to conduct monitoring, backups, and other regular maintenance. On-call engineers may also use this account to access the server during an incident with certificate authentication and must request access using just-in-time (JIT) processes.