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 26-50 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
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific tools (such as 'NVM for Windows' and Winget) before or in addition to their Linux/macOS equivalents, and by mentioning Windows Firewall prompts. However, most instructions and examples are cross-platform and use bash commands, with no exclusive use of PowerShell or Windows-only command-line patterns.
Recommendations
  • When mentioning Node.js version managers, list cross-platform tools (like nvm) first, and clarify that nvm is available for Linux/macOS, while 'nvm-windows' is for Windows.
  • Avoid referencing Windows-specific package managers (like Winget) without mentioning Linux/macOS alternatives (such as apt, brew, or snap).
  • If mentioning Windows Firewall prompts, add a note about possible firewall prompts on Linux/macOS (such as ufw or system dialogs), or clarify that this step is Windows-specific.
  • Continue using bash commands and avoid PowerShell-specific syntax unless providing equivalent Linux/macOS instructions.
  • Where possible, provide parity in troubleshooting or setup notes for both Windows and Linux/macOS environments.
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-10 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 command-line steps, but PowerShell is consistently presented alongside Bash, sometimes immediately after, and is given equal prominence. There are no Linux-specific tools, troubleshooting steps, or environment considerations mentioned. The Azure Portal instructions are platform-neutral, but the command-line instructions show a slight Windows bias by always including PowerShell and never mentioning Linux-specific shells (e.g., zsh, fish) or Linux environment nuances. There are no examples or notes for Linux-specific database management tools or local development patterns.
Recommendations
  • Explicitly mention Linux as a supported development environment in the prerequisites and throughout the tutorial.
  • Add notes or examples for Linux-specific shells (e.g., zsh, fish) where environment variable syntax may differ.
  • Include troubleshooting tips or links for common Linux issues (e.g., firewall configuration, package installation).
  • Reference Linux-native database management tools (e.g., sqlcmd, Azure Data Studio on Linux) where appropriate.
  • Consider listing Bash examples first, as Bash is the default shell on most Linux systems.
  • Add a section or note about local database development on Linux, including setup and connectivity considerations.
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
Medium Priority View Details →
Scanned: 2026-01-10 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 environment variable setup and CLI usage, but consistently lists Bash first, then PowerShell. There are no Linux-specific tools or patterns mentioned, but the inclusion of PowerShell examples suggests a Windows-centric approach. No Linux-only examples or troubleshooting are provided, and the documentation does not mention WSL, macOS, or Linux-specific issues. The CLI commands and workflow are cross-platform, but the explicit PowerShell support and ordering may indicate a mild Windows bias.
Recommendations
  • Explicitly mention Linux and macOS compatibility in prerequisites and CLI instructions.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, npm global install paths).
  • Consider listing Bash and PowerShell examples in alternating order or grouping them together to avoid 'windows_first' bias.
  • Include a note about using WSL for Windows users who prefer a Linux-like environment.
  • Provide links to platform-specific setup guides for npm and CLI tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally maintains cross-platform parity, using bash-based commands and referencing Linux, macOS, Windows, and WSL as supported platforms. However, there is mild Windows bias: Visual Studio Code is recommended as the text editor (a Microsoft product popular on Windows), and Windows-specific environment variable setting commands (PowerShell and CMD) are included before or alongside Linux/macOS equivalents. No Linux example is missing, but Windows tools and patterns are mentioned, and Windows-specific instructions are present.
Recommendations
  • Explicitly mention alternative text editors for Linux/macOS users (e.g., Vim, Sublime Text, Atom) alongside Visual Studio Code.
  • When listing environment variable commands, present bash/zsh (Linux/macOS) examples first, followed by Windows (PowerShell/CMD) examples.
  • Clarify that all commands are cross-platform and note any platform-specific caveats.
  • Consider including screenshots or references for Linux/macOS terminals, not just generic or Windows-centric visuals.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows mild Windows bias by mentioning Windows-specific tools (NVM for Windows, installation via Winget) and referencing Windows Firewall prompts. These Windows details are presented before or without equivalent Linux/macOS instructions. However, most CLI and code examples are cross-platform and do not use PowerShell or Windows-only commands.
Recommendations
  • Add explicit instructions for Linux and macOS where Windows-specific tools are mentioned (e.g., NVM installation, firewall prompts).
  • When referencing NVM, clarify installation steps for Linux/macOS and Windows equally, rather than listing Windows first.
  • For firewall prompts, mention that Linux/macOS users may need to adjust local firewall settings or confirm network access, or note that this step is Windows-specific.
  • Where installation methods are given (e.g., Winget), provide equivalent package manager commands for Linux (apt, yum) and macOS (brew).
  • Review all tips and notes to ensure parity between Windows, Linux, and macOS, especially for tool installation and environment setup.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-sql.md ...ob/main/articles/static-web-apps/database-azure-sql.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 command-line operations, but PowerShell is always listed second, and there is no mention of Linux-specific tools or workflows. All instructions for database setup and management are given via the Azure portal, which is platform-agnostic, but there are no explicit references to Linux environments or tools (e.g., Azure CLI, local SQL tools for Linux). The examples and instructions implicitly assume a Windows or cross-platform environment, but do not demonstrate Linux parity beyond Bash commands.
Recommendations
  • Explicitly mention Linux as a supported development environment in the prerequisites and throughout the tutorial.
  • Provide examples using Azure CLI for database setup and management, which is commonly used on Linux.
  • Include instructions or notes for using local SQL tools on Linux (e.g., sqlcmd, Azure Data Studio) for database operations.
  • Clarify that Bash commands are applicable on Linux/macOS and PowerShell commands are for Windows, or provide a 'Linux/macOS' tab instead of just 'Bash'.
  • Add troubleshooting or environment setup notes specific to Linux (e.g., installing npm, setting environment variables, using the Static Web Apps CLI on Linux).
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md ...n/articles/static-web-apps/database-azure-cosmos-db.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 environment variable setup and CLI usage, but consistently lists Bash first and PowerShell second. There are no Linux-specific tools or patterns mentioned, but the parity between Bash and PowerShell is maintained throughout. No Windows-only tools are referenced, and no steps are exclusive to Windows. However, the ordering and inclusion of PowerShell examples may suggest a slight Windows-first bias, especially as PowerShell is primarily associated with Windows environments, though it is available cross-platform.
Recommendations
  • Explicitly mention Linux and macOS compatibility in prerequisites and CLI instructions.
  • Provide a brief note clarifying that PowerShell examples are also valid for PowerShell Core on Linux/macOS.
  • Consider alternating the order of Bash and PowerShell examples or grouping them under 'Shell (Bash/PowerShell)' to avoid perceived prioritization.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, npm installation differences).
  • Include a table or section listing supported platforms for all CLI commands and environment variable setup.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/deploy-web-framework.md .../main/articles/static-web-apps/deploy-web-framework.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 a subtle Windows bias. Visual Studio Code is recommended as the text editor, which is a Microsoft product, and CMD/PowerShell environment variable commands are included alongside bash/csh. The Windows-specific instructions (CMD/PowerShell) appear after Linux/macOS examples, but their inclusion without explicit Linux parity explanations may reinforce a Windows-centric perspective. There are no missing Linux examples, and the main workflow uses bash commands, which are cross-platform.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux/macOS and suggest other popular editors (e.g., Sublime Text, Vim, Atom) to avoid implying a Windows-only workflow.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide guidance for users of WSL or native Linux terminals.
  • Consider listing Linux/macOS instructions first or in parallel with Windows instructions, rather than always including Windows tools.
  • Add a short note explaining how to open a terminal on each platform (e.g., Terminal on macOS/Linux, Command Prompt/PowerShell on Windows).
  • Ensure screenshots and examples do not implicitly favor Windows environments.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias by mentioning Windows-specific tools (NVM for Windows, Winget) and referencing Windows Firewall prompts. These references appear before or without equivalent Linux/macOS instructions. However, most command-line examples and tooling are cross-platform, and there are no exclusive PowerShell or Windows-only code samples.
Recommendations
  • When mentioning Node.js version managers, provide equal visibility to Linux/macOS tools (e.g., 'nvm' for Unix, 'NVM for Windows' for Windows) and installation instructions for both platforms.
  • For package installation, include Linux/macOS equivalents (e.g., Homebrew, apt, yum) alongside Winget for Windows.
  • Clarify that firewall prompts may appear on Windows, and note what Linux/macOS users should expect (e.g., no prompt, or how to open ports if needed).
  • Add troubleshooting notes for Linux/macOS users where Windows-specific behavior is described.
  • Ensure that all tool installation and usage instructions are explicitly cross-platform, or provide platform-specific tabs/sections.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-sql.md ...ob/main/articles/static-web-apps/database-azure-sql.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 command-line operations, but consistently lists Bash first, followed by PowerShell. There are no Linux-specific tools or patterns mentioned, but the inclusion of PowerShell throughout may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux. No explicit Linux-only examples or troubleshooting steps are present, and Azure Portal instructions are platform-neutral.
Recommendations
  • Consider including explicit Linux troubleshooting steps or notes, especially for common issues like firewall configuration or SQL connectivity from Linux environments.
  • Add a brief note clarifying that PowerShell commands are also available on Linux, or provide examples using other popular Linux shells (e.g., zsh, fish) if relevant.
  • Where possible, mention any Linux-specific tools or alternatives (e.g., using Azure CLI in Bash vs. PowerShell).
  • Ensure that Bash and PowerShell examples are presented with equal prominence, or alternate the order to avoid implicit prioritization.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md ...n/articles/static-web-apps/database-azure-cosmos-db.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. In sections where shell commands are provided, both Bash and PowerShell examples are given, but PowerShell is always presented second. The tutorial assumes usage of the Azure portal (a web interface, platform-neutral), but when it comes to environment variable setup and CLI usage, Windows/PowerShell is given equal but not primary treatment. There are no Linux-specific tools or patterns mentioned, but the documentation does not provide Linux-only examples or address Linux-specific concerns (such as file permissions or common Linux shells beyond Bash).
Recommendations
  • Present Bash and PowerShell examples in parallel tabs, or randomize their order to avoid implicit prioritization.
  • Explicitly mention that Bash examples work on Linux and macOS, and PowerShell examples work on Windows (and optionally on Linux).
  • Add notes about common Linux shell alternatives (e.g., zsh, fish) and how commands may differ.
  • Include troubleshooting tips for Linux users (e.g., file permissions, environment variable persistence).
  • Ensure that all CLI commands are tested and work identically on Linux, macOS, and Windows.
  • Consider adding a section or appendix for Linux-specific best practices when working with Azure Static Web Apps.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/deploy-web-framework.md .../main/articles/static-web-apps/deploy-web-framework.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally uses cross-platform commands and avoids Windows-specific tooling in its main flow. However, there is a subtle Windows bias: Visual Studio Code is recommended as the editor (which, while cross-platform, is often associated with Windows), and in the environment variable section, Windows command shells (PowerShell and CMD) are listed after bash/csh, but are present. There are no examples that are exclusively Windows or PowerShell, and Linux/macOS commands are given equal or greater prominence. No Linux-specific tools or editors are recommended, and the editor recommendation is Windows-centric.
Recommendations
  • Explicitly mention Linux/macOS editors (e.g., Vim, Emacs, GNOME Text Editor) alongside Visual Studio Code.
  • Clarify that Visual Studio Code is cross-platform and provide links to its Linux/macOS installation guides.
  • In environment variable examples, consider listing bash/csh/zsh first, but also note that PowerShell is available on Linux/macOS.
  • Add a note that all commands work on Linux, macOS, and Windows, and highlight any platform-specific caveats if present.
  • Where screenshots or instructions reference Windows UI elements, provide Linux/macOS equivalents.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-sql.md ...ob/main/articles/static-web-apps/database-azure-sql.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for command-line steps, but consistently lists Bash first, then PowerShell. There is no evidence of exclusive use of Windows tools or missing Linux examples; however, the presence of PowerShell examples throughout and the explicit tabbing for PowerShell indicates a slight Windows bias. The Azure Portal instructions are platform-neutral, but the CLI instructions could be improved for Linux parity.
Recommendations
  • Explicitly mention that all CLI steps work on Linux, macOS, and Windows, and clarify any platform-specific differences if they exist.
  • Consider including a brief note or section for users on Linux/macOS, confirming that Bash instructions are applicable and that no additional steps are required.
  • If any steps have platform-specific caveats (e.g., environment variable syntax, npm installation), highlight these in a dedicated 'Platform differences' note.
  • Ensure that screenshots and UI references do not imply a Windows-only environment.
  • If possible, add a table or summary at the start of the CLI section indicating supported platforms for each command.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md ...n/articles/static-web-apps/database-azure-cosmos-db.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell command examples for environment variable setup, npm usage, and CLI commands, but consistently lists Bash first. There is no exclusive use of Windows tools, and Linux (Bash) is always represented. However, the presence of PowerShell tabs and examples throughout, and the order in which Bash is always presented before PowerShell, may indicate a slight bias towards Windows users by ensuring PowerShell parity, even though the commands are cross-platform. There are no missing Linux examples, and no exclusive mention of Windows-only tools or patterns.
Recommendations
  • Continue to provide both Bash and PowerShell examples to ensure parity.
  • Consider explicitly mentioning that Bash commands work on Linux and macOS, and PowerShell commands are for Windows, to clarify platform applicability.
  • If possible, add a short section at the start of the tutorial explaining how to choose between Bash and PowerShell based on the user's OS.
  • Ensure that any screenshots or UI references are not Windows-specific, or provide Linux/macOS equivalents if UI differences exist.
  • Maintain the current practice of not favoring Windows-specific tools or patterns, and avoid implying that PowerShell is the default unless it truly is.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/getting-started.md .../blob/main/articles/static-web-apps/getting-started.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Visual Studio Code UI navigation patterns (e.g., 'File > Open Folder') and omitting any mention of Linux-specific instructions or terminal-based workflows. There are no examples or notes for Linux users, nor are there alternative instructions for common Linux environments. The reliance on GUI-based steps and lack of parity for Linux users may hinder accessibility for non-Windows developers.
Recommendations
  • Add explicit instructions or notes for Linux (and macOS) users, especially where UI navigation or keyboard shortcuts may differ.
  • Include terminal-based alternatives for key steps (e.g., opening folders, installing extensions) that are common in Linux workflows.
  • Where possible, provide screenshots or examples from Linux environments in addition to Windows.
  • Clarify that Visual Studio Code and the Azure extension are cross-platform, and link to platform-specific installation guides.
  • Review all steps for assumptions about the user's operating system and add parity for Linux users.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/database-azure-cosmos-db.md ...n/articles/static-web-apps/database-azure-cosmos-db.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 provides both Bash and PowerShell command examples for environment variable setup, npm usage, and CLI commands. However, in each case, Bash (Linux/macOS) instructions are presented before PowerShell (Windows), which is a positive sign for Linux parity. There is no exclusive use of Windows tools, and no steps are limited to Windows. However, the inclusion of PowerShell-specific tabs and commands throughout the tutorial, even for simple npm or CLI usage, may indicate a slight bias toward Windows users, as PowerShell is not the default shell on all Windows systems and is rarely used on Linux/macOS. No Linux-specific tools or patterns are highlighted, and there are no Linux-only troubleshooting tips or considerations.
Recommendations
  • Continue presenting Bash instructions first to reinforce Linux parity.
  • Consider adding explicit notes about shell compatibility (e.g., Bash, Zsh, Fish) for Linux/macOS users.
  • Where possible, provide a generic shell example and mention that PowerShell is optional for Windows users who prefer it.
  • Include troubleshooting tips or common issues for Linux users, such as file permissions or npm installation differences.
  • Ensure that screenshots and UI references are OS-agnostic or include both Windows and Linux/macOS visuals where relevant.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/getting-started.md .../blob/main/articles/static-web-apps/getting-started.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 Windows-first bias by referencing Visual Studio Code UI navigation patterns (e.g., 'File > Open Folder') and omitting any mention of Linux-specific instructions or terminal-based workflows. There are no examples or guidance for Linux users, such as using the command line or addressing differences in file navigation and shortcuts. All instructions assume a GUI workflow typical of Windows environments.
Recommendations
  • Include Linux-specific instructions or notes, such as how to open folders in VS Code from the terminal (e.g., 'code .') and alternative keyboard shortcuts.
  • Provide examples or guidance for users who prefer or require command-line workflows, which are common on Linux.
  • Mention any platform-specific differences in installing prerequisites (e.g., Git, VS Code extension installation) and provide links or steps for Linux distributions.
  • Ensure that screenshots and navigation steps are inclusive of both Windows and Linux environments, or clarify when instructions are platform-agnostic.
GitHub Create Pull Request
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform, but there are minor signs of Windows bias. The Node.js version manager (nvm) is mentioned for Linux/macOS, but the Windows-specific 'NVM for Windows' is called out separately and referenced before any Linux/macOS installation instructions. Additionally, there is a mention of Windows Firewall prompting for access, which is a Windows-specific behavior and may confuse Linux/macOS users. However, all core instructions (CLI usage, code samples, workflow configuration) are platform-agnostic and do not rely on Windows-only tools or patterns.
Recommendations
  • When mentioning Node.js version management, present Linux/macOS and Windows options together, or clarify that nvm is for Linux/macOS and NVM for Windows is for Windows.
  • Add a note clarifying that the Windows Firewall prompt is specific to Windows, and Linux/macOS users will not see this prompt.
  • Consider including brief instructions or links for installing Node.js and CLI tools on Linux/macOS, to match the Windows references.
  • Ensure that any platform-specific behaviors (such as firewall prompts) are clearly marked as such.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation displays mild Windows bias by recommending Azure Data Studio (a Microsoft tool most commonly used on Windows) as the primary database client, and by presenting PowerShell examples alongside Bash for all CLI commands. Windows tools and patterns are mentioned first or exclusively in some steps, and PowerShell is given equal prominence to Bash, which may not reflect the usage patterns of Linux/macOS users. However, alternatives like MySQL Workbench and generic 'any other tool' are mentioned, and Bash examples are provided throughout.
Recommendations
  • Explicitly mention Linux/macOS compatibility for Azure Data Studio and MySQL Workbench, or suggest CLI-based alternatives like the MySQL CLI for table creation and data manipulation.
  • Present Bash examples before PowerShell, or clarify that Bash is the default for Linux/macOS users.
  • Add a section or note on using native Linux/macOS tools for MySQL management (e.g., mysql CLI, DBeaver).
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., file paths, UI conventions).
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation is generally cross-platform and uses bash-based commands for core tasks, but there are some signs of Windows bias. Visual Studio Code is recommended as the editor (which is cross-platform but often associated with Windows). In the Angular section, environment variable setup is shown for bash, csh, PowerShell, and CMD, with Windows shells (PowerShell and CMD) included and shown after Unix shells. There are no Linux/macOS-specific troubleshooting tips, and Windows tools are mentioned (CMD, PowerShell) without equivalent emphasis on Linux/macOS alternatives.
Recommendations
  • Explicitly mention that all commands work on Linux/macOS and Windows, and clarify any platform-specific differences.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, shell differences).
  • When listing shell commands, alternate the order or clarify that all platforms are supported equally.
  • Consider including examples for popular Linux/macOS editors (e.g., Vim, Sublime) alongside Visual Studio Code.
  • Add a note about using the Azure CLI on Linux/macOS, if there are any differences.
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
Low Priority View Details →
Scanned: 2026-01-13 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 environment variable setup, npm commands, and CLI usage. However, PowerShell examples are consistently shown after Bash, and no Linux/macOS-specific tools or patterns are mentioned. There is a slight Windows bias in the ordering and inclusion of PowerShell examples, but Linux/macOS users are not blocked from completing the tutorial.
Recommendations
  • Explicitly mention Linux/macOS compatibility in prerequisites and CLI instructions.
  • Provide guidance for common Linux/macOS shells beyond Bash (e.g., zsh, fish) for environment variable setup.
  • Alternate the order of Bash and PowerShell examples, or group them under clear OS headings.
  • Add a note clarifying that all CLI commands work on Linux/macOS as well as Windows.
  • Include troubleshooting tips for Linux/macOS users if any platform-specific issues are known.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows mild Windows bias. Windows installation instructions for Azure CLI are listed first, and Visual Studio Code is recommended as the editor with a link to Windows-focused setup. PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. There is no explicit Linux/macOS example for editors or shell environments, though Azure CLI is cross-platform and Bash is mentioned for CLI examples.
Recommendations
  • List installation instructions for Azure CLI in the order: Linux, macOS, Windows, or group them equally.
  • Explicitly mention that Visual Studio Code is cross-platform and provide links to Linux/macOS installation guides.
  • Provide example commands for Bash, zsh, or other common Linux/macOS shells, not just PowerShell.
  • Include alternative editors (e.g., Vim, Sublime Text) for ARM template editing, or clarify that any JSON editor can be used.
  • Clarify that Azure CLI is recommended for cross-platform use, and PowerShell is optional for Windows users.
GitHub Create Pull Request
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows minor Windows bias by mentioning Windows-specific tools (NVM for Windows, Winget) and referencing Windows Firewall prompts. These Windows details are presented before or in addition to Linux/macOS equivalents, but Linux/macOS instructions are present and sufficient for completing the task.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions (e.g., mention how firewalls may prompt on Linux/macOS, or clarify that this step is Windows-specific).
  • When listing tools like NVM, present cross-platform options first, and only mention platform-specific variants as needed.
  • Add explicit instructions or links for installing Visual Studio Code and required extensions on Linux/macOS.
  • Clarify that the CLI and all commands work on Linux/macOS, and note any platform-specific caveats.
  • Avoid presenting Windows-specific details before cross-platform or Linux/macOS instructions unless necessary.
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
Low 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 generally uses cross-platform tools and bash commands, but there is a subtle Windows bias. Visual Studio Code is recommended as the editor for Azure work, which is popular on Windows but also available on Linux/macOS. In the Angular section, environment variable setting is shown for bash, csh, PowerShell, and CMD, with Windows shells (PowerShell, CMD) included and PowerShell shown before CMD. There are no Linux/macOS-specific tools or examples highlighted, and no explicit mention of Linux/macOS editors or shell alternatives. The overall flow is cross-platform, but Windows tools and patterns are slightly prioritized.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux/macOS, or suggest other popular editors for those platforms.
  • In environment variable examples, consider listing bash/csh first to reflect Linux/macOS usage, or clarify that the order is arbitrary.
  • Add a note that all commands work on Linux/macOS, and provide troubleshooting tips for those platforms if needed.
  • Include links to platform-specific installation guides for Azure CLI and Node.js.
  • Consider adding a brief section or callout for Linux/macOS users to ensure parity and address any platform-specific nuances.
GitHub Create Pull Request
Static Web Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/static-web-apps/deployment-token-management.md ...rticles/static-web-apps/deployment-token-management.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples or tooling, but it also does not mention or show any Linux-specific workflows, commands, or screenshots. All instructions are GUI-based and platform-agnostic, but there is a lack of parity for users who may prefer or require command-line or Linux-native approaches.
Recommendations
  • Add CLI-based instructions for resetting and updating deployment tokens using Azure CLI, PowerShell, and Bash, ensuring both Windows and Linux users are supported.
  • Include examples of how to update GitHub secrets using the GitHub CLI (gh) or via scripts, with both Windows (PowerShell) and Linux (Bash) syntax.
  • Provide screenshots or terminal output from both Windows and Linux environments where relevant.
  • Explicitly mention that the process can be performed on any OS, and link to cross-platform tools or documentation where appropriate.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →