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 1851-1875 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/connectors-create-api-informix.md
.../articles/connectors/connectors-create-api-informix.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by mentioning 'IBM Informix for Windows running in Azure virtualization' as the primary cloud-based example and listing 'Windows (kerberos)' as an authentication option without referencing Linux equivalents. There is no explicit Linux example or mention of Linux-specific tools or authentication methods, and the documentation does not clarify cross-platform compatibility or provide parity in examples for Linux environments.
Recommendations
- Explicitly mention Linux-based Informix deployments in cloud and on-premises scenarios alongside Windows.
- Provide example connection strings and screenshots for both Linux and Windows Informix servers.
- Clarify authentication options for Linux (e.g., PAM, LDAP) if supported, not just 'Windows (kerberos)'.
- Add a note or section on any platform-specific considerations or differences when connecting to Informix on Linux versus Windows.
- Ensure that all examples, especially those referencing server names or authentication, are platform-neutral or provide both Windows and Linux variants.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/virtual-machine-solutions-sgx.md
...onfidential-computing/virtual-machine-solutions-sgx.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific resources before Linux equivalents and linking to Windows-focused documentation. While both Ubuntu and Windows images are mentioned, the ARM template deployment section links to a Windows-specific template description, and the order of OS images and examples often places Windows first.
Recommendations
- Provide parallel links to both Windows and Linux template documentation, or use a neutral landing page that covers both.
- When listing supported OS images or examples, alternate the order or present Linux and Windows options side by side.
- Ensure that all example commands (such as Azure CLI) are shown in a cross-platform way, avoiding backticks (`) for line continuation, which is PowerShell-specific; use backslash (\) or show both variants.
- Where possible, explicitly mention Linux tools, patterns, or workflows alongside Windows equivalents.
- Review all references and links to ensure Linux users have equal access to relevant guidance and examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-integrate-osdu-service-logs-with-azure-monitor.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-integrate-osdu-service-logs-with-azure-monitor.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes integration and log analysis using Azure Portal and Azure-native tools, with no mention of Linux command-line workflows, CLI, or cross-platform automation. There are no examples using Azure CLI, Bash, or Linux-based scripting, and all screenshots and instructions assume GUI interaction typical of Windows environments.
Recommendations
- Add step-by-step instructions for configuring diagnostic settings and querying logs using the Azure CLI, which is cross-platform and commonly used on Linux.
- Provide examples of accessing archived logs from Azure Storage using Linux tools (e.g., azcopy, wget, or Azure CLI commands in Bash).
- Include sample automation scripts for log export and analysis using Bash or Python, demonstrating Linux-friendly workflows.
- Explicitly mention that all operations can be performed from Linux or macOS as well as Windows, and provide links to relevant cross-platform tooling documentation.
- Balance screenshots and instructions by including CLI and code-based alternatives alongside GUI steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/connectors-create-api-oracledatabase.md
...les/connectors/connectors-create-api-oracledatabase.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of the on-premises data gateway, which is primarily a Windows-only tool, and all installation and troubleshooting steps are written with Windows environments in mind. There are no examples or guidance for Linux-based environments, nor is there mention of Linux compatibility or alternatives for the gateway or Oracle client installation.
Recommendations
- Explicitly state the platform requirements for the on-premises data gateway (e.g., that it is Windows-only), and provide links to official documentation about supported operating systems.
- If Linux is not supported for the gateway, mention this limitation clearly and suggest possible workarounds (such as running the gateway in a Windows VM on Linux hosts).
- If Linux support is available or planned, provide equivalent installation and troubleshooting instructions for Linux environments.
- Include examples or notes for connecting to Oracle Database from Linux-based environments, or clarify if such scenarios are not supported.
- Consider referencing cross-platform alternatives or Azure-native solutions that do not require Windows-only components.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/integrate-ibmi-apps-distributed-program-calls.md
...ctors/integrate-ibmi-apps-distributed-program-calls.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft Windows tools (such as Host Integration Server Designer, which requires .NET Framework 4.8) for generating required metadata files. There are no mentions of Linux-compatible alternatives or instructions for Linux users, nor are there any examples or guidance for performing these tasks on non-Windows platforms.
Recommendations
- Provide information on whether the HIS Designer tool can be run on Linux (e.g., via Mono or Wine), or clarify its Windows-only status.
- If possible, offer or recommend a cross-platform or Linux-native tool for generating HIDX files, or provide a manual method for Linux users.
- Include explicit instructions or notes for Linux and macOS users regarding prerequisites and alternatives.
- Add examples or workflow steps that demonstrate how Linux users can participate in the process, or at least acknowledge current limitations and suggest workarounds.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/integrate-3270-apps-ibm-mainframe.md
...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring the use of the 3270 Design Tool, which is dependent on Microsoft .NET Framework 4.8 (a Windows-only technology). There are no instructions or alternatives for Linux or macOS users, nor are there any cross-platform examples or tool recommendations. All setup and tooling references assume a Windows environment.
Recommendations
- Provide information about running the 3270 Design Tool on Linux or macOS, such as via Wine or Mono, if possible.
- Offer or reference a cross-platform or web-based alternative to the 3270 Design Tool for generating HIDX files.
- Explicitly state the OS requirements for the 3270 Design Tool and suggest workarounds for non-Windows users.
- Include Linux/macOS-specific guidance for any steps that can be performed outside of the Azure Portal (e.g., file uploads via CLI, automation scripts).
- If no Linux alternative exists, acknowledge this limitation and provide a roadmap or feedback link for users needing Linux support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/azure-arc-enable-cluster.md
...n//articles/container-apps/azure-arc-enable-cluster.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for all commands, but does not include any Linux-specific shell examples beyond Bash, nor does it mention or prioritize Linux-native tools or workflows. In most cases, PowerShell examples are presented alongside Bash, but the presence of PowerShell throughout and the lack of explicit Linux (e.g., zsh, fish, or other Linux shell) or macOS guidance suggests a mild Windows bias. Additionally, PowerShell examples are always present, and sometimes the syntax (such as variable assignment) is tailored for Windows/PowerShell users.
Recommendations
- Clarify that Bash examples are suitable for Linux and macOS users, and PowerShell is for Windows users.
- Explicitly mention Linux and macOS compatibility in the prerequisites and setup sections.
- Where environment variables are set, note any differences in syntax or behavior between Bash (Linux/macOS) and PowerShell (Windows).
- Consider adding a short section or note for users on Linux or macOS, confirming that all Azure CLI commands work natively in their environments.
- If possible, provide troubleshooting tips or links for common issues encountered on Linux/macOS (e.g., file permissions, path differences).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/dapr-functions-extension.md
...n//articles/container-apps/dapr-functions-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for invoking HTTP endpoints and viewing logs, but consistently lists PowerShell first in tabbed code blocks. There are no Linux-specific tools or shell examples beyond curl, and the structure implies a slight preference for Windows/PowerShell users. However, the Azure CLI is used throughout, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and curl tabs, or list curl first to avoid implicit prioritization of Windows tools.
- Explicitly mention that all CLI and curl commands work on Linux, macOS, and Windows to reinforce cross-platform support.
- Consider adding bash or zsh shell script examples where appropriate, especially for scripting or automation steps.
- Where PowerShell is used, clarify that equivalent commands can be run in other shells, or provide a brief note about cross-platform compatibility.
- If referencing the Azure portal, note that it is web-based and platform-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/deploy-visual-studio-code.md
...//articles/container-apps/deploy-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is written in a platform-neutral tone but implicitly assumes a Windows environment by referencing Visual Studio Code shortcuts (F1), GUI workflows, and omitting any mention of Linux- or macOS-specific steps, terminal commands, or alternative workflows. There are no explicit PowerShell or Windows-only tool references, but the lack of Linux/macOS parity (e.g., keyboard shortcuts, terminal usage, or CLI alternatives) may disadvantage non-Windows users.
Recommendations
- Include platform-specific notes for keyboard shortcuts (e.g., F1 on Windows/Linux, Cmd+Shift+P on macOS).
- Add alternative instructions for performing tasks via the terminal or Azure CLI, which are common on Linux/macOS.
- Mention any OS-specific prerequisites or differences in extension installation or usage.
- Provide explicit confirmation that the steps work identically on Linux and macOS, or call out any differences.
- Where possible, include screenshots or references for Linux/macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/communicate-between-microservices.md
...es/container-apps/communicate-between-microservices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for most commands, but in several key sections, the PowerShell workflow is more detailed and prominent. For example, the deployment of the frontend application is described in a much more elaborate way for PowerShell users, including the use of template objects and multiple steps, whereas the Bash workflow is a single command. Additionally, in some sections, PowerShell appears before Bash, and the PowerShell workflow uses Azure PowerShell cmdlets (e.g., New-AzContainerApp) rather than Azure CLI, which is more cross-platform. There are no missing Linux examples, but the PowerShell workflow is more verbose and detailed, potentially giving the impression of Windows preference.
Recommendations
- Ensure that both Bash and PowerShell workflows are equally detailed. For example, provide a step-by-step Bash alternative for the multi-step PowerShell deployment process, possibly using Azure CLI and environment variables.
- Where possible, use Azure CLI for both Bash and PowerShell examples to maintain cross-platform parity, as Azure CLI works identically on Windows, Linux, and macOS.
- Present Bash examples first, as Bash is the default shell on Linux and macOS, and is also available on Windows via WSL or Git Bash.
- If using PowerShell-specific cmdlets (e.g., New-AzContainerApp), provide equivalent Azure CLI commands for Bash users.
- Review the order and depth of examples to ensure Linux users are not disadvantaged or required to 'figure out' missing steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-manage-users.md
...//articles/energy-data-services/how-to-manage-users.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently instructs users to run commands in 'Azure Cloud Shell', which is a Microsoft-hosted environment that defaults to Bash but is tightly integrated with Azure and may be more familiar to Windows users. There are no explicit PowerShell or Windows command examples, but the documentation does not mention or provide guidance for running these commands in native Linux/macOS terminals or non-Azure environments. The focus on Azure Cloud Shell and Azure-specific patterns may implicitly favor Windows-centric workflows and tools.
Recommendations
- Clarify that all curl commands are standard and can be run from any Bash-compatible terminal on Linux, macOS, or Windows (with WSL or Git Bash), not just Azure Cloud Shell.
- Add explicit notes or examples for running the commands in native Linux/macOS terminals, and mention any prerequisites (e.g., curl installation, authentication setup).
- If Azure Cloud Shell is recommended for convenience, explain why, and provide alternatives for users who prefer or require local environments.
- Ensure screenshots and instructions for obtaining object IDs or tokens are not solely based on the Azure Portal UI, but also mention CLI-based alternatives (e.g., using Azure CLI on Linux/macOS).
- Avoid language that assumes the reader is using Windows or Azure-hosted environments by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/sessions.md
...re-docs/blob/main//articles/container-apps/sessions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Hyper-V, a Windows-based virtualization technology, as the foundation for session isolation. There is no mention of Linux-based isolation technologies (such as KVM, gVisor, or Kata Containers), nor are Linux equivalents or cross-platform considerations discussed. The documentation also links to Windows Server Hyper-V documentation, reinforcing a Windows-first perspective.
Recommendations
- Acknowledge and describe any Linux-based isolation technologies used (if applicable), or clarify if Hyper-V is used regardless of the underlying host OS.
- If Azure Container Apps supports Linux hosts or Linux-based isolation (such as KVM, gVisor, or Kata Containers), provide equivalent explanations and references.
- Avoid linking exclusively to Windows-specific documentation; instead, provide cross-platform or neutral explanations where possible.
- Include a note on platform compatibility, especially if sessions can run on both Windows and Linux hosts, and clarify any differences in isolation mechanisms.
- If only Hyper-V is used, explicitly state this and explain any implications for Linux users or workloads.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/samples.md
...ure-docs/blob/main//articles/container-apps/samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page predominantly features .NET/ASP.NET Core and Microsoft Orleans samples, which are technologies most commonly associated with Windows development. The majority of the examples are focused on Microsoft-centric stacks, with only a few non-.NET samples (Drupal and Java). There are no explicit Linux-specific examples or references to Linux-native tools, and the ordering and selection of samples implicitly prioritize Windows/Microsoft technologies.
Recommendations
- Add samples that showcase deploying popular Linux-native stacks (e.g., Node.js, Python Flask/Django, Ruby on Rails, Go) on Azure Container Apps.
- Include examples that use Linux command-line tools and deployment patterns, such as Bash scripts or Docker Compose, alongside any PowerShell or Windows-specific instructions.
- Ensure parity in documentation by providing equivalent walkthroughs for both Windows and Linux environments, especially for setup, deployment, and troubleshooting.
- Highlight cross-platform compatibility and explicitly mention when a sample or technology is equally suited for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/tutorial-scaling.md
...blob/main//articles/container-apps/tutorial-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity in command-line instructions. However, in the 'Send requests' section, the Bash example uses standard Linux tools (seq, xargs, curl) with detailed explanations and links to Linux man pages, while the PowerShell example uses a more complex, Windows-specific approach (runspaces, Invoke-WebRequest) with less explanation and no cross-platform alternatives. Additionally, the instructions for opening a new shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for PowerShell, subtly placing Windows/PowerShell as a primary environment. The Bash examples are generally presented before PowerShell, but the overall structure and explanations are balanced. There are no missing Linux examples, but the PowerShell approach is more elaborate and may suggest a Windows-centric workflow for users unfamiliar with Linux tools.
Recommendations
- In the 'Send requests' section, provide a cross-platform alternative for Windows users who may not have PowerShell (e.g., using WSL or Git Bash on Windows, or suggesting curl in Command Prompt if available).
- For the PowerShell example, consider simplifying the approach or explaining why such complexity (runspaces) is needed compared to the straightforward Bash pipeline.
- Add a note clarifying that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash), and that PowerShell Core is available cross-platform.
- Where possible, provide links to PowerShell documentation similar to the links provided for Linux tools.
- Ensure that the order of presentation does not implicitly prioritize Windows/PowerShell over Linux/Bash, or vice versa—consider alternating or explicitly stating parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md
...g/automate/automation-ingest-usage-details-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows a subtle Windows bias by mentioning Microsoft Excel as the primary example for opening CSV files, without referencing Linux or cross-platform alternatives. No command-line or scripting examples are provided for either Windows (PowerShell) or Linux (bash), but the only tool explicitly named is Excel, which is Windows-centric. There is also no mention of Linux-native tools (such as LibreOffice Calc, csvkit, or command-line utilities) for handling cost details data.
Recommendations
- When suggesting tools to open CSV files, mention cross-platform and Linux-native options such as LibreOffice Calc, Google Sheets, or command-line tools like csvkit, awk, or pandas.
- If providing examples for automating data ingestion or processing, include both PowerShell (Windows) and bash (Linux/macOS) scripts.
- Explicitly state that the data can be processed on any platform and provide links or references to relevant tools for Linux users.
- Consider including a section or callout for Linux/macOS users, outlining recommended workflows and tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/tutorial-reservoir-ddms-websocket.md
...rgy-data-services/tutorial-reservoir-ddms-websocket.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation introduces the tutorial as using PowerShell to work with Reservoir DDMS APIs, suggesting a Windows-centric approach. However, all actual command examples use Bash and Docker, which are cross-platform. There are no explicit Linux examples or references, but the initial framing and variable syntax ($VAR) may be more familiar to Windows/PowerShell users, potentially causing confusion for Linux users.
Recommendations
- Clarify in the introduction that the tutorial uses Bash shell commands, which are compatible with Linux, macOS, and Windows (via WSL or Git Bash), not just PowerShell.
- Provide equivalent variable setting examples for both Bash (export VAR=...) and PowerShell ($env:VAR = ...), or explain the syntax difference.
- Avoid stating 'in PowerShell' unless the examples are specifically for PowerShell; otherwise, use 'in the command line' or 'in your terminal'.
- Explicitly mention cross-platform compatibility and provide notes for Windows users on using WSL or Git Bash if needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/automate/get-small-usage-datasets-on-demand.md
...billing/automate/get-small-usage-datasets-on-demand.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by recommending Excel for data analysis after download, without mentioning Linux-friendly alternatives. There are no explicit command-line examples (PowerShell, Bash, etc.), but the only tool suggested for post-processing is Excel, which is primarily a Windows application. No Linux or cross-platform tools (such as LibreOffice Calc, csvkit, or pandas) are mentioned for analyzing the downloaded CSV data.
Recommendations
- When suggesting tools for data analysis, include cross-platform or Linux-friendly options such as LibreOffice Calc, csvkit, or pandas, alongside Excel.
- If providing examples of how to process or analyze the downloaded CSV data, include both Windows (Excel) and Linux (command-line tools, Python scripts) workflows.
- Explicitly state that the CSV output can be used with a variety of spreadsheet and data analysis tools available on all major operating systems.
- Consider adding a section or note on how to automate or script the download and processing of cost data using Bash, Python, or other cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/assign-access-acm-data.md
...ost-management-billing/costs/assign-access-acm-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references the Azure portal UI for all access assignment tasks, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows-only tools, it implicitly favors Windows-centric workflows by not providing cross-platform (Linux/macOS) command-line examples. There is no mention of Linux or cross-platform tooling, nor any CLI or automation options, which can disadvantage users who prefer or require non-GUI, scriptable, or Linux-native approaches.
Recommendations
- Add Azure CLI examples for all access assignment tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where relevant, provide PowerShell examples as an alternative, but ensure CLI examples are given equal or higher prominence.
- Mention REST API options for automation and scripting, with example requests for common tasks.
- Explicitly state that all tasks can be performed on any OS using CLI or API, not just via the Azure portal.
- Consider including a 'Command-line alternatives' section for each major task, linking to relevant Azure CLI or API documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/cost-analysis-common-uses.md
...-management-billing/costs/cost-analysis-common-uses.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal UI for cost analysis tasks, with all navigation and screenshots reflecting a Windows-centric interface. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), but all instructions and UI conventions assume a Windows/desktop environment. There is no mention of Linux tools, CLI workflows, or parity for users who may prefer or require non-Windows environments.
Recommendations
- Add equivalent Azure CLI and/or Bash command examples for each cost analysis task, enabling Linux and cross-platform users to perform the same actions via the command line.
- Explicitly mention that all tasks can be performed from any OS via the Azure portal web interface, but also provide guidance for users who prefer automation or scripting.
- Where possible, include PowerShell and Azure CLI code snippets side-by-side to demonstrate parity and inclusivity.
- Clarify any limitations or differences in experience for users on Linux or macOS, especially if certain features are only available in the portal or via Windows-specific tools.
- Consider adding a section or links to documentation on using Cost Management APIs for programmatic access, which is platform-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/create-enterprise-subscription.md
...ement-billing/manage/create-enterprise-subscription.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes how to create an Enterprise Agreement subscription using the Azure portal, a web-based GUI tool. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor is there any mention of Linux or cross-platform tooling. The only programmatic reference is a link to another page, with no direct examples. The documentation implicitly assumes use of the Azure portal, which is platform-agnostic but often associated with Windows-centric workflows. There is no explicit Windows-first language, but the lack of Linux or CLI examples represents a bias toward GUI-based (and thus traditionally Windows-oriented) usage patterns.
Recommendations
- Add step-by-step instructions for creating an Enterprise Agreement subscription using the Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples if relevant, but always provide Azure CLI or REST API equivalents alongside them.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows-only access.
- Provide links or inline examples for programmatic creation using Bash scripts or REST API calls, not just references to other documentation.
- Where screenshots are used, ensure they do not show Windows-specific UI elements (such as Windows taskbars or browsers) to reinforce cross-platform applicability.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/quick-create-budget-bicep.md
...-management-billing/costs/quick-create-budget-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management steps, but consistently lists PowerShell examples immediately after CLI, and uses PowerShell-specific syntax and variable handling. There is no explicit mention of Linux or macOS environments, nor any guidance for shell differences (e.g., Bash vs PowerShell variable syntax). While Azure CLI is cross-platform, the documentation assumes familiarity with PowerShell and Windows conventions, which may disadvantage Linux users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific variable assignment examples alongside PowerShell.
- For each example, include both Bash (for Linux/macOS) and PowerShell (for Windows) variable assignment and usage, e.g., show 'myContactEmails=("user1@contoso.com" "user2@contoso.com")' for Bash.
- Add a note clarifying that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS users.
- Where referencing tools to retrieve resource IDs (e.g., 'az monitor action-group show' and 'Get-AzActionGroup'), ensure CLI (cross-platform) is mentioned first or equally, and provide example outputs for both.
- Consider adding a 'Platform differences' section to highlight any nuances or issues Linux/macOS users might encounter, such as quoting, variable expansion, or file path differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/create-free-services.md
...cost-management-billing/manage/create-free-services.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation repeatedly references 'B1S Windows virtual machine' as the example for free usage, without mentioning Linux VM options or providing Linux-specific examples. This creates a Windows-first impression and omits guidance for users interested in Linux-based workloads.
Recommendations
- Include examples that reference both Windows and Linux virtual machines (e.g., 'B1S Windows or Linux virtual machine').
- Explicitly state that Linux VMs are also available within the free tier, and provide usage examples for both operating systems.
- Where possible, alternate between Windows and Linux examples, or present them side-by-side to ensure parity.
- Clarify that the free VM hours can be used for either Windows or Linux images, and link to documentation on creating both types.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/auth0-log-stream-app-insights.md
...//articles/event-grid/auth0-log-stream-app-insights.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of Visual Studio Code and Azure Functions tooling, but all instructions and links are oriented toward the Windows/VS Code workflow. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tooling or alternative workflows. The use of screenshots and step-by-step instructions is based on the Azure Portal UI, which is platform-agnostic, but the development and deployment steps are Windows/VS Code-centric.
Recommendations
- Include explicit instructions for creating and deploying Azure Functions using the Azure CLI and/or PowerShell Core, which are cross-platform.
- Provide alternative steps or links for users developing on Linux or macOS, such as using the Azure Functions Core Tools and command-line editors.
- Add a note clarifying that Visual Studio Code and the Azure Portal are available on all major operating systems, and provide links to Linux/macOS setup guides.
- Where possible, include terminal/command-line examples alongside or instead of GUI-based instructions.
- Ensure that all referenced quickstarts and tutorials have Linux/macOS parity, or link to platform-specific guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/mca-request-billing-ownership.md
...gement-billing/manage/mca-request-billing-ownership.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes the transfer process using the Azure Portal GUI, with all screenshots and instructions referencing the web interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux or cross-platform tooling. The only implicit tooling mentioned is the Azure Portal, which is web-based and cross-platform, but the absence of CLI or script-based instructions is a form of bias, as many Linux users prefer or require non-GUI automation methods.
Recommendations
- Add Azure CLI examples for all major steps (creating transfer requests, reviewing, approving, and checking status), as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added, ensure Bash/Azure CLI equivalents are provided and presented with equal prominence.
- Explicitly mention that all steps can be performed via the Azure CLI or REST API, and link to relevant documentation.
- Include at least one section or note for users who prefer automation or non-GUI workflows, with sample scripts or command sequences.
- Clarify that the Azure Portal is accessible from any OS, but provide parity for users who may not have GUI access or prefer terminal-based workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/mca-enterprise-operations.md
...management-billing/manage/mca-enterprise-operations.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal as the primary (and only) interface for completing billing and administrative tasks, with no mention of command-line alternatives or cross-platform tools. There are no examples or instructions for performing these tasks using CLI tools (such as Azure CLI or REST APIs), which are commonly used on Linux and macOS as well as Windows. This implicitly prioritizes a GUI-centric, Windows-friendly workflow and omits guidance for users on other platforms.
Recommendations
- Include instructions and examples for performing key tasks (such as viewing charges, managing roles, downloading usage data) using the Azure CLI and/or REST APIs, which are cross-platform and widely used on Linux.
- Where possible, provide both portal (GUI) and command-line (CLI/API) workflows side by side, so users can choose their preferred method regardless of OS.
- Explicitly mention that the Azure CLI and REST APIs are available and supported on Linux, macOS, and Windows, and link to their installation and usage guides.
- For tasks that can only be performed in the portal, clarify this limitation explicitly, so Linux users are aware of any constraints.