Hints and Tips - ibm-messaging/mq-azure GitHub Wiki
This page contains various general hints and tips about using IBM MQ on Microsoft Azure.
If you Shutdown a virtual machine using the Azure Portal and then Start it again, both the Public and Private IP addresses will be different so you cannot use IP addresses when configuring MQ.
If you want to ping the public IP address of a virtual machine you will need to change the Windows firewall to allow ICMP.
I followed the tutorial at [1] to set up a storage account using Azure Files and created a share for a directory containing data and logs directories.
If you want to use Azure Files storage for the data and logs of a queue manager you have to import the credentials of the storage account into the context of the user which the Windows service runs as, by default MUSR_MQADMIN, as well as the user which you use to manage the queue manager.
To do this you use the runas command to run a PowerShell as the MUSR_MQADMIN user and then run the command to add the storage key.
You will need to set a password for the MUSR_MQADMIN user as the initial password is generated during the installation of MQ and is random. Follow the steps at [2]. I found I needed to start the service after changing the password.
I use the primary storage key to do the share and the secondary storage key when importing credentials. Note that MQ does not support mapped drives so you have to specify the full UNC paths when creating a queue manager with its data and logs in Azure Storage.