Azure Maps

301
Total Pages
286
Linux-Friendly Pages
15
Pages with Bias
5.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

29 issues found
Showing 1-25 of 29 flagged pages
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (Azure Storage Explorer, WSL) are mentioned without Linux alternatives, and instructions for running rio-rgbify are given in the context of WSL (Windows Subsystem for Linux), implying a Windows-first audience. There are no explicit Linux or macOS instructions for tasks like uploading to Azure Blob Storage or running Azure Functions locally. The use of localhost and Windows drive mounting in WSL further reinforces the Windows-centric approach.
Recommendations
  • Provide explicit Linux and macOS instructions for all steps, including installing and running rio-rgbify natively (not via WSL), uploading files to Azure Blob Storage (e.g., using azcopy or Azure CLI), and running Azure Functions locally.
  • Mention cross-platform alternatives to Azure Storage Explorer, such as azcopy or Azure CLI, and provide example commands for Linux/macOS.
  • Avoid assuming WSL as the default for non-Windows users; include native Linux/macOS workflows.
  • Where file paths or commands are shown, use platform-agnostic syntax or provide both Windows and Linux/macOS examples.
  • Add notes or tables summarizing tool availability and installation steps for all major platforms.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily describes deploying an Azure Maps account via the Azure Portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) after the main Windows-centric workflow. The 'Deploy templates' link points to a PowerShell-focused page, and there are no explicit Linux or cross-platform examples for template deployment. While Azure CLI is used for post-deployment tasks, the initial deployment workflow and linked resources favor Windows/PowerShell users.
Recommendations
  • Provide explicit Azure CLI examples for deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell examples alongside PowerShell where scripts or commands are shown.
  • Reorder or clarify the 'Deploy the template' section to present Azure CLI and REST API methods equally with the Azure Portal and PowerShell.
  • Update the 'Deploy templates' link to point to a page covering all deployment methods (Portal, PowerShell, CLI, REST) rather than just PowerShell.
  • Add a note or section highlighting cross-platform compatibility and recommending tools for Linux/macOS users.
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-12-29 18:00
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 providing PowerShell commands for project setup, package installation, and environment variable configuration. No Bash or Linux shell equivalents are given, and all command-line examples assume a Windows/PowerShell environment. This may hinder Linux or macOS users who use Bash or other shells.
Recommendations
  • Provide equivalent Bash (or generic shell) command examples alongside PowerShell for creating projects, installing packages, and setting environment variables.
  • Explicitly mention that the .NET SDK and Azure CLI are cross-platform, and clarify that the instructions apply to Linux and macOS as well.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
  • Where screenshots or UI references are given, ensure they are not Windows-specific or provide alternatives if necessary.
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-12-29 18:00
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 management, without providing equivalent Linux/macOS shell examples. All CLI and environment variable instructions are shown in PowerShell syntax, and no mention is made of Bash or other Unix shells. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Provide equivalent Bash (Linux/macOS) examples alongside PowerShell commands for project setup (e.g., mkdir, cd, touch demo.py).
  • Show how to set environment variables in Bash (e.g., export AZURE_CLIENT_ID=...) in addition to PowerShell.
  • Explicitly mention cross-platform compatibility and direct users to choose the appropriate shell commands for their OS.
  • Consider using generic CLI commands (e.g., Azure CLI) in a way that is OS-agnostic, or provide both 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-dev-guide-js-sdk.md ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using PowerShell commands for project setup, package installation, and running scripts. No Linux or macOS shell equivalents (such as Bash) are provided, and Windows/PowerShell commands are presented first and exclusively. This may create confusion or extra work for developers using Linux or macOS systems.
Recommendations
  • Provide Bash equivalents for all PowerShell commands, such as using 'mkdir mapsDemo && cd mapsDemo' and 'npm init' in Bash.
  • Use generic cross-platform commands (e.g., 'node search.js') without PowerShell syntax, or show both PowerShell and Bash examples side by side.
  • Add a note clarifying that the commands work on Windows (PowerShell) and provide instructions for Linux/macOS users.
  • Where file system operations are shown, use syntax that is valid on all platforms, or explicitly show both.
  • Review all code blocks and tips to ensure Linux/macOS users are not excluded or forced to translate commands themselves.
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: 2025-12-29 18:00
Reviewed by: Unknown
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 instructions, which may imply a Windows-centric approach. There are no explicit Linux or macOS shell examples, nor any mention of platform-specific considerations for non-Windows environments. This could lead Linux/macOS users to feel the documentation is not tailored for them.
Recommendations
  • Provide command-line examples using generic shell syntax (e.g., bash) or use unmarked code blocks for cross-platform commands like 'npm install'.
  • Add notes clarifying that all npm commands work identically on Linux, macOS, and Windows, and that PowerShell is not required.
  • Where relevant, mention any platform-specific differences (such as file paths, permissions, or browser opening methods).
  • Consider alternating or combining shell and PowerShell examples, or use a neutral prompt (e.g., '$') for commands.
  • Explicitly state that the instructions apply to all major operating systems, and link to official Node.js installation guides for Linux/macOS as well as Windows.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-add-path-layer.md .../articles/azure-maps/power-bi-visual-add-path-layer.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation assumes the use of Power BI (a Windows-centric tool) and Power Query for data transformation, with no mention of Linux or cross-platform alternatives. All examples and instructions are tailored to the Windows/Power BI environment, and there are no references to how users on Linux or other platforms might perform equivalent tasks.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., Power BI Desktop is Windows-only, but Power BI Service is web-based and cross-platform).
  • Provide guidance or references for Linux users, such as using Power BI Service or alternative data transformation tools (e.g., pandas in Python) to prepare data.
  • Include equivalent data transformation examples using open-source or cross-platform tools (e.g., Python scripts for data unpivoting).
  • Clarify whether all features are available in the browser-based Power BI Service, and if not, suggest workarounds for non-Windows users.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-geocode.md ...ob/main/articles/azure-maps/power-bi-visual-geocode.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Power BI Desktop and SQL Server Data Tools (SSDT), both of which are primarily Windows applications. There are no examples or mentions of Linux or cross-platform alternatives for data categorization or geocoding workflows. The screenshots and instructions assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Include information about Power BI on the web and its feature parity for geocoding and data categorization, especially for non-Windows users.
  • Mention any available cross-platform or Linux-compatible tools for data modeling and categorization, or clarify platform limitations.
  • Add explicit notes about platform support and alternatives for users on Linux or macOS, such as using Power BI Service or Azure Data Studio.
  • Provide screenshots and instructions for web-based interfaces where possible, not just Windows desktop applications.
  • If certain features are Windows-only, clearly state this and suggest workarounds or alternatives for other platforms.
GitHub Create Pull Request
Azure Maps Create your Azure Maps account using an Azure Resource Manager template in Azure Maps ...lob/main/articles/azure-maps/how-to-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily demonstrates ARM template deployment via the Azure portal, which is platform-agnostic, but references Azure PowerShell before Azure CLI and REST API when mentioning alternative deployment methods. The link for 'Deploy templates' points to a PowerShell-focused page, and there are no explicit Linux/macOS-specific instructions or examples. CLI examples are present for resource review and cleanup, but the initial deployment workflow is Windows-centric.
Recommendations
  • Provide explicit Azure CLI deployment instructions alongside PowerShell, especially in the 'Deploy the template' section.
  • Ensure that links to further deployment documentation include both PowerShell and CLI options, or link to a page that covers all platforms equally.
  • Add a note clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation guidance for non-Windows platforms if relevant.
  • Consider showing CLI examples first or in parallel with PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the C# REST SDK ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell for all command-line examples, such as project creation, package installation, and environment variable setting. No Bash or Linux/macOS shell equivalents are provided, and Windows/PowerShell commands appear first and exclusively. This creates friction for Linux and macOS users who may not be familiar with PowerShell syntax or environment variable management.
Recommendations
  • Provide equivalent Bash/Linux/macOS shell commands for all PowerShell examples, especially for project creation, package installation, and environment variable setting.
  • Clearly indicate cross-platform compatibility of .NET CLI commands and environment variable setup.
  • Where screenshots or instructions reference Windows-specific tools or UI, add notes or alternatives for Linux/macOS users.
  • Consider reordering examples or providing tabs for Windows/PowerShell and Linux/Bash to improve parity.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Java REST SDK (preview) .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell for command-line examples, such as creating Maven projects, setting environment variables, and running Java programs. No Linux/macOS shell equivalents (e.g., Bash) are provided, and the PowerShell commands are presented as the only option. This creates friction for Linux/macOS users, who must translate commands themselves.
Recommendations
  • Provide Bash equivalents for all PowerShell command-line examples, including Maven project creation, environment variable setting, and running Java programs.
  • Clearly indicate which commands are for Windows/PowerShell and which are for Linux/macOS/Bash, ideally side-by-side.
  • Add notes or tips for cross-platform usage, especially for environment variable syntax differences.
  • Ensure screenshots and instructions referencing the Azure Portal are platform-neutral.
GitHub Create Pull Request
Azure Maps How to secure an Azure Maps application with a SAS token ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by presenting all CLI scripting examples in PowerShell syntax, referencing PowerShell sessions explicitly, and omitting any Linux/macOS shell equivalents. There are no bash or zsh examples, and the workflow assumes a Windows environment by default, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent bash/zsh shell examples alongside PowerShell, especially for Azure CLI commands and scripting.
  • Clarify that Azure CLI works cross-platform and note any differences in command syntax or environment variables between Windows and Linux/macOS.
  • Avoid referencing 'PowerShell session' as the default; instead, use 'terminal' or specify both PowerShell and bash/zsh options.
  • Add explicit instructions or troubleshooting notes for Linux/macOS users, such as file path conventions and environment variable usage.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the JavaScript REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for project setup and package installation, with no equivalent Linux/macOS shell (bash) examples. All CLI and script-running instructions are shown in PowerShell syntax, which may confuse or hinder Linux/macOS users. There is no mention of Linux/macOS alternatives or parity in the setup steps.
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, use 'node search.js' in a generic shell block or show both Windows (PowerShell) and Linux/macOS (bash) variants.
  • Explicitly state that commands work on Linux/macOS and Windows, or note any platform-specific differences.
  • Consider using generic shell blocks for cross-platform commands (e.g., 'sh' or 'bash' instead of 'powershell').
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Python REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for project setup and environment variable management, with no Linux/macOS shell equivalents provided. All CLI and environment variable examples are shown in PowerShell syntax, which may be unfamiliar or unusable for Linux/macOS users. There is no mention of Linux tools or shell commands (e.g., bash, export), and Windows-centric patterns are presented first and exclusively.
Recommendations
  • Provide equivalent bash/zsh (Linux/macOS) commands alongside PowerShell for all project setup steps (e.g., mkdir, cd, touch, export).
  • Show both Windows (PowerShell) and Linux/macOS (bash) syntax for setting environment variables.
  • Explicitly mention cross-platform compatibility and note any platform-specific differences.
  • Consider presenting examples for both platforms side-by-side or in tabs.
  • Avoid assuming PowerShell is the default shell for all users.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Python REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-py-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for project setup and environment variable management, with no equivalent Linux/macOS shell (bash) examples. All CLI and environment variable instructions are shown in PowerShell syntax, which is Windows-specific. There are no bash or cross-platform alternatives provided, making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide bash equivalents for all PowerShell commands, especially for creating directories, files, and setting environment variables.
  • When showing CLI commands, present both Windows (PowerShell) and Linux/macOS (bash) examples side-by-side.
  • Add a note clarifying that the examples are shown in PowerShell and provide links or inline examples for Linux/macOS users.
  • Consider using cross-platform commands (e.g., 'python -m venv', 'touch demo.py', 'export VAR=value') where possible.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias, particularly in the section on retrieving the Azure Maps Client ID programmatically. PowerShell is mentioned first and in detail, with a full example, while the Azure CLI (cross-platform) is mentioned second and less prominently. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored to those platforms. The use of PowerShell and references to Windows-centric tools may create friction for Linux/macOS users, though most tasks can still be completed using Azure CLI or REST APIs.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add Bash or shell script examples for Linux/macOS users where programmatic access is discussed.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Avoid language that implies PowerShell is the default or preferred method.
  • Where possible, provide REST API examples for direct HTTP requests, which are platform-agnostic.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the C# REST SDK ...ain/articles/azure-maps/how-to-dev-guide-csharp-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell for all command-line examples, including project creation, package installation, and environment variable setup. No Linux/macOS shell equivalents (e.g., Bash) are provided, and Windows/PowerShell patterns are presented first and exclusively. This creates friction for Linux/macOS users, who must translate commands themselves.
Recommendations
  • Provide equivalent Bash examples alongside PowerShell for project creation, package installation, and environment variable setup.
  • Explicitly state cross-platform compatibility for all CLI commands and environment variable patterns.
  • Add notes or tables showing both Windows (PowerShell) and Linux/macOS (Bash) commands where relevant.
  • Consider using generic .NET CLI commands (e.g., 'dotnet new', 'dotnet add package') without shell-specific syntax when possible.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the JavaScript REST SDK (preview) ...ob/main/articles/azure-maps/how-to-dev-guide-js-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell commands for project setup and package installation, with no mention of Linux/macOS shell equivalents (e.g., bash). All CLI and file system examples are shown in PowerShell syntax, and instructions for running scripts use 'node search.js' in PowerShell code blocks. This may create friction for Linux/macOS users unfamiliar with PowerShell, and omits bash/zsh alternatives.
Recommendations
  • Provide equivalent bash/zsh commands alongside PowerShell examples for all project setup, npm installation, and file operations.
  • Use generic shell code blocks (e.g., 'bash') for commands that work cross-platform, or explicitly show both Windows and Linux/macOS alternatives.
  • Clarify that 'node search.js' can be run from any terminal, not just PowerShell.
  • Add notes or sections for Linux/macOS users regarding environment variable setup and file system commands.
GitHub Create Pull Request
Azure Maps How to create Azure Maps applications using the Java REST SDK (preview) .../main/articles/azure-maps/how-to-dev-guide-java-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell and Windows-centric commands for project setup, file creation, environment variable management, and program execution. There are no equivalent Linux/macOS shell (bash/zsh) examples provided, which may cause friction for non-Windows users. Windows tools and patterns are presented exclusively, and always first, with no mention of alternatives.
Recommendations
  • Provide equivalent bash/zsh commands for all PowerShell examples, including Maven project creation, file creation, environment variable setup, and program execution.
  • Add notes clarifying cross-platform compatibility and any differences in command syntax.
  • Where possible, use platform-neutral instructions (e.g., 'run mvn clean install from your terminal') and supplement with both Windows and Linux/macOS command examples.
  • Explicitly mention that all steps can be performed on Linux/macOS and provide troubleshooting tips for common platform-specific issues.
GitHub Create Pull Request
Azure Maps How to secure an Azure Maps application with a SAS token ...blob/main/articles/azure-maps/how-to-secure-sas-app.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively presenting Azure CLI usage within a PowerShell context, using Windows-style variable assignment and command substitution syntax. There are no explicit Linux/macOS shell examples, and instructions repeatedly reference PowerShell as the assumed environment. This may cause friction for Linux/macOS users unfamiliar with PowerShell syntax or conventions.
Recommendations
  • Provide equivalent Bash shell examples for all Azure CLI commands, using standard Bash variable assignment and command substitution (e.g., $(...) instead of $()).
  • Clarify that Azure CLI works cross-platform and specify which commands are shell-agnostic.
  • Avoid referencing PowerShell as the default environment; instead, present both PowerShell and Bash examples side-by-side or indicate how users can adapt commands for their shell.
  • Mention any platform-specific considerations (e.g., file path formats, quoting) where relevant.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing 'Windows Service' as a primary example of a daemon application, while not mentioning Linux equivalents such as 'systemd service' or 'Linux daemon.' There are no explicit Linux or cross-platform examples provided for hosting or configuring daemon applications, nor are Linux-specific tools or patterns referenced. The instructions and screenshots focus exclusively on Azure Portal and general Azure concepts, without addressing Linux hosting scenarios or command-line examples (e.g., systemd, bash, etc.).
Recommendations
  • Include Linux-specific examples for hosting daemon applications, such as referencing 'systemd service' alongside 'Windows Service.'
  • Add instructions or code samples for configuring authentication and secrets retrieval in Linux environments (e.g., using bash, curl, or systemd service files).
  • Provide parity in terminology and examples, ensuring both Windows and Linux hosting scenarios are addressed equally.
  • Where possible, include cross-platform SDK usage or REST API calls from both Windows and Linux perspectives.
  • Explicitly mention Linux as a supported environment for daemon applications in Azure Maps, and link to relevant Linux documentation.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/how-to-secure-device-code.md .../main/articles/azure-maps/how-to-secure-device-code.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing 'Desktop app' scenarios and providing instructions and links that implicitly target Windows environments. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or patterns mentioned. The guidance assumes use of Microsoft Authentication Library (MSAL) and desktop application flows, which are typically associated with Windows, without clarifying Linux compatibility or providing Linux-centric instructions.
Recommendations
  • Add explicit Linux examples for device code flow authentication, including command-line usage and sample code for common Linux languages (e.g., Python, Bash).
  • Clarify that MSAL libraries are available for Linux and provide installation instructions for Linux environments.
  • Include screenshots or instructions for registering applications and configuring authentication using Linux tools (e.g., Azure CLI, cross-platform editors).
  • Reference cross-platform or Linux-specific documentation where relevant, and avoid assuming a desktop/Windows environment in examples and terminology.
  • Mention and demonstrate how to make REST API calls using Linux-native tools (e.g., curl, wget) in addition to generic HTTP clients.
GitHub Create Pull Request
Azure Maps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/power-bi-visual-conversion.md ...main/articles/azure-maps/power-bi-visual-conversion.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page assumes the use of Power BI Desktop, which is only available on Windows. There are no mentions of Linux or cross-platform alternatives, nor are there instructions or guidance for users on Linux or macOS. All examples and migration steps are implicitly Windows-centric due to Power BI Desktop's platform limitation.
Recommendations
  • Explicitly state that Power BI Desktop is only available on Windows, and clarify options for Linux/macOS users (e.g., using Power BI Service, remote desktop solutions, or alternatives).
  • If possible, provide guidance for users who need to perform these tasks from non-Windows environments, such as using Power BI Service or other supported methods.
  • Mention any known limitations or workarounds for Linux/macOS users regarding map visual migration.
  • Consider including a note about platform support at the beginning of the article to set expectations for cross-platform users.
GitHub Create Pull Request
Azure Maps Authentication with Microsoft Azure Maps .../main/articles/azure-maps/azure-maps-authentication.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for retrieving the Azure Maps Client ID, but PowerShell (a Windows-centric tool) is presented first, and the tip is explicitly labeled 'When using PowerShell'. There are no Linux/macOS-specific shell examples (e.g., Bash), and no mention of platform-specific considerations for Linux/macOS users. The rest of the documentation is generally platform-neutral, focusing on REST APIs and Azure concepts.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for common authentication tasks to improve accessibility for Linux/macOS users.
  • Add a note clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is most commonly used on Windows.
  • Where possible, avoid labeling examples by platform unless there is a functional difference.
GitHub Create Pull Request
Azure Maps How to use the Azure Maps map control npm package ...lob/main/articles/azure-maps/how-to-use-npm-package.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently uses PowerShell syntax (e.g., 'npm install' and 'npm init' shown as PowerShell code blocks) for all CLI commands, which may imply a Windows-centric approach. There are no explicit Linux/macOS examples or terminal instructions, and PowerShell is not the default shell on Linux/macOS. This could create confusion or friction for non-Windows users, though the commands themselves are cross-platform.
Recommendations
  • Use generic shell/terminal code blocks (e.g., 'bash' or no language tag) for npm commands instead of 'powershell'.
  • Add notes clarifying that commands work on Linux/macOS terminals (bash/zsh) as well as Windows.
  • If there are platform-specific steps (e.g., opening HTML files), mention alternatives for Linux/macOS (such as 'xdg-open index.html' or 'open index.html').
  • Avoid implying PowerShell is required for npm usage; show examples in a neutral shell context.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →