Optimization Azure Function and Azure Container Registry Utilization

Udit Shah 0 Reputation points
2025-06-28T07:33:51.89+00:00

As a part of AI deployment,

5 Azure Functions had been deployed and corresponding 5 container registries were attached.

Now the count has been reduced to one. The credits utilization amount has not decreased to 1/5th of the previous one and it is still utilization similar quantum of credits inspite of decreasing count of functions and container registries.

So, now only 2 resources ( 1 Function - EP1 and 1 Container Registry ) are deployed instead of 10 ( 5 Functions - EP1 and 5 Container Registry ). However the headers of credits utilization are still showing same utilization on daily basis.

Example : If during deployment of 10 resources - utilization was USD X dollars under four headers, it is still showing USD X when only 2 resources are deployed.

This is a part of optimization exercise and reducing the unrequired utilization of cloud resources as a part of discretionary update.

Looking forward to inputs so that there is required utilization of resources and unrequired increase in resource utilization is decreased.

Here is the image that compares pricing of Functions under 4 headers. In the month of May, 5 resources had been deployed which were reduced to 1 in the month of June. However it is still showing same price point

final_image_may_june.png

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,940 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Krishna Chowdary Paricharla 805 Reputation points Microsoft External Staff Moderator
    2025-06-30T02:47:11.65+00:00

    Hello Udit Shah,

    Thanks for reaching out!
    The reason your cost hasn't dropped 1/5th is likely because EP1 plan resources are provisioned independently of function count—it's about runtime allocation (CPU/Memory), not the number of deployed functions.

    • EP1 plan charges are based on vCPU and memory usage over time, not number of functions.
    • Reduce minInstances or remove Always Ready instances to lower idle cost.
    • Monitor execution duration, memory usage, and instance scaling to identify inefficiencies.
    • Use Basic SKU unless premium features (e.g., geo-replication) are needed.
    • Enable retention policies to auto-delete unused images.
    • Regularly clean up old image versions to reduce storage cost.

    For your reference, please go through this following documentation:

    Azure Functions pricingAzure Container Registry pricing

    Functions scaling

    Container-registry-retention-policy

    Best practices for Azure Container Registry

    Hope this helps!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.