This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 89%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
When trying to publish a new Azure Function project from Visual Studio 2019 I have started receiving the error "Consumption functions apps are not available in a location and resource group that match a non-Consumption functions app". I have selected our normal resource group and location (north central U.S.) but now something is preventing us from being able to publish to that same location and resource group.
All functions in that resource group had been consumption functions. However, we were getting started with an Azure Data Factory demo and tried to publish the ADF project to its own new resource group and that failed. So we ended up publishing it to our main resource group. Ever since doing so we have been unable to publish any new Azure functions to this resource group.
Error is displayed in the attached.
116505-image.png
An Azure service that provides an event-driven serverless compute platform.
@Rob Kribs Looks like you might hit this limitation. Can you confirm what are the function app resources (Consumption/non-consumption) in your resource group and what are the OS and location for individual function app. Did you observe the same behavior in new resource group with all the combination of your existing function app in your failed resource group.
I am suspecting this has something to do with the other resources in that resource group (especially the ADF resources). Can you try removing ADF related resources from the RG and redeploying. It will help us isolate the issue.
If it resolves the issue, then we can figure out why you can't deploy your ADF project to a new resource group and tackle that separately.
Hope this makes sense!
Hi Jaliya, I agree with your suspicions that it is something related to a recent deployment of ADF. I moved all of the related ADF items to their own resource group and unfortunately am still getting the same answer when I try to deploy any new function to the original resource group and location. The existing functions in that resource group are all working, I am just unable to deploy any new ones. I have reviewed that original resource group as best I can an it appears everything remaining in it are all on a consumption plan.
Any ideas of anything else I could look at, or next steps I can take to get support from Azure? My thought is to start deploying all new functions into a new resource group from this point forward. If someone could answer if it is best practice to have a RG per deployment, or if it is ok to deploy several related functions to the same RG?
Thanks.
I am sorry for the delayed response.
Hmm, I see. Maybe you should open up a technical support ticket with Azure. You can do it from the portal itself, they should be able to investigate what's happening behind the scene. While deploying to a new RG fixes the issue, I think it's quite important we find out the root cause. Because in case you get it again with the new RG, we are back to the beginning.
Resource group basically is a container for resources that you want to manage as a group. Saying that there are some important factors that should be followed when maintaining resource groups. (Read more here: Resource groups).
.