Static Web Apps

79
Total Pages
68
Linux-Friendly Pages
11
Pages with Bias
13.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

52 issues found
Showing 1-25 of 52 flagged pages
Static Web Apps Add an API to Azure Static Web Apps with Azure Functions ...ure-docs/blob/main/articles/static-web-apps/add-api.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits mild Windows bias. While most instructions are cross-platform and use bash commands, Windows-specific tools and patterns are mentioned first or exclusively in some places. For example, the use of Visual Studio Code (which is cross-platform but more popular on Windows), and the explicit mention of 'NVM for Windows' and Winget for installation. There is also a reference to Windows Firewall prompts, with no mention of Linux/macOS equivalents. No PowerShell commands are present, but there is a lack of explicit Linux/macOS instructions or troubleshooting tips where Windows-specific issues are discussed.
Recommendations
  • When mentioning tools like NVM, provide both Linux/macOS and Windows installation instructions side by side, not just a link to NVM for Windows.
  • Where Windows-specific prompts (e.g., Windows Firewall) are mentioned, add notes about what Linux/macOS users might encounter (e.g., ufw, iptables, or no prompt).
  • If referencing package managers (like Winget), also mention Linux/macOS alternatives (e.g., Homebrew, apt, yum).
  • Include troubleshooting tips for common Linux/macOS issues, not just Windows-specific ones.
  • Ensure that all command-line instructions are clearly cross-platform, and explicitly state if any step differs on Linux/macOS.
GitHub Create Pull Request
Static Web Apps Tutorial: Add an Azure Cosmos DB database connection in Azure Static Web Apps ...n/articles/static-web-apps/database-azure-cosmos-db.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While both Bash and PowerShell examples are provided for environment variable setup and npm commands, PowerShell is presented as the only alternative to Bash, with no mention of other Linux shells (e.g., zsh, fish) or macOS-specific instructions. The instructions for opening browser developer tools use the CMD/CTRL notation, which is cross-platform, but the overall flow assumes familiarity with Windows tooling and the Azure portal, which is most commonly used on Windows. There are no explicit Linux-only examples, and the documentation does not address potential differences or issues when running commands on Linux or macOS environments.
Recommendations
  • Add explicit Linux and macOS instructions, including shell-specific examples (e.g., zsh, fish).
  • Clarify that Bash instructions apply to Linux and macOS, and mention any platform-specific caveats.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., npm global install permissions, environment variable persistence).
  • Provide parity in examples for all major platforms, not just Windows (PowerShell) and Bash.
  • Consider referencing Linux package managers (e.g., apt, yum, brew) for installing Node.js/npm if not present.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a MySQL database connection in Azure Static Web Apps ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools such as Azure Data Studio and MySQL Workbench are mentioned first and most prominently for database management, with no explicit mention of Linux-native alternatives (e.g., DBeaver, command-line MySQL client). In command examples, PowerShell is consistently presented alongside Bash, but Bash is not prioritized, and PowerShell is given equal weight, which may confuse Linux users. The instructions for configuring the database and environment variables reference Windows tools and patterns (e.g., Azure Data Studio, PowerShell syntax) before or instead of Linux equivalents.
Recommendations
  • Explicitly mention Linux-native database management tools such as DBeaver, the MySQL CLI, or phpMyAdmin as alternatives to Azure Data Studio and MySQL Workbench.
  • Prioritize Bash examples before PowerShell in code tabs and instructions, or clarify which shell is recommended for Linux/macOS users.
  • Add notes or sections for Linux-specific setup steps, such as installing MySQL client tools via apt/yum and using Linux file paths and environment variable conventions.
  • Include screenshots or references for Linux desktop environments where relevant (e.g., showing DBeaver or MySQL CLI usage).
  • Ensure all instructions and tooling references are cross-platform, or clearly indicate platform-specific steps.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a PostgreSQL database connection in Azure Static Web Apps ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Azure Data Studio (a Microsoft tool, primarily used on Windows) is listed as the main tool for database management, with PgAdmin only mentioned as an alternative. Command-line examples are provided for both Bash and PowerShell, but PowerShell (Windows shell) is given equal prominence, which may not reflect the actual usage patterns of cross-platform developers. The Azure portal (web-based, but often associated with Windows environments) is the only method shown for configuration, with no mention of CLI or Linux-native alternatives. There are no Linux-specific tools or workflows highlighted, and Windows-centric patterns (such as PowerShell and Azure Data Studio) are presented before or alongside their Linux equivalents.
Recommendations
  • Provide explicit examples using Linux-native tools such as psql and PgAdmin, and show how to install and use them on Linux.
  • Include instructions for configuring the database using Azure CLI or PostgreSQL CLI tools, not just the Azure portal.
  • Make Bash the default or primary example for command-line instructions, with PowerShell as an alternative for Windows users.
  • Mention and link to Linux installation guides for all required tools.
  • Clarify that all steps can be performed on Linux, and highlight any platform-specific differences.
  • Consider adding a section or callout for Linux users, summarizing the workflow and tools best suited for Linux environments.
GitHub Create Pull Request
Static Web Apps Tutorial: Publish Azure Static Web Apps using an ARM template ...cles/static-web-apps/publish-azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked for Windows first. The Azure CLI installation instructions list Windows before Linux and macOS. PowerShell is presented as an equal alternative to Azure CLI, but PowerShell is primarily a Windows-centric tool (though cross-platform now). The examples for Azure CLI are written for Bash, but there are no explicit Linux shell examples or mentions of Linux-native editors or tooling. The documentation does not provide Linux-specific guidance or highlight Linux workflows, and Windows tools/patterns (PowerShell, Visual Studio Code) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add explicit Linux shell examples (e.g., bash, zsh) and clarify that Azure CLI commands work on Linux and macOS.
  • Mention Linux-native editors (e.g., Vim, Emacs, nano) as alternatives to Visual Studio Code, or at least acknowledge their use.
  • Reorder installation instructions to present all platforms equally, or start with Linux to balance historical bias.
  • Clarify that PowerShell is available cross-platform, but also suggest Bash or other Linux-native shells for Linux users.
  • Include screenshots or instructions for resource group management using Azure CLI on Linux/macOS, not just the Azure portal.
  • Add notes or sections specifically for Linux users to ensure parity and inclusivity.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a PostgreSQL database connection in Azure Static Web Apps ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. It consistently references Azure Data Studio—a Microsoft tool most commonly used on Windows—as the primary database client, mentioning PgAdmin only as an alternative. In command-line examples, both Bash and PowerShell are provided, but PowerShell is always listed second, and there is no mention of Linux-specific shell environments or tools. The tutorial assumes use of the Azure portal (web-based, but often associated with Windows workflows) and does not discuss Linux-native database management tools (e.g., psql) or development environments. There are no explicit Linux-only examples, and the overall workflow is oriented toward Windows-centric tools and patterns.
Recommendations
  • Provide equal prominence to Linux-native tools such as psql and PgAdmin, including explicit instructions and screenshots for these tools.
  • Include Linux-specific shell examples (e.g., zsh, fish) and clarify any differences in environment variable syntax.
  • Add a section on installing and using Azure Data Studio and PgAdmin on Linux, or suggest other open-source alternatives.
  • Ensure that Bash examples are clearly marked as cross-platform and not just for macOS/Linux.
  • Where possible, avoid assuming the use of Windows-only tools or workflows; mention platform-agnostic alternatives.
  • Consider including troubleshooting tips for common Linux issues (e.g., firewall configuration, package installation).
GitHub Create Pull Request
Static Web Apps Tutorial: Add a MySQL database connection in Azure Static Web Apps ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-centric tools like Azure Data Studio are presented as the default for database management, with alternatives (MySQL Workbench) mentioned only secondarily. Command examples are consistently provided for both Bash and PowerShell, but PowerShell is always listed after Bash, suggesting a slight 'windows_second' pattern rather than 'windows_first'. However, the primary database management workflow is described using Azure Data Studio, which is a Microsoft product most commonly used on Windows. There is no mention of Linux-native tools (e.g., mysql CLI, DBeaver) or Linux-specific setup steps. The tutorial assumes use of the Azure portal, which is cross-platform, but the local development environment and tooling recommendations lean toward Windows.
Recommendations
  • Add explicit examples and instructions for Linux users, including use of native MySQL CLI tools (e.g., mysql, mysqladmin) for database creation and querying.
  • Mention and provide examples for cross-platform database management tools such as DBeaver or the MySQL CLI, not just Azure Data Studio and MySQL Workbench.
  • Clarify that Azure Data Studio is available on Linux and macOS, or suggest alternatives for those platforms.
  • Where PowerShell and Bash examples are given, consider listing Bash first for Linux parity, or explicitly state that both shells are supported equally.
  • Include troubleshooting or setup notes for Linux environments, such as installing required packages or configuring firewalls.
GitHub Create Pull Request
Static Web Apps Tutorial: Publish Azure Static Web Apps using an ARM template ...cles/static-web-apps/publish-azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits mild Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked for Windows. The Azure CLI installation instructions list Windows first, and Azure PowerShell (a Windows-centric tool) is presented as an equal alternative to Azure CLI throughout, with full example parity. There is no explicit Linux shell example (e.g., bash script), and the CLI examples are written for Bash but not shown in a Linux context. No Linux-specific editors or tools are mentioned.
Recommendations
  • Add explicit Linux shell examples (e.g., bash scripts) and clarify CLI usage on Linux.
  • Mention cross-platform editors (e.g., Vim, nano) or clarify that Visual Studio Code is available on Linux and macOS.
  • List installation instructions for Azure CLI in a neutral order (not Windows first).
  • Clarify that Azure PowerShell is cross-platform, or suggest alternatives for Linux users.
  • Provide screenshots or instructions for resource group deletion using Azure CLI, not just the Azure portal.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench), presenting PowerShell examples alongside Bash, and referencing the Azure portal for configuration. While Bash examples are present, there is no mention of Linux-native database tools (e.g., mysql CLI), and the tooling recommendations and screenshots are Windows-oriented. Linux alternatives and workflows are not discussed or shown, and the order of presentation often puts Windows tools first.
Recommendations
  • Explicitly mention and provide examples using Linux-native tools such as the mysql CLI for database management and querying.
  • Include screenshots and instructions for accessing the Azure portal from Linux browsers or using Azure CLI for configuration tasks.
  • List Bash/Linux commands before PowerShell commands where possible, or clarify parity between the two.
  • Suggest Linux equivalents to Azure Data Studio and MySQL Workbench, such as DBeaver or direct CLI usage.
  • Add a section or callouts for Linux users, highlighting any differences or additional steps required.
  • Ensure that all steps (especially those involving environment variables and npm usage) are tested and documented for Linux shells (e.g., zsh, fish) as well as Bash.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits moderate Windows bias. Azure Data Studio (a Microsoft tool most commonly used on Windows) is presented as the primary database client, with PgAdmin only mentioned as an alternative. In command-line instructions, both Bash and PowerShell examples are provided, but PowerShell (Windows) is always listed second, which is less severe but still a subtle ordering bias. The tutorial relies heavily on Azure portal UI instructions, which are platform-agnostic but tend to be more familiar to Windows users. There are no explicit Linux-only examples or recommendations for Linux-native tools (e.g., psql CLI), and no mention of macOS-specific considerations.
Recommendations
  • Provide explicit examples using Linux-native tools such as the psql command-line client for PostgreSQL, alongside Azure Data Studio and PgAdmin.
  • Include instructions for installing and using PgAdmin and psql on Linux and macOS, not just Azure Data Studio.
  • When listing command-line examples, alternate the order of Bash and PowerShell, or clarify that Bash is for Linux/macOS and PowerShell is for Windows.
  • Add a section or note on using the Azure portal and CLI from Linux/macOS environments, including browser compatibility and CLI installation.
  • Ensure parity in troubleshooting steps for Linux users (e.g., firewall rules, connection string formatting, environment variable setup).
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/publish-azure-resource-manager.md ...cles/static-web-apps/publish-azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked (which are Windows-centric by default). The Azure CLI installation links list Windows first, and PowerShell is presented as an equal alternative to Azure CLI, despite PowerShell being primarily a Windows tool. Examples for both Azure CLI and PowerShell are provided, but PowerShell is not as commonly used on Linux. There is no explicit Linux shell example (e.g., Bash script), and no mention of Linux-native editors or workflows.
Recommendations
  • Add explicit Bash shell examples and clarify that Azure CLI commands work cross-platform.
  • Mention Linux-native editors (e.g., Vim, nano) as alternatives for editing ARM templates.
  • Present installation instructions for Azure CLI in a neutral order (not Windows first).
  • Clarify that PowerShell is optional and less common on Linux, and consider focusing on Azure CLI for cross-platform parity.
  • Include notes or examples for macOS and Linux users where workflows or commands may differ.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/publish-azure-resource-manager.md ...cles/static-web-apps/publish-azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked for Windows. In the prerequisites, the Azure CLI installation instructions list Windows first, followed by Linux and macOS. Azure PowerShell is mentioned as an alternative to Azure CLI, and PowerShell examples are provided alongside Azure CLI throughout the deployment steps. There is no explicit Linux shell example (e.g., Bash, zsh) beyond a note that CLI examples are written for Bash, and no mention of Linux-native editors or tooling. The overall structure and examples prioritize Windows tools and workflows, with Linux alternatives mentioned but not equally emphasized.
Recommendations
  • Provide explicit Bash/zsh examples for Linux users, including variable assignment and file path conventions.
  • Include installation and usage instructions for popular Linux editors (e.g., Vim, nano) or mention their suitability for editing ARM templates.
  • Reorder installation instructions to avoid listing Windows first; consider grouping by platform or listing alphabetically.
  • Add notes or sections highlighting Linux-specific considerations, such as file permissions, environment variables, and shell differences.
  • Ensure parity in example commands, showing both Windows (PowerShell) and Linux (Bash) syntax side-by-side where appropriate.
  • Mention cross-platform editors and tools (e.g., VS Code, Atom, Sublime Text) as suitable for all operating systems.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for MySQL management, with MySQL Workbench mentioned only as an alternative. Step-by-step instructions and screenshots focus on Azure Data Studio. Command-line examples are provided for both Bash and PowerShell, but PowerShell is given equal prominence, which is uncommon for Linux/macOS users. There are no explicit Linux/macOS-specific instructions or tool recommendations (e.g., mysql CLI, TablePlus, DBeaver). The workflow assumes use of the Azure portal and Microsoft tooling, which may be less familiar or accessible to Linux users.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including use of the mysql CLI and other cross-platform database tools (e.g., DBeaver, TablePlus).
  • List Bash examples before PowerShell, as Bash is the default shell on Linux/macOS.
  • Include screenshots or instructions for database creation and querying using the mysql CLI.
  • Mention installation and usage of Azure Data Studio on Linux/macOS, or recommend alternative open-source tools.
  • Clarify that Azure Data Studio is available cross-platform, and provide links or steps for Linux/macOS installation.
  • Avoid assuming the use of Windows-specific tools or workflows; ensure parity in tool recommendations and instructions.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools such as Azure Data Studio are listed first and described in detail, while cross-platform alternatives like PgAdmin are mentioned only as secondary options. Command-line examples consistently present PowerShell syntax alongside Bash, but PowerShell is always listed second, which is less severe but still notable. The tutorial assumes use of the Azure portal (web-based, but often associated with Windows workflows) and does not provide explicit Linux-native alternatives for database management or configuration tasks. There are no Linux-specific troubleshooting tips or references to Linux package managers for installing required tools.
Recommendations
  • Provide equal prominence and step-by-step instructions for cross-platform and Linux-native tools (e.g., PgAdmin, psql CLI) alongside Azure Data Studio.
  • Include installation instructions for required tools using Linux package managers (apt, yum, etc.), not just links to Azure Data Studio.
  • Add troubleshooting notes or tips for common Linux-specific issues (e.g., firewall configuration, environment variable syntax differences).
  • Consider listing Bash examples before PowerShell, or at least alternating the order, to avoid implicit prioritization.
  • Clarify that all steps are cross-platform where applicable, and note any platform-specific caveats.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft tool, primarily Windows-focused) is recommended first for MySQL management, with MySQL Workbench only mentioned as an alternative. Command examples are consistently provided for both Bash and PowerShell, but PowerShell is always presented alongside Bash, rather than offering Linux-specific alternatives (e.g., native Linux tools or workflows). The use of Azure Data Studio and the Azure portal (both Microsoft-centric tools) is emphasized throughout, with no mention of Linux-native database management tools (such as the mysql CLI or Linux desktop clients) or Linux-specific configuration steps. There are no explicit Linux examples or guidance for Linux users, and the workflow assumes familiarity with Windows tooling and patterns.
Recommendations
  • Provide explicit Linux examples and workflows, such as using the mysql CLI for database management and querying, and instructions for configuring environment variables in Linux shells (e.g., Bash, Zsh) without referencing PowerShell.
  • List Linux-native tools (e.g., DBeaver, mysql CLI) as first-class options for database management, not just as alternatives.
  • Include screenshots and instructions for Linux environments (e.g., Ubuntu, Fedora) when demonstrating Azure portal or CLI usage.
  • Clarify any platform-specific differences in steps (such as file paths, environment variable syntax, or CLI installation commands) for Linux users.
  • Consider adding a 'Platform considerations' section that highlights differences and best practices for both Windows and Linux users.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for interacting with PostgreSQL, with PgAdmin only briefly mentioned as an alternative. Command-line examples are provided for both Bash and PowerShell, but PowerShell is given equal prominence, which may not reflect the usage patterns of Linux/macOS developers. The instructions for configuring the database and accessing the Azure portal are written from a perspective familiar to Windows users, with no mention of Linux-specific tools or workflows (e.g., psql, Linux desktop environments, or CLI-only workflows).
Recommendations
  • Provide explicit examples using Linux-native tools such as psql for database creation and querying, alongside Azure Data Studio and PgAdmin.
  • Clarify that Azure Data Studio is cross-platform, and offer installation instructions for Linux and macOS users.
  • Include screenshots and instructions for Linux desktop environments (e.g., GNOME, KDE) when referencing GUI tools.
  • When listing command-line examples, consider listing Bash first and PowerShell second, or clarify which is most common for Linux/macOS users.
  • Add a section or note on using the Azure CLI for portal-related steps, as many Linux users prefer CLI workflows.
  • Ensure parity in troubleshooting and cleanup instructions for Linux environments (e.g., using psql to drop tables).
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-postgresql.md ...b/main/articles/static-web-apps/database-postgresql.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft/Windows-centric tool) is presented as the primary tool for database management, with PgAdmin only mentioned as an alternative. In all code examples (git, npm, environment variable setting), both Bash and PowerShell are shown, but PowerShell is always presented second, not first. However, the documentation does not provide Linux-specific troubleshooting or mention Linux-native tools (like psql CLI) for PostgreSQL management. The focus on Azure Data Studio and the lack of Linux-first or CLI-native workflows indicate a Windows-centric approach.
Recommendations
  • Provide equal prominence to Linux-native tools such as psql CLI and PgAdmin, including step-by-step instructions for these tools.
  • When listing tools for database management, mention cross-platform and Linux-native tools first or equally (e.g., 'You may use Azure Data Studio, PgAdmin, or the psql command-line tool').
  • Include Linux-specific troubleshooting tips or notes where relevant (e.g., firewall configuration, environment variable syntax).
  • For all command examples, consider using a tabbed interface with Bash (Linux/macOS) as the default or first tab, or explicitly state that both shells are supported equally.
  • Add a section or callout for users developing on Linux, highlighting any differences or additional steps required.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench) for database management, omitting explicit Linux-native alternatives (such as the MySQL CLI). While both Bash and PowerShell examples are provided for CLI commands, the database tooling and portal navigation instructions assume a GUI workflow more common on Windows. There are no explicit Linux-specific instructions or screenshots, and the documentation does not mention Linux package managers or command-line tools for MySQL database management.
Recommendations
  • Include explicit instructions and examples for using the MySQL CLI (mysql, mysqladmin) for database creation, querying, and data manipulation, especially for Linux users.
  • Mention Linux-native tools (e.g., DBeaver, command-line MySQL clients) alongside Azure Data Studio and MySQL Workbench.
  • Provide package manager installation commands for Azure Data Studio, MySQL CLI, or other recommended tools on Linux (e.g., apt, yum, snap).
  • Add screenshots or terminal output examples from Linux environments where appropriate.
  • Clarify that all steps can be performed on Linux, and highlight any differences or prerequisites for Linux users.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/local-development.md ...lob/main/articles/static-web-apps/local-development.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Code Heavy Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by emphasizing Visual Studio Code (a Microsoft product popular on Windows) for debugging, and by not providing any Linux- or macOS-specific instructions, terminal commands, or troubleshooting notes. All examples are generic but implicitly assume a Windows-centric workflow, especially in the debugging section. There are no explicit references to Windows-only tools or PowerShell, but the absence of Linux/macOS parity in examples and tool recommendations is notable.
Recommendations
  • Include explicit instructions or notes for Linux and macOS users, such as alternative editors (e.g., VS Code, Vim, or JetBrains IDEs) and terminal usage.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, environment variables, or port conflicts).
  • Provide example commands or screenshots from Linux/macOS terminals to demonstrate cross-platform compatibility.
  • Mention that Visual Studio Code is cross-platform, and suggest alternatives for users who may not use it.
  • Clarify that all CLI commands are platform-agnostic, and note any platform-specific differences if they exist.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/add-api.md ...ure-docs/blob/main/articles/static-web-apps/add-api.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the way it references Windows-specific tools and installation patterns. For example, the Node.js version manager (nvm) is mentioned with a Windows-specific alternative (NVM for Windows) and installation via Winget, a Windows package manager. There is also a reference to Windows Firewall prompts, which is not relevant to Linux or macOS users. No explicit Linux or macOS-specific instructions or troubleshooting are provided, and the only OS-specific tool mentioned is for Windows. While most commands are cross-platform, the lack of parity in OS-specific guidance and the order of tool recommendations indicate a subtle Windows-first bias.
Recommendations
  • When mentioning tools like nvm, provide equal visibility to Linux/macOS installation methods (e.g., Homebrew for macOS, apt/yum for Linux) alongside Windows options.
  • If referencing Windows Firewall prompts, add notes about equivalent network/security prompts or considerations on Linux and macOS, or clarify that this step is Windows-specific.
  • Include troubleshooting tips or environment setup notes for Linux/macOS users, such as permissions, path configuration, or common issues.
  • Where possible, avoid mentioning Windows-specific tools (like Winget) without also mentioning cross-platform or Linux/macOS alternatives.
  • Consider adding a short section or callout for Linux/macOS users in the prerequisites or setup steps to ensure parity and inclusivity.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-mysql.md ...s/blob/main/articles/static-web-apps/database-mysql.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (Azure Data Studio, MySQL Workbench), referencing the Azure portal UI, and providing PowerShell examples alongside Bash. There is no mention of Linux-native tools (e.g., mysql CLI, DBeaver) or headless/server workflows, and the prerequisite tooling and workflow instructions assume a GUI environment typical of Windows users. Linux alternatives are not offered, and the order of examples often lists Windows/PowerShell first.
Recommendations
  • Explicitly mention and provide examples for Linux-native tools such as the mysql CLI, DBeaver, or other cross-platform database clients.
  • Include instructions for performing database setup and queries using the mysql command-line client, especially for headless/server environments.
  • When listing tools, avoid Windows-first ordering; instead, present cross-platform options or group by OS.
  • For shell commands, always provide Bash examples first or equally, and clarify which commands are cross-platform.
  • Add a section or notes for users working in Linux environments, including how to install required tools and perform equivalent actions.
  • Reference the Azure CLI for portal actions where possible, as it is cross-platform.
  • Ensure screenshots and UI references are supplemented with CLI alternatives for users who may not use the Azure portal.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a MySQL database connection in Azure Static Web Apps ...s/blob/main/articles/static-web-apps/database-mysql.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft tool, most commonly used on Windows) is presented as the primary tool for MySQL management, with MySQL Workbench mentioned only as an alternative. In step-by-step instructions, GUI actions (right-click, select, etc.) are described in the context of Azure Data Studio, which is more familiar to Windows users. Command-line examples are provided for both Bash and PowerShell, but PowerShell is given equal prominence, which is less relevant for Linux/macOS users. There are no explicit Linux/macOS-specific instructions or screenshots, and the workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide explicit instructions and screenshots for Linux/macOS users, using native tools such as the MySQL CLI or cross-platform GUIs.
  • List MySQL Workbench and the MySQL CLI as equal alternatives to Azure Data Studio, and provide example commands for them.
  • Clarify which steps are platform-agnostic and which require adaptation for Linux/macOS.
  • Consider presenting Bash examples before PowerShell, as Bash is the default shell on Linux/macOS.
  • Add a note about installing and using Azure Data Studio on Linux/macOS, or link to platform-specific installation guides.
GitHub Create Pull Request
Static Web Apps Tutorial: Add a PostgreSQL database connection in Azure Static Web Apps ...b/main/articles/static-web-apps/database-postgresql.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Azure Data Studio (a Microsoft tool) is recommended as the primary database client, with PgAdmin only mentioned as an alternative. Command-line examples are consistently provided for both Bash and PowerShell, but PowerShell is always shown second. There are no Linux/macOS-specific instructions or troubleshooting notes, and the workflow assumes familiarity with Azure portal and Microsoft-centric tooling.
Recommendations
  • Provide explicit instructions and screenshots for using PgAdmin or psql CLI for database creation and querying, especially for Linux/macOS users.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., networking, environment variable syntax differences).
  • Add a section listing alternative tools for Linux/macOS, such as DBeaver or native PostgreSQL CLI.
  • Consider showing Bash examples first or alternating order to avoid implicit prioritization of Windows.
  • Clarify that all steps can be completed on Linux/macOS and highlight any platform-specific caveats.
GitHub Create Pull Request
Static Web Apps Tutorial: Add an Azure SQL database connection in Azure Static Web Apps ...ob/main/articles/static-web-apps/database-azure-sql.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for shell commands, but PowerShell is always presented immediately after Bash, indicating a slight 'windows_first' bias in ordering. There are no Linux-specific tools or instructions, and the only shell alternatives shown are Bash and PowerShell, with no mention of other common Linux shells (e.g., zsh, fish) or Linux-specific package managers. The Azure Portal instructions are platform-neutral, but the shell command sections could be improved for Linux parity.
Recommendations
  • Explicitly mention Linux as a supported platform in prerequisites and instructions.
  • Add notes or examples for common Linux shells beyond Bash, such as zsh or fish, if relevant.
  • Include instructions for Linux-specific package managers (e.g., apt, yum) for installing Node.js/npm if not already present.
  • Consider alternating the order of Bash and PowerShell examples, or grouping them together under a 'Shell (Bash/PowerShell)' heading to avoid implicit prioritization.
  • Add troubleshooting tips for Linux users, such as common permission issues or environment variable handling differences.
GitHub Create Pull Request
Static Web Apps Deploy your web app to Azure Static Web Apps. .../main/articles/static-web-apps/deploy-web-framework.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally presents cross-platform instructions, but there is subtle Windows bias. Visual Studio Code is recommended as the text editor, which is a Microsoft product, and the environment variable examples list Windows shells (PowerShell, CMD) after Linux/macOS shells but still include them. No explicit Linux-only tools or editors are mentioned, and the screenshots and instructions do not show Linux-specific environments. There are no missing Linux examples, but Windows tools are referenced and the editor recommendation is Windows-centric.
Recommendations
  • Recommend a truly cross-platform text editor (e.g., VS Code, Sublime Text, Vim) or mention alternatives for Linux users.
  • Include screenshots or terminal prompts from Linux/macOS environments alongside Windows examples.
  • Explicitly state that all commands work on Linux, macOS, and Windows, and highlight any platform-specific differences.
  • Add a note about installing Azure CLI on Linux and macOS, not just linking to the generic install page.
  • Consider listing Linux/macOS shells first in environment variable examples, or randomize the order to avoid implicit prioritization.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →