Edit

Migrate local agent workflows to Azure Functions hosted skills

In this article, you use the Azure Functions migration skill with your coding agent to move a local workflow to Azure Functions hosted skills. The example is a weekly GitHub activity report that runs on your computer. You migrate it to a timer-triggered hosted skill that runs in Azure.

The migration skill, azure-functions-hosted-skills-migrate, checks the workflow's dependencies and creates a function app from the Azure Functions hosted skills template. The deployed app doesn't need your computer or an active coding-agent session. You configure service access for the app separately from your local sign-in.

Important

Azure Functions hosted skills is currently in preview. Features, configuration names, and supported connectors can change before general availability.

Choose a workflow to migrate

You can start from an automation prompt, agent definition, reusable skill, or code. The workflow must use operations that the deployed app can perform. Examples include:

Local workflow Migration approach
Read GitHub issues and pull requests, and summarize repository activity. Use GitHub Connector operations to retrieve the required data.
Read mail, calendar entries, Teams messages, or a known SharePoint file. Check the corresponding connector for the required operations and account access.
Format or analyze data with a script. Convert the processing to Python and use explicit inputs and outputs instead of local file paths.

These examples are candidates for migration, not a guarantee that every operation is available. The migration skill checks the required fields, filters, permissions, and service availability before generating the integration. If an operation isn't supported, you can change the workflow or leave it unmigrated. For exclusions, see Migration limits.

Prerequisites

  • GitHub Copilot CLI, the GitHub Copilot app, Claude Code, or Codex CLI. For plugin installation, see Install Azure Functions skills.
  • The instructions and dependencies for the workflow you want to migrate. Remove secrets and sensitive data before sharing them with your coding agent.
  • An Azure account with an active subscription. Create an account for free.
  • Azure CLI and Azure Developer CLI (azd) for deployment.
  • Permissions to create the Azure resources and assign the roles required by the generated app.
  • Access to a model deployment supported by Azure Functions hosted skills and to the services the workflow uses.

Note

Running the migrated workflow can incur charges for Azure resources and model calls. Review the resources and expected usage before deployment.

Install Azure Functions skills

Install the Azure Functions skills plugin from the Azure/azure-functions-skills marketplace. If you already installed the plugin, update it before continuing.

  1. Start an interactive Copilot CLI session.

  2. Add the marketplace and install the plugin:

    /plugin marketplace add Azure/azure-functions-skills
    /plugin install azure-functions-skills@azure-functions-skills
    

    To update an existing installation, run:

    /plugin update azure-functions-skills@azure-functions-skills
    

For other supported clients and current installation steps, see the Azure Functions skills installation instructions. Installing the @azure/functions-skills npm package alone doesn't install the coding-agent plugin.

Note

The migration skill requires Azure Functions skills version 0.0.7-preview or later. Installing the plugin from the marketplace retrieves the latest version from the repository's main branch. If you already installed the plugin, update it before continuing.

Check your environment

  1. Start a new coding-agent session in the workspace that contains your workflow.

  2. Enter this prompt to check the required tools and language runtimes:

    Use azure-functions-setup to check my environment for an Azure Functions
    hosted skills project.
    
  3. Follow the setup guidance to install or configure any missing tools.

The setup skill checks your environment. It doesn't migrate the workflow.

If the agent can't find azure-functions-hosted-skills-migrate, update the plugin by following the installation instructions, and then start a new session.

Prepare the source workflow

Start with an existing local workflow, such as an Automation in the GitHub Copilot app or a skill configured in Claude Code or Codex. This example uses an existing GitHub Copilot Automation named Weekly GitHub report. The following block shows the instructions saved in that Automation, not a request to create a new one. You can use your own workflow instead.

Each week, review Azure/azure-functions-host and
Azure/azure-functions-python-worker.

List issues created or updated during the previous seven days, including
closed issues. Summarize open pull requests that need attention.
Include source links and explain the evidence for each suggested action.

Distinguish issues from pull requests. Report missing data and access errors.
Don't change GitHub content or local repositories.
Save the report in the Automation run's final response.
  1. Select the workflow you want to migrate. Include the instructions, referenced skills, and scripts it needs.

  2. Make the source available in your coding-agent session. For a GitHub Copilot Automation, provide its name, prompt, and schedule. If the agent can't read the Automation, paste that information into the session.

  3. Identify where the workflow reads data and saves its result. In this example, the workflow reads GitHub issues and pull requests, and the report appears in the Automation run's final response. The hosted skill needs a GitHub connection and a destination for the report, such as cloud storage.

Don't include unrelated chat history, tokens, or credential stores. The migration skill preserves the original Automation and source files.

Assess and convert the workflow

  1. In the coding-agent session, enter a migration request that names the skill and the source workflow. For this example, use:

    Use azure-functions-hosted-skills-migrate to migrate my GitHub Copilot
    Automation named "Weekly GitHub report" to Azure Functions hosted skills.
    Run the hosted skill every Monday at 9:00 AM UTC.
    

    You don't need to specify the project files or connector configuration. The migration skill reads the source and checks which operations can run in Azure. A general question about migration doesn't start the workflow.

  2. Answer the agent's questions about the schedule, report destination, and service account. Review any differences from the local workflow, including operations that aren't supported.

  3. Review the migration plan and approve the changes you want to make. The agent then creates the hosted skills project in a separate directory.

The generated project includes hosted skill definitions in .agent.md files, reusable skills, and Python tools where needed. It also includes mcp.json for the selected MCP servers and connector tools, and Bicep files for the required Azure resources. Unverified integrations remain unavailable until their required checks pass.

Deploy to Azure

When the agent generates the project, ask it to deploy the project.

  1. In the coding-agent session, enter:

    Use azure-functions-hosted-skills to deploy the migrated workflow to Azure.
    
  2. Confirm the Azure subscription, region, resources, and expected cost. Approve deployment when the settings match your requirements.

  3. Follow the connection setup instructions. Sign in to the external services and grant consent where required. For this example, confirm which GitHub account the connection uses and which repositories it can access.

Keep scheduled execution disabled until you finish testing. Deployment and connection setup don't automatically approve the schedule.

Test the migrated workflow

  1. Follow the agent's instructions to run a controlled test of the deployed workflow.

  2. Open the report in the selected destination. Check the reporting period, repositories, source links, and issue and pull request summaries against the source data.

  3. Review the tests for empty results, access errors, and service failures. Check that a failed data retrieval produces an error, not a report that incorrectly claims there's no activity.

  4. When the required checks pass, approve the hosted schedule. Disable the original Automation when you're ready to switch to the hosted report so that both workflows don't produce reports.

If a required check can't run, keep the schedule disabled and resolve the reported issue. To resume the migration, enter:

Resume azure-functions-hosted-skills-migrate for this workflow.

Service connections

The deployed app doesn't inherit your local sign-in. For a connector-based integration, the app needs permission to call the connector, and the connection needs authorization for the external account. A shared connection uses the account that authorized it, not the identity of each caller. Don't copy local user tokens into app settings.

The migration skill checks connector options first. For services other than GitHub, it can also use a remote HTTP MCP server or a Python API or SDK client if the deployed runtime supports the operation and authentication method.

GitHub access in this migration workflow uses GitHub Connector operations only. Direct GitHub API or SDK calls, personal access tokens, new GitHub App authentication, and customer GitHub MCP servers aren't supported alternatives.

For connection setup and permissions, see Use managed connectors in Azure Functions.

Migration limits

The migration skill doesn't convert workflows that require the hosted app to:

  • Clone or change Git repositories, create pull requests, or run build and deployment pipelines.
  • Create, delete, or change Azure resources or role assignments.
  • Run arbitrary shell commands, local executables, desktop automation, or local stdio MCP servers.
  • Use Work IQ CLI or direct Work IQ MCP access.

Some mail, Teams, and SharePoint operations can use connectors, but connectors don't replace Work IQ cross-service search or reasoning.

These limits apply to the migrated app, not to the coding agent that creates and deploys it. They don't prevent your local coding agent from deploying the app after you approve the deployment.

Clean up resources

If you no longer need the test deployment, enter the following prompt in the coding-agent session:

Show me the Azure resources created for this test deployment.

Review the list before approving removal. Keep any connections or storage that other apps still use, and keep your original source files.