An Azure service that provides real-time messaging for web applications using WebSockets and the publish-subscribe pattern.
Azure Front Door Standard/Premium profiles incur an hourly base fee for every hour (or partial hour) that the profile is deployed, regardless of whether the rest of the subscription is being actively used. Charges also apply for requests and data transfer while the profile exists.
If Front Door continued to run after the proof of concept, it means the Front Door profile itself was still deployed and accruing its base fees. To stop further charges, delete or disable the Front Door profile in the Azure portal so it is no longer deployed.
To pursue a refund for the past charges, open a billing/support request with Microsoft so a billing engineer can review the situation and determine eligibility. Billing support is free, and invoice-level credits (for example, for data egress when leaving Azure) are handled through Azure Support requests. After canceling all relevant subscriptions and stopping consumption, support can evaluate whether any credits or refunds can be applied.
Key points for the process:
- Ensure all Azure Front Door profiles are deleted or fully deprovisioned so base fees stop.
- Cancel any remaining Azure subscriptions associated with the environment.
- In the Azure portal, create a Billing support request describing the unintended ongoing Front Door charges and the date the POC was supposed to end.
- Work with the assigned billing engineer to review invoices and determine whether any credits or refunds can be issued.
Note that standard Azure service charges (including Azure Front Door) are generally billable for as long as the resources remain deployed. Credits are at Microsoft’s discretion and are processed only after a formal support review.
References: