Unable to create a new Function App: Code: DeploymentNotFound

SeaDude 106 Reputation points
2022-07-27T20:13:21.903+00:00

I'm unsure what is going on. I've created a number of Function Apps over the years, largely without issue. For some reason, when trying to create a Function App in US WEST 3, I'm stuck with this error:

225436-image.png

Going through the "Self Diagnostics" result in "Everything Ok".

How should I troubleshoot this?

Thank you

---

EDIT 1

Trying to create in US WEST 2 results in ANOTHER error: This region has quota of 0 instances for your subscription. Try selecting different region or SKU.

Does this mean that US WEST 2 does not have any Linux Consumption plan availablilty?

225299-image.png

---

EDIT 2

Was successful created a new Function App in US WEST. Hm. Its bizarre to have two different errors when attempting to create Function Apps in two different regions.

Ideally, the error would present itself earlier in the creation wizard. Like, as soon as you select a region where the resource you're attempting to create is unavailable to be created.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,200 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,813 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ryan Hill 25,476 Reputation points Microsoft Employee
    2022-07-28T03:04:56.663+00:00

    Hi @SeaDude ,

    For your first ask, DeploymentNotFound really doesn't have anything to do with the resources being deployed per se. If you already had the resources created and you're deploying your artifacts, that's more than likely why you got Everything Ok from diagnostics. It really depends on how you were you deploying; CI/CD, VS/Code, FTP, etc. There could've been a transient error at time of deployment resulting in the received error message.

    Per your first edit, this normally occurs when too many resources have been procured in subscription in a short period of time. That platform will throttle down the subscription for that region to ensure a bad actor isn't requesting a lot of resources at once.

    I don't know if you have any deployment logs with the failures in it, but I hypothesize that the continued failed deployments may have triggered the throttled state. If it occurs again, you can create a support request asking for an increase in your quota.

    0 comments