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 126-147 of 147 flagged pages
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 Linux/macOS, but otherwise offers parity in examples and instructions for all platforms.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group all platform instructions together without prioritizing one.
- Consider explicitly mentioning that all code and steps work identically on Linux/macOS unless otherwise noted.
- Add a note clarifying that the Python/Flask app is cross-platform and does not require Windows-specific tools.
Create Pull Request
Azure App Configuration
Enable telemetry for feature flags in a Node.js application
.../azure-app-configuration/howto-telemetry-javascript.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. All other code and instructions are platform-neutral and do not show a Windows bias.
Recommendations
- Present environment variable setup instructions for Linux/macOS first, or group all platform instructions together without prioritizing Windows.
- Explicitly state that the instructions apply equally to all platforms unless otherwise noted.
- Consider using cross-platform tools or commands (e.g., cross-env for Node.js) in examples where possible.
Azure App Configuration
Use variant feature flags in a Python application
...pp-configuration/howto-variant-feature-flags-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias, primarily in the order and detail of environment setup instructions. The Python installation prerequisite links only to Windows documentation, and the virtual environment activation example uses Windows syntax ('.\venv\Scripts\Activate') without providing the Linux/macOS equivalent ('source venv/bin/activate'). In the environment variable setup section, Windows command prompt and PowerShell instructions are given before the Linux/macOS example. However, Linux/macOS instructions are present for environment variables and package installation, and the rest of the tutorial is platform-neutral.
Recommendations
- Provide a link to Python installation instructions for Linux/macOS alongside the Windows link in prerequisites.
- Show both Windows and Linux/macOS commands for activating the Python virtual environment (e.g., 'source venv/bin/activate' for Linux/macOS).
- Consider presenting environment variable setup instructions for all platforms together, or alternate the order to avoid Windows-first bias.
- Explicitly state that all commands (except where noted) work on Linux/macOS as well as Windows.
Azure App Configuration
Integrate Azure App Configuration using a continuous integration and delivery pipeline
...es/azure-app-configuration/integrate-ci-cd-pipeline.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows command prompt and PowerShell examples are presented before macOS and Linux equivalents. The MSBuild script uses Windows-style path separators (\) in the export command, which may not work on Linux/macOS. Visual Studio Code is mentioned as cross-platform, but the build instructions and scripting examples are more tailored to Windows environments.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, rather than after.
- Use platform-agnostic path separators or provide separate MSBuild script examples for Windows and Unix-based systems.
- Explicitly mention any differences in command syntax or file paths for Linux/macOS users.
- Include troubleshooting notes for common Linux/macOS issues (e.g., path separator problems, environment variable persistence).
- Highlight that the Azure CLI and .NET CLI are cross-platform, and provide links to installation instructions for all major OSes.
Azure App Configuration
Quickstart for Azure App Configuration with Aspire
.../articles/azure-app-configuration/quickstart-aspire.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation shows a mild Windows bias by consistently referencing Docker Desktop as the container runtime, which is most commonly used on Windows. There are no explicit PowerShell-only examples or Windows-exclusive commands, but Docker Desktop is mentioned as the default tool for container management, and screenshots feature Docker Desktop. Linux alternatives (e.g., Docker Engine, Podman) are not mentioned. The order of presentation also puts Windows-centric tools first.
Recommendations
- Mention Linux-native container runtimes such as Docker Engine, Podman, or containerd alongside Docker Desktop.
- Include screenshots or instructions for running containers on Linux/macOS, not just Docker Desktop.
- Clarify that all CLI commands (dotnet, etc.) work cross-platform and specify any OS-specific steps if needed.
- Add a note that Aspire and Azure App Configuration emulator work on Linux/macOS and provide links to relevant setup guides.
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 command-line operations, but PowerShell examples are given equal prominence and are presented immediately after CLI examples. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no explicit mention is made of Linux/macOS compatibility or alternative shell usage. There are no Linux/macOS-specific instructions, nor is there any guidance for users who may not have PowerShell available.
Recommendations
- Clearly state that Azure CLI works on Windows, Linux, and macOS, and is recommended for cross-platform use.
- Present Azure CLI examples before PowerShell examples, or indicate CLI as the default/preferred method for non-Windows users.
- Add a note clarifying that PowerShell examples are intended for Windows users, and provide installation guidance for PowerShell Core if relevant to Linux/macOS.
- Consider adding bash-specific tips or troubleshooting notes for Linux/macOS users if any differences exist.
- Explicitly mention that all steps can be completed on Linux/macOS using Azure CLI.
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
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 shown first, with Linux/macOS instructions given last. No Linux-specific tools or patterns are missing, but the ordering prioritizes Windows users.
Recommendations
- Present environment variable setup instructions for Linux/macOS first, or in parallel with Windows examples.
- Use a tabbed or side-by-side format for platform-specific commands to avoid implicit prioritization.
- Explicitly state that all platforms are supported and tested.
- Add troubleshooting notes for common Linux/macOS issues, if any.
Azure App Configuration
Quickstart for Azure App Configuration with .NET | Microsoft Docs
.../azure-app-configuration/quickstart-dotnet-core-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 .NET CLI is emphasized as cross-platform.
Recommendations
- Present environment variable instructions for all platforms in parallel or start with Linux/macOS to avoid Windows-first ordering.
- Add notes clarifying that all commands work equally on Linux/macOS and Windows.
- Consider grouping platform-specific instructions in tabs or side-by-side for parity.
- Ensure screenshots and references are not Windows-centric.
Azure App Configuration
Quickstart for adding feature flags to JavaScript apps
...pp-configuration/quickstart-feature-flag-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). The Windows command prompt and PowerShell commands are described in detail, with explicit instructions to restart the prompt, while the Linux/macOS instructions are listed last and without additional context. The Node.js installation link also references Windows and WSL before other platforms.
Recommendations
- Present environment variable instructions for Linux/macOS alongside or before Windows examples, or use tabs for platform parity.
- Add context for Linux/macOS users, such as shell persistence (e.g., adding exports to .bashrc/.zshrc).
- Reference cross-platform Node.js installation guides, not just Windows/WSL.
- Ensure all platform instructions are equally detailed and visible.
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, indicating a 'windows_first' bias. However, all platforms are covered with equivalent instructions, and no Windows-specific tools or patterns are used elsewhere.
Recommendations
- Present environment variable setup instructions in a neutral or alphabetical order, or group Windows, macOS, and Linux equally.
- Consider starting with a cross-platform example (e.g., Python's os.environ usage) before platform-specific shell commands.
- Explicitly mention that all platforms are supported and provide parity in instructions.
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 both Windows command prompt and PowerShell examples. Linux/macOS instructions are present and correct, but are listed after Windows instructions, which may signal a slight prioritization of Windows users.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Consider grouping all OS instructions in a table or side-by-side tabs for parity.
- Ensure that Linux/macOS users are addressed equally in all sections, not only as an afterthought.
- If possible, provide screenshots or CLI examples for Linux/macOS users (e.g., Azure CLI usage on bash).
Azure App Configuration
Quickstart for adding feature flags to Spring Boot with Azure App Configuration
...p-configuration/quickstart-feature-flag-spring-boot.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 all other steps (Java, Maven, Spring Boot) are cross-platform.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or side-by-side.
- Consider grouping all OS instructions in a table for parity.
- Add explicit notes confirming that all steps are cross-platform except environment variable setup, to reassure non-Windows users.
- Avoid language like 'restart the command prompt' that is Windows-specific; clarify for Linux/macOS users (e.g., 'restart your terminal session').
Azure App Configuration
Quickstart for using Azure App Configuration with Go web applications
...icles/azure-app-configuration/quickstart-go-web-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 all code samples are cross-platform Go code.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
- Consider grouping environment variable instructions by OS or using tabs for each platform.
- Add a note clarifying that all Go code and Azure CLI commands are cross-platform.
- Ensure parity in troubleshooting or advanced sections if present (none detected here).
Azure App Configuration
Using Azure App Configuration in JavaScript apps with the Azure SDK for JavaScript | Microsoft Docs
...icles/azure-app-configuration/quickstart-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page generally provides cross-platform instructions for using Azure App Configuration in JavaScript apps, but there is a mild Windows bias in the environment variable setup section. Windows Command Prompt and PowerShell instructions are listed before Linux/macOS equivalents, and PowerShell is called out specifically. The Node.js installation and usage instructions are platform-neutral, and Linux/macOS users are not blocked from completing the tutorial.
Recommendations
- Present environment variable instructions in parallel or grouped by OS, rather than listing Windows first.
- Avoid calling out Windows-specific tools (like PowerShell) unless necessary, and provide equal detail for Linux/macOS shells.
- Consider using tabs or collapsible sections for OS-specific instructions to improve parity and clarity.
- Explicitly state that all steps work on Linux/macOS unless otherwise noted.
Azure App Configuration
Using Azure App Configuration in Python apps with the Azure SDK for Python
.../articles/azure-app-configuration/quickstart-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits minor Windows bias in the 'Prerequisites' section, where instructions for setting up Python link only to Windows-specific documentation. Additionally, when setting environment variables, Windows command prompt and PowerShell examples are listed before Linux/macOS equivalents. However, Linux/macOS instructions are present and complete, and all code samples are cross-platform.
Recommendations
- Provide links to Python installation/setup documentation for Linux and macOS alongside the Windows link in the Prerequisites section.
- Alternate the order of environment variable examples, or present Linux/macOS instructions first in at least some sections.
- Explicitly state that all code samples are platform-agnostic and can be run on Windows, Linux, or macOS.
- Consider adding a brief note at the top clarifying cross-platform compatibility.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page displays a mild Windows bias in the environment variable setup section, where Windows CMD and PowerShell examples are given first and in more detail, while Linux/macOS equivalents are provided later and less prominently. The use of setx (Windows-specific) is described with restart instructions, whereas the Linux/macOS export command is listed without such context. Other sections, such as code editing and build/test commands, are cross-platform and neutral.
Recommendations
- Present environment variable setup instructions for Windows, Linux, and macOS in parallel tabbed sections, giving equal prominence and detail to each.
- Clarify restart requirements for environment variable changes on all platforms, not just Windows.
- Avoid listing Windows commands first; alternate or use tabs to prevent perceived priority.
- Include explicit Linux/macOS shell examples for all CLI steps where applicable.
- Mention that Azure CLI works on all platforms, and provide troubleshooting tips for common platform-specific issues.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/feature-management-overview.md
...azure-app-configuration/feature-management-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists .NET and ASP.NET Core libraries first in all tables and sections, which are traditionally associated with Windows development. No explicit Windows-only tools or PowerShell examples are present, and Linux is not mentioned at all. However, the ordering and focus on .NET/ASP.NET Core may subtly prioritize Windows-centric frameworks over cross-platform or Linux-first technologies.
Recommendations
- Explicitly mention the cross-platform nature of .NET Core and ASP.NET Core, and clarify that these libraries are supported on Linux and macOS as well as Windows.
- Rotate or randomize the order of frameworks in tables, or group them by language family rather than by traditional Windows-first frameworks.
- Add a note or section highlighting Linux compatibility and any Linux-specific considerations for each library.
- Where possible, provide examples or references for running the libraries on Linux (e.g., using .NET on Ubuntu, Java on CentOS, etc.).
- Ensure that documentation does not implicitly suggest Windows is the default or primary platform by always listing Windows-associated frameworks first.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/how-to-targeting-filter-python.md
...re-app-configuration/how-to-targeting-filter-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and macOS/Linux instructions for setting up a Python virtual environment and setting environment variables. However, in both cases, the Windows instructions are presented first, followed by macOS/Linux. There are no Linux-specific examples or tools missing, and parity is maintained in the commands provided. No exclusive use of Windows tools or PowerShell is present, but the order of presentation consistently favors Windows.
Recommendations
- Alternate the order of platform instructions (e.g., show Linux/macOS first in some sections) to avoid implicit prioritization of Windows.
- Consider grouping platform-specific instructions under clear headings, so users can quickly find their OS without perceiving bias.
- Explicitly mention that all platforms are equally supported, and ensure that Linux/macOS users feel their workflows are first-class.
- Where possible, provide combined or platform-agnostic commands (e.g., using `python -m venv venv` and then describing activation for each OS in a table or side-by-side format).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-javascript.md
.../azure-app-configuration/howto-telemetry-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions in the order: Windows CMD, PowerShell, then macOS/Linux. This prioritizes Windows tools and patterns before Linux equivalents, which may suggest a subtle Windows-first bias. However, all platforms are ultimately covered with appropriate examples.
Recommendations
- Present environment variable setup instructions for all platforms in parallel (e.g., a table or side-by-side code blocks) rather than listing Windows first.
- Rotate the order of platform instructions or start with the platform most relevant to the target audience.
- Explicitly state that the instructions apply equally to Windows, macOS, and Linux to reinforce cross-platform parity.
- Where possible, use platform-agnostic language and tools in introductory explanations before diving into platform-specific commands.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-targetingfilter-aspnet-core.md
...app-configuration/howto-targetingfilter-aspnet-core.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only cross-platform .NET CLI commands and code samples, but does not include any platform-specific instructions or examples. However, it omits any explicit mention of Linux or macOS environments, and does not address platform-specific considerations (such as file paths, environment variables, or shell differences). There are no Windows-only tools or PowerShell commands, but the lack of explicit Linux/macOS parity or troubleshooting guidance may disadvantage non-Windows users.
Recommendations
- Explicitly state that all dotnet CLI commands work on Windows, Linux, and macOS.
- Add notes or examples for common Linux/macOS shell environments (e.g., bash/zsh), especially for commands involving file paths or environment variables.
- Mention where files (such as user secrets) are stored on Linux/macOS, as paths differ from Windows.
- Include troubleshooting tips for Linux/macOS users, such as permissions or .NET SDK installation guidance.
- If screenshots or UI references are shown, provide Linux/macOS equivalents where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-core-app.md
.../azure-app-configuration/quickstart-dotnet-core-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents Windows command-line instructions (cmd and PowerShell) before Linux/macOS equivalents when setting environment variables. However, all major steps include Linux/macOS commands, and the .NET CLI is emphasized as cross-platform. There are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present Linux/macOS commands before or alongside Windows commands to avoid implicit prioritization of Windows.
- Explicitly state that all steps are cross-platform at the beginning of relevant sections.
- Where possible, use generic or platform-agnostic instructions first, then provide platform-specific notes.
- Ensure screenshots and terminal output examples are not exclusively from Windows environments.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md
...icles/azure-app-configuration/quickstart-go-web-app.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 macOS/Linux, but does include equivalent Linux/macOS commands. There are no exclusive Windows tools or missing Linux examples, and the Go application instructions are cross-platform.
Recommendations
- Present macOS/Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
- Consider using tabbed or parallel layouts for OS-specific instructions to reinforce parity.
- Explicitly state that all Go commands and code samples are cross-platform.
- Where possible, use OS-agnostic language (e.g., 'your terminal') before listing OS-specific commands.