Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 301-325 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/managed-identity.md
...//articles/automation/troubleshoot/managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Connect-AzureRMAccount) and PowerShell scripting for troubleshooting and examples. There are no examples or guidance for Linux-based automation, Bash, Azure CLI, or cross-platform scripting. The troubleshooting steps and error messages are all tailored to Windows-centric tools and workflows, potentially excluding Linux users or those using non-PowerShell environments.
Recommendations
- Add equivalent troubleshooting steps and examples using Azure CLI (az) commands and Bash scripts, especially for authentication and role assignment scenarios.
- Include sample error messages and resolutions that might be encountered when running runbooks on Linux Hybrid Runbook Workers.
- Explicitly mention that the guidance applies to both Windows and Linux automation environments, or clarify any platform-specific limitations.
- Provide links to cross-platform documentation or best practices for using managed identities in Linux-based automation.
- Ensure that all code samples are available in both PowerShell and Bash/Azure CLI where possible.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/shared-resources/variables.md
...ain//articles/automation/shared-resources/variables.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples use Windows PowerShell and Az PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native scripting. The internal cmdlets and runbook examples are PowerShell-centric. The only alternative shown is Python, but there are no examples or guidance for Linux shell users or for using Azure CLI. Windows tools and terminology (e.g., 'Windows PowerShell', 'Windows Hybrid Runbook Worker') are referenced exclusively or before any cross-platform alternatives.
Recommendations
- Add equivalent examples using Azure CLI (az automation variable ...) for variable management, which works cross-platform.
- Include Bash or shell script examples for Linux users, especially for common tasks like creating, retrieving, and updating variables.
- When referencing PowerShell, clarify that Az PowerShell modules are available cross-platform, and provide explicit instructions for Linux/macOS environments.
- Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' unless specifically referring to Windows-only features.
- Mention and provide guidance for running runbooks on Linux Hybrid Runbook Workers, not just Windows.
- Ensure that references to tools and workflows are not Windows-first; present cross-platform options in parallel or with equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-troubleshoot-remote-desktop-connectivity.md
...box/how-to-troubleshoot-remote-desktop-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias: all troubleshooting steps, error messages, and solutions are specific to Windows environments. Only Windows tools (e.g., Hyper-V, Windows Hello, certutil, Windows Update, Windows Settings) and PowerShell commands are mentioned. There are no Linux or cross-platform examples, nor any mention of Linux/Mac clients or dev boxes, despite Remote Desktop being available on multiple platforms.
Recommendations
- Include troubleshooting steps and examples for Linux and macOS clients connecting to dev boxes, such as using rdesktop, Remmina, or FreeRDP.
- Mention equivalent Linux tools or commands where possible (e.g., how to check network connectivity, manage certificates, or troubleshoot display issues on Linux).
- Clarify whether the dev boxes are exclusively Windows-based or if Linux dev boxes are supported; if so, provide parity in troubleshooting guidance.
- When describing issues like network latency, display problems, or Teams integration, offer platform-agnostic advice or note any platform-specific differences.
- If PowerShell or Windows-specific commands are required, provide analogous commands or steps for Linux/macOS environments where feasible.
- Reorganize sections to avoid always presenting Windows solutions first, or clearly label sections as Windows-specific and provide Linux/macOS equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/desired-state-configuration.md
...automation/troubleshoot/desired-state-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a strong Windows and PowerShell bias. Troubleshooting steps, examples, and tools are almost exclusively described in terms of PowerShell cmdlets and Windows-centric workflows. Linux is only mentioned in passing or in a single scenario, with no equivalent Linux commands, logs, or troubleshooting steps provided. Windows tools and patterns (such as xDscDiagnostics, WMI, and PowerShell DSC cmdlets) are referenced throughout, while Linux alternatives are omitted or relegated to a single section.
Recommendations
- Provide Linux-specific troubleshooting steps and examples alongside Windows/PowerShell instructions, especially for log collection, agent registration, and error resolution.
- Include Linux command-line equivalents (e.g., shell commands, log file paths, systemd interactions) wherever PowerShell cmdlets are referenced.
- Mention Linux tools and diagnostic patterns (such as journalctl, /var/log/messages, or OMSAgent logs) in relevant troubleshooting sections.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first or Windows-only.
- Where features are deprecated or limited for Linux, clearly state this at the top and provide links to Linux-specific guidance or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/shared-resources/schedules.md
...ain//articles/automation/shared-resources/schedules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets (Az modules), which are native to Windows and only more recently available on other platforms. There are no examples using Azure CLI, Bash, or other Linux-native tools. The documentation refers exclusively to PowerShell for scripting and automation, and the structure of the page presents PowerShell options before any mention of cross-platform alternatives. This approach may alienate Linux users or those who prefer non-PowerShell workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that PowerShell Core and Az modules are available on Linux/macOS, and provide installation guidance or links.
- Where possible, provide Bash script examples or note how to use REST API calls for schedule management.
- Reorganize sections so that cross-platform tools (Azure CLI, REST API) are presented alongside or before Windows-centric tools.
- Include a table or section comparing PowerShell and Azure CLI commands for common schedule management tasks.
- Clarify in the introduction that all examples are cross-platform where applicable, or clearly label those that are Windows-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/hybrid-runbook-worker.md
...icles/automation/troubleshoot/hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows troubleshooting steps and examples are often presented first or in greater detail, especially in the initial sections. Many examples and resolutions rely on Windows-specific tools (such as PowerShell, Windows Event Logs, registry edits, and Windows file paths), with Linux equivalents either omitted or relegated to later sections. Some scenarios provide detailed PowerShell scripts for Windows but lack equivalent Linux shell commands or troubleshooting steps. Linux troubleshooting is grouped into a separate section, which may make it less discoverable and less comprehensive compared to the Windows coverage.
Recommendations
- For every Windows-specific example (e.g., PowerShell commands, registry edits, file paths), provide equivalent Linux commands (e.g., Bash scripts, Linux file paths, configuration file locations) alongside or immediately after the Windows instructions.
- Present Windows and Linux troubleshooting steps in parallel for each scenario, rather than grouping them into separate sections. This improves parity and discoverability.
- Where Windows Event Logs are referenced, provide the equivalent Linux log file locations (e.g., /var/log/...) and commands (e.g., journalctl, tail, grep) for troubleshooting.
- Avoid assuming PowerShell as the default scripting environment; offer Bash or Python examples for Linux where automation or scripting is discussed.
- Ensure that all configuration file changes or workarounds (such as editing Orchestrator.Sandbox.exe.config) have Linux analogs or explicitly state if not applicable.
- Review all scenarios for completeness: if a scenario applies to both Windows and Linux, ensure both are covered with equal detail and actionable steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/shared-resources/modules.md
.../main//articles/automation/shared-resources/modules.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell modules and Windows-centric workflows. All code examples and module management instructions are provided using PowerShell cmdlets, with no equivalent Bash, CLI, or Linux-native examples. Internal cmdlets and features such as Orchestrator.AssetManagement.Cmdlets are only available on Windows Hybrid Runbook Workers, with Linux support explicitly excluded. The documentation repeatedly references Windows PowerShell versions and features, and there is no guidance or parity for Linux users or those using non-PowerShell environments.
Recommendations
- Provide equivalent examples and workflows using Azure CLI and/or Bash scripts for managing modules, especially for Linux Hybrid Runbook Workers.
- Clearly indicate which features are Windows-only and offer alternative approaches for Linux environments where possible.
- Include a section or table summarizing feature parity and limitations between Windows and Linux Hybrid Runbook Workers.
- Add guidance or links for managing Python modules and runbooks on Linux, not just PowerShell.
- When introducing tools or patterns (e.g., module import, runbook testing), present cross-platform options or explicitly mention Linux alternatives.
- Update language to avoid assuming PowerShell as the default or only automation environment, and highlight support for other scripting languages where available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/runbooks.md
...lob/main//articles/automation/troubleshoot/runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on PowerShell-based automation, with all code examples and troubleshooting steps using PowerShell cmdlets and modules (e.g., Az.Automation, Get-AzVM, Connect-AzAccount). There is no mention of Linux-specific tools, shell environments, or examples using Bash, Azure CLI, or Python (except for a brief mention of Python runbooks in one error message). Windows/PowerShell patterns and tools are presented exclusively, with no Linux or cross-platform parity.
Recommendations
- Add equivalent troubleshooting steps and code examples for Linux environments, such as using Bash scripts or Azure CLI commands.
- Include Python runbook examples and troubleshooting guidance, especially since Python is supported in Azure Automation.
- Clearly indicate when a solution or workaround is PowerShell-specific, and provide alternatives for Linux users where possible.
- Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and provide guidance for both environments.
- Mention any platform-specific limitations or differences in behavior between Windows and Linux Hybrid Runbook Workers.
- Where PowerShell modules are referenced, note if they are available on PowerShell Core (cross-platform) or only on Windows PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/runbook-input-parameters.md
.../main//articles/automation/runbook-input-parameters.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with detailed examples, screenshots, and step-by-step guides for PowerShell and graphical (PowerShell-based) runbooks. Linux-native workflows, tools, or shell examples are absent. Python runbooks are mentioned but only briefly, with no parity in example depth or workflow coverage. There are no Bash, CLI, or Linux-specific examples or guidance, and all automation examples use Windows/PowerShell conventions and tools.
Recommendations
- Add equivalent examples for starting and managing runbooks using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Provide Bash shell examples for passing parameters to runbooks, including how to invoke runbooks and handle JSON input from Linux environments.
- Expand the Python runbook section to include detailed parameter handling, input examples, and end-to-end workflows similar to the PowerShell sections.
- Include notes or sections on how Linux users can authenticate, manage files, and interact with Azure Automation from non-Windows environments.
- Balance screenshots and walkthroughs to include Linux terminal/CLI usage, not just PowerShell and graphical editors.
- Mention and link to documentation for Linux tools and workflows wherever Windows/PowerShell tools are referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/whats-new.md
...azure-docs/blob/main//articles/automation/whats-new.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows and PowerShell bias. Most automation and scripting examples, feature announcements, and tooling references focus on PowerShell (a Windows-centric technology) and Windows environments. PowerShell runbooks are consistently mentioned before Python runbooks, and there is an emphasis on PowerShell version updates. Azure CLI support is highlighted only in the context of PowerShell runbooks, not as standalone Bash or Linux-native automation. References to tools and extensions (such as Visual Studio Code integration) are also primarily described in the context of PowerShell. There are few, if any, Linux- or Bash-specific examples, and Linux parity is often implied rather than explicitly demonstrated.
Recommendations
- Provide equal prominence to Python and Bash runbooks alongside PowerShell in all feature announcements and examples.
- Include explicit Linux/Bash scripting examples and scenarios, not just PowerShell or Windows-centric workflows.
- When introducing new features (e.g., runtime environments, CLI support), clarify support and usage for Linux-native tools and shells.
- Reference Linux and Windows platforms equally when discussing hybrid worker support, migration, and deprecation notices.
- Highlight cross-platform capabilities and provide guidance for both Windows and Linux users in tooling and extension documentation.
- Ensure that documentation updates and new features are illustrated with both PowerShell and Python/Bash sample scripts where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/shared-resources.md
...//articles/automation/troubleshoot/shared-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All troubleshooting examples and resolutions are provided exclusively in PowerShell, with no mention of Linux, Bash, or cross-platform alternatives. Windows-specific tools, cmdlets, and DLLs are referenced throughout, and there is no guidance for users operating from Linux environments or using non-PowerShell automation. The documentation assumes the user is familiar with Windows patterns and tools, and does not provide parity for Linux users.
Recommendations
- Provide equivalent troubleshooting steps and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Include Bash script examples alongside PowerShell for common tasks such as module management and authentication.
- Mention any differences or limitations when using Azure Automation from Linux environments, and offer guidance for those scenarios.
- Reference Linux-specific error messages or issues where applicable, and provide resolutions for those cases.
- Avoid assuming PowerShell as the default shell; clarify when steps are Windows-specific and offer alternatives for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/tutorial-configure-servers-desired-state.md
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows and PowerShell, providing only Windows-based examples (such as installing IIS via WindowsFeature) and exclusively using PowerShell cmdlets for all tasks. Prerequisites and walkthroughs reference Windows VMs and Windows-specific tools first or exclusively, with no Linux configuration examples or equivalent Linux tooling mentioned. Although there is a brief mention of Linux support and a retirement announcement, the actual tutorial content does not address Linux scenarios.
Recommendations
- Add parallel Linux examples throughout the tutorial, such as configuring a Linux VM to install and manage packages (e.g., using the nx package resource in DSC to install nginx or apache).
- Include Linux VM creation and onboarding steps in the prerequisites and walkthrough, referencing the appropriate Azure documentation for Linux VMs.
- Demonstrate the use of cross-platform DSC resources and configurations, and clarify any differences or limitations for Linux nodes.
- Reference Linux command-line tools (such as Bash or Azure CLI) where appropriate, or provide equivalent scripts for Linux environments.
- Clearly indicate in each section whether the steps apply to Windows, Linux, or both, and provide links to Linux-specific documentation if full parity is not possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md
.../troubleshoot/extension-based-hybrid-runbook-worker.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Windows Registry Focus
Windows Event Log Focus
Summary
The documentation generally provides parity between Windows and Linux in terms of troubleshooting steps, file locations, and commands. However, there is a subtle but consistent Windows bias: Windows examples and tools are often listed first, Windows-specific tools (like PowerShell scripts, registry edits, and event logs) are described in detail, and some troubleshooting scenarios are only described for Windows or are more detailed for Windows than for Linux. There is also a heavier reliance on Windows concepts such as registry keys and event logs, with less equivalent Linux guidance (e.g., syslog or journalctl usage).
Recommendations
- Alternate the order in which Windows and Linux instructions are presented, or group them together to avoid always listing Windows first.
- Where Windows event logs are referenced (e.g., Microsoft-SMA event logs), provide equivalent Linux log file locations and commands (such as journalctl or syslog paths).
- For PowerShell-heavy instructions, provide equivalent Bash or Python commands for Linux where possible.
- Where registry edits are described for Windows, clarify if there are equivalent configuration files or settings for Linux, or explicitly state if not applicable.
- Expand Linux troubleshooting scenarios to match the detail given for Windows, especially for error codes, log analysis, and permission issues.
- When referencing Windows-specific tools or patterns (like .ps1 scripts), ensure Linux equivalents (such as .sh or .py scripts) are equally documented and described.
- Add more Linux-specific troubleshooting tips, such as using systemctl, checking permissions with ls -l, or inspecting logs with tail/grep/journalctl.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/enable-dynamic-configuration-aspnet-netfx.md
...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias. Visual Studio (Windows-only) is the only IDE mentioned for development, and all project creation steps assume a Windows GUI workflow. Environment variable setup instructions list Windows Command Prompt and PowerShell before Linux/macOS, and restarting Visual Studio is required, which is not cross-platform. There are no instructions for developing or running the sample on Linux (e.g., with Mono), and no mention of cross-platform editors like VS Code.
Recommendations
- Include instructions for setting up and running the application on Linux using Mono or .NET Framework alternatives, or clarify that the tutorial is Windows-only if that is the case.
- Mention cross-platform editors such as Visual Studio Code and provide CLI-based project creation steps where possible.
- Present environment variable setup instructions for Windows, Linux, and macOS in parallel, not with Windows first.
- If Visual Studio is required, explicitly state that the tutorial targets Windows and suggest alternatives for Linux users.
- Add notes or links for Linux/macOS users regarding any limitations or alternative approaches.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/quickstart-get-started-template.md
...n//articles/dev-box/quickstart-get-started-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based licensing (Windows 11/10 Enterprise), using a Windows-based image for dev box creation, and omitting any mention of Linux or cross-platform development environments. There are no examples or guidance for setting up or using Linux-based dev boxes, nor are Linux tools or workflows referenced.
Recommendations
- Include examples or instructions for configuring dev boxes with Linux-based images, if supported by the platform.
- Mention the availability (or lack thereof) of Linux dev box images and clarify platform support early in the documentation.
- Provide parity in guidance for Linux users, such as how to select a Linux image, connect to a Linux dev box, and manage it using common Linux tools.
- If Linux is not supported, explicitly state this to set expectations for cross-platform users.
- Reference cross-platform or Linux-specific tools and workflows where applicable, not just Windows-centric ones.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally aims for cross-platform parity, but there is a subtle Windows bias. In the environment variable setup section, Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. PowerShell and Windows command prompt commands are given with more detail (e.g., mentioning the need to restart the command prompt after setx), and PowerShell is called out specifically. There is also mention of Visual Studio as an alternative to the .NET CLI, which is a Windows-centric tool, though the CLI is recommended. No Linux-specific tools or patterns are discussed, and screenshots are only of the console, not OS-specific, but the overall flow assumes familiarity with Windows environments.
Recommendations
- Alternate the order of environment variable instructions, sometimes listing Linux/macOS first to avoid reinforcing a Windows-first perspective.
- Provide equal detail for Linux/macOS instructions (e.g., mention if a new terminal session is needed for export to take effect).
- Explicitly mention cross-platform editors (e.g., VS Code) alongside Visual Studio.
- Add a note clarifying that all .NET CLI commands work identically on Linux/macOS and Windows.
- Where possible, include screenshots or terminal output from both Windows and Linux/macOS environments.
- Consider including troubleshooting tips for Linux/macOS users, such as shell differences or permission issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/overview-what-is-microsoft-dev-box.md
...articles/dev-box/overview-what-is-microsoft-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page for Microsoft Dev Box demonstrates a Windows-centric bias. It references Windows-specific management tools (Intune), focuses on keeping 'Windows devices' up to date, and only mentions Windows-based scenarios and tools. There are no examples or mentions of Linux-based dev boxes, Linux management tools, or cross-platform development workflows. The documentation assumes Windows as the default environment, omitting Linux equivalents or guidance.
Recommendations
- Explicitly mention support for Linux-based dev boxes if available, and provide examples of configuring and managing Linux dev boxes.
- Include references to Linux management tools (such as Azure Arc, SSH, or Linux configuration management) alongside Windows tools like Intune.
- Provide parity in examples and scenarios, ensuring both Windows and Linux developer workflows are described.
- Clarify whether Dev Box supports non-Windows OS images, and if so, link to relevant documentation for those platforms.
- Avoid language that assumes all dev boxes are Windows devices; use more inclusive phrasing such as 'dev boxes' or 'virtual machines' where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/quickstart-configure-dev-box-arm-template.md
...s/dev-box/quickstart-configure-dev-box-arm-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell/PowerShell-based deployment instructions and code samples, with no equivalent Bash or Linux shell examples. The step-by-step deployment section exclusively uses PowerShell and references Azure Cloud Shell in a way that assumes familiarity with Windows tooling. While Azure CLI is mentioned, no CLI or Bash examples are actually provided. There are no Linux-specific instructions or parity in the walkthrough.
Recommendations
- Add equivalent deployment instructions and code samples using Azure CLI in Bash (Linux/macOS) syntax, not just PowerShell.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide both options in the documentation.
- Reorder or parallelize instructions so that Linux/Bash examples are given equal prominence to PowerShell/Windows examples.
- Where tools or commands are referenced (e.g., 'Copy', 'Paste', 'Right-click'), clarify how these actions are performed in both Windows and Linux environments.
- Consider including screenshots or terminal snippets from both Windows and Linux environments to reinforce cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/integrate-ci-cd-pipeline.md
...es/azure-app-configuration/integrate-ci-cd-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a Windows-first bias, particularly in the ordering and emphasis of examples for setting environment variables. Windows command prompt and PowerShell instructions are presented before macOS and Linux, and PowerShell is given its own dedicated section. The build script example uses Windows-style path separators (\) in the MSBuild XML, which may not work on Linux/macOS. Visual Studio Code is mentioned as cross-platform, but the primary application example is for ASP.NET Core, which is more common on Windows. There are no Linux-specific troubleshooting notes or parity checks for the build script.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or alternate the order to avoid always listing Windows first.
- Provide explicit notes or examples for Linux/macOS path separators in the MSBuild script (e.g., use $(OutDir)/azureappconfig.json or document cross-platform compatibility).
- Include troubleshooting tips or caveats for running the build and export steps on Linux/macOS, especially regarding file paths and shell differences.
- Ensure that all CLI and scripting examples are tested and confirmed to work on Linux and macOS, not just Windows.
- Consider adding a non-Windows-centric application example (such as a .NET app running on Linux) to demonstrate true cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/monitor-app-configuration.md
...s/azure-app-configuration/monitor-app-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. In the Azure CLI section, Windows PowerShell is mentioned as the example terminal, and in the PowerShell section, only Windows PowerShell is referenced, with no mention of cross-platform PowerShell Core or Linux/macOS equivalents. There are no explicit Linux or macOS instructions or screenshots, and the documentation does not mention alternative shells (e.g., Bash) or terminal environments. This may make it less accessible or intuitive for Linux/macOS users.
Recommendations
- In CLI instructions, mention both Windows PowerShell and Bash (or other common Linux/macOS shells) as valid environments for running Azure CLI commands.
- In the PowerShell section, clarify whether the instructions are compatible with PowerShell Core (pwsh), which is cross-platform, and provide guidance for Linux/macOS users if so.
- Add explicit examples or notes for Linux/macOS users, including how to open a terminal and run the same commands.
- Avoid phrases like 'Open a Windows PowerShell command window' in favor of more inclusive language such as 'Open your preferred terminal or command prompt.'
- Include screenshots or references that are not specific to Windows UI where possible, or provide alternatives for other platforms.
- Consider adding a dedicated section or callout for Linux/macOS users to ensure parity and clarity.
Azure Docs
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
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing on Visual Studio (Windows-only), .NET Framework (primarily Windows), and providing Windows command prompt and PowerShell instructions before Linux/macOS equivalents. Linux/macOS instructions are present but always listed last, and there are no examples or guidance for developing or running the app outside Windows (e.g., with Mono or .NET Core on Linux). All tooling and project setup assumes a Windows environment.
Recommendations
- Provide equal prominence to Linux/macOS instructions, listing them alongside or before Windows examples where appropriate.
- Include guidance for setting up and running the sample app on Linux (e.g., using Mono or .NET Core if possible), or explicitly state Windows-only limitations.
- Mention and provide alternatives to Visual Studio, such as Visual Studio Code or JetBrains Rider, which are cross-platform.
- Clarify which steps are Windows-specific and which are cross-platform.
- If the .NET Framework sample cannot run on Linux, suggest .NET (Core/5+) alternatives and link to relevant documentation.
Azure Docs
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 demonstrates a Windows bias by exclusively referencing Windows tools (Visual Studio, Windows command prompt, PowerShell) and providing only Windows-specific instructions for setting environment variables and running the application. There are no Linux or cross-platform alternatives mentioned for these steps, and the instructions assume the use of Windows throughout the quickstart.
Recommendations
- Add equivalent instructions for Linux and macOS users, such as using the 'export' command in bash/zsh to set environment variables.
- Mention and provide examples for using cross-platform editors like VS Code or the 'dotnet' CLI for project creation and management.
- Reorder or parallelize instructions so that Windows and Linux/macOS steps are presented equally, rather than Windows-first.
- Clarify that the .NET SDK and Azure App Configuration are cross-platform, and provide guidance for non-Windows environments.
- Include screenshots or terminal output examples from Linux/macOS where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-azure-functions-csharp.md
...app-configuration/quickstart-azure-functions-csharp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and all project creation and debugging instructions are tailored for Visual Studio users. In the environment variable setup section, Windows Command Prompt and PowerShell instructions are listed before Linux/macOS equivalents. There is also a reliance on Windows-specific tools and workflows (e.g., 'Press F5', Visual Studio dialogs, and screenshots). Linux and cross-platform alternatives (such as VS Code, Azure Functions Core Tools CLI, or dotnet CLI) are not mentioned, and no Linux-specific troubleshooting or development guidance is provided.
Recommendations
- Add instructions for creating and running Azure Functions projects using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Include Linux/macOS commands before or alongside Windows commands when setting environment variables, to avoid Windows-first ordering.
- Provide guidance for users developing on Linux/macOS, including screenshots and steps for those environments.
- Mention and link to cross-platform development workflows (e.g., using dotnet CLI, VS Code, or JetBrains Rider) in the prerequisites and throughout the quickstart.
- Clarify that Visual Studio is optional and highlight alternative editors and tools for non-Windows users.
Azure Docs
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
Visual Studio Only
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by centering the workflow around Visual Studio (a Windows-centric IDE), mentioning Windows tools and patterns before Linux/macOS equivalents, and providing detailed instructions for Windows command prompt and PowerShell before bash. There is no mention of cross-platform editors like VS Code or CLI-based workflows, and the requirement for Visual Studio excludes native Linux development environments.
Recommendations
- Add instructions for creating and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Present environment variable setting commands for Linux/macOS before or alongside Windows commands, rather than always listing Windows first.
- Include explicit guidance for Linux users regarding installation and use of required tools (e.g., .NET SDK, Azure Functions Core Tools) outside of Visual Studio.
- Clarify that Visual Studio is not required and provide alternative steps for users on Linux or macOS.
- Ensure screenshots and workflow descriptions are not exclusively tied to Visual Studio or Windows UI elements.
Azure Docs
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 mild Windows bias. In the prerequisites, Windows-specific Python setup documentation is mentioned before the general Python download link. In the environment variable setup section, Windows Command Prompt and PowerShell instructions are presented before macOS and Linux, with more detailed validation steps for Windows. The use of 'setx' and PowerShell environment variable syntax are Windows-specific tools and patterns, while Unix/Linux instructions are present but less emphasized.
Recommendations
- Present environment variable setup instructions for all platforms in parallel tabs or in a consistent order (e.g., alphabetical or with no clear priority).
- Provide equal detail and validation steps for Linux/macOS as for Windows (e.g., show how to check the variable in Unix shells).
- In the prerequisites, mention Python setup for all platforms equally, or link to the official Python documentation for all OSes before platform-specific guides.
- Avoid using Windows-specific tools (like 'setx') without providing equivalent Linux/macOS commands (e.g., adding to ~/.bashrc or ~/.zshrc for persistence).
- Ensure screenshots and examples are cross-platform or clarify when they are platform-specific.