Hello C Pfleger,
Thank you for posting your query here!
Can you please try to force a content update of the website that is called by the CDN is to purge the cached content from all edge nodes as described at Purge an Azure CDN endpoint. In the endpoint overview, click the "Purge" button. Then, confirm the "Purge all" checkbox and click on the "Purge" button at the bottom of the panel as here.
This process usually takes about one to two minutes. The notifications show the success of the purge operation.
The Azure CDN should now immediately retrieve the new assets for the next client requests. You may see that the first request takes some time because the website is completely reloaded - but now with the most recent data from the storage and from the $web folder. As expected, all subsequent requests are served quickly from the CDN cache.
If the issue persists, it's possible that the issue lies elsewhere in the configuration or setup of your
Azure CDN or Blob Storage.
In that case, you can find out how to create and to deploy a static website on an Azure Storage Account at Static website hosting in Azure Storage and a tutorial at Tutorial: Host a static website on Blob Storage. If the website has a custom domain bound to the website with Azure CDN, see more at Quickstart: Integrate an Azure Storage account with Azure CDN.
Once deployed and configured, we have the static website up and running in Azure CDN with some basic rules, like redirection of HTTP to HTTPS and so on. In the Azure Storage Account, the Azure CDN is configured with an *.azureedge.net endpoint as here:
Do let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.