Azure Functions Flex Consumption — OneDeploy succeeds, but deployment detector reports FailedA

Jorge Alexanders Morales 0 Reputation points
2026-11-18T16:55:09.4433333+00:00

Hello,

I'm testing a deployment and recovery workflow for an Azure Functions application running on Flex Consumption (Linux, Python 3.11).

Two deployments using ARM OneDeploy returned Succeeded.

The deployment logs confirmed the following steps completed successfully:

  • Package download

Package validation

Package upload to deployment storage

Pipeline completed for FDM deployment

However, the Azure Portal's Flex Consumption Deployment diagnostic reports:

Code deployment: Detected

Function app updates summary: Failed

Site update / config change: Not detected

The application was stopped after the deployment test.

I would appreciate clarification on the following:

Does a successful ARM OneDeploy operation guarantee that the uploaded package becomes the effective runtime package?

What is the officially supported method to identify the package selected for execution by a Flex Consumption Function App?

Can the diagnostic report Failed or Site update not detected when the deployment pipeline succeeds but there are no active instances?

After a successful deployment, is the original source package still required, or can temporary source artifacts and access permissions be safely removed?

What is the recommended way to verify successful activation and rollback without relying exclusively on ARM provisioning status?

I'm looking for the supported deployment verification procedure, rather than troubleshooting a specific resource.Hello,

I'm testing a deployment and recovery workflow for an Azure Functions application running on Flex Consumption (Linux, Python 3.11).

Two deployments using ARM OneDeploy returned Succeeded.

The deployment logs confirmed the following steps completed successfully:

Package download

Package validation

Package upload to deployment storage

Pipeline completed for FDM deployment

However, the Azure Portal's Flex Consumption Deployment diagnostic reports:

Code deployment: Detected

Function app updates summary: Failed

Site update / config change: Not detected

The application was stopped after the deployment test.

I would appreciate clarification on the following:

Does a successful ARM OneDeploy operation guarantee that the uploaded package becomes the effective runtime package?

What is the officially supported method to identify the package selected for execution by a Flex Consumption Function App?

Can the diagnostic report Failed or Site update not detected when the deployment pipeline succeeds but there are no active instances?

After a successful deployment, is the original source package still required, or can temporary source artifacts and access permissions be safely removed?

What is the recommended way to verify successful activation and rollback without relying exclusively on ARM provisioning status?

I'm looking for the supported deployment verification procedure, rather than troubleshooting a specific resource.

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-18T16:56:40.63+00:00

    A successful OneDeploy operation confirms that the package was processed and stored, but runtime activation should be verified by starting the app and executing a health check or representative trigger while reviewing Application Insights telemetry.

    What OneDeploy Succeeded establishes

    For Flex Consumption code deployments, OneDeploy processes the submitted package and stores the ready-to-run ZIP in the configured deployment container. The function app subsequently runs directly from that package. Uploading a ZIP directly to the container is not equivalent to deploying it.^1^

    Therefore, Succeeded plus Pipeline completed for FDM deployment establishes successful package ingestion and publication to deployment storage. It does not, by itself, demonstrate that:

    • an instance started successfully;
    • the Functions host loaded the package;
    • Python imports and dependencies loaded;
    • triggers were indexed;
    • an invocation completed successfully.

    Those require runtime validation.

    Identifying the effective package

    The supported operator-facing surface is:

    1. Function App → Diagnose and solve problems.
    2. Search for Flex Consumption Deployment.
    3. Review deployment history, package status, and the associated deployment details.^2^
    4. Correlate the deployment ID with Application Insights deployment traces:
    traces
    | extend deploymentId = tostring(customDimensions.deploymentId)
    | where deploymentId != ""
    | project timestamp, deploymentId, message,
              severityLevel, customDimensions, appName
    | order by timestamp desc
    

    This is Microsoft’s documented query for Flex Consumption code-deployment logs.^3^

    The published documentation does not define a supported runtime API or app setting that returns an immutable package hash or exact blob name currently mounted by a particular instance. For deterministic release identification, include a commit SHA or release ID in the package and expose it through a health/version endpoint or telemetry. That application-level identifier should be treated as the runtime proof of which build executed.

    Meaning of the diagnostic result while stopped

    Microsoft documents that a site update occurs for code or configuration changes and that rollout behavior operates on running instances. It also states that there is no built-in completion signal for site updates; instance logs can only provide a best-effort estimate.^4^

    The documentation does not define Function app updates summary: Failed or Site update / config change: Not detected as authoritative evidence that a successfully processed package was rejected. It also does not explicitly guarantee that these exact detector results are expected when the app is stopped or has zero instances. In that state, there is no runtime activation to observe, so do not use this detector result alone as either success or failure.

    Start the app and perform runtime validation before interpreting the deployment as activated.

    Which artifacts and permissions must remain

    Two artifacts have different lifetimes:

    • Original package source referenced by packageUri: after OneDeploy has successfully downloaded, processed, and copied it, the runtime executes the processed package from the deployment container—not directly from the original source URL.^5^
    • Processed package in the configured deployment container: this is runtime content and must remain available. Flex Consumption stores and runs the current package there.^1^

    Consequently, temporary source URLs, SAS tokens, or staging blobs can be retired after confirmed deployment provided they are not the configured deployment container or credentials used by the app. Do not delete the processed package, deployment container, storage account, or remove the function app identity’s required access. The app retrieves the package on startup, including after scaling from zero.^2^

    1. Deploy and require OneDeploy to finish successfully.
    2. Query deployment telemetry by deploymentId; fail the pipeline on validation, storage, or build errors.
    3. Start the app if the workflow stopped it.
    4. Invoke a dedicated health/version HTTP endpoint, or submit a controlled event to a representative non-HTTP trigger.
    5. Verify:
      • the expected release ID is returned or logged;
      • the invocation succeeds;
      • Application Insights has no startup, import, indexing, or dependency exceptions.
    6. Only then mark the release active and remove temporary source access.
    7. Retain the commit SHA, dependency lock file, configuration, and successful pipeline run.

    Flex Consumption has no deployment slots or built-in package revision history. Each code-package deployment overwrites the current package. Rollback is another deployment of the previous state—not a platform-side package selection operation.^6^

    For rollback:

    1. Re-run the previous successful GitHub Actions or Azure Pipelines run.
    2. Ensure it checks out the original commit SHA and restores both code and versioned settings.
    3. Repeat the same health/version invocation and telemetry checks.
    4. For higher assurance, validate releases in a separate Flex Consumption app because deployment slots are unavailable.^6^

    References

    1. Deployment technologies in Azure Functions (flex-consumption-plan)
    2. Azure Functions Flex Consumption plan hosting
    3. Analyze Azure Functions telemetry in Application Insights
    4. Site update strategies in Flex Consumption
    5. Package-based deployment for Azure Functions | Microsoft Learn
    6. Recover from a bad Flex Consumption plan app deployment
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.