You can send images from the web app to a container in Microsoft Azure Blob Storage. The browser sends each image directly to your container. For the general steps of an upload, read Uploads: send images to processing and storage services.
You do not sign in. You paste a SAS URL of the container. A SAS URL is a link that gives access to the container until it expires.
What you need
- A Microsoft Azure storage account. To learn about Azure Blob Storage, click the icon at the right end of the Microsoft row that shows Azure Blob Storage below the name, in the New Upload dialog. The Azure Blob Storage site opens in a new tab.
- A container in the storage account.
- A CORS rule on the storage account that allows uploads from the web app. Read "Set the CORS rule of the storage account" below.
- A SAS URL of the container, with the Create and Write permissions. Read "Make a SAS URL" below.
- A computer browser at app.dronelink.com.
- A plan that includes this integration. To see which plans include it, find "Azure Blob Storage" in the plan comparison table.
Set the CORS rule of the storage account
The browser sends the images to your container from app.dronelink.com. Azure refuses an upload from a web page, unless a CORS rule of the storage account allows that page.
- In the Azure portal, open the storage account.
- Under Settings, click Resource sharing (CORS).
- Click Blob service.
- Add a rule with these values:
- Allowed origins:
https://app.dronelink.com - Allowed methods: PUT
- Allowed headers:
x-ms-blob-type,x-ms-version,content-type - Exposed headers:
* - Max age: 3600
- Allowed origins:
- Click Save.
Make a SAS URL
- In the Azure portal, open the container.
- Click Shared access tokens.
- In Permissions, select Create and Write.
- Set the expiry time to a time after the end of the upload.
- Click Generate SAS token and URL.
- Copy the Blob SAS URL.
Make the SAS URL on the container, not on the storage account.
Important: Each person who has the SAS URL can add files to the container until it expires. Do not share it. Use a SAS URL that expires soon after the upload.
Settings
- Container SAS URL: the Blob SAS URL of the container. It must start with https://. Only an emulator on this computer can use http://localhost. The browser does not keep it. Paste it for each upload.
- Path: optional. The folder in the container for the images, for example folder/subfolder. If you do not enter a path, the images go to the top level of the container. If you start the upload from a mission page, the default is the mission name and the capture time, for example my-mission/2026-11-16_14-30-00.
The browser keeps the Path for the next upload. It does not keep the Container SAS URL.
If the Container SAS URL is not correct, the dialog shows a message below the field:
- "Paste a URL that starts with https://, for example https://account.blob.core.windows.net/container?sv=…. Only an emulator on this computer can use http://localhost.": the text is not a URL, it does not start with https://, or it has a user name or a "#" part. Copy the Blob SAS URL again.
- "This URL has no SAS token (sig=). Copy the Blob SAS URL, not the container URL.": you copied the URL of the container. Copy the Blob SAS URL.
- "This URL has no container. Make the SAS URL on the container, not on the storage account.": open the container in the Azure portal, and make the SAS URL there.
Next stays unavailable until the Container SAS URL is correct. When you click Next, the web app does not check the container or the permissions. A problem shows on the upload card when the first image starts.
Where the images go
Each image goes to the Path in the container, with its file name. Example: DJI_0001.JPG becomes folder/subfolder/DJI_0001.JPG. The web app does not keep folders from your computer. It removes empty folder names, and the folder names "." and "..".
If two or more files in the upload have the same name (capital and small letters count as the same), each file after the first gets a number before the extension. A file name with no extension gets no number. The number is the position of the file among the files that the upload sends. The first file is 0. Files with the label Skipped or Missing do not count. Example: folder/subfolder/DJI_0001_7.JPG.
If a file with the same name is already in the container, the result depends on the permissions of the SAS URL:
- With Write, the new file replaces the file in the container.
- With Create only, Azure refuses the new file, and the upload stops. The card shows "The SAS URL does not allow file."
To keep each upload apart, use a different Path for each upload.
After the upload
The upload card shows the storage account address, the container and the path, for example account.blob.core.windows.net | container | folder/subfolder. The card does not show the SAS URL.
The card shows the Path as you typed it. The files go to the path without empty folder names, ".", and "..".
The card has no Open button. To see the images, open the container in the Azure portal.
Troubleshooting
- "Azure Blob Storage did not answer. Make sure that the CORS rules of the storage account allow PUT from this site, then check your connection.": the CORS rule is missing or not correct, or the connection failed. Make sure that the CORS rule is correct. Then start a new upload.
- "Azure refused the SAS URL for file. The SAS URL expired or is not valid for this container, or the network rules of the storage account block this browser. Make a new SAS URL, then start the upload again.": make a new SAS URL with a later expiry time. If the storage account has network rules, make sure that they allow your computer.
- "The SAS URL does not allow file. It needs the Create and Write permissions. If a file with that name is already in the container, Write is necessary to replace it.": make a new SAS URL with the Create and Write permissions.
- "The container container does not exist.": the container was removed, or the SAS URL is for a different container. Make a new SAS URL on the correct container.
- "Azure Blob Storage refused file:" and a reason: Azure refused the file. The reason comes from Azure. Correct the cause, and start a new upload.
- One file failed: the web app sends a failed image again, up to 3 times. If Azure refused the image, the web app does not send it again. If the image does not arrive, the upload stops. The files that arrived stay in the container.
In the messages, file is the name of the file in the container, with the Path, for example folder/subfolder/DJI_0001.JPG. container is the name of the container in the SAS URL.