File name issue with plus sign - Get blob content using path (V2)

Suresh Kumar Chermadurai 20 Reputation points
2024-02-06T13:18:26.58+00:00

I am trying to get content of a file from Blob storage in Logic Apps using the connector "Get blob content using path (V2)". Connected Logic Apps with the specific Blob Storage using Managed Identity. Passing below blob path in the connector where file name having plus sign in it. Blob Path - /attachments/Testfile T&C+re+MISC+check+.pdf_IKE-256987.docx.

Output for the blob

{
  "status": 404,
  "message": "Specified resource /attachments/Testfile T&C re MISC check .pdf_IKE-256987.docx/ not found.\r\nclientRequestId: 1b18d505-e570-4545-85a4-fba215783608",
  "error": {
    "message": "Specified resource /attachments/Testfile T&C re MISC check .pdf_IKE-256987.docx/ not found."
  },
  "source": "xxxxxxxxxxxxxxxx"
}

All the plus sign are replaced with space and thrown file not found error. The file is available in the storage account container "attachments". Is this a limitation with the connector? If then what are all the characters will not work with the connector.

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,143 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,470 questions
{count} votes

Accepted answer
  1. Nehruji R 8,176 Reputation points Microsoft External Staff
    2024-02-07T13:44:32.0966667+00:00

    Hello Suresh Kumar Chermadurai,

    Greetings! Welcome to Microsoft Q&A Platform.

    Adding to above response, Since the blob name is URL-encoded in the backend, that is the reason why the '+' is replaced by ' '. Can you please try replacing the + with %2bor by modifying the file as per naming convention.

    refer - https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#unicode-characters-not-recommended-for-use-in-container-or-blob-names where it clearly mentions the blob naming conventions and rules.

    Similar SO thread - https://stackoverflow.com/questions/54805654/do-we-have-list-of-unsupported-characters-for-azure-blob-file-names for reference.

    Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Suresh Kumar Chermadurai 20 Reputation points
    2024-02-06T13:29:51.2633333+00:00

    Looks like this is a limitation with the connector based on the below article.

    https://learn.microsoft.com/en-us/connectors/azureblob/#known-issues-and-limitations

    "The connector does not support blob names and paths that contain URL decodable characters, i.e. "+" or "%" followed by two hexadecimal digits."

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.