This post was most recently updated on September 19th, 2021.

2 min read.

Another day, another issue with Azure Functions! For such a 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”?

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:

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.
Close and reopen your Visual Studio instance
Just in case. It’s easy, it’s quick, and it has helped me once or twice!
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. 😊
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!

Antti K. Koskela

Developer / Speaker / Consultant at Koskila / Etteplan Oyj / Norppandalotti Software Co / Alter - Experience Ideas Ltd.

Antti Koskela is a proud digital native nomadic millennial full stack developer (is that enough funny buzzwords? That's definitely enough funny buzzwords!), who works as a Cloud Solutions Architect for Etteplan Oyj, an engineering company that employs something like 700 devs building and fixing anything even half-digital.

He's been a developer from 2004 (starting with PHP and Java), and he's been working on .NET projects, Azure, Office 365, SharePoint and a lot of other stuff. He's also Microsoft MVP for Office Development.

This is his personal professional (e.g. professional, but definitely personal) blog.

Latest posts by Antti K. Koskela (see all)

System.Text.Json.JsonPropertyName not working for CosmosDb in .NET Core/5? - October 19, 2021
Errors loading an assembly that’s using Microsoft Graph API - October 12, 2021
ILogger binding suddely failing for Azure Functions – what to do? - October 5, 2021

4.4 7 votes

Article Rating

#SharePointProblems

Solutions are worthless unless shared! Antti K. Koskela's Personal Professional Blog

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

Problem

Solution

References

Posts Related to "How to fix "Missing value for AzureWebJobsStorage in local.settings.json" when you're debugging Azure Functions locally?":