Front Door implementation for optimal cost analysis

Question

I'm looking at Front Door as a way to provide general and specific redirects for old sites we want to archive.

We might have a blanket rule of redirecting any request for site A to the homepage of site B, as well as specific requests for site A to a specific path on site B or site C, and so on.

E.g.

• siteA.example.com/* -> siteB.example.com/*
• siteA.example.com/1 -> siteB.example.com/1
• siteA.example.com/2 -> siteC.example.com/2
• siteD.example.com/* -> siteB.example.com/*
• etc.

There are a few sites we want to archive and redirect to a combination of newer sites; it's not always going to be one-to-one.

So far, Front Door's flexibility is great for configuring this.

Ideally we would like to be able to see the usage levels and cost implications of these redirects, so that we might optionally pass the cost on to the other internal team whose site we're archiving.

My question is: should I just try to do this with one Front Door resource, or should I create one for each archived site?

I have one Front Door resource at the moment, and I don't think it will break down cost per 'front-end' within the Resource (a.k.a. the archived site URL that we're redirecting)

Answer 1

Azure Front Door routing rules are charged at $0.03/hr for the first 5 rules, then $0.012 per rule per hour after that. It should be easy to keep track of how long each rule existed for.

If you also want to track the ingress and egress, that will be almost impossible on a single Front Door. You might need to break those down into multiple Front Doors to get an accurate estimate of billing.