Azure-docs: Description of AZURE_FUNCTIONS_ENVIRONMENT is inaccurate

[MisinformedDNA]

The description says

> When AZURE_FUNCTIONS_ENVIRONMENT isn't set, it defaults to Production.

This may be true in Azure, but it is not true for development in VS. It defaults to "Development".

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 18aa54fd-3aa1-37c5-925c-51a0195b1030
• Version Independent ID: 60198016-1ea9-e7ae-b00b-2c665d5ad8ca
• Content: App settings reference for Azure Functions
• Content Source: articles/azure-functions/functions-app-settings.md
• Service: azure-functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[mike-urnun-msft]

Hi @MisinformedDNA - Thank you for your feedback! We will review and update as appropriate.

[mike-urnun-msft]

Hi @MisinformedDNA - We're making an update to the statement to read as follows:

When AZURE_FUNCTIONS_ENVIRONMENT isn't set, it defaults to Development on a local environment and Production on Azure.

[mike-urnun-msft]

@MisinformedDNA We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[MisinformedDNA]

I just created a new Function app in VS and if I add the variable to local.settings.json

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
    "FUNCTIONS_WORKER_RUNTIME": "dotnet",
    "AZURE_FUNCTIONS_ENVIRONMENT": "Staging"
  }
}

And run locally, then I get the error

Azure Functions Core Tools (2.7.1434 Commit hash: eac7c2888f315da0f2b51831b47f134330b501fd)
Function Runtime Version: 2.0.12555.0
An item with the same key has already been added. Key: AZURE_FUNCTIONS_ENVIRONMENT

How do I set AZURE_FUNCTIONS_ENVIRONMENT when testing in VS?

[mslot]

I just created a new Function app in VS and if I add the variable to local.settings.json

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
    "FUNCTIONS_WORKER_RUNTIME": "dotnet",
    "AZURE_FUNCTIONS_ENVIRONMENT": "Staging"
  }
}

And run locally, then I get the error

Azure Functions Core Tools (2.7.1434 Commit hash: eac7c2888f315da0f2b51831b47f134330b501fd)
Function Runtime Version: 2.0.12555.0
An item with the same key has already been added. Key: AZURE_FUNCTIONS_ENVIRONMENT

How do I set AZURE_FUNCTIONS_ENVIRONMENT when testing in VS?

I also experience this. Both on .net core 2.1 and .net core 3.0:

Azure Functions Core Tools (2.7.1846 Commit hash: 458c671341fda1c52bd46e1aa8943cb26e467830)
Function Runtime Version: 2.0.12858.0
An item with the same key has already been added. Key: AZURE_FUNCTIONS_ENVIRONMENT

I can still set ASPNETCORE_ENVIRONMENT on local development machine, and it reflects the given environment when starting up the Azure Functions runtime. I don't know if this reflects in same way in Azure, can someone confirm this? Can I set the ASPNETCORE_ENVIRONMENT in Azure and expect the hosting to be resolved properly, or do I need to make some code to automatically not add the AZURE_FUNCTIONS_ENVIRONMENT when on local development?