File name issue with plus sign - Create blob (v2)

Question

File name issue with plus sign - Create blob (v2)

Suresh Kumar Chermadurai 20

I'm encountering an issue while copying a file from one Azure Blob Storage account to another using Logic Apps. The workflow uses the "Get blob content using path (V2)" connector to read the file from the source and the "Create blob (V2)" connector to write it to the destination.

The issue arises when the file name contains a "+" symbol, e.g., TestDocument+sample12.docx. I’ve tried the following:

I am retrieving the blob content from the source storage using the "Get blob content using path (V2)" connector, and I replace the "+" symbol with %2b in the path to correctly fetch the file.

However, problems occur during the creation of the new blob in the target storage:

Using the "+" character directly in the file name in the Create Blob (V2) connector:
- The file is copied successfully with the correct content.
- But the file name is changed in the target container. The "+" is dropped, resulting in TestDocument sample12.docx.
Using %2b in place of "+" in the file name in the Create Blob (V2) connector:

The connector throws a "file not found" error.
Despite this, it creates an empty and unusable file in the target with the correct name (TestDocument+sample12.docx).
- The file shows Lease status as 'Leased' and contains no data.

Has anyone faced a similar issue, or is there a recommended way to handle file names with special characters like "+" when copying blobs using Logic Apps?

Any help or suggestions would be greatly appreciated.

Shireesha Eeraboina 2,815 Reputation points Microsoft External Staff

2025-04-30T05:25:59.52+00:00
Hi Suresh Kumar Chermadurai,

To address the issue with the file name containing a plus sign, you need to ensure that the file name follows the naming rules for blobs in Azure Storage. The error you are encountering could be due to unsupported characters in the file name.

When dealing with file names that contain special characters like the "+" symbol in Azure Logic Apps, it's important to note that the "+" character can be interpreted differently in URLs. Here are some suggestions to handle this issue:

Directly Using "+": If you use the "+" character directly in the file name while creating the blob, it may be dropped or altered, as you've experienced.

Using URL Encoding: Replacing "+" with "%2b" in the file name can lead to a "file not found" error, as you've noted. This suggests that the encoding might not be correctly interpreted by the Logic Apps connectors.

To resolve this, consider renaming the file to remove or replace the "+" with a different character (like an underscore "_") before copying it. This avoids issues with special characters altogether.

Here is an example of how you can encode the plus sign (+) in the file name:

Original File Name: @$&+%2b={}[]ab;-_.,)(^_IE-496570_OE-517355.docx

Encoded File Name: @$&%2B%2b={}[]ab;-_.,)(^_IE-496570_OE-517355.docx

To assist you in understanding, please refer to the documents below:

https://learn.microsoft.com/en-us/answers/questions/2115369/logic-app-sharepoint-move-files-with-special-chara

https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

By correctly encoding the plus sign and ensuring that the file name complies with the Azure Blob Storage naming rules, you should be able to create the blob successfully using the Logic Apps connector.
Shireesha Eeraboina 2,815 Reputation points Microsoft External Staff

2025-05-02T05:53:51.4566667+00:00

Hello Suresh Kumar Chermadurai,

Just checking in to see if the below answer provided by RithwikBojja helped.

if you have any further query do let us know.

2 answers

Your answer

Shireesha Eeraboina 2,815 Reputation points Microsoft External Staff

2025-04-30T05:25:59.52+00:00

Hi Suresh Kumar Chermadurai,

To address the issue with the file name containing a plus sign, you need to ensure that the file name follows the naming rules for blobs in Azure Storage. The error you are encountering could be due to unsupported characters in the file name.

When dealing with file names that contain special characters like the "+" symbol in Azure Logic Apps, it's important to note that the "+" character can be interpreted differently in URLs. Here are some suggestions to handle this issue:

Directly Using "+": If you use the "+" character directly in the file name while creating the blob, it may be dropped or altered, as you've experienced.

Using URL Encoding: Replacing "+" with "%2b" in the file name can lead to a "file not found" error, as you've noted. This suggests that the encoding might not be correctly interpreted by the Logic Apps connectors.

To resolve this, consider renaming the file to remove or replace the "+" with a different character (like an underscore "_") before copying it. This avoids issues with special characters altogether.

Here is an example of how you can encode the plus sign (+) in the file name:

Original File Name: @$&+%2b={}[]ab;-_.,)(^_IE-496570_OE-517355.docx

Encoded File Name: @$&%2B%2b={}[]ab;-_.,)(^_IE-496570_OE-517355.docx

To assist you in understanding, please refer to the documents below:

https://learn.microsoft.com/en-us/answers/questions/2115369/logic-app-sharepoint-move-files-with-special-chara

https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

By correctly encoding the plus sign and ensuring that the file name complies with the Azure Blob Storage naming rules, you should be able to create the blob successfully using the Logic Apps connector.
Shireesha Eeraboina 2,815 Reputation points Microsoft External Staff

2025-05-02T05:53:51.4566667+00:00

Hello Suresh Kumar Chermadurai,

Just checking in to see if the below answer provided by RithwikBojja helped.

if you have any further query do let us know.

Answer 1

Hello Suresh Kumar Chermadurai,

Thank you for posting your question in the Microsoft Q&A forum.

When using the "Create blob (V2)" connector in Azure Logic Apps to transfer files between Blob Storage accounts, special characters in filenames—such as plus signs (+)—must be properly encoded to avoid errors. In your case, replacing "+" with "%2B" (URL encoding) is correct, as raw special characters can disrupt the URI parsing. However, Logic Apps may still encounter issues if the decoding/encoding process is inconsistent across connectors.

To ensure seamless file transfer, verify that:

The source blob path uses consistent encoding (e.g., %2B instead of +).
The destination blob name follows Azure Storage naming conventions (avoid reserved characters such as ?, , % unless encoded).
The "Create blob (V2)" action dynamically preserves encoded characters—sometimes Logic Apps auto-decodes them, breaking the path.

If issues persist, you may consider below steps:

Using Azure Functions or Storage SDKs for complex filename handling.
Logging the raw and encoded paths in a Compose step to debug mismatches.
Testing with a simplified filename first to isolate the issue.

Proper encoding and validation ensure reliable file transfers in Logic Apps.

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.

Suresh Kumar Chermadurai 20 Reputation points

2025-04-29T10:18:21.8666667+00:00

Suwarna S Kale - Thank you for your comments. I've updated my question with additional details—apologies for the earlier version. It should now be clearer and more appropriate.

Answer 2

Hi @Suresh Kumar Chermadurai ,

To fetch the file with plus (+), I used below design which works:


  /testcon/rith%2bch.txt

enter image description here

Output:

enter image description here

Firstly, I have below file in testcon:

enter image description here

When we use Create Blob (V2) action, it is creating lease and data is empty.

But as an alternative, you can use below design:


  /testcon/rith%2bch.txt

enter image description here

Then taken the output in Compose as below:

enter image description here

Then in Create Block Blob (V2) Action :


decodeUriComponent('rit%2bbch.txt')

enter image description here

Output:

enter image description here

If you directly give body('Get_blob_content_using_path_(V2)') directly in Create block blob action, it taking as a space . But if you give in Compose action and use its output, then its working fine.

With Create blob it gives space in names:

enter image description here

If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.

enter image description here

If you have any other questions or are still experiencing issues, feel free to ask in the "comments" section, and I'd be happy to help.

Share via

File name issue with plus sign - Create blob (v2)

2 answers

Your answer