Glenn Gailey

Thanks @balag0! @naomihall I'm going to include your commit with some other work I'm doing in this article in our private repo. You'll still get credit for the commit. Thanks...

Contents from this PR were merged in https://github.com/MicrosoftDocs/azure-docs-pr/pull/208417 #please-close

Hey @walterstypula, I'm trying to incorporate your commit into a more comprehensive fix. Could you please answer a couple of questions for me about why you are submitting this addition:...

Contents from this PR were merged in https://github.com/MicrosoftDocs/azure-docs-pr/pull/208417 #please-close

@nzthiago just to clarify, we are discussing the **"ConnectionStrings"** object in the local.settings.json (since **"Values"** just maps to so called application settings)? { "IsEncrypted": false, "Values": { "AzureWebJobsStorage": "", "AzureWebJobsDashboard":...

I have an update that attempts to address the ConnectionStrings issue in the private docs repo: https://github.com/MicrosoftDocs/azure-docs-pr/pull/43131

I worked with @nzthiago to try and tease out the nuance between **Application Settings** and **Connection Strings** in the [local.settings.json section](https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local#local-settings-file)—clearly, unsuccessfully. 😦 Another complicating factor is that we have...

We should also consider including the fix made to Timer trigger docs in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/198949

We are now documenting this metric [here](https://docs.microsoft.com/azure/azure-functions/analyze-telemetry-data#azure-monitor-metrics).

I would have to do some deep research to determine how we ended up with conflicting guidance. Since some of it is in best practices, maybe @FinVamp1 remembers?