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 376-400 of 479 flagged pages
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists .NET-based provider libraries first in all tables and examples, with .NET Standard, ASP.NET Core, Azure Functions, and .NET Framework appearing before Java, Python, JavaScript, and Go. While the content covers cross-platform libraries and does not provide Windows-only instructions or tools, the ordering and emphasis may subtly prioritize Windows/.NET users.
Recommendations
- Reorder the provider libraries table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than listing all .NET options first.
- Explicitly mention that .NET Standard and .NET Core are cross-platform and supported on Linux/macOS as well as Windows.
- Add a brief note clarifying that all listed libraries (except .NET Framework) are intended for cross-platform use.
- Consider rotating the order of examples or highlighting non-.NET samples in introductory sections.
Create Pull Request
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists .NET-based (Microsoft-centric) libraries and examples first in all tables, with Windows-oriented platforms (.NET Standard, ASP.NET Core, .NET Framework) leading before Java, Python, JavaScript, and Go. However, the content covers cross-platform libraries and provides parity for Linux/macOS users, with samples and release notes for all major languages and platforms.
Recommendations
- Consider rotating or randomizing the order of provider libraries in tables, or grouping by platform type (e.g., Microsoft/.NET, JVM, Python, JavaScript, Go) to avoid implicit prioritization.
- Explicitly mention cross-platform compatibility for .NET Standard and ASP.NET Core providers, clarifying that they work on Linux/macOS as well as Windows.
- Add a brief note at the top stating that all listed libraries are supported on Linux and macOS unless otherwise specified.
- Where possible, provide direct links to Linux/macOS-specific usage guides or samples for .NET and other providers.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists .NET-based configuration providers first in all tables and feature matrices, with .NET Standard, ASP.NET Core, and .NET Framework libraries preceding Java, Python, JavaScript, and Go. However, the content covers cross-platform libraries and provides parity in feature tracking and sample links for all major languages, including Linux-friendly stacks. There are no Windows-specific tools, PowerShell examples, or exclusive references to Windows patterns.
Recommendations
- Consider rotating the order of provider libraries in tables or grouping by language family (e.g., statically typed, dynamically typed) to avoid implicit prioritization of Windows/.NET.
- Explicitly mention cross-platform compatibility for .NET Standard and ASP.NET Core providers, clarifying that they run on Linux/macOS as well as Windows.
- Add a brief note that all listed providers (except .NET Framework) are supported on Linux/macOS, to reassure non-Windows users.
- Ensure that future examples and sample links include Linux/macOS usage instructions where relevant.
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
Powershell Heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning Linux/macOS (bash), and references Windows-specific Python setup documentation in prerequisites. However, Linux/macOS instructions are present and complete, so Linux users can follow along without major issues.
Recommendations
- Present environment variable instructions for all platforms in parallel or in a table, rather than listing Windows first.
- Add a link to Python installation/setup documentation for Linux/macOS alongside the Windows link in prerequisites.
- Consider using generic cross-platform instructions or clarify that all major platforms are supported.
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 Command Prompt and PowerShell before mentioning the macOS/Linux equivalent. All other code and instructions are cross-platform, and Linux/macOS users are not blocked from completing the tutorial.
Recommendations
- Present environment variable setup instructions for macOS/Linux before or alongside Windows instructions.
- Consider grouping all OS-specific instructions together and labeling them clearly.
- Explicitly state that all code examples work on Linux/macOS unless otherwise noted.
Azure App Configuration
Use variant feature flags in a Node.js application
...onfiguration/howto-variant-feature-flags-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt, PowerShell, and then macOS/Linux, listing Windows methods first and giving both cmd and PowerShell examples. Linux/macOS instructions are present and correct, but appear after Windows examples, which may subtly prioritize Windows users.
Recommendations
- Present environment variable instructions for all platforms in parallel or grouped by OS family, not with Windows first.
- Consider listing Linux/macOS instructions before or alongside Windows, or use tabs to let users select their OS.
- Ensure parity in troubleshooting or tool references if any are added in future revisions.
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 demonstrates a mild Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell is explicitly called out, and Windows-specific tools (setx) are mentioned. However, Linux/macOS instructions are present and complete, and the rest of the guide is platform-neutral.
Recommendations
- Present environment variable instructions in a platform-neutral order (e.g., Linux/macOS first or side-by-side).
- Consider grouping all OS instructions in a table or tabs for equal visibility.
- Add a note clarifying that all steps work equally on Linux/macOS and Windows.
- Where Windows-specific tools (e.g., setx) are mentioned, briefly explain Linux/macOS equivalents (e.g., .bashrc, .zshrc for persistent variables).
Azure App Configuration
Azure App Configuration REST API - Microsoft Entra authorization
...e-app-configuration/rest-api-authorization-azure-ad.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure CLI, PowerShell, and the Azure portal for managing role assignments, but lists PowerShell before CLI and does not provide explicit Linux/macOS examples or guidance. The mention of PowerShell and the Azure portal (both Windows-centric tools) before CLI may subtly prioritize Windows workflows. There are no command-line examples, but the order and tool emphasis suggest a mild Windows bias.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands for role assignment using Azure CLI.
- Include Linux/macOS-specific notes or examples where relevant.
- List Azure CLI before PowerShell when describing cross-platform procedures.
- Clarify that the Azure portal is web-based and accessible from any OS.
Azure App Configuration
Azure App Configuration preview API life cycle
...re-app-configuration/concept-preview-api-life-cycle.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for checking API versions, but PowerShell is presented second, and both examples use the Azure CLI, which is cross-platform. There is a slight Windows bias in including a PowerShell example, but Linux users are not disadvantaged, as Bash examples are present and shown first. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
- Continue to provide Bash examples first for command-line instructions.
- Consider clarifying that PowerShell examples are for Windows users, and Bash for Linux/macOS.
- Explicitly mention cross-platform compatibility of Azure CLI.
- If possible, add macOS-specific notes if there are any platform caveats.
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 presented first in each section, with screenshots and example outputs shown in Windows Command Prompt. All platforms are covered, but Windows is prioritized in ordering and visuals.
Recommendations
- Rotate or randomize the order of platform-specific instructions so Linux/macOS are sometimes shown first.
- Include screenshots or example outputs from Linux/macOS terminals alongside Windows Command Prompt.
- Explicitly state that all instructions are equivalent across platforms to reassure non-Windows users.
- Consider grouping Unix-like platforms (Linux/macOS) together for brevity and clarity.
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 includes explicit Visual Studio/Windows tooling references (e.g., setx, PowerShell, Visual Studio prompts). Linux/macOS instructions are present but are listed after Windows examples, and there is a slight emphasis on Windows-centric development environments.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Include CLI-based instructions that work cross-platform (e.g., Azure Functions Core Tools usage from terminal) and mention VS Code as an alternative to Visual Studio for non-Windows users.
- Clarify that Azure Functions Core Tools are available on all platforms and provide installation/testing steps for Linux/macOS.
- Avoid language that assumes Visual Studio is the default development environment; mention alternatives for Linux/macOS users.
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), and includes both Windows command prompt and PowerShell examples. However, Linux/macOS instructions are present and not omitted. The .NET CLI is promoted as cross-platform, and no Windows-only tools or patterns are required.
Recommendations
- Present Linux/macOS (bash) instructions before or alongside Windows examples to avoid implicit prioritization.
- Reduce the emphasis on Windows-specific shells (cmd, PowerShell) by grouping all OS instructions together or using tabs.
- Explicitly state cross-platform compatibility in relevant sections to reassure non-Windows users.
- Consider adding screenshots or output examples from Linux/macOS terminals, not just Windows.
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
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the Linux/macOS equivalent. Screenshots and refresh instructions reference Windows terminals (Command Prompt/PowerShell) specifically, and the example workflow implicitly centers on Windows usage patterns. However, Linux/macOS instructions are present and accurate.
Recommendations
- Present environment variable setup instructions for all platforms in parallel or start with a cross-platform example (e.g., bash first, then Windows).
- Include screenshots or explicit references to Linux/macOS terminals (e.g., Terminal.app, GNOME Terminal) alongside Windows examples.
- When describing steps that involve the terminal, use neutral language (e.g., 'your terminal window') instead of 'Command Prompt or PowerShell window.'
- Ensure parity in troubleshooting and logging instructions for Linux/macOS environments.
- Consider adding a note or section on platform-specific differences, if any, for .NET development.
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 commands (setx) and PowerShell examples. However, Linux/macOS equivalents are present and clearly marked. The order and prominence of Windows instructions may create minor friction for non-Windows users, but all critical steps are covered for Linux/macOS.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than listing Windows first.
- Use neutral language and avoid implying Windows is the default platform.
- Add explicit notes that all steps are cross-platform unless otherwise stated.
- Consider using generic shell commands (where possible) before platform-specific ones.
- Where tools like Visual Studio Code are mentioned, clarify cross-platform support up front.
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 Linux/macOS (bash). All platforms are covered, but Windows commands are shown first, which may subtly prioritize Windows users.
Recommendations
- Present environment variable setup instructions for Linux/macOS first or in parallel with Windows.
- Consider grouping platform-specific instructions together under clear subheadings (e.g., 'Windows', 'Linux/macOS').
- Ensure equal prominence and clarity for Linux/macOS instructions throughout the documentation.
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 displays a mild Windows bias: Windows command prompt and PowerShell instructions are listed before macOS and Linux equivalents, and Windows-specific tools (Visual Studio Code, MSBuild) are mentioned. However, Linux/macOS instructions are present, and the Azure CLI is cross-platform.
Recommendations
- Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or alphabetical).
- Explicitly mention that MSBuild and .csproj scripts work cross-platform with .NET Core SDK.
- Add notes clarifying that Visual Studio Code and Azure CLI are available on all platforms.
- Where possible, provide examples or notes for common Linux/macOS build tools or shell environments.
- Ensure screenshots and file path examples use platform-neutral or platform-specific variants as appropriate.
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 equivalent, but all code and tooling is cross-platform Node.js and does not rely on Windows-specific tools or patterns.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions for setting environment variables.
- Explicitly state that all steps are cross-platform except where noted.
- Consider grouping OS-specific instructions together, or using tabs for platform selection.
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 Linux/macOS equivalent. All other code and instructions are cross-platform and do not show Windows-specific bias.
Recommendations
- Present environment variable setup commands for all platforms together, or list Linux/macOS first to avoid implicit prioritization of Windows.
- Consider grouping platform-specific instructions under clear subheadings (e.g., 'Windows', 'Linux/macOS') for parity.
- Explicitly state that all code samples are platform-agnostic unless otherwise noted.
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
Powershell Heavy
Summary
The documentation displays a mild Windows bias in the 'Prerequisites' and 'Build and run the app' sections. Windows setup instructions (including links and commands) are presented first, with PowerShell and Command Prompt examples given before Linux/macOS equivalents. The virtual environment activation example uses Windows syntax only, omitting the Linux/macOS alternative.
Recommendations
- Provide Linux/macOS setup instructions and links alongside Windows, not after.
- Show both Windows and Linux/macOS commands for activating Python virtual environments (e.g., 'source venv/bin/activate' for Linux/macOS).
- Alternate the order of platform instructions or present them in parallel tables or tabs.
- Ensure all CLI examples include both Windows and Linux/macOS syntax where they differ.
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 instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows-specific commands (setx, PowerShell syntax) are presented first, with Linux/macOS bash instructions given last. The rest of the guide is cross-platform, as .NET Core and Azure SDKs are supported on all major OSes.
Recommendations
- Present environment variable instructions for Linux/macOS and Windows side-by-side, or in parallel sections, rather than listing Windows first.
- Explicitly state that all steps are cross-platform and .NET Core works on Linux/macOS.
- Provide troubleshooting notes for common Linux/macOS issues (e.g., shell differences, permissions).
- Include sample terminal output for Linux/macOS users, not just Windows.
- Avoid using Windows-centric terminology like 'command prompt' without also mentioning 'terminal' for Linux/macOS.
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 environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Windows-specific installation guidance for Node.js in the prerequisites. However, all code samples and main workflow are cross-platform and do not rely on Windows-only tools or patterns.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions for environment variable setup.
- Include a direct link to Node.js installation instructions for Linux/macOS in the prerequisites, not just Windows.
- Consider grouping OS instructions in a tabbed format to avoid implicit prioritization.
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 tools (setx, PowerShell syntax) are mentioned first, with Linux/macOS instructions given after. All code samples for the Go app itself are cross-platform, but the ordering and emphasis in setup steps show a mild Windows bias.
Recommendations
- Present environment variable setup instructions for Linux/macOS and Windows side-by-side or in parallel lists, rather than listing Windows first.
- Consider using a table or tabs for platform-specific commands to avoid implicit prioritization.
- Explicitly state that all Go code and Azure SDK usage is cross-platform, and highlight any OS-specific caveats if present.
- If possible, provide parity in troubleshooting or tips for all platforms (e.g., how to check environment variables on Linux/macOS).
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 parity is generally maintained throughout the page.
Recommendations
- Present Linux/macOS (bash) instructions before or alongside Windows examples to avoid implicit prioritization.
- Consider grouping environment variable instructions by OS, or using tabs for each platform to improve clarity and parity.
- Add a note at the start of environment variable sections indicating that all major platforms are supported.
- Ensure that any screenshots or terminal images are not Windows-specific, or provide equivalents for Linux/macOS.
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 complete, but appear after Windows examples, which may create minor friction for non-Windows users.
Recommendations
- Present Linux/macOS (bash) instructions before Windows examples, as Go developers are often cross-platform.
- Group environment variable setup instructions by OS, or use tabs to allow users to select their platform.
- Ensure parity in all command examples and avoid giving Windows instructions priority in ordering.
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 and CLI usage are cross-platform. No Windows-only tools or patterns are used, and Linux users can complete all steps.
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 parity.
- Ensure that CLI and code examples remain cross-platform and avoid Windows-centric language.
- Add a note clarifying that all steps work on Linux/macOS and Windows equally.