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 401-425 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-scenario-database-table-cleanup.md
...functions/functions-scenario-database-table-cleanup.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all steps, referencing Windows-specific UI and workflows, and omitting any mention or examples for Linux or cross-platform development environments. There are no instructions for using VS Code, CLI tools, or other editors common on Linux. The process for setting app settings, installing packages, and running/debugging the function is described only via Visual Studio's GUI, with no CLI or platform-agnostic alternatives.
Recommendations
- Add equivalent instructions for Linux users, such as using Visual Studio Code or the Azure Functions Core Tools CLI for project creation, configuration, and publishing.
- Provide examples for setting application settings and connection strings using the Azure CLI or Azure Portal, not just through Visual Studio.
- Include steps for installing NuGet packages via the dotnet CLI (e.g., 'dotnet add package Microsoft.Data.SqlClient') rather than only through Visual Studio's GUI.
- Describe how to run and debug the function locally using the Azure Functions Core Tools and VS Code, including relevant commands.
- Ensure screenshots and UI references are either cross-platform or supplemented with text-based/CLI alternatives.
- Explicitly mention that the steps are applicable to both Windows and Linux, and note any platform-specific differences.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-versions.md
...b/main//articles/azure-functions/functions-versions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Visual Studio, .csproj, .NET Framework) and workflows before or instead of Linux alternatives. There are no explicit Linux or cross-platform command-line examples, and guidance for Linux users is limited or absent. The process for pinning to a minor version mentions that it differs between Windows and Linux, but only links to another page rather than providing parity in examples or instructions.
Recommendations
- Provide explicit Linux and macOS examples alongside Windows/Visual Studio instructions, especially for local development and configuration.
- Include Azure CLI and cross-platform command-line instructions for tasks such as changing runtime versions, in addition to Visual Studio workflows.
- When referencing differences between Windows and Linux (e.g., pinning to a minor version), summarize both approaches directly in the documentation rather than only linking out.
- Highlight cross-platform tools (such as Azure Functions Core Tools) earlier and more prominently, and ensure all examples are shown for both Windows and Linux environments.
- Avoid assuming Visual Studio or .NET Framework as the default development environment; mention VS Code and CLI-based workflows with equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-concepts.md
...ob/main//articles/devtest-labs/devtest-lab-concepts.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows virtual machines and tools before or instead of Linux equivalents. The only direct VM reference links to 'Windows virtual machines in Azure', and artifact/tool examples (e.g., Visual Studio, Fiddler) are Windows-centric. There are no explicit Linux VM or tool examples, nor links to Linux VM documentation.
Recommendations
- Include references and links to both Windows and Linux virtual machines in Azure when discussing VM concepts.
- Provide examples of artifacts/tools relevant to Linux environments (e.g., Git, Apache, NGINX) alongside Windows tools.
- Ensure that documentation and example links for creating and managing VMs, custom images, and formulas mention both Windows and Linux scenarios.
- Balance the order of presentation so that Linux is mentioned alongside or before Windows where appropriate.
- Add a section or note clarifying support for both Windows and Linux VMs in DevTest Labs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-reference-java.md
...//articles/azure-functions/functions-reference-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides both Bash and Windows CMD examples for command-line operations, but Windows CMD examples are consistently presented alongside or immediately after Bash, sometimes with more detail. There is a notable lack of Linux-specific guidance or troubleshooting, and some sections (such as Java version support) list Windows before Linux, with more detailed notes for Windows. There are no PowerShell-specific examples, but the overall pattern is to treat Windows as a primary or default environment, with Linux as a secondary consideration. There are no Linux-only tools or patterns highlighted, and Linux troubleshooting or nuances are not discussed.
Recommendations
- Wherever command-line examples are given, ensure Bash (Linux/macOS) examples are presented first, or at least equally, and clarify that Bash applies to both Linux and macOS.
- Add Linux-specific troubleshooting notes or guidance, especially for common issues such as file permissions, environment variable configuration, and differences in Java installation paths.
- In tables and lists, avoid listing Windows before Linux by default; consider alphabetical or usage-based ordering.
- Where the Azure CLI is used, clarify that it is cross-platform and provide any necessary notes for Linux users (e.g., installation, shell compatibility).
- If there are any differences in behavior or configuration between Windows and Linux (such as supported Java versions, file system paths, or environment variable conventions), call these out explicitly.
- Consider including a section or appendix specifically for Linux/macOS users, summarizing any unique considerations or best practices.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/machine-learning-pytorch.md
...//articles/azure-functions/machine-learning-pytorch.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides cross-platform instructions, but there is a subtle Windows bias. Windows-specific tools and patterns (such as 'py' launcher, registry edits, and PowerShell/Cmd examples) are mentioned or prioritized. Linux instructions are present but sometimes secondary or less detailed. Troubleshooting tips focus on Windows-specific issues, and the order of examples often lists Windows shells before bash.
Recommendations
- Ensure that bash/Linux instructions are always presented first or equally alongside Windows examples, especially in code tabs and command listings.
- Provide Linux/macOS-specific troubleshooting tips (e.g., permissions, path issues) alongside Windows-specific ones.
- Avoid referencing Windows-only tools (like the 'py' launcher or registry edits) without Linux/macOS equivalents or explanations.
- When mentioning editors or tools (e.g., Visual Studio Code), clarify their cross-platform availability.
- Balance the depth of instructions and troubleshooting for all platforms, not just Windows.
- Explicitly state when a command or step differs between platforms, and provide clear alternatives for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/legacy-proxies.md
.../blob/main//articles/azure-functions/legacy-proxies.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, primarily through references to Windows-specific file paths (e.g., D:\home\LogFiles\Application\Proxies\DetailedTrace) and tools (Kudu/Advanced Tools), without mentioning Linux equivalents or clarifying cross-platform differences. There are no explicit Linux or cross-platform command-line examples, and the documentation assumes familiarity with Windows-centric deployment and troubleshooting patterns.
Recommendations
- When referencing file paths (such as for logs), provide both Windows and Linux paths, or clarify that the path is the same or different on Linux-based Function Apps.
- When mentioning 'advanced tools (kudu)', clarify that Kudu is available for both Windows and Linux App Service plans, but access methods and file paths may differ.
- Include explicit notes or examples for Linux users, especially regarding file system locations, deployment, and troubleshooting.
- Where possible, provide cross-platform CLI examples (e.g., using Azure CLI, Bash, or PowerShell Core) for managing proxies.json and application settings.
- Add a section or callout about any known differences in proxy behavior, file access, or portal editing support between Windows and Linux Function Apps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/migrate-version-3-version-4.md
...rticles/azure-functions/migrate-version-3-version-4.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits Windows bias primarily by providing only PowerShell scripts for identifying apps to migrate, referencing Visual Studio (a Windows-centric tool) for deployment, and omitting equivalent Linux/bash/CLI examples. The initial migration steps and tooling guidance are Windows-focused, with Linux alternatives either missing or mentioned later, if at all.
Recommendations
- Provide equivalent Bash/Azure CLI scripts alongside PowerShell for identifying function apps to migrate.
- Include explicit instructions and examples for Linux/macOS users in all migration steps, especially for command-line operations.
- Reference cross-platform tools (e.g., VS Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
- Ensure that all code and configuration examples are clearly marked as cross-platform or provide platform-specific tabs where necessary.
- Audit the documentation for other implicit Windows assumptions (e.g., file paths, tool usage) and address them for Linux parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/migrate-dotnet-to-isolated-model.md
...es/azure-functions/migrate-dotnet-to-isolated-model.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing only Azure PowerShell scripts for identifying function apps, with no equivalent Bash, Azure CLI, or Linux-native instructions. The use of PowerShell as the default scripting language assumes a Windows environment or user familiarity with Windows tooling. There are no explicit Linux or cross-platform command-line examples for key operational steps, and no mention of Linux-specific considerations or parity in the migration process.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell scripts for identifying and managing function apps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, but also offer Bash or shell script alternatives for Linux users.
- Include notes or sections addressing any Linux-specific considerations for local development, deployment, or configuration (e.g., file paths, environment variables, tool installation).
- Ensure that all operational instructions (such as changing app settings or deploying code) have both Windows/PowerShell and Linux/Azure CLI examples, presented in parallel tabs or side-by-side.
- Review references to Visual Studio and clarify alternatives for Linux users, such as Visual Studio Code or command-line deployment tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/openapi-apim-integrate-visual-studio.md
...zure-functions/openapi-apim-integrate-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows, specifically Visual Studio on Windows. All instructions, screenshots, and tooling references are for Windows environments. There are no examples or guidance for Linux or cross-platform development (e.g., Visual Studio Code, CLI, or non-Windows deployment targets). The publishing workflow explicitly targets 'Azure Function App (Windows)', and all steps assume the use of Windows-based Visual Studio and related tools.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using Visual Studio Code or the Azure Functions Core Tools CLI.
- Include examples and screenshots for cross-platform tools, not just Visual Studio on Windows.
- Document how to publish to 'Azure Function App (Linux)' and clarify differences, if any, between Windows and Linux hosting.
- Reference and link to cross-platform development guides and tools (e.g., .NET CLI, VS Code extensions).
- Avoid assuming the use of Windows-specific features (e.g., F5 debugging in Visual Studio, Package Manager Console) and offer alternatives for other platforms.
- Clearly indicate when a step or tool is Windows-only, and provide alternatives where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/run-functions-from-deployment-package.md
...ure-functions/run-functions-from-deployment-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias by consistently listing Windows paths and deployment instructions before Linux equivalents. Windows-specific tools and patterns (such as MSDeploy and c:\ paths) are mentioned or discussed in detail, while Linux alternatives are only referenced as secondary or in passing. There are no Linux-specific command-line examples or tooling recommendations, and no Linux shell (bash) or CLI examples are provided. The documentation assumes familiarity with Windows conventions, which may disadvantage Linux users.
Recommendations
- Present Linux and Windows instructions/examples in parallel, or alternate which platform is listed first.
- Include Linux-specific command-line examples (e.g., using bash, az CLI, or scp) for creating and uploading deployment packages.
- Reference Linux-native tools (such as tar/gzip, where applicable) and explain why .zip is required.
- Provide explicit Linux file path examples and highlight any differences in behavior or requirements.
- Mention Linux deployment caveats and best practices with the same level of detail as Windows.
- Avoid assuming the use of Windows-only tools (like MSDeploy); if mentioned, provide Linux alternatives or clarify their platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/recover-python-functions.md
...//articles/azure-functions/recover-python-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias in several areas: Windows or PowerShell commands are often presented first or exclusively, especially for checking Python interpreter bitness and deleting directories. Some instructions and examples reference Windows-specific tools or patterns before their Linux equivalents, and in a few places, Linux/Bash examples are present but not always given equal prominence or detail. There are also references to Windows/macOS local development without always providing explicit Linux guidance.
Recommendations
- Ensure that all command-line examples are provided for Windows (PowerShell/CMD), Linux (Bash), and macOS where applicable, and present them in parallel tabs or sections.
- When referencing tools or commands (e.g., checking Python version or bitness), always provide both Windows and Linux/macOS equivalents, and avoid listing Windows first by default.
- Where instructions mention local development on Windows or macOS, explicitly include Linux as a supported local development environment.
- In sections where only Windows or PowerShell commands are given (e.g., deleting directories), ensure Bash/Linux equivalents are always present and equally prominent.
- Review all troubleshooting steps to ensure Linux users are not required to infer steps from Windows instructions.
- Where possible, use neutral, cross-platform language and avoid implying Windows is the default or primary development environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-dev-guide-csharp-sdk.md
...in//articles/azure-maps/how-to-dev-guide-csharp-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for all command-line examples (project creation, package installation, and environment variable setup). There are no equivalent Bash or Linux/macOS shell examples provided, and the instructions for setting environment variables use Windows-specific syntax. This may hinder Linux or macOS developers from following the guide seamlessly.
Recommendations
- Provide equivalent Bash shell examples alongside PowerShell for all command-line instructions, including project creation, package installation, and environment variable setup.
- When demonstrating environment variable usage, show both Windows (PowerShell) and Linux/macOS (Bash) syntax (e.g., export VAR=value).
- Explicitly mention that the .NET SDK and Azure CLI are cross-platform, and clarify that the examples apply to all platforms with appropriate shell syntax.
- Consider alternating the order of examples or presenting both Windows and Linux/macOS commands together to avoid the perception of Windows-first bias.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-dev-guide-py-sdk.md
...b/main//articles/azure-maps/how-to-dev-guide-py-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using PowerShell commands for project setup, environment variable configuration, and package installation. There are no equivalent Linux/macOS (bash/sh) commands or instructions provided, which may hinder users on non-Windows platforms. This is especially notable in the sections for creating a project directory, installing packages, and setting environment variables.
Recommendations
- Provide equivalent bash (Linux/macOS) commands alongside PowerShell examples for all shell operations, such as directory creation (e.g., 'mkdir', 'cd', 'touch'), package installation ('pip install ...'), and setting environment variables (e.g., 'export VAR=value').
- When presenting shell commands, either show both Windows and Linux/macOS versions together or default to cross-platform syntax where possible.
- Explicitly mention that the examples are shown in PowerShell and provide a note or tabbed interface for users to select their platform.
- Review all code snippets and instructions to ensure Linux and macOS users can follow along without ambiguity or additional research.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/set-runtime-version.md
.../main//articles/azure-functions/set-runtime-version.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and references to Windows-specific tools (such as Visual Studio and .csproj modifications) are provided alongside Azure CLI and portal instructions, but Linux-specific instructions are less prominent or are only present in dedicated Linux pivots. In several places, PowerShell is given equal or greater prominence than Azure CLI, and some advanced configuration (like pinning via .csproj) is only described for Windows/.NET scenarios. Additionally, some instructions (such as setting linuxFxVersion) are less detailed or lack parity with Windows guidance.
Recommendations
- Ensure that Linux-specific instructions are as detailed and discoverable as Windows instructions, not just in pivots but in mainline content where possible.
- Provide parity for advanced scenarios, such as pinning runtime versions, for both Windows and Linux, including equivalent examples for non-.NET stacks.
- Avoid referencing Windows-specific tools (e.g., Visual Studio, .csproj) without offering Linux/OSS alternatives or clarifying their scope.
- Where PowerShell is presented, ensure Bash or shell script equivalents are provided for Linux users.
- Consider leading with cross-platform tools (Azure CLI, portal) before platform-specific tools (PowerShell, Visual Studio) to reduce perceived Windows-first bias.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/update-language-versions.md
...//articles/azure-functions/update-language-versions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias in several areas: Windows/Azure portal instructions and examples are consistently presented before Linux equivalents, and in some cases, Linux instructions are only available for certain plans or are less detailed. Some language stacks (e.g., Python) are explicitly unsupported on Windows, but the documentation still defaults to Windows tabs. There is also a lack of parity in example commands and guidance for Linux users, especially regarding portal-based updates and plan limitations.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel tabs, rather than always leading with Windows.
- Ensure that all examples and step-by-step instructions are available for both Windows and Linux, including portal-based and CLI-based workflows.
- Clearly indicate plan limitations for both OSes at the start of relevant sections, not only in Linux-specific notes.
- Where a feature is unsupported on one OS (e.g., Python on Windows), default the documentation tab to the supported OS, or provide a clear redirect.
- Provide equivalent depth and detail for Linux workflows, including screenshots and portal navigation, where possible.
- Avoid assuming Windows as the default environment in language or structure; use neutral phrasing such as 'On Windows' and 'On Linux' equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-extension.md
...azure-government/documentation-government-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands and referencing Windows-centric tools for obtaining VM extension lists in Azure Government. There are no CLI or Bash examples for Linux users, and the workflow is described only in terms of Windows/PowerShell usage. Additionally, the 'Next steps' section lists the Windows extension deployment link before the Linux equivalent.
Recommendations
- Add equivalent Azure CLI (az) and/or Bash examples for listing VM extensions, ensuring Linux and cross-platform users are supported.
- Explicitly mention that PowerShell is not required and provide alternative instructions for non-Windows environments.
- In the 'Next steps' section, alternate the order of Windows and Linux links or present them together to avoid implicit prioritization.
- Clarify in the introduction that the instructions apply to both Windows and Linux users, and provide links to both sets of tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/storage-considerations.md
...in//articles/azure-functions/storage-considerations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific plans and settings are often mentioned before their Linux equivalents, and PowerShell examples are provided alongside Azure CLI, but there is a lack of explicit Linux shell examples (e.g., Bash). Some features and limitations are described primarily in the context of Windows (e.g., Azure Files in Consumption plan), and Linux-specific guidance is sometimes relegated to later sections or notes.
Recommendations
- Ensure that Linux and Windows hosting plans are described with equal prominence and clarity, especially in sections discussing storage features and limitations.
- Provide explicit Linux shell (Bash) command examples alongside PowerShell and Azure CLI, particularly for common administrative tasks.
- Where features differ between Windows and Linux (e.g., Azure Files usage, mounting shares), clearly summarize the differences in a comparative table or callout.
- Avoid phrasing such as 'Windows only' or 'Linux only' without immediately providing the counterpart scenario or guidance for the other platform.
- In sections where Visual Studio or Windows tools are referenced (e.g., Azurite emulator), also mention equivalent Linux development workflows and tools.
- Review all examples and ensure that, for every Windows-specific example or tool, a Linux equivalent is provided or a note is included if not available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/azure-secure-isolation-guidance.md
...es/azure-government/azure-secure-isolation-guidance.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows-centric bias in several areas. Windows technologies, tools, and terminology are frequently mentioned first or exclusively (e.g., Hyper-V, BitLocker, Windows Firewall, Windows Server, RDP, PowerShell), with Linux equivalents either mentioned later, in passing, or omitted. Example commands and operational guidance often reference Windows or PowerShell, with Linux/CLI alternatives less prominent or missing. This can make the documentation less accessible or actionable for Linux-focused users.
Recommendations
- Ensure all operational guidance, examples, and tool references are provided for both Windows and Linux platforms, with parity in detail and order of presentation.
- When describing Azure features (e.g., VM provisioning, disk encryption, remote access), always include both Windows and Linux workflows, including CLI and SSH examples, not just PowerShell or RDP.
- Avoid using Windows-specific terminology as the default; instead, use platform-neutral language or explicitly mention both platforms (e.g., 'Windows Firewall and Linux iptables').
- In tables or lists, alternate the order of Windows and Linux entries or present them side-by-side.
- Where Windows tools or technologies are referenced (e.g., BitLocker, Hyper-V, Windows Firewall), ensure Linux equivalents (e.g., dm-crypt, KVM, iptables/firewalld) are also described with equal depth.
- Provide links to Linux-specific Azure documentation alongside Windows links.
- Review all examples and ensure that for every PowerShell or Windows-centric example, a Linux/CLI/SSH equivalent is present.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-cognitiveservices.md
...vernment/documentation-government-cognitiveservices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All provisioning and management examples are provided exclusively with Azure PowerShell commands, with no mention of Azure CLI, Bash, or Linux-native workflows. The quickstart links and tabs also prioritize Windows and Visual Studio, with no clear Linux or cross-platform alternatives. There is no guidance for users on Linux or macOS, nor are equivalent commands or tools mentioned.
Recommendations
- Add Azure CLI examples alongside PowerShell for all resource provisioning and management steps.
- Explicitly mention that Azure CLI and Bash can be used on Linux/macOS, and provide equivalent commands.
- In quickstart links, ensure Linux and cross-platform tabs are present and not just Windows/Visual Studio.
- Include screenshots or terminal output from Linux environments where appropriate.
- Review all instructions and ensure parity for Linux and macOS users, not just Windows/PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-howto-deploy-webandmobile.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-howto-deploy-webandmobile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes deploying an Azure App Services app using Visual Studio 2019, a Windows-centric IDE, and does not mention or provide examples for Linux or cross-platform deployment tools (such as Azure CLI, Git, or VS Code). All instructions and screenshots are based on Windows/Visual Studio workflows, with no guidance for Linux or macOS users.
Recommendations
- Add alternative deployment instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include examples for deploying from VS Code, which is available on all major operating systems.
- Provide command-line examples (e.g., using Git or zip deployment) that are platform-agnostic.
- Explicitly mention Linux/macOS compatibility and provide equivalent steps or links to relevant documentation.
- Balance the order of presentation so that Windows-specific tools are not always mentioned first or exclusively.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-connect-ssms.md
...re-government/documentation-government-connect-ssms.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and provides step-by-step instructions with screenshots for its use. There are no examples or guidance for connecting to Azure Government SQL Server from Linux or cross-platform tools (e.g., Azure Data Studio, sqlcmd, or other CLI tools). This creates a Windows-centric bias and excludes Linux/macOS users.
Recommendations
- Include instructions for connecting to Azure Government SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI-based methods.
- Add Linux/macOS-specific examples and screenshots where applicable.
- Mention the availability of cross-platform alternatives to SSMS early in the documentation, and provide links to their documentation.
- Ensure that firewall rule setup and connection steps are described in a platform-agnostic way, or provide parallel instructions for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/connect-with-azure-pipelines.md
...icles/azure-government/connect-with-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively providing PowerShell scripts and instructions for generating a service principal, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting any equivalent Bash, Azure CLI, or Linux-native instructions. There are no examples or guidance for users on Linux or macOS platforms, and the workflow assumes a Windows environment throughout.
Recommendations
- Provide equivalent Bash/Azure CLI scripts for service principal creation and management, suitable for Linux/macOS users.
- Include instructions for running scripts on Linux/macOS terminals, such as using chmod +x and ./script.sh, or az ad sp create-for-rbac commands.
- Avoid assuming PowerShell as the default shell; explicitly mention cross-platform alternatives.
- Where PowerShell is required, clarify if PowerShell Core (cross-platform) can be used, and provide installation guidance for non-Windows systems.
- Balance the order of examples: present Linux/macOS and Windows instructions side by side or in parallel sections.
- Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-create-template.md
...//articles/devtest-labs/devtest-lab-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only command-line scripting example explicitly mentioned for creating custom images, and uploading VHDs via PowerShell is listed as an option. The use of Windows-specific tools (PowerShell, sysprep) is more prominent, and Windows terminology or steps are often mentioned before Linux equivalents (e.g., 'sysprep' for Windows is described before 'deprovision' for Linux). There are no Linux shell/CLI examples or references to Linux-native tools for uploading VHDs.
Recommendations
- Add explicit Linux shell/CLI examples (e.g., using Azure CLI or Bash scripts) for creating custom images and uploading VHDs.
- Mention Linux-native tools (such as azcopy from a Linux shell, or sftp/scp) alongside PowerShell and Storage Explorer.
- When describing OS-specific preparation steps, present Windows and Linux instructions in parallel (e.g., 'If you choose Windows, run sysprep; if you choose Linux, run deprovision') rather than listing Windows first.
- Ensure that links to Linux-specific documentation or examples are provided wherever PowerShell or Windows tools are referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-get-started-connect-to-storage.md
...ocumentation-government-get-started-connect-to-storage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It recommends Windows-centric tools (Visual Studio 2019) as a prerequisite for .NET development, and does not mention or provide parity for Linux alternatives (such as VS Code or JetBrains Rider). The Storage Explorer section, while describing a cross-platform tool, does not clarify or show Linux/macOS installation or usage. There are no command-line examples (e.g., Azure CLI, PowerShell, Bash) for connecting to Azure Storage, nor are there any Linux-specific instructions or troubleshooting tips. The focus on Visual Studio and the lack of explicit Linux guidance may hinder Linux developers.
Recommendations
- For .NET development, mention and provide instructions for cross-platform IDEs/editors such as Visual Studio Code or JetBrains Rider, and clarify that Visual Studio is only required if using Windows-specific features.
- In the Storage Explorer section, explicitly mention that the tool is available for Windows, macOS, and Linux, and provide download/installation links or steps for each OS.
- Add command-line examples using Azure CLI (az storage ...) for common tasks, and show usage in both Windows (CMD/PowerShell) and Linux/macOS (Bash) environments.
- Include troubleshooting notes or tips for Linux/macOS users, such as environment variable setup, file permissions, or dependency installation.
- Review all screenshots and instructions to ensure they are not Windows-specific, or provide equivalent visuals for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-connect-vs.md
...zure-government/documentation-government-connect-vs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes connecting to Azure Government using Visual Studio, a Windows-centric IDE, without mentioning or providing alternatives for Linux users. There are no examples or instructions for connecting via cross-platform tools (e.g., VS Code, CLI, or SDKs), nor is there acknowledgment of Linux environments. This presents a clear Windows bias by focusing solely on Windows tools and workflows.
Recommendations
- Include instructions for connecting to Azure Government using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure PowerShell (which are available on Linux and macOS).
- Explicitly mention and provide examples for Linux and macOS users, including any prerequisites or differences in the connection process.
- Add a section or links to documentation for connecting to Azure Government using command-line tools or SDKs, which are platform-agnostic.
- Clarify in the prerequisites that Visual Studio is a Windows-only tool, and suggest alternatives for users on other operating systems.