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 76-90 of 90 flagged pages
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/set-drawing-options.md
...s/blob/main/articles/azure-maps/set-drawing-options.md
Medium Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/spatial-io-read-write-spatial-data.md
...icles/azure-maps/spatial-io-read-write-spatial-data.md
Medium Priority
View Details →
Detected Bias Types
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.).
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/tutorial-ev-routing.md
...s/blob/main/articles/azure-maps/tutorial-ev-routing.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-dataset-geojson.md
...lob/main/articles/azure-maps/how-to-dataset-geojson.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/weather-service-tutorial.md
...b/main/articles/azure-maps/weather-service-tutorial.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/drawing-package-guide.md
...blob/main/articles/azure-maps/drawing-package-guide.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-daemon-app.md
...b/main/articles/azure-maps/how-to-secure-daemon-app.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-indoor-module.md
...b/main/articles/azure-maps/how-to-use-indoor-module.md
Medium Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-use-npm-package.md
...lob/main/articles/azure-maps/how-to-use-npm-package.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily demonstrates template deployment using the Azure portal, which is platform-agnostic, but references Azure PowerShell, Azure CLI, and REST API only in passing, without providing concrete examples for PowerShell or REST. The only command-line examples given are for Azure CLI, which is cross-platform, but the 'Deploy templates' link points to a PowerShell-focused page, and no Linux/macOS-specific considerations or examples are provided. There is a subtle Windows-first bias in the ordering and linking of deployment methods.
Recommendations
- Provide explicit examples for deploying the ARM template using Azure CLI (already present for resource management, but not for deployment), and REST API, alongside PowerShell.
- Ensure that links to deployment methods include both PowerShell and CLI documentation, or link to a page that covers all platforms equally.
- Add notes or examples for Linux/macOS users, such as installation instructions for Azure CLI and PowerShell on those platforms.
- Consider reordering or clarifying that all deployment methods are equally supported across platforms.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page includes a code sample for installing npm packages using PowerShell syntax (npm install --save-dev style-loader css-loader), which is typically associated with Windows environments. There are no explicit Linux/macOS shell examples (e.g., Bash), and the installation command is presented in a way that may imply Windows-first usage. However, the rest of the documentation is platform-agnostic, focusing on JavaScript and HTML, which are cross-platform.
Recommendations
- Provide installation command examples using Bash syntax (e.g., $ npm install --save-dev style-loader css-loader) alongside PowerShell, or use a generic prompt symbol.
- Clarify that the npm installation command works on all platforms, not just Windows.
- Avoid using PowerShell-specific formatting unless Windows-only instructions are necessary.
- Consider adding a note or section for Linux/macOS users regarding any platform-specific steps or differences.
Azure Maps
How to use the Azure Maps map control npm package
...lob/main/articles/azure-maps/how-to-use-npm-package.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently uses PowerShell syntax (e.g., 'npm install' and 'npm init' shown as PowerShell code blocks) for all command-line examples, which may imply a Windows-centric approach. There are no explicit Linux/macOS command-line examples, and no mention of platform-specific differences or considerations. While the npm and webpack workflows are cross-platform, the exclusive use of PowerShell syntax and lack of Linux/macOS references could create minor friction for non-Windows users.
Recommendations
- Use generic shell (bash) syntax for npm commands, or provide both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) examples.
- Add a note clarifying that npm and webpack commands work on all major platforms and that the examples are platform-agnostic.
- Avoid labeling code blocks as 'powershell' unless Windows-specific syntax is required; use 'bash' or untyped code blocks for cross-platform commands.
- Mention any platform-specific considerations, such as file path formats or browser opening instructions, if relevant.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page includes a command-line example for installing webpack loaders using PowerShell syntax (`npm install --save-dev style-loader css-loader`), which is most commonly associated with Windows environments. No equivalent Linux/macOS shell example (e.g., Bash) is provided. Additionally, the only explicit command-line example is in PowerShell, and it appears before any mention of cross-platform usage, which may create friction for Linux/macOS users.
Recommendations
- Provide Bash shell equivalents for all command-line examples, e.g., `npm install --save-dev style-loader css-loader` in a generic shell block.
- Clarify that the npm install command works on all platforms and is not specific to PowerShell.
- Avoid labeling command blocks as 'powershell' unless Windows-specific syntax is required.
- Add notes or examples for Linux/macOS users where relevant, especially for steps involving local development or bundler configuration.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/spatial-io-read-write-spatial-data.md
...icles/azure-maps/spatial-io-read-write-spatial-data.md
Low Priority
View Details →
Detected Bias Types
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.
Azure Maps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-creator-wfs.md
...cs/blob/main/articles/azure-maps/how-to-creator-wfs.md
Low Priority
View Details →
Detected Bias Types
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.