About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation demonstrates a Windows-first bias, particularly in the prerequisites and local testing sections. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and instructions for setting environment variables list Windows Command Prompt and PowerShell before Linux/macOS equivalents. The workflow assumes Visual Studio usage and references Windows-specific tools and patterns, with Linux parity only addressed as an afterthought.
Recommendations:
- Add explicit instructions and examples for developing and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Present environment variable setting commands for Linux/macOS before or alongside Windows commands, rather than after.
- Include guidance for using .NET CLI and editors available on all platforms, not just Visual Studio.
- Clarify that the quickstart is applicable to all platforms and provide parity in screenshots and workflow steps for Linux/macOS users.
- Mention and link to documentation for developing Azure Functions on Linux/macOS environments.
Create pull request
Flagged Code Snippets
$Env:AZURE_APPCONFIG_CONNECTION_STRING = "<connection-string-of-your-app-configuration-store>"
setx AZURE_APPCONFIG_ENDPOINT "<endpoint-of-your-app-configuration-store>"
$Env:AZURE_APPCONFIG_CONNECTION_STRING = "<connection-string-of-your-app-configuration-store>"
setx AZURE_APPCONFIG_ENDPOINT "<endpoint-of-your-app-configuration-store>"
$Env:AZURE_APPCONFIG_ENDPOINT = "<endpoint-of-your-app-configuration-store>"