103
Pages Scanned
22
Pages Flagged
103
Changed Pages
21.4%
% Pages Flagged
Scan Information
Started At: 2026-01-15 00:00:34
Finished At: 2026-01-15 20:51:26
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 103
Files Completed: 103
Problematic Pages
22 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, MSI installers, WinGet, and PowerShell commands. All setup instructions and examples for Artifact Signing client tools are exclusively for Windows environments, with no mention of Linux or macOS alternatives or equivalent signing workflows. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, the detailed guidance is only for Windows/SignTool.
Recommendations
- Add explicit instructions or examples for setting up Artifact Signing on Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or platform-agnostic .NET tools) if available.
- Clarify whether SignTool integration is Windows-only, and if so, provide parity by expanding detailed setup guides for other integrations (e.g., GitHub Actions, Azure DevOps) that work cross-platform.
- Include Linux/macOS installation commands for the .NET runtime and Artifact Signing SDK/dlib, using package managers like apt, yum, brew, etc.
- If Artifact Signing is not supported on Linux/macOS for certain workflows, state this explicitly to set user expectations.
Create Pull Request
Backup
Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file
...ackup/quick-backup-postgresql-flexible-server-bicep.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only PowerShell examples for deploying the Bicep template and restoring backups, with no mention of Azure CLI or Bash equivalents. The instructions and next steps are written from a Windows/PowerShell perspective, creating friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
- Add Azure CLI and Bash examples for deploying the Bicep template.
- Clearly state that both PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
- Ensure next steps include Linux/macOS-friendly instructions (e.g., restoring via Azure CLI).
- Where possible, mention cross-platform tools first or equally.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for using the Azure portal, Azure PowerShell, and ARM templates to manage identities in Azure API Management. However, all CLI/scripted examples use Azure PowerShell, which is primarily a Windows-centric tool, and there are no equivalent examples using Azure CLI (cross-platform) or bash scripts. PowerShell instructions are presented before ARM template examples, and there are no Linux/macOS-specific notes or parity guidance.
Recommendations
- Add Azure CLI examples alongside Azure PowerShell for all identity creation and management tasks.
- Explicitly state that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Where possible, provide bash or shell script equivalents for common operations.
- Present CLI examples in a neutral order (e.g., Azure CLI first, then PowerShell, or side-by-side).
- Include notes or links for Linux/macOS users about any platform-specific caveats.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides examples and instructions for both Windows and Linux environments, but there are several instances where Windows tools, commands, and patterns are mentioned first or exclusively. Windows-specific deployment and configuration steps are often presented before Linux equivalents, and PowerShell is referenced as a primary automation tool. Some CLI examples and troubleshooting steps focus on Windows scenarios, with Linux alternatives sometimes only briefly mentioned or relegated to tabs. There are also sections where Linux-specific instructions are less detailed or missing.
Recommendations
- Ensure all command-line instructions (az CLI, dotnet CLI, etc.) are presented for both Windows and Linux/macOS, ideally side-by-side or in clearly labeled tabs.
- When listing deployment or configuration options, present Windows and Linux approaches with equal prominence and detail.
- Avoid mentioning Windows tools (PowerShell, Visual Studio) before cross-platform alternatives (Azure CLI, Visual Studio Code) unless contextually necessary.
- Expand Linux/macOS troubleshooting and setup sections to match the depth of Windows coverage.
- Where PowerShell is referenced, provide equivalent bash/zsh examples for Linux/macOS users.
- Audit sample code and project file snippets to ensure Linux runtime identifiers and settings are included alongside Windows examples.
Azure Resource Manager
Relocate Azure Backup to Another Region
...rce-manager/management/relocation/relocation-backup.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides some examples and instructions that are Windows-centric, such as referencing Azure PowerShell scripts and listing Windows update instructions before Linux equivalents. Linux instructions are present but less detailed, and scripting examples are PowerShell-focused with no Bash or CLI alternatives. Some steps (e.g., certificate updates) mention Linux only briefly and refer users to external distributor guidance, rather than providing concrete steps or examples.
Recommendations
- Provide equivalent Bash/Azure CLI examples alongside PowerShell scripts for bulk VM protection and other automation tasks.
- Offer step-by-step instructions for updating trusted root certificates and CRLs on common Linux distributions, rather than referring users to distributor guidance.
- Ensure that Linux VM procedures are described with equal detail and clarity as Windows VM procedures.
- Where screenshots or UI steps are shown, clarify any OS-specific differences or provide Linux/macOS alternatives if relevant.
Backup
Delete a Microsoft Azure Recovery Services Vault
...blob/main/articles/backup/backup-azure-delete-vault.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary automation method, with detailed scripts and command references. Windows-specific tools (MARS, MABS, DPM consoles) are described in depth, while Linux alternatives for on-premises backup management are not mentioned. The ARMClient installation instructions use Chocolatey, a Windows package manager, with no Linux/macOS equivalents. The CLI section is limited in scope and does not provide parity with PowerShell capabilities, and there are no Bash or cross-platform scripting examples.
Recommendations
- Provide Bash or Azure CLI script examples for deleting vaults and backup items, especially for Linux/macOS users.
- Include instructions for installing ARMClient on Linux/macOS (e.g., via npm or direct download), not just via Chocolatey.
- Clarify which steps or tools are Windows-only and offer Linux/macOS alternatives where possible.
- Expand CLI support and documentation to cover more backup types, not just Azure VM backups.
- Add notes or links for Linux/macOS users on how to perform equivalent operations, especially for on-premises scenarios.
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation offers two deployment methods: Azure CLI and PowerShell script. The PowerShell script is explicitly labeled as 'Windows only,' and is presented alongside the cross-platform Azure CLI method. There are no Linux/macOS shell script equivalents provided, and PowerShell is the only scripting automation option mentioned. The ordering and labeling may imply a preference or greater support for Windows tooling.
Recommendations
- Add a Bash or shell script example for Linux/macOS users to automate the deployment process, mirroring the PowerShell script functionality.
- Clarify that the PowerShell script is Windows-only and suggest alternatives for Linux/macOS users, such as using Azure CLI or providing a sample Bash script.
- Consider listing the cross-platform Azure CLI method first, or explicitly stating that it is recommended for all platforms.
- If automation is important, provide guidance or templates for scripting with Bash/zsh on non-Windows platforms.
Reliability
Reliability in Azure Storage Mover
...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for associating job definitions to a new agent, without offering an equivalent example for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). Additionally, the instructions mention using the Azure portal or PowerShell first, rather than presenting cross-platform options equally.
Recommendations
- Add Azure CLI and/or REST API examples alongside the PowerShell example for updating job definitions.
- Explicitly mention that the Azure portal, PowerShell, Azure CLI, and REST API are all supported methods for agent assignment, and provide links or code samples for each.
- Ensure that instructions do not prioritize Windows-centric tools (PowerShell) over cross-platform alternatives.
- Where possible, clarify any platform-specific limitations or requirements.
Storage
Create multiple Azure Elastic SAN volumes in a batch
...storage/elastic-san/elastic-san-batch-create-sample.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides a PowerShell script for batch creation of Azure Elastic SAN volumes, with file path examples and scripting patterns typical of Windows environments. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI), nor mention of cross-platform alternatives. The use of Windows-style file paths and PowerShell-specific cmdlets further reinforces the Windows bias.
Recommendations
- Add equivalent Azure CLI or Bash script examples for batch volume creation.
- Include notes on how to run the process on Linux/macOS (e.g., file path formats, prerequisites).
- Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance if so.
- Present examples for both Windows and Linux/macOS environments, or explicitly state platform requirements.
Virtual Network Manager
What is IP address management (IPAM) in Azure Virtual Network Manager?
...rtual-network-manager/concept-ip-address-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure CLI examples using PowerShell-style syntax (backticks for line continuation and variable assignment with $), which is specific to Windows/PowerShell environments. There is no mention of Linux/macOS shell equivalents or examples using Bash syntax, which may cause confusion or friction for non-Windows users.
Recommendations
- Provide Azure CLI examples using Bash syntax (backslash for line continuation, variable assignment with export or plain assignment) alongside PowerShell examples.
- Explicitly state that the CLI commands can be run on Linux/macOS and provide any necessary syntax differences.
- Add notes or tabs to switch between PowerShell and Bash examples where appropriate.
VPN Gateway
Create site-to-site high bandwidth tunnels in the Azure portal
...cles/vpn-gateway/site-to-site-high-bandwidth-tunnel.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides critical configuration steps using Azure PowerShell commands, with no equivalent Azure CLI or REST API examples. PowerShell is a Windows-centric tool, and presenting only PowerShell commands creates friction for Linux/macOS users. Additionally, PowerShell instructions are given before mentioning that similar actions can be performed in the Azure portal, reinforcing a Windows-first approach.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line configuration steps, especially for enabling FastPath and PrivateLinkFastPath attributes.
- Explicitly mention that all steps can be completed in the Azure portal and provide portal navigation instructions wherever possible.
- Where device configuration examples are given, clarify that syntax may vary by vendor and OS, and provide links or references to Linux-based VPN device documentation if available.
- Consider including REST API equivalents for advanced users on any platform.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation lists .NET-based configuration providers first in all tables and feature matrices, with .NET Standard, ASP.NET Core, and .NET Framework libraries preceding Java, Python, JavaScript, and Go. However, the content covers cross-platform libraries and provides parity in feature tracking and sample links for all major languages, including Linux-friendly stacks. There are no Windows-specific tools, PowerShell examples, or exclusive references to Windows patterns.
Recommendations
- Consider rotating the order of provider libraries in tables or grouping by language family (e.g., statically typed, dynamically typed) to avoid implicit prioritization of Windows/.NET.
- Explicitly mention cross-platform compatibility for .NET Standard and ASP.NET Core providers, clarifying that they run on Linux/macOS as well as Windows.
- Add a brief note that all listed providers (except .NET Framework) are supported on Linux/macOS, to reassure non-Windows users.
- Ensure that future examples and sample links include Linux/macOS usage instructions where relevant.
Storage
Connect Azure Elastic SAN to Azure Kubernetes over iSCSI
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation lists both Azure PowerShell and Azure CLI as prerequisites, but mentions PowerShell first and provides PowerShell examples before CLI equivalents. This ordering and inclusion of PowerShell may subtly favor Windows users, though CLI examples are present and all core steps use cross-platform tools (kubectl, bash, YAML).
Recommendations
- List Azure CLI before Azure PowerShell in prerequisites and examples, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly note that Azure CLI is available on all platforms, while PowerShell may require additional setup on Linux/macOS.
- Where possible, provide CLI examples as the primary/default, with PowerShell as an alternative.
- Add a brief note clarifying that all kubectl/bash/YAML steps are platform-agnostic.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium v4 app creation, but lists PowerShell as a primary automation method alongside CLI. PowerShell is a Windows-centric tool, while CLI is cross-platform. The CLI examples are present and correct, but PowerShell is mentioned equally, which may imply parity or preference for Windows users. Additionally, in the 'Premium v4 availability' section, the Windows SKU CLI command is shown before the Linux SKU CLI command, indicating a slight 'windows_first' ordering bias.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows environments.
- Consider listing CLI examples before PowerShell examples to reinforce cross-platform parity.
- Explicitly state that all CLI commands work on Linux/macOS and Windows, and provide any Linux/macOS-specific notes if needed.
- Ensure that Linux-specific instructions (such as for custom containers) are as detailed as Windows instructions where relevant.
Azure App Configuration
How to use Agent Framework in a Python app with Azure App Configuration
...zure-app-configuration/howto-ai-agent-config-python.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning Linux/macOS (bash), and references Windows-specific Python setup documentation in prerequisites. However, Linux/macOS instructions are present and complete, so Linux users can follow along without major issues.
Recommendations
- Present environment variable instructions for all platforms in parallel or in a table, rather than listing Windows first.
- Add a link to Python installation/setup documentation for Linux/macOS alongside the Windows link in prerequisites.
- Consider using generic cross-platform instructions or clarify that all major platforms are supported.
API Management
VNet configuration settings | Azure API Management
...n/articles/api-management/virtual-network-reference.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_specific_endpoints
Summary
The documentation is generally platform-neutral and focuses on Azure networking concepts relevant to API Management in VNets. However, there are a few sections that mention Windows-specific endpoints and tools, such as KMS activation for Windows VMs and outbound connectivity for Windows Update and Windows Defender. These are presented as requirements only when Windows VMs are present, and do not affect the core API Management VNet configuration for Linux users. There are no PowerShell-only examples, and Linux equivalents are not missing for any critical configuration steps.
Recommendations
- Clarify that Windows-specific endpoints (KMS, Windows Update, Windows Defender) are only relevant when Windows VMs are present, and are not required for Linux-based API Management deployments.
- If possible, add a brief note or section outlining that Linux VMs do not require these endpoints, and reference any Linux-specific considerations if they exist.
- Ensure that any references to configuration tools (e.g., PowerShell) are accompanied by Azure CLI or ARM template equivalents, if relevant to API Management VNet setup.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are consistently shown after CLI and are included in all relevant sections. There is a slight 'windows_first' bias in that PowerShell is always present, but Linux/macOS users are not left without guidance, as CLI and bash examples are provided. No critical tasks are Windows-only, and Linux parity is generally maintained.
Recommendations
- Consider explicitly noting that Azure CLI commands work cross-platform (Windows, Linux, macOS) to reassure non-Windows users.
- Where PowerShell examples are given, clarify that Azure CLI is the recommended cross-platform approach.
- Add a brief note or table summarizing which commands are platform-agnostic and which are Windows-specific.
- Ensure that bash/CLI examples are always shown first, or at least equally prominent, to avoid perception of Windows-first bias.
Migrate
Support for VMware vSphere migration in Azure Migrate
...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux support details for VMware vSphere migration in Azure Migrate, but there is a mild Windows bias. Windows examples and requirements are often listed before Linux equivalents, and PowerShell is mentioned as the primary scripting interface for appliance deployment and VM replication configuration, with no Linux CLI or automation alternatives referenced. However, Linux support is clearly documented and most requirements are covered for both platforms.
Recommendations
- Provide Linux CLI (e.g., Bash, Azure CLI) examples or mention automation options for Linux users alongside PowerShell references.
- Alternate the order of Windows and Linux instructions/examples to avoid consistently listing Windows first.
- Where PowerShell is referenced for appliance deployment or replication configuration, clarify if Linux users can use Azure CLI, Bash scripts, or other supported methods.
- Explicitly state cross-platform support for scripting and automation where applicable.
Sentinel
This file is auto-generated . Do not edit manually. Changes will be overwritten.
...b/main/articles/sentinel/includes/connector-details.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation lists a large number of Microsoft Sentinel data connectors, many of which are cross-platform or cloud-focused. However, there are several connectors and sections that are Windows-centric (e.g., Windows Firewall, Windows DNS Events, Windows Security Events, IIS Logs, Exchange logs, etc.), and in these cases, Windows tools and patterns are referenced without always providing equivalent Linux/macOS guidance. Additionally, in some multi-platform scenarios (e.g., custom logs, agent installation), Windows instructions or terminology are sometimes presented first or more prominently.
Recommendations
- For connectors that support both Windows and Linux (e.g., Custom Logs via AMA), ensure that Linux/Unix instructions, examples, and terminology are presented alongside Windows, not as an afterthought.
- Where agent installation is referenced (e.g., Azure Monitor Agent), provide explicit Linux/macOS installation and configuration steps/examples, not just Windows/PowerShell.
- For event log connectors (e.g., SecurityEvent, WindowsEvent), clarify if there are Linux/macOS equivalents (e.g., Syslog) and cross-reference them.
- In sections about Windows-specific features, clearly state if there is no Linux/macOS equivalent, to avoid confusion.
- Review the ordering of examples and instructions to avoid always listing Windows first when cross-platform options exist.
Storage
Azure Elastic SAN configuration best practices
...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows examples and tools before Linux equivalents, especially in sections on enabling Accelerated Networking and configuring MPIO/iSCSI. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are mentioned by name and with screenshots, while Linux instructions are present but sometimes less detailed or shown after Windows. The overall structure and flow tend to favor Windows, though Linux guidance is included for all major configuration steps.
Recommendations
- Alternate the order of Windows and Linux examples so that Linux is shown first in some sections.
- Provide equivalent CLI examples for Linux where PowerShell is used for Windows, and link to Linux-specific documentation as prominently as Windows links.
- Include screenshots for Linux configuration steps where possible, matching the detail given to Windows.
- Explicitly state parity between Windows and Linux support at the start of each section to reassure non-Windows users.
- Ensure that all configuration steps (such as enabling Accelerated Networking) have clear Linux instructions and links.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux-specific instructions for disconnecting volumes, with scripts tailored for each platform. However, Windows/PowerShell examples and instructions are consistently presented before their Linux/Azure CLI counterparts throughout the page. PowerShell is emphasized as the first option for resource deletion, which may subtly signal a Windows-first approach.
Recommendations
- Alternate the order of examples so that Linux/Azure CLI instructions are sometimes presented first, or present both platforms side-by-side.
- Explicitly state that both PowerShell and Azure CLI are fully supported and equivalent for these operations.
- Consider adding macOS-specific notes if relevant, or clarify that CLI instructions apply to both Linux and macOS.
- Ensure parity in detail and clarity between Windows and Linux instructions/scripts.
Low Priority
View Details →
Detected Bias Types
powershell_heavy
Summary
The documentation is generally cross-platform and avoids Windows-specific bias in its examples and workarounds. However, there is one instance where PowerShell is used to demonstrate how to check Microsoft Entra token length, without providing an equivalent example for Linux/macOS users (e.g., using Azure CLI or REST API). No other Windows-only tools, patterns, or examples are present, and the page covers Azure Synapse Analytics, which is not inherently Windows-specific.
Recommendations
- Where PowerShell is used (e.g., to check token length), provide equivalent Azure CLI or REST API examples for Linux/macOS users.
- Explicitly state that the PowerShell example is one option, and link to cross-platform alternatives.
- Review future troubleshooting steps to ensure command-line examples are provided for both Windows and Linux/macOS environments.