"az mysql flexible-server import create" - InvalidImportSourceDetails from Azure blob

Question

"az mysql flexible-server import create" - InvalidImportSourceDetails from Azure blob

Jeremy Buisson 0

I need to migrate multiple onprem mysql databases to Azure Database for MySQL flexible server. The dumps (corresponding to .sql script files) are then stored in an Azure Storage account.

The storage account allows public access without any restriction. Regarding authentication, the command is run with my personal account, granted as "Storage Blob Data Contributor".

I got 'Import source storage is not accessible.' error during provisioning using following az cli command:

az mysql flexible-server import create -g rsg-test -n mysql02 --version 8.0.21 --sku-name Standard_D4ds_v4 --tier GeneralPurpose --location francecentral --public-access 0.0.0.0 --storage-size 200 --storage-auto-grow Enabled --data-source-type azure_blob --data-source https://storagemysql.blob.core.windows.net/dumps --admin-user "username" --admin-password "password"

Detailed error:

(InvalidImportSourceDetails) Import source details provided are not valid for import from storage. Error details: 'Import source storage is not accessible.'. Code: InvalidImportSourceDetails Message: Import source details provided are not valid for import from storage. Error details: 'Import source storage is not accessible.'.

Hari Babu Vattepally 2,640 Reputation points Microsoft External Staff

2025-04-08T16:25:05.6066667+00:00
Hi @Jeremy Buisson,

Thanks for sharing the detailed error message. As per the error message, we see that there is an issue with the accessibility of the Azure Blob Storage where your MySQL dumps are stored.

As you mentioned that you are using personal account and relying on public access which may not meet the authentication requirements for the import process. In this case, you need to provide proper credentials through a Shared Access Signature (SAS) token to ensure the importer can securely read the dump files.

Please follow the below recommendation in order to resolve the issue:

Please make sure to check and confirm the container named dumps exists in your storage account (storagemysql) and that it contains the required .sql dump files.

Generate SAS token with the required permissions Read(r), List(l) for the container called dumps from the storage account.

Once it is SAS token is generated for the specific container, set an appropriate expiration time. Once generated, copy the SAS token (it will look like a query string, e.g., sv=2021-02-10&ss=b&srt=sco&sp=rl&se=...). And, then append the SAS token to your container URL and update the URL as https://storagemysql.blob.core.windows.net/dumps?<SAS_TOKEN> and make sure to replace <SAS_TOKEN> with the actual generated token.

Also, please make sure to check that the personal account is still assigned Storage Blob Contributor role at the container or storage account level or higher roles at the storage account level.

If your MySQL flexible server has public access, please make sure that storage accounts firewall settings allow access from the server's public IP. In the same way, if your Azure storage account has any network restrictions (like virtual network configurations), ensure that your Azure Database for MySQL flexible server can access the storage account.

However, also ensure to test the connection using Azure Storage Explorer or az storage commands to check that the MySQL server can access the container.

Once all the above steps are done. Please rerun the import command as below:

az mysql flexible-server import create -g rsg-test -n mysql02 \ --version 8.0.21 \ --sku-name Standard_D4ds_v4 \ --tier GeneralPurpose \ --location francecentral \ --public-access 0.0.0.0 \ --storage-size 200 \ --storage-auto-grow Enabled \ --data-source-type azure_blob \ --data-source "https://storagemysql.blob.core.windows.net/dumps?<SAS_TOKEN>" \ --admin-user "username" \ --admin-password "password"

After retrying the above command, monitor the import process by checking the Activity Log or Metrics section for the MySQL Flexible server. Also, make sure to verify the imported data in the Azure Database for MySQL Flexible server.

For more additional information, please refer the below document:

Migrate MySQL on-premises or Virtual Machine (VM) workload to Azure Database for MySQL with Azure Database for MySQL Import CLI

I hope by following the above helps in resolving the issue.

Please let us know in the comments below, if the issue is resolved or still persists. We will be glad to assist you closely.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Hari Babu Vattepally 2,640 Reputation points Microsoft External Staff

2025-04-09T02:46:53.4033333+00:00

Hi @Jeremy Buisson,

Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Hari Babu Vattepally 2,640 Reputation points Microsoft External Staff

2025-04-10T02:58:48.2466667+00:00

Hi @Jeremy Buisson,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Your answer

Hari Babu Vattepally 2,640 Reputation points Microsoft External Staff

2025-04-09T02:46:53.4033333+00:00

Hi @Jeremy Buisson,

Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Hari Babu Vattepally 2,640 Reputation points Microsoft External Staff

2025-04-10T02:58:48.2466667+00:00

Hi @Jeremy Buisson,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

"az mysql flexible-server import create" - InvalidImportSourceDetails from Azure blob

Your answer