Azure Maps

170
Total Pages
150
Linux-Friendly Pages
20
Pages with Bias
11.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (24)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-npm-package.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-indoor-module.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/drawing-error-visualizer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-data-registries.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/spatial-io-read-write-spatial-data.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools
Summary:
The documentation is generally cross-platform and browser/JavaScript focused, but there is a subtle Windows bias in the example proxy service implementation, which uses an .ashx handler (ASP.NET), a Windows/IIS technology. There are no explicit PowerShell or Windows command-line examples, and no overt prioritization of Windows tools or patterns elsewhere. However, the proxy example may be confusing or less directly applicable to Linux or non-Windows developers.
Recommendations:
  • Provide proxy service examples using cross-platform technologies (e.g., Node.js/Express, Python/Flask, or a generic HTTP server) alongside or instead of .ashx/ASP.NET.
  • Clarify that the proxy service can be implemented in any web technology, and provide links or code snippets for Linux-friendly implementations.
  • Avoid referencing technology-specific file extensions (like .ashx) without alternatives or explanation.
  • Explicitly state that all JavaScript examples are platform-agnostic and can be used on any OS with a compatible browser.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/set-drawing-options.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation includes a code sample for installing npm packages using PowerShell syntax (npm install --save-dev style-loader css-loader) and does not provide a corresponding Linux/macOS shell example. The only explicit command-line example uses PowerShell, and there is no mention of Linux or cross-platform shell usage. This may lead Linux or macOS users to feel the documentation is Windows-centric.
Recommendations:
  • Provide shell command examples using a generic shell prompt (e.g., $ or #) or include both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples.
  • Explicitly mention that the npm commands work across platforms, or note any platform-specific differences if they exist.
  • Avoid using PowerShell-specific prompts (>) unless the example is truly Windows-only.
  • Consider adding a note or section for Linux/macOS users, especially when discussing local development, npm, or bundler configuration.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/spatial-io-read-write-spatial-data.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation is generally cross-platform and browser/JavaScript focused, but there is a subtle Windows bias in the proxy service example, which uses an .ashx handler (a Windows/IIS/ASP.NET-specific pattern). There are no explicit Linux or cross-platform proxy service examples, and the documentation does not mention how to implement the proxy on non-Windows platforms. No PowerShell or Windows command-line examples are present, but the only server-side implementation detail given is Windows-specific.
Recommendations:
  • Replace or supplement the .ashx proxy service example with cross-platform alternatives, such as Node.js (Express), Python (Flask), or Nginx proxy configurations.
  • Explicitly mention that the proxy service can be implemented in any language or platform, and provide links or code snippets for Linux-friendly implementations.
  • Avoid referencing Windows/IIS/ASP.NET-specific file extensions or handlers as the default or only example.
  • Add a note or section on deploying the proxy service on Linux-based environments (e.g., Azure App Service for Linux, Docker containers, etc.).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-ev-routing.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial assumes and instructs users to use Visual Studio Code (VS Code) and its integrated terminal for all steps, including installing Python packages and opening Jupyter Notebooks. There are no references to Linux-specific environments, tools, or alternative editors (such as JupyterLab, classic Jupyter Notebook, or command-line usage). All instructions and screenshots are tailored to the Windows/VS Code experience, with no mention of Linux or macOS workflows, terminal commands, or potential differences in file management or environment setup.
Recommendations:
  • Add explicit instructions for Linux and macOS users, including how to install Python packages using a standard terminal (e.g., bash/zsh) and how to open Jupyter Notebooks using JupyterLab or the classic Jupyter Notebook interface.
  • Include alternative steps for opening notebooks outside of VS Code, such as using the command line: `jupyter notebook EVrouting.ipynb` or `jupyter lab EVrouting.ipynb`.
  • Mention that the tutorial works on all major operating systems (Windows, Linux, macOS) and highlight any OS-specific considerations (such as file paths or package installation nuances).
  • Provide screenshots or notes that reflect the experience on Linux (e.g., GNOME Terminal, KDE Konsole) and macOS (Terminal.app), or at least clarify that the steps are similar across platforms.
  • Avoid implying that Visual Studio Code is required; clarify that any Jupyter-compatible environment can be used.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-create-store-locator.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dataset-geojson.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by recommending the use of Guidgen.exe (a Windows/Visual Studio tool) for generating GUIDs, without mentioning any Linux or cross-platform alternatives. There are no command-line or tool examples for Linux users, and the only tool explicitly referenced is Windows-specific.
Recommendations:
  • Mention cross-platform or Linux-native GUID generation tools, such as uuidgen (available on most Linux distributions) or online GUID generators.
  • Provide example commands for generating GUIDs on Linux/macOS (e.g., `uuidgen` in bash) alongside the Windows/Guidgen.exe example.
  • Review the documentation for other tool or workflow recommendations to ensure Linux and macOS users have clear, equivalent instructions.
  • Where possible, use neutral language and tool recommendations that apply to all platforms, or always provide both Windows and Linux/macOS alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/azure-maps-authentication.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-creator-wfs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides HTTP request examples for querying datasets using the Web Feature Service but does not include any platform-specific command-line examples (such as curl, PowerShell, or CLI). However, it also does not provide Linux/Unix-specific examples or mention Linux tools, which may leave Linux users without clear guidance on how to perform these actions from their environment.
Recommendations:
  • Add example commands using curl (commonly available on Linux, macOS, and Windows) to demonstrate how to make the HTTP GET requests.
  • If providing platform-specific instructions, ensure parity by including both PowerShell (for Windows) and shell/curl (for Linux/macOS) examples.
  • Explicitly mention that the HTTP requests can be made from any platform using standard tools, and provide links or references to cross-platform tools where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/weather-service-tutorial.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently references Visual Studio Code (VS Code) and its terminal, but all instructions and screenshots assume a Windows environment. There are no explicit mentions or examples for Linux or macOS users, such as alternative ways to open files, install packages, or use Jupyter Notebooks outside VS Code. The 'Open Jupyter Notebook' section describes right-clicking and menu options specific to Windows Explorer and VS Code on Windows, with no mention of Linux file managers or command-line alternatives.
Recommendations:
  • Add instructions and screenshots for opening Jupyter Notebooks on Linux and macOS, including command-line alternatives (e.g., 'code weatherDataMaps.ipynb' or 'jupyter notebook weatherDataMaps.ipynb').
  • Clarify that pip commands can be run in any terminal (not just the 'Visual Studio terminal'), and provide guidance for Linux/macOS users (e.g., using 'python3 -m pip' if needed).
  • Mention that VS Code is cross-platform and provide links or notes about installing and using it on Linux/macOS.
  • Where file paths are referenced (e.g., './data/weather_dataset_demo.csv'), clarify that these are POSIX-style and will work on Linux/macOS, but also note any differences if relevant.
  • Include a note or section on using Jupyter Notebooks outside of VS Code, such as with the standalone JupyterLab or classic Jupyter Notebook interface, which are common on Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/drawing-package-guide.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation is heavily oriented towards Autodesk's AutoCAD® software, which is primarily a Windows application. All CAD command examples and screenshots are based on AutoCAD, with no mention of Linux-compatible CAD tools or workflows. There are no examples or instructions for preparing drawing packages using Linux-based tools, nor is there guidance for users who may not have access to AutoCAD or Windows environments.
Recommendations:
  • Include references to cross-platform or Linux-compatible CAD software (e.g., LibreCAD, BricsCAD, DraftSight) and clarify which features/commands are required from the CAD tool.
  • Provide equivalent instructions or workflows for preparing DWG files and manifest files using Linux-based tools, or at least acknowledge the limitations and suggest alternatives.
  • Add screenshots and command references from at least one Linux-compatible CAD application.
  • Clarify any requirements that are specific to AutoCAD and suggest workarounds or alternatives for users on non-Windows platforms.
  • Consider providing a table or appendix comparing CAD commands and features across popular Windows and Linux CAD tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/elevation-data-services.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-create-data-registries.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-csharp-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-java-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-daemon-app.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a subtle Windows bias by listing 'Windows Service' as a primary example of a daemon application and omitting explicit Linux equivalents (such as 'systemd service' or 'Linux daemon'). There are no command-line examples, but all references to hosting environments and tools are Azure-centric or Windows-first, with no mention of Linux-specific patterns, tools, or terminology. No Linux or cross-platform CLI examples are provided for key tasks such as certificate management or service hosting.
Recommendations:
  • Include Linux-specific examples of daemon applications, such as 'systemd service' or 'Linux background process', alongside 'Windows Service'.
  • When discussing hosting environments, explicitly mention Linux-based Azure hosting options (e.g., Azure App Service for Linux, Azure Virtual Machines running Linux) and on-premises Linux servers.
  • Provide cross-platform or Linux-specific instructions for tasks like certificate management (e.g., using OpenSSL), secret storage, and service registration.
  • Add example commands or scripts for both Windows (PowerShell) and Linux (Bash) where relevant, especially for authentication flows and API requests.
  • Use neutral terminology such as 'background service' or 'daemon' rather than only 'Windows Service' to ensure inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-sas-app.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-indoor-module.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation shows 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 or macOS shell examples, and the use of the PowerShell prompt (>) may confuse users on other platforms. However, the overall content is largely cross-platform JavaScript/HTML, and no Windows-specific tools or patterns are otherwise promoted.
Recommendations:
  • Replace PowerShell prompt (>) in npm install commands with a generic shell prompt ($) or omit the prompt entirely to avoid confusion.
  • Explicitly mention that npm commands work on Windows, Linux, and macOS, and provide examples using the standard shell prompt.
  • Where command-line instructions are given, provide both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) examples if there are any differences.
  • Add a note clarifying that all JavaScript and npm instructions are cross-platform unless otherwise stated.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-npm-package.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
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, nor any mention of platform-specific considerations for non-Windows users. While the content itself is cross-platform (Node.js/npm/webpack), the exclusive use of PowerShell code blocks and lack of bash/sh alternatives can be perceived as a Windows-first bias.
Recommendations:
  • Provide all command-line examples in both PowerShell and bash (or generic shell) formats, or use neutral code blocks without specifying a shell.
  • Add a note clarifying that all commands work on Windows, Linux, and macOS, and mention any platform-specific differences if applicable.
  • Where possible, use the 'sh' or no language tag for npm commands, as they are cross-platform.
  • Consider including screenshots or instructions for running the project on Linux/macOS, or at least acknowledge those platforms in the prerequisites or installation sections.