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 1-25 of 90 flagged pages
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in the section about programmatically retrieving the Azure Maps Client ID. PowerShell is presented first and in detail, while the Azure CLI is mentioned second. There are no examples using Bash, Linux shell scripting, or other cross-platform tools. The only explicit tooling examples are Windows-centric (PowerShell, Azure CLI), and no Linux-specific or platform-neutral alternatives are provided.
Recommendations
  • Provide Bash/Linux shell examples for retrieving the Client ID, e.g., using Azure CLI in Bash.
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS.
  • Include platform-neutral code snippets where possible, such as REST API calls using curl.
  • Avoid presenting Windows-specific tools (PowerShell) as the primary or only method.
  • Review other sections for implicit Windows assumptions and add Linux/macOS equivalents where needed.
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
High Priority View Details →
Scanned: 2026-01-12 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 bias towards Windows environments by exclusively using PowerShell commands for project setup, package installation, and script execution. There are no Linux or macOS shell (bash/sh/zsh) equivalents provided, and Windows/PowerShell commands are presented as the default or only option. This may hinder Linux and macOS users from following the instructions seamlessly.
Recommendations
  • Provide equivalent bash/sh/zsh commands alongside PowerShell examples for all project setup, npm installation, and script execution steps.
  • Explicitly mention cross-platform compatibility and clarify that commands can be run in any terminal (Windows, Linux, macOS) with appropriate syntax.
  • Add a section or callout for Linux/macOS users, highlighting any differences in environment setup, file paths, or command usage.
  • Where possible, use generic commands (e.g., 'npm install ...', 'node search.js') in documentation examples, or show both PowerShell and bash variants side by side.
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
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by exclusively using PowerShell commands for project setup and environment variable configuration, without providing equivalent Linux/macOS shell examples (e.g., Bash). All command-line instructions (mkdir, cd, file creation, pip install, setting environment variables) are shown in PowerShell syntax, and there is no mention of Linux tools or patterns. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Provide Bash (Linux/macOS) equivalents for all PowerShell commands, including project creation (mkdir, cd, touch demo.py), package installation (pip install), and environment variable setting (export VAR=value).
  • Add a note clarifying that both Windows and Linux/macOS are supported, and show both sets of commands side-by-side or in tabs.
  • Avoid using only PowerShell syntax in documentation targeting cross-platform Python developers.
  • Mention common Linux/macOS tools (e.g., nano, vi for editing files) where appropriate.
  • Review all code snippets and command-line instructions for OS-specific assumptions, ensuring Linux parity.
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
High Priority View Details →
Scanned: 2026-01-12 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 strong Windows bias by exclusively using PowerShell for all command-line examples, including project creation, package installation, and environment variable setup. There are no equivalent examples for Linux or macOS users, such as Bash or sh commands. The documentation assumes a Windows environment throughout, which may hinder accessibility for developers on other platforms.
Recommendations
  • Provide equivalent Bash/sh examples alongside PowerShell for all command-line instructions, including project creation, package installation, and environment variable setup.
  • Explicitly state cross-platform compatibility for .NET and Azure Maps SDK, and clarify that instructions apply to Windows, Linux, and macOS.
  • Add notes or sections for Linux/macOS users, highlighting any differences in environment variable syntax or shell usage.
  • Consider using generic .NET CLI commands (without shell-specific syntax) where possible, or present both PowerShell and Bash side-by-side.
  • Review screenshots and references to ensure they do not assume a Windows-only environment.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. All shell and command-line examples use PowerShell syntax, including project creation, file creation, environment variable setting, and program execution. There are no equivalent Linux/macOS shell (bash/sh) examples, and Windows-specific tools and patterns (e.g., New-Item, $Env:) are used exclusively and presented first. This may hinder Linux/macOS users from following the guide without additional research or translation.
Recommendations
  • Provide equivalent bash/sh examples for all PowerShell commands, including Maven project creation, file creation (e.g., touch demo.java), environment variable setting (e.g., export SUBSCRIPTION_KEY=...), and program execution (e.g., java demo.java).
  • When presenting command-line instructions, show both Windows (PowerShell/CMD) and Linux/macOS (bash/sh) variants side-by-side or in tabs.
  • Avoid using Windows-specific tools (e.g., New-Item) without alternatives; use cross-platform commands where possible.
  • Explicitly mention cross-platform compatibility and provide guidance for users on Linux/macOS.
  • Review and update all code snippets and instructions to ensure Linux parity and accessibility.
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
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by presenting all command-line examples in PowerShell syntax, explicitly stating that Azure CLI runs in a PowerShell instance, and using Windows-style variable assignment and command substitution (e.g., $var = $(...)). There are no Linux shell (bash/zsh) equivalents provided, nor any mention of how to adapt the examples for Linux or macOS environments. The documentation assumes a Windows/PowerShell context throughout, which may hinder accessibility for Linux users.
Recommendations
  • Provide equivalent bash/zsh examples for all command-line steps, using Linux-style variable assignment and command substitution (e.g., var=$(...) instead of $var = $(...)).
  • Clarify that Azure CLI is cross-platform and can be run in any shell, not just PowerShell.
  • Add notes or sections explicitly addressing Linux/macOS usage, including any differences in file paths, environment setup, or command syntax.
  • Avoid language that implies PowerShell is the default or only environment (e.g., 'runs in a PowerShell instance'); instead, use neutral phrasing such as 'in your terminal'.
  • Where scripts are provided, offer both PowerShell and bash versions, or use syntax compatible with both where possible.
GitHub Create Pull Request
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
High Priority View Details →
Scanned: 2026-01-12 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 syntax (e.g., 'npm install' and 'npm run build' shown as PowerShell code blocks) for all command-line examples, which may suggest a Windows-centric approach. There are no explicit Linux or macOS terminal examples, nor any mention of platform-specific differences or considerations. The documentation does not reference Windows-specific tools, but the command-line instructions implicitly favor Windows by using PowerShell formatting and not acknowledging other shells.
Recommendations
  • Provide command-line examples in a neutral shell format (e.g., generic bash or sh), or show both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) examples side-by-side.
  • Use 'shell' or 'bash' code block formatting for npm commands, as these are cross-platform and most users on Linux/macOS expect bash syntax.
  • Add a note clarifying that npm commands work on all major platforms and mention any platform-specific considerations (e.g., file paths, permissions).
  • Avoid using PowerShell-specific formatting unless demonstrating a PowerShell-specific feature.
  • Explicitly mention Linux/macOS compatibility in the prerequisites or installation sections.
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
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by presenting all command-line examples in PowerShell syntax, explicitly stating that Azure CLI runs in a PowerShell instance, and using Windows-centric variable assignment and command substitution patterns (e.g., $var = $(...)). There are no Bash or Linux shell equivalents provided, nor any mention of how to adapt the steps for Linux or macOS environments. The only scripting example is PowerShell, and the instructions assume a Windows shell context throughout.
Recommendations
  • Provide equivalent Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands and variable assignments.
  • Clarify that Azure CLI can be run in any shell (PowerShell, Bash, etc.), and note any differences in syntax or environment setup.
  • Avoid language that implies PowerShell is the default or only supported environment; use neutral phrasing such as 'in your shell' or 'in your terminal'.
  • Include notes or callouts for cross-platform usage, such as how to perform variable assignment and command substitution in Bash.
  • Add a complete script example for Linux/macOS users using Bash syntax.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits significant Windows bias. All shell and environment variable examples use PowerShell syntax, and commands for creating projects, files, and running Java programs are given only in PowerShell. There are no Linux/macOS equivalents (e.g., Bash), and Windows tools/patterns are mentioned exclusively. This may confuse or exclude users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Bash examples alongside PowerShell for all shell commands, including creating Maven projects, setting environment variables, and running Java programs.
  • Clearly indicate which commands are for Windows and which are for Linux/macOS, possibly using tabs or callouts.
  • Avoid using Windows-specific tools (e.g., New-Item) without alternatives; suggest 'touch' or 'echo' for file creation on Linux/macOS.
  • Show how to run Java programs using 'java demo.java' or 'java Demo' for Linux/macOS.
  • Add notes or tips for cross-platform usage, ensuring parity and inclusivity for non-Windows developers.
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
High Priority View Details →
Scanned: 2026-01-11 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, with no mention of Linux/macOS equivalents (e.g., Bash). All CLI and script-running examples use PowerShell syntax, which may confuse or exclude users on Linux or macOS. There is no guidance or parity for non-Windows environments, even though Node.js is cross-platform.
Recommendations
  • Provide Bash equivalents for all PowerShell commands (e.g., 'mkdir mapsDemo && cd mapsDemo && npm init', 'npm install ...', 'node search.js').
  • Explicitly mention that commands work on Linux/macOS and Windows, or provide OS-specific tabs or callouts.
  • Use generic shell commands (e.g., 'npm install ...') where possible, or show both PowerShell and Bash syntax.
  • Add a note that Node.js and Azure Maps SDK are cross-platform and can be used on Linux/macOS as well as Windows.
  • Avoid using Windows-specific command syntax unless necessary, and ensure Linux users are not excluded from setup instructions.
GitHub Create Pull Request
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
High Priority View Details →
Scanned: 2026-01-11 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 syntax (e.g., 'npm install' and 'npm run build' shown as PowerShell code blocks) for all command-line examples, which may imply a Windows-first approach. There are no explicit Linux or macOS shell examples (e.g., bash, sh), nor is there mention of platform-specific considerations for non-Windows users. The use of PowerShell for npm commands is unnecessary, as these commands are cross-platform and typically shown in bash or generic shell syntax in most documentation.
Recommendations
  • Replace PowerShell code blocks with generic shell (bash) code blocks for npm commands, or provide both PowerShell and bash examples.
  • Add a note clarifying that all npm commands work on Windows, Linux, and macOS, and show examples in both environments if there are any platform-specific differences.
  • Avoid using PowerShell syntax for cross-platform commands unless there is a Windows-specific reason.
  • Explicitly mention that the instructions apply to all major operating systems, and provide troubleshooting or tips for Linux/macOS users if relevant.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most commonly used on Windows), mentioning Azure PowerShell before Azure CLI and REST API as alternative deployment methods, and linking to a 'Deploy templates' page that is focused on PowerShell. There is a lack of explicit Linux-focused instructions or examples, and no mention of Linux-specific patterns or tools. While Azure CLI is used in some examples, it is not presented as the primary method, and there is no guidance for Linux users regarding environment setup or command-line usage.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Include explicit instructions for deploying ARM templates using Azure CLI on Linux and macOS, with terminal screenshots or step-by-step guidance.
  • Add references to Linux-specific documentation or setup guides for Azure CLI.
  • Ensure that links to deployment methods include both PowerShell and CLI options, and clarify which are cross-platform.
  • Mention that the Azure portal is accessible from any OS via browser, but highlight CLI as a first-class option for Linux users.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively using PowerShell commands for project setup and environment variable configuration, without providing equivalent Linux/macOS shell examples. All CLI and environment variable instructions are shown in PowerShell syntax, and there is no mention of Linux or macOS alternatives. This may hinder accessibility for developers on non-Windows platforms.
Recommendations
  • Provide equivalent Bash (Linux/macOS) command examples alongside PowerShell, especially for directory creation, file creation, and setting environment variables.
  • Clearly indicate cross-platform compatibility for CLI commands (e.g., 'az maps account create' works on all platforms).
  • Add notes or sections for Linux/macOS users, including common shell commands (e.g., 'export VAR=value' for environment variables, 'mkdir', 'touch demo.py').
  • Consider using platform-agnostic instructions or explicitly showing both Windows and Linux/macOS command variants in all setup steps.
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
High Priority View Details →
Scanned: 2026-01-11 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 clear Windows bias by exclusively providing PowerShell commands for project setup, package installation, and environment variable configuration. No Linux (bash/sh) equivalents are given, and Windows tooling (PowerShell) is presented as the default or only option. This may hinder Linux or macOS developers from following the guide without additional research or translation.
Recommendations
  • Provide equivalent bash/sh commands alongside PowerShell examples for project creation, package installation, and environment variable setup.
  • Explicitly mention cross-platform compatibility of .NET and Azure CLI, and clarify that examples are shown for both Windows and Linux/macOS.
  • Add notes or sections for Linux/macOS users, including screenshots or terminal commands where appropriate.
  • Avoid assuming PowerShell as the default shell; use generic CLI commands where possible, or present both options equally.
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
High Priority View Details →
Scanned: 2026-01-10 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 strong Windows bias by exclusively providing PowerShell commands for project setup, package installation, and environment variable configuration. No Linux or cross-platform shell (e.g., Bash) equivalents are offered, and Windows/PowerShell patterns are presented as the default approach throughout. This may hinder usability for developers on Linux or macOS systems.
Recommendations
  • Provide equivalent Bash (sh) commands alongside PowerShell for project creation, package installation, and environment variable setup.
  • Explicitly mention cross-platform compatibility of .NET CLI and environment variable usage, clarifying any differences between Windows and Linux/macOS.
  • Add notes or sections for Linux/macOS users, including screenshots or instructions relevant to those platforms.
  • Avoid assuming PowerShell as the default shell; use generic .NET CLI commands where possible, and supplement with platform-specific instructions as needed.
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
High Priority View Details →
Scanned: 2026-01-10 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 strong Windows bias by exclusively providing PowerShell commands for project setup, environment variable configuration, and running Java programs. There are no equivalent examples for Linux or macOS users (e.g., Bash commands), and Windows tooling is implicitly prioritized throughout the guide. This may hinder accessibility and clarity for developers using non-Windows platforms.
Recommendations
  • Provide equivalent Bash (Linux/macOS) command examples alongside PowerShell snippets for all steps, including Maven project creation, environment variable setup, and running Java programs.
  • Clearly indicate cross-platform compatibility for all commands and tools, and specify any platform-specific differences.
  • Add a section or notes highlighting how to perform each step on Linux/macOS, including screenshots or terminal output where appropriate.
  • Avoid using Windows-specific syntax (e.g., '.\demo.java') without also showing the cross-platform alternative ('java demo.java').
  • Consider using generic command-line instructions (e.g., 'mvn archetype:generate ...') where possible, and only supplement with platform-specific details when necessary.
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
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by exclusively using PowerShell commands for project setup and environment variable configuration, without providing equivalent Linux/macOS shell examples. All CLI and environment variable instructions are given in PowerShell syntax, and there is no mention of Linux or macOS alternatives. This may hinder accessibility for developers on non-Windows platforms.
Recommendations
  • Add equivalent Bash (Linux/macOS) command examples alongside PowerShell commands for project setup (e.g., mkdir, cd, touch demo.py).
  • Provide Bash syntax for setting environment variables (e.g., export AZURE_CLIENT_ID=...) wherever PowerShell examples are shown.
  • Explicitly mention cross-platform compatibility and clarify which commands are for Windows and which are for Linux/macOS.
  • Consider presenting Linux/macOS examples first or side-by-side with Windows examples to avoid implicit prioritization.
  • Review all CLI and scripting instructions to ensure Linux users can follow without ambiguity.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is featured as the primary example for programmatically retrieving the Azure Maps Client ID, with the Azure CLI (cross-platform) mentioned second. No Linux-specific shell (bash) or scripting examples are provided. The use of Windows-centric tools and patterns (PowerShell, Get-AzMapsAccount) is emphasized, and there are no explicit Linux or macOS command-line examples or references to Linux-native tooling. This may disadvantage users on Linux or macOS platforms, who are likely to use bash, zsh, or other shells.
Recommendations
  • Provide bash and/or zsh examples for retrieving the Client ID and other common tasks, using Azure CLI and jq where appropriate.
  • When listing command-line examples, present Azure CLI (cross-platform) first, before PowerShell.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands for each platform where differences exist.
  • Avoid exclusive references to Windows tools (e.g., PowerShell) unless necessary; ensure parity by including Linux/macOS alternatives.
  • Add a section or note on platform compatibility for SDKs and management tools, clarifying usage on non-Windows systems.
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
High Priority View Details →
Scanned: 2026-01-10 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 bias toward Windows environments by exclusively using PowerShell syntax for all command-line examples (e.g., mkdir, cd, npm init, npm install, node search.js), and does not provide equivalent Linux/macOS shell commands (bash/sh/zsh). This may create confusion or extra effort for developers using Linux or macOS, as some PowerShell commands (e.g., mkdir, cd) have different syntax or behavior in bash. Additionally, the use of PowerShell is presented without alternatives, and there is no mention of Linux-specific tools, patterns, or troubleshooting.
Recommendations
  • Provide all command-line examples in both PowerShell (Windows) and bash/sh (Linux/macOS) formats, either side-by-side or with tabs.
  • Explicitly state that the examples are cross-platform and clarify any differences in command syntax or behavior.
  • Include notes or troubleshooting tips for Linux/macOS users, such as file path conventions, environment variable setup, and package installation.
  • Avoid assuming the use of PowerShell by default; use neutral or platform-agnostic commands where possible.
  • Add a section or quickstart for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
High Priority View Details →
Scanned: 2026-01-10 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 syntax (e.g., 'npm install' and 'npm run build' shown as PowerShell code blocks) for all command-line examples, which may suggest a Windows-centric approach. There are no explicit Linux or macOS shell examples (e.g., Bash), nor any mention of platform-specific considerations for non-Windows environments. The use of PowerShell code blocks for npm commands may mislead Linux/macOS users, and the documentation does not clarify that these commands are cross-platform.
Recommendations
  • Use generic shell code blocks (e.g., 'bash' or no language tag) for npm commands instead of 'powershell', since these commands are cross-platform.
  • Add notes or examples for Linux/macOS users, clarifying that the commands work in Bash/zsh and do not require PowerShell.
  • If there are any platform-specific steps (e.g., opening HTML files, installing Node.js), mention differences or provide guidance for Linux/macOS.
  • Avoid implying Windows-first usage by ensuring examples and instructions are platform-neutral unless a genuine platform difference exists.
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
High Priority View Details →
Scanned: 2026-01-10 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 bias towards Windows environments by exclusively presenting Azure CLI usage within PowerShell, referencing PowerShell sessions, and using Windows-style variable assignment and command substitution syntax. There are no explicit examples or instructions for running the same workflow in Linux or macOS shells (e.g., Bash), nor any mention of cross-platform compatibility for the CLI commands. The only scripting example is in PowerShell, and the instructions assume a Windows-first context.
Recommendations
  • Provide equivalent Bash shell examples for all CLI commands, including variable assignment and command substitution, to ensure Linux/macOS users can follow along.
  • Explicitly state that Azure CLI is cross-platform and can be run in Bash, PowerShell, or other shells, and clarify any syntax differences.
  • Replace or supplement PowerShell-specific instructions (e.g., $var = $(...)) with Bash equivalents (e.g., var=$(...)).
  • Add a note or section on running the workflow on Linux/macOS, including any file path or environment differences.
  • Ensure references to tools or commands (such as Get-AzADUser) are accompanied by platform-agnostic alternatives or explanations.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/azure-maps-authentication.md .../main/articles/azure-maps/azure-maps-authentication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section on retrieving the Azure Maps Client ID programmatically. PowerShell is presented first and in more detail, while the Azure CLI example is provided second and lacks explicit Linux context. No Linux-specific shell examples (e.g., bash) are given, and there is no mention of Linux tooling or patterns elsewhere. The documentation assumes familiarity with Windows/PowerShell environments and does not provide parity for Linux users.
Recommendations
  • Provide bash or shell script examples for retrieving the Client ID using Azure CLI, explicitly showing usage in Linux/macOS terminals.
  • When listing command-line examples, alternate the order or present both Windows (PowerShell) and Linux (bash) examples side-by-side.
  • Explicitly mention cross-platform compatibility of Azure CLI and clarify that commands can be run in Linux, macOS, and Windows environments.
  • Add notes or tips for Linux users regarding environment setup, authentication, and any platform-specific considerations.
  • Review other sections for implicit Windows assumptions and ensure documentation is inclusive of Linux workflows and tools.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-csharp-sdk.md ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for all command-line examples (project creation, package installation, environment variable setup), with no mention or examples of Linux/macOS equivalents (such as Bash). Windows tools and patterns (PowerShell syntax, $Env: variables) are presented first and solely, potentially making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide equivalent Bash examples for all PowerShell commands, including project creation, package installation, and environment variable setup.
  • Include a note or section clarifying cross-platform usage, highlighting differences in command syntax between Windows (PowerShell) and Linux/macOS (Bash).
  • Where environment variables are set, show both PowerShell ($Env:VAR) and Bash (export VAR=value) syntax.
  • Consider alternating or balancing the order of examples, sometimes showing Linux/Bash first.
  • Explicitly state that .NET and Azure Maps SDK are cross-platform and can be used on Linux/macOS, not just Windows.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-java-sdk.md .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for project creation, environment variable setup, and program execution. There are no equivalent Linux/macOS shell (bash/sh) commands or instructions, which may hinder users on non-Windows platforms. The use of PowerShell is assumed throughout, and no mention is made of cross-platform alternatives.
Recommendations
  • Provide equivalent bash/sh examples for all PowerShell commands, including Maven project creation, environment variable setup, and running Java programs.
  • Explicitly state that the instructions apply to Windows and add a section for Linux/macOS users.
  • Use cross-platform command syntax where possible (e.g., 'mvn archetype:generate' works the same, but environment variable setup and file creation differ).
  • For environment variables, show both PowerShell and bash export syntax (e.g., 'export AZURE_CLIENT_ID=...').
  • For file creation, use 'touch demo.java' for Linux/macOS.
  • For running Java programs, use 'java demo.java' or clarify platform differences.
  • Add a note that PowerShell commands are for Windows and provide alternatives for other platforms.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively using PowerShell commands for project setup and environment variable management, without providing equivalent Linux/macOS shell examples. All CLI and environment variable instructions are shown in PowerShell syntax, and there are no bash or cross-platform alternatives. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Provide equivalent bash/zsh shell commands alongside PowerShell examples for project setup (e.g., mkdir, cd, touch demo.py).
  • Include Linux/macOS instructions for setting environment variables (e.g., export VAR=value) wherever PowerShell ($Env:VAR=...) is used.
  • Add a note clarifying that commands are platform-specific and offer guidance for both Windows and Linux/macOS users.
  • Consider using cross-platform tools (e.g., Azure CLI) in examples and clarify their usage on different operating systems.
  • Ensure screenshots and references to tools do not assume a Windows environment unless necessary, and mention Linux/macOS alternatives if available.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →