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 26-50 of 90 flagged pages
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-sas-app.md ...blob/main/articles/azure-maps/how-to-secure-sas-app.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 Windows bias by exclusively presenting command-line examples in PowerShell syntax, referencing PowerShell sessions as the default environment for running Azure CLI commands, and omitting any explicit Linux/bash shell equivalents. There are no instructions or notes for Linux or macOS users, nor any mention of cross-platform considerations for running the scripts.
Recommendations
  • Provide explicit bash/Linux/macOS command-line examples alongside PowerShell, especially for Azure CLI usage.
  • Clarify that Azure CLI commands can be run in any shell (PowerShell, bash, zsh, etc.), and note any syntax differences (e.g., variable assignment, command substitution).
  • Add a section or callout for Linux/macOS users, including example scripts and tips for adapting the instructions.
  • Avoid language that assumes PowerShell is the default or only environment; use neutral phrasing such as 'in your command-line shell'.
  • Where variable assignment or command substitution is shown, provide both PowerShell and bash syntax (e.g., $outputs = $(...) vs outputs=$(...) ).
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md ...ob/main/articles/azure-maps/how-to-dev-guide-js-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 consistently uses PowerShell commands (e.g., mkdir, cd, npm init, npm install, node search.js) for all shell and project setup instructions, which are Windows-centric. No Linux/macOS shell equivalents (such as bash or sh) are provided, and there is no mention of Linux-specific patterns or tools. This may confuse or inconvenience users on Linux or macOS platforms, especially since Node.js is cross-platform.
Recommendations
  • Provide bash/sh equivalents for all PowerShell commands, either alongside or in place of PowerShell examples.
  • Explicitly mention that commands work on Linux/macOS and provide instructions for those platforms where necessary.
  • Use generic cross-platform commands (e.g., 'mkdir mapsDemo && cd mapsDemo && npm init') or show both Windows (PowerShell) and Linux/macOS (bash) versions.
  • Add a note clarifying that the SDK and instructions are platform-agnostic, and highlight any platform-specific considerations if they exist.
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
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 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 or Windows-only development environment. There are no explicit Linux or macOS shell examples (e.g., bash), nor any mention of platform-specific considerations or parity. This could make Linux/macOS users feel excluded or uncertain about compatibility.
Recommendations
  • Use generic shell code blocks (e.g., 'bash' or no language specifier) for npm commands, as they are cross-platform.
  • Add a note clarifying that all commands work on Linux/macOS terminals as well as Windows, and mention any platform-specific differences if relevant.
  • Provide at least one example using a Linux/macOS terminal (e.g., showing '$ npm install ...' or using bash code blocks).
  • Avoid using PowerShell code blocks for generic npm commands unless demonstrating a PowerShell-specific feature.
  • Explicitly state platform compatibility in the prerequisites or introduction section.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily guiding users through the Azure Portal (a GUI, most commonly used on Windows), referencing Azure PowerShell and CLI as secondary options, and linking to a deployment guide that is PowerShell-centric. There are no explicit Linux-specific instructions or examples, and the CLI examples provided are generic without OS-specific context. The documentation does not mention Linux tools or workflows, nor does it provide parity for Linux users in terms of step-by-step instructions or screenshots.
Recommendations
  • Include explicit Linux deployment instructions, such as using Azure CLI on Linux terminals.
  • Provide examples for Bash shell usage, and clarify CLI commands are cross-platform.
  • Add screenshots or walkthroughs for deploying via CLI on Linux (e.g., Ubuntu) environments.
  • Link to documentation pages that cover both PowerShell and Bash/CLI workflows equally.
  • Ensure references to deployment methods do not prioritize Windows tools (PowerShell, Portal) over cross-platform alternatives.
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-08 00:53
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 creation, environment variable setup, and program execution. There are no Linux or macOS equivalents (e.g., Bash commands) for these steps, and Windows tooling is presented as the default or only option. This may hinder Linux/macOS users from following the guide without additional research.
Recommendations
  • Provide equivalent Bash shell commands alongside PowerShell for all steps involving the command line, including Maven project creation, environment variable setup, and Java program execution.
  • Clearly indicate cross-platform compatibility for all CLI commands and tools.
  • Add notes or sections specifically for Linux/macOS users, highlighting any differences in workflow or command syntax.
  • Avoid using Windows-specific syntax (e.g., '.\demo.java') without also showing the Unix-style alternative ('./demo.java').
  • Consider using generic command-line instructions where possible, or present Windows and Linux/macOS instructions side-by-side.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-sas-app.md ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 the context of PowerShell, using Windows-specific syntax (e.g., $() for variable assignment), and explicitly stating that Azure CLI is run in a PowerShell instance. There are no equivalent Linux/bash examples, nor any mention of how to adapt the commands for Linux or macOS environments. The documentation assumes a Windows user experience throughout the resource deployment and scripting sections.
Recommendations
  • Provide equivalent bash/Linux/macOS command examples alongside PowerShell examples, especially for Azure CLI usage.
  • Clarify that Azure CLI can be run on multiple platforms and provide guidance for Linux/macOS users (e.g., variable assignment, command substitution differences).
  • Avoid language that implies PowerShell is the default or only environment; instead, use cross-platform-neutral phrasing.
  • Add notes or callouts where syntax or behavior differs between Windows/PowerShell and Linux/bash.
  • Include a complete script example for bash/zsh, highlighting any necessary changes (e.g., $(...) vs $(), quoting, array syntax).
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias in several ways. In the section on retrieving the Azure Maps Client ID programmatically, PowerShell (a Windows-centric tool) is presented first and in more detail, while Azure CLI (cross-platform) is mentioned second and with less explanation. There are no examples using Linux-native tools (e.g., Bash, curl, jq), and no mention of how to perform equivalent operations on Linux or macOS. The only programmatic examples for account property retrieval use PowerShell and Azure CLI, with no parity for Linux shell environments.
Recommendations
  • Provide Linux/macOS shell examples using Bash, curl, and jq for retrieving Azure Maps account properties (e.g., Client ID).
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used outside Windows.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add a note or section on using REST API calls directly with curl or similar tools for authentication tasks.
  • Ensure that all programmatic examples are available for both Windows and Linux environments, and avoid assuming PowerShell as the default.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, package installation, and running scripts, with no mention of Linux/macOS equivalents (e.g., Bash). This may confuse or exclude users on non-Windows platforms. The use of PowerShell is presented as the default, and there are no alternative examples for Linux users, despite Node.js and npm being cross-platform.
Recommendations
  • Provide Bash equivalents for all PowerShell commands (e.g., use 'mkdir mapsDemo && cd mapsDemo && npm init' and 'npm install ...').
  • When showing how to run scripts, include both 'node search.js' (which works cross-platform) and clarify that the command works on Windows, Linux, and macOS.
  • Explicitly mention that all steps are applicable to Linux/macOS, and note any platform-specific differences if present.
  • Consider using generic shell commands (e.g., Bash) in examples, or show both PowerShell and Bash side-by-side for parity.
  • Add a note in the prerequisites or setup section about cross-platform compatibility, and link to Node.js installation instructions for Linux/macOS.
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-08 00:53
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. All shell and environment variable examples use PowerShell syntax exclusively, with no Bash or Linux equivalents provided. The instructions for creating a Python project, installing packages, and setting environment variables are all shown in PowerShell, which is native to Windows. There are no examples or guidance for Linux or macOS users, such as using Bash, sh, or other common Unix shells. This may confuse or exclude users on non-Windows platforms.
Recommendations
  • Provide equivalent Bash/Linux/macOS shell commands alongside PowerShell examples for creating directories, files, and setting environment variables.
  • Explicitly mention cross-platform compatibility and note any differences in command syntax between Windows and Linux/macOS.
  • Add a section or callout for Linux/macOS users, including examples using Bash (e.g., 'export VAR=value') and file creation commands ('touch demo.py').
  • Consider using generic Python code for file creation (e.g., using open('demo.py', 'w')) to avoid shell-specific instructions.
  • Where PowerShell is used, clarify that it is for Windows and provide the alternative for other platforms.
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-08 00:53
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 shell commands (project creation, package installation, environment variable setup), with no mention of Linux or cross-platform alternatives such as Bash. Windows tools and patterns (PowerShell syntax, $Env: variables) are presented as the default and only option, and there are no examples or instructions for Linux or macOS users. This may hinder accessibility and usability for developers working on non-Windows platforms.
Recommendations
  • Provide equivalent Bash shell examples for Linux/macOS users alongside PowerShell commands (e.g., using 'export' for environment variables, standard Bash syntax for project setup).
  • Explicitly state that the SDK and CLI commands are cross-platform, and clarify any platform-specific differences.
  • Add a section or callout for Linux/macOS setup, including common shell usage and environment variable configuration.
  • Avoid assuming PowerShell as the default shell; use neutral language and offer both Windows and Linux/macOS instructions in parallel.
  • Where screenshots or UI references are made, clarify if they are platform-specific or provide alternatives.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
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 is most familiar to Windows users. There is no mention of Linux or macOS equivalents, nor any reference to common Linux shell environments (bash, sh, etc.). The file structure and tooling instructions are generic, but the command-line bias may make Linux/macOS users feel excluded or uncertain about compatibility.
Recommendations
  • Provide command-line examples using bash or sh syntax alongside PowerShell, or use generic code blocks for cross-platform commands like 'npm install'.
  • Add a note clarifying that all npm and webpack commands work the same way on Linux/macOS terminals.
  • Explicitly mention Linux/macOS compatibility in the prerequisites or installation sections.
  • Avoid using PowerShell-specific code blocks for generic npm commands; use 'console' or 'bash' where appropriate.
  • If there are any platform-specific caveats (e.g., file paths, permissions), call them out for Linux/macOS users.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-create-store-locator.md ...n/articles/azure-maps/tutorial-create-store-locator.md
High Priority View Details →
Scanned: 2025-08-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (Excel, Notepad), using Windows UI terminology (e.g., 'File > Save As...'), and showing screenshots from Windows applications. There are no instructions or examples for performing equivalent steps on Linux or macOS, such as converting Excel files to tab-delimited text or viewing/editing files. The tutorial assumes access to Microsoft Excel and Notepad, which are not standard on Linux systems, and does not mention or show how to use cross-platform or Linux-native tools for these tasks.
Recommendations
  • Provide alternative instructions for Linux and macOS users, such as using LibreOffice Calc or command-line tools (e.g., csvkit, awk, or ssconvert) to convert Excel files to tab-delimited text.
  • Include screenshots or command-line examples for Linux/macOS environments alongside Windows examples.
  • Use cross-platform terminology (e.g., 'text editor' instead of 'Notepad') and avoid assuming the presence of Windows-only applications.
  • Mention that Visual Studio Code is available on all major platforms, and suggest alternatives (e.g., Vim, Emacs, Sublime Text) for users who may not use VS Code.
  • Where UI navigation is described (e.g., 'File > Save As...'), clarify how to perform the equivalent action in LibreOffice or via command line.
  • Explicitly state that the tutorial is platform-agnostic and provide parity in setup and data preparation steps for all major operating systems.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-create-store-locator.md ...n/articles/azure-maps/tutorial-create-store-locator.md
High Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The tutorial exhibits a mild Windows bias by referencing Microsoft Excel and Notepad for data preparation and preview, and by describing UI actions (such as 'File > Save As...') in a way that is most familiar to Windows users. No Linux or cross-platform alternatives (such as LibreOffice, Google Sheets, or command-line tools) are mentioned for converting or viewing tab-delimited files. The only editor explicitly recommended is Visual Studio Code, which is cross-platform, but the workflow and screenshots assume a Windows environment. There are no explicit PowerShell or Windows command-line instructions, but the lack of Linux-specific guidance or examples may hinder parity.
Recommendations
  • When describing how to convert Excel files to tab-delimited text, mention cross-platform alternatives such as LibreOffice Calc or Google Sheets, and provide instructions for those tools.
  • For viewing or editing text files, suggest cross-platform editors (e.g., VS Code, Sublime Text, nano, vim) instead of only Notepad.
  • Where UI actions are described (e.g., 'File > Save As...'), clarify that the steps may differ on non-Windows platforms and link to relevant documentation for Linux/macOS users.
  • Consider providing command-line alternatives for data conversion (e.g., using csvkit or pandas in Python) for users who prefer or require CLI workflows.
  • Add a note or section confirming that all steps can be performed on Linux/macOS, and highlight any differences or additional requirements.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-create-store-locator.md ...n/articles/azure-maps/tutorial-create-store-locator.md
High Priority View Details →
Scanned: 2025-08-06 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The tutorial exhibits a mild Windows bias by exclusively referencing Microsoft Excel and Notepad for data preparation and preview, and by describing UI steps using Windows-centric terminology (e.g., 'File > Save As...', 'Text (Tab delimited)(*.txt)'). There are no Linux or cross-platform alternatives mentioned for converting Excel files or viewing text files. The recommended development environment is Visual Studio Code, which is cross-platform, but no explicit Linux instructions or screenshots are provided. No PowerShell or Windows command-line tools are used, but the data preparation workflow assumes access to Microsoft Office tools, which are less common on Linux.
Recommendations
  • Include instructions or alternatives for Linux users to convert Excel files to tab-delimited text, such as using LibreOffice Calc or command-line tools like csvkit or ssconvert.
  • Mention cross-platform text editors (e.g., VS Code, Sublime Text, nano) instead of only Notepad for viewing/editing text files.
  • Clarify that Visual Studio Code is available on Windows, Linux, and macOS, and provide links or notes for Linux installation.
  • Where UI steps are described (e.g., 'File > Save As...'), add notes for equivalent steps in LibreOffice or Google Sheets.
  • Add a section or callout box summarizing Linux/macOS-specific setup steps, if any, to ensure parity.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/drawing-error-visualizer.md ...b/main/articles/azure-maps/drawing-error-visualizer.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It refers to the 'File Explorer dialog' and uses terminology and UI patterns most familiar to Windows users, without mentioning Linux equivalents (such as file managers like Nautilus, Dolphin, or generic 'file picker'). The only API development tool mentioned is Postman, which is cross-platform, but no command-line (e.g., curl) or Linux-native alternatives are suggested. There are no explicit PowerShell or Windows command-line examples, but the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • When referencing file dialogs, use neutral language such as 'file picker dialog' or mention both Windows (File Explorer) and Linux (file manager, e.g., Nautilus, Dolphin) equivalents.
  • Provide examples or mention alternative API tools such as curl or httpie, which are commonly used on Linux.
  • Explicitly state that the instructions apply to all platforms and, where relevant, provide Linux-specific notes (e.g., how to unzip files or open HTML files in common Linux browsers).
  • Avoid assuming the user is on Windows; use cross-platform terminology and examples throughout.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-data-registries.md ...n/articles/azure-maps/how-to-create-data-registries.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily by referencing Windows-specific tools (Guidgen.exe, Visual Studio) for GUID generation, without mentioning cross-platform or Linux alternatives. There are no command-line examples for Linux/macOS users, and the only tool suggested for GUID generation is a Windows utility. The documentation also implicitly assumes use of the Azure Portal UI, which is cross-platform, but where command-line or scripting is referenced, it is Windows-centric.
Recommendations
  • When suggesting GUID generation, include cross-platform alternatives such as the uuidgen command (available on Linux/macOS) or PowerShell's [guid]::NewGuid() for Windows, and note that online GUID generators are also available.
  • Wherever a Windows-specific tool is mentioned (e.g., Guidgen.exe), provide equivalent commands or tools for Linux/macOS.
  • If showing command-line or scripting examples, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) equivalents.
  • Explicitly state that all steps can be performed on any OS via the Azure Portal, and provide CLI/REST API examples where appropriate.
  • Review all tool recommendations to ensure they are not Windows-exclusive, or at least present cross-platform options with equal prominence.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-create-store-locator.md ...n/articles/azure-maps/tutorial-create-store-locator.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial demonstrates a mild Windows bias, particularly in the data preparation steps. It exclusively references Microsoft Excel and Notepad for converting and viewing data files, and describes UI actions (e.g., 'File > Save As...') in a way that is specific to Windows applications. There are no instructions or examples for performing these steps on Linux or macOS, nor are alternative tools mentioned. The recommended IDE is Visual Studio Code, which is cross-platform, but the workflow and screenshots assume a Windows environment.
Recommendations
  • Provide alternative instructions for Linux and macOS users for converting Excel files to tab-delimited text, such as using LibreOffice Calc, csvkit, or command-line tools like 'ssconvert' or 'in2csv'.
  • Mention and show examples of opening and editing text files using cross-platform editors (e.g., VS Code, nano, vim, gedit) instead of only Notepad.
  • Avoid UI instructions that are specific to Windows applications (like Excel's 'Save As' dialog) or supplement them with equivalent steps for LibreOffice or command-line tools.
  • Include screenshots or notes that reflect cross-platform usage, or explicitly state that the steps apply regardless of OS, with links to relevant Linux/macOS resources.
  • Clarify that Visual Studio Code is available on all major platforms and that any suitable editor or IDE can be used.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in the section on retrieving the Azure Maps Client ID programmatically. PowerShell is presented first, with a detailed example using the Get-AzMapsAccount cmdlet, which is specific to Windows environments. The Azure CLI example is provided second, but there are no Linux- or macOS-specific shell examples (e.g., Bash, curl, jq), nor is there mention of cross-platform scripting approaches. The documentation also references Windows-centric tools and patterns (PowerShell) without providing parity for Linux users.
Recommendations
  • Provide Bash (Linux/macOS) shell examples alongside PowerShell, using curl and jq to retrieve the Client ID via the Azure REST API or Azure CLI.
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly state that both PowerShell and Azure CLI are available on all major platforms, and clarify any platform-specific requirements.
  • Avoid assuming the use of Windows tools (such as PowerShell) as the default or primary method.
  • Where possible, use cross-platform tools and patterns in code samples to ensure inclusivity for Linux and macOS users.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/elevation-data-services.md ...ob/main/articles/azure-maps/elevation-data-services.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it does mention using Ubuntu on WSL for rio-rgbify (acknowledging Windows limitations), the overall flow assumes a Windows environment (e.g., mounting drives with drvfs, referencing D: drives, and using Azure Storage Explorer, which is primarily a Windows GUI tool). There are no explicit Linux-native or macOS-native instructions for key steps like uploading to Azure Blob Storage or running the workflow outside WSL. The documentation also references Windows filesystem conventions and tools before or instead of cross-platform or Linux-native alternatives.
Recommendations
  • Provide explicit Linux and macOS instructions for all steps, not just WSL/Ubuntu. For example, show how to run rio-rgbify natively on Linux and macOS.
  • Offer command-line alternatives for uploading to Azure Blob Storage, such as using the Azure CLI (az storage blob upload), which is cross-platform.
  • Avoid referencing Windows drive letters (e.g., D:) and drvfs mounting in the main instructions. Instead, provide platform-agnostic or platform-specific sections.
  • Mention and demonstrate open-source or cross-platform tools where possible, and clarify when a tool is Windows-only.
  • Ensure screenshots and UI walkthroughs are not exclusively from Windows environments, or provide equivalents for other OSes.
  • Add a section or callouts for macOS users, especially for steps involving QGIS, Python, and Azure tools.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-data-registries.md ...n/articles/azure-maps/how-to-create-data-registries.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily through its recommendation of the Windows-only Guidgen.exe tool for generating GUIDs, without mentioning cross-platform alternatives. There are no Linux or macOS-specific instructions or examples, and the only tool explicitly mentioned for a technical task is a Windows tool. Additionally, the documentation does not provide command-line or scripting examples (e.g., PowerShell, Bash, Azure CLI), but when it does suggest a tool, it defaults to a Windows solution.
Recommendations
  • When suggesting GUID generation, include cross-platform options such as 'uuidgen' (available on Linux/macOS/Windows), Python's uuid module, or online GUID generators.
  • Avoid referencing Windows-only tools (like Guidgen.exe) without providing alternatives for other platforms.
  • Where possible, provide Azure CLI or REST API command-line examples for common tasks (e.g., creating managed identities, uploading blobs), and show both Windows (PowerShell/CMD) and Linux/macOS (Bash) syntax.
  • Explicitly state that all steps can be performed from any OS using the Azure Portal or cross-platform tools.
  • If screenshots are used, consider including at least one from a non-Windows environment, or clarify that the portal UI is OS-agnostic.
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: 2025-07-08 04:23
Reviewed by: Unknown
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 using PowerShell commands for all shell-based instructions, such as creating projects, installing packages, and setting environment variables. There are no equivalent examples for Linux or macOS shells (e.g., Bash), and the syntax for setting environment variables is only shown in PowerShell format. This may hinder Linux/macOS developers from following the guide smoothly.
Recommendations
  • For every PowerShell command, provide an equivalent Bash (Linux/macOS) example, especially for dotnet CLI usage and setting environment variables.
  • When showing how to set environment variables, include both PowerShell and Bash syntax (e.g., $Env:VAR=... for PowerShell, export VAR=... for Bash).
  • Add a note at the start of the guide clarifying that examples are provided for both Windows (PowerShell) and Linux/macOS (Bash) users.
  • Consider using cross-platform neutral language and tools where possible, or explicitly mention platform differences.
  • Review screenshots and UI instructions to ensure they are not Windows-specific unless necessary.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for project creation, file creation, environment variable setup, and program execution use PowerShell syntax, with no equivalent Bash or Linux/macOS shell commands provided. Windows tools and patterns (e.g., PowerShell's New-Item, $Env:VAR) are used exclusively, and Linux alternatives are not mentioned or shown. This may hinder Linux/macOS users, who form a significant portion of the Java development community.
Recommendations
  • For every PowerShell example, provide an equivalent Bash/Linux/macOS shell example side-by-side or in a tabbed interface.
  • When showing environment variable setup, include both PowerShell ($Env:VAR=) and Bash (export VAR=) syntax.
  • For file creation, show both New-Item (PowerShell) and touch (Bash) commands.
  • For running Java programs, show both Windows (java .\demo.java) and Linux/macOS (java ./demo.java) command syntax.
  • Explicitly state that the instructions apply to both Windows and Linux/macOS, and highlight any OS-specific differences.
  • Consider using cross-platform-neutral language and tools where possible, or at least avoid presenting Windows as the default or only option.
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: 2025-07-08 04:23
Reviewed by: Unknown
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. There are no Linux/macOS shell (bash) equivalents provided for creating directories, files, or setting environment variables. This may hinder Linux and macOS users, as the instructions are not directly applicable to their platforms.
Recommendations
  • Provide equivalent bash (Linux/macOS) commands alongside PowerShell for all shell-based instructions, such as project directory creation and environment variable setting.
  • When showing how to set environment variables, include both PowerShell and bash/zsh syntax (e.g., export VAR=value).
  • Consider using platform-agnostic language or clearly labeling which commands are for Windows and which are for Linux/macOS.
  • Add a note or section addressing cross-platform usage, ensuring parity and clarity for users on non-Windows systems.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands (e.g., mkdir, cd, npm init, npm install, node search.js) for all shell-based instructions, which are Windows-centric. No Linux or macOS shell equivalents (such as bash or sh) are provided, and there is no mention of cross-platform compatibility for these commands. This may create the impression that the guide is primarily intended for Windows users and could hinder Linux/macOS users who expect bash/zsh syntax.
Recommendations
  • Provide both PowerShell (Windows) and bash (Linux/macOS) command examples for all shell instructions, or use bash as the default for broader cross-platform compatibility.
  • Explicitly mention that the commands are cross-platform where applicable, or note any platform-specific differences.
  • Where screenshots or UI instructions are given, clarify if the steps are identical across platforms or provide alternatives if not.
  • Consider using 'terminal' or 'shell' instead of 'PowerShell' in code block labels unless the syntax is truly PowerShell-specific.
  • Add a short section or note at the beginning clarifying that the SDK and instructions are cross-platform and that examples are provided for both Windows and Linux/macOS users.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-sas-app.md ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting all command-line examples in PowerShell syntax, explicitly stating that Azure CLI is run in a PowerShell instance, and using variable assignment and command substitution patterns specific to PowerShell (e.g., $var = $(...)). There are no examples or notes for running the same commands in Bash or other Linux shells, nor is there guidance for Linux or macOS users. The only scripting example is in PowerShell, and the documentation assumes a Windows environment throughout.
Recommendations
  • Provide parallel Bash/Linux shell examples for all Azure CLI commands, including variable assignment and command substitution.
  • Add a note early in the document clarifying that Azure CLI commands can be run from any platform, and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash).
  • Where PowerShell-specific syntax is used (e.g., $var = $(...)), show the equivalent Bash syntax (e.g., var=$(...) or use export).
  • In the 'Complete script example' section, include a Bash version of the script.
  • Avoid language such as 'runs in a PowerShell instance' unless also mentioning Bash or cross-platform alternatives.
  • Ensure that references to tools or commands (such as Get-AzADUser) are either cross-platform or alternatives are provided for Linux users.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →