Reputation: 5496
The new "Consumption" tier plans that you can utilise for Functions don't allow you to change the process bitness via the Portal. Is some other way I can flip the process to 64 bits as it's required for DocDB access.
Upvotes: 3
Views: 9195
Reputation: 6245
Azure Functions consumption plan is billed based on resource consumption and executions. Consumption plan pricing includes a monthly free grant of 1 million requests and 400,000 GB-s of resource consumption per month. Customers can also run Functions within their App Service plan at regular App Service plan rates.
Source: Functions Pricing
Try to Kudu into the Function App based on the Consumption pricing tier App Service Plan, found out that the total disk space is 1GB, which is equivalent to the Free or Shared pricing tier of the standard App Service Plan.
Bitness
The Basic, Standard, and Premium tiers support 64-bit and 32-bit applications.
The Free and Shared plan tiers support 32-bit applications only.
Source: https://learn.microsoft.com/en-us/azure/app-service-web/web-sites-scale#bitness
The conclusion is the Consumption pricing tier App Service plan is equivalent to Free/Shared pricing tier App Service plan, which explains why it can only support 32-bit.
Upvotes: 0
Reputation: 12538
Currently, 64-bit selection is disabled for Azure Functions (both, in consumption and app service plans). We're working on some validation to enable that, so customers requiring a 64-bit can make that change.
One thing to note is that the DocumentDB team has added 32-bit support to their latest release (1.11.3), and although we haven't upgraded to that yet (which will happen), you can reference their package directly and use their client in Functions running in 32 bit.
David's answer also gives you a way to enable 64-bit today.
Upvotes: 4
Reputation: 43193
You can set this by API. But note that it is not officially supported until you see the option show up in the portal.
Here is an easy way to do it:
config/web
under it in the treeUpvotes: 6