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 1826-1850 of 2185 flagged pages
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/call-automation-ai-csharp.md ...services/samples/includes/call-automation-ai-csharp.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page demonstrates bias by referencing Windows-specific tabs and pivots in prerequisite links (e.g., 'tabs=windows'), and does not provide any Linux-specific setup or run instructions. All examples and instructions are generic or implicitly assume a Windows environment, with no mention of Linux equivalents or considerations.
Recommendations
  • Provide explicit Linux setup and run instructions, including any differences in commands or environment setup.
  • Ensure all prerequisite links and referenced quickstarts include Linux tabs or pivots, or link to platform-agnostic pages.
  • Mention and test the sample on Linux environments, noting any platform-specific requirements or troubleshooting steps.
  • If using .NET, clarify that .NET Core/SDK is cross-platform and provide instructions for installing and running on Linux.
  • Avoid defaulting to Windows-specific terminology or links unless alternatives are also presented.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/email-resource-management-azurecli-python.md .../includes/email-resource-management-azurecli-python.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily in the 'Prerequisites' section where the Azure CLI installation link points only to the Windows installation guide, and all command-line instructions refer to a generic 'command prompt' without mentioning Linux or macOS terminals. There are no explicit PowerShell or Windows-only commands, and the Python/CLI automation is cross-platform, but the lack of Linux/macOS parity in setup instructions and terminology may confuse or exclude non-Windows users.
Recommendations
  • Provide installation links for Azure CLI for all major platforms (Windows, Linux, macOS), or link to the cross-platform installation overview.
  • In the prerequisites and command sections, clarify that commands can be run in Command Prompt (Windows), Terminal (macOS), or shell (Linux).
  • If any platform-specific differences exist (e.g., command syntax, environment setup), explicitly document them.
  • Consider adding a short section or note confirming that the Python/CLI scripts are cross-platform and tested on Windows, Linux, and macOS.
  • Use inclusive language such as 'terminal or command prompt' instead of just 'command prompt'.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/call-automation-ai-javascript.md ...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows some Windows bias, notably in the prerequisites where the link to creating an Azure Communication Resource uses a Windows-specific tab and pivot. Additionally, the instructions for running the application specify opening a PowerShell window, with no mention of Linux or macOS terminal alternatives. There are no explicit Linux/macOS examples or notes about cross-platform compatibility.
Recommendations
  • Ensure that all links and instructions default to platform-neutral or provide both Windows and Linux/macOS options (e.g., use '?tabs=windows' only when necessary, and add Linux/macOS tabs).
  • In the 'Run the application' section, mention that users can use any terminal (PowerShell, Command Prompt, Terminal on macOS/Linux) and provide equivalent commands if any are platform-specific.
  • Explicitly state that the sample can be run on Windows, Linux, and macOS, and note any platform-specific considerations.
  • If there are any platform-specific steps (e.g., for Azure Dev Tunnels or npm), provide both Windows and Linux/macOS command examples.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/call-automation-azure-openai-csharp.md ...amples/includes/call-automation-azure-openai-csharp.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation references setup instructions and resource creation with links and pivots that default to Windows (e.g., '?tabs=windows'), and does not provide Linux-specific instructions or examples. All command-line examples are generic, but there is no explicit mention of Linux compatibility or alternative commands/tools for Linux users.
Recommendations
  • Provide explicit instructions or notes for Linux users, especially for resource creation and running the application.
  • Ensure that links to Azure portal instructions include Linux/macOS pivots or clarify that the steps are cross-platform.
  • Add a section or note confirming that the sample and tools (such as Azure Dev Tunnels and dotnet CLI) work on Linux, and provide any necessary Linux-specific setup steps.
  • Avoid using Windows-specific pivots or, if unavoidable, provide equivalent Linux/macOS pivots alongside.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/web-calling-hero.md ...nication-services/samples/includes/web-calling-hero.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific shells (PowerShell, Windows Terminal, Command Prompt) first and explicitly, while only referring to 'equivalent' shells for other platforms. There are no explicit Linux or macOS terminal examples or instructions, and the setup instructions assume familiarity with Windows tools and patterns.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., 'Terminal on macOS or Linux') alongside Windows shells.
  • Provide example commands or notes for Linux/macOS users where relevant (e.g., file paths, environment variable setting).
  • Avoid listing Windows shells first or exclusively; use neutral language such as 'Open a terminal (e.g., PowerShell, Command Prompt, Terminal on macOS or Linux)'.
  • Include troubleshooting or setup notes for common Linux/macOS issues if any exist.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/call-automation-azure-openai-js.md ...es/samples/includes/call-automation-azure-openai-js.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by consistently mentioning Windows shells (PowerShell, Windows Terminal, Command Prompt) before any Linux or cross-platform equivalents. Instructions for running commands specifically reference PowerShell and do not mention Linux or macOS terminals. There are no explicit Linux/macOS command-line examples or tool references, though the commands themselves are cross-platform.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., 'Terminal', 'bash', 'zsh') alongside Windows shells in setup and run instructions.
  • Add a note clarifying that all command-line instructions work on Linux/macOS as well as Windows.
  • Provide Linux/macOS-specific examples or screenshots where appropriate, especially for shell commands and environment setup.
  • Avoid listing Windows shells first; use neutral language such as 'Open a terminal (PowerShell, Command Prompt, or Terminal on Linux/macOS)'.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/integrate-azure-communication-services-with-copilot-studio.md ...grate-azure-communication-services-with-copilot-studio.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits a 'windows_first' bias, particularly in the prerequisites section, where the link to creating an Azure Communication Services resource uses a Windows-specific tab and pivot. There are no explicit Linux or cross-platform instructions or examples provided, and no mention of Linux-specific tools or considerations. The code samples are platform-agnostic (C#), but the setup and resource creation guidance implicitly prioritize Windows users.
Recommendations
  • Provide explicit instructions or links for Linux and macOS users alongside Windows, especially in the prerequisites and resource creation steps.
  • Ensure that documentation tabs and pivots include Linux (and macOS) options, not just Windows.
  • Mention cross-platform tools (e.g., ngrok, DevTunnels) and clarify their availability on all major operating systems.
  • If any setup steps (such as running the sample code) differ on Linux, provide those instructions or note any OS-specific requirements.
  • Audit linked documentation to ensure parity in guidance for non-Windows platforms.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/call-duration.md ...cles/communication-services/tutorials/call-duration.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides platform-specific guidance for Android, iOS, and Windows, but does not mention Linux or provide Linux-specific examples or instructions. Windows is included as a primary desktop platform, while Linux is omitted, which may disadvantage developers targeting Linux environments.
Recommendations
  • Add a Linux-specific section or pivot alongside Android, iOS, and Windows, covering how to manage call duration events on Linux (if supported by the SDK).
  • If the SDK is not available for Linux, explicitly state this limitation to inform developers.
  • Include cross-platform examples (e.g., using .NET Core or JavaScript) that work on both Windows and Linux where possible.
  • Ensure parity in documentation by providing equivalent examples, troubleshooting, and setup instructions for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/chat-interop/includes/meeting-interop-features-inline-image-receiving-csharp.md ...meeting-interop-features-inline-image-receiving-csharp.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation is focused exclusively on C# and .NET, which are traditionally associated with Windows development. There are no examples or guidance for Linux or cross-platform environments, nor is there mention of running the SDK or application on Linux. The instructions and code samples assume a Windows-centric development environment (e.g., references to Dispatcher, CoreDispatcherPriority, BitmapImage, and running from an IDE), and do not provide Linux alternatives or considerations.
Recommendations
  • Include explicit instructions or notes on how to run the sample code on Linux (e.g., using .NET Core/6/7 on Linux).
  • Provide equivalent code samples or guidance for Linux environments, such as using cross-platform UI frameworks (e.g., Avalonia, MAUI) instead of Windows-specific APIs like Dispatcher and BitmapImage.
  • Mention any platform-specific dependencies or limitations, and suggest alternatives for Linux users.
  • Add a section on how to set up the development environment on Linux, including installation of .NET SDK and any required libraries.
  • Clarify whether the sample is intended to be cross-platform, and if not, provide links or references to Linux-compatible samples.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/contact-center.md ...les/communication-services/tutorials/contact-center.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias, primarily in the way it links to quickstarts and examples. Many links use 'tabs=windows' or 'tabs=uwp' as defaults, and there is no mention of Linux-specific instructions, tools, or examples. There are no explicit PowerShell or Windows-only command-line examples, but the navigation and example pivots prioritize Windows and UWP (Universal Windows Platform), with no visible parity for Linux users.
Recommendations
  • Provide Linux-specific quickstart links and examples alongside Windows/UWP, ensuring that Linux users can easily find relevant instructions.
  • Use neutral or multi-platform pivots in documentation tables and links (e.g., 'tabs=linux', 'tabs=mac', or 'tabs=web') rather than defaulting to Windows.
  • Explicitly mention Linux compatibility and any required steps or differences for Linux environments.
  • Where code or setup instructions are given, include both Windows and Linux command-line examples (e.g., PowerShell and Bash).
  • Audit referenced quickstart and tutorial pages to ensure Linux parity in all code samples and setup instructions.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/trusted-service-js.md ...tion-services/tutorials/includes/trusted-service-js.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and Azure Functions workflows, but all step-by-step links and instructions point to a 'Create a C# function in Azure by using Visual Studio Code' quickstart, which is Windows-centric in its examples and screenshots. There is no mention of Linux-specific steps, terminal commands, or alternative editors. The documentation assumes the use of Visual Studio Code and its Azure Functions extension, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell or deployment instructions, and no mention of Linux-specific considerations.
Recommendations
  • Include explicit instructions or notes for Linux users, such as verifying that all steps work identically on Linux and MacOS.
  • Add examples of running and deploying the function using common Linux shells (e.g., bash) and terminal commands.
  • Reference Linux package managers and tools where appropriate (e.g., apt, yum, Homebrew for Node.js installation).
  • Provide links to Azure Functions quickstarts or documentation that are explicitly cross-platform or that include Linux/macOS screenshots and steps.
  • Mention any platform-specific caveats or differences, if any, in the development or deployment process.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-chat-ios-tutorial.md .../tutorials/includes/twilio-to-acs-chat-ios-tutorial.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the prerequisites section by linking only to Windows-specific Azure CLI installation instructions and referencing a resource creation quickstart with a Windows tab. There are no Linux or macOS equivalents or instructions provided for these steps, which may hinder users on non-Windows platforms.
Recommendations
  • Provide platform-agnostic or parallel instructions for installing Azure CLI, including explicit links to Linux and macOS installation guides.
  • Ensure that resource creation quickstart links use neutral or multi-platform tabs, or explicitly mention Linux/macOS options.
  • Review all prerequisite steps and ensure parity for Linux and macOS users, including command-line instructions and environment setup.
  • Consider adding a note that all CLI commands work cross-platform, and provide troubleshooting tips for common Linux/macOS issues.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-video-android-tutorial.md ...rials/includes/twilio-to-acs-video-android-tutorial.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits a mild Windows bias in the prerequisites section, where instructions for installing the Azure CLI are provided only for Windows, with no mention of Linux or macOS alternatives. The link to create a Communication Services Resource also defaults to a 'windows' tab. However, the rest of the documentation is platform-neutral and focused on Android development, with no further evidence of Windows-specific tools, commands, or patterns.
Recommendations
  • In the prerequisites, provide installation instructions or links for Azure CLI on Linux and macOS alongside Windows.
  • Ensure that links to Azure portal or resource creation guides do not default to 'windows' tabs; use a neutral or platform-agnostic default.
  • Wherever platform-specific setup is mentioned, include parity for Linux (and optionally macOS) users to ensure inclusivity.
  • Consider adding a note that the CLI commands are cross-platform, and provide troubleshooting tips for common Linux environments if relevant.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/url-shortener-csharp.md ...on-services/tutorials/includes/url-shortener-csharp.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by focusing exclusively on C#/.NET and Azure Functions, with all code samples and setup instructions tailored for the .NET ecosystem. There are no examples or guidance for Linux users, such as using Python, Node.js, or Bash, nor are there instructions for running or deploying the function on Linux environments. The only terminal command shown is platform-agnostic, but the overall workflow assumes Visual Studio Code and .NET, which are more commonly associated with Windows development.
Recommendations
  • Provide equivalent code samples and setup instructions for at least one popular Linux-friendly language (e.g., Python or Node.js) using Azure Functions.
  • Include instructions for installing and running the Azure Functions Core Tools on Linux, including any required dependencies.
  • Demonstrate how to deploy and test the function using Linux-native tools and workflows (e.g., Bash, curl, or HTTPie instead of Postman).
  • Mention cross-platform editors (such as VS Code, which is available on Linux) and clarify that the steps work on both Windows and Linux.
  • If referencing Visual Studio Code, specify that it is available on Linux and provide any Linux-specific setup notes.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-chat-js-tutorial.md ...s/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in the prerequisites section, where instructions for installing the Azure CLI specifically reference Windows and link only to the Windows installation guide. There are no Linux or macOS installation instructions or links provided. Additionally, the quickstart link for creating a Communication Services Resource includes a 'tabs=windows' parameter, further emphasizing Windows. No Linux-specific examples or parity guidance are present.
Recommendations
  • Provide installation instructions and links for Azure CLI on Linux and macOS alongside Windows.
  • Use platform-agnostic or multi-tabbed links (e.g., /cli/azure/install-azure-cli) that allow users to select their OS.
  • Ensure that all quickstart and setup links either default to a neutral platform or offer tabs for Windows, Linux, and macOS.
  • Explicitly mention that the SDK and CLI commands work cross-platform, and provide any necessary notes for Linux/macOS users (e.g., shell differences, permissions).
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-video-ios-tutorial.md ...tutorials/includes/twilio-to-acs-video-ios-tutorial.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a Windows-first bias in the prerequisites, specifically in the Azure CLI installation step, where only instructions for installing the Azure CLI on Windows are linked. There are no equivalent instructions or links for installing the Azure CLI on Linux or macOS, nor is there mention of cross-platform compatibility in this context. The rest of the documentation is focused on iOS development and does not exhibit Windows bias.
Recommendations
  • In the prerequisites, provide links to Azure CLI installation instructions for all major platforms (Windows, Linux, macOS), or link to the general Azure CLI installation page that covers all platforms.
  • Explicitly mention that the Azure CLI is cross-platform and can be used on Linux and macOS as well as Windows.
  • Where platform-specific instructions are given, ensure parity by including Linux/macOS equivalents or clarifying when steps are platform-agnostic.
  • Review other quickstart/resource links to ensure they do not default to Windows tabs or pivots unless contextually appropriate.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/integrate-express-route.md ...nication-services/tutorials/integrate-express-route.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing actions and tools in a way that implicitly assumes a Windows environment. For example, instructions such as 'perform a ping test' and 'use traceroute tools' are generic, but there is no explicit mention of Linux/Unix equivalents (e.g., specifying 'tracert' for Windows and 'traceroute' for Linux). All configuration steps are described via the Azure Portal UI, which is cross-platform, but there are no CLI or PowerShell/Azure CLI/Bash examples, nor are Linux-specific firewall or network configuration steps mentioned. The absence of Linux command-line examples or references to Linux tools suggests a lack of parity for Linux users.
Recommendations
  • Provide explicit examples for both Windows and Linux environments when referencing network tools (e.g., 'tracert' for Windows, 'traceroute' for Linux).
  • Include Azure CLI or Bash-based instructions alongside portal-based steps to support automation and Linux users.
  • Mention Linux-specific firewall configuration (e.g., iptables, firewalld, ufw) in the network security section.
  • Clarify that the steps apply to both Windows and Linux environments, and call out any differences where relevant.
  • Add troubleshooting steps that include Linux command-line examples (e.g., using curl, netcat, or other common Linux utilities).
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/virtual-visits/extend-teams/before-and-after-appointment.md ...al-visits/extend-teams/before-and-after-appointment.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exclusively references Microsoft-centric tools such as Power Automate, Logic Apps, Microsoft Graph API, and Azure Communication Services, all of which are primarily designed for or most commonly used within Windows environments. There are no examples or mentions of Linux-native tools, command-line interfaces, or cross-platform scripting alternatives. The automation and extensibility workflows are described only in the context of Microsoft's graphical tools, with no guidance for users who may prefer or require Linux-based or open-source solutions.
Recommendations
  • Provide equivalent examples using cross-platform tools or APIs that can be accessed from Linux environments, such as using curl or Python scripts to interact with Microsoft Graph API and Azure Communication Services.
  • Include command-line examples (e.g., Bash, curl, Python) for automating appointment workflows, in addition to or instead of only Power Automate/Logic Apps GUI flows.
  • Mention and document any available SDKs or REST APIs, and show how to use them from Linux or macOS systems.
  • Clarify whether the described features and tools are accessible and supported from non-Windows platforms, and provide links to relevant cross-platform documentation.
  • If Power Automate or Logic Apps have web-based or cross-platform interfaces, explicitly state this to reassure Linux users of compatibility.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-integrate-elastic-logs-with-azure-monitor.md ...es/how-to-integrate-elastic-logs-with-azure-monitor.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only GUI-based instructions using the Azure Portal and does not mention or provide any CLI-based examples (such as Azure CLI, PowerShell, or Bash). There is no reference to Linux tools or workflows, nor are there any command-line examples that would be relevant for Linux users. The instructions and screenshots are oriented around the Azure Portal, which is platform-agnostic but often more familiar to Windows users. There is also an implicit bias in mentioning Visual Studio Code as the code editor, which, while cross-platform, is often associated with Windows environments.
Recommendations
  • Add equivalent instructions for performing the same tasks using the Azure CLI, with example commands that work on Linux/macOS terminals.
  • If PowerShell examples are added, ensure Bash equivalents are also provided.
  • Mention and show how to use cross-platform tools (e.g., azcopy, Azure CLI) for downloading and managing log files from storage accounts.
  • Include examples of opening and processing JSON log files using common Linux tools (e.g., jq, less, cat) in addition to Visual Studio Code.
  • Explicitly state that all steps can be performed from any OS, and provide links to relevant CLI documentation for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/authentication-github.md ...main//articles/container-apps/authentication-github.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page provides instructions exclusively through the Azure portal UI, with no command-line examples. There are no explicit Windows-only tools or PowerShell commands, but the lack of CLI (az CLI, Bash) examples means Linux users do not see parity. The absence of Linux-specific or cross-platform command-line instructions can be considered a subtle form of Windows-first or GUI-first bias, as Windows users are more likely to use the Azure portal, while Linux users often prefer CLI workflows.
Recommendations
  • Add equivalent instructions using the Azure CLI (az) for all steps, including registering the GitHub app and configuring authentication providers.
  • Include Bash shell command examples for secret management and environment variable configuration.
  • Explicitly mention that all steps can be performed via CLI and provide links or code blocks for those workflows.
  • Ensure that any references to tools or workflows are cross-platform, or provide both GUI and CLI alternatives.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/confidential-vm-overview.md ...les/confidential-computing/confidential-vm-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. References to Windows-specific technologies (such as TPM and Secure Boot) link to Microsoft/Windows documentation, and the Trusted Platform Module (TPM) section links exclusively to a Windows-focused page. In the OS support matrix, Windows client and server versions are listed in more detail and with more variants than Linux, and Windows appears before Linux in some lists and links. There are no command-line examples, but where tools or concepts are referenced, Windows documentation is prioritized or exclusively linked.
Recommendations
  • Where possible, link to cross-platform or Linux-specific documentation for technologies like TPM and Secure Boot, or provide additional Linux-focused links alongside Windows ones.
  • In the OS support table, consider listing Linux first or alternating the order to avoid the impression of Windows primacy.
  • When referencing features like attestation or disk encryption, include links to both Windows and Linux implementation guides or documentation.
  • If command-line or configuration examples are added in the future, ensure parity by providing both Windows (PowerShell/CLI) and Linux (Bash/CLI) examples.
  • Review all external documentation links to ensure Linux users are not redirected to Windows-centric resources unless strictly necessary.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-convert-segy-to-ovds.md ...es/energy-data-services/how-to-convert-segy-to-ovds.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation assumes the use of GUI tools (Postman) and Python-based utilities (sdutil) without specifying or providing examples for Linux or cross-platform command-line alternatives. There is no mention of Linux-specific instructions, package installation, or shell commands, and all screenshots and instructions implicitly assume a Windows or desktop GUI environment. The only CLI tool (sdutil) is Python-based and cross-platform, but there is no explicit guidance for Linux users (e.g., installation, dependencies, or shell usage).
Recommendations
  • Explicitly state that all tools (Postman, sdutil) are cross-platform and provide installation instructions for Linux (e.g., apt, yum, snap, pip).
  • Include Linux-specific command-line examples (e.g., using curl or wget in bash) alongside or instead of GUI-based instructions.
  • When referencing file paths or commands, use examples that are OS-agnostic or provide both Windows and Linux path formats.
  • Add troubleshooting notes for common Linux issues (e.g., permissions, Python environment setup, dependency installation).
  • Mention that screenshots are from a specific OS and that the UI may look different on Linux.
  • For sdutil, clarify that it can be run on Linux and provide shell command examples (e.g., bash) and installation steps for Linux environments.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/key-rotation-offline.md ...rticles/confidential-computing/key-rotation-offline.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes key rotation using the Azure portal GUI, which is a cross-platform web interface but often aligns with Windows-centric workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux-specific tools or workflows. The absence of CLI or automation examples may disadvantage Linux users or those preferring non-GUI, scriptable approaches.
Recommendations
  • Add Azure CLI examples for key rotation, including full command sequences.
  • Include PowerShell examples for parity, but ensure CLI/Bash examples are presented equally or first.
  • Mention automation options (e.g., using Bash scripts or ARM templates) for Linux users.
  • Clarify that the Azure portal is web-based and cross-platform, but provide alternatives for users who prefer command-line or automated workflows.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-manage-data-security-and-encryption.md ...services/how-to-manage-data-security-and-encryption.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes configuration steps using the Azure Portal (a web GUI) and references Azure-specific tools and workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any instructions or examples for Linux users. The documentation implicitly assumes use of the Azure Portal, which is platform-agnostic but omits parity for users who prefer or require command-line or automation approaches, which are common in Linux environments.
Recommendations
  • Add Azure CLI examples for all key management and configuration steps, as Azure CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are provided in other documentation, ensure Bash equivalents are also included.
  • Explicitly mention that all steps can be performed from any OS via the Azure Portal, but provide links or examples for command-line automation.
  • Include references to scripting and automation guides for Linux users.
  • Where screenshots or UI steps are shown, consider adding equivalent CLI commands as code blocks beneath each step.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/migrate-nested-confidential-vms.md ...fidential-computing/migrate-nested-confidential-vms.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes the migration process using the Azure Portal UI, which is a platform-agnostic web interface, but does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of Linux CLI (e.g., Azure CLI, Bash) or automation examples. This omission may disadvantage Linux users or those who prefer scripting/automation, as the documentation implicitly assumes a GUI-first (often Windows-centric) workflow.
Recommendations
  • Add equivalent Azure CLI command-line instructions for each step, including image capture, gallery creation, and VM deployment in the new region.
  • Provide PowerShell and Bash script examples for users who prefer automation.
  • Explicitly mention that the Azure Portal is cross-platform, but highlight that all steps can also be performed from Linux, macOS, or Windows using CLI tools.
  • Include links to relevant Azure CLI and PowerShell documentation for further reference.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific browser UI or file dialogs).
GitHub Create Pull Request
← Previous Page 74 of 88 Next →