Skip to main content
Question

Azure Blob Storage Connector 2024.2

  • November 25, 2025
  • 3 replies
  • 43 views
stuart_miso
Contributor
Forum|alt.badge.img+9

EDIT - I have solved my own issue here! We had some network changes, and I needed the SAS from the top level of the storage account rather than the specific container. Problem solved.

 

I’ve successfully connected to the Azure BLOb using 2025.1 Form using the AzureBlobStorage Connector:

I can connect to the “Hosted” folder inside the container “shared-data”. I am connecting using SAS.

 

However, I need to use Flow 2024.2 and so I need to open this same workbench in Form 2024.2…. and this is where the fun starts!

The transformer is slightly different, when I try to configure the Container I don’t seem to have the option to add the “Shared-data”.

 

I am a complete novice at connecting to Azure, so please do not worry about over-explaining anything, I need all the help I can get! 

Many thanks in advance for any words of wisdom.

Regards

Stu

3 replies

desiree_at_safe
Safer
Forum|alt.badge.img+16

Hi ​@stuart_miso. I’m glad you were able to figure this out!

That's a really helpful find about needing the (broader scope) storage account-level SAS token rather than the container-level one after your network changes.

Do you know what specifically about those network changes required the broader SAS permissions? Was it related to how your network routes to Azure, or something about the 2024.2 connector's authentication behavior? This may help other users and us at Safe better understand these environment specific issues, but no pressure!

Either way, great troubleshooting on your part! 😊

Happy FME-ing!
stuart_miso
Contributor
Forum|alt.badge.img+9
  • stuart_misoContributor
  • Author
  • Contributor
  • November 28, 2025

Hi ​@stuart_miso. I’m glad you were able to figure this out!

That's a really helpful find about needing the (broader scope) storage account-level SAS token rather than the container-level one after your network changes.

Do you know what specifically about those network changes required the broader SAS permissions? Was it related to how your network routes to Azure, or something about the 2024.2 connector's authentication behavior? This may help other users and us at Safe better understand these environment specific issues, but no pressure!

Either way, great troubleshooting on your part! 😊

Thanks Desiree.
The change we had as users was to switch from a laptop / machine login to a Windows / 365 Account login. Why this would affect connections to Azure I am unsure, but it did! 
Whilst I still cannot connect from 2024.2 Form on my laptop to the BLOb store, I can connect on 2025.1 and .2, so that is unchanged.
I can however, use 2024.2 on an Azure VM to connect to the BLOb store, which is the main game here for me.
None of this is very helpful to others, I’m sure, and I am still a complete novice when understanding Azure and SAS connectivity!

desiree_at_safe
Safer
Forum|alt.badge.img+16

Seems like there’s a few things at play but this still adds really great context! Thank you for sharing!!

Happy FME-ing!

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.