Azure App Configuration
322
Total Pages
266
Linux-Friendly Pages
56
Pages with Bias
17.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
147 issues found
Showing 76-100 of 147 flagged pages
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-bicep.md
...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented in parallel tabs throughout. There are no Linux-specific instructions, nor is there mention of Linux shell patterns or tools. The use of PowerShell may implicitly favor Windows users, as it is less commonly used on Linux. The documentation does not explicitly state platform requirements or differences, and does not mention Linux or macOS environments.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), while PowerShell is most common on Windows.
- Add a note clarifying that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Consider listing Azure CLI examples first, as it is the most cross-platform tool.
- Include brief instructions or links for installing Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available on Linux/macOS, but is less commonly used for Azure tasks on those platforms.
- Add troubleshooting tips for Linux/macOS users if any steps differ.
Create Pull Request
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md
...p-configuration/quickstart-feature-flag-aspnet-core.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation implicitly assumes a Windows-centric development environment by referencing only the .NET CLI and Azure Portal, without addressing cross-platform shell differences or providing explicit Linux/macOS instructions. There are no examples or notes for Linux users regarding environment setup, shell commands, or alternative tools.
Recommendations
- Explicitly state that the .NET CLI commands work on Windows, Linux, and macOS, and provide any necessary prerequisites for Linux/macOS (e.g., installing .NET SDK).
- Include notes or callouts for Linux/macOS users, such as common shell differences, file path conventions, or troubleshooting tips.
- If any steps differ on Linux (e.g., file permissions, case sensitivity), document them.
- Mention that the Azure Portal is web-based and platform-agnostic, but also provide Azure CLI or Azure PowerShell alternatives for managing feature flags, with example commands for both Windows and Linux shells.
- Add a section or note confirming that the instructions are cross-platform, or link to platform-specific guides as appropriate.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-chat-completion-dotnet.md
...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Build and run the app' section, where instructions for setting environment variables are presented with Windows Command Prompt and PowerShell examples before the macOS/Linux equivalent. However, Linux/macOS instructions are present and accurate. There is no exclusive use of Windows tools or patterns, and no missing Linux examples.
Recommendations
- Present cross-platform instructions in parallel tables or grouped lists, rather than listing Windows first.
- For setting environment variables, consider using a tabbed interface (Windows CMD, PowerShell, Linux/macOS Bash) to give equal prominence.
- Explicitly confirm that all steps and code samples are cross-platform and tested on Linux/macOS.
- Add a note at the start of the 'Build and run the app' section stating that the guide works on Windows, Linux, and macOS.
- Where possible, provide troubleshooting tips for common Linux/macOS issues (e.g., environment variable persistence).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-deployment-overview.md
...re-app-configuration/quickstart-deployment-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal UI for configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts) for managing App Configuration resources. While the portal is cross-platform, the absence of CLI examples (which are especially important for Linux and automated deployments) and the lack of explicit Linux-oriented instructions or screenshots indicate a subtle Windows-first and GUI-first bias. There are no Linux-specific tools, shell commands, or automation examples provided.
Recommendations
- Add Azure CLI examples for all configuration steps (e.g., setting authentication mode, enabling private network access), as Azure CLI is cross-platform and widely used in Linux environments.
- Include Bash script snippets for common deployment tasks to demonstrate parity with PowerShell/Windows approaches.
- Where screenshots of the Azure portal are used, supplement them with equivalent CLI commands and outputs.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI documentation.
- If PowerShell is referenced in related articles, ensure Bash/Azure CLI equivalents are also present.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md
...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Windows-specific commands (setx, PowerShell syntax) are described in detail, while Linux/macOS instructions are present but appear after Windows examples. No Linux-specific tools or patterns are mentioned elsewhere, but parity is generally maintained in other sections.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in tabs, rather than listing Windows first.
- Include notes about differences in environment variable persistence between setx (Windows) and export (Linux/macOS).
- Explicitly mention that Linux/macOS users do not need to restart their terminal for environment variable changes to take effect.
- Where possible, use cross-platform commands (e.g., Maven, Java) before platform-specific instructions.
- Consider adding troubleshooting notes for Linux/macOS users, such as shell-specific environment variable behavior.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-javascript.md
...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Additionally, the prerequisites link for installing Node.js prioritizes Windows and WSL, with no direct mention of Linux-native installation methods. PowerShell and Windows command prompt commands are given more detailed instructions (e.g., restart requirement), while Linux/macOS instructions are more succinct.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Include links or guidance for installing Node.js natively on Linux distributions (e.g., apt, yum, snap) in the prerequisites.
- Provide equal detail for Linux/macOS commands (e.g., mention shell profile persistence for environment variables).
- Consider using tabs or side-by-side formatting for OS-specific instructions to avoid implicit prioritization.
- Review all examples and ensure parity in explanation and troubleshooting steps for Linux/macOS users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-python-provider.md
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. In the prerequisites, it links only to Windows-specific Python installation instructions. When setting environment variables, Windows command prompt and PowerShell instructions are consistently presented before Linux/macOS equivalents. Both Windows and Linux/macOS commands are provided, but Windows is prioritized in order and detail.
Recommendations
- Provide links to Python installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Alternate the order of environment variable instructions, or present all platforms in parallel (e.g., in a table or tabbed format) to avoid prioritizing Windows.
- Ensure that Linux/macOS instructions are as detailed as Windows instructions (e.g., mention shell session persistence if relevant).
- Consider adding a short note affirming cross-platform support and parity to reassure non-Windows users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on ASP.NET Core applications, which are commonly developed on Windows, and does not provide any Linux-specific instructions, examples, or considerations. All code examples and prerequisites assume a Windows-centric development environment (e.g., Visual Studio, C#), and there are no mentions of Linux tools, shell commands, or cross-platform development patterns. The Azure Portal UI instructions are platform-agnostic, but the lack of Linux parity in code and tooling is evident.
Recommendations
- Add explicit instructions or notes for developers working on Linux, such as using VS Code, JetBrains Rider, or command-line .NET SDK tools.
- Provide shell (bash) commands for common tasks (e.g., using the Azure CLI to manage Key Vault and App Configuration) alongside or in place of portal instructions.
- Clarify that the .NET Core SDK and Azure App Configuration libraries are cross-platform, and provide guidance for running and testing the sample code on Linux.
- Include troubleshooting tips or links for Linux users, especially around authentication (e.g., DefaultAzureCredential behavior on Linux).
- Ensure that future examples and tutorials include parity for both Windows and Linux development environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/secure-azure-app-configuration.md
...re-app-configuration/secure-azure-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any OS-specific examples, commands, or scripts. However, where code or integration examples are referenced, they are exclusively for ASP.NET Core (a .NET/Windows-centric framework), and there are no equivalent examples or references for Linux-first or cross-platform frameworks (e.g., Java, Python, Node.js). There are no mentions of Linux command-line tools, shell scripts, or deployment patterns, and the only explicit code integration references are for .NET/ASP.NET, which is most commonly associated with Windows environments.
Recommendations
- Add code and integration examples for popular Linux-first or cross-platform frameworks (e.g., Python, Java, Node.js) alongside or in place of ASP.NET Core examples.
- Include references to Linux command-line tools and shell scripting for tasks such as key rotation, monitoring, or deployment, where appropriate.
- When referencing tutorials (such as Key Vault integration), provide links or guidance for non-.NET platforms and frameworks.
- Explicitly mention that all features and guidance apply equally to Linux-based deployments, and provide examples or notes for Linux users where there may be differences.
- Consider adding a section or callout for cross-platform best practices, ensuring parity for both Windows and Linux environments.
Azure App Configuration
How to use Agent Framework in a Python app with Azure App Configuration
...zure-app-configuration/howto-ai-agent-config-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (Command Prompt and PowerShell) before mentioning the equivalent macOS/Linux command. The only other Windows-specific reference is a link to Python setup documentation for Windows, but this is contextually appropriate given the section's focus.
Recommendations
- Present environment variable setup instructions for all platforms in parallel (e.g., in a table or side-by-side code blocks), or rotate the order so that Linux/macOS is not always last.
- Optionally, provide a link to Python installation instructions for Linux/macOS alongside the Windows link, or clarify that users should refer to their OS-specific Python installation guides.
Azure App Configuration
How to use Agent Framework in a Python app with Azure App Configuration
...zure-app-configuration/howto-ai-agent-config-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. The only other minor Windows bias is a link to Python setup instructions specifically for Windows in the prerequisites.
Recommendations
- Present environment variable instructions for all platforms together, or list macOS/Linux first to avoid implicit prioritization of Windows.
- In the prerequisites, provide links for setting up Python on all major platforms (Windows, macOS, Linux), or link to the official Python download page which covers all OSes.
- Consider using a tabbed or side-by-side format for platform-specific commands to improve parity and clarity.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing .NET/.NET Framework libraries and samples first, which are traditionally associated with Windows development. The sample links for .NET libraries point to examples named 'DotNetCore' and 'DotNetFramework/WebDemo', which are often Windows-centric. There is no explicit mention of Linux/macOS compatibility for these libraries, nor are there platform-specific usage notes or parity assurances. However, the page does include libraries and samples for Java, Python, JavaScript, and Go, which are cross-platform.
Recommendations
- Explicitly state platform compatibility for each library, especially for .NET and .NET Framework, clarifying Linux/macOS support.
- Include Linux/macOS-specific sample links or usage notes for .NET libraries if supported.
- Balance the order of presentation by alternating or grouping cross-platform libraries together, rather than listing Windows-centric ones first.
- Add a section or note on cross-platform development considerations, especially for .NET users deploying on Linux.
- Ensure that all sample repositories include Linux/macOS instructions where applicable.
Azure App Configuration
Roll out features to targeted audiences in a Python app
...re-app-configuration/how-to-targeting-filter-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent, but otherwise offers parity in examples and instructions for all platforms.
Recommendations
- Present Linux/macOS commands before or alongside Windows commands to avoid implicit prioritization.
- Consider grouping platform-specific instructions in a table or clearly labeled sections for equal visibility.
- Add a note clarifying that all platforms are supported and that the order of instructions does not imply preference.
Azure App Configuration
Quickstart for using chat completion configuration in a Go app
...ure-app-configuration/quickstart-chat-completion-go.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), indicating a 'windows_first' bias. All other code and instructions are cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions to avoid implying Windows is the default platform.
- Explicitly state that all steps are cross-platform unless otherwise noted.
- Where possible, group environment variable instructions together and clarify which applies to each OS.
Azure App Configuration
Create an Azure App Configuration store using Bicep
...n/articles/azure-app-configuration/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and examples are always shown together. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor any guidance for Bash or shell scripting, which are common on Linux/macOS. The ordering of examples does not favor Windows, but the inclusion of PowerShell throughout may suggest a slight Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add notes clarifying that Azure PowerShell is available on Linux/macOS, or recommend CLI for those platforms.
- Consider showing CLI examples first, as CLI is the default on Linux/macOS.
- Include brief instructions for running commands in Bash or other common Linux shells, if relevant.
- Add a section or note on platform compatibility for the tools used.
Azure App Configuration
Quickstart for using Azure App Configuration with Go applications
...s/azure-app-configuration/quickstart-go-console-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and complete, and the main Go code is cross-platform.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
- Use tabbed or parallel formatting for environment variable setup commands, so all platforms are equally visible.
- Consider mentioning that Go code and Azure CLI commands are cross-platform, reinforcing parity.
- Reduce emphasis on Windows-specific tools (e.g., setx, PowerShell) unless necessary for a Windows-only feature.
Azure App Configuration
Quickstart for using chat completion configuration in a .NET app
...app-configuration/quickstart-chat-completion-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS (bash). The Windows instructions are more detailed, including a note to restart the command prompt for setx, while Linux/macOS instructions are brief and lack such guidance. There is a slight ordering bias favoring Windows users, but Linux/macOS instructions are present and functional.
Recommendations
- Present environment variable setup instructions for all platforms in parallel, or start with a neutral cross-platform example (e.g., using .NET's cross-platform environment variable APIs).
- Add notes for Linux/macOS users regarding shell session persistence (e.g., using ~/.bashrc or export for current session).
- Ensure parity in detail for Linux/macOS instructions, such as mentioning session persistence and when changes take effect.
- Consider using tabbed or side-by-side code blocks for platform-specific instructions to avoid implicit prioritization.
Azure App Configuration
Quickstart for using Azure App Configuration with JavaScript apps
...re-app-configuration/quickstart-javascript-provider.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before showing the Linux/macOS equivalent, and references Windows installation methods for Node.js before mentioning WSL. However, all code samples and CLI instructions are cross-platform and do not rely on Windows-only tools.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions for setting environment variables.
- Provide a more balanced introduction to Node.js installation, mentioning Linux/macOS methods equally or first.
- Consider grouping platform-specific instructions in a tabbed or parallel format to avoid implicit prioritization.
Azure App Configuration
Quickstart for adding feature flags to Python with Azure App Configuration
...re-app-configuration/quickstart-feature-flag-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions with Windows Command Prompt and PowerShell examples before macOS and Linux equivalents. However, all platforms are covered with explicit instructions and code samples are platform-agnostic.
Recommendations
- Present environment variable setup instructions in a neutral order (e.g., Linux/macOS first, or alphabetical) to avoid implicit prioritization of Windows.
- Consider grouping Windows, macOS, and Linux instructions in a single table or section to emphasize parity.
- Add explicit notes that all code samples work identically across platforms, unless there are platform-specific caveats.
- Provide links to Python installation guides for Linux/macOS alongside the Windows link in prerequisites.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows/.NET bias by listing .NET-based providers and samples first, with the majority of initial examples referencing .NET Standard, ASP.NET Core, and .NET Framework. The sample links for .NET Framework point to a 'WebDemo', which is typically Windows-centric. There is no explicit mention of Linux or cross-platform usage in the .NET samples, nor are there examples or guidance for Linux-specific scenarios (e.g., running .NET providers on Linux, using Mono, or .NET Core on Linux). Other languages (Java, Python, JavaScript, Go) are included, but their placement is after the .NET entries, and none of the samples or documentation sections explicitly address Linux or macOS environments.
Recommendations
- Add explicit Linux/macOS usage notes for .NET providers, clarifying cross-platform compatibility and any platform-specific considerations.
- Provide Linux/macOS sample projects or scripts for .NET, especially for .NET Core/Standard, demonstrating usage on non-Windows platforms.
- Reorder the provider table to avoid implicit prioritization of Windows/.NET; consider alphabetical or feature-based ordering.
- Include a section or FAQ addressing platform support and parity, highlighting any differences or limitations for Linux/macOS users.
- Ensure that all sample links and documentation reference cross-platform usage where applicable, not only Windows-centric scenarios.
Azure App Configuration
Tutorial: Use Dynamic Configuration Using Push Refresh in a .NET App
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt, PowerShell, macOS, and Linux. However, Windows instructions are consistently presented first in each section, with screenshots and output examples shown in Windows Command Prompt. No critical functionality is missing for Linux/macOS users, but the ordering and visual emphasis favor Windows.
Recommendations
- Alternate the order in which platform instructions are presented, or present all platforms equally (e.g., side-by-side tabs).
- Include screenshots or output examples from Linux/macOS terminals as well as Windows.
- Explicitly state that all steps and code are cross-platform, and highlight any platform-specific caveats if they exist.
- Consider using generic shell commands (e.g., 'export') first, or group Windows instructions after Linux/macOS if usage statistics support it.
Azure App Configuration
Tutorial for using Azure App Configuration dynamic configuration in an Azure Functions app
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Visual Studio and Windows-specific tooling for local testing. However, Linux/macOS instructions are present and complete, so the bias is mostly in ordering and emphasis.
Recommendations
- Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or equal prominence), rather than listing Windows first.
- Include explicit instructions for running and debugging Azure Functions locally on Linux/macOS (e.g., using VS Code or Azure Functions Core Tools CLI), not just Visual Studio.
- Mention cross-platform tools and workflows, and clarify any platform-specific requirements or limitations.
- Avoid language that assumes Windows as the default environment (e.g., 'If you use Windows...'), instead use neutral phrasing ('On Windows...', 'On Linux/macOS...').
Azure App Configuration
Tutorial: Use dynamic configuration in a .NET background service
...enable-dynamic-configuration-dotnet-background-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Windows-specific tools (cmd, PowerShell) are mentioned first in each section, with Linux/macOS instructions following. All other code and CLI examples are cross-platform, and the .NET CLI is explicitly described as available on all platforms.
Recommendations
- Present environment variable setup instructions for Linux/macOS and Windows side-by-side, or alternate which platform is shown first.
- Explicitly state that all .NET CLI commands work on Linux/macOS and Windows.
- Consider grouping OS-specific instructions in tabs or collapsible sections to avoid implicit prioritization.
- Add a note at the beginning clarifying that all steps are applicable to Linux, macOS, and Windows unless otherwise stated.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and uses Windows-specific tools (setx) and command syntax. However, Linux/macOS instructions are present and complete. The curl example is shown in Windows command prompt format, but is equally applicable to Linux/macOS. No critical steps are Windows-only, and Linux users can follow all instructions.
Recommendations
- Present environment variable instructions for Linux/macOS before or alongside Windows examples, rather than after.
- Use neutral formatting for command examples (e.g., show curl in bash format, or clarify that it works on all platforms).
- Mention Linux/macOS equivalents for any Windows-specific tools (e.g., setx) and clarify restart requirements.
- Explicitly state that all steps can be performed on Linux/macOS, and highlight any platform-specific caveats if present.
Azure App Configuration
Tutorial: Use dynamic configuration in a .NET app
...figuration/enable-dynamic-configuration-dotnet-core.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents environment variable setup instructions with Windows Command Prompt and PowerShell examples before the Linux/macOS equivalent. It specifically calls out the Command Prompt and PowerShell in the refresh step, and screenshots show Windows terminals. While Linux/macOS instructions are present, Windows tooling and patterns are prioritized and referenced first.
Recommendations
- Present environment variable setup instructions for Linux/macOS before or alongside Windows examples, rather than after.
- Use neutral language when referring to terminal windows (e.g., 'terminal window' instead of 'Command Prompt or PowerShell window').
- Include screenshots of the app running in Linux/macOS terminals, or use generic terminal screenshots.
- Explicitly state that all steps are cross-platform and work on Linux/macOS as well as Windows.
- Ensure parity in troubleshooting and logging instructions, mentioning any platform-specific caveats if present.