How can I verify the currently mounted Azure Functions Flex Consumption package?

Question

How can I verify the currently mounted Azure Functions Flex Consumption package?

Tim McConnehey 0

For an Azure Functions Flex Consumption app using package deployment, what supported read-only method can confirm the package currently mounted by the running app when Deployment Center has no release rows and the Flex Consumption Deployment diagnostic only shows recent activity? Can the exact active deployment ID be associated with an immutable package digest or storage version using existing read access, with public and deployment-management ingress left closed?

Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-11-11T01:58:06.0933333+00:00
Hi Tim McConnehey,

Thanks for explaining your requirements.

Azure Functions Flex Consumption uses package deployment, where the application runs directly from a ZIP package stored in Azure Blob Storage.

You can perform the following checks using read-only access:

Identify the deployment storage

Retrieve the Function App resource using Azure Resource Manager.

Check properties.functionAppConfig.deployment.storage to identify the configured storage account and container.

Inspect the stored package

Use Storage Blob Data Reader permissions to inspect released-package.zip.

Check its ETag, Last-Modified timestamp and Blob version ID, if versioning is enabled.

You can also download the package and calculate its SHA-256 hash to identify its contents.

Check deployment diagnostics

The Flex Consumption Deployment diagnostic provides deployment history, package status and troubleshooting information.

However, this information does not conclusively identify the exact package currently mounted by an existing running worker.

These checks do not require opening the Function App's public or SCM endpoints, provided the storage account is accessible from your inspection environment.

Regarding your main question: Microsoft does not currently document a supported read-only API that conclusively links an active deployment ID to the exact package mounted by a running worker and its immutable digest or Blob version.

For future deployments, you can include a build ID or Git commit SHA in the package and log it during application startup. This helps identify the running build without opening inbound endpoints.

References:

Azure Functions Flex Consumption plan

Create and manage Flex Consumption apps

Deployment technologies in Azure Functions

Automate resource deployment for Azure Functions

Your answer

Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-11-11T01:58:06.0933333+00:00

Hi Tim McConnehey,

Thanks for explaining your requirements.

Azure Functions Flex Consumption uses package deployment, where the application runs directly from a ZIP package stored in Azure Blob Storage.

You can perform the following checks using read-only access:

Identify the deployment storage

Retrieve the Function App resource using Azure Resource Manager.

Check properties.functionAppConfig.deployment.storage to identify the configured storage account and container.

Inspect the stored package

Use Storage Blob Data Reader permissions to inspect released-package.zip.

Check its ETag, Last-Modified timestamp and Blob version ID, if versioning is enabled.

You can also download the package and calculate its SHA-256 hash to identify its contents.

Check deployment diagnostics

The Flex Consumption Deployment diagnostic provides deployment history, package status and troubleshooting information.

However, this information does not conclusively identify the exact package currently mounted by an existing running worker.

These checks do not require opening the Function App's public or SCM endpoints, provided the storage account is accessible from your inspection environment.

Regarding your main question: Microsoft does not currently document a supported read-only API that conclusively links an active deployment ID to the exact package mounted by a running worker and its immutable digest or Blob version.

For future deployments, you can include a build ID or Git commit SHA in the package and log it during application startup. This helps identify the running build without opening inbound endpoints.

References:

Azure Functions Flex Consumption plan

Create and manage Flex Consumption apps

Deployment technologies in Azure Functions

Automate resource deployment for Azure Functions