Preflight Checklist

• I have installed the latest version of GitHub Copilot for Azure in VS Code.
• I have checked existing resources, including using the /help command in the chat window.
• I have searched for similar issues.

Repro Steps

1. Install the Skills into GitHub Copilot.

2. Run this prompt "Create an Azure Functions Node 24 app that has a staging slot and make sure that WEBSITE_CONTENT_SHARE is different on each slot and also ensure that the created Storage account has logging enabled for Azure Files. Create a Node 24 Function App but do not deploy. "

3. There is no Elastic Premium Quota so I ask to switch back to Consumption and then it hallucinates

Asked user: Your subscription has 0 Elastic Premium (EP) App Service ...
└ User responded: Switch to the Dynamic Plan aka Windows Consumption

◐ The user wants to switch to the Consumption plan (Dynamic/Y1). Let me update the Bicep to use a Consumption plan.

For Consumption plan on Linux:

• SKU: Y1, tier: Dynamic
• kind: 'functionapp,linux'- reserved: true
• No need for WEBSITE_CONTENTAZUREFILECONNECTIONSTRING or WEBSITE_CONTENTSHARE on Linux Consumption

Wait, actually on Windows Consumption you DO need WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE.
The user said "Windows Consumption" so let me use Windows.

Actually, the user said "Dynamic Plan aka Windows Consumption". But our Bicep has kind: 'functionapp,linux' and
linuxFxVersion: 'Node|24'.

I need to switch to Windows for Node.js, which means using WEBSITE_NODE_DEFAULT_VERSION instead of
linuxFxVersion. But here's the issue: Consumption plans don't support deployment slots at all—only Standard,
Premium, and Isolated tiers do. The user originally wanted a slot, but with Y1/Dynamic, that's not possible.

Let me update the Bicep template accordingly: I'll change to a Y1/Dynamic App Service Plan, set kind: 'functionapp' without the reserved property, use WEBSITE_NODE_DEFAULT_VERSION: '~24' for the runtime, and
remove the staging slot since it's not supported on Consumption. I'll also need to include
WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE for proper file storage configuration.

● Asked user: Note: The Consumption (Dynamic/Y1) plan does NOT support ...
└ User responded: I don't want Flex I want Windows Consumption with Slots Suppo...

◐ The user wants Windows Consumption with Slots support. But Consumption plan (Y1/Dynamic) does NOT support deployment
slots. This is a hard limitation of the Azure platform.

Slot support by plan:

• Free/Shared: 0 slots- Basic: 0 slots (wait, actually Basic B1 has 0 slots? Let me think...)
• Standard (S1+): 5 slots
• Premium (P1v2/P1v3): 20 slots- Elastic Premium (EP1+): 20 slots- Isolated: 20 slots

Consumption (Y1/Dynamic) definitely does not support slots.

This is a platform limitation, so I need to suggest alternatives that actually support slots—like Standard S1,
Premium V2/V3, or Elastic Premium plans—since Consumption just won't work for this requirement.

Asked user: Since Consumption doesn't support slots, should I switch ...
└ User responded: The Windows Consumption plan that isn't flex supports Slots

◐ The user insists that Windows Consumption supports slots. Let me research this to check if this is actually true.
Let me do a web search to verify.

Actually, I know for a fact that the Azure Consumption plan (Y1/Dynamic) does NOT support deployment slots. This has
been a long-standing Azure limitation. Only Premium and Standard/higher dedicated plans support slots for
Functions.

But wait - let me double-check. Maybe something changed recently (since this is February 2026). Let me do a web
search.

● Web Search: Does Azure Functions Consumption plan support deployment slots in 2025 2026?
└ {"type":"text","text":{"value":"As of 2025 and into 2026, Azure Functions on ...

◐ The user is correct! Windows Consumption plan DOES support deployment slots (up to 2, including production, so 1
staging slot). I was wrong. Let me update the Bicep to use Windows Consumption (Y1/Dynamic) with a staging slot.

Key changes needed:

1. App Service Plan: SKU Y1, tier Dynamic, kind removed or set to functionapp
2. Function App: kind: 'functionapp' (no linux), remove linuxFxVersion, add WEBSITE_NODE_DEFAULT_VERSION
3. Keep the staging slot
4. For Windows Consumption, we need WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE

Prompt

Create a Node 24 Functions App on the Elastic Premium with a Slot and make sure that the Storage account has Azure
Files logging enabled . Create a Node 24 app with a HTTP Trigger but do not deploy it.

Expected Result

That when I suggest to switch to a Consumption SKU that supports slots it understands that this is possible.

Actual Result

It tells me that no the Consumption plan doesn't support slots.

Attachments

No response

Regression?

No response

Additional Context

No response