Azure Front Door with Storage Account Containers for Each Environment – 404 Issue

Question

Hello,

I am implementing Azure Front Door with a single Azure Storage Account that contains multiple containers, each designated for a specific environment (e.g., dev, QA, UAT, etc.). My goal is to use Azure Front Door Private Endpoints to securely expose the respective containers per environment while integrating this setup with Azure DevOps release pipelines.

Issue:

• I have configured Azure Front Door routing to forward requests to the correct storage container for each environment.
• However, I am consistently encountering a 404 - WebContentNotFound error when trying to access the content via Azure Front Door.
• The container paths exist in the storage account, but Azure Front Door does not seem to resolve them correctly.

Configuration Details:

• Storage Account: One storage account with multiple environment-specific containers.
• Azure Front Door Routing:
  • Patterns to match: /dev-finance-central/*, /*, /path
    • Origin path: /dev-finance-central/
      • Forwarding protocol: Match incoming request
      • All containers are private, and I am using private endpoints.

Questions:

1. How should the Azure Front Door routing rules be set up correctly for each environment-specific container?
2. How do I ensure that Azure Front Door properly forwards requests to the storage container via the private endpoint?
3. Is there an additional configuration required in Azure Storage, Private Endpoints, or Azure Front Door to avoid the 404 WebContentNotFound error?
4. How can I integrate this setup into Azure DevOps release pipelines for smooth deployment?

I have attached screenshots of my Azure Front Door routing setup, storage account structure, and error message for reference.

Any guidance on resolving this issue would be highly appreciated.

Thanks!

Issue:

• I have configured Azure Front Door routing to forward requests to the correct storage container for each environment.
• However, I am consistently encountering a 404 - WebContentNotFound error when trying to access the content via Azure Front Door.
• The container paths exist in the storage account, but Azure Front Door does not seem to resolve them correctly.

Configuration Details:

• Storage Account: One storage account with multiple environment-specific containers.
• Azure Front Door Routing:
  • Patterns to match: /dev-finance-central/*, /*, /path
    • Origin path: /dev-finance-central/
      • Forwarding protocol: Match incoming request
      • All containers are private, and I am using private endpoints.

Questions:

1. How should the Azure Front Door routing rules be set up correctly for each environment-specific container?
2. How do I ensure that Azure Front Door properly forwards requests to the storage container via the private endpoint?
3. Is there an additional configuration required in Azure Storage, Private Endpoints, or Azure Front Door to avoid the 404 WebContentNotFound error?
4. How can I integrate this setup into Azure DevOps release pipelines for smooth deployment?

I have attached screenshots of my Azure Front Door routing setup, storage account structure, and error message for reference.

Any guidance on resolving this issue would be highly appreciated.

Thanks!
Abdul

Answer 1

Hi @Gafoor, Abdul

Since you are using Azure Front Door with the Standard tier to access the storage account privately via a private endpoint, the Standard tier does not support the private connectivity option, even if the private endpoint is enabled in the storage account.

If you are not using the private link feature and are still on the Standard tier in Azure Front Door, your origin will be accessed publicly. This means your storage account should be on a public network, as there is no way to access it privately from AFD.

You can refer to the AFD architect regarding the traffic flow, including how AFD will access the PaaS service or how the origin can be hosted in a virtual network (e.g., virtual machine).

Reference: Secure your Origin with Private Link in Azure Front Door Premium | Microsoft Learn

I hope this is helpful! Do not hesitate to let me know if you have any other questions.