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
474 issues found
Showing 101-125 of 474 flagged pages
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-app.md
...icles/azure-app-configuration/quickstart-dotnet-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows tools (Visual Studio, Command Prompt, PowerShell) in both prerequisites and step-by-step instructions. Environment variable setting instructions list Windows methods (cmd, PowerShell) before Linux/macOS (bash), and the overall workflow assumes Visual Studio as the development environment, which is primarily Windows-based. There are no Linux-specific development environment suggestions or parity in tooling guidance.
Recommendations
- Present environment variable setting instructions in a neutral or rotating order (e.g., Linux/macOS, then Windows, or all at once in a table).
- Include alternative development environment instructions for Linux (e.g., using VS Code, JetBrains Rider, or MonoDevelop).
- Clarify that .NET Framework is Windows-only, but suggest .NET (Core/5+) for cross-platform scenarios, and link to equivalent cross-platform guides.
- Where possible, provide CLI-based project creation steps (e.g., using dotnet CLI) for users on non-Windows platforms.
- Explicitly state any Windows-only requirements at the top, and offer links to cross-platform alternatives for similar functionality.
Create Pull Request
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-azure-functions-csharp.md
...tion/quickstart-feature-flag-azure-functions-csharp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and all instructions for creating and running the Azure Functions app are centered around it. In environment variable setup, Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. The use of Visual Studio tooling and references to Windows-specific patterns (like setx and F5 debugging) further reinforce this bias. There are no Linux-specific development environment suggestions or CLI-based workflows for cross-platform parity.
Recommendations
- Include instructions for creating and running Azure Functions apps using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Present Linux/macOS and Windows instructions in parallel or in a neutral order, rather than always listing Windows first.
- Provide examples for setting environment variables and running/debugging the function using Bash and cross-platform tools, not just Windows command prompt, PowerShell, and Visual Studio.
- Mention and link to cross-platform development environments and workflows, such as using VS Code or JetBrains Rider.
- Clarify that Visual Studio is not required and that the process can be completed on Linux/macOS with appropriate tools.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md
...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively referencing Windows tools (Visual Studio, Windows command prompt, PowerShell) for setup and environment configuration. There are no instructions or examples for Linux or macOS users, such as using Bash or cross-platform editors. The order and presence of Windows-specific instructions, without Linux equivalents, may hinder non-Windows developers.
Recommendations
- Add equivalent instructions for setting environment variables on Linux (e.g., export ConnectionString=...) and macOS.
- Include examples using cross-platform editors or .NET CLI (e.g., dotnet new console) instead of only Visual Studio.
- Present setup instructions for both Windows and Linux/macOS, or use tabbed sections to separate platform-specific steps.
- Reference cross-platform terminal commands (e.g., Bash) alongside Windows Command Prompt and PowerShell.
- Clarify that the .NET SDK and Azure App Configuration are cross-platform, and provide links or notes for non-Windows users.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-resource-manager.md
...azure-app-configuration/quickstart-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing deployment instructions and examples exclusively using PowerShell cmdlets, which are native to Windows environments. There are no equivalent examples using cross-platform tools such as Azure CLI or Bash scripts, and no explicit mention of Linux or macOS workflows. The only command-line example for enabling public network access uses Azure CLI, but the main deployment workflow is Windows/PowerShell-centric. The order of presentation and tooling assumes a Windows-first audience.
Recommendations
- Add equivalent deployment instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Provide Bash script examples for deploying ARM templates to Azure, alongside PowerShell.
- Explicitly mention that the instructions apply to all platforms and provide guidance for Linux/macOS users.
- Where PowerShell is used, offer a side-by-side or alternative example using Azure CLI.
- Review the documentation for other places where Windows tools or patterns are assumed, and ensure Linux parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-python.md
...re-app-configuration/quickstart-feature-flag-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In the prerequisites, Windows-specific Python setup is mentioned first, and the environment variable setup instructions prioritize Windows command prompt and PowerShell before macOS and Linux. Windows tools (setx, PowerShell) are described in more detail, and validation steps are more explicit for Windows. While Linux/macOS instructions are present, they appear after Windows and are less detailed.
Recommendations
- Present environment variable setup instructions in a more platform-neutral order, or group them together with clear tabs for each OS.
- Give equal detail and validation steps for Linux/macOS as for Windows (e.g., show how to check environment variables on Unix systems).
- In prerequisites, mention Python setup for all platforms equally, or link to cross-platform instructions before platform-specific ones.
- Avoid describing Windows tools (like setx) in more detail than their Unix equivalents; ensure parity in command explanations.
- Consider using a table or tabbed interface for OS-specific commands to avoid implicit prioritization.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-java-spring-app.md
.../azure-app-configuration/quickstart-java-spring-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows command-line instructions (setx, PowerShell) before Linux/macOS equivalents, using Windows-specific tools and syntax, and labeling the Linux/macOS example as an afterthought. The primary build/run instructions use generic commands, but environment variable setup is Windows-centric.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel sections, rather than listing Windows first and Linux/macOS last.
- Use neutral or cross-platform shell syntax (e.g., POSIX-compliant export) where possible, or clearly separate platform-specific instructions.
- Avoid using Windows-specific tools (like setx) as the default; instead, provide equivalent instructions for all platforms.
- Explicitly mention that all major platforms are supported and tested.
- Consider using tabs or collapsible sections for platform-specific instructions to improve clarity and parity.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides instructions for monitoring Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. While the Azure CLI section is cross-platform, the PowerShell section is Windows-centric and explicitly references 'Windows PowerShell'. Additionally, in the CLI instructions, Windows PowerShell is mentioned as an example of a command console application before other platforms. No Linux/macOS-specific shell examples (e.g., Bash) are provided, and PowerShell is given a dedicated tab, which may suggest a Windows-first approach.
Recommendations
- In CLI instructions, mention Bash or other Linux/macOS shells alongside Windows PowerShell when referring to command consoles.
- Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and provide example commands in Bash where relevant.
- For PowerShell instructions, note that PowerShell Core is available cross-platform, and provide guidance for Linux/macOS users if applicable.
- Consider adding explicit Bash examples or notes for Linux/macOS users to ensure parity and reduce friction.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS (export), and uses Windows-specific commands (setx, PowerShell syntax) with only a brief Linux/macOS example. The Windows instructions are more detailed (mentioning restart of command prompt), while the Linux/macOS instructions are minimal and lack equivalent detail. There are no screenshots or step-by-step UI instructions that are OS-specific, but the CLI and environment variable setup sections show a clear Windows-first bias.
Recommendations
- Present Linux/macOS and Windows environment variable instructions side-by-side or in tabs, giving equal prominence and detail.
- For each command, provide both Windows (cmd, PowerShell) and Linux/macOS (bash/zsh) equivalents, with notes about session persistence (e.g., setx vs export).
- Clarify that 'export' only sets variables for the current shell session, and suggest adding to ~/.bashrc or ~/.zshrc for persistence, mirroring the Windows 'setx' behavior.
- Add Linux/macOS-specific screenshots or notes where relevant, or explicitly state when steps are identical across platforms.
- Consider using cross-platform tools (like Azure CLI) for all automation steps, and avoid assuming a Windows shell as default.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides monitoring instructions for Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. While the Azure CLI section is platform-neutral, the PowerShell section is Windows-specific and is presented as a main option. Additionally, in the Azure CLI instructions, Windows PowerShell is mentioned as a typical command console application, which may imply Windows as the default environment. Linux/macOS equivalents (such as Bash or Terminal) are not mentioned, and PowerShell examples are not flagged as Windows-only, potentially creating friction for non-Windows users.
Recommendations
- Explicitly mention Bash/Terminal as alternatives to Windows PowerShell for Azure CLI usage.
- Clarify that PowerShell instructions are Windows-specific and provide guidance for Linux/macOS users (e.g., using Azure CLI or PowerShell Core if supported).
- Ensure that CLI instructions are presented as the default cross-platform option, with PowerShell as an additional, Windows-specific alternative.
- Add notes or links for Linux/macOS users where relevant, especially in sections referencing Windows tools.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides monitoring instructions for Azure App Configuration using the Azure Portal, Azure CLI, and PowerShell. While the Azure CLI section is cross-platform, the PowerShell section is Windows-centric and explicitly instructs users to open a Windows PowerShell command window. Additionally, in the CLI section, Windows PowerShell is mentioned as an example of a command console application before any Linux/macOS alternatives. No Linux/macOS-specific instructions or terminal examples are provided, and PowerShell is presented as a primary scripting option, which may create friction for Linux/macOS users.
Recommendations
- In the Azure CLI section, clarify that CLI commands can be run from any terminal on Windows, Linux, or macOS, not just Windows PowerShell.
- In the PowerShell section, note that PowerShell Core is available cross-platform and provide instructions for Linux/macOS users, or explicitly state that this section is Windows-specific.
- Add example terminal instructions for Linux/macOS users (e.g., 'Open a terminal on Linux/macOS').
- Consider mentioning Bash or other common Linux/macOS shells as alternatives for running Azure CLI commands.
- Review screenshots and UI references to ensure they are not Windows-specific unless necessary.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page lists configuration provider libraries for multiple languages and platforms, but .NET and ASP.NET Core (Windows-centric technologies) are presented first in all tables and examples. All .NET sample links point to repositories and samples that are typically Windows-oriented (.NET Framework, ASP.NET Core), with no explicit mention of Linux/macOS compatibility or equivalent Linux-first examples. There is no discussion of Linux-specific configuration patterns, nor are Linux/macOS usage scenarios highlighted. The page implicitly prioritizes Windows/.NET technologies, which may create friction for Linux/macOS users.
Recommendations
- Add explicit notes or sections clarifying cross-platform compatibility for .NET Core and ASP.NET Core libraries, including Linux/macOS usage.
- Provide sample links or code snippets demonstrating usage on Linux/macOS environments (e.g., running .NET Core on Ubuntu, using Python/Go/JavaScript providers on Linux).
- Reorder the provider library tables to alternate or group by platform/language rather than always listing Windows-centric technologies first.
- Include references to Linux/macOS configuration patterns or tools where relevant.
- Ensure that documentation samples and guides are not exclusively Windows/PowerShell-based, and provide Bash or Linux shell equivalents where appropriate.
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, with no equivalent example for Bash or other Linux/macOS shells. This may create friction for users running pipelines on Linux or macOS agents, as they must infer how to access environment variables in their preferred shell.
Recommendations
- Add Bash and/or sh examples for accessing environment variables, e.g., `echo "$myBuildSetting"`.
- Explicitly mention that environment variables are accessible in all supported agent operating systems and provide cross-platform usage guidance.
- Where PowerShell is referenced, clarify that similar steps apply for other shells and link to relevant documentation.
Azure App Configuration
Quickstart for adding feature flags to Azure Functions | Microsoft Docs
...tion/quickstart-feature-flag-azure-functions-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Visual Studio Only
Missing Linux Example
Summary
The documentation prioritizes Windows tooling and workflows, especially Visual Studio, and presents Windows command-line examples (cmd, PowerShell) before Linux/macOS equivalents. There is no mention of cross-platform editors (e.g., VS Code) or CLI-based workflows for Linux/macOS users. Critical steps like project creation and debugging are described only with Visual Studio, which is primarily a Windows tool.
Recommendations
- Add instructions for creating and running Azure Functions projects using cross-platform tools such as Visual Studio Code and Azure Functions Core Tools CLI.
- Present Linux/macOS shell commands before or alongside Windows commands, rather than after.
- Include screenshots and workflow steps for Linux/macOS environments, not just Visual Studio on Windows.
- Clarify that Visual Studio is optional and provide parity for non-Windows users.
- Explicitly mention and link to platform-agnostic development guides.
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
Missing Linux Example
Windows Tools
Summary
The documentation provides deployment instructions using PowerShell only, with no equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users who do not use PowerShell, and may not have it installed. The only command-line example for enabling public network access uses Azure CLI, but the main deployment workflow is PowerShell-centric.
Recommendations
- Add Azure CLI and Bash examples for deploying the ARM template and cleaning up resources.
- Present Azure CLI examples before or alongside PowerShell examples to ensure platform parity.
- Explicitly mention that the PowerShell instructions are for Windows users, and provide guidance for Linux/macOS users.
- Consider including a table or section comparing PowerShell and Azure CLI workflows.
Azure App Configuration
Quickstart for Adding Feature Flags to .NET/.NET Framework Apps
...re-app-configuration/quickstart-feature-flag-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a notable Windows bias. All environment variable setup instructions use Windows Command Prompt and PowerShell, with no mention of Linux/macOS equivalents (e.g., Bash, export commands). Visual Studio is listed as the only IDE, and all screenshots and workflow steps assume a Windows environment. There are no instructions for Linux/macOS users on setting environment variables or using alternative development tools.
Recommendations
- Add equivalent instructions for setting environment variables on Linux/macOS (e.g., export Endpoint=..., export ConnectionString=...)
- Mention cross-platform IDEs such as VS Code or JetBrains Rider, or clarify that Visual Studio is optional if using the .NET CLI
- Include screenshots or notes for running the app in Linux/macOS terminals
- Add a section or callouts for Linux/macOS users, especially for environment setup and running the app
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page displays a notable Windows/.NET bias: the configuration provider libraries table lists .NET Standard, ASP.NET Core, Azure Functions, and .NET Framework providers first, with their samples and release notes, before mentioning Java, Python, JavaScript, and Go. The only sample for .NET Framework links to a 'WebDemo', which is typically Windows/IIS-centric, and there is no explicit mention of Linux or cross-platform usage for .NET. There are no Linux-specific examples, nor is there guidance for running .NET providers on Linux or macOS. The documentation does not mention Powershell or Windows tools directly, but the ordering and sample selection favor Windows-first development patterns.
Recommendations
- Add explicit examples or notes for running .NET providers on Linux and macOS (e.g., using .NET Core on Ubuntu).
- Include Linux/macOS sample projects or usage instructions for each provider, especially for .NET and ASP.NET Core.
- Reorder the provider table to alternate or group by language/platform rather than listing all .NET/Windows-centric providers first.
- Provide parity in sample applications, ensuring that non-Windows platforms are equally represented.
- Clarify that the .NET Standard and ASP.NET Core providers are cross-platform and provide links to documentation for Linux/macOS deployment.
Azure App Configuration
Quickstart for Azure App Configuration with Aspire
.../articles/azure-app-configuration/quickstart-aspire.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation consistently references Docker Desktop as the container runtime, which is a Windows/macOS-specific tool, and does not mention Linux alternatives (e.g., Docker Engine, Podman). Additionally, Docker Desktop is mentioned first and exclusively when instructing users to start their container runtime, suggesting a Windows/macOS-centric approach. There are no explicit PowerShell-only examples, but the overall tooling guidance leans toward Windows/macOS environments.
Recommendations
- Mention Linux-native container runtimes (e.g., Docker Engine, Podman) alongside Docker Desktop when discussing prerequisites and steps for running containers.
- Provide explicit instructions or notes for Linux users on how to start their container runtime and verify containers are running.
- Where screenshots or UI references are given (e.g., Docker Desktop), consider including CLI alternatives or Linux-specific screenshots.
- Clarify that all steps are cross-platform and provide troubleshooting tips for common Linux issues (e.g., permissions, service management).
Azure App Configuration
.NET Framework: dynamic configuration in App Configuration
...p-configuration/enable-dynamic-configuration-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. Visual Studio is listed as the only IDE in prerequisites, and instructions for creating and running the app are tailored to Windows workflows (Visual Studio, Command Prompt, PowerShell). Environment variable setup instructions consistently list Windows methods (setx, PowerShell) before Linux/macOS (bash export). Screenshots and run instructions reference Windows terminals. No Linux/macOS IDEs or development workflows are mentioned.
Recommendations
- Include instructions for using cross-platform IDEs such as VS Code, JetBrains Rider, or CLI-based workflows.
- Present environment variable setup commands for Linux/macOS before or alongside Windows commands, not after.
- Add screenshots or terminal output examples for Linux/macOS.
- Clarify that .NET Framework apps can be developed and run on Windows only, but .NET Core/.NET 5+ equivalents are cross-platform and link to those tutorials.
- Explicitly mention limitations for Linux/macOS users (e.g., Visual Studio requirement, .NET Framework platform support) and suggest alternatives where possible.
Azure App Configuration
Integrate Azure App Configuration with Kubernetes Deployment using Helm
...-configuration/integrate-kubernetes-deployment-helm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a PowerShell script for passing secrets to Helm using the --set argument, but does not offer an equivalent Bash/Linux shell example. The PowerShell example is presented as the only method for dynamic key-value injection, which may create friction for Linux/macOS users. Additionally, the use of PowerShell is introduced without mentioning cross-platform alternatives, and Windows-centric tooling appears first in the dynamic example section.
Recommendations
- Provide a Bash/Linux shell example for passing secrets to Helm using the --set argument, using jq or similar tools to process JSON output from Azure CLI.
- Clearly indicate that the PowerShell example is for Windows and offer a cross-platform alternative immediately after.
- Where possible, use cross-platform scripting in examples, or explicitly provide both Windows (PowerShell) and Linux/macOS (Bash) variants.
- Add a note about the cross-platform nature of Azure CLI and Helm, and clarify that scripting approaches may differ by OS.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given its own dedicated section, and Windows PowerShell is mentioned explicitly as a command console example before alternatives. The CLI section suggests using Windows PowerShell as a console, and the PowerShell section assumes use of Windows. There are no explicit Linux/macOS examples or terminal instructions, and no mention of Bash or other cross-platform shells.
Recommendations
- In the Azure CLI section, mention Bash or other cross-platform shells as alternatives to Windows PowerShell for running CLI commands.
- In the PowerShell section, clarify that PowerShell Core is cross-platform and provide guidance for Linux/macOS users (e.g., how to install and run PowerShell on those platforms).
- Add explicit Linux/macOS instructions or notes where relevant, especially for opening terminals and running commands.
- Avoid suggesting Windows PowerShell as the default console for CLI usage; instead, use neutral language like 'open a terminal or command prompt'.
- Where screenshots or UI elements are shown, ensure they are not Windows-specific unless unavoidable.
Azure App Configuration
Quickstart for Azure App Configuration with Azure Functions | Microsoft Docs
...app-configuration/quickstart-azure-functions-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio (Windows-centric) is the only development environment mentioned, and all instructions for creating and running the Azure Functions app are tailored to Visual Studio. When setting environment variables, Windows command prompt and PowerShell examples are presented before Linux/macOS bash commands. There is no mention of cross-platform editors (e.g., VS Code) or Linux/macOS-specific development workflows. The documentation assumes the use of Windows tools and patterns throughout, which may create friction for Linux/macOS users.
Recommendations
- Add instructions for creating and running Azure Functions apps using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Present environment variable examples for Linux/macOS before or alongside Windows examples, not after.
- Include explicit guidance for Linux/macOS users on installing prerequisites and running/debugging the function locally.
- Reference cross-platform development workflows and tools where possible, rather than assuming Visual Studio on Windows.
- Clarify that all code and configuration steps are applicable on Linux/macOS, and note any platform-specific differences.
Azure App Configuration
Quickstart for Azure App Configuration with .NET Framework
...icles/azure-app-configuration/quickstart-dotnet-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Visual Studio, Command Prompt, PowerShell) are referenced first and exclusively in the prerequisites and setup steps. Examples for setting environment variables are shown for Windows Command Prompt and PowerShell before Linux/macOS equivalents. The workflow assumes Visual Studio, which is primarily a Windows tool, and does not mention cross-platform alternatives (e.g., VS Code, JetBrains Rider). The .NET Framework itself is Windows-only, but the documentation could better acknowledge Linux/macOS developer workflows for related tasks (such as environment variable setup and editor choice).
Recommendations
- Explicitly state that .NET Framework is Windows-only and suggest .NET Core/.NET for cross-platform scenarios.
- Mention cross-platform editors like Visual Studio Code or JetBrains Rider as alternatives to Visual Studio.
- Present Linux/macOS commands for environment variable setup before or alongside Windows examples, not after.
- Clarify which steps are Windows-specific and provide guidance for Linux/macOS users where applicable (e.g., using Mono for .NET Framework apps, if relevant).
- Add a note for Linux/macOS users about limitations and alternatives for .NET Framework development.
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
Missing Linux Example
Summary
The documentation shows a Windows-first bias in the environment variable setup section, presenting Windows Command Prompt and PowerShell instructions before macOS and Linux. The Windows instructions are more detailed, with explicit validation steps, while Linux/macOS instructions are less emphasized. There is also a reference to Windows-specific Python setup documentation, with only a generic link for other platforms. No Linux-specific tools or troubleshooting are mentioned, and the overall flow prioritizes Windows users.
Recommendations
- Present environment variable setup instructions for all platforms with equal detail and prominence, possibly starting with a generic cross-platform example.
- Provide validation steps for environment variables on Linux/macOS (e.g., 'echo $APP_CONFIGURATION_ENDPOINT') as is done for Windows.
- Include a link to Python installation/setup documentation for Linux and macOS, not just Windows.
- Consider grouping platform instructions together or using tabs that do not default to Windows.
- Mention any platform-specific caveats or troubleshooting steps for Linux/macOS users.
Azure App Configuration
Quickstart for using Azure App Configuration with Python apps | Microsoft Learn
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and the only link for Python installation is for Windows. While Linux/macOS commands are present, they are consistently listed last, and there is no guidance for installing Python on Linux/macOS. This ordering and omission may create friction for non-Windows users.
Recommendations
- Provide links or brief instructions for installing Python on Linux and macOS in the prerequisites section.
- Alternate the order of environment variable instructions, or present all OS options in parallel (e.g., in a table or side-by-side tabs).
- Ensure that any referenced tooling or setup steps (such as Python installation) are covered for all major platforms, not just Windows.
- Consider using neutral, cross-platform language and examples where possible.
Azure App Configuration
Integrate Azure App Configuration with Kubernetes Deployment using Helm
...-configuration/integrate-kubernetes-deployment-helm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a PowerShell script for passing secrets to Helm, without offering an equivalent Bash/Linux shell example. The only explicit scripting example for dynamic key-value passing uses PowerShell syntax, which is Windows-centric. There is no mention of Linux/macOS alternatives, and the PowerShell example is presented without context or parity for other platforms.
Recommendations
- Provide a Bash (Linux/macOS) equivalent script for the PowerShell example, using common tools like jq or awk for JSON parsing.
- Explicitly mention that the PowerShell example is for Windows and offer cross-platform alternatives.
- Ensure scripting examples are provided for both Windows and Linux/macOS users, or use platform-neutral commands where possible.
- Add a note clarifying platform compatibility for all CLI and scripting examples.