An Azure service that provides an event-driven serverless compute platform.
Hello Martin Konicek (DHL IT Services),
Thanks for your question about migrating Azure Functions from Linux Consumption (Dynamic Y1) to Flex Consumption. There's no direct "migration button" because the plans have significant architectural differences you'll need to create a new Flex Consumption app and migrate your configuration. Here's the correct approach:
Migration Steps
Check Eligibility: Ensure you have Azure CLI 2.77.0 or later installed. Run this command to list eligible apps for migration:
text
az functionapp flex-migration list
This returns eligible and ineligible apps with reasons (e.g., unsupported region or language stack).
Start Migration: Use the new Azure CLI migration command to automate most steps:
text
az functionapp flex-migration start --source-name <SOURCE_APP_NAME> --source-resource-group <SOURCE_RG> --name <NEW_APP_NAME> --resource-group <NEW_RG>
Create the new resource group in the same region as your current app first.
Manual Migration (Alternative): If you prefer full control or the CLI doesn't work, follow the official migration guide, which covers creating a new Flex app, transferring settings (excluding deprecated ones), configuring networking, managed identities, and deploying code.
Key Points
No in-place upgrade: You create a new Flex Consumption app, not convert the existing one.
Deadline: Migrate before September 30, 2028 to avoid service disruptions.
Benefits: Flex offers better performance, VNET integration, always-ready instances, and improved scaling.
The Azure CLI migration command (available since August 2025) simplifies the process significantly compared to manual steps. Check the migration guide for detailed instructions!
Best Regards,
Jerald Felix