You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
False-positive AzureWebJobsStorage warning with URI-based managed identity configuration #407
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.
Activity
silkfire commentedon Oct 28, 2026
I hit the same warning on a Flex Consumption app with a system-assigned identity and
AzureWebJobsStorage__blobServiceUri/__queueServiceUri/__tableServiceUriconfigured.Cause:
resourceValidator.tsonly checksAzureWebJobsStorageandAzureWebJobsStorage__accountName, in bothgetFunctionappSettingsRbacandgetFunctionappSettingsScm. On Flex the settings are never read (deploy goes through Kuduapi/publish), so the warning is cosmetic there. On the run-from-package path it is a real bug, though:websiteRunFromPackageDeploy.tsbuildshttps://${AzureWebJobsStorage__accountName}.blob.core.windows.net, which becomeshttps://undefined.blob.core.windows.netwhen 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 usesAzureWebJobsStorage__blobServiceUriwhen present (falling back to__accountName), with a clear error if neither is set.