Azure Maps

172
Total Pages
150
Linux-Friendly Pages
22
Pages with Bias
12.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

90 issues found
Showing 51-75 of 90 flagged pages
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently uses PowerShell syntax (e.g., 'npm install' and 'npm init' shown as PowerShell code blocks) for all command-line examples, which may suggest a Windows-first approach. There are no Linux/macOS-specific instructions, nor are shell (bash/sh) examples provided. While the content itself is cross-platform, the presentation may create friction for non-Windows users.
Recommendations
  • Use generic shell (bash) syntax for npm commands, or provide both PowerShell and bash examples.
  • Clarify that commands work on Linux/macOS terminals as well, and mention any OS-specific considerations if relevant.
  • Avoid labeling npm commands as PowerShell unless there is a Windows-specific nuance.
  • Add a note or section about running these commands on Linux/macOS, including any differences in file paths or tooling.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides programmatic examples for retrieving the Azure Maps Client ID using PowerShell and Azure CLI, with PowerShell (a Windows-centric tool) presented first and in greater detail. There are no examples for Linux/macOS-native tools (e.g., Bash, REST with curl, or Python SDK). The only explicit programmatic example for Windows is PowerShell, and Azure CLI is cross-platform but is shown after PowerShell. No Linux/macOS-specific patterns or tools are mentioned.
Recommendations
  • Provide Bash/curl examples for retrieving the Client ID and other authentication details.
  • Include Python or other cross-platform SDK examples for authentication tasks.
  • Present Azure CLI examples before PowerShell, or clarify that Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI and REST API calls work on Linux/macOS.
  • Add notes or sections for Linux/macOS users, ensuring parity in programmatic access and tool usage.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the JavaScript REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for all shell-based instructions (e.g., creating directories, running scripts, installing npm packages), and does not provide equivalent Linux/macOS shell (bash/sh) examples. This may create friction for users on non-Windows platforms, as PowerShell syntax differs from bash/zsh, which are standard on Linux/macOS. The documentation also presents Windows-style commands first and exclusively, with no mention of Linux tools or patterns.
Recommendations
  • Provide bash/sh equivalents for all PowerShell commands (e.g., use 'mkdir mapsDemo && cd mapsDemo' and 'npm init' in bash syntax).
  • Use cross-platform commands or explicitly show both Windows (PowerShell) and Linux/macOS (bash) examples side-by-side.
  • When showing how to run scripts, use 'node search.js' without the PowerShell code block, or clarify that this works on all platforms.
  • Add notes or sections highlighting any platform-specific differences, especially for environment variable handling and file paths.
  • Avoid presenting Windows commands first or exclusively; strive for parity in example ordering.
GitHub Create Pull Request
Azure Maps How to secure an Azure Maps application with a SAS token ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias by presenting all command-line examples in PowerShell syntax, explicitly referencing PowerShell as the environment, and omitting any Linux/macOS shell equivalents. There are no bash or cross-platform shell examples, and variable assignment and command substitution use PowerShell-specific constructs. This may create friction for Linux/macOS users, who must translate the examples themselves.
Recommendations
  • Provide all command-line examples in both PowerShell and bash/zsh syntax, or use cross-platform-agnostic Azure CLI commands with notes on variable assignment differences.
  • Clarify that Azure CLI is cross-platform and can be used in any shell, not just PowerShell.
  • Avoid language like 'PowerShell session' unless the steps are truly Windows-specific; otherwise, use 'terminal' or 'shell'.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
  • Where variable assignment or command substitution is shown, provide both PowerShell ($var = ...) and bash (var=$(...)) forms.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the C# REST SDK ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently uses PowerShell for all command-line examples, including project creation, package installation, and environment variable setup. No Linux/macOS shell equivalents (e.g., Bash) are provided, and Windows/PowerShell commands are presented first and exclusively. This creates friction for Linux/macOS users, who must translate commands themselves.
Recommendations
  • Provide equivalent Bash (Linux/macOS) command-line examples alongside PowerShell, especially for dotnet CLI usage and environment variable setup.
  • Explicitly mention cross-platform compatibility of the .NET SDK and CLI tools.
  • Add notes or sections clarifying differences in environment variable syntax between Windows/PowerShell and Linux/macOS shells.
  • Where screenshots or UI instructions are given, clarify if steps differ for non-Windows platforms.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Java REST SDK (preview) .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell commands for project creation, environment variable setup, and program execution. There are no equivalent Linux/macOS shell (bash/sh) examples, and Windows tooling and patterns (e.g., PowerShell, backslash paths) are used throughout. This creates friction for Linux/macOS users, who must translate commands themselves.
Recommendations
  • Provide equivalent bash/sh commands alongside PowerShell examples for all shell operations (e.g., project creation, setting environment variables, running Java programs).
  • Use platform-neutral instructions where possible (e.g., 'run mvn clean install from your terminal').
  • Document any OS-specific differences, such as path separators or command syntax.
  • Add notes or sections explicitly for Linux/macOS users to ensure parity.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Python REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in setup and environment variable instructions. All shell commands (creating directories, files, installing packages, setting environment variables) are shown exclusively using PowerShell syntax, with no Bash or Linux/macOS equivalents. This can create confusion or friction for users on non-Windows platforms, as the commands are not directly portable. The bias is most evident in the initial project setup and authentication steps, where Linux users must mentally translate PowerShell commands to Bash.
Recommendations
  • Provide Bash/Linux/macOS equivalents for all PowerShell commands, especially for creating directories/files and setting environment variables.
  • Present cross-platform shell examples side-by-side or note the differences explicitly.
  • Avoid using only PowerShell syntax for pip installation; use generic 'pip install' commands or clarify platform-specific nuances.
  • Add a note early in the documentation clarifying that examples are shown in PowerShell and provide links or inline examples for Bash/zsh.
  • Ensure screenshots and instructions for obtaining credentials are platform-neutral.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Java REST SDK (preview) .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell and Windows-centric commands for project creation, file creation, environment variable setting, and program execution. There are no equivalent examples for Linux/macOS users (e.g., Bash commands), and Windows/PowerShell instructions are presented as the default or only option. This creates friction for non-Windows users, who must translate commands themselves.
Recommendations
  • Provide Bash equivalents for all PowerShell commands (e.g., project creation, file creation, setting environment variables, running Java programs).
  • Add explicit instructions or code blocks for Linux/macOS users alongside PowerShell examples.
  • When showing command-line examples, present both Windows and Linux/macOS commands, or use a neutral format when possible.
  • Clarify that the SDK and workflow are cross-platform, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Python REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its setup and authentication instructions. All shell commands (creating directories, files, setting environment variables, installing packages) are shown exclusively using PowerShell syntax, with no Bash or Linux/macOS alternatives. This may confuse or slow down users on Linux or macOS, especially when setting environment variables or creating files. The bias is most evident in the initial project setup and authentication steps, which are critical for getting started.
Recommendations
  • Provide equivalent Bash/Linux/macOS commands alongside PowerShell examples for all shell operations (e.g., mkdir, cd, touch, export).
  • Explicitly mention that the examples are for Windows/PowerShell, and offer guidance for non-Windows users.
  • Add notes or tabs to switch between Windows and Linux/macOS instructions where shell commands are required.
  • Show how to set environment variables in Bash (e.g., export VAR=value) and how to create files (e.g., touch demo.py).
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides both PowerShell and Azure CLI examples for retrieving the Azure Maps Client ID, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. There is no mention of Linux/macOS-specific shell usage or examples, and the CLI example is not shown in a Linux shell context. The only explicit tooling examples are for PowerShell and Azure CLI, with PowerShell given precedence, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Include explicit Linux/macOS shell examples (e.g., bash) for CLI commands.
  • Clarify that Azure CLI works on all platforms and provide installation/use links for Linux/macOS.
  • Avoid implying PowerShell is the default or preferred method for cross-platform tasks.
  • Where possible, add notes or examples for Linux/macOS users, especially for environment variable management and scripting.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the C# REST SDK ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: all shell/command-line examples use PowerShell syntax, including environment variable setting and .NET project/package management. There are no Linux/macOS shell equivalents (e.g., Bash), and Windows/PowerShell commands are presented exclusively and first. This may create friction for Linux/macOS users who need to translate commands to their own environment.
Recommendations
  • Provide Bash equivalents for all PowerShell command-line examples, including dotnet CLI usage and environment variable setting.
  • Clearly indicate cross-platform compatibility of the .NET SDK and CLI tools.
  • Add notes or sections for Linux/macOS users, highlighting any differences in workflow or commands.
  • Consider presenting both Windows and Linux/macOS examples side-by-side, or use tabs for platform-specific instructions.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the JavaScript REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for project setup and package installation (e.g., mkdir, cd, npm init, npm install), and instructs users to run scripts with 'node search.js' in PowerShell syntax. No Linux/macOS shell equivalents (bash, sh, etc.) are provided, and Windows/PowerShell commands are shown first and exclusively. This may cause friction for Linux/macOS users unfamiliar with PowerShell syntax.
Recommendations
  • Provide equivalent bash/sh commands alongside PowerShell examples for directory creation, navigation, and npm usage.
  • Use generic cross-platform commands (e.g., 'npm install ...') or clarify that commands work in any terminal.
  • Explicitly mention that all commands are compatible with Linux/macOS terminals unless otherwise noted.
  • Add notes or code blocks for Linux/macOS users where file paths or environment variable handling may differ.
GitHub Create Pull Request
Azure Maps How to secure an Azure Maps application with a SAS token ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias by assuming the use of PowerShell as the primary shell environment for running Azure CLI commands. All command-line examples use PowerShell syntax (e.g., $variable = $(...)), and the complete script is explicitly labeled as a PowerShell session. There are no examples or notes for running the same workflow in Bash or on Linux/macOS systems, despite the Azure CLI being cross-platform. Additionally, references to obtaining Azure AD object IDs mention PowerShell cmdlets (Get-AzADUser), with no mention of Bash or cross-platform alternatives.
Recommendations
  • Provide parallel Bash/Linux/macOS command examples alongside PowerShell, especially for variable assignment and command substitution.
  • Add a note clarifying that Azure CLI commands work on all platforms, and show how to adapt variable assignment and scripting for Bash.
  • Where PowerShell cmdlets are referenced (e.g., Get-AzADUser), include Azure CLI or Microsoft Graph API alternatives that are platform-agnostic.
  • In the 'Complete script example', offer a Bash version or at least highlight the differences for Linux/macOS users.
  • Avoid language like 'PowerShell session' unless the steps are truly Windows-specific; otherwise, use 'terminal' or 'shell'.
GitHub Create Pull Request
Azure Maps Create your Azure Maps account using an Azure Resource Manager template in Azure Maps ...lob/main/articles/azure-maps/how-to-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deploying Azure Maps accounts using the Azure Portal, which is platform-neutral, but when mentioning alternative deployment methods, it lists Azure PowerShell first, followed by Azure CLI and REST API. There are no explicit PowerShell examples, but the CLI examples provided use Azure CLI, which is cross-platform. However, there is no mention of Linux-specific tools, shell scripts, or guidance for Linux users, and the linked 'Deploy templates' page refers to PowerShell before CLI. This ordering and lack of Linux-specific context indicate a subtle Windows-first bias and missing Linux parity.
Recommendations
  • Ensure that deployment method lists alternate between PowerShell and CLI, or list CLI first to reflect cross-platform parity.
  • Provide explicit examples for both Azure PowerShell and Azure CLI, and clarify that CLI commands work on Windows, Linux, and macOS.
  • Include references to Linux shell scripting or automation where appropriate.
  • Add notes or sections for Linux/macOS users, such as prerequisites for installing Azure CLI on those platforms.
  • Review linked pages to ensure Linux parity and avoid PowerShell-first ordering.
GitHub Create Pull Request
Azure Maps Drawing tools module ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example for installing npm packages ("npm install --save-dev style-loader css-loader") and referencing PowerShell syntax in the context of JavaScript development. There are no Linux or macOS shell equivalents (e.g., bash) shown, and the installation command is presented in PowerShell format without alternatives. This may cause confusion for developers on non-Windows platforms and suggests a Windows-first approach.
Recommendations
  • Provide equivalent installation commands using bash/sh (e.g., `npm install --save-dev style-loader css-loader`) without the PowerShell prompt, or clarify that the command works cross-platform.
  • Avoid using platform-specific prompts (e.g., `powershell`) unless necessary, and if used, always provide alternatives for Linux/macOS users.
  • Add notes or examples that explicitly mention cross-platform compatibility for all commands and tooling.
  • Where tooling (like webpack) is discussed, ensure instructions are not tailored to Windows environments only.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides programmatic examples for retrieving the Azure Maps Client ID using PowerShell and Azure CLI, with PowerShell (a Windows-centric tool) presented first and in more detail. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. While Azure CLI is cross-platform, the ordering and emphasis favor Windows/PowerShell users. No Linux-specific instructions or parity examples are given for key operations.
Recommendations
  • Add bash/Linux shell examples for retrieving the Client ID, e.g., using Azure CLI in bash.
  • Explicitly state that Azure CLI works on Linux/macOS and provide example commands in those contexts.
  • When presenting multiple tool examples, alternate the order or present them side-by-side to avoid Windows-first bias.
  • Reference Linux-native tools (e.g., curl, jq) for REST API calls or JSON parsing where appropriate.
  • Review other sections for implicit assumptions of Windows environments and clarify cross-platform compatibility.
GitHub Create Pull Request
Azure Maps Drawing tools module ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias in the section describing npm package installation for webpack. The only command-line example for installing style-loader and css-loader uses PowerShell syntax (`npm install --save-dev style-loader css-loader`), and no Linux/macOS shell equivalents are provided. Additionally, there are no explicit mentions of Linux tools or patterns, and the documentation assumes a Windows-centric workflow for dependency installation.
Recommendations
  • Provide equivalent Linux/macOS shell commands alongside PowerShell examples, e.g., using bash syntax.
  • Clarify that the npm install command works across platforms, and note any platform-specific considerations if relevant.
  • Include notes or examples for common Linux-based development environments (e.g., Ubuntu, WSL, macOS Terminal) to ensure parity.
  • Avoid assuming a Windows environment in command-line instructions; use generic shell syntax or provide both PowerShell and bash/zsh examples.
GitHub Create Pull Request
Azure Maps Create your Azure Maps account using an Azure Resource Manager template in Azure Maps ...lob/main/articles/azure-maps/how-to-create-template.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure Maps account using the Azure portal, with only brief mentions of Azure PowerShell, Azure CLI, and REST API as alternative methods. The main workflow and screenshots are focused on the Azure portal (a web interface, not OS-specific), but the 'Deploy templates' link points to a PowerShell-centric page, and there are no explicit Linux-specific instructions or examples (e.g., Bash, shell scripts). The CLI examples provided are generic and cross-platform, but the absence of Linux/Bash-specific deployment examples or terminal screenshots suggests a subtle Windows-first bias.
Recommendations
  • Add explicit Bash or shell script examples for deploying ARM templates, especially for Linux users.
  • Include instructions and screenshots for using the Azure CLI in a Linux terminal environment.
  • Ensure that alternative deployment methods (CLI, REST API) are described with parity to the portal and PowerShell approaches.
  • Link to documentation pages that cover both PowerShell and Bash/CLI workflows equally, or provide direct links to Linux-focused guides.
GitHub Create Pull Request
Azure Maps Drawing tools module ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page shows evidence of Windows bias in the development workflow section. The only command-line example for installing webpack loaders uses PowerShell syntax (`npm install --save-dev style-loader css-loader`), and there is no mention of Linux or macOS equivalents (such as Bash). The documentation does not provide parity for Linux users in terms of shell commands or tooling references, and the order of presentation implicitly assumes a Windows-first environment.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash/sh) command-line examples for npm installation and other shell commands.
  • Explicitly mention that the instructions apply to all platforms, or note any platform-specific differences.
  • Include references to Linux/macOS development environments and tools where relevant.
  • Avoid assuming a Windows-first workflow in examples and instructions; present cross-platform guidance wherever possible.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-template.md ...lob/main/articles/azure-maps/how-to-create-template.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure Maps account using the Azure portal, with brief mentions of alternative methods (Azure PowerShell, Azure CLI, REST API) only after the portal workflow. While Azure CLI examples are provided for post-deployment tasks, there are no explicit Linux-specific instructions or screenshots, and PowerShell is referenced in the 'Deploy templates' link. The portal-centric workflow implicitly favors Windows environments, as the Azure portal and PowerShell are more commonly used on Windows.
Recommendations
  • Include explicit Linux workflow examples, such as deploying the ARM template using Azure CLI from a Linux shell.
  • Provide equivalent instructions for macOS and Linux users, including screenshots or terminal output.
  • Add PowerShell and Bash script examples side-by-side for deployment and resource management tasks.
  • Clarify that Azure CLI is cross-platform and provide installation guidance for Linux.
  • Avoid referencing PowerShell as the primary alternative to the portal; mention Azure CLI and Bash first.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/set-drawing-options.md ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page includes a command-line example for installing webpack loaders using PowerShell syntax (`npm install --save-dev style-loader css-loader`), which is typical for Windows environments. No equivalent Linux/macOS shell example is provided, and the only explicit shell command is given in PowerShell format. This may unintentionally signal a Windows-first approach and could hinder Linux users unfamiliar with PowerShell.
Recommendations
  • Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples for npm installation steps.
  • Explicitly mention that the npm commands work across platforms, and clarify any platform-specific differences if relevant.
  • Avoid using only PowerShell syntax for shell commands; use generic shell syntax or include both variants.
  • Review other examples and instructions to ensure they are platform-neutral or offer parity for Linux/macOS users.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/set-drawing-options.md ...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the section describing npm package installation and webpack loader setup. The only shell command example provided uses PowerShell syntax (`npm install --save-dev style-loader css-loader`), and there is no mention of Linux/macOS shell equivalents (e.g., Bash). The documentation does not explicitly mention Windows-only tools, but the command and example order suggest a Windows-first approach. No Linux-specific instructions or parity examples are given.
Recommendations
  • Provide shell command examples using Bash syntax (e.g., `$ npm install --save-dev style-loader css-loader`) alongside PowerShell, or use a generic prompt symbol.
  • Explicitly state that the npm and webpack instructions apply to all platforms (Windows, Linux, macOS), and note any platform-specific considerations if relevant.
  • Where possible, avoid using platform-specific prompt symbols (e.g., `powershell` or `PS>`), or provide both Windows and Linux/macOS variants.
  • Add a note or section confirming cross-platform compatibility of the Azure Maps Web SDK and its modules.
  • Ensure that all tooling instructions (e.g., npm, webpack) reference documentation or examples for both Windows and Linux environments.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-get-started.md ...ain/articles/azure-maps/power-bi-visual-get-started.md
Medium Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references Power BI Desktop as the primary environment for examples and instructions, which is a Windows-only application. All screenshots and step-by-step guides are based on Power BI Desktop, with no mention of Power BI on Linux or alternative platforms. There are no examples or guidance for Linux users, nor any mention of Linux-specific tools or patterns.
Recommendations
  • Include explicit guidance for Power BI users on Linux, such as using Power BI service via web browsers.
  • Add screenshots and examples for Power BI service (web) to demonstrate cross-platform usage.
  • Clarify platform limitations early in the documentation, and direct Linux users to supported alternatives.
  • Where possible, provide parity in instructions for both Windows (Power BI Desktop) and web-based Power BI service.
  • Avoid assuming Power BI Desktop as the default experience; balance examples between desktop and web.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-npm-package.md ...lob/main/articles/azure-maps/how-to-use-npm-package.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently uses PowerShell syntax (e.g., 'npm install ...' and 'npm run build' in PowerShell code blocks) for all command-line examples, which may imply a Windows-first or Windows-only development environment. There are no explicit Linux or macOS shell examples, and no mention of cross-platform command-line usage or differences.
Recommendations
  • Use generic shell (sh, bash) code blocks for npm and CLI commands instead of PowerShell, unless a Windows-specific command is required.
  • Add a note clarifying that all npm commands work on Windows, Linux, and macOS, and that the examples are cross-platform.
  • If platform-specific differences exist (e.g., file paths, environment variables), provide both Windows and Linux/macOS examples.
  • Avoid using PowerShell-specific code block annotations unless demonstrating PowerShell-specific functionality.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-indoor-module.md ...b/main/articles/azure-maps/how-to-use-indoor-module.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a mild Windows bias by using PowerShell syntax (>) in npm install commands and presenting these commands in a way that is most familiar to Windows users. There are no explicit Linux shell (bash) examples, and the use of the PowerShell prompt may confuse Linux/macOS users. However, the overall content is largely cross-platform, as it focuses on JavaScript, HTML, and npm, which are platform-agnostic.
Recommendations
  • Replace PowerShell-specific prompts (>) in npm install commands with a generic shell prompt ($) or no prompt at all to avoid implying a Windows-only environment.
  • Add explicit Linux/macOS shell examples where command-line instructions are given, or use a neutral format (e.g., 'npm install azure-maps-indoor') without any prompt.
  • Include a note clarifying that all npm and JavaScript commands work on Windows, Linux, and macOS, and that the instructions are platform-independent.
  • If referencing tools or workflows that differ between platforms (such as file paths or environment variables), provide both Windows and Linux/macOS examples.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →