277
Pages Scanned
113
Pages Flagged
277
Changed Pages
40.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-01 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 277
Files Completed: 277
Problematic Pages
113 issues found
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows are described in the context of Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST APIs, or cross-platform tools to perform upgrades.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using Azure CLI, REST API, or other cross-platform tools.
- Include guidance for Linux/macOS users on how to configure upgrade parameters and health policies outside of Visual Studio.
- Mention alternative editors or deployment methods for users not on Windows.
- Clarify which steps are Windows-only and provide parity where possible.
Create Pull Request
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples reference Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). The ApplicationManifest and ServiceManifest examples exclusively use Windows-specific constructs. There is no mention of Linux container support, nor are Linux examples or equivalents provided. The page assumes familiarity with Windows container applications and does not address Linux container scenarios.
Recommendations
- Add examples using Linux container images (e.g., mcr.microsoft.com/linux/base) and Linux commands (bash, echo, cat, etc.).
- Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if not, explicitly state this limitation.
- If Linux containers are supported, provide parallel Linux-focused ServiceManifest and ApplicationManifest examples.
- Mention Linux path conventions and volume mounting patterns alongside Windows examples.
- Update the 'Complete example' section to include both Windows and Linux container scenarios, or clearly indicate if only Windows containers are supported.
Service Fabric
Azure Service Fabric reverse proxy
...articles/service-fabric/service-fabric-reverseproxy.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are Windows-centric. There are no Linux equivalents or workarounds provided, and the feature is fundamentally unavailable on Linux, creating a platform disparity.
Recommendations
- Clearly state at the beginning that the reverse proxy is a Windows-only feature to set user expectations.
- Provide links or references to alternative approaches for Linux clusters, such as custom service discovery or proxy solutions.
- If possible, document any roadmap or plans for Linux support, or clarify why the feature is unavailable on Linux.
- Add a prominent note in the 'Next steps' section to warn Linux users that these guides are not applicable to Linux clusters.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI usage. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
- Add code examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
- Include instructions for querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
- Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in examples and guidance.
- Present Windows and Linux examples side-by-side or indicate platform-specific differences explicitly.
- Mention any limitations or considerations for Linux container scenarios, if applicable.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides several manual scaling instructions and examples using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or cross-platform CLI alternatives. PowerShell is referenced as the primary tool for manual operations, and Windows-specific tooling is presented first or exclusively in step-by-step guides. However, the page does acknowledge Linux clusters and links to Linux-specific cluster creation documentation, indicating some awareness of cross-platform needs.
Recommendations
- Add Azure CLI or Service Fabric CLI (sfctl) examples for scaling operations, especially for disabling/removing nodes, to support Linux/macOS users.
- Clarify whether PowerShell cmdlets are available cross-platform (via PowerShell Core), or provide alternatives where they are not.
- Where PowerShell is used, mention if/how Linux users can perform equivalent actions, and link to relevant Linux tooling documentation.
- Ensure step-by-step guides include both Windows and Linux approaches, or explicitly state if a step is Windows-only.
Service Fabric
Application upgrade: data serialization
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page references Windows-centric tools (Visual Studio and PowerShell) for application upgrades in the 'Next steps' section, with no mention of Linux/macOS alternatives or CLI options. Examples and recommendations are focused on C# and .NET serialization, which are cross-platform, but the upgrade guidance is Windows-oriented.
Recommendations
- Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
- Mention Linux/macOS-compatible development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Clarify whether PowerShell instructions are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI equivalents.
- Explicitly state if certain upgrade steps are Windows-only, and provide Linux/macOS alternatives where possible.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All command-line examples use PowerShell, which is Windows-centric, and there are no equivalent examples for Linux/macOS environments (e.g., Bash, Azure CLI, or REST API). The documentation implicitly assumes Windows as the primary platform for operational tasks, potentially creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI or REST API examples for configuring placement policies, as these are cross-platform and usable from Linux/macOS.
- Explicitly mention whether PowerShell examples are supported on Linux (via PowerShell Core), or provide Bash equivalents if possible.
- Clarify any platform-specific limitations or requirements for Service Fabric management tools.
- Consider including a section on managing Service Fabric clusters from Linux/macOS, referencing relevant tools and documentation.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides examples and references to Azure PowerShell modules for managing Service Fabric managed clusters, with PowerShell mentioned first and in detail. While Azure CLI and ARM/Bicep are also referenced, PowerShell is emphasized, and there are no explicit Linux/macOS shell examples or callouts. The use of PowerShell-centric guidance may create friction for Linux/macOS users, though Azure CLI and ARM tools are cross-platform.
Recommendations
- Add explicit Azure CLI command examples for key operations (e.g., deleting NodeType, restarting/reimaging scale sets) alongside PowerShell examples.
- Clarify that Azure CLI and ARM/Bicep tools are fully cross-platform and suitable for Linux/macOS users.
- Consider providing bash/zsh shell snippets or guidance for Linux/macOS users where appropriate.
- Ensure that references to PowerShell are balanced with equivalent CLI guidance, especially in 'Best practices' sections.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for querying partition health, with no equivalent Linux/macOS CLI example (such as using sfctl or REST API). The PowerShell example is presented as the sole method, and Windows paths are referenced, suggesting a Windows-first approach. No Linux-specific tools or cross-platform guidance is given for the health report example.
Recommendations
- Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API for querying partition health.
- Mention that PowerShell is Windows-specific and provide guidance for non-Windows users.
- Include cross-platform instructions and clarify tool availability for Linux/macOS administrators.
- Where possible, show both Windows and Linux commands side-by-side.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits moderate Windows bias. Windows terminology and examples are presented first and most prominently, including the use of 'custom windows images' and a PowerShell command for role assignment. Linux equivalents are referenced but not demonstrated, and the ARM template examples are generic but lack explicit Linux-focused guidance.
Recommendations
- Clarify that custom images can be Linux-based as well, and provide explicit examples for Linux custom images.
- Include Linux CLI (az) commands for role assignment alongside the PowerShell example.
- Ensure that ARM template examples show both Windows and Linux image scenarios, or note any differences.
- Reorder sections to treat Windows and Linux equally, or explicitly state if Windows is required for certain steps.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides numerous PowerShell-based examples and references, with no equivalent CLI or Linux/macOS instructions. Windows tools and patterns (PowerShell cmdlets) are used exclusively for key upgrade operations, and PowerShell is referenced first and often. There are no examples using Service Fabric CLI (sfctl), Bash, or cross-platform tools, which creates friction for Linux/macOS users.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
- Where PowerShell cmdlets are referenced, also mention the corresponding sfctl command or REST API, if available.
- Clarify which operations are possible via CLI or REST API for non-Windows environments.
- Include Bash or shell script examples where appropriate.
- Update 'Next steps' to include links to Linux/macOS upgrade tutorials or CLI-based guides.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows tools and patterns (PowerShell, Windows Defender, DSC) are mentioned exclusively or before Linux equivalents. Linux examples are present for certificate generation and secret encryption, but some sections (e.g., Windows Defender, security baselines) are Windows-only without Linux alternatives or parity suggestions.
Recommendations
- Ensure Linux examples are presented alongside Windows examples, not after or as an afterthought.
- Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are discussed, provide Linux equivalents or clarify their absence.
- For security baseline recommendations, reference industry-standard Linux baselines (e.g., CIS benchmarks) and configuration management tools (e.g., Ansible, Chef, Puppet) for Linux clusters.
- Explicitly note when a feature or tool is Windows-only and suggest Linux alternatives or best practices.
- Consider balancing the order of examples so Linux and Windows are equally represented in critical sections.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The manifest examples are based on a Windows Server 2016 container sample, and Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths) are referenced. Windows tools (e.g., 'winver' command) are mentioned exclusively for OS build identification, and Windows paths (e.g., 'c:\VolumeTest\Data') are used in volume binding examples. Linux equivalents (such as 'uname' for OS build or Linux file paths) are not provided. Certificate handling is explained for both Windows (PFX) and Linux (PEM), but Linux-specific manifest examples or guidance are missing.
Recommendations
- Provide Linux-based manifest examples or reference a Linux container sample repository.
- Mention Linux tools (e.g., 'uname -r') for OS build/version detection alongside 'winver'.
- Show Linux file path conventions (e.g., '/mnt/volume/data') in volume binding examples.
- Clarify which manifest settings are cross-platform and which are Windows-specific.
- Add explicit guidance or links for Linux Service Fabric container deployments.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The use of PowerShell cmdlets is presented as the primary method, and no cross-platform alternatives (such as Azure CLI, REST, or SDK code samples) are shown. This creates friction for Linux/macOS users, who may not have access to PowerShell or the cmdlets referenced.
Recommendations
- Add equivalent examples using REST API calls for health reporting and querying, which are cross-platform.
- Include Azure CLI or .NET SDK code samples for health report submission and evaluation.
- Explicitly mention Linux/macOS-compatible methods alongside PowerShell, and clarify platform support for each example.
- Consider showing REST or cross-platform examples first, or in parallel with PowerShell examples.
Service Fabric
Azure Service Fabric hosting model
...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for service creation and management, with no equivalent Linux CLI (e.g., Azure CLI, Bash) examples. PowerShell is mentioned first and most prominently, which may create friction for Linux/macOS users, although REST API and .NET examples are also provided.
Recommendations
- Add Azure CLI or Bash examples for service creation and management tasks, especially for commands like creating services with Exclusive Process model.
- Mention cross-platform tools (such as Azure CLI) alongside PowerShell, and clarify their applicability.
- Provide guidance or links for Linux/macOS users on how to perform equivalent operations.
- Ensure REST API examples are highlighted as cross-platform options.
Service Fabric
Networking patterns for Azure Service Fabric
...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page consistently uses PowerShell for deployment examples and command-line instructions, with no mention of Azure CLI or Bash equivalents. Windows tools and patterns (such as RDP and Windows directory paths) are referenced, and Windows-style command prompts are shown. Linux/macOS users are not provided with alternative instructions or examples, creating friction for those not using Windows.
Recommendations
- Provide Azure CLI and Bash equivalents for all PowerShell deployment commands.
- Include examples using Linux/macOS directory paths and shell prompts.
- Mention SSH as a remote access method alongside RDP, and provide instructions for Linux/macOS users.
- Clearly indicate when PowerShell is required, and offer guidance for cross-platform users.
- Add notes or sections specifically addressing Linux/macOS workflows for Service Fabric networking setup.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 managed disks, but all VM creation examples use Windows images (e.g., 'Win2016Datacenter') and Windows-centric parameters. There are no Linux VM image examples or explicit guidance for Linux users, even though Premium SSD v2 is suitable for Linux workloads. This creates friction for Linux users who must adapt the examples themselves.
Recommendations
- Add Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in Azure CLI and PowerShell sections.
- Explicitly mention that the disk deployment steps are OS-agnostic, and provide guidance on selecting Linux images.
- In variable initialization, show both Windows and Linux image values, or provide a table of common image references.
- Ensure that authentication examples include SSH for Linux VMs, not just password authentication.
- Clarify any OS-specific considerations for disk attachment or performance tuning.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are several instances where Windows terminology, tools, or documentation are mentioned first or exclusively, and some links and examples are Windows-centric. For example, partitioning and disk size limitations are explained with references to Windows MBR/GPT documentation, and the process for creating images links only to a Windows-specific guide. In the upload VHD section, both Azure CLI (Linux) and PowerShell (Windows) are linked, but the image creation section only references Windows. Some disk management concepts (like drive letters) are described in Windows terms before or instead of Linux equivalents.
Recommendations
- When discussing disk partitioning and size limits, include Linux-specific guidance and documentation (e.g., referencing Linux partitioning tools and GPT/MBR handling).
- For the 'Images' section, provide or link to Linux-specific instructions for creating managed images from generalized Linux VMs.
- When describing disk roles and mounting, ensure Linux device paths and conventions (e.g., /dev/sdX, mount points) are mentioned alongside or before Windows drive letters.
- In all sections where both Azure CLI and PowerShell are relevant, ensure both are always referenced and that Linux-first examples are included where appropriate.
- Review all links to ensure parity between Linux and Windows documentation, especially for critical VM lifecycle tasks.
Service Fabric
X.509 Certificate-based Authentication in a Service Fabric Cluster
...ticles/service-fabric/cluster-security-certificates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides comprehensive coverage of X.509 certificate-based authentication in Service Fabric clusters, but exhibits moderate Windows bias. Windows-specific concepts (certificate stores, Win32 CryptoAPI, event logs, error codes, and troubleshooting tools) are mentioned first or exclusively, with Linux equivalents only briefly referenced. Troubleshooting and configuration examples focus on Windows paths and tools, and some advanced troubleshooting steps (like CAPI2 logging) are Windows-only. Linux-specific guidance is minimal and often relegated to parenthetical notes.
Recommendations
- Expand Linux-specific instructions, paths, and troubleshooting steps (e.g., detail how to access logs and certificate stores on Linux nodes).
- Provide Linux/macOS equivalents for Windows-centric error codes, tools, and troubleshooting workflows.
- Include explicit Linux examples for certificate configuration and management, not just brief mentions.
- Clarify any differences in certificate handling between Windows and Linux nodes, especially for advanced scenarios.
- Add links or references to Linux documentation for Service Fabric certificate management and troubleshooting.
Service Fabric
Manage certificates in a Service Fabric cluster
...vice-fabric/cluster-security-certificate-management.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides a mix of conceptual guidance and hands-on examples for managing certificates in Azure Service Fabric clusters. While much of the content is platform-agnostic and focuses on Azure-native mechanisms (Key Vault, VM extensions, ARM templates), there is a notable bias toward Windows in several areas: PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is described exclusively in its Windows variant. Additionally, certain explanations (such as certificate linking and S-channel) are explicitly Windows-specific, and Windows terminology/tools are referenced before any Linux alternatives (if any exist). There are no Linux/bash examples for certificate enrollment or provisioning, and the documentation does not mention the Key Vault VM extension for Linux, which exists and is relevant for cross-platform clusters.
Recommendations
- Add bash/CLI examples for certificate enrollment and provisioning alongside PowerShell examples.
- Mention and link to the Key Vault VM extension for Linux (https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/key-vault-linux) when discussing provisioning agents.
- Clarify which mechanisms and examples are Windows-specific and provide Linux/macOS equivalents where possible.
- When discussing certificate linking and S-channel, explicitly state that these are Windows-only features and describe Linux alternatives (such as OpenSSL or other certificate handling mechanisms).
- Ensure that ARM template snippets and deployment steps are platform-neutral or indicate any OS-specific requirements.
Service Fabric
Configure or modify a Service Fabric managed cluster node type
...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting, which are more common on Linux/macOS. The PowerShell examples are presented alongside Portal and ARM template methods, but there is no Linux-specific guidance or parity for command-line operations. The documentation does not reference Windows-only features, so the bias is not intentional.
Recommendations
- Add Azure CLI examples for all operations (add, remove, scale, configure placement properties, etc.) to ensure Linux/macOS users have equivalent command-line guidance.
- Mention Bash scripting or provide links to Azure CLI documentation for Service Fabric managed clusters.
- Clarify that PowerShell examples are cross-platform (if applicable), or explicitly state any limitations for Linux/macOS users.
- Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
Service Fabric
Introduction to the Service Fabric Infrastructure Service
.../articles/service-fabric/infrastructure-service-faq.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux alternatives. While Service Fabric clusters can be managed from Linux, the examples and tooling focus on Windows/PowerShell, creating friction for Linux/macOS users.
Recommendations
- Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
- Mention cross-platform management tools or clarify if Service Fabric Explorer is available on Linux/macOS.
- Provide guidance for Linux users on how to perform the same operations (e.g., bypassing Infrastructure Service) without PowerShell.
- Explicitly state if certain commands or tools are Windows-only, and offer alternatives or workarounds.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some tutorials/examples focus on .NET/Windows scenarios. Linux-specific guidance is present but often secondary, and some configuration details for Linux are only linked, not explained inline.
Recommendations
- Ensure Linux monitoring tools and workflows are described with equal prominence and detail as Windows equivalents.
- Provide Linux-specific examples and tutorials directly in the documentation, not just as external links.
- When referencing tools (e.g., EventStore, Diagnostics Agent), clarify their availability and alternatives for Linux clusters.
- Add sample code and configuration snippets for Linux (e.g., using Syslog, LTTng, Application Insights for Linux workloads).
- Where Windows tools are mentioned (e.g., Event Viewer), immediately follow with Linux alternatives (e.g., Syslog, LTTng) and how to access equivalent data.
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation contains evidence of Windows bias, notably in the warning suggesting the use of Visual Studio and referencing a Windows file path for schema validation. Additionally, the mention of using the ServiceFabric PowerShell module to create service instances implies Windows-centric tooling. Windows examples and tools are presented first and exclusively, with no Linux/macOS alternatives or parity guidance.
Recommendations
- Provide instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other XML editors) and reference Linux/macOS file paths if applicable.
- Mention and provide examples for using Service Fabric CLI (sfctl) or REST APIs for service management, which are cross-platform, alongside PowerShell.
- Ensure that tooling recommendations (such as Visual Studio) are accompanied by alternatives for Linux/macOS users (e.g., VS Code, JetBrains Rider, or command-line tools).
- Explicitly state if certain features or tools are Windows-only, and offer Linux/macOS equivalents or workarounds where possible.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell) for operations, and references PowerShell before or instead of Azure CLI equivalents. While az resource (Azure CLI) is mentioned once, PowerShell is the dominant example format. There are no Linux-specific examples or explicit parity guidance.
Recommendations
- Provide Azure CLI equivalents for all PowerShell cmdlets, especially for operations like unprovisioning application type versions, creating applications, and services.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, show both PowerShell and Azure CLI examples side-by-side.
- Clarify if any operations are PowerShell-only, and offer alternatives or workarounds for Linux/macOS users.
Service Fabric
Migrate an Azure Service Fabric cluster to availability zone support
...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page provides migration guidance for Azure Service Fabric clusters to availability zone support. While much of the content is platform-neutral (focused on ARM templates and Azure resources), the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies exclusively on PowerShell commands and Windows-centric tooling (e.g., Service Fabric PowerShell cmdlets). Additionally, Windows-based examples (such as sample templates and file paths) are referenced before Linux equivalents, and Linux-specific guidance is minimal or absent.
Recommendations
- Provide equivalent Bash/CLI examples for all PowerShell steps, especially for disabling/removing nodes and updating resources.
- Reference and link to Linux/Ubuntu sample templates alongside Windows templates in migration sections.
- Clarify which steps are platform-agnostic and which require Windows, and offer Linux alternatives where possible.
- Explicitly mention if certain operations (e.g., Service Fabric node management) can be performed via Azure CLI or REST API, and provide those examples.
- Ensure file paths and certificate handling are explained for both Windows and Linux environments.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (like AD domain accounts, gMSA, BitLocker) are mentioned with more detail or exclusively, while Linux equivalents are missing or relegated to TODO comments. Examples and guidance often reference Windows tools or patterns first, and Linux-specific instructions are sparse or absent.
Recommendations
- Add explicit Linux examples for securing disks at rest (e.g., using Azure Disk Encryption with Linux clusters).
- Provide parity in guidance for running services under different user accounts on Linux clusters, including how to configure principals and policies.
- Include Linux-specific instructions for certificate management and container security, matching the detail given for Windows (e.g., gMSA alternatives).
- Ensure that API gateway and service communication examples include Linux-friendly tools and patterns, not just ASP.NET Core or Windows-centric approaches.
- Remove or resolve TODO comments regarding Linux disk encryption and provide actionable guidance.
Service Fabric
Azure Service Fabric dynamic node tags
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for managing node tags and configuring services, but does not offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its usage is presented before C# API examples. There is no mention of Linux-native tools or Azure CLI commands, which creates friction for Linux/macOS users.
Recommendations
- Add Azure CLI or REST API examples for managing node tags and configuring services, as these are cross-platform.
- Explicitly mention whether PowerShell Core (cross-platform) is supported, or clarify if only Windows PowerShell is required.
- Provide bash or shell script examples where possible, or reference relevant Linux tooling.
- Reorder examples so that cross-platform methods (e.g., REST API, Azure CLI) are shown before or alongside PowerShell.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides PowerShell examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. While the main deployment workflow is based on Azure Resource Manager templates (cross-platform), the only explicit command-line example is in PowerShell, and PowerShell is mentioned before CLI alternatives. Linux/macOS users may need to adapt these steps or use REST API/CLI equivalents, which are not shown.
Recommendations
- Add Azure CLI examples alongside PowerShell for resource management tasks, such as removing applications.
- Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) equally and provide links or examples for Linux/macOS users.
- Clarify that PowerShell commands can be substituted with Azure CLI or REST API calls, and provide sample commands for those environments.
- Ensure that references to PowerShell are not presented as the only or primary option unless the task is Windows-specific.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation frequently references PowerShell cmdlets and Windows-centric tools (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET API methods and REST operations. PowerShell examples are given in detail, and Windows tools are often mentioned first or exclusively. There is minimal mention of cross-platform CLI tools (such as sfctl or Azure CLI), and Linux/macOS equivalents are not provided or are only referenced via a generic include link. This creates friction for Linux/macOS users, who may not use PowerShell or Windows tools.
Recommendations
- Add explicit examples using sfctl and Azure CLI for each lifecycle operation, alongside PowerShell and .NET API examples.
- Ensure that cross-platform tools are mentioned before or equally with Windows tools in each section.
- Clarify which tools are available on Linux/macOS and provide links to their documentation.
- Where PowerShell is used, note any cross-platform alternatives and how to achieve the same outcome on Linux/macOS.
- Expand the [links to azure cli and service fabric cli] include to show concrete usage examples in the main text.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Service Fabric application upgrades demonstrates notable Windows bias. All code examples are provided exclusively in PowerShell, a Windows-centric tool, with no equivalent CLI or Linux/macOS examples. References to Windows-specific APIs (e.g., http.sys) and error messages reinforce the Windows focus. Additionally, upgrade instructions and links prioritize Windows tools (PowerShell, Visual Studio) without mentioning cross-platform alternatives such as Azure CLI or REST API. This creates friction for Linux/macOS users, who may not be able to follow the documented procedures directly.
Recommendations
- Add equivalent examples using Azure CLI or REST API for application upgrades, especially for retrieving and passing application parameters.
- Include guidance for Linux/macOS users, such as how to perform upgrades from non-Windows environments.
- Mention cross-platform tools and workflows (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell and Visual Studio.
- Clarify which features or steps are Windows-only, and provide alternatives or workarounds for Linux/macOS users where possible.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require installation of Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. The prerequisite to install a PowerShell module and connect to the cluster via PowerShell further reinforces the Windows-centric approach.
Recommendations
- Add equivalent Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger restores and track progress.
- Mention Azure CLI or cross-platform tools if available for Service Fabric backup/restore operations.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or if there are alternatives for Linux/macOS.
- Include a note about PowerShell Core compatibility on Linux/macOS, if relevant, or explicitly state if only Windows PowerShell is supported.
- Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and authenticating REST API calls.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or cross-platform approaches. Windows tools and patterns are mentioned first and exclusively, creating friction for Linux cluster administrators.
Recommendations
- Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
- Provide Linux-specific or cross-platform examples for accessing and analyzing events.
- Clarify which features or instructions are Windows-only and offer Linux alternatives where possible.
- Mention any limitations or differences in event access between Windows and Linux clusters.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples first, with detailed tables and explanations, while Linux-centric tools (SFCTL CLI) are covered later and less prominently. The PowerShell and Visual Studio sections are more extensive and appear before SFCTL, potentially creating friction for Linux/macOS users. However, SFCTL parameters are documented, and Linux upgrade workflows are referenced in the 'Next steps' section.
Recommendations
- Reorganize the page so that cross-platform tools (SFCTL, REST API) are presented alongside or before Windows-specific tools (PowerShell, Visual Studio).
- Add explicit Linux/macOS usage examples for SFCTL in the main parameter tables, not just in the 'Next steps'.
- Clarify which tools are cross-platform and which are Windows-only at the start of the article.
- Ensure that parameter tables for SFCTL are as detailed and prominent as those for PowerShell/Visual Studio.
- Consider adding a summary table comparing upgrade methods (PowerShell, Visual Studio, SFCTL, REST) and their platform support.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation references PowerShell cmdlets as a primary management interface for Service Fabric, and mentions Windows security as a transport option before X509 certificates. No Linux-specific management tools or examples are provided, and PowerShell is presented as the default for provisioning and lifecycle operations, which may create friction for Linux/macOS users.
Recommendations
- Include references to cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
- Clarify whether PowerShell cmdlets are available and supported on Linux/macOS, or provide alternative instructions for those platforms.
- Mention Linux security mechanisms (e.g., certificate-based authentication) equally when discussing transport subsystem security.
- Add examples or links for Linux/macOS users to manage Service Fabric clusters, if available.
Service Fabric
On-demand backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or Azure CLI). The prerequisite section mandates installation of a PowerShell module, and the workflow assumes PowerShell as the primary tool, creating friction for non-Windows users.
Recommendations
- Add equivalent Bash/curl examples for REST API calls, so Linux/macOS users can trigger backups and track progress without PowerShell.
- Mention Azure CLI commands if available for backup/restore operations.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for PowerShell users, and provide alternative instructions for Linux/macOS environments.
- Reorganize examples so that REST API usage is shown independently of PowerShell, and provide cross-platform guidance.
- Explicitly state platform requirements and limitations, if any, for Service Fabric backup/restore operations.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric backup configuration via REST APIs and JSON payloads. However, the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication', with no mention of Linux-compatible file share paths or authentication methods. There are no Linux-specific examples or guidance for configuring file share backups from Linux-based Service Fabric clusters.
Recommendations
- Add examples for file share backup storage using Linux-compatible paths (e.g., SMB/CIFS mounts, NFS, or local file system paths).
- Document authentication methods for file shares on Linux (e.g., username/password, mount options) and clarify any limitations or requirements.
- Explicitly state whether file share backup storage is supported on Linux clusters, and if so, provide parity examples and guidance.
- If file share backup is Windows-only, clarify this explicitly in the documentation to avoid confusion.
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides several examples and references that prioritize Windows and PowerShell usage, such as mentioning PowerShell APIs and classic PowerShell tasks in Azure DevOps, referencing Windows-specific ARM templates, and describing Windows container networking patterns. Linux equivalents are sometimes mentioned but often appear after Windows examples or lack detailed guidance. Some sections, like port usage and tooling, are Windows-centric, and Linux-specific instructions or examples are limited or missing.
Recommendations
- Add equivalent Linux CLI (az CLI, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
- Ensure Linux-specific ARM templates and sample links are provided, not just Windows-focused ones.
- Clarify which networking patterns, port ranges, and tooling apply to Linux clusters, and provide explicit Linux guidance where differences exist.
- Expand Linux container networking best practices and reference Linux container orchestration tools where relevant.
- Where Windows tools (e.g., netsh) are mentioned, provide Linux alternatives (e.g., ss, ip, netstat) for port range checks.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is the only scripting language shown for cluster upgrades. Windows-specific registry keys and VM configuration examples are included, while Linux equivalents or guidance are missing or not given equal prominence. Some upgrade and patching instructions focus on Windows (e.g., registry settings, disabling Windows Update) without Linux alternatives.
Recommendations
- Provide equivalent Linux/bash examples for all PowerShell scripts, especially for cluster upgrade operations.
- When discussing VM configuration (e.g., disabling automatic updates), include Linux-specific instructions or clarify when a step is Windows-only.
- If a section is Windows-specific, clearly label it as such, and provide a parallel Linux section where applicable.
- Ensure that Linux and Windows examples are presented with equal prominence, or alternate their order to avoid 'windows_first' bias.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or commands. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users, who typically use Bash or Azure CLI. There is no guidance or parity for Linux users, nor are cross-platform alternatives referenced.
Recommendations
- Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and supported on Linux/macOS.
- Mention and link to documentation for Service Fabric CLI (sfctl), which is the official cross-platform command-line tool for Service Fabric.
- Clarify which management operations can be performed using sfctl or Azure CLI, and provide equivalent examples.
- If PowerShell is required for certain operations, explicitly state this and explain any Linux/macOS workarounds or limitations.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml with <WindowsServer> infrastructure) and cross-platform (ClusterConfig.json) examples for cluster configuration. However, Windows terminology and XML examples are presented first and more prominently. PowerShell examples are given for service creation and updates, but there are no equivalent Linux CLI or Bash examples. The documentation does not mention Linux-specific tools or patterns, nor does it clarify how Linux users should perform these tasks, even though Service Fabric supports Linux clusters.
Recommendations
- Add explicit Linux cluster configuration examples (e.g., <Linux> infrastructure in ClusterManifest.xml) alongside Windows examples.
- Include Bash or Azure CLI examples for service creation and updates, not just PowerShell.
- Clarify any differences or limitations for Linux clusters, if applicable.
- Ensure that cross-platform JSON examples are presented equally and not secondary to Windows XML examples.
- Mention Linux node support and reference relevant documentation for Linux users.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', NTLM authentication, and references to Windows Defender Firewall) are used as defaults or examples, and Windows-specific settings are often mentioned before Linux equivalents. Some parameters and guidance reference Windows APIs or documentation (e.g., CertGetCertificateChain), and certain settings (like NTLM authentication) are inherently Windows-centric. Linux-specific settings are present but less prominent and sometimes only noted in parentheses.
Recommendations
- Where parameters have different defaults or behaviors on Linux, clarify these explicitly and provide Linux-first examples.
- For certificate store names and locations, add Linux equivalents and explain differences (e.g., file-based certificate storage vs. Windows store).
- When referencing Windows APIs or documentation, provide Linux alternatives or note if the feature is not applicable.
- Highlight Linux-specific settings (e.g., LinuxExternalExecutablePath) more prominently and ensure parity in guidance.
- For authentication and firewall settings, clarify Linux support and alternatives, avoiding Windows-centric language where possible.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page provides a conceptual overview of Service Fabric node types and their relationship to Azure VM scale sets. While the JSON snippet includes both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' types, the example configuration uses a Windows-style file path ('D:\\SvcFab') and certificate store parameters, which are Windows-centric. The 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks, without Linux/SSH equivalents or guidance. There is no explicit Linux/macOS example for connecting to nodes or managing credentials, and Windows tools and patterns are referenced first or exclusively.
Recommendations
- Provide equivalent Linux/macOS examples for connecting to scale set instances (e.g., SSH instead of RDP).
- Include sample configuration snippets that use Linux-style paths (e.g., '/var/svcfab') and certificate locations.
- Add links or guidance for managing Linux admin credentials and SSH port ranges.
- Clarify which steps or scripts are Windows-only and provide Linux alternatives where possible.
Service Fabric
Azure Service Fabric Auto Scaling Services and Containers
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI/script examples are PowerShell-based, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents, and PowerShell examples are presented alongside C# and manifest examples without alternatives for Linux users. Additionally, PowerShell is shown before any mention of Linux tooling, and there is no guidance for Linux users on how to perform equivalent operations.
Recommendations
- Add bash/CLI examples for Linux users, such as using Azure CLI or REST API to configure scaling policies.
- Explicitly mention cross-platform options where available, and clarify which steps are Windows-only.
- If PowerShell is required, note that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
- Include a section or note describing how Linux users can manage Service Fabric scaling policies (e.g., via Azure CLI, REST API, or Service Fabric CLI).
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell, but does not include equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash, or REST API). PowerShell commands are shown prominently, and there is no mention of Linux-native tools or cross-platform alternatives for managing Service Fabric metrics. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention REST API options for managing Service Fabric metrics, with example requests.
- Clarify whether PowerShell examples are Windows-only, and provide guidance for Linux/macOS users (e.g., using Azure CLI or Service Fabric CLI).
- Where possible, include Bash script examples or references to Service Fabric CLI (sfctl), which is cross-platform.
- Ensure that documentation sections do not assume PowerShell as the default scripting environment.
Service Fabric
Service Fabric Cluster Resource Manager: Movement cost
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not offer equivalent Linux/Unix shell (e.g., Bash/CLI) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# examples, reinforcing a Windows-first pattern. No mention is made of Azure CLI or REST API alternatives, which are cross-platform.
Recommendations
- Add Azure CLI examples for service creation and updating move cost, as Azure CLI is cross-platform and widely used on Linux/macOS.
- If REST APIs exist for these operations, provide example requests and responses.
- Explicitly note if PowerShell is required due to feature limitations, and link to any Linux-compatible tools or workarounds.
- Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to avoid Windows-first ordering.
Service Fabric
Service sensitivity
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# APIs. However, PowerShell is featured prominently for service creation and updates, with no equivalent CLI or Bash examples for Linux/macOS users. The PowerShell examples are shown before C# API examples, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
- Add Azure CLI or REST API examples for service sensitivity and maximum load configuration, if supported.
- Explicitly mention whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or provide Bash equivalents.
- Clarify if these operations can be performed via SDKs in other languages (Python, Java) and provide sample code.
- Consider reordering examples so that cross-platform methods (XML/JSON, CLI, REST) are shown before Windows-specific tools like PowerShell.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently presents Windows-specific guidance and links before Linux equivalents, and in several sections, Linux standalone clusters are not mentioned at all. While Azure-hosted clusters are implied to be cross-platform, standalone cluster security instructions are exclusively for Windows Server, with no Linux standalone guidance or links. Certificate creation recommendations focus on Windows tools and services, and there are no explicit Linux example workflows or references.
Recommendations
- Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate and authentication setup.
- Provide Linux-specific examples for certificate creation, installation, and cluster configuration (e.g., using OpenSSL, Linux file paths, and relevant tools).
- Clarify which security scenarios apply equally to Linux and Windows, and highlight any platform-specific differences.
- Ensure parity in recommendations and next steps for Linux users, including links to Linux-focused documentation where available.
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily references Windows-specific upgrade instructions and tools, such as linking to Windows Server-specific guides and the Patch Orchestration Application for Windows. There are no explicit Linux examples or references to Linux cluster upgrade procedures, even though Service Fabric standalone clusters can be deployed on both Windows and Linux. This creates friction for Linux users seeking upgrade guidance.
Recommendations
- Add links and examples for upgrading Service Fabric standalone clusters on Linux, including Linux-specific configuration and upgrade steps.
- Mention Linux equivalents for patch orchestration and cluster configuration where applicable.
- Ensure that references to upgrade guides and configuration settings are platform-neutral or provide separate sections for Windows and Linux.
- Clarify in the introduction that the guidance applies to both Windows and Linux clusters, or specify if certain sections are Windows-only.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without providing equivalent Azure CLI or Bash examples. The packaging step references Visual Studio, a Windows-centric tool, and screenshots are from Windows environments. There is no mention of Linux/macOS workflows or tools, nor are cross-platform alternatives presented.
Recommendations
- Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
- Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
- Provide sample commands and screenshots from Linux/macOS environments where applicable.
- Clarify that PowerShell is not required and highlight cross-platform options for users on non-Windows systems.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. No Linux-specific examples, tools, or guidance are provided, despite Service Fabric standalone clusters being theoretically cross-platform. This may create friction for Linux users attempting to scale clusters.
Recommendations
- Add equivalent Linux instructions, including examples using Bash, CLI, or relevant Linux-native tools.
- Clarify whether Service Fabric standalone clusters can be managed on Linux, and if so, provide guidance for Linux environments.
- If PowerShell is required on Linux, explicitly state this and provide installation instructions.
- Link to or create documentation for scaling standalone clusters on Linux, if supported.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (e.g., Bash, Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux cluster node upgrade information. Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
- Add explicit Linux guidance and examples where PowerShell is mentioned, such as Bash or Azure CLI commands for Linux.
- Include links or sections for patching/upgrading Linux cluster node OS images, not just Windows.
- When referencing Azure CLI, clarify its cross-platform nature and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Ensure that portal and scripting instructions are equally applicable to Linux clusters, or note any differences.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell and C#, both of which are strongly associated with Windows environments. There are no equivalent Linux CLI or bash examples, and PowerShell commands are referenced as the main administrative method. The section on platform differences does mention Linux, but only in the context of logging implementation, not in operational examples. This creates friction for Linux users who may not have access to PowerShell or prefer bash/CLI tools.
Recommendations
- Add equivalent Linux CLI/bash examples for administrative actions, such as scaling services and creating/removing instances.
- Reference Service Fabric REST APIs or cross-platform tools where possible, rather than only PowerShell.
- Clarify which PowerShell commands are available on Linux (if any), or provide guidance for Linux users.
- Ensure Linux operational patterns are mentioned alongside Windows/PowerShell patterns, not only in the platform differences section.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which is a cross-platform technology supporting both Windows and Linux. However, there are multiple instances where Windows concepts, tools, and examples are mentioned first or exclusively, such as references to Windows services (FabricHost.exe), PowerShell cmdlets, and standalone cluster creation only for Windows. Linux equivalents are sometimes mentioned later or omitted, and some tooling (e.g., PowerShell) is highlighted without clear Linux alternatives.
Recommendations
- Ensure Linux-specific examples and tools (such as Bash, Linux CLI, or sfctl) are presented alongside or before Windows/PowerShell examples.
- Clarify when features or instructions are Windows-only, and provide Linux alternatives or links where available.
- Expand documentation on Linux cluster creation and management, or clearly state limitations and roadmap for Linux support.
- Where possible, use cross-platform terminology and avoid defaulting to Windows-specific concepts (e.g., 'auto-start Windows service') unless necessary.
- Highlight Linux support for Service Fabric in relevant sections, including programming models, cluster management, and health monitoring.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are noted without offering Linux-centric workflows or examples. There is no guidance for Linux users on how to set DNS names or manage Service Fabric clusters using Linux-native tools.
Recommendations
- Add examples for setting DNS names using Linux-native tools, such as Azure CLI or Bash scripts.
- Include instructions for editing ARM templates and deploying services from Linux environments.
- Provide guidance for managing Service Fabric clusters and services on Linux, including containerized workflows.
- Mention Linux-friendly editors and approaches (e.g., VS Code, nano, vim) for editing ApplicationManifest.xml.
- Clarify any differences in workflows between Windows and Linux, and ensure Linux users have a clear path to accomplish all documented tasks.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell commands are presented first and in greater detail, which may signal a Windows-first bias. The CLI examples are included and are cross-platform, but the prominence and depth of PowerShell coverage may create friction for Linux/macOS users.
Recommendations
- Present CLI (sfctl) examples before PowerShell, or at least give them equal prominence.
- Explicitly note that sfctl is cross-platform and preferred for Linux/macOS users.
- Add clarifying statements about platform compatibility for each tool.
- Ensure that all critical operations (deploy, status, upgrade, rollback, etc.) are covered equally for both PowerShell and CLI.
- Consider adding a table or section comparing PowerShell and CLI usage, highlighting cross-platform options.
Service Fabric
Azure Service Fabric hosting activation and deactivation life cycle
...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle shows a moderate Windows/PowerShell bias. While the core concepts are platform-agnostic, the only explicit tooling reference for deployment/removal is PowerShell, and the 'Next steps' section links only to PowerShell-based workflows. There are no Linux/bash equivalents or cross-platform CLI examples provided, and the only advanced example for downloading ServicePackages in advance links to a PowerShell cmdlet. This may cause friction for Linux/macOS users.
Recommendations
- Add Azure CLI or Bash examples for deploying and removing applications, alongside or in place of PowerShell examples.
- Where possible, link to cross-platform documentation or explicitly note Linux/macOS workflows.
- If certain operations are only possible in PowerShell, clearly state this and provide Linux alternatives or workarounds if available.
- Include references to Linux tools or scripts for managing Service Fabric clusters, especially for common tasks like package deployment.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides Service Fabric manifest examples and references Windows-specific concepts and tools, such as running scripts via Setup.bat, using EXE files, and referencing Windows user accounts (Administrators, NetworkService). Windows terminology and patterns (e.g., .bat files, EXE hosts, PowerShell module mention) are used throughout, with no explicit Linux equivalents or guidance. However, the content is not exclusively Windows-only, and Service Fabric supports Linux clusters, so Linux users may experience friction but can adapt the examples.
Recommendations
- Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group concepts.
- Clarify which manifest settings and patterns are cross-platform and which are Windows-only.
- Mention Linux deployment tools (e.g., Azure CLI, Bash) alongside PowerShell, and provide links to Linux Service Fabric documentation.
- Where EXE or .bat files are referenced, note that Linux services should use ELF binaries and shell scripts.
- Explicitly state any platform-specific limitations or requirements for Service Fabric manifest elements.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed examples for health reporting in Service Fabric using PowerShell, with explicit Windows paths and commands. PowerShell is presented as a primary CLI method, but there are no equivalent Linux/bash examples or references to cross-platform CLI tools. The REST API and .NET API are mentioned, but CLI guidance is Windows-centric.
Recommendations
- Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
- Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or provide bash equivalents.
- Explicitly mention cross-platform tooling and provide sample commands for Linux/macOS environments.
- Reorder sections so that REST and cross-platform CLI methods are presented before or alongside PowerShell.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page provides a comprehensive overview of specifying Service Fabric service endpoints, with XML manifest examples that are cross-platform. However, there is a notable bias in deployment instructions and tooling: the only concrete example of deploying an application uses the Windows PowerShell cmdlet New-ServiceFabricApplication, with a Windows-style path prompt (PS C:\>). There is no equivalent example for Linux (e.g., using sfctl or Azure CLI), and the only mention of Linux is a brief note about the certificate store path. Windows tools and patterns are presented first and exclusively in deployment scenarios.
Recommendations
- Add Linux/macOS deployment examples using sfctl or Azure CLI alongside the PowerShell example.
- When showing command-line examples, provide both Windows and Linux/macOS equivalents, or note when a tool is Windows-only.
- Clarify in the text that Service Fabric supports both Windows and Linux clusters, and link to cross-platform deployment guides.
- Consider reordering or grouping examples so that Windows and Linux approaches are presented with parity.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific build/publish actions (F5/Ctrl+F5/Publish) and GUI interactions. There are no examples or guidance for Linux/macOS users or CLI-based workflows, and PowerShell is mentioned as the alternative for service creation, with no Linux equivalent provided.
Recommendations
- Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml and ApplicationManifest.xml outside Visual Studio.
- Provide CLI-based examples (e.g., using Azure CLI, Bash, or cross-platform tools) for deploying Service Fabric applications.
- Clarify which features are Visual Studio/Windows-only and offer alternatives or workarounds for Linux/macOS environments.
- Mention any limitations or unsupported scenarios for Linux/macOS users up front.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, Windows-specific tools and patterns (such as HTTP.sys, Windows HTTP Server API, netsh, and ServiceManifest.xml endpoint registration) are discussed in detail and often before their Linux equivalents. The HTTP.sys section is extensive, despite being Windows-only, and references Windows tools like netsh and kernel drivers. Kestrel (the cross-platform option) is covered well, but Windows-specific mechanisms and terminology (e.g., endpoint registration, port sharing, kernel drivers) are prominent and discussed first in several sections. There are no Linux/macOS-specific troubleshooting tips, environment setup instructions, or explicit parity notes. PowerShell is not directly referenced, but Windows tools are.
Recommendations
- Add explicit notes or sections clarifying Linux/macOS support and limitations for Service Fabric Reliable Services and ASP.NET Core integration.
- Provide Linux/macOS-specific troubleshooting tips, environment setup instructions, and example workflows (e.g., how to configure ServiceManifest.xml endpoints, firewall rules, and port assignment on Linux).
- Where Windows tools (like netsh or HTTP.sys) are mentioned, offer Linux alternatives or clarify that these steps are not required for Kestrel on Linux/macOS.
- Ensure Kestrel examples are shown first or equally with HTTP.sys, and highlight its cross-platform nature.
- Add links to Linux/macOS documentation for Service Fabric and ASP.NET Core hosting where relevant.
Service Fabric
Replica soft delete for enhanced data protection in Service Fabric
...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), which are Windows-centric tools. There is no mention of Linux equivalents, nor are examples provided for Linux/macOS users (such as using Service Fabric CLI, REST APIs, or FabricClient in .NET Core). Windows tools and patterns are presented exclusively and first, creating friction for non-Windows users.
Recommendations
- Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, if supported.
- Document REST API endpoints or FabricClient usage in .NET Core for cross-platform parity.
- Clarify whether the PowerShell cmdlets are available on Linux via PowerShell Core, or provide alternative instructions.
- Explicitly state any limitations or differences for Linux clusters, if applicable.
- Where possible, show both Windows and Linux/macOS workflows side-by-side.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
Although the page introduction claims Service Fabric clusters run on both Windows Server and Linux, the actual content and supported OS list indicate that standalone clusters are currently Windows-only. Security sections reference Windows authentication and Windows-specific features, and there are no Linux-specific examples or guidance. The documentation gives Windows details first and omits Linux parity.
Recommendations
- Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not yet available.
- Remove or update statements suggesting Linux parity unless Linux support is imminent.
- If Linux support is planned, provide equivalent Linux examples, security guidance, and supported OS lists.
- Explicitly state that all instructions and examples are for Windows environments to avoid confusion.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides examples and instructions for using the Fault Analysis Service primarily via C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API usage), nor is there guidance for Linux-based Service Fabric clusters. The focus on PowerShell and Windows tools creates friction for Linux/macOS users.
Recommendations
- Add examples for using the Fault Analysis Service via Azure CLI, Bash scripts, or REST API, which are cross-platform.
- Clarify whether the Fault Analysis Service is available and supported on Linux-based Service Fabric clusters.
- Provide installation and usage instructions for Linux/macOS environments, including any required SDKs or tools.
- Mention alternative scripting options for non-Windows users, such as Python or Bash.
Virtual Machine Scale Sets
Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration
...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or parity is provided. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section, and the only command-line example is in Azure CLI, but no bash or Linux shell context is given. The documentation assumes cross-platform usage but subtly prioritizes Windows tools and scenarios.
Recommendations
- Add explicit Linux/bash examples for key operations, such as VM creation and migration.
- Provide parity between Azure PowerShell and Azure CLI examples, clarifying which commands are cross-platform.
- Mention Linux-specific migration considerations, such as package manager access and OS disk handling.
- Ensure Linux scenarios (e.g., package manager updates) are given equal prominence to Windows scenarios.
- Clarify which tools (Azure CLI, PowerShell) are recommended for Linux/macOS users and provide links to installation guides.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation is intended for both Windows and Linux VMs, as indicated at the top. However, there are several areas of Windows bias: (1) PowerShell examples are provided alongside CLI, but there are no bash or Linux shell script equivalents; (2) The ARM template example is Windows-centric, defaulting to Windows images and only listing Windows SKUs; (3) In some sections, Windows tools and patterns (like PowerShell) are given equal or more prominence than Linux-native approaches; (4) There are no explicit Linux-focused examples or instructions for Linux-specific configuration (e.g., SSH keys, Linux images in ARM templates).
Recommendations
- In ARM template examples, provide both Windows and Linux image options, or show how to select a Linux image (e.g., Ubuntu, CentOS) and configure SSH authentication.
- Include bash or Linux shell script examples where PowerShell is shown, especially for common tasks like deallocating or updating VMs.
- When listing allowed values for OSVersion or similar parameters, include popular Linux distributions.
- Instruct users on how to configure Linux-specific settings (e.g., SSH keys) in the portal and ARM templates.
- Where possible, alternate the order of CLI and PowerShell examples, or clarify that both are equally supported.
- Explicitly note any differences or additional steps required for Linux VMs, if applicable.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section. PowerShell examples are shown for ARM template deployment, and the prerequisite steps for ARM templates use PowerShell commands exclusively. Additionally, the PowerShell examples use Windows VM images and configurations, while Azure CLI examples use Ubuntu images. The documentation does not provide Bash or cross-platform scripting alternatives for ARM template deployment or feature registration, and PowerShell is presented before CLI in some sections.
Recommendations
- Add Bash or cross-platform shell examples for ARM template deployment and feature registration, using 'az' CLI where possible.
- Include Linux VM image examples in PowerShell sections, or clarify that PowerShell can be used on Linux/macOS (with Azure PowerShell Core).
- Provide parity in example ordering: show CLI and PowerShell examples side-by-side or alternate which comes first.
- Clarify that PowerShell commands can be run on Linux/macOS if using Azure PowerShell Core, or link to instructions for installing Azure PowerShell on non-Windows platforms.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows-specific VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples, and does not provide equivalent Linux image examples. The Quickstart link in the portal section references creating a Windows VM, and Linux VM creation is not mentioned. This creates friction for Linux users, as they must adapt the examples themselves.
Recommendations
- Provide Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in all CLI and PowerShell code blocks.
- Add a Quickstart link for creating a Linux VM in the portal section, or mention both Windows and Linux options.
- Explicitly state that the steps apply to both Linux and Windows VMs, and show how to select a Linux image where relevant.
- Where variables are set (e.g., $image), show both Windows and Linux values, or explain how to choose the appropriate image.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation references both Azure CLI and Azure PowerShell for configuring disk restrictions, but PowerShell is mentioned first and is linked in the custom RBAC role section. The custom RBAC role creation link directs to a PowerShell-specific page, while Linux/CLI alternatives are not mentioned or linked. The CLI is referenced later for private links and network access policy, but PowerShell is given prominence.
Recommendations
- Provide links and examples for creating custom RBAC roles using Azure CLI or ARM templates, not just PowerShell.
- Ensure that CLI and PowerShell options are presented together or in parallel, rather than PowerShell first.
- Add explicit Linux/macOS instructions or links where only Windows/PowerShell options are given.
- Review the order of tool mentions to avoid Windows-first bias.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
recommended_windows
missing_linux_example
Summary
The documentation covers both Linux and Windows VMs, but there are subtle biases: Windows is listed first in the 'Recommended OS for Performance' row, and only Windows is specifically recommended for performance. The only explicit OS recommendation is 'Windows Server 2019+'; no Linux distribution is recommended for best performance, despite Linux being widely used for HPC. Additionally, the 'lstopo' example is Linux-specific, but there are no equivalent Windows/PowerShell commands or guidance for viewing NUMA topology on Windows, which may leave Windows users at a disadvantage.
Recommendations
- Provide explicit Linux OS recommendations for best performance (e.g., RHEL 8.x, Ubuntu 20.04+), not just Windows.
- When listing 'Recommended OS for Performance', include both Linux and Windows options if both are supported.
- Add Windows/PowerShell equivalents for topology inspection (e.g., using 'Get-WmiObject', 'systeminfo', or third-party tools) alongside the 'lstopo' example.
- Where possible, alternate the order of OS mentions or clarify that both Linux and Windows are equally supported unless there is a technical reason to prefer one.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation provides extensive Azure PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and provides installation commands for cmd.exe and PowerShell. While Azure CLI and portal instructions are included, PowerShell is presented first and in greater detail. There are no Linux-specific shell examples or guidance for Linux-native package managers or tools, especially for REST API usage.
Recommendations
- Provide Bash or shell script examples for Linux users alongside PowerShell scripts.
- For REST API usage, recommend cross-platform tools (e.g., curl, httpie, az CLI) instead of or in addition to 'armclient', and explain how to use them on Linux/macOS.
- Clarify that Chocolatey and armclient installation steps are Windows-specific, and offer alternatives for Linux/macOS users.
- Balance the order and depth of PowerShell and CLI examples, ensuring CLI instructions are as detailed as PowerShell.
- Add explicit Linux/macOS guidance where relevant, especially for scripting and automation.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page provides both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is presented first and in greater detail. References to enabling customer-managed keys and double encryption in the prerequisites link to PowerShell guides before CLI or cross-platform alternatives. There are also references to Windows-specific cryptography documentation. While Azure CLI examples are present and sufficient for Linux/macOS users, the overall structure and example ordering show a Windows-first and PowerShell-heavy bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Ensure all prerequisite links include Azure CLI or REST API options where possible, not just PowerShell and Portal.
- Where Windows-specific cryptography documentation is referenced, also provide links to platform-agnostic or Linux-relevant Azure encryption documentation.
- Explicitly state that all steps can be performed from Linux/macOS using Azure CLI, and highlight any differences if they exist.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links exclusively to Windows-specific clustering requirements. There are no mentions of Linux clustering solutions (such as Pacemaker or Corosync), nor are Linux-specific limitations or guidance provided. Windows clustering is the only OS-level scenario discussed, and Windows links are given before any Linux equivalents (which are missing).
Recommendations
- Add information about Linux clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux documentation for clustering and shared disk support.
- Explicitly state whether shared disks are supported or unsupported for Linux-based clusters, and provide guidance for Linux users.
- If Windows Failover Cluster is the only supported scenario, clarify this explicitly to avoid confusion.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as the primary or sole method for creating and converting VHDs. Hyper-V instructions and UI steps are given, but equivalent Linux-native approaches (such as using qemu-img or KVM) are not provided. PowerShell's Convert-VHD is mentioned without Linux alternatives. Windows tools and steps are presented first and more prominently, creating friction for Linux users.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, KVM, VirtualBox).
- Provide step-by-step examples for extracting and manipulating VHDs on Linux, not just Windows/WSL.
- Include Linux-specific guidance for deprovisioning and shutting down the VM, rather than referencing Hyper-V UI actions.
- Mention Linux alternatives alongside Windows tools, not after or instead of them.
- Clarify that Hyper-V and Convert-VHD are Windows-specific, and offer parity for Linux/macOS users.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides a Windows-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd"â¯"sas-URI" --blob-type PageBlob') but does not include a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the explicit example uses Windows file paths and executable names. While the rest of the CLI commands are cross-platform, the critical upload step is Windows-centric. There is no mention of how to run AzCopy on Linux/macOS, nor are Linux file path examples provided.
Recommendations
- Add a Linux/macOS AzCopy example, such as 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Mention that the AzCopy executable may be 'azcopy' on Linux/macOS, not 'AzCopy.exe'.
- Provide both Windows and Linux/macOS file path examples for clarity.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation is focused on Linux VMs, but exhibits Windows bias in several areas: PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are given equal or greater prominence than Azure CLI, despite PowerShell being a Windows-centric tool for most users. Windows-specific terminology and tools (e.g., PowerShell script references, Windows VM mentions, SAS token generation via PowerShell) are used throughout, sometimes before or instead of Linux-native alternatives. REST API and ARM template examples use Windows-style scripts (Write-Host, .ps1) and do not consistently show Linux shell script equivalents. Some notes and examples reference Windows behaviors or requirements (e.g., 'Secondary Logon' service), even in Linux-focused sections.
Recommendations
- Prioritize Azure CLI and Bash examples for Linux scenarios, placing them before PowerShell in the documentation.
- Ensure REST API and ARM template examples use Linux shell scripts (e.g., 'echo Hello World!' or .sh files) rather than Windows PowerShell scripts (.ps1).
- Clarify when PowerShell examples are for cross-platform PowerShell Core, and provide Bash alternatives where possible.
- Remove or clearly separate Windows-specific notes (e.g., 'Secondary Logon' service) from Linux instructions.
- Add guidance for generating SAS tokens and managing blobs using Azure CLI or Bash, not just PowerShell.
- Where commandId examples are given, ensure Linux-relevant commands are shown (e.g., 'ifconfig', 'RunShellScript') and Windows commands are omitted or clearly marked as Windows-only.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Windows and Linux guidance for Azure Image Builder, but there are several areas where Windows-specific tools, commands, and examples are emphasized or presented first. PowerShell is frequently referenced for checksum generation, validation, and build operations, sometimes without equal prominence for Linux alternatives. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less extensive. Some sections (e.g., restart customizer) note the absence of Linux support, and Windows tools (PowerShell cmdlets) are often mentioned before Linux commands.
Recommendations
- Ensure Linux commands (e.g., sha256sum) are always presented alongside PowerShell alternatives for checksum generation and validation.
- Where PowerShell examples are given for build/cancel operations, provide equivalent Bash/Azure CLI scripts for Linux/macOS users.
- When describing customizers, balance the detail between Windows and Linux (e.g., Shell customizer usage, limitations, and troubleshooting).
- For sections where Windows tools are referenced (e.g., Get-FileHash, Start-Sleep), explicitly mention and link to Linux equivalents (e.g., sha256sum, sleep).
- Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
- Clarify limitations (such as lack of Linux restart customizer) and suggest Linux workarounds if possible.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and IIS scenarios are mentioned before Linux equivalents in some sections, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed in detail. However, Linux support is clearly described, and Linux tutorials are linked alongside Windows ones.
Recommendations
- Ensure Linux examples and tools are presented with equal prominence and detail as Windows equivalents.
- When listing container runtimes, provide more information about Linux alternatives (e.g., mention containerd or other runtimes if supported).
- In scenario sections, balance Windows-specific use cases (like IIS lift and shift) with Linux-centric examples (such as Apache or NGINX migration).
- Where possible, alternate the order of Linux and Windows examples to avoid 'windows_first' bias.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is consistently listed first, and there are no explicit Linux/CLI/bash examples or guidance. This creates a subtle Windows-first bias, though the core content is platform-neutral.
Recommendations
- Add explicit examples or references for retrieving the cluster manifest using Azure CLI or bash scripts, especially for Linux/macOS users.
- When listing programmatic options, alternate the order or clarify that all methods are equally supported across platforms.
- Provide a 'Next steps' link to a cross-platform deployment guide (e.g., using Azure CLI or REST) in addition to the PowerShell-focused guide.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides migration guidance applicable to both Linux and Windows VMs. However, in the section describing how to filter disks in the Disk Storage Center, the OS type filter is described as 'Linux and Windows', with Windows mentioned first. Both Azure CLI and PowerShell examples are provided, but neither is prioritized over the other. No Windows-specific tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
- When listing OS types or examples, alternate the order (e.g., 'Linux and Windows' or 'Windows and Linux') to avoid subtle bias.
- Ensure that CLI and PowerShell examples are always presented together, as in this document.
- Consider explicitly stating that all guidance applies equally to Linux and Windows VMs to reinforce parity.
Virtual Machine Scale Sets
Networking for Azure Virtual Machine Scale Sets
...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often given before CLI examples, and some sections (e.g., querying public IPs) provide more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tools, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or in a consistent order (e.g., CLI first, then PowerShell) to avoid implicit Windows-first bias.
- Ensure that CLI examples are as detailed as PowerShell examples, especially in sections like querying public IPs.
- Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) to reassure non-Windows users.
- Where PowerShell is used for advanced tasks, provide equivalent CLI commands or note any limitations.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with equivalent detail, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell documentation, but does not show a preference for Windows tools.
Recommendations
- Consider listing Linux operating system support before Windows, or presenting both together to avoid implicit prioritization.
- Ensure that linked 'Next steps' guides (CLI, Portal, PowerShell) provide parity for Linux users, such as Bash/CLI examples alongside PowerShell.
- Explicitly state that all features and instructions apply equally to Linux and Windows unless otherwise noted.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are presented before Linux equivalents in several sections (e.g., sample workloads, performance throttling examples). All major features and tools for Linux are described, but Windows scenarios are consistently shown first, which may subtly reinforce Windows as the default or primary platform.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel (side-by-side) where possible.
- Ensure Linux examples are as detailed and prominent as Windows examples.
- Consider starting some sections (such as sample workloads or performance examples) with Linux scenarios to balance presentation.
- Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows benchmarking tool (DISKSPD) examples and explanations before Linux tool (FIO) examples. Both platforms are covered with detailed instructions and sample commands, but Windows is given precedence in ordering and tool introduction.
Recommendations
- Reorder sections so Linux (FIO) and Windows (DISKSPD) examples are presented in parallel or with equal prominence.
- Add a summary table comparing DISKSPD and FIO usage for benchmarking on Windows and Linux VMs.
- Explicitly state that both tools are recommended and supported, and clarify which tool is best for each OS.
- Ensure that Linux instructions are as detailed and prominent as Windows instructions.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
Summary
The documentation is focused on Linux VM disk expansion and provides thorough, distribution-specific Linux guidance. However, in the section about classic VM SKU support for 'expand without downtime', only a PowerShell script is provided to check SKU compatibility, with no equivalent Azure CLI or Bash example for Linux users.
Recommendations
- Add an Azure CLI or Bash example for checking VM SKU compatibility for classic VM SKUs, so Linux users can perform the same check without needing PowerShell.
- Where possible, ensure that any Azure PowerShell guidance is accompanied by Azure CLI alternatives, especially for tasks relevant to Linux VM management.
Container Instances
Configure role permissions for standby pools in Azure Container Instances
...container-instances-standby-pool-configure-permissions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation primarily uses the Azure portal for role assignment instructions and mentions PowerShell/CLI only briefly and generically. There are no explicit Windows-only tools or PowerShell-heavy examples, but the portal-centric workflow is often associated with Windows users, and there is no parity for Linux/macOS command-line instructions (e.g., Azure CLI or Bash examples). The troubleshooting section references querying Log Analytics via the portal, and REST API usage is shown, but no CLI or Bash examples are provided.
Recommendations
- Add Azure CLI examples for role assignment and troubleshooting steps, including querying Log Analytics and checking the Runtime View API.
- Provide Bash or cross-platform command-line instructions alongside portal workflows.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or REST API, and link to relevant CLI documentation.
- Where REST API is referenced, show how to use curl or az rest for cross-platform access.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell (commonly associated with Windows environments) is presented before CLI. There is no explicit Linux/macOS bias, but the ordering and emphasis on PowerShell may subtly favor Windows users. All examples are cross-platform, and no Windows-only tools or patterns are used.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally used across Linux, macOS, and Windows.
- Explicitly note that both PowerShell and CLI are cross-platform, and clarify that CLI is available natively on Linux/macOS.
- Consider adding brief notes or links about installing Azure CLI on Linux/macOS for new users.
- Ensure parity in example depth and clarity between PowerShell and CLI sections.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced with a Windows file path, and the application package structure example uses a Windows-style executable (.exe). There is no explicit Linux example or mention of Linux tooling, and Visual Studio (a Windows-centric IDE) is referenced as a packaging option before command-line utilities. However, the content does not prevent Linux/macOS users from understanding or completing the task, as Service Fabric supports guest executables of any type (Node.js, Java, C++), and the packaging model is platform-agnostic.
Recommendations
- Add Linux/macOS file path examples for schema definitions, or clarify if the schema is available on non-Windows platforms.
- Include examples of packaging non-Windows executables (e.g., .sh, Node.js, Java) in the directory structure.
- Mention cross-platform command-line tools and editors (e.g., VS Code, CLI utilities) alongside Visual Studio.
- Explicitly state that the packaging process is platform-agnostic and provide links or guidance for Linux/macOS users.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, mentioning PowerShell and Visual Studio (both Windows-centric tools) first, with Linux-compatible tools (sfctl, install.sh) mentioned second. There is a slight bias toward Windows tools and workflows, but Linux options are present.
Recommendations
- Present Linux-compatible tools (sfctl, install.sh) before or alongside Windows tools to avoid Windows-first bias.
- Include explicit Linux/macOS example commands and workflows, such as using sfctl from Bash or shell scripts.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
- Add a section or note for Linux/macOS users outlining recommended workflows and tools.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions Windows development and tools (Visual Studio, PowerShell) before Linux equivalents (Eclipse, Yeoman), and links to the Windows quickstart as the primary next step. However, Linux support and tools are referenced, and the page is not Windows-specific.
Recommendations
- Present Windows and Linux development options in parallel, rather than listing Windows first.
- Include links to both Windows and Linux quickstart guides in the 'Next steps' section.
- Ensure examples and tool references are balanced between Windows and Linux throughout the documentation.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is largely platform-neutral, but there are subtle indications of Windows bias. Windows terminology and tools (such as references to 'auto-start Windows service', 'FabricHost.exe', and EXE/DLL files) are mentioned first or exclusively in some sections, even though Service Fabric supports Linux. Linux equivalents are not always described with equal clarity or prominence. However, the page does acknowledge Linux support and containers, and does not prevent Linux/macOS users from understanding the concepts.
Recommendations
- Where Windows-specific tools or terminology are mentioned (e.g., 'auto-start Windows service', 'EXE/DLL'), add clarifying notes about Linux equivalents (e.g., systemd services, ELF binaries).
- When describing node startup and service processes, explicitly mention Linux process management and file types alongside Windows examples.
- Ensure that references to executables and packaging (e.g., code packages) include Linux file formats and conventions.
- Consider alternating the order of Windows and Linux mentions, or grouping them together to reinforce parity.
- Add links or references to Linux-specific documentation or guides where appropriate.
Virtual Machine Scale Sets
Configure rolling upgrades on Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI, and are presented in dedicated tabs throughout. While Azure CLI is cross-platform, PowerShell is primarily used by Windows users, and there are no explicit Linux/macOS-specific instructions or notes. The order of examples is generally CLI first, then PowerShell, which is positive, but the presence of PowerShell throughout may suggest a mild Windows bias. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks using Azure CLI or ARM templates.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add a note clarifying that PowerShell examples are primarily for Windows users, and that CLI is suitable for all platforms.
- Consider including Bash or shell script examples for common automation scenarios, or linking to relevant Linux/macOS guidance.
- Ensure that all screenshots and instructions referencing the Azure portal are platform-neutral.
Virtual Machine Scale Sets
Rolling upgrades with MaxSurge for Virtual Machine Scale Sets
...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is present, which is Windows-centric, and appears after the CLI example. However, the CLI example is cross-platform and is shown before PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and Linux parity is generally maintained. There are no missing Linux examples, as Azure CLI is the recommended cross-platform tool. The bias is minor, mainly due to the inclusion of PowerShell and its labeling, but does not significantly impact Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Optionally, add a note that PowerShell is available cross-platform, but is most commonly used on Windows.
- Ensure that CLI examples are always shown before PowerShell to reinforce Linux parity.
- Consider adding Bash shell scripting examples if relevant for advanced automation.
Virtual Machine Scale Sets
Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview)
...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or immediately after CLI examples, and the PowerShell section uses Windows-specific extension names (e.g., ApplicationHealthWindows). Portal instructions reference Windows UI patterns. There is a slight bias in the order and prominence of Windows tools and examples, but Linux parity is generally maintained via Azure CLI and REST API instructions.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples in each section.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
- For VMSS extension examples, explicitly mention both ApplicationHealthLinux and ApplicationHealthWindows, and clarify which to use for Linux/Windows VM images.
- Consider adding a short note at the start of each section indicating which tools are cross-platform and which are Windows-only.
- Ensure screenshots and portal instructions are not overly Windows UI-specific, or clarify that the portal is platform-agnostic.
Virtual Machine Scale Sets
Orchestration modes for Virtual Machine Scale Sets in Azure
...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides an Azure CLI example for VM creation, but does not specify whether the example is for Windows or Linux, nor does it provide explicit Linux-specific guidance or parity. The mention of Azure Site Recovery 'via PowerShell' in the backup/recovery section suggests a Windows-centric tool is referenced without a Linux alternative. Overall, the documentation is mostly platform-neutral, but there is a mild bias in tool references and lack of explicit Linux examples.
Recommendations
- Provide explicit Linux-specific examples alongside Windows/PowerShell examples, especially for VM creation and management.
- Clarify whether Azure CLI commands are applicable to both Windows and Linux, and provide any necessary OS-specific flags or considerations.
- When referencing Azure Site Recovery via PowerShell, mention if there are equivalent CLI or REST API options for Linux users.
- Add sample workflows or links for Linux VM scale set scenarios, such as deploying Linux workloads, configuring extensions, or monitoring health.
- Ensure that all referenced tools (e.g., Azure CLI, PowerShell) are presented with parity, and note cross-platform compatibility.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension and custom metrics. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash examples, and Windows-specific tools (PowerShell cmdlets, ApplicationHealthWindows extension type) are referenced prominently. The PowerShell example for installing the extension uses 'ApplicationHealthWindows' as the type, while the Bash example uses 'ApplicationHealthLinux'. Both are shown, but Windows tools and patterns are often mentioned first or in more detail.
Recommendations
- Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in critical sections.
- Clarify that both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' extension types are supported, and provide explicit guidance for each OS.
- Balance the detail and prominence of PowerShell and Bash examples, ensuring Linux instructions are as comprehensive as Windows ones.
- Where possible, use neutral language and tools (e.g., Azure CLI, REST API) before platform-specific tools.
- Explicitly state OS-specific requirements or differences where relevant.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a balanced overview of backup and disaster recovery for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before their Linux equivalents. For example, application-consistent backup is described using Windows-specific mechanisms first, and Linux solutions (like fsfreeze) are referenced as secondary, with less detail. SQL Server backup options are discussed in depth, while Linux database solutions (like Oracle or MongoDB) are mentioned but not elaborated upon. Examples and tool recommendations tend to prioritize Windows approaches.
Recommendations
- Provide equal detail for Linux backup tools and patterns, such as describing how to achieve application-consistent backups for popular Linux workloads (e.g., Oracle, PostgreSQL, MySQL) and referencing relevant Linux-native solutions.
- When mentioning Windows tools (e.g., Volume Shadow Service), immediately follow with Linux equivalents (e.g., fsfreeze, LVM snapshots, or application-specific backup mechanisms) and clarify their limitations or advantages.
- Expand examples for Linux database solutions (e.g., Oracle, MongoDB, PostgreSQL) to match the depth given to SQL Server.
- Ensure that tables and comparison sections reference both Windows and Linux consistency mechanisms equally.
- Consider including links to Linux backup best practices or third-party solutions for Linux VMs.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally presents cost optimization best practices for Azure virtual machines in a platform-neutral manner. However, there is a minor bias in the development/test environment section, where Windows VM sizing guidance ('Use at least B2 for Windows machines') is provided before any Linux-specific guidance, and Windows pricing links are mentioned before Linux equivalents in one section. No PowerShell-heavy, Windows tools, or missing Linux example biases are evident. All major recommendations and features are applicable to both Windows and Linux VMs.
Recommendations
- Provide equivalent VM sizing guidance for Linux machines if relevant, or clarify if the recommendation is Windows-specific.
- When referencing pricing pages or VM sizes, mention Linux and Windows options together, or list Linux first in some cases for parity.
- If automation examples are provided in future updates, include both Windows (PowerShell) and Linux (Bash/shell) scripts.
- Clarify when recommendations are OS-specific (e.g., 'Use at least B2 for Windows machines; for Linux, B1 may suffice depending on workload').
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, there are several instances where Windows/PowerShell tools and documentation links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent (e.g., in revoking access and enabling automatic key rotation), and Windows documentation links are often listed first. No critical Linux gaps are present, but the ordering and prominence of Windows tools create minor friction for Linux users.
Recommendations
- Present Azure CLI (Linux/macOS) and PowerShell (Windows) links and examples in parallel, or alternate their order to avoid Windows-first bias.
- Where PowerShell and CLI are mentioned, clarify that both are fully supported and provide equal visibility to Linux/macOS workflows.
- Add explicit Linux/macOS examples or references where only PowerShell is mentioned, such as in the 'revoking access' section.
- Consider grouping CLI and PowerShell instructions under a common heading (e.g., 'Using Azure CLI or PowerShell') to reinforce parity.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for creating an Azure Compute Gallery using Portal, Azure CLI, PowerShell, and REST API. The PowerShell example is presented as a dedicated tab alongside CLI and REST, and is not Windows-specific in its content. However, PowerShell is a Windows-centric tool, and its inclusion as a primary example (with its own tab) may signal a mild Windows bias. The CLI examples use Azure CLI, which is cross-platform, and REST API examples are platform-agnostic. The ordering of examples (Portal, CLI, PowerShell, REST) places PowerShell before REST, but after CLI, which is acceptable. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a note that PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Ensure that CLI examples are always present and up-to-date.
- If possible, provide Bash shell scripting examples for Linux users (though Azure CLI is sufficient).
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for key operations, but PowerShell is often presented before CLI. Portal, PowerShell, and CLI are all covered, but PowerShell (a Windows-centric tool) is given prominence in several sections. However, Linux parity is generally maintained, and CLI examples are present. The 'Next steps' section lists both Linux and Windows guides, with Linux listed first.
Recommendations
- Where possible, alternate the order of PowerShell and CLI examples to avoid implicit prioritization of Windows tools.
- Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add brief notes or links for Bash scripting or Linux-native tools if relevant.
- Ensure screenshots and portal instructions are not Windows-specific (they appear generic here).
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types, but PowerShell examples are consistently present and often shown alongside or immediately after CLI examples. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are always present and are cross-platform. There are no Windows-only tools or missing Linux examples, but PowerShell usage is emphasized and sometimes appears before CLI in section ordering.
Recommendations
- Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (with some support on Linux/macOS).
- Where possible, add bash shell scripting examples for disk operations, especially in sections where PowerShell scripting is shown.
- Clarify that all disk operations shown via CLI are fully supported on Linux and macOS.
- Review section ordering to ensure CLI is not secondary to PowerShell, reducing perceived Windows bias.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is focused on Linux VM extensions, but consistently presents Azure PowerShell examples alongside Azure CLI, and often lists PowerShell examples immediately after CLI. While both CLI and PowerShell are cross-platform, PowerShell is more commonly associated with Windows. The documentation does not provide Linux-native command-line examples (such as Bash scripting or direct REST API usage), and sometimes references PowerShell before CLI in explanations. However, all examples are functional for Linux users and do not require Windows-specific tools.
Recommendations
- Consider emphasizing Azure CLI as the primary example, since it is more commonly used on Linux and macOS.
- Where PowerShell is shown, clarify that Azure PowerShell is cross-platform, and provide links to installation instructions for Linux/macOS.
- Add Bash or shell script examples for common extension management tasks, especially where Azure CLI is used.
- Ensure that CLI examples are always listed before PowerShell, or group them together with clear labeling.
- Explicitly note that all shown tools (CLI, PowerShell) are available on Linux/macOS, to avoid confusion.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on Azure Linux VMs and the NVIDIA GPU Driver Extension for Linux, with nearly all examples and instructions tailored for Linux environments. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is presented before Azure CLI in the deployment section. There is a brief mention of a Windows extension, but it is clearly separated and not the focus. No Windows-specific tools or patterns are prioritized, and Linux commands and troubleshooting steps are comprehensive. The inclusion of PowerShell is likely for cross-platform Azure management, but its placement before CLI may create minor friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more native to Linux environments.
- Clarify that PowerShell examples are for users managing Azure from non-Linux platforms, and highlight CLI as the primary method for Linux users.
- Consider adding Bash script examples for common tasks, as Bash is the default shell for most Linux distributions.
- Ensure screenshots and instructions in the Azure portal section are explicitly labeled as Linux-specific where relevant.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is focused on Linux, as indicated by the title and content. However, in several sections, Windows-oriented tools and patterns (specifically Azure PowerShell) are presented before their Linux-native equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown first, which may create friction for Linux users who typically use Azure CLI or shell scripting. There are also warnings about PowerShell-specific issues, but no equivalent Linux-specific troubleshooting advice. All actual extension configuration, certificate paths, and operational details are Linux-centric.
Recommendations
- Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux.
- Add Linux-specific troubleshooting tips (e.g., using journalctl, systemd, or bash scripting) alongside PowerShell troubleshooting.
- Clarify that PowerShell is optional and not required for Linux deployments.
- Consider grouping CLI and PowerShell instructions under clearly labeled sections for each platform.
- Ensure that all example commands use Linux shell syntax (e.g., $VAR, --options) where appropriate.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows instructions for deprovisioning/generalizing VMs before imaging. However, the Windows section presents Windows-specific tools and PowerShell examples first in the 'Generalize a Windows VM' step, and the Windows prerequisites are more detailed. The Linux section is clear and includes links to distro-specific guides, but Windows examples (such as Set-AzVm) are shown in PowerShell, while Linux uses Azure CLI. The order of sections is Linux first, but Windows tools are emphasized in their section.
Recommendations
- Ensure parity in detail between Linux and Windows prerequisites and steps.
- Provide Azure CLI equivalents for Windows VM generalization (if available), not just PowerShell.
- Consider adding a summary table comparing Linux and Windows steps/tools for clarity.
- Balance the depth of instructions for both OS types, especially regarding prerequisites and troubleshooting.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but in several places Windows/PowerShell examples are presented before Linux/CLI equivalents. PowerShell examples are detailed and prominent, and Windows terminology (e.g., Sysprep) is mentioned before Linux-specific steps. However, Linux is well-represented overall, and CLI examples are provided for both OS types.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (cross-platform) examples first.
- Ensure Linux-specific terminology and examples are given equal prominence and detail as Windows/PowerShell.
- Consider adding explicit Linux PowerShell (pwsh) examples if relevant, or clarify that PowerShell examples are Windows-centric.
- Where possible, clarify that CLI commands work on Linux/macOS as well as Windows.
- Review for subtle language that assumes Windows as the default (e.g., mentioning Sysprep before waagent -deprovision).
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is focused on Azure Disk Encryption for Linux VMs and provides both Azure CLI and Azure PowerShell examples throughout. However, PowerShell cmdlets and scripts are often mentioned first, and some critical instructions (such as backup requirements and encryption prerequisites) reference PowerShell cmdlets before their CLI equivalents. There is also frequent use of PowerShell-specific terminology and patterns, which may create friction for Linux users who typically prefer CLI or shell scripting. Nevertheless, CLI examples are present for all major operations, and the documentation is not Windows-exclusive.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially in critical sections.
- Clarify that PowerShell can be used cross-platform, but highlight that Azure CLI is the native tool for Linux environments.
- Reduce PowerShell-specific terminology in general Linux-focused documentation, or provide equivalent Bash/shell scripting guidance.
- Add explicit notes or guidance for Linux users on how to use Azure CLI in native shells, not just in PowerShell sessions.
- Where possible, provide Bash script examples for common automation scenarios.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is focused on Linux VMs and provides Linux-specific instructions and examples. However, it mentions Azure PowerShell and PowerShell scripts alongside Azure CLI, and references PowerShell cmdlets in the terminology section. In the 'Next steps' section, PowerShell resources are listed immediately after CLI resources, rather than prioritizing Linux-native tools. There is minor bias in the inclusion and ordering of Windows-centric tools (PowerShell), but Linux parity is largely maintained.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, or prioritize Azure CLI as the primary tool for Linux users.
- In 'Next steps', list Azure CLI resources before PowerShell resources, and explicitly note that PowerShell is optional for Linux users.
- In the terminology section, explain that PowerShell cmdlets are available on Linux and macOS, or remove if not relevant to Linux VM management.
- Where PowerShell is referenced, provide context about its cross-platform support to avoid confusion for Linux users.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more detailed and extensive. This creates a mild Windows bias, as PowerShell is less commonly used on Linux, and Linux users typically prefer Azure CLI or Bash. The OS-level section uses Bash commands, which is appropriate for Linux, but the prominence and depth of PowerShell coverage may create friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is more native to Linux environments.
- Ensure Azure CLI coverage is as detailed as PowerShell, including all scenarios (single pass, dual pass, unattached disks, managed/unmanaged disks).
- Clarify that PowerShell examples are optional for Linux users and highlight Azure CLI as the primary cross-platform tool.
- Consider removing or minimizing PowerShell examples unless there is a strong use case for PowerShell on Linux.
- Add Bash scripting examples for interacting with Azure CLI, especially for common automation scenarios.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, in several sections, Windows/Hyper-V instructions are presented first, and references to Windows tools (such as Hyper-V Manager and PowerShell convert-vhd cmdlet) appear before Linux alternatives. Linux/KVM/VMware instructions are comprehensive and present, but Windows/Hyper-V is prioritized in ordering and introductory notes.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- When mentioning disk conversion tools, list Linux tools (qemu-img, guestfish) before or alongside Windows tools (Hyper-V Manager, convert-vhd).
- In introductory notes, avoid phrasing that implies Windows/Hyper-V is the default or primary method; instead, clarify that multiple platforms are equally supported.
- Ensure that all references to disk conversion or VM preparation include both Windows and Linux options in parallel, not sequentially.
- Consider adding a summary table or matrix at the top to help users quickly identify instructions relevant to their platform.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is focused on Linux VM time sync in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific content, which may create a perception of Windows-first bias. All technical examples, tools, and instructions are Linux-centric and relevant to the page's purpose.
Recommendations
- Move or minimize Windows Server 2016 discussion to a background or context section, clarifying its relevance to Linux VM time sync.
- Ensure Linux-specific guidance is presented first in the overview and configuration sections.
- Add a brief summary explaining why Windows host time sync is relevant for Linux VMs, to avoid confusion.
- Consider linking to Linux time sync concepts before referencing Windows documentation in the 'Next steps' section.