Azure App Configuration
166
Total Pages
109
Linux-Friendly Pages
57
Pages with Bias
34.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
479 issues found
Showing 451-475 of 479 flagged pages
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.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 ordering prioritizes Windows users, which may suggest a subtle Windows-first bias. However, all major platforms are represented, and no examples or tools are exclusive to Windows.
Recommendations
- Present environment variable setup instructions in a neutral order, such as grouping Windows and Linux/macOS together or listing Linux/macOS first.
- Consider using tabbed code blocks or clear headings for each platform to avoid implying priority.
- Ensure parity in instructions and examples for all supported platforms throughout the documentation.
Create Pull Request
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/configuration-provider-overview.md
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by listing .NET/.NET Framework and related Microsoft technologies (which are most commonly associated with Windows) at the top of the provider libraries table, with Linux-native or cross-platform-first frameworks (like Python, JavaScript, Go) listed later. There are no explicit Linux or Unix-specific examples, tools, or patterns mentioned, but the ordering and emphasis on Microsoft-centric stacks may implicitly prioritize Windows environments.
Recommendations
- Reorder the 'Configuration Provider Libraries' table to alternate or group by language family or platform neutrality, rather than leading with .NET/Microsoft technologies.
- Explicitly mention cross-platform compatibility for each provider, highlighting Linux support where applicable.
- Add a section or note clarifying that all listed providers are supported on Linux and provide links to Linux-specific setup or usage guides if available.
- Where possible, provide sample links or usage notes that demonstrate running these providers in Linux environments (e.g., with Docker, on Ubuntu, etc.).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.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 (bash). This ordering gives Windows precedence, which may suggest a subtle Windows-first bias. However, all major platforms are covered and no examples or tools are missing for Linux/macOS.
Recommendations
- Present environment variable setup instructions in a neutral or rotating order (e.g., Linux/macOS first, or group by shell type rather than OS).
- Explicitly state that the instructions apply equally to all platforms, and consider using a tabbed or collapsible UI for platform-specific commands to avoid implicit prioritization.
- Ensure future documentation consistently provides parity in examples and tool references for all major platforms.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/configuration-provider-overview.md
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric technologies) and their libraries at the top of the provider table, with their samples and release notes featured first. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET/Windows frameworks over Linux-native or cross-platform frameworks may signal a preference for Windows environments.
Recommendations
- Reorder the provider libraries table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than placing all .NET/Windows-centric entries first.
- Explicitly mention cross-platform compatibility for each provider, especially for .NET libraries that also run on Linux via .NET Core.
- Add a section or note highlighting Linux and container-native scenarios (such as Kubernetes), and link to relevant samples or documentation.
- Ensure that any future code or CLI examples include both Windows (PowerShell/cmd) and Linux (bash/sh) variants where applicable.
- Consider including a summary table or quickstart for Linux users to improve parity and discoverability.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.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 bash. This ordering prioritizes Windows users and may give the impression that Windows is the primary or preferred platform.
Recommendations
- Present environment variable setup instructions for all platforms together, or rotate the order in which platforms are presented (e.g., start with Linux/macOS, then Windows).
- Use platform-agnostic language where possible, such as 'In your terminal, set the environment variable as follows:', then provide all variants in a single code block or table.
- Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
- Consider adding a note that all major platforms are supported equally.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/configuration-provider-overview.md
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists .NET and ASP.NET Core provider libraries first and in greatest detail, with their samples and release notes highlighted before those for Java, Python, JavaScript, and Go. This ordering and emphasis reflects a 'windows_first' bias, as .NET and ASP.NET Core are primarily associated with Windows development. There are no explicit PowerShell examples or Windows-only tools mentioned, but the prioritization of Windows-centric frameworks may make Linux or cross-platform users feel secondary.
Recommendations
- Reorder the provider libraries table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) or by popularity, rather than always listing .NET/.NET Framework first.
- Explicitly mention the cross-platform support of .NET Core and .NET 5+ to clarify that these libraries are not Windows-only.
- Add a note or section highlighting Linux and container-native usage patterns, especially for Java, Python, and Go.
- Ensure that sample links and documentation for non-Windows platforms are as prominent and detailed as those for .NET.
- Consider including a brief statement about the parity of features and support across platforms, and encourage feedback from Linux and macOS users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions in the order of Windows (cmd), then PowerShell, and only afterwards macOS/Linux. This ordering prioritizes Windows users and may give the impression that Windows is the primary or preferred platform. However, all platforms are covered and examples are provided for each.
Recommendations
- Present environment variable setup instructions in a neutral or rotating order (e.g., Linux/macOS first, or group by shell type rather than OS).
- Consider using tabs or collapsible sections for platform-specific instructions to give equal prominence to all platforms.
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS to reinforce cross-platform parity.
- Ensure that any future examples or troubleshooting steps also provide parity across platforms, not just in environment variable setup.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/configuration-provider-overview.md
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric technologies) libraries and examples before those for Java, Python, JavaScript, and Go. There are no explicit PowerShell examples or Windows-only tools, but the ordering and emphasis on .NET frameworks may implicitly prioritize Windows development environments. There are no missing Linux examples, but the documentation could better highlight cross-platform parity.
Recommendations
- Reorder the 'Configuration Provider Libraries' table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than listing all .NET/Windows-centric libraries first.
- Explicitly mention that all libraries are cross-platform where applicable, and provide sample links or notes for Linux/macOS usage if any differences exist.
- Add a short section or note clarifying that Azure App Configuration providers are supported on both Windows and Linux, and that the .NET libraries work on .NET Core/.NET 5+ (which are cross-platform), not just on Windows.
- If possible, provide at least one example or sample link that demonstrates usage on Linux (e.g., running a .NET Core app on Ubuntu, or a Java/Python/Go example on Linux).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions in the order of Windows CMD, PowerShell, and then macOS/Linux, which is a 'windows_first' bias. However, all platforms are ultimately covered, and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present environment variable instructions for all platforms in parallel (e.g., a table or side-by-side code blocks) rather than listing Windows first.
- Consider rotating the order of platform instructions or starting with the platform most likely used by the target audience (e.g., Linux for Python development).
- Explicitly state that the instructions apply equally to all platforms to reinforce cross-platform parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions in the order of Windows (cmd), PowerShell, and then macOS/Linux, which is a common 'windows_first' bias. However, all platforms are covered and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present environment variable setup instructions with Linux/macOS first, or present all platforms in parallel (e.g., a table or side-by-side code blocks) to avoid implicit prioritization.
- Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
- Consider explicitly stating that the instructions apply equally to all platforms to reinforce parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions in the order: Windows CMD, PowerShell, then macOS/Linux. This 'Windows-first' ordering may suggest a preference for Windows users, though Linux/macOS instructions are present and complete.
Recommendations
- Present environment variable setup instructions in a neutral or platform-parallel format, such as a table with all platforms side-by-side.
- Rotate the order of platform instructions, or begin with the most common platform for the target audience.
- Explicitly state that the instructions apply equally to Windows, macOS, and Linux to reinforce cross-platform parity.
- Where possible, use cross-platform tools or commands (e.g., Python's os.environ in code) to minimize OS-specific steps.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions in the order of Windows CMD, then PowerShell, and finally macOS/Linux, which is a 'windows_first' ordering. However, all platforms are covered and no examples or tools are missing for Linux/macOS.
Recommendations
- Present environment variable setup instructions with Linux/macOS first or in parallel with Windows, to avoid implying Windows is the primary or default platform.
- Consider grouping all platform-specific instructions together under a table or clear headings, so no platform appears prioritized.
- Ensure future documentation maintains parity by providing examples for all major platforms in a balanced order.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.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 Linux/macOS (bash). This ordering prioritizes Windows tooling and patterns, which may suggest a subtle Windows-first bias. However, all platforms are represented and no platform is omitted.
Recommendations
- Rotate or randomize the order of platform-specific instructions, or explicitly state that the order does not imply priority.
- Consider grouping all environment variable setup commands in a table for parity, or present Linux/macOS first if usage data supports it.
- Add a note acknowledging cross-platform usage and encourage users to select the instructions appropriate for their OS.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents environment variable setup instructions in the order: Windows CMD, PowerShell, then macOS/Linux, which may subtly prioritize Windows users. However, all platforms are covered and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present environment variable instructions for all platforms together, or start with a neutral (e.g., bash) example.
- Consider using a tabbed or side-by-side format for platform-specific commands to give equal prominence to Windows, macOS, and Linux.
- Explicitly state that the instructions apply to all major platforms to reinforce cross-platform parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.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 (bash). While all platforms are covered, Windows commands are presented first, which may signal a subtle preference or bias toward Windows users.
Recommendations
- Present environment variable setup instructions in a neutral or rotating order (e.g., Linux/macOS first, or group all together without prioritizing one OS).
- Consider using tabbed code blocks or collapsible sections for each platform to give equal prominence.
- Explicitly state that the instructions apply to all major platforms and that the order does not imply priority.
- Review other sections for similar ordering and ensure parity in example prominence.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions in a Windows-first order, listing Windows Command Prompt and PowerShell commands before the equivalent macOS/Linux bash command. However, all other instructions and code samples are platform-agnostic and do not show a preference for Windows-specific tools or patterns.
Recommendations
- Present environment variable setup instructions in a platform-neutral order, such as listing Linux/macOS first or grouping all OS instructions together without prioritizing Windows.
- Consider using a tabbed or side-by-side format for environment variable setup commands, allowing users to easily find instructions for their operating system.
- Explicitly state that the tutorial is cross-platform and that all steps apply equally to Windows, Linux, and macOS, except where OS-specific commands are required.
- Ensure future documentation sections maintain parity by providing examples for all major platforms where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions in the order: Windows Command Prompt (setx), PowerShell, then macOS/Linux (export). This ordering prioritizes Windows users by listing their instructions first, which may subtly reinforce a Windows-centric perspective. However, all major platforms are represented and no platform is omitted.
Recommendations
- Rotate or randomize the order of platform-specific instructions, or list Linux/macOS first to balance exposure.
- Consider grouping all environment variable commands in a table with columns for each OS/shell, so no platform is visually prioritized.
- Explicitly state that the instructions apply equally to all platforms, and that the order does not imply preference.
- Where possible, use cross-platform commands or tools, or highlight them if available.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-recover-deleted-stores-in-azure-app-configuration.md
...owto-recover-deleted-stores-in-azure-app-configuration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes recovery and purge operations using the Azure Portal UI, with no mention of command-line tools or scripts. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, nor are there any PowerShell examples. However, the absence of CLI examples means Linux and macOS users are not provided with parity for automation or non-GUI workflows.
Recommendations
- Add Azure CLI examples for all major operations (setting retention policy, enabling purge protection, listing/recovering/purging stores) to ensure Linux and macOS users can follow along.
- If PowerShell examples are added, ensure Azure CLI equivalents are always included and presented either first or side-by-side.
- Explicitly mention that all operations can be performed via CLI and provide links to relevant Azure CLI documentation.
- Consider including bash script snippets for common automation scenarios.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-javascript.md
...onfiguration/howto-variant-feature-flags-javascript.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 macOS/Linux equivalent, but does include all major platforms. No Linux examples or tools are missing, and the rest of the tutorial uses cross-platform Node.js and bash commands.
Recommendations
- Present platform-specific instructions in parallel (side-by-side or in a table), rather than listing Windows first.
- Consider listing Linux/macOS instructions before Windows, or at least alternating the order in different tutorials to avoid implicit prioritization.
- Explicitly state that all platforms are supported and tested, to reinforce parity.
- Where possible, use cross-platform commands (e.g., via npm scripts or dotenv files) to minimize platform-specific steps.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-targetingfilter-javascript.md
...-app-configuration/howto-targetingfilter-javascript.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 Linux/macOS equivalent. All other code and instructions are cross-platform and do not show a Windows or PowerShell bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel (side-by-side or in a tabbed format) rather than listing Windows first.
- Consider listing Linux/macOS commands first, as Node.js development is common on those platforms.
- Explicitly state that all commands and code samples are cross-platform, except where noted.
- Where possible, use platform-agnostic instructions or provide clear parity for all supported platforms.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-javascript.md
...icles/azure-app-configuration/quickstart-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform instructions, but in the 'Prerequisites' and 'Configure an environment variable' sections, Windows-specific instructions (Windows command prompt and PowerShell) are listed before Linux/macOS equivalents. The Node.js installation link also prioritizes Windows and WSL. However, Linux/macOS instructions are present and complete, and there are no sections that are Windows-only or missing Linux examples.
Recommendations
- Present platform-specific instructions in a neutral or rotating order (e.g., start with Linux/macOS in some sections, or use tabbed content with no clear priority).
- In the 'Prerequisites' section, provide a more balanced Node.js installation reference, such as linking to the official Node.js site or including Linux/macOS installation resources alongside Windows.
- Consider using tabbed or side-by-side layouts for environment variable setup, so no platform is visually prioritized.
- Explicitly state that all examples are cross-platform unless otherwise noted, to reassure non-Windows users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/azure-pipeline-import-task.md
.../azure-app-configuration/azure-pipeline-import-task.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not show explicit Windows bias in terms of command-line examples, tools, or instructions, but it also does not provide any platform-specific guidance or examples. There are no references to Windows-only tools (such as PowerShell), nor are there instructions or screenshots that are specific to Windows. However, the documentation lacks any mention of Linux or cross-platform considerations, such as file path formats, agent OS compatibility, or differences in running pipelines on Linux versus Windows agents. This absence may lead to implicit bias by not addressing the needs of Linux users.
Recommendations
- Add a section clarifying that the Azure Pipelines agent and the App Configuration Import task are supported on both Windows and Linux agents, and note any OS-specific considerations.
- Include examples or notes about specifying file paths in a cross-platform way (e.g., using forward slashes for Linux, backslashes for Windows, or using environment variables).
- If there are any differences in behavior or requirements between Windows and Linux agents (such as permissions, file system case sensitivity, or Node.js installation), document these explicitly.
- Provide at least one example or screenshot showing the task being configured or run on a Linux agent, or clarify that the UI and steps are the same across platforms.
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 for Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. All other code and instructions are cross-platform and do not show a strong Windows or PowerShell bias.
Recommendations
- Present environment variable setup commands for all platforms together, or alternate the order (e.g., show Linux/macOS first in some sections).
- Consider using a table or tabbed code blocks to make platform parity more visually clear.
- Explicitly state that all code examples are cross-platform unless otherwise noted, to reassure non-Windows users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-recover-deleted-stores-in-azure-app-configuration.md
...owto-recover-deleted-stores-in-azure-app-configuration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes Azure App Configuration recovery operations using the Azure Portal UI, with no mention of command-line tools or automation. There are no examples or instructions for performing these tasks via CLI, PowerShell, or scripting, and thus no Linux (or cross-platform) parity is demonstrated. This omission implicitly favors GUI-based workflows, which are more common on Windows, and neglects users who prefer or require command-line or automated solutions, especially on Linux or macOS.
Recommendations
- Add equivalent instructions and examples for performing all recovery, purge, and configuration operations using the Azure CLI (az appconfig commands), which is cross-platform.
- If PowerShell examples are added, ensure to also provide Azure CLI examples for Linux/macOS users.
- Explicitly mention that all operations can be performed via CLI and provide links to relevant CLI documentation.
- Consider including bash script snippets for common automation scenarios.
- Clarify any differences or limitations between portal, CLI, and PowerShell approaches.
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 does not display overt Windows bias in terms of command-line instructions or tool references; all shell commands use the cross-platform 'dotnet' CLI and .NET Secret Manager, which are available on both Windows and Linux. However, there is a subtle bias in that there are no explicit Linux/macOS-specific instructions, troubleshooting notes, or terminal output examples, which may leave Linux users uncertain about environment-specific differences or requirements.
Recommendations
- Explicitly mention that all dotnet CLI and Secret Manager commands work on Linux/macOS as well as Windows.
- Add a note or section confirming cross-platform compatibility, and provide any Linux/macOS-specific prerequisites (such as ensuring the dotnet CLI is in PATH, or how to install it on Linux).
- Include screenshots or terminal output examples from Linux/macOS environments alongside or in place of Windows examples, where relevant.
- If there are any known differences in behavior or setup steps for Linux/macOS (such as file permissions or environment variable handling), document these explicitly.