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 426-450 of 479 flagged pages
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 platform-specific instructions for setting environment variables, listing Windows Command Prompt and PowerShell methods before the Linux/macOS equivalent. However, all code samples and build/run instructions are cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
- List Linux/macOS environment variable instructions before Windows/PowerShell, or present all platforms in parallel.
- Explicitly state that all steps are cross-platform and that the Go app works on Linux/macOS as well as Windows.
- Consider adding a note about how to unset or update environment variables on each platform for completeness.
Create Pull Request
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
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). All other code and workflow examples are cross-platform and do not show Windows-specific bias.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions to avoid implying Windows primacy.
- Consider grouping OS-specific instructions in tabs or side-by-side format for equal visibility.
- Explicitly state that all Go and Azure CLI commands are cross-platform and work on Linux/macOS.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias in several places: environment variable setup is shown first with Windows Command Prompt and PowerShell examples, while Linux/macOS is mentioned last. The use of 'setx' and PowerShell commands are Windows-specific tools, and the build/run instructions reference 'command prompt' terminology. Linux/macOS instructions are present but not prioritized.
Recommendations
- Present environment variable setup instructions for Linux/macOS before or alongside Windows examples, not after.
- Use neutral terminology like 'terminal' or 'shell' instead of 'command prompt'.
- Provide explicit instructions for common Linux/macOS shells (bash, zsh, etc.) where relevant.
- Avoid Windows-specific tools (like 'setx') as the primary example; offer cross-platform alternatives or clarify platform applicability.
- Where multiple platforms are supported, group instructions by OS or use tabs to allow users to select their platform.
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
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Windows-specific installation guidance for Node.js before mentioning WSL. However, all code samples and main workflows are cross-platform and do not rely on Windows-only tools or patterns.
Recommendations
- Present environment variable instructions for Linux/macOS first or side-by-side with Windows to avoid implying Windows is the primary platform.
- In the prerequisites, mention Linux/macOS installation options for Node.js before or alongside Windows, and provide a direct link to cross-platform installation guides.
- Ensure that all platform-specific instructions are grouped together and clearly labeled, rather than listing Windows first by default.
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
Windows Tools
Summary
The documentation page displays minor Windows bias in the prerequisites and environment variable setup sections. Specifically, it links only to Windows-specific Python installation instructions and lists Windows command prompt and PowerShell commands before Linux/macOS equivalents when setting environment variables. However, all code samples and instructions for running the Python app are cross-platform, and Linux/macOS commands are present and correct.
Recommendations
- In the prerequisites, add links or instructions for installing Python on Linux and macOS, not just Windows.
- When listing environment variable setup commands, alternate the order or present Linux/macOS commands first in some sections to avoid implicit prioritization of Windows.
- Explicitly state that all code samples and instructions are platform-agnostic unless otherwise noted.
- Consider adding a table or tabbed interface for environment variable setup, so users can easily find instructions for their OS.
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
Windows Tools
Summary
The documentation demonstrates a mild Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are explicitly mentioned, while Linux/macOS instructions are grouped together and shown last. The Node.js installation prerequisite also references Windows and WSL before other platforms.
Recommendations
- Present platform instructions in parallel tabs or side-by-side, rather than listing Windows first.
- Give equal prominence to Linux/macOS instructions, possibly listing them first or in alphabetical order.
- Include direct links or guidance for installing Node.js on Linux/macOS, not just Windows/WSL.
- Avoid language that suggests Windows is the default or primary platform.
- Where possible, use platform-neutral instructions (e.g., cross-platform environment variable setting tools).
Azure App Configuration
Roll out features to targeted audiences in a Node.js app
...-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 method. Windows methods are listed first and in greater detail, which may suggest a slight Windows-first bias. However, Linux/macOS instructions are present and correct, and the rest of the tutorial is platform-neutral (Node.js/Express).
Recommendations
- Present environment variable instructions in a platform-neutral or parallel format (e.g., a table or side-by-side code blocks for Windows and Linux/macOS).
- Avoid listing Windows commands before Linux/macOS commands; consider alphabetical or usage-based ordering.
- Explicitly state that all steps work on Linux/macOS unless otherwise noted.
- Add a note clarifying that the Node.js/Express code is cross-platform and works on Windows, Linux, and macOS.
Azure App Configuration
Enable telemetry for feature flags in a Python application
...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 for Windows (cmd and PowerShell) before mentioning the equivalent Linux/macOS command. No other platform-specific bias is present; all code and tooling examples are cross-platform Python and Azure services.
Recommendations
- Present Linux/macOS environment variable instructions before Windows commands, or group them together without prioritizing one platform.
- Explicitly state that all commands are cross-platform where applicable.
- Consider adding a table or section that lists environment variable setup for all major platforms side-by-side for parity and clarity.
Azure App Configuration
Roll out features to targeted audiences in a Node.js app
...-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 method. Windows commands are listed first, which may suggest a Windows-centric approach. However, Linux/macOS instructions are present and accurate, and all code samples use cross-platform Node.js/Express commands.
Recommendations
- Present environment variable instructions in parallel (side-by-side) or start with a neutral/cross-platform method (e.g., bash) before listing Windows-specific commands.
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS where possible.
- Consider using a table or tabs to allow users to select their OS for command-line instructions.
- Ensure that any references to Azure portal or tooling mention cross-platform compatibility if relevant.
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 libraries (which are primarily associated with Windows development) first in the configuration provider libraries table, with their samples and release notes prominently linked. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET/Windows-centric frameworks before cross-platform or Linux-native stacks (such as Python, JavaScript, Go) suggests a subtle 'windows_first' bias. There are no Linux-specific examples, tools, or guidance, nor are Linux or cross-platform usage patterns highlighted.
Recommendations
- Reorder the configuration provider libraries table to alternate or group by language family (e.g., interpreted, compiled, JVM-based) rather than placing .NET/Windows-centric libraries first.
- Explicitly mention the cross-platform nature of the .NET Standard and .NET Core libraries, clarifying that they work on Linux and macOS as well as Windows.
- Add Linux-specific or cross-platform usage notes or examples, especially for popular Linux deployment scenarios (e.g., Docker, Kubernetes, CLI usage on Linux).
- Ensure that samples and documentation links for each provider include Linux-compatible instructions or highlight any OS-specific considerations.
- If possible, add a section or callout that addresses platform compatibility and best practices for both Windows and Linux environments.
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 providers first in the table of configuration provider libraries, with their samples and release notes prominently featured before Java, Python, JavaScript, and Go equivalents. This ordering may implicitly prioritize Windows-centric technologies, as .NET and ASP.NET Core are most commonly associated with Windows environments, even though they are now cross-platform. There are no explicit Windows-only tools or PowerShell examples, and Linux is not mentioned or omitted in examples, but the ordering and emphasis suggest a subtle Windows/.NET-first bias.
Recommendations
- Reorder the provider libraries table to alternate or group by language family or platform neutrality, rather than leading with .NET/Windows-centric stacks.
- Explicitly mention cross-platform compatibility for .NET and ASP.NET Core providers to clarify that they are not Windows-only.
- Add a note or section highlighting Linux and container-native usage patterns, especially for Java, Python, Go, and JavaScript stacks.
- Ensure that future documentation and samples include Linux-specific instructions or examples where relevant, such as environment variable configuration, CLI usage, or deployment scenarios.
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 configuration provider libraries for multiple languages and platforms, but the ordering and emphasis place .NET (and by extension, Windows-centric technologies) first, with detailed links and samples for .NET Standard, ASP.NET Core, Azure Functions, and .NET Framework before mentioning Java, Python, JavaScript, and Go. There are no explicit Linux or cross-platform command-line examples, but the structure implicitly prioritizes Windows/.NET ecosystems.
Recommendations
- Reorder the provider library table to rotate or randomize the order of languages/platforms, or group by language family (e.g., statically typed, dynamically typed) rather than placing .NET/.NET Framework first.
- Add explicit mention of cross-platform compatibility for each provider, especially for .NET Core and ASP.NET Core, which are cross-platform.
- Include Linux/macOS-specific notes or examples where relevant, such as how to use these providers in Linux containers or on non-Windows environments.
- Ensure parity in sample links and documentation depth for non-Windows platforms and languages.
- Consider adding a section or callout highlighting Linux and containerized deployment scenarios, which are common in modern cloud-native development.
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, with their samples and release notes, before Java, Python, JavaScript, and Go equivalents. This ordering implicitly prioritizes Windows-centric technologies (especially .NET/ASP.NET) over Linux-native or cross-platform stacks, despite the cross-platform nature of Azure App Configuration. However, there are no explicit Windows-only tools, PowerShell examples, or missing Linux examples; all samples are language/platform-specific and not OS-specific.
Recommendations
- Reorder the provider libraries table to alternate or group by language family (e.g., JVM, .NET, scripting) or by popularity, rather than listing all .NET/Windows-centric libraries first.
- Add a clarifying note that all listed libraries are cross-platform unless otherwise specified, and that .NET Core and ASP.NET Core are supported on Linux and macOS as well as Windows.
- Consider including explicit Linux/macOS usage notes or examples where relevant, especially for .NET Core and ASP.NET Core, to reinforce cross-platform support.
- If possible, provide a section or table that highlights OS compatibility for each provider, making it clear that Windows is not a prerequisite.
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 configuration provider libraries for multiple languages and platforms, but the ordering and emphasis place .NET (a Windows-centric ecosystem) and related Microsoft technologies first, before Java, Python, JavaScript, and Go. There are no explicit Windows-only tools or PowerShell examples, but the .NET focus and ordering may implicitly prioritize Windows development environments.
Recommendations
- Reorder the provider library table to avoid always listing .NET/Microsoft-first; consider alphabetical or usage-based ordering.
- Explicitly mention cross-platform compatibility for .NET libraries (e.g., .NET Core runs on Linux/macOS).
- Add a note clarifying that all listed providers are supported on both Windows and Linux where applicable.
- If possible, provide Linux/macOS-specific usage notes or samples, especially for .NET and Java providers.
- Ensure that future documentation and examples do not assume a Windows environment by default.
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 related Microsoft technologies (including .NET Standard, ASP.NET Core, Azure Functions, .NET Framework) first in both the provider library table and the feature matrix, before Java, Python, JavaScript, and Go. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET ecosystems (which are historically Windows-centric) may suggest a bias toward Windows/Microsoft platforms.
Recommendations
- Reorder the provider library table and feature matrix to avoid always listing .NET/Microsoft-first; consider alphabetical or usage-based ordering.
- Explicitly mention cross-platform compatibility for .NET providers, clarifying that they work on Linux and macOS as well as Windows.
- Add a brief section or note highlighting parity and support for Linux and non-Windows environments.
- If possible, provide Linux-specific usage notes or examples, especially for scenarios where platform differences may arise.
- Ensure that future documentation and samples are balanced in coverage between Windows and Linux environments.
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 related Microsoft technologies) provider libraries first and in greater detail, with .NET-specific samples and release notes preceding those for Java, Python, JavaScript, and Go. There is a clear ordering that prioritizes Windows-centric technologies, but there are no explicit Windows-only tools, PowerShell examples, or missing Linux examples. The bias is subtle and structural, favoring Windows/.NET ecosystems over others.
Recommendations
- Reorder the provider libraries table to avoid always listing .NET/Microsoft technologies first; consider alphabetical or usage-based ordering.
- Add explicit mention that all provider libraries are cross-platform and provide links to platform-agnostic usage guides.
- Where possible, include Linux/macOS-specific notes or samples, especially for .NET Core and Java, to reinforce cross-platform support.
- Ensure that documentation for each language/platform is equally detailed, with parity in sample links and release notes.
- If any CLI or scripting examples are added in the future, provide both Windows (PowerShell/CMD) and Linux (Bash) equivalents.
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 providers first, which are traditionally Windows-centric technologies, before mentioning Java, Python, JavaScript, and Go providers. There is no explicit mention of Windows-only tools or PowerShell, nor are there missing Linux examples or exclusive references to Windows patterns. However, the ordering of platforms and the focus on .NET/ASP.NET may subtly prioritize Windows environments.
Recommendations
- Reorder the provider libraries table to group by language family or popularity, or rotate the order periodically to avoid implicit prioritization.
- Explicitly mention cross-platform compatibility for .NET Core and ASP.NET Core providers, highlighting their support on Linux and macOS as well as Windows.
- Add a brief section or note clarifying that all listed providers are supported on both Windows and Linux (where applicable), and provide links to Linux-specific setup guides if available.
- Ensure that any future examples or walkthroughs include both Windows and Linux command-line instructions where relevant.
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 providers (which are primarily Windows-centric technologies) first in the provider libraries table, with their samples and release notes. There is no explicit mention of Windows-only tools or PowerShell, nor are there missing Linux examples, but the ordering and emphasis on .NET/Windows frameworks before cross-platform or Linux-native stacks (Java, Python, Go, JavaScript) suggests a subtle 'windows_first' bias.
Recommendations
- Reorder the provider libraries table to group or order entries by language popularity or cross-platform relevance, rather than placing .NET/Windows-centric frameworks first.
- Explicitly mention the cross-platform nature of .NET Core and clarify which providers are suitable for Linux environments.
- Provide a brief section or callout highlighting Linux usage, including any platform-specific considerations or links to Linux-focused samples.
- Ensure that all sample links and documentation are equally accessible and relevant for both Windows and Linux users.
- Consider adding a column or note indicating OS compatibility for each provider to make Linux support more visible.
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 in the table, followed by Java, Python, JavaScript, and Go. This ordering implicitly prioritizes Windows-centric technologies, as .NET and ASP.NET Core are traditionally associated with Windows environments, even though they are now cross-platform. There are no explicit Windows-only tools or PowerShell examples, and Linux is not mentioned at all, but the ordering and focus suggest a subtle Windows-first bias.
Recommendations
- Reorder the provider libraries table to group by language family or present all platforms equally, possibly rotating the order or using alphabetical order.
- Explicitly mention cross-platform compatibility for .NET and ASP.NET Core providers, highlighting Linux and macOS support.
- Add a note or section clarifying that all listed providers are supported on both Windows and Linux (where applicable), and provide links or references to Linux-specific usage or deployment guides if available.
- Ensure that future documentation and samples include Linux command-line and deployment examples alongside any Windows-specific instructions.
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 (Windows-centric platforms) configuration providers first in both the library table and the feature matrix, with Linux/Unix-first platforms (such as Python, Go, and JavaScript) appearing later. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET/Windows frameworks may suggest a subtle Windows bias.
Recommendations
- Reorder the configuration provider libraries table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than placing all .NET/Windows-centric providers first.
- Explicitly mention cross-platform compatibility for each provider, especially for .NET Standard and .NET Core, which run on Linux and macOS as well as Windows.
- Add a note clarifying that Azure App Configuration is supported equally on Linux and Windows, and that most providers are cross-platform.
- Consider including at least one Linux/Unix-specific example or reference (e.g., using the Python or Go provider on Linux) to balance the implicit focus on Windows.
- If possible, provide parity in sample links and documentation depth for Linux/Unix-targeted languages (Python, Go, JavaScript) as is done for .NET.
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 presents .NET/.NET Core (Microsoft technologies, typically associated with Windows) provider libraries and examples first in all lists and tables, before Java, Python, JavaScript, and Go equivalents. There are no explicit Linux or cross-platform command-line examples, but the ordering implicitly prioritizes Windows-centric technologies.
Recommendations
- Reorder the provider libraries table to rotate or randomize the order, or group by language family (e.g., statically typed, dynamically typed) rather than always listing .NET/.NET Core first.
- Explicitly mention the cross-platform nature of the provider libraries, especially for .NET Core, Java, Python, JavaScript, and Go.
- Add a section or note clarifying that all listed libraries are supported on both Windows and Linux (where applicable), and provide links to platform-specific setup guides if differences exist.
- Ensure that future documentation includes Linux/Unix-specific examples or notes where relevant (e.g., environment variable setup, file paths), even if not present on this page.
- Consider including a table column or icon indicating cross-platform compatibility for each provider.
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 providers (which are primarily Windows-centric technologies) first in the library table, with their samples and release notes, before mentioning Java, Python, JavaScript, and Go equivalents. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET/ASP.NET Core may suggest a subtle Windows-first bias.
Recommendations
- Reorder the provider libraries table to group by language family or present cross-platform options (e.g., Java, Python, Go) before or alongside .NET/ASP.NET Core to avoid the perception of Windows-first bias.
- Explicitly mention the cross-platform nature of .NET Core and ASP.NET Core, and clarify which libraries are usable on Linux/macOS as well as Windows.
- Add a note or section highlighting Linux and container-native usage patterns, such as integration with Kubernetes, to balance the focus.
- Ensure that future documentation includes Linux/macOS-specific guidance or examples where relevant, especially for setup, deployment, or troubleshooting.
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 providers (primarily Windows-centric technologies) first in the table of configuration provider libraries, with their samples and release notes appearing before Java, Python, JavaScript, and Go equivalents. There are no explicit Windows-only tools or PowerShell examples, nor are Linux or cross-platform command-line examples present. However, the ordering and emphasis on .NET/Windows technologies may subtly suggest a Windows-first bias.
Recommendations
- Reorder the provider libraries table to group by language family or present cross-platform options (e.g., Java, Python, Go) before or alongside .NET/Windows-centric options.
- Explicitly mention the cross-platform compatibility of each provider, especially for .NET Standard and .NET Core, to clarify that they are not Windows-only.
- Add a note or section highlighting Linux and macOS support, and provide links to Linux/macOS-specific samples or documentation where relevant.
- Ensure that future documentation includes examples and troubleshooting steps for Linux environments, not just Windows or Visual Studio workflows.
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 presents environment variable setup instructions in the order of Windows CMD, PowerShell, and then macOS/Linux, which prioritizes Windows users. However, all platforms are covered and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present environment variable setup instructions in parallel (side-by-side table or grouped subsections) rather than listing Windows first.
- Consider starting with a cross-platform example (e.g., using dotenv or a Node.js script) before platform-specific instructions.
- Explicitly state that all major platforms are supported and provide equal prominence to Linux/macOS instructions.
- Where possible, use platform-agnostic language and tools in code and instructions.
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 exhibits a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric frameworks) and their samples before other cross-platform or Linux-native technologies. The table of configuration provider libraries leads with Microsoft/.NET providers, and the feature matrix columns are ordered with .NET first, followed by Java Spring, Kubernetes, and then other languages. However, there are no explicit Windows-only tools, PowerShell examples, or missing Linux examples; the bias is primarily in ordering and emphasis.
Recommendations
- Reorder the provider libraries table to alternate or group by platform type (e.g., .NET, Java, Python, JavaScript, Go) or by popularity, rather than always leading with .NET/Windows-centric frameworks.
- In the feature matrix, consider rotating the order of columns or providing a note that the order does not imply priority or platform preference.
- Explicitly mention cross-platform compatibility for each provider, especially for .NET Standard and .NET Core, to clarify that they are not Windows-only.
- If possible, add Linux-specific or cross-platform usage notes or examples where relevant, to reinforce parity.
- Ensure that documentation samples and links are balanced across platforms and not predominantly .NET/Windows.