GitHub action `Azure/functions-action` down

The deployment action for Azure Functions remains Azure/functions-action. The official guidance continues to use this action for GitHub Actions–based continuous delivery to an existing function app or deployment slot.

Key points from the current guidance:

• Azure/functions-action is the documented action used to publish code from GitHub to Azure Functions.
• It is used in all the language- and OS-specific workflow templates generated from:
  • Azure portal Deployment Center
  • Azure CLI (az functionapp deployment github-actions)
  • GitHub repository templates
• The action supports multiple hosting plans (Consumption, Elastic Premium, App Service, Flex Consumption) via parameters such as:
  • app-name (required)
  • package (required; defaults to .)
  • sku and remote-build for Flex Consumption when using a publish profile.

There is no alternative deployment action documented in the provided material; the recommended approach is still to use Azure/functions-action in the GitHub Actions workflow YAML stored under /.github/workflows/.

If the repository or action appears disabled in GitHub at a given moment, the supported path in the documentation is still to:

1. Use the existing Azure/functions-action in the workflow.
2. (If needed) Regenerate or update the workflow from the Azure portal or Azure CLI so it uses the current templates and parameters.

References:

• Continuous delivery by using GitHub Actions (method-cli)
• Continuous delivery by using GitHub Actions (method-manual)
• Continuous delivery by using GitHub Actions (method-template)
• Continuous delivery by using GitHub Actions (method-portal)
• Continuous delivery by using GitHub Actions (method-portal) – Update a workflow configuration
• Continuous delivery by using GitHub Actions (method-manual) – Update a workflow configuration
• az functionapp deployment github-actions remove