Azure Functions CLI - such a pretty logo for such an awesome functionality

How to fix “Missing value for AzureWebJobsStorage in local.settings.json” when you’re debugging Azure Functions locally?

This post was most recently updated on July 15th, 2021.

2 min read.

Another day, another issue with Azure Functions! For such simple and powerful tool, it sure does produce a lot of topics for blog articles! 😁

So let’s get down to fixing another Azure Functions configuration issue. But wait – what WAS the problem again?

Problem

Table of Contents

When firing up your Azure Functions project locally, this error is what you’re confronted with:

"Missing value for AzureWebJobsStorage in local.settings.json. This is required for all triggers other than httptrigger, kafkatrigger. You can run 'func azure functionapp fetch-app-settings ' or specify a connection string in local.settings.json."

But… You might actually have that property in the file – what’s the error about, then? Let’s take a look!

Solution

The solution might be one of the following – I’m starting from the most obvious and simple one, which is likely where you should start as well.

Time needed: 10 minutes.

How to fix “Missing value for AzureWebJobsStorage in local.settings.json”?

  1. Add “AzureWebJobsStorage” value to your local.settings.json file

    Obviously, you could be missing this app setting completely – maybe by adding it somewhat like this:
    This image has an empty alt attribute; its file name is image-10.png

    And in copy-pasteable form – this is what you should add to local.settings.json -file’s “Values”-node:

    "AzureWebJobsStorage": "UseDevelopmentStorage=true"

    Simple as that! Except if it doesn’t work, try the other options below.

  2. Close and reopen your Visual Studio instance

    Just in case. It’s easy, it’s quick, and it has helped me once or twice!

  3. No nested values in local.settings.json

    Valid JSON can have values nested infinitely deep. Your local.settings.json file does not support that (beyond predefined “sections”, such as “Values” (for appsettings) or “ConnectionStrings”, however!

    Verify you’re not trying anything too fancy there.

    What’s a bit confusing, however, is that appsettings.json file DOES support nested configuration values. So no consistency here. 😊

  4. Make sure your local.settings.json file is getting deployed (copied) to the output folder

    Modify your .csproj file to have this:

    <None Update="local.settings.json">
    <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
    </None>


    This applies at least to .NET with Visual Studio, but YMMV. 😌

And at this point, you should be good!

References

mm
4.4 7 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments