# Multiple Front Door Standard or Premium Profiles With Few Endpoints Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/multiple-front-door-standard-or-premium-profiles-with-few-endpoints Azure Front Door Standard and Premium charge a fixed monthly base fee for every profile, on top of request and data transfer charges. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Azure Front Door Standard and Premium charge a fixed monthly base fee for every profile, on top of request and data transfer charges. PointFive Research Cloud cost research at PointFive Azure service [Azure Front Door](https://www.pointfive.co/efficiency-hub/cloud-services/azure-front-door) Category [Networking](https://www.pointfive.co/efficiency-hub/service-category/networking) Reference CER-0412 Type Inefficient Architecture ## Explanation Why the waste happens and who it affects. A single profile can hold several endpoints, each with its own routes and custom domains, yet teams often create one profile per application, microservice, team or environment. Each extra profile adds another base fee while serving only one endpoint and often little traffic. The pattern is common after migrating from Front Door (classic), where a profile had no base fee, and in estates where every dev and test environment gets its own Premium profile. Azure Advisor flags subscriptions that contain multiple Standard or Premium profiles with a small number of endpoints. In Microsoft's own pricing example, 80 single-service Premium profiles pay 26,400 USD a month in base fees, against 1,320 USD for the same services consolidated into four multi-endpoint profiles. ## Billing model The pricing dimensions that drive this cost. Standard and Premium bill per profile plus usage; routing rules and the first 100 custom domains are free. Base fee A fixed charge per profile, calculated hourly; the pricing page lists 35 USD a month for Standard and 330 USD a month for Premium Requests Billed per 10,000 requests from clients to the edge by pricing zone, with a higher unit rate on Premium Outbound data transfer Billed per GB from edge to client and from edge to origin by pricing zone Endpoints per profile A profile can contain up to 10 endpoints on Standard and 25 on Premium, according to the Azure Advisor recommendation ## How to detect 5 checks to find it in your estate. - Review the Azure Advisor cost recommendation Consider using multiple endpoints under one single Front Door Standard/Premium profile - List Microsoft.Cdn/profiles with a Standard\_AzureFrontDoor or Premium\_AzureFrontDoor SKU and count the afdEndpoints under each; profiles with one or two endpoints are consolidation candidates - Group the candidate profiles by owner, environment and tier to find sets that could share a profile, for example all dev and test endpoints or all microservices of one application - For Premium profiles, check whether they actually use Premium-only capabilities such as managed WAF rule sets, bot protection or Private Link to origins; profiles that do not could share a Standard profile - In Cost Management, group Front Door cost by resource and meter to see how much of each profile's cost is the base fee compared with requests and data transfer ## How to fix 4 ways to remove the waste. - Consolidate endpoints that belong together into fewer profiles, within the endpoint limit per profile, and delete the emptied profiles to stop their base fees - Keep separate profiles only where there is a real boundary, such as separate owners needing separate RBAC, a genuine need for Premium on some endpoints but not others, or reaching the endpoint limit - Place dev and test endpoints in a shared Standard profile unless they must test Premium-only features - When migrating several Front Door (classic) profiles, plan the target as a small number of multi-endpoint profiles rather than one Standard or Premium profile per classic profile ## Documentation Vendor references for pricing and configuration. - [Compare Pricing Between Azure Front Door Tiers learn.microsoft.com](https://learn.microsoft.com/en-us/azure/frontdoor/understanding-pricing) - [Cost recommendations - Azure Advisor learn.microsoft.com](https://learn.microsoft.com/en-us/azure/advisor/advisor-reference-cost-recommendations) - [Endpoints in Azure Front Door learn.microsoft.com](https://learn.microsoft.com/en-us/azure/frontdoor/endpoint) - [Pricing - Front Door azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/frontdoor/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Front Door CER-0413 ### [Front Door (classic) Profiles With Many Routing Rules and Domains](https://www.pointfive.co/efficiency-hub/inefficiencies/front-door-classic-profiles-with-many-routing-rules-and-domains) Azure Front Door (classic) uses an older pricing model that charges for configuration as well as traffic: every routing rule is billed per hour, custom domains beyond the first 100 are billed monthly, inbound data is billed per GB, and... Networking - Azure Data Factory V2 CER-0261 ### [Suboptimal Integration Runtime Region Selection in Azure Data Factory](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-integration-runtime-region-selection-in-azure-data-factory-0bcad) When Integration Runtimes use the default "Auto Resolve" region setting, the work does not always run in the region where the data lives. For copy activities, Azure makes a best effort to run in the sink data store's region (or the closest... Networking - Azure Firewall CER-0415 ### [Per-Spoke Azure Firewall Deployments Instead of a Shared Hub Firewall](https://www.pointfive.co/efficiency-hub/inefficiencies/per-spoke-azure-firewall-deployments-instead-of-a-shared-hub-firewall) Azure Firewall is designed to be deployed centrally, in a hub virtual network or a Virtual WAN secured hub, and shared by the spoke virtual networks connected to that hub in the same region. In decentralized estates, application teams or... Networking --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.