Hi Yu Chai.
It seems like there might be a small mix-up with the container references in your Azure Machine Learning job setup. Why not take a moment to double-check the container names listed in your Azure portal? It's quite easy to overlook details when dealing with similar names.
Would you mind verifying that the container azureml-blobstore-ed619ea0-85f4-45e8-88d9-672ac6a082dc is indeed present and correctly spelled in your Azure Blob Storage? Sometimes, the simplest solution is the correct one.
Also, consider taking a peek at your job configuration settings. There's a chance that a file or a parameter might be pointing to a different container than intended. It's a good practice to ensure that all references align with the container where your dat_final_05.10.2023.csv file resides.
Permissions can be quite the tricksters as well. It wouldn't hurt to revisit the IAM settings to confirm that your Azure ML service is still on friendly terms with the Blob Storage container.
And here's a thought – if you've registered a datastore in Azure ML with a unique name, it could be that the name being used in your job configurations needs a quick update to match. Datastore names can sometimes differ from the actual storage container names, so it's worth a check.
Lastly, if you're employing connection strings or keys, a routine verification that they're current could save the day. These credentials have a habit of changing when we least expect them to.
I hope this helps?