Share via

Azure Functions App Deployment

Pavlin Penev 20 Reputation points
2026-02-25T15:40:13.0966667+00:00

Hello,

I'm experiencing an issue with my Functions app deployment since around 11:00AM today. The GitHub Action says that the Kudu Service is unavailable. Tried to curl it - same response. I've investigated the Service Health Issues in the portal and came across an alert where the message stated: 

What happened?

Between 11:09 UTC and 11:13 on 25 February 2026, a platform issue resulted in an impact to the Function Apps hosted on Flex Consumption SKU in the West Europe region. Customers may have experienced HTTP 500-level response codes, experience timeouts or high latency when accessing Function Apps hosted on Flex Consumption SKU in this region.

What went wrong, and why? The issue was caused by a sudden surge in demand that exhausted available compute capacity in the West Europe region, resulting in insufficient resources to support Function Apps running on the Flex Consumption plan.

Did someone experience such an issue as well or is it just me? Thank you in advance.

Kind Regards

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

{count} votes

Answer accepted by question author
  1. Siddhesh Desai 3,935 Reputation points Microsoft External Staff Moderator
    2026-02-25T15:59:41.7966667+00:00

    Hi @Pavlin Penev

    Thank you for reaching out to Microsoft Q&A.

    Thanking for confirming that the issue is resolved.

    Apologies for the inconvenience, yes, it's a known outage where consumption apps were failing in West Europe. I could see the incident is mitigated and you will be able to deploy your Function successfully. If it fails again, try after few hours as the incident was just mitigated and it takes time for the fix to populate from the backend.

    Here are the details of Incident:

    • A regional upgrade caused simultaneous VM restarts, triggering a surge in OS image downloads from a shared storage account, leading to egress throttling and VM stabilization failures. This caused capacity loss and intermittent 500 errors in Consumption functions. Mitigations included pausing deployments, increasing storage egress limits, blocking Linux image downloads temporarily, and controlled network throttling to reduce load.
    • The team coordinated on the incident bridge, reviewed and published final communications, confirmed incident closure, and restored operational settings to default values. Immediate mitigations were implemented, and longer-term architectural changes were discussed to prevent recurrence.
    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-02-25T15:40:55.17+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It appears that you are experiencing a known issue with Azure Functions hosted on the Flex Consumption SKU in the West Europe region. According to the service health alert, there was a platform issue between 11:09 UTC and 11:13 on 25 February 2026, which caused HTTP 500-level response codes, timeouts, and high latency due to a surge in demand that exhausted available compute capacity. This means that it is not just you; other customers may have faced similar issues during that time.

    If you continue to experience problems, you may want to check the Azure portal for any updates or further service health notifications regarding this issue. Additionally, you can try accessing the Kudu service again later as the platform issues may be resolved.

    0 comments No comments

Your answer

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