|
| 1 | +--- |
| 2 | +title: "Quickstart: Migrate Linux Consumption apps to Flex Consumption using GitHub Copilot" |
| 3 | +description: Use GitHub Copilot with Azure skills to interactively migrate your Linux function apps from the Consumption plan to the Flex Consumption plan. |
| 4 | +ms.service: azure-functions |
| 5 | +ms.collection: |
| 6 | + - migration |
| 7 | +ms.date: 04/07/2026 |
| 8 | +ms.topic: quickstart |
| 9 | + |
| 10 | +#customer intent: As a developer, I want to use GitHub Copilot to more easily migrate my Linux Consumption plan function apps to the Flex Consumption plan so that I can get better performance and features. |
| 11 | +--- |
| 12 | + |
| 13 | +# Quickstart: Migrate Linux Consumption apps to Flex Consumption using GitHub Copilot |
| 14 | + |
| 15 | +In this quickstart, use GitHub Copilot with the Azure skills plugin to interactively migrate your Linux function apps from the [Consumption plan](../consumption-plan.md) to the [Flex Consumption plan](../flex-consumption-plan.md). Copilot automates most of the migration, including assessment, app creation, configuration, deployment, and validation. |
| 16 | + |
| 17 | +> [!IMPORTANT] |
| 18 | +> This article demonstrates how to use Copilot to recreate an existing Linux Consumption app in a Flex Consumption plan. The [Azure skill](https://github.com/microsoft/GitHub-Copilot-for-Azure/blob/main/plugin/skills/azure-upgrade/references/services/functions/consumption-to-flex.md) that Copilot uses to achieve the migration work is designed to work with most Linux Consumption apps. For high-value production apps, apps with complex deployments or dependencies, and for Consumption apps running on Windows, follow [Migrate Consumption plan apps to the Flex Consumption plan](migrate-plan-consumption-to-flex.md). |
| 19 | +
|
| 20 | +You can review the specific skill used by Copilot when performing this migration in the [GitHub Copilot Azure skills repository](https://github.com/microsoft/GitHub-Copilot-for-Azure/blob/main/plugin/skills/azure-upgrade/references/services/functions/consumption-to-flex.md). |
| 21 | + |
| 22 | +## Prerequisites |
| 23 | + |
| 24 | ++ An Azure subscription with one or more Linux function apps running on the Consumption plan. |
| 25 | + |
| 26 | ++ The account used for the migration must have the **Owner** or **Contributor** role in the resource group containing your function apps. For the full list of required permissions, see [Prerequisites](migrate-plan-consumption-to-flex.md#prerequisites). |
| 27 | + |
| 28 | ++ [Azure CLI](/cli/azure), version 2.77.0 or later. |
| 29 | + |
| 30 | ++ Configure GitHub Copilot in your preferred mode: |
| 31 | + |
| 32 | + [!INCLUDE [functions-copilot-setup](~/includes/functions-copilot-setup.md)] |
| 33 | + |
| 34 | +## Migrate your apps |
| 35 | + |
| 36 | +Use this prompt to start an interactive migration that scans your subscription and lets you choose which apps to migrate: |
| 37 | + |
| 38 | +``` |
| 39 | +migrate my linux function apps in azure from consumption to flex consumption |
| 40 | +``` |
| 41 | + |
| 42 | +Copilot follows the [migration guide](migrate-plan-consumption-to-flex.md) and identifies your eligible Linux Consumption apps, lets you choose which ones to migrate, and then handles assessment, app creation, and configuration migration for each app. |
| 43 | + |
| 44 | +You might be asked by Copilot for feedback during the migration, as needed for a successful migration. |
| 45 | +## Migration results |
| 46 | + |
| 47 | +When complete, Copilot generates helpful output, which includes: |
| 48 | + |
| 49 | ++ A summary table with the status of each migrated app. |
| 50 | ++ A brief summary of the overall tasks accomplished. |
| 51 | + + A list of any remaining post-migration tasks that it couldn't complete or that must be done by you. |
| 52 | + |
| 53 | +## Verify the migration |
| 54 | + |
| 55 | +While Copilot does its best to validate the state of your migrated app, always verify that your new app works correctly: |
| 56 | + |
| 57 | +1. In the [Azure portal](https://portal.azure.com), ensure that each new Flex Consumption app shows a **Status** of `Running`. |
| 58 | + |
| 59 | +1. Call at least one HTTP trigger endpoint or otherwise trigger your new app to confirm it responds as expected. |
| 60 | + |
| 61 | +## (Optional) Remove the original app |
| 62 | + |
| 63 | +When you're confident the new app works correctly, remove the original Consumption plan app. If you keep the original app in place, remember to [disable any triggers](../disable-function.md) to avoid duplicate processing or competing with the new app. |
| 64 | + |
| 65 | +Use this command to remove the original app: |
| 66 | + |
| 67 | +``` |
| 68 | +delete my original consumption app <ORIGINAL_APP_NAME> |
| 69 | +``` |
| 70 | + |
| 71 | +Copilot always asks for your explicit confirmation before deleting anything. |
| 72 | + |
| 73 | +> [!IMPORTANT] |
| 74 | +> Before deleting, make sure you migrate all functionality, verify no traffic goes to the original app, and back up any relevant logs or configuration. |
| 75 | +
|
| 76 | +## Next step |
| 77 | + |
| 78 | +> [!div class="nextstepaction"] |
| 79 | +> [How to use the Flex Consumption plan](../flex-consumption-how-to.md) |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments