Where in the Azure portal can i find my Phpmyadmin password for a wordpress installation.

Hello Matt Newboult,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are using phpMyAdmin deployed with your Azure WordPress site, and you're looking to log in directly via the phpMyAdmin web interface, without resetting the password, and you don’t want to connect externally or reset password or use tools like MySQL Workbench.

If you're using a Marketplace WordPress offering such as WordPress by Bitnami, or WordPress on App Service with MySQL (Flexible Server / Web App + Database Plan). In either of those, phpMyAdmin uses the same MySQL credentials as your WordPress site, but Azure doesn’t surface the password in the portal UI after installation. Azure doesn’t tell this password in the portal unless you saved it manually during setup, or the deployment method stored it somewhere accessible. The workaround or only real ways to recover it without resetting anything are:

1. You can view wp-config.php (safe, read-only, reveals password) even if you don’t want to use external tools, this is entirely through Azure’s UI:
   1. Go to App Services in the Azure Portal.
   2. Select your WordPress App.
   3. Under Development Tools, click Advanced Tools > Go (opens Kudu).
   4. Click Debug Console > CMD.
   5. Navigate to: site/wwwroot
   6. Open the file: wp-config.php
   7. Find this section:

            define('DB_NAME', '...');
            define('DB_USER', '...');
            define('DB_PASSWORD', '...'); //This is your phpMyAdmin login password
            
      

   8. That value in DB_PASSWORD is exactly what phpMyAdmin needs (use the DB_USER too). You’re not changing anything here just viewing.
2. If you're using Azure Database for MySQL (Flexible/Single) that's your WordPress site uses a separate MySQL server, then you can:
   1. Go to the MySQL server resource in Azure.
   2. Click Connection strings.
   3. If it shows a full connection string, it might include the password (rarely).
   4. If not, there’s no way to recover the password directly from the portal, you’ll have to view wp-config.php as above.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

I re-installed the Wordpress installation (Microsoft Azure Wordpress). I opted out of using Entra and now see the settings for the DB user and DB password in the appsettings. However when I navigate to /phpAdmin for the site and enter the username and password it errors.

Wondering why it's so hard to see the database in this Microsoft template. It seems so incredibly hard.
I also used Kudo and this is what's in wp-config.php:

$connectstr_dbusername = getenv('DATABASE_USERNAME');

$connectstr_dbpassword = getenv('DATABASE_PASSWORD');

No user and password in there and still no closer to connecting to the db.

Is there a way of using Kudu to create a token or something so I can login using Azure Data Studio or something?

Hi Matt Newboult,

I apologize for any inconvenience you've experienced with this process. I understand your frustration with the challenges in accessing the database using the Microsoft Azure WordPress template.

Here's some insight into the situation:

1. Configuration via Environment Variables The template uses environment variables (accessible through app settings) to store the database username and password rather than hardcoding them in wp-config.php. This approach is intended to enhance security by keeping sensitive details out of the file system where they might be seen by accident.
2. Accessing the Database Credentials Although you see placeholders like

   
      $connectstr_dbusername = getenv('DATABASE_USERNAME');
   
      $connectstr_dbpassword = getenv('DATABASE_PASSWORD');
   
   

   in your configuration file, the actual values are set in the Azure Web App configuration. To view these:
   • Navigate to your Web App in the Azure portal.
   • Go to Configuration under Settings.
   • Check the Application settings or Connection Strings sections.
   These sections should display the connection string details, including the database server, username, and (if not masked) the password.
3. Using Kudu and Connection Attempts Kudu is a powerful tool for managing and troubleshooting your Azure Web App, but it doesn't offer a built-in feature to generate tokens or reveal secrets for alternative connection methods. It primarily provides you with access to the file system and the ability to run scripts or commands. While you can use the Kudu debug console to inspect environment variables (for example, using the echo command), it typically won’t reveal sensitive information if it’s stored securely.
4. Connecting with Azure Data Studio To connect to your database via Azure Data Studio (or any client tool), you need the full connection details—including the server name, database name, username, and password—from the Azure portal’s configuration sections. If the password is hidden, you may have to use the portal’s options to reset or reveal it, provided your permissions allow it. Also, ensure that your database’s firewall settings permit your client’s IP address to connect.
5. Why It Seems Complicated The design choice to manage credentials through environment variables is common in Azure templates for security and ease of centralized management. However, it can make external connections seem less transparent at first glance. Unfortunately, there’s no mechanism in Kudu to “create a token” for database connections—credentials must be managed through the Azure portal.

In summary, while the Microsoft Azure WordPress template secures database credentials using environment variables, you’ll need to retrieve the full connection details from the Azure portal’s configuration settings instead of relying on Kudu to generate a token for connections like those made through Azure Data Studio.

I hope this helps clarify the situation. If you found my comments helpful, please vote for me

Hello Matt Newboult,

Thank you for your feedback and good to know that your credentials are stored in environment variables.

The below is more precise:

1. Accessing Environment Variables by navigate to your Web App in the Azure portal.

• Go to Configuration under Settings.
• Check the Application settings or Connection Strings sections to find the database credentials.

1. To use the Credentials: Make sure that the credentials you found in the app settings are correctly entered in phpMyAdmin.
   • If the password is masked, you may need to reset it through the Azure portal.
2. Check that your database's firewall settings allow connections from your IP address.
   • Navigate to your MySQL server resource in Azure.
   • Go to Connection security and add your IP address to the allowed list.
3. To use Kudu for Debugging:
   • While Kudu does not generate tokens, you can use it to inspect environment variables.
   • Open Kudu (Advanced Tools) from the Azure portal.
   • Use the Debug Console to run commands like echo $DATABASE_USERNAME and echo $DATABASE_PASSWORD to verify the values.
4. Then, use the full connection details from the Azure portal to connect via Azure Data Studio and be sure that the server name, database name, username, and password are correctly entered.

Success

Hello   Matt Newboult,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.