Programmatically Purging Azure Frontdoor CDN With Azure DevOps
Benefits of using Frontdoor with CDN
Content Delivery Networks (CDNs) accelerate web traffic across the internet through servers residing in strategic locations (known as points of presence or PoPs) across the globe. Each PoP has a number of caching servers, each of which contains a cached version of your website or application. By bringing content closer to each visitor, CDNs improve performance and reduce the load on the origin server. This feature makes Frontdoor a powerful application delivery network.
List of Azure CDN POP locations from Microsoft https://docs.microsoft.com/en-us/azure/cdn/cdn-pop-locations
Adding CDN capability to Frontdoor is just one click feature.
Purge Azure Frontdoor CDN from Azure Portal
Purge Azure Frontdoor CDN from the command line
az extension add — name front-dooraz network front-door purge-endpoint — resource-group myrg — name mymap — content-paths “/”# Note: The --name parameter does not use the FQDN of Frontdoor (https://mymap.azurefd.net) and just naked name as "mymap"
Programmatically Purging Azure Frontdoor CDN With AzDevOps
