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 generally aims for cross-platform parity, but there is a subtle Windows bias. In the environment variable setup section, Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. PowerShell and Windows command prompt commands are given with more detail (e.g., mentioning the need to restart the command prompt after setx), and PowerShell is called out specifically. There is also mention of Visual Studio as an alternative to the .NET CLI, which is a Windows-centric tool, though the CLI is recommended. No Linux-specific tools or patterns are discussed, and screenshots are only of the console, not OS-specific, but the overall flow assumes familiarity with Windows environments.
Recommendations:
- Alternate the order of environment variable instructions, sometimes listing Linux/macOS first to avoid reinforcing a Windows-first perspective.
- Provide equal detail for Linux/macOS instructions (e.g., mention if a new terminal session is needed for export to take effect).
- Explicitly mention cross-platform editors (e.g., VS Code) alongside Visual Studio.
- Add a note clarifying that all .NET CLI commands work identically on Linux/macOS and Windows.
- Where possible, include screenshots or terminal output from both Windows and Linux/macOS environments.
- Consider including troubleshooting tips for Linux/macOS users, such as shell differences or permission issues.
Create pull request
Flagged Code Snippets
setx Endpoint "<endpoint-of-your-app-configuration-store>"
$Env:Endpoint = "<endpoint-of-your-app-configuration-store>"
setx ConnectionString "<connection-string-of-your-app-configuration-store>"
$Env:ConnectionString = "<connection-string-of-your-app-configuration-store>"