Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'LinuxDynamicWorkersNotAllowedInResourceGroup' error occurs when trying to have an app service and a linux function app in same resource group #1952

Closed
onionhammer opened this issue Jul 7, 2021 · 10 comments

Comments

@onionhammer
Copy link

This seems like a relatively common need for an unsupported scenario;

You want a web app (on linux), and you want a function app (on linux).

However, if you have a linux app service for webapps, you cannot create a dynamic linux app service in the same resource group:

      {
        "code": "ValidationForResourceFailed",
        "message": "Validation failed for a resource. Check 'Error.Details[0]' for more information.",
        "details": [
          {
            "code": "LinuxDynamicWorkersNotAllowedInResourceGroup",
            "message": "Linux dynamic workers are not available in resource group yourResourceGroup. Use this link to learn more http://go.microsoft.com/fwlink/?LinkId=825764."
          }
        ]
      }

https://github.com/Azure/Azure-Functions/wiki/Creating-Function-Apps-in-an-existing-Resource-Group

Are there plans to eventually fix this limitaiton?

@balag0
Copy link

balag0 commented Jul 7, 2021

Yes, There is work in progress to remove this limitation. But no ETA yet.

@v-anvari
Copy link

Closing this issue as the required information is provided, please find any further updates in the App Service Announcements issues page: https://github.com/Azure/app-service-announcements/issues

@petrkoutnycz
Copy link

How does this look like please at the moment? This is really awkward limitation :-/

@GeorgDangl
Copy link

We also just hit this yesterday. Not a big deal, since it's easy to workaround, but makes deployment a bit more complicated and ugly. Is there any current status for this?

@shakthifuture
Copy link

I am also facing same issue, what is the solution?

@florinasaveiext
Copy link

In my case, I just choose to use Windows Function Apps since it didn't really matter to me but I did want to keep the AppService Plan on Linux.

@elier
Copy link

elier commented Aug 6, 2023

I encountered this issue today while deploying with bicep. I'm creating 2 service plans with 'Microsoft.Web/serverfarms@2022-09-01', one for an App Service, and another for 2 Functions App.
I managed to make it work by changing the order of the creation.

  • I create the service plans first, and the Function App's service plan is also created before the App Service plan.
  • Then, I create the App Service at the very end, and it works.

@Sharparam
Copy link

We are encountering this as well, but strangely it works in one resource group but not the other.

They are both set up the same way using a bicep file.

@onionhammer
Copy link
Author

Odd to close this issue years before it's actually available

@ggirard07
Copy link

@bhagyshricompany any chance to look back into this?
In my case, the same ARM template is working fine in one subscription, while it fails with Requested features 'Dynamic SKU, Linux Worker' not available in resource group Sandbox-BuilderRestoreBkp2. Please try using a different resource group or create a new one. in another subscription...
I do have both app service plan for function apps in the template, one is Y1 Linux and the other is EP1 Linux, both in East US 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants