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 51-75 of 147 flagged pages
Azure App Configuration
Create an Azure App Configuration store by using Azure Resource Manager template (ARM template)
...azure-app-configuration/quickstart-resource-manager.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides deployment instructions using PowerShell only, with no equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The only CLI command shown is for enabling public network access, but the main deployment workflow is PowerShell-only.
Recommendations
- Add Azure CLI and Bash examples for deploying the ARM template, alongside PowerShell.
- Present CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links if needed.
- Where possible, use generic commands (e.g., az group create, az deployment group create) that work across platforms.
Create Pull Request
Azure App Configuration
Azure App Configuration REST API - Microsoft Entra authorization
...e-app-configuration/rest-api-authorization-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions Azure CLI, PowerShell, and Azure portal as options for managing role assignments, but the only specific example link provided is for the Azure portal (GUI), and PowerShell is listed before CLI. There are no explicit Linux/macOS command-line examples or references, and no mention of Bash or shell scripting. The documentation does not provide parity for Linux users in terms of actionable examples or tool recommendations.
Recommendations
- Add explicit examples using Azure CLI commands for role assignment, as Azure CLI is cross-platform and preferred by Linux/macOS users.
- Provide links to documentation for both Azure CLI and PowerShell role assignment procedures.
- Mention that Azure CLI works on Linux/macOS and provide guidance for those platforms.
- Ensure that command-line examples are shown for both PowerShell and Bash/CLI where relevant.
Azure App Configuration
Export settings from App Configuration with Azure Pipelines
.../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only a PowerShell example for consuming exported key-values, without offering a Linux shell (e.g., Bash) equivalent. This may unintentionally signal a preference for Windows environments and PowerShell usage, while omitting guidance for users running pipelines on Linux agents.
Recommendations
- Add equivalent Bash (or sh) examples for accessing environment variables in subsequent tasks, e.g., `echo "$myBuildSetting"`.
- Explicitly mention that the export task works on both Windows and Linux agents, and clarify any platform-specific considerations if present.
- Where screenshots or UI instructions are platform-neutral, consider adding notes or images for Linux agent setup if relevant.
- Review troubleshooting and FAQ sections for any implicit Windows assumptions and provide Linux alternatives where appropriate.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and references Visual Studio and Windows-specific tooling (e.g., setx, F5, firewall exception) without offering equivalent Linux development workflows or tooling guidance. PowerShell and Windows command prompt examples are given more prominence and detail than bash equivalents.
Recommendations
- Present Linux/macOS (bash) instructions before or alongside Windows examples, not after.
- Include equivalent Linux development workflows, such as using VS Code, Azure Functions Core Tools CLI, or other cross-platform editors, and describe how to run and debug functions on Linux.
- Mention Linux-specific considerations (e.g., permissions, shell differences) where relevant.
- Avoid language that assumes Visual Studio or Windows as the default development environment; reference cross-platform tools and editors.
- Ensure all command-line examples are provided for bash/zsh/fish as well as Windows shells, with equal detail and troubleshooting guidance.
Azure App Configuration
Roll out features to targeted audiences in a Node.js app
...-app-configuration/howto-targetingfilter-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in the section about setting environment variables. Windows Command Prompt and PowerShell instructions are presented before Linux/macOS equivalents, and both Windows shells are given dedicated examples. No other Windows-specific tools or patterns are present, and the main Node.js/Express workflow is cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before Windows/PowerShell, or group all OS instructions together for parity.
- Consider using a table or side-by-side layout to show environment variable commands for all platforms equally.
- Explicitly state that the Node.js/Express workflow is cross-platform and works on Windows, Linux, and macOS.
- Avoid giving Windows-specific instructions more prominence than Linux/macOS unless there is a technical reason.
Azure App Configuration
Enable telemetry for feature flags in a Python application
...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Build and run the app' section, where Windows (cmd) and PowerShell commands for setting environment variables are presented before the Linux/macOS equivalent. The inclusion of both Windows and Linux/macOS commands is positive, but the ordering prioritizes Windows environments. There are no exclusive Windows tools or missing Linux examples elsewhere in the page.
Recommendations
- Present environment variable commands for Linux/macOS and Windows side-by-side or in parallel sections, rather than listing Windows first.
- Consider using tabbed or collapsible sections for platform-specific instructions to avoid implicit prioritization.
- Explicitly state that all platforms are supported and provide equal visibility to Linux/macOS instructions.
- Review other documentation pages for similar ordering and update to ensure Linux parity.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell and Windows command prompt examples. While Linux/macOS instructions are present, Windows tooling and patterns are mentioned first, and Windows command-line examples are more detailed (e.g., restart prompt note). There are no Linux-specific tools or patterns highlighted, and the overall flow assumes familiarity with Windows environments.
Recommendations
- Present Linux/macOS and Windows instructions in parallel or start with Linux/macOS to avoid implicit prioritization.
- Add notes about differences in environment variable persistence between shells (e.g., setx vs export), and clarify that Linux/macOS changes are session-scoped unless added to shell profiles.
- Include Linux/macOS-specific troubleshooting tips or common patterns (e.g., using systemd for environment variables, or .env files).
- Ensure that all command examples (curl, Maven, etc.) are shown in both Windows and Linux/macOS contexts where relevant.
- Mention cross-platform editors and tools (e.g., IntelliJ IDEA, Eclipse) alongside Visual Studio Code.
- Review images and screenshots to ensure they are not Windows-centric (e.g., Azure Portal screenshots should not show Windows-only features).
Azure App Configuration
Create an Azure App Configuration store using Bicep
...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there notes about running PowerShell on Linux or macOS. The ordering of examples does not consistently prioritize cross-platform tools (CLI) over Windows-centric ones (PowerShell).
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- List Azure CLI examples before PowerShell examples to reinforce CLI as the default, cross-platform choice.
- Add notes or tabs for Bash or other Linux-native shells if relevant.
- Mention that PowerShell Core is available on Linux/macOS, if PowerShell usage is necessary.
- Ensure all instructions and examples work seamlessly on Linux, and highlight any platform-specific considerations.
Azure App Configuration
Quickstart for using chat completion configuration in a .NET app
...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in the 'Build and run the app' section, where Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. PowerShell and Windows-specific commands are explicitly called out, while Linux/macOS instructions are present but appear after Windows examples. No Linux-specific tools or patterns are discussed elsewhere, but the .NET CLI commands and code samples themselves are cross-platform.
Recommendations
- Present environment variable instructions in a platform-neutral order (e.g., group Windows, macOS, and Linux together or list Linux/macOS first in some cases).
- Explicitly state that all .NET CLI commands and code samples work on Windows, Linux, and macOS.
- Consider providing more parity in troubleshooting or configuration steps for Linux/macOS (e.g., mention common shell environments, permissions, or differences in environment variable persistence).
- Avoid using terms like 'If you use Windows...' first; instead, use 'On Windows...', 'On macOS...', 'On Linux...' in parallel bullet points.
- Add a note clarifying that Azure App Configuration and Azure OpenAI SDKs are supported cross-platform.
Azure App Configuration
Quickstart for Azure App Configuration with .NET | Microsoft Docs
.../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setting instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the .NET CLI is emphasized as cross-platform. No major Windows-only tools or patterns are used, and Linux parity is generally maintained.
Recommendations
- Present environment variable instructions for all platforms in parallel or grouped by OS, rather than listing Windows first.
- Consider listing Linux/macOS commands before Windows, or in a neutral order, to avoid implicit prioritization.
- Add notes clarifying that all .NET CLI commands work identically on Linux/macOS.
- Where PowerShell is mentioned, clarify its availability on Linux/macOS, or provide bash equivalents if relevant.
- Ensure screenshots and terminal output examples reflect cross-platform usage, not just Windows terminals.
Azure App Configuration
Quickstart for adding feature flags to Python with Azure App Configuration
...re-app-configuration/quickstart-feature-flag-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the section about setting environment variables. Windows Command Prompt and PowerShell instructions are listed before macOS and Linux, and PowerShell is given its own tab. The Windows instructions are more detailed, including validation steps, while Linux/macOS instructions are more succinct. No Linux-specific tools or patterns are mentioned elsewhere, but the environment variable setup section prioritizes Windows.
Recommendations
- Present OS instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) rather than Windows-first.
- Ensure parity in detail and validation steps for Linux/macOS instructions, matching those given for Windows.
- Consider combining macOS and Linux instructions if they are identical, and avoid giving Windows multiple tabs unless justified.
- Explicitly state that the instructions apply equally to all platforms, and provide troubleshooting tips for Linux/macOS users where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/azure-pipeline-export-task.md
.../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides an explicit example of consuming exported key-values using PowerShell syntax only (echo "$env:myBuildSetting"). There are no equivalent examples for Linux shells (e.g., Bash), nor is there mention of cross-platform usage patterns. This may lead Linux users to feel unsupported or unsure how to access pipeline variables in their environment.
Recommendations
- Add equivalent examples for Bash (e.g., echo "$myBuildSetting" or echo "$MYBUILDSETTING") when showing how to consume pipeline variables.
- Explicitly state that pipeline variables are available as environment variables in all supported agent operating systems, including Linux and macOS.
- Where PowerShell is mentioned, also mention Bash or other common Linux shells to ensure parity.
- Consider adding a table or section with cross-platform usage patterns for accessing pipeline variables.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/concept-preview-api-life-cycle.md
...re-app-configuration/concept-preview-api-life-cycle.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for checking API versions, but PowerShell is given equal prominence, which may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, and Windows/PowerShell is presented as a primary alternative to Bash. No Linux examples are missing, but the inclusion of PowerShell may prioritize Windows users.
Recommendations
- Ensure that Bash examples are presented first, as Bash is the default shell on most Linux systems.
- Consider adding examples for other common Linux shells (e.g., zsh) or scripting languages (e.g., Python) where relevant.
- Clarify in the documentation which examples are intended for Linux/macOS and which for Windows, to help users choose the appropriate commands.
- If PowerShell is included, note that PowerShell Core is cross-platform, but specify if the example is Windows-specific.
- Include troubleshooting tips or notes for Linux users, such as package installation or environment setup, to improve parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium 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), and provides detailed steps for Visual Studio (a Windows-centric tool) including F5 debugging and firewall exception notes. PowerShell and Windows command prompt examples are given equal or greater prominence than bash, and Visual Studio is assumed as the primary local development environment.
Recommendations
- Present Linux/macOS (bash) instructions before or alongside Windows instructions, rather than after.
- Include instructions for cross-platform editors and tools, such as VS Code or Azure Functions Core Tools CLI, not just Visual Studio.
- Add notes for Linux/macOS users regarding local testing, such as using 'func start' from Azure Functions Core Tools.
- Avoid assuming Visual Studio as the default; mention alternatives for Linux/macOS users.
- Ensure that all command examples (environment variable setup, local testing) are given equal prominence for Linux/macOS and Windows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md
...ration/enable-dynamic-configuration-java-spring-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by providing command-line examples using the Windows-style 'cmd' prompt and syntax (e.g., 'curl -X GET http://localhost:8080/' under a 'cmd' code block), without offering equivalent Linux or macOS shell examples. There is no mention of Linux-specific tools, nor are Linux shell commands (such as Bash) shown. The Azure Portal instructions are platform-neutral, but the command-line testing section implicitly prioritizes Windows.
Recommendations
- Provide both Windows (cmd/PowerShell) and Linux/macOS (Bash/sh) command-line examples for testing the application, e.g., show 'curl' usage in a Bash shell.
- Use generic shell code blocks (e.g., 'shell' or 'bash') for commands that work cross-platform, or explicitly show both variants if there are differences.
- Include a note clarifying that the commands work on Linux/macOS as well, and mention any platform-specific considerations if relevant.
- Ensure that documentation does not assume a Windows environment by default, especially for Java/Spring Boot applications which are commonly deployed on Linux.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-python.md
...p-configuration/enable-dynamic-configuration-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific Python setup documentation in the prerequisites and omitting explicit Linux or macOS setup guidance. No Linux/macOS command-line examples or platform-specific notes are provided, and the only external setup link is for Windows.
Recommendations
- Add links or instructions for setting up Python on Linux and macOS alongside the Windows documentation link.
- Include platform-agnostic or platform-specific notes for environment variable setup and running Python scripts (e.g., differences in shell syntax).
- Explicitly mention that the examples work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
- Ensure parity in CLI instructions, such as referencing both Bash and PowerShell where relevant.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-background-service.md
...enable-dynamic-configuration-dotnet-background-service.md
Medium 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 Linux/macOS equivalents. Windows-specific tools (cmd, PowerShell) are listed first, and PowerShell commands are included, which can reinforce a Windows-centric approach. However, Linux/macOS instructions are present and the .NET CLI is emphasized as cross-platform.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Group environment variable setup commands by platform, or use tabs to allow users to select their OS.
- Explicitly state cross-platform compatibility at the start of relevant sections.
- Include screenshots or examples from Linux/macOS terminals as well as Windows.
- Avoid giving Windows instructions (cmd, PowerShell) priority in ordering unless there is a user base justification.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-app-configuration-event.md
...ure-app-configuration/howto-app-configuration-event.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses Azure CLI for all examples, which is cross-platform, but it subtly assumes a Windows-first perspective by referencing the Azure Cloud Shell and local CLI installation without mentioning Linux-specific considerations or shell differences. There are no explicit Linux shell examples (e.g., bash vs. PowerShell), and no mention of Linux-specific tools or troubleshooting steps. All command-line examples use a syntax compatible with bash but do not clarify shell compatibility, which may confuse users on Windows using PowerShell or CMD.
Recommendations
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and clarify any shell-specific syntax (e.g., variable assignment differences between bash and PowerShell).
- Provide parallel examples or notes for PowerShell and bash where syntax differs, or link to documentation explaining these differences.
- Mention Linux and macOS as supported platforms for the Azure CLI, and provide installation links for all platforms.
- Add troubleshooting tips or notes for common issues on Linux (e.g., permissions, path issues) and clarify that the Cloud Shell is available in both bash and PowerShell flavors.
- Where environment variables are used (e.g., $sitename), clarify that this syntax is for bash and provide the equivalent for PowerShell if needed.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-chat-completion-config.md
...zure-app-configuration/howto-chat-completion-config.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions primarily through the Azure Portal UI and does not include any explicit command-line examples. Where command-line options are referenced, it generically mentions 'the CLI' without specifying or providing examples for either Windows (PowerShell/Command Prompt) or Linux (Bash). There are no Linux-specific instructions, nor is there parity in showing how to perform tasks using Bash or cross-platform CLI tools. The ordering and language imply a Windows-first approach, as is common in Azure documentation, and there is a lack of Linux or cross-platform command-line examples.
Recommendations
- Add explicit CLI examples for both Windows (PowerShell) and Linux (Bash) where relevant, such as using Azure CLI commands to create and manage chat completion configurations.
- When referencing the CLI, specify the commands for both Windows and Linux environments, or clarify that the Azure CLI is cross-platform and provide examples in Bash.
- Include screenshots or terminal outputs from Linux environments where applicable.
- Ensure that any references to tools or workflows (such as Key Vault references or adding key-values) are demonstrated with cross-platform parity, not just through the Azure Portal UI.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-feature-filters-aspnet-core.md
...app-configuration/howto-feature-filters-aspnet-core.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions and examples that are platform-neutral in terms of .NET Core usage, but it implicitly assumes a Windows or Windows-first development environment by not mentioning Linux or macOS explicitly. All command-line instructions use dotnet CLI, which is cross-platform, but there are no notes or examples for Linux users (e.g., shell commands, environment differences, or screenshots from non-Windows systems). The browser screenshots and folder navigation instructions also implicitly reflect a Windows-centric workflow.
Recommendations
- Explicitly state that the instructions work on Windows, Linux, and macOS, and mention any platform-specific prerequisites if applicable.
- Include example shell commands (e.g., using bash) or clarify that the dotnet CLI commands are cross-platform.
- Add screenshots or notes that reflect running the application on Linux (e.g., terminal output, browser screenshots showing localhost on Linux).
- Mention common Linux development patterns, such as using VS Code on Linux, or navigating directories with Linux commands.
- If any step is platform-specific (such as file paths or environment variable configuration), provide Linux/macOS equivalents.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-labels-aspnet-core.md
...es/azure-app-configuration/howto-labels-aspnet-core.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates per-environment configuration using Azure App Configuration in the context of an ASP.NET Core app. It references modifying 'launchSettings.json' and uses .NET CLI commands, but does not provide Linux-specific instructions or examples (e.g., setting environment variables via bash or running the app outside Visual Studio/Windows-centric workflows). The workflow assumes a Windows/Visual Studio development environment, with no mention of Linux or cross-platform alternatives.
Recommendations
- Add instructions for setting environment variables on Linux/macOS (e.g., using 'export ASPNETCORE_ENVIRONMENT=Production' in bash).
- Mention how to run the app and set environment variables outside of 'launchSettings.json', which is specific to Visual Studio/Windows workflows.
- Include a note or section for developers using Linux or macOS, highlighting any differences or additional steps.
- Provide equivalent bash/zsh shell commands alongside .NET CLI examples where applicable.
- Clarify that the instructions apply to all platforms supported by .NET, and explicitly mention cross-platform compatibility.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows and PowerShell commands are listed first, which may suggest a prioritization of Windows users. However, Linux/macOS instructions are present and correct, and the rest of the tutorial is platform-neutral.
Recommendations
- Present environment variable setup instructions for all platforms together, or list Linux/macOS first to balance historical bias.
- Consider grouping platform-specific commands in a table or side-by-side format for parity.
- Explicitly state that the tutorial is cross-platform and works equally well on Linux/macOS and Windows.
- Add a note that the Python code and Azure services are platform-independent.
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
Medium 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 method. Windows-specific commands (setx, PowerShell syntax) are described in detail, with Linux/macOS covered last and more briefly. No Linux-specific tools or patterns are discussed elsewhere, but the environment variable section demonstrates a 'windows_first' and 'powershell_heavy' bias.
Recommendations
- Present environment variable instructions for Linux/macOS first or in parallel with Windows, to avoid implying Windows is the primary platform.
- Include more detailed Linux/macOS instructions, such as how to persist environment variables across sessions (e.g., editing .bashrc/.zshrc), not just the export command.
- Consider grouping all platform-specific instructions together and using clear headings for each OS, so users can quickly find relevant information.
- If possible, provide parity in troubleshooting steps and screenshots for Linux/macOS users, not just Windows.
- Review other sections for subtle Windows-centric language or assumptions, and ensure examples and terminology are inclusive of all major platforms.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry.md
...in/articles/azure-app-configuration/howto-telemetry.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI and Application Insights, which are typically accessed via a web browser on any OS, but does not provide any command-line or automation examples. There are no references to Linux-specific tools, CLI commands, or automation via Bash or cross-platform scripting. No PowerShell or Windows-specific tools are directly mentioned, but the lack of parity for Linux/CLI users is evident.
Recommendations
- Add Azure CLI and/or Azure PowerShell command examples for enabling telemetry and managing feature flags, ensuring both Windows and Linux users can automate these tasks.
- Include examples or references for interacting with Azure App Configuration and Application Insights via REST API or SDKs, which are cross-platform.
- Provide guidance for headless or automated environments (e.g., CI/CD pipelines) where portal access is not practical.
- Explicitly mention that all portal steps are OS-agnostic, and offer alternative instructions for users who prefer or require command-line or script-based workflows.
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
Medium 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 command prompt and PowerShell commands are listed first, with Linux/macOS only mentioned afterwards. This ordering and explicit inclusion of PowerShell and setx (Windows-specific tools) demonstrate a subtle Windows-first and PowerShell-heavy bias.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Use tabbed or collapsible sections for platform-specific instructions to avoid implicit prioritization.
- Explicitly mention that all platforms are supported and provide equal detail for each.
- Consider using cross-platform tools (e.g., cross-env for npm scripts) in examples where possible.
- Add troubleshooting notes for platform-specific issues, if any, for parity.