Hi ,
Thanks for reaching out to Microsoft Q&A.
This issue usually happens because of changes in how azure blob storage handles public access. Earlier, containers often defaulted to allowing anonymous blob access, so direct URLs worked without extra configuration. Recently, Microsoft has made public access disabled by default for new storage accounts and containers, which means that while you can upload files, the URLs will not resolve unless you explicitly allow access. That explains why your older container still works, but the new one does not. It is also possible that the storage account now requires access through SAS tokens or has network restrictions such as private endpoints or firewalls enabled. To resolve this, check the container’s public access settings in the portal and compare them with the container that works. If anonymous access is disabled and you want public URLs, you will need to enable it at the container level. Otherwise, the recommended approach is to generate SAS tokens for secure access. This ensures that your files remain accessible without opening the storage account broadly to the internet.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.