Skip to content

False-positive AzureWebJobsStorage warning with URI-based managed identity configuration #407

Open

Description

Azure/functions-action v1.5.7 emits:
"Neither AzureWebJobsStorage nor AzureWebJobsStorage__accountName exist..."

when host storage uses URI-based managed identity configuration.

The action does not recognize these settings:

  • AzureWebJobsStorage__blobServiceUri
  • AzureWebJobsStorage__queueServiceUri
  • AzureWebJobsStorage__credential
  • AzureWebJobsStorage__clientId

Creating anxiety when deploying

Activity

  1. silkfire commented on Oct 28, 2026

    @silkfire

    I hit the same warning on a Flex Consumption app with a system-assigned identity and AzureWebJobsStorage__blobServiceUri / __queueServiceUri / __tableServiceUri configured.

    Cause: resourceValidator.ts only checks AzureWebJobsStorage and AzureWebJobsStorage__accountName, in both getFunctionappSettingsRbac and getFunctionappSettingsScm. On Flex the settings are never read (deploy goes through Kudu api/publish), so the warning is cosmetic there. On the run-from-package path it is a real bug, though: websiteRunFromPackageDeploy.ts builds https://${AzureWebJobsStorage__accountName}.blob.core.windows.net, which becomes https://undefined.blob.core.windows.net when only the URI-based settings exist.

    I opened #408 with a fix: any non-empty AzureWebJobsStorage__* setting now counts as configured host storage, and the publisher uses AzureWebJobsStorage__blobServiceUri when present (falling back to __accountName), with a clear error if neither is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions