Want to confirm that my blob trigger for function app is updating worm blob storage

Question

Want to confirm that my blob trigger for function app is updating worm blob storage

TLIT 25

Hi I wanted help confirming if my Blob Trigger to copy from one storage account Blob to another storage account WORM was working correctly. I know the script(uses AZCopy) works but I am unsure if it is actually updating the WORM side of things, specifically with versioning.

Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2025-03-15T17:09:48.4266667+00:00

Hi TLIT ,

To confirm if your Blob Trigger is correctly updating the WORM (Write Once, Read Many) storage with versioning Ensure that your function app logs are enabled and check the logs to see if the Blob Trigger is firing as expected. You can use Application Insights or Log Streaming in the Azure portal for this.

Navigate to the destination WORM storage account in the Azure portal. Check the blob properties to see if versioning is enabled and if new versions are being created when the Blob Trigger runs.Look at the metadata of the blobs in the WORM storage. You should see version IDs and timestamps that indicate when each version was created.

This tool can help you visually inspect the blobs and their versions in both the source and destination storage accounts.Since you mentioned using AZCopy, ensure that your script includes the necessary parameters to copy blobs with versioning. You can run the script manually and check the destination storage to confirm that versions are being created.

If you're using an event-based Blob Trigger, make sure the Event Grid subscription is correctly set up and that events are being delivered to your function app

For more information,

https://learn.microsoft.com/en-us/azure/azure-functions/functions-event-grid-blob-trigger?pivots=programming-language-csharp

Please let us know if you have any further queries. I’m happy to assist you further.
Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2025-03-17T16:30:54.7933333+00:00

Hi TLIT ,

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.
TLIT 25 Reputation points

2025-03-17T20:33:43.7333333+00:00

I have confirmed versioning is enabled on the WORM storage, my only concern is I do not see the timestamp updating on the files that ran. This is where my confusion is coming in.

It is a blob trigger(not the event grid one) so maybe that has something to do with it?

I attatched my script and removed the sensitive info from it but I know the containers are right, as I have another script running this as well into an empty container and it is not updating the files either.

script.txt
TLIT 25 Reputation points

2025-03-18T23:26:22.9533333+00:00

I have confirmed it is not copying over as the Blob Trigger only operates once when the blob is added, not updated. I am looking for a way around this right now, and believe a timer trigger that checks dates on all the blobs might work, but am unsure. Would appreciate any input
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2025-03-19T22:44:47.58+00:00

@TLIT Apologies for the delay in getting back to you on this issue. Can you share more information on how you are modifying the file in the source container? The blob trigger function should have pick up the file when added or modified. Have you noticed the function app invocation logs and validate if it is getting triggered when the blob is modified?

1 answer

Your answer

Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2025-03-15T17:09:48.4266667+00:00

Hi TLIT ,

To confirm if your Blob Trigger is correctly updating the WORM (Write Once, Read Many) storage with versioning Ensure that your function app logs are enabled and check the logs to see if the Blob Trigger is firing as expected. You can use Application Insights or Log Streaming in the Azure portal for this.

Navigate to the destination WORM storage account in the Azure portal. Check the blob properties to see if versioning is enabled and if new versions are being created when the Blob Trigger runs.Look at the metadata of the blobs in the WORM storage. You should see version IDs and timestamps that indicate when each version was created.

This tool can help you visually inspect the blobs and their versions in both the source and destination storage accounts.Since you mentioned using AZCopy, ensure that your script includes the necessary parameters to copy blobs with versioning. You can run the script manually and check the destination storage to confirm that versions are being created.

If you're using an event-based Blob Trigger, make sure the Event Grid subscription is correctly set up and that events are being delivered to your function app

For more information,

https://learn.microsoft.com/en-us/azure/azure-functions/functions-event-grid-blob-trigger?pivots=programming-language-csharp

Please let us know if you have any further queries. I’m happy to assist you further.
Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2025-03-17T16:30:54.7933333+00:00

Hi TLIT ,

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.
TLIT 25 Reputation points

2025-03-17T20:33:43.7333333+00:00

I have confirmed versioning is enabled on the WORM storage, my only concern is I do not see the timestamp updating on the files that ran. This is where my confusion is coming in.

It is a blob trigger(not the event grid one) so maybe that has something to do with it?

I attatched my script and removed the sensitive info from it but I know the containers are right, as I have another script running this as well into an empty container and it is not updating the files either.

script.txt
TLIT 25 Reputation points

2025-03-18T23:26:22.9533333+00:00

I have confirmed it is not copying over as the Blob Trigger only operates once when the blob is added, not updated. I am looking for a way around this right now, and believe a timer trigger that checks dates on all the blobs might work, but am unsure. Would appreciate any input
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2025-03-19T22:44:47.58+00:00

@TLIT Apologies for the delay in getting back to you on this issue. Can you share more information on how you are modifying the file in the source container? The blob trigger function should have pick up the file when added or modified. Have you noticed the function app invocation logs and validate if it is getting triggered when the blob is modified?

Answer 1

TLIT 25

All okay. So I have completely switched this up now. No longer using a Blob Trigger and am instead using a Timer trigger, to run every 3 hours. Now I just simply run an AZ copy every few hours and that seems to have solved it. I have now run into a different issue with the timer function but I can confirm the versioning is now working properly. So I am going to create a different post for that!

Share via

Want to confirm that my blob trigger for function app is updating worm blob storage

1 answer

Your answer