← Back to Dashboard
281
Pages Scanned
102
Pages Flagged
281
Changed Pages
36.3%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09 Scan started

Scan Information

Started At: 2026-02-26 00:00:09

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 281

Files Completed: 281

Problematic Pages

102 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples, configuration guidance, and usage scenarios are implicitly Windows-centric. There are no Linux-specific instructions, examples, or parity guidance, and Linux users are explicitly excluded from using this feature.
Recommendations
  • Add a prominent note at the top clarifying that reverse proxy is Windows-only and not supported on Linux clusters.
  • Provide alternative guidance or links for Linux cluster users, such as recommended patterns for service discovery and communication.
  • If possible, document any roadmap or alternatives for Linux users, or clarify if/when Linux support is expected.
  • Ensure that all setup and usage instructions are clearly marked as Windows-only to avoid confusion.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform guidance is given for critical operations, creating friction for non-Windows users.
Recommendations
  • Add equivalent CLI examples using Azure CLI or REST API for Linux/macOS users.
  • Clarify whether Service Fabric Explorer is accessible from Linux/macOS, or provide alternatives.
  • Explicitly state platform requirements for commands and tools.
  • Include cross-platform instructions for connecting to Service Fabric clusters and performing administrative tasks.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell-only examples for key upgrade operations and references Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux/macOS instructions. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for application upgrade operations alongside PowerShell examples.
  • Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
  • Clarify when a feature or limitation (such as http.sys or certificate handling) is Windows-specific, and provide Linux alternatives or workarounds if available.
  • Ensure that all critical upgrade workflows are documented with at least one cross-platform method.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
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), and reference Windows container compatibility. Querying deployment status is only shown via PowerShell and C# APIs, with no mention of Linux CLI or Bash alternatives. There are no Linux container examples or guidance for Linux/macOS users.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) with Bash commands.
  • Provide instructions for querying deployment status using Azure CLI or Bash, if available.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and if so, provide relevant examples.
  • If Windows-only support is intentional, explicitly state this in the introduction to avoid confusion.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, with some Windows-centric patterns. The JSON snippet for the Service Fabric Virtual Machine extension uses a Windows-style file path (D:\\SvcFab) in the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks. There is no explicit Linux/macOS example or guidance for equivalent operations, and Windows patterns (such as RDP and file paths) are referenced without Linux alternatives.
Recommendations
  • Provide Linux-specific examples for the 'dataPath' property (e.g., /var/svcfab or similar) alongside the Windows example.
  • Add guidance or links for connecting to Linux nodes (e.g., SSH instructions) in the 'Next steps' section, not just Windows RDP.
  • Include Linux/macOS equivalent scripts or instructions for changing admin credentials and port ranges.
  • Clarify when instructions are Windows-only and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides a PowerShell example for querying Service Fabric partition health, using Windows-specific syntax and paths (e.g., 'PS C:\Users\User >'). No equivalent Linux/macOS CLI example is given, and PowerShell is presented as the default/only method for interacting with Service Fabric health. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via REST APIs and sfctl (Service Fabric CLI), but these are not mentioned.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API calls for health queries.
  • Mention that Service Fabric management can be performed on Linux/macOS using sfctl and REST APIs, and provide links to relevant documentation.
  • Avoid presenting Windows/PowerShell examples as the default; instead, offer both Windows and Linux/macOS examples side-by-side.
  • Clarify any platform-specific limitations if certain commands/tools are Windows-only.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides general guidance on upgrading Azure Service Fabric clusters and includes references to using PowerShell and Azure CLI for management tasks. However, it notably references Windows-specific upgrade procedures (such as Patch Orchestration Application and a link to 'Patch the Windows operating system in your Service Fabric cluster') without mentioning Linux equivalents or providing Linux-specific guidance. Examples and tool references (PowerShell) are presented without Linux parity or explicit mention of Bash/CLI usage, and Windows OS patching is discussed exclusively.
Recommendations
  • Add explicit Linux cluster upgrade guidance, including links to relevant documentation for patching Linux nodes.
  • When referencing PowerShell, also mention Bash/Azure CLI usage for Linux/macOS users, and provide examples for both platforms.
  • Clarify which sections are Windows-only and provide Linux alternatives or note if Linux clusters are managed differently.
  • Include links or references to Linux Service Fabric cluster maintenance and upgrade documentation, if available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no mention of Azure CLI equivalents or Linux/macOS workflows. Application packaging is described using Visual Studio, a Windows-centric tool, and directory paths are given in Windows format. There are no Linux/macOS-specific instructions or examples, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Provide directory path examples in both Windows and Linux/macOS formats.
  • Mention alternative editors or tools for non-Windows users.
  • Clearly indicate which steps are Windows-only and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric networking patterns demonstrates Windows bias primarily through the exclusive use of PowerShell commands for deployment and management examples. There are no Linux/macOS CLI (e.g., Azure CLI/bash) equivalents provided, and Windows tools (such as RDP and ping from a Windows command prompt) are referenced without mentioning cross-platform alternatives. Windows-centric examples are presented first and throughout, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Mention cross-platform alternatives for accessing VMs (e.g., SSH instead of RDP) and for network testing (e.g., ping from Linux/macOS terminal).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and provide relevant instructions or links.
  • Where possible, provide template deployment instructions using the Azure portal and Azure CLI, not just PowerShell.
  • Review all examples to ensure Linux/macOS users can follow along without needing Windows-specific tools.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page presents PowerShell as the primary scripting interface for interacting with the Fault Analysis Service, without mentioning or providing examples for Linux/macOS command-line tools or SDKs. PowerShell is highlighted as the main way to use the service after C#, and no Linux-specific instructions or CLI alternatives (such as Bash or Azure CLI) are given.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Mention cross-platform SDKs or tools (e.g., Python, Java) if available, and provide sample usage.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance for Linux/macOS users if so.
  • If the Fault Analysis Service is accessible only via PowerShell on Windows, explicitly state this limitation.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The Service Fabric schema location is referenced using a Windows file path first, and Windows terminology (e.g., 'MY' certificate store) is used before mentioning Linux equivalents. Linux-specific deployment instructions or CLI examples are missing, and Linux file paths and tools are only briefly referenced.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
  • Reference Linux file paths and certificate stores equally and earlier in relevant sections.
  • Clarify which steps or commands differ between Windows and Linux clusters, and provide explicit guidance for Linux users.
  • Where possible, avoid Windows-centric terminology or provide Linux equivalents in parallel.
  • Include links to Linux-specific Service Fabric documentation or tutorials.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs, but the PowerShell section is presented before the Azure CLI section and contains more detailed, step-by-step examples. This may create friction for Linux users, as PowerShell is not the native or default scripting environment for Linux, and the CLI section, while present, is less comprehensive in some areas. The portal instructions are platform-neutral, and the OS-level checks use Linux-native tools, but the prominence and detail of PowerShell examples suggest a Windows bias.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, covering all scenarios (single pass, dual pass, unattached disks, managed/unmanaged disks).
  • Explicitly note that PowerShell examples are for users who have PowerShell Core installed on Linux, but Azure CLI is recommended for Linux environments.
  • Consider adding Bash script examples for common tasks, where appropriate.
  • Review and balance the depth of coverage between PowerShell and CLI sections.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and patterns, such as the Key Vault VM extension for Windows and S-channel certificate linking. Windows terminology and mechanisms (e.g., certificate store locations, ACLing, S-channel, CERT_RENEWAL_PROP_ID) are used throughout, often without Linux/macOS equivalents or guidance. While the Service Fabric cluster can run on Linux, the examples and explanations are heavily Windows-centric, and Linux-specific instructions or parity are missing.
Recommendations
  • Add equivalent Linux/macOS examples for certificate provisioning, rotation, and management, using Bash, Azure CLI, or relevant Linux tools.
  • Clarify which mechanisms (e.g., Key Vault VM extension, certificate linking) are Windows-only and provide alternative approaches for Linux clusters.
  • Include guidance for Linux certificate stores and permissions (e.g., /etc/ssl/certs, file permissions) alongside Windows certificate store and ACLing.
  • Provide troubleshooting steps and automation scripts for Linux environments, not just PowerShell.
  • Explicitly state platform limitations and supported OSes for each mechanism and example.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Azure Service Fabric container image management references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, and these are mentioned before any Linux equivalents. The examples and explanations focus on Windows images and do not mention common Linux container images or provide Linux-specific guidance, despite Service Fabric supporting Linux containers.
Recommendations
  • Include examples of Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify that the cleanup settings apply to both Windows and Linux containers, and provide parity in documentation for Linux scenarios.
  • Mention Linux base images in the default exclusions or explain how to configure exclusions for Linux containers.
  • Add a note or section describing any differences in image management between Windows and Linux nodes, if applicable.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., certificate store paths like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting guidance (event logs, CAPI2 logging) are presented first or exclusively. Linux equivalents are mentioned briefly (e.g., /var/lib/sfcerts), but Windows concepts and tools dominate the examples and troubleshooting advice.
Recommendations
  • Expand Linux-specific guidance: Provide explicit instructions and examples for Linux certificate management, including certificate store locations, relevant commands (e.g., openssl, Linux file permissions), and troubleshooting steps.
  • Balance troubleshooting advice: Include Linux log locations, error codes, and diagnostic tools (e.g., journalctl, syslog, Service Fabric logs on Linux) alongside Windows event log guidance.
  • Clarify cross-platform differences: Where Windows APIs or concepts are referenced (e.g., CertGetCertificateChain, CAPI2 logging), explain Linux equivalents or note platform-specific behavior.
  • Show Linux-first or parallel examples: When presenting configuration snippets or procedures, offer Linux examples or note differences in order and prominence.
  • Reference Linux documentation: Link to Service Fabric Linux-specific docs or Azure docs covering Linux cluster setup and certificate management.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While there are references to Linux custom image creation and Azure CLI usage, Windows is emphasized first and PowerShell is used for role assignment, with no equivalent Linux/bash example provided.
Recommendations
  • Clarify in the introduction that both Windows and Linux custom images are supported if applicable.
  • Provide equivalent Linux/bash commands for role assignment (e.g., using Azure CLI instead of PowerShell).
  • Include ARM template examples for Linux node types if Service Fabric Managed Cluster supports them.
  • Ensure links to Linux documentation are as prominent as Windows links.
  • Explicitly state any limitations or parity differences between Windows and Linux custom image support.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (mcr.microsoft.com/windows/nanoserver:1809), and uses Windows-specific paths and commands (e.g., C:\, cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible patterns or tools. The ApplicationManifest and ServiceManifest examples are Windows-centric, and the 'IMPORTANT' note explicitly assumes familiarity with Windows container applications.
Recommendations
  • Add equivalent examples using Linux containers (e.g., mcr.microsoft.com/linux/base images) and Linux shell commands.
  • Show how Initializer CodePackages can be used with Linux containers, including appropriate volume mounts and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance for Linux users.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
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 only explicit command-line examples are PowerShell-based, and these are used for critical migration steps (disabling nodes, removing nodes, updating DNS). There are no equivalent Bash/CLI or Linux/macOS instructions, and PowerShell is presented as the default tool for these operations. Additionally, the sample template for Basic SKU migration references a Windows-specific template first, with the Ubuntu template mentioned only in passing.
Recommendations
  • Add Azure CLI or Bash script examples for node management, resource removal, and DNS updates to provide parity for Linux/macOS users.
  • Explicitly mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
  • Reference both Windows and Linux sample templates equally, and clarify which template is suitable for each OS.
  • Where possible, use platform-agnostic Azure CLI commands instead of PowerShell for resource management.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided for scripting/automation, with no mention of Azure CLI (az), Bash, or cross-platform scripting. PowerShell is presented as the default scripting tool, and there are no Linux/macOS-specific instructions or parity for command-line operations.
Recommendations
  • Add Azure CLI (az) examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples require PowerShell Core (pwsh) for cross-platform use, or clarify if only Windows PowerShell is supported.
  • Where possible, provide Bash scripting examples or reference REST API usage for automation.
  • Reorder sections to present cross-platform methods (Portal, ARM template, Azure CLI) before Windows-specific tools like PowerShell.
  • Add a note clarifying the supported platforms for each tool and recommend Azure CLI for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, the emphasis on PowerShell may create friction for Linux/macOS users who typically prefer CLI or other native tools. The examples and guidance do not include Linux-specific command-line usage or highlight Azure CLI usage equivalently.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention Azure CLI before or equally with PowerShell in best practices, recognizing CLI as the default for many Linux/macOS users.
  • Clarify that Azure PowerShell is cross-platform, but provide links to CLI documentation for parity.
  • Include sample sfctl commands where appropriate, especially for Linux users.
  • Consider a table or section comparing PowerShell and CLI usage for common tasks.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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 for resource operations, with only brief mention of the Azure CLI (az resource) for deleting applications. Most examples and links are PowerShell-focused, and PowerShell tools are mentioned before Azure CLI equivalents, which are more cross-platform and commonly used on Linux/macOS.
Recommendations
  • Add Azure CLI equivalents for all PowerShell cmdlet examples, especially for creating and deleting applications, services, and application type versions.
  • Present Azure CLI and PowerShell examples side-by-side or indicate both options equally, rather than defaulting to PowerShell.
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and provide links to relevant CLI documentation.
  • Review links to ensure both PowerShell and CLI documentation are referenced.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation generally covers both Windows and Linux Service Fabric clusters, but there are several instances where Windows tools, terminology, or examples are presented first or exclusively. Windows-specific tools (Event Log, EventStore APIs, Diagnostics Agent) are mentioned with more detail, while Linux equivalents are referenced but not explained or linked as thoroughly. Some sections provide Windows configuration steps or references before Linux, and Linux-specific guidance is sometimes relegated to a single sentence or external link. There are also missing Linux-specific examples for certain monitoring scenarios.
Recommendations
  • Ensure Linux monitoring tools and configuration steps are described with equal detail and clarity as Windows equivalents.
  • Provide Linux-specific examples (e.g., using LTTng, Syslog, or other Linux-native tools) alongside Windows/PowerShell examples.
  • When referencing tools or APIs (e.g., EventStore, Diagnostics Agent), clarify their availability and alternatives for Linux clusters.
  • Avoid presenting Windows tools or terminology first unless the feature is Windows-only; use neutral or parallel structure.
  • Add links to Linux-focused tutorials and documentation where available, matching the depth of Windows guidance.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell commands and modules (e.g., Microsoft.ServiceFabric.Powershell.Http), with no mention of Linux/macOS-compatible tools or CLI equivalents. There are no Bash, Azure CLI, or cross-platform REST API examples outside of PowerShell scripting. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add Azure CLI examples for backup and restore operations, where possible.
  • Provide generic REST API examples using curl or HTTPie for Linux/macOS users.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform, and if not, suggest alternatives.
  • Include Bash shell scripts or instructions for Linux/macOS environments.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation contains evidence of Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio, a Windows-centric tool, for authoring manifests. Additionally, it mentions the ServiceFabric PowerShell module for service creation, without providing Linux/bash equivalents or clarifying cross-platform alternatives. Windows-specific terminology and tools are presented first or exclusively, while Linux/macOS options are not discussed.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as referencing the location of Service Fabric schema files on non-Windows systems.
  • Suggest cross-platform editors (e.g., VS Code) and explain how to enable XML schema validation and IntelliSense for manifest files.
  • Mention and provide examples for using Service Fabric CLI (sfctl) or REST APIs for service creation and management, alongside PowerShell.
  • Clarify any differences in file paths, tooling, or workflows for Linux/macOS clusters and developers.
  • Explicitly state if certain steps are Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) as primary examples for operational tasks such as deployment, upgrade, and removal. REST API alternatives are mentioned, but PowerShell is often listed first and no Linux-specific CLI examples (such as Azure CLI or sfctl) are provided for these workflows. This creates friction for Linux/macOS users, as they must infer how to perform these actions using cross-platform tools.
Recommendations
  • Add explicit examples using Azure CLI and sfctl for all operational tasks (deploy, upgrade, remove, etc.), especially where PowerShell cmdlets are currently used.
  • Where multiple tooling options exist, list cross-platform tools (Azure CLI, sfctl, REST API) before Windows-specific tools (PowerShell).
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
  • Include sample command lines for Linux/macOS environments alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell and Visual Studio. SFCTL (the cross-platform CLI) is covered in a separate section with less detail and fewer examples. The page structure and example order favor Windows tools, which may create friction for Linux/macOS users.
Recommendations
  • Present SFCTL (Service Fabric CLI) parameters and examples alongside PowerShell/Visual Studio, not after them, to avoid Windows-first ordering.
  • Provide equally detailed parameter tables and usage examples for SFCTL as are given for PowerShell.
  • Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter formats.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
  • Consider a summary table comparing all upgrade methods (PowerShell, Visual Studio, SFCTL, REST) with OS/platform applicability.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration. However, in the section describing file share backup storage, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are mentioned, with no examples or guidance for Linux-based file shares (e.g., Samba/CIFS or NFS). There are no PowerShell or Windows command-line examples, but the file share section implicitly assumes Windows environments.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., Samba/CIFS or NFS), including path formats and authentication options.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide relevant instructions.
  • Mention any limitations or requirements for Linux/macOS clusters regarding file share backup storage.
  • If file share backup is Windows-only, explicitly state this to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides several manual scaling steps exclusively using PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without Linux CLI or cross-platform alternatives. Windows/PowerShell tooling is referenced first and exclusively in procedural sections, creating friction for Linux users. No Linux-specific commands or guidance are given for equivalent operations, despite Service Fabric supporting Linux clusters.
Recommendations
  • Add equivalent Linux CLI commands (e.g., Azure CLI, Bash scripts, or Service Fabric CLI) for node management and scaling operations.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives where possible.
  • Reorder procedural sections to present cross-platform or Linux options alongside Windows/PowerShell examples.
  • Clarify whether PowerShell commands can be run on Linux (via PowerShell Core), and if so, provide guidance; otherwise, offer native Linux instructions.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 (such as Active Directory domain accounts, gMSA, BitLocker, and PowerShell disk encryption) are mentioned or linked, while Linux equivalents are either missing or referenced only as TODOs. Examples and instructions often default to Windows terminology and tools, with Linux guidance less prominent or absent.
Recommendations
  • Add explicit Linux examples and instructions for disk encryption (currently only PowerShell/BitLocker/Windows are mentioned, Linux is a TODO).
  • Ensure parity in describing how to run services under different accounts on Linux clusters, not just Windows (e.g., clarify Linux user/group management in manifests).
  • Include Linux-specific guidance for certificate management and container security (expand on how certificates are handled in Linux clusters).
  • Where Windows tools (e.g., PowerShell) are referenced, provide equivalent Linux commands (e.g., Bash, CLI) and link to relevant documentation.
  • Review all sections for Windows-first language and ensure Linux options are presented equally, not as afterthoughts or TODOs.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Advanced Application Upgrade Topics' in Azure Service Fabric heavily features PowerShell cmdlets for all procedural examples and upgrade operations. There are no CLI, Bash, or Linux-native tool examples provided, nor is it clarified whether these PowerShell commands are cross-platform or Windows-only. The documentation assumes PowerShell usage and does not mention or link to Linux/macOS equivalents or alternatives, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all upgrade operations alongside PowerShell examples, or clarify if PowerShell cmdlets are cross-platform.
  • Explicitly state which commands/tools are available on Linux/macOS and provide links to relevant documentation.
  • Include Bash or shell script examples where applicable, especially for ARM template deployments.
  • Mention any limitations or prerequisites for Linux/macOS users when using Service Fabric upgrade features.
  • Reorganize examples so that cross-platform tools (e.g., Azure CLI, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, upgrade tutorials are presented first for Visual Studio (a Windows-centric IDE) and PowerShell (primarily a Windows tool, though available on Linux). There is no mention of Linux-native tools or CLI-based upgrade workflows, nor are Linux/macOS-specific examples provided. The serialization discussion is focused on C# and .NET, but Service Fabric supports .NET Core, which is cross-platform.
Recommendations
  • Add explicit references and links to Linux/macOS upgrade workflows using Azure CLI or Service Fabric CLI (sfctl), if available.
  • Include examples or tutorials for upgrading applications on Linux/macOS environments.
  • Clarify that PowerShell is available cross-platform, but also mention native Linux tools where applicable.
  • Consider providing parity in example ordering (e.g., Visual Studio, then CLI, then PowerShell) to avoid Windows-first impression.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), and the prerequisite steps assume a Windows environment. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS as well.
Recommendations
  • Add equivalent Bash or Azure CLI examples for REST API calls (e.g., using curl or az rest).
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows, and provide alternatives for Linux/macOS users.
  • Include instructions for connecting to Service Fabric clusters from Linux/macOS (e.g., using certificate files and curl).
  • Present cross-platform examples side-by-side, or indicate which steps are Windows-specific.
  • Mention any limitations or differences for Linux/macOS users explicitly.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring move cost, but does not offer equivalent Linux/Unix shell or CLI examples. PowerShell is primarily a Windows tool, and its usage is presented before any mention of cross-platform alternatives. There are no Linux-specific instructions or examples for users managing Service Fabric clusters on Linux nodes.
Recommendations
  • Add Azure CLI or Bash examples for configuring move cost, especially for cluster operations that can be performed from Linux/macOS.
  • Clarify whether PowerShell commands are available cross-platform (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Include notes or links to Linux-specific documentation for Service Fabric cluster management.
  • Ensure that configuration file examples (ClusterManifest.xml, ClusterConfig.json) are accompanied by instructions relevant to Linux deployments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a notable bias toward Windows: PowerShell and Windows-specific tools are referenced more frequently and often before Linux equivalents. Some examples and links are Windows-focused, and Linux-specific guidance is less detailed or referenced later. Several sections (e.g., API access, DevOps, port usage) mention Windows tools or patterns first, and Linux examples are sometimes missing or less emphasized.
Recommendations
  • Ensure Linux CLI examples are provided alongside PowerShell examples, especially for cluster management and networking configuration.
  • When referencing tools (e.g., PowerShell), mention Linux equivalents (e.g., Azure CLI, Bash scripts) and provide links or examples.
  • Balance the order of Windows and Linux guidance so Linux is not always secondary.
  • Add Linux-specific ARM template samples or links where only Windows samples are given.
  • Clarify which features or steps are platform-agnostic and which are Windows-only, to help Linux users navigate the guidance.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows examples (PowerShell, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows-specific tools and extensions (e.g., Windows Defender, Azure DSC) are discussed without Linux equivalents or with notes stating Linux is not supported. PowerShell commands are used for Windows encryption, while Linux uses bash/openssl, but the Windows section is more prominent and detailed.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after or as an afterthought.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), briefly mention Linux alternatives or clarify if no equivalent exists.
  • Balance the detail and prominence of Windows and Linux instructions, especially in critical sections like certificate management and secret encryption.
  • Consider adding a summary table or section highlighting parity and differences between Windows and Linux security practices for Service Fabric.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, REST API). This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal).
  • Include REST API sample requests for relevant actions.
  • Clarify whether PowerShell cmdlets are available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any limitations or differences in managing Service Fabric clusters from Linux/macOS, if applicable.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides code examples for scaling Service Fabric services primarily in C# and PowerShell, with no equivalent Linux shell or CLI examples. PowerShell commands are referenced as the main administrative tooling, and Windows-specific implementation details (such as kernel driver logging) are discussed before Linux equivalents. While Linux is mentioned in the platform section, Linux users may find friction due to the lack of parity in examples and tooling guidance.
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell for administrative actions such as creating/updating services.
  • Explicitly mention Linux-compatible tools and workflows for managing Service Fabric clusters.
  • Clarify which PowerShell commands are available cross-platform (if any), or provide links to Linux-specific documentation.
  • Consider providing sample scripts or references for Linux users to perform equivalent tasks.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is given its own section and used for cluster upgrades, which are shown only with Windows-specific PowerShell commands. Windows registry keys and Windows Update settings are discussed without Linux equivalents. The upgrade section only provides Windows (MSI) instructions, omitting Linux (DEB) examples. Windows configuration is described in detail, while Linux-specific instructions are minimal or missing.
Recommendations
  • Add Linux-specific examples for cluster upgrades, including DEB package instructions and relevant shell commands.
  • Include Linux configuration details for VM scale sets, such as disabling automatic updates on Linux VMs.
  • Provide Bash or shell script equivalents for PowerShell commands where applicable.
  • Ensure that Linux and Windows examples are presented with equal prominence, ideally side-by-side.
  • Mention Linux registry/file configuration (if applicable) when discussing Windows registry keys.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users who typically use Bash or Azure CLI. There is no mention of Linux-specific tools or patterns, nor guidance for non-Windows environments.
Recommendations
  • Add Azure CLI or Bash examples for each placement policy configuration, where possible.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core) or if they are Windows-only.
  • Mention any Linux/macOS limitations or differences in Service Fabric management, if applicable.
  • Provide links or references to Linux/macOS documentation for Service Fabric management.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are shown after C# but before any mention of Linux tooling. There is no guidance for Linux users on how to perform these operations via Bash, Azure CLI, or REST API. The documentation mentions that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific instructions or examples.
Recommendations
  • Add Linux/Bash examples for configuring scaling policies, such as using Azure CLI or REST API.
  • Explicitly mention any limitations or differences for Linux clusters and provide guidance for Linux users.
  • Include instructions or references for Linux users to achieve the same tasks, especially for cluster management and service updates.
  • Consider providing sample scripts or commands for Linux environments alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only practical example for reporting and querying health uses PowerShell cmdlets. There are no Linux/macOS CLI or REST API examples, even though Service Fabric supports cross-platform management. This creates friction for non-Windows users, as they must infer how to perform equivalent actions.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API usage examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tooling and clarify which tools are available on each OS.
  • Ensure that PowerShell examples are accompanied by CLI or REST examples where possible.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but code samples for service creation and updates are given only in C# and PowerShell, with PowerShell being a Windows-centric tool. The XML configuration section is labeled <WindowsServer>, and PowerShell examples are shown before any Linux CLI or cross-platform alternatives (which are missing). There is no explicit mention of Linux-specific tools or patterns, and Linux/macOS users may need to adapt instructions for their environments.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for service creation and placement constraints, which are cross-platform.
  • Clarify that ClusterConfig.json is used for standalone deployments, including Linux clusters, and provide explicit Linux cluster configuration guidance.
  • Include references or links to Linux/macOS setup guides for Service Fabric clusters.
  • Where PowerShell is used, note Linux/macOS equivalents or alternatives.
  • Consider providing bash or shell script examples for relevant operations.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples primarily in C# and PowerShell, with PowerShell commands used for service creation and metric configuration. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. Additionally, PowerShell examples are presented before any mention of alternative tools, and there is no guidance for Linux/macOS users on how to perform these tasks.
Recommendations
  • Add equivalent Azure CLI or REST API examples for service creation and metric configuration.
  • Explicitly mention cross-platform tools and provide guidance for Linux/macOS users.
  • Where possible, include Bash scripting examples or reference documentation for non-Windows environments.
  • Clarify which tools are supported on which platforms, and link to relevant installation guides for PowerShell Core (if applicable) or Azure CLI.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# API examples are cross-platform, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or bash examples for managing node tags and service requirements, if supported.
  • Explicitly mention whether PowerShell commands are available on Linux/macOS (via PowerShell Core), and provide installation guidance if relevant.
  • If REST API endpoints exist for these operations, include sample curl or HTTP requests.
  • Clarify any limitations or differences for Linux-based Service Fabric clusters.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and there is no mention of cross-platform tools or instructions for Linux users. The C# API is platform-neutral, but operational scripting is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for configuring service sensitivity and maximum load, where possible.
  • Clarify whether PowerShell examples are usable on Linux/macOS (e.g., via PowerShell Core), or provide guidance for Linux users.
  • Explicitly mention any cross-platform alternatives or limitations for Linux/macOS users.
  • Consider including REST API examples if available, as these are platform-independent.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting Linux. Windows is mentioned first and exclusively in upgrade/configuration contexts.
Recommendations
  • Add links to Linux-specific upgrade and configuration documentation (e.g., 'service-fabric-cluster-upgrade-linux.md', if available).
  • Include examples or instructions for Linux clusters alongside Windows examples.
  • Mention Linux patch orchestration options or clarify if POA is Windows-only.
  • Ensure parity in guidance for customizing cluster settings and upgrades for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. No Linux equivalents, commands, or tools are mentioned, nor are Linux-specific instructions provided. This creates friction for Linux users who may be running standalone clusters outside of Windows environments.
Recommendations
  • Add Linux-specific instructions for scaling standalone clusters, including relevant commands and tools (e.g., using sfctl or REST APIs).
  • Provide examples for querying and updating cluster manifests on Linux, not just via PowerShell.
  • Clarify whether standalone cluster scaling is supported on Linux, and if so, link to Linux documentation or guides.
  • Ensure parity in guidance and examples for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page covers security scenarios for Azure Service Fabric clusters, including both Azure-hosted and standalone Windows clusters. However, it repeatedly references standalone clusters as 'Windows Server clusters' and provides links and examples only for Windows (e.g., 'Secure a standalone cluster on Windows by using X.509 certificates', 'Secure a standalone cluster on Windows by using Windows security'). There is no mention of standalone Linux clusters, nor guidance or links for securing Service Fabric clusters running on Linux outside Azure. Certificate creation instructions and recommendations are also Windows-centric (e.g., Windows Server certificate service, MakeCert.exe), with no Linux tooling or process described.
Recommendations
  • Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, if supported.
  • Provide links to Linux-specific documentation for certificate creation, installation, and cluster configuration.
  • Mention Linux certificate management tools (e.g., OpenSSL) and processes alongside Windows tools.
  • Clarify whether standalone Linux clusters are supported, and if not, state this clearly to avoid confusion.
  • Ensure parity in example coverage for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
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. It does not mention Linux equivalents or provide guidance for accessing Service Fabric events on Linux-based clusters, nor does it offer Linux-specific examples or monitoring patterns. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in logging channels, agents, or integration steps.
  • Provide examples or references for Linux-compatible monitoring tools and log aggregation methods (e.g., using Azure Monitor, Log Analytics, or other agents on Linux).
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are cross-platform and provide usage examples for Linux/macOS environments.
  • Explicitly state any limitations or differences for Linux clusters regarding event access and diagnostics.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance or parity. No Linux-centric workflow or example is provided for DNS service configuration or verification.
Recommendations
  • Add Azure CLI or Bash examples for configuring DNS names and services, especially for Linux clusters.
  • Include instructions for editing service manifests and deploying from Linux environments (e.g., using VS Code, nano, or other editors instead of Visual Studio).
  • Clarify Linux workflows for enabling DNS service, including any required steps or workarounds (such as using ARM templates or REST API).
  • Provide explicit guidance for verifying DNS configuration on Linux clusters, possibly using Linux-native tools (e.g., dig, nslookup).
  • Ensure Linux limitations are accompanied by actionable alternatives or links to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is evidence of Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows concepts (such as FabricHost.exe as a Windows service) are described in detail, while Linux-specific workflows and examples are less prominent or missing. Standalone cluster creation is only described for Windows, and Linux standalone clusters are noted as unsupported. CLI and REST API options are mentioned, but PowerShell is often listed first. There are few, if any, Linux-specific examples or guidance.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows examples, especially for cluster management and application lifecycle tasks.
  • Mention Linux tools (such as Bash, Linux CLI usage) before or alongside Windows tools like PowerShell.
  • Clarify which features are cross-platform and which are Windows-only, and provide links to Linux-specific documentation where available.
  • Add guidance for Linux users on cluster creation, management, and troubleshooting, even if standalone Linux clusters are not yet supported.
  • Ensure parity in example ordering (e.g., CLI before PowerShell, or both together) and tool recommendations.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and does not provide equivalent Linux/macOS paths or examples. The application package structure and manifest files are described generically, but the only explicit tooling and directory references are Windows-centric. There are no Linux/macOS-specific instructions, examples, or clarifications about cross-platform support. Visual Studio is mentioned as a packaging tool, but alternatives for Linux/macOS users are not discussed.
Recommendations
  • Add Linux/macOS equivalent file paths for schema definitions and clarify where these files are located on non-Windows systems.
  • Provide command-line examples for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) instead of or in addition to Visual Studio.
  • Mention or link to Linux/macOS-compatible tools and instructions for creating application and service manifests.
  • Clarify any platform-specific limitations or requirements for Service Fabric guest executables, including whether Linux clusters are supported and how packaging differs.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal instructions as the main 'Next steps'. While Service Fabric is cross-platform, the documentation does not provide Linux/macOS CLI or scripting alternatives (such as Bash or Azure CLI), nor does it mention Linux-specific workflows or tools. The focus on PowerShell and Visual Studio (which are Windows-centric) creates friction for Linux/macOS users.
Recommendations
  • Add examples and links for deploying and managing Service Fabric clusters using Azure CLI or Bash scripts, where possible.
  • Mention cross-platform tools and workflows explicitly, such as using REST APIs or .NET Core SDKs on Linux/macOS.
  • Provide parity in 'Next steps' by linking to Linux/macOS instructions or general (platform-agnostic) guides.
  • Clarify which steps or tools are Windows-only and offer alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but the practical examples and tooling references are heavily skewed toward Windows and PowerShell. The only CLI example given is PowerShell, and all links to command references are for PowerShell modules. There are no Linux/macOS CLI examples (e.g., Bash, Azure CLI), nor is it mentioned how to perform equivalent operations on Linux clusters. The C# example is cross-platform, but the operational guidance is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for creating services with ExclusiveProcess mode, especially for Linux clusters.
  • Mention or link to Linux/macOS-compatible tools or workflows for managing Service Fabric services.
  • Clarify if PowerShell examples are usable on Linux (via PowerShell Core), or provide alternative commands if not.
  • Balance example ordering so Linux/macOS users see relevant options alongside Windows users.
  • Add a note about platform support for Service Fabric management tools, specifying which tools are available on which OS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric container application manifest examples that are based on Windows Server 2016 Container Sample manifests. Windows-specific tools and patterns are referenced first or exclusively in several places, such as instructions to use 'winver' to get the OS build version and the use of Windows-style paths (e.g., 'c:\VolumeTest\Data'). There is some mention of Linux (e.g., certificates being exposed as PEM files), but Linux-specific examples, paths, or instructions are missing.
Recommendations
  • Provide equivalent Linux-based manifest examples or explicitly state Linux compatibility where applicable.
  • Include Linux-style paths (e.g., '/mnt/data') in volume mount examples alongside Windows paths.
  • When referencing OS build version detection, mention Linux equivalents (e.g., 'uname -r' or '/etc/os-release') in addition to 'winver'.
  • Clarify which features or manifest elements are cross-platform and which are Windows-only.
  • Link to or provide Linux container sample manifests if available.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core service communication in Azure Service Fabric. However, Windows-only tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, sometimes before their Linux equivalents. Windows-specific configuration steps and limitations are highlighted, and Windows terminology is used throughout. While Kestrel is recommended for Linux and cross-platform scenarios, the HTTP.sys sections and endpoint configuration guidance are Windows-centric and may create friction for Linux/macOS users.
Recommendations
  • Clearly separate Windows-only guidance (HTTP.sys, netsh, Windows HTTP Server API) from cross-platform guidance.
  • Add explicit notes or sections for Linux/macOS users, clarifying that Kestrel is the only supported web server and that HTTP.sys is not available.
  • Move Kestrel guidance and examples before HTTP.sys sections to emphasize cross-platform support.
  • Provide Linux/macOS-specific troubleshooting tips or configuration notes where relevant.
  • Ensure that all code samples and configuration steps are clearly labeled as Windows-only or cross-platform.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Replica Soft Delete in Service Fabric predominantly references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux-specific command-line equivalents, nor are cross-platform usage patterns or examples provided. The focus on PowerShell and Windows tools creates friction for Linux/macOS users, who may need to use FabricClient APIs or other methods not documented here.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Clarify whether the PowerShell APIs are available or supported on Linux/macOS, and if not, provide guidance for equivalent operations.
  • Include sample commands or code snippets for FabricClient usage in cross-platform languages (e.g., Python, Java, .NET Core).
  • Mention any limitations or differences in replica soft delete behavior on Linux clusters, if applicable.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell examples for health reporting, with no equivalent Linux/bash CLI examples. Windows/PowerShell commands are shown first and exclusively, while REST and API options are mentioned but not demonstrated with Linux-friendly tools. There is no mention of Linux Service Fabric CLI usage or cross-platform scripting, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Show bash or cross-platform scripting examples alongside PowerShell.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Mention and link to Linux-specific documentation or guidance for health reporting.
  • Ensure REST examples include curl or other Linux-friendly command-line usage.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation is heavily focused on Visual Studio workflows, which are Windows-centric. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), and PowerShell is mentioned as the CLI tool for service creation. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools (such as Azure CLI or other SDKs) referenced. The documentation assumes a Windows development environment and omits Linux/macOS parity.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), if supported.
  • Clarify whether StartupServices.xml is strictly a Windows/Visual Studio feature, and if so, mention alternatives for Linux/macOS users.
  • If PowerShell is referenced, also mention Bash or other shell equivalents for Linux/macOS.
  • Include a section outlining limitations or differences for non-Windows environments.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Windows-specific tools (Visual Studio and PowerShell) for upgrading Service Fabric applications. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS equivalents or cross-platform CLI tools. Linux users are not provided with alternative approaches or guidance, creating friction for non-Windows environments.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for Linux/macOS users, such as using Bash scripts or relevant CLI commands.
  • Clarify whether Visual Studio and PowerShell are required, or if alternative tools exist for non-Windows platforms.
  • Provide links to documentation for Linux/macOS workflows, if available.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_windows_arm_template
Summary
The documentation covers both Windows and Linux VMs, with parity in CLI and API instructions. However, PowerShell examples are provided alongside CLI, and ARM template examples are heavily Windows-centric (defaulting to Windows images and parameters). Windows-specific tools (PowerShell) are featured equally with cross-platform CLI, and ARM template parameters focus on Windows OS versions, with no Linux ARM template shown. Portal instructions are neutral. The CLI examples do use a Linux image (Ubuntu2204), but the ARM template is Windows-only.
Recommendations
  • Add ARM template examples for Linux VMs (e.g., Ubuntu, CentOS) alongside the Windows ARM template.
  • Clarify in the ARM template section that Linux images can be used, and provide parameter options for Linux OS.
  • Consider showing CLI examples for both Windows and Linux images, or explicitly state that the CLI works for both.
  • If PowerShell is shown, also mention Bash or other Linux-native scripting options where relevant.
  • Ensure that cross-platform tools (CLI, API, Portal) are always presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links (e.g., custom roles via PowerShell) appear first or are emphasized. The custom RBAC role section links only to a PowerShell-based guide, and the PowerShell module is mentioned alongside Azure CLI, but not after or equally. There are no explicit Linux-only examples or links, and the CLI link for private links is labeled 'linux', but the main guidance is not Linux-focused.
Recommendations
  • Add links to custom RBAC role creation using Azure CLI and/or Azure Portal, not just PowerShell.
  • Ensure Azure CLI examples are presented before or equally with PowerShell examples.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide explicit Linux/macOS guidance where relevant.
  • Where possible, provide portal-based instructions for users on any platform.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or instructions for VHD creation/conversion. Linux users are left without clear guidance for critical steps such as converting disk formats or creating VHDs, creating friction and potential blockers.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
  • Provide Linux CLI alternatives for disk conversion and VM preparation, not just referencing Hyper-V and PowerShell.
  • Mention and link to relevant Linux virtualization solutions (e.g., KVM, VirtualBox, QEMU) alongside Hyper-V.
  • Ensure that Linux steps are presented first or in parallel with Windows steps, given the Linux-focused topic.
  • Clarify that Hyper-V and PowerShell are optional and provide parity for Linux/macOS users.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most sections. However, there are several areas where Windows bias is evident: PowerShell examples and tools (e.g., Get-FileHash) are often shown first or exclusively, especially for checksum generation and generalization steps; Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail, and Windows-specific commands are presented before Linux equivalents. Linux examples are present but sometimes appear after Windows ones or lack equivalent detail. Some tool references (e.g., PowerShell for checksum) do not mention Linux alternatives alongside.
Recommendations
  • Ensure Linux (bash/terminal) examples are shown alongside or before Windows/PowerShell examples, especially for common tasks like checksum generation.
  • When referencing tools (e.g., Get-FileHash), always mention the Linux/macOS equivalent (e.g., sha256sum) in the same context.
  • Provide equal detail for Linux customizers and validation steps as for Windows (e.g., Shell customizer, Linux restart guidance).
  • Where Windows customizers are described (e.g., WindowsRestart), clarify Linux alternatives or explicitly state limitations.
  • Review ordering of examples and tool references to avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell cmdlets and patterns are heavily emphasized throughout, including frequent references to PowerShell-specific parameters and behaviors. PowerShell examples are often given equal or greater prominence than Azure CLI, despite the Linux focus. There are also multiple references to using PowerShell locally, which is a Windows-centric tool, and some instructions assume familiarity with PowerShell scripting conventions. Additionally, PowerShell is mentioned first in several sections, and some backup/restore instructions reference PowerShell cmdlets before CLI equivalents.
Recommendations
  • Prioritize Azure CLI examples and instructions before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Clarify that PowerShell can be run on Linux/macOS, but recommend Azure CLI as the default for Linux users.
  • Add explicit guidance for Linux users on installing and using Azure CLI, including troubleshooting for common Linux issues.
  • Where PowerShell-specific behaviors are discussed (e.g., sequence version handling), provide equivalent CLI notes or highlight CLI's advantages for Linux users.
  • Reduce reliance on PowerShell scripting conventions in example scripts; use CLI syntax and patterns where possible.
  • Ensure backup/restore instructions reference CLI and portal options before PowerShell.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and Bash scripting examples, but the AzCopy upload example is given only for Windows (using AzCopy.exe and a Windows file path). There is no explicit Linux/macOS AzCopy example, and the Windows-style example is shown first. The documentation mentions using 'wc' and 'ls' for file size, which are Linux commands, but does not provide a PowerShell equivalent for Windows users. Overall, the AzCopy upload step is Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Add a Linux/macOS AzCopy example (using './azcopy' and a Unix-style file path, e.g., '/home/user/mydisk.vhd').
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention that Bash scripts and Azure CLI commands work on both Linux and Windows, and provide PowerShell equivalents for file size calculation for Windows users.
  • Present both Windows and Linux/macOS examples side-by-side, or note differences where relevant.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
While the documentation is focused on Linux VMs, there is notable bias toward Windows tooling and PowerShell usage. PowerShell examples are provided extensively, sometimes before or instead of Azure CLI examples. Windows-specific tools and patterns (e.g., PowerShell cmdlets, SAS token generation via PowerShell, REST API examples using PowerShell scripts) are referenced frequently. There are missing or minimal Linux-native scripting examples (e.g., bash, shell scripting), and some sections use Windows terminology or tools first. REST API and ARM template examples often use PowerShell scripts (.ps1) as the default, rather than shell scripts (.sh).
Recommendations
  • Provide more bash/shell script examples alongside PowerShell, especially in REST API and ARM template sections.
  • Ensure Azure CLI examples are given equal prominence and detail as PowerShell examples.
  • When referencing SAS token generation or blob operations, include CLI or Linux-native methods (e.g., az storage blob generate-sas) in addition to PowerShell.
  • Use .sh scripts as the default in Linux-focused examples, or show both .ps1 and .sh variants.
  • Clarify when a tool or method is Windows-specific, and offer Linux alternatives where possible.
  • Review and adjust ordering so Linux-native tools and examples are presented first or equally.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation covers backup and disaster recovery for Azure unmanaged disks and is intended for both Linux and Windows VMs. However, there are several instances where Windows tools (e.g., PowerShell, Volume Shadow Service) are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some example links and instructions (e.g., incremental snapshots, SQL Server backup) point to Windows-specific pages or tools, and PowerShell is often listed as the primary scripting option, with less emphasis on Azure CLI or Linux-native tools. Application-consistent backup for Linux is referenced but not explained in detail. There are also references to Windows-specific backup mechanisms (e.g., VSS) without clear Linux alternatives.
Recommendations
  • Ensure Linux and Azure CLI examples are provided alongside PowerShell, especially in sections about scripting and automation.
  • When mentioning Windows tools (e.g., Volume Shadow Service), immediately provide Linux equivalents (e.g., fsfreeze, application-consistent backup for Linux) and link to relevant Linux documentation.
  • Balance references to Windows and Linux in tables and step-by-step instructions, avoiding Windows-first ordering.
  • Add explicit Linux examples for incremental snapshots and backup/restore workflows, including links to Linux-specific guides.
  • Clarify and expand on application-consistent backup for Linux, including how to achieve it and any limitations.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner for most subsystems. However, in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as the primary tooling for lifecycle management, without referencing equivalent Linux/macOS tools (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the Transport subsystem, but Linux equivalents are not discussed. These patterns indicate a mild Windows bias, primarily in tooling references.
Recommendations
  • Mention Azure CLI and REST API options for management tasks alongside PowerShell cmdlets.
  • Clarify that management operations can be performed from Linux/macOS using Azure CLI or SDKs.
  • In the Transport subsystem section, explain how security is handled on non-Windows platforms (e.g., X509 certificates, other mechanisms).
  • Ensure examples and tooling references are platform-neutral or provide parity for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation presents Windows/PowerShell examples first and in greater detail, such as referencing the New-ServiceFabricApplication PowerShell cmdlet and Visual Studio workflows before mentioning Linux-compatible tools like sfctl. While Linux tools are mentioned, the ordering and emphasis favor Windows environments.
Recommendations
  • Present Linux-compatible tools (e.g., sfctl, install.sh) before or alongside Windows/PowerShell examples.
  • Provide explicit Linux/macOS command-line examples for parameter passing and deployment.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Add guidance for Linux/macOS users on using parameter files and scripts outside Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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 is presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples (sfctl) are cross-platform, but the initial focus on PowerShell may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI coverage does allow non-Windows users to complete all tasks.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
  • Explicitly mention that all deployment and management tasks can be performed on Linux/macOS using sfctl.
  • Consider adding a short Bash example or note for Linux/macOS users to reinforce parity.
  • Add a table summarizing which tools are available on which platforms.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support for Service Fabric, and references development tools for each platform. However, Windows development (Visual Studio and PowerShell) is mentioned before Linux development (Eclipse and Yeoman), and the quickstart link points to a .NET (likely Windows-focused) guide. There are no Linux-specific examples or quickstart links provided, and Windows tools are referenced first.
Recommendations
  • Provide Linux/macOS quickstart links alongside the Windows/.NET quickstart.
  • Alternate the order of mentioning Windows and Linux development tools to avoid implicit prioritization.
  • Include explicit examples or walkthroughs for Linux development and deployment.
  • Clarify parity between Windows and Linux features, linking to documentation on differences.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized over CLI or Portal. However, the PowerShell example is included alongside CLI and REST, which are cross-platform, but PowerShell is primarily a Windows-centric tool. The CLI examples are shown before PowerShell, and there are no Windows-specific tools or patterns mentioned exclusively. There is minor bias in the inclusion of PowerShell, but Linux parity is maintained through CLI and REST examples.
Recommendations
  • Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for cross-platform usage.
  • Consider adding notes for macOS/Linux users about PowerShell Core compatibility if relevant.
  • Ensure that CLI examples are always presented before PowerShell to reinforce cross-platform parity.
  • Explicitly mention that Azure CLI and REST API are fully supported on Linux/macOS.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. While the content is largely platform-neutral, there are several subtle signs of Windows bias: Windows terminology (e.g., 'certificate store', 'MY', 'LocalMachine'), Windows-centric defaults (e.g., NTLM authentication, Windows Defender Firewall), and Windows-specific references (e.g., 'Windows Fabric Replicator', 'fabric.exe'). Windows tools and patterns (such as certificate store names and NTLM) are mentioned exclusively or before Linux equivalents. Linux-specific settings are present but less prominent and often appear as exceptions or afterthoughts.
Recommendations
  • Where certificate store names are referenced (e.g., 'MY', 'LocalMachine'), clarify Linux equivalents and provide explicit Linux guidance.
  • For NTLM authentication and Windows Defender Firewall, clearly state Linux alternatives or limitations.
  • When referencing Windows-specific tools (e.g., 'fabric.exe', 'Windows Fabric Replicator'), add Linux context or note if the feature is unavailable on Linux.
  • Ensure Linux-specific settings (such as X509Folder, LinuxExternalExecutablePath) are given equal prominence and explanation.
  • Review default values and descriptions to ensure Linux defaults are equally documented.
  • Consider adding a summary table or section highlighting platform differences for key settings.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias towards Windows, such as mentioning Windows container runtimes and IIS scenarios before Linux equivalents, and referencing Windows-specific tools and patterns (e.g., Mirantis Container Runtime, IIS lift-and-shift). Linux support is present and linked, but Windows examples and tools are sometimes presented first or in greater detail.
Recommendations
  • Ensure Linux examples and scenarios are presented with equal prominence and detail as Windows.
  • When listing container runtimes, mention Linux (Docker) first or equally alongside Windows options.
  • Add Linux-specific 'lift-and-shift' scenarios (e.g., Apache, NGINX) to balance the IIS example.
  • Where Windows tools are mentioned (e.g., Mirantis, IIS), include Linux equivalents or clarify their scope.
  • Review the order of quickstart/tutorial links to alternate Linux and Windows, or group them together.
GitHub Create Pull Request
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page provides Service Fabric application and service manifest examples, but it exhibits minor Windows bias. The only explicit cross-platform friction is the mention of 'ServiceFabric PowerShell module' for service creation, with no Linux CLI equivalent. Additionally, references to Windows-centric accounts (e.g., NetworkService, Administrators) are present, but these are intrinsic to Service Fabric's security model and not strictly Windows-only. No Linux-specific examples, tools, or patterns are provided, and Windows terminology appears first or exclusively in some sections.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) commands for service creation and management, especially for Linux users.
  • Clarify which security principal/account types are supported on Linux clusters (e.g., local user, group, etc.) and note any differences.
  • Where scripts are referenced (e.g., Setup.bat), provide examples or guidance for Linux shell scripts (e.g., Setup.sh) if supported.
  • Explicitly state any limitations or differences for Linux Service Fabric clusters, especially regarding user accounts, endpoints, and resource governance.
  • Consider including manifest snippets or examples that highlight Linux-specific deployment patterns if applicable.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides code examples and references exclusively in C#/.NET, which is cross-platform but historically associated with Windows. The 'Next steps' section lists Visual Studio and PowerShell upgrade tutorials, with Visual Studio (a Windows-centric IDE) mentioned before PowerShell. No Linux/macOS-specific tools, patterns, or examples are provided, but the content is not strictly Windows-only.
Recommendations
  • Add examples or guidance for using cross-platform .NET development tools (such as VS Code, CLI tools) on Linux/macOS.
  • Include references to Linux/macOS-compatible upgrade workflows (e.g., using Azure CLI or .NET CLI instead of PowerShell/Visual Studio).
  • Clarify that Service Fabric Reliable Collections and custom serialization are supported on Linux node types, if applicable.
  • Consider providing sample code or links for Linux/macOS environments where relevant.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on Windows Server and Linux, the documentation page only provides details and examples for Windows Server environments. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, and all security and scaling guidance is Windows-centric. No Linux-specific instructions, examples, or tools are mentioned.
Recommendations
  • Clarify in the introduction that standalone Service Fabric clusters are currently Windows-only, and Linux support is not yet available.
  • Remove or revise statements implying Linux parity if Linux is not supported.
  • When Linux support becomes available, add Linux-specific examples, instructions, and tools throughout the documentation.
  • Consider adding a section that describes the roadmap or status of Linux support for standalone clusters.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally platform-neutral, but there are some subtle Windows biases. Windows terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe', and code packages are described as containing 'EXE/DLL files'. While Linux is mentioned in the context of containers and guest executables, Windows-specific patterns and terminology are more prominent and appear first. However, Linux support is acknowledged and described in relevant places.
Recommendations
  • Clarify that the node startup process differs between Windows and Linux, and describe the Linux equivalent (e.g., systemd services or relevant Linux processes).
  • When describing code packages, mention Linux executable formats (e.g., ELF binaries) alongside EXE/DLL files.
  • Ensure examples and terminology are balanced, mentioning Linux and Windows equally, and avoid defaulting to Windows-first descriptions.
  • Add links or references to Linux-specific documentation or guides where appropriate.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VM between scale sets). However, PowerShell examples are always present and shown alongside CLI, which is cross-platform, but PowerShell is primarily used on Windows. Additionally, PowerShell examples are more verbose and detailed, sometimes including extra parameters (e.g., networking setup) not shown in CLI. The ordering of examples is mostly CLI first, then PowerShell, which is good, but the presence of PowerShell throughout may signal a slight Windows bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally good.
Recommendations
  • Ensure that all PowerShell examples are clearly marked as Windows-specific, since Azure PowerShell is primarily used on Windows.
  • Consider adding Bash shell script examples for Linux users, especially for more complex operations.
  • Where PowerShell examples include extra parameters (e.g., networking), ensure the CLI examples are equally detailed for parity.
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • If possible, provide links or references to Linux/macOS-specific guidance for Azure VM management.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell examples are always present and sometimes shown immediately after CLI, reinforcing Windows-centric tooling. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is not cross-platform by default in Azure context, so the documentation leans toward Windows users. However, Azure CLI is cross-platform and always included, mitigating the impact.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are for Windows PowerShell or PowerShell Core, and indicate their cross-platform support if relevant.
  • If possible, provide links or references to Azure CLI installation and usage on Linux/macOS.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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 presented before CLI examples, and some sections (e.g., querying public IPs) give more detailed PowerShell usage. Portal instructions are generic, but scripting examples sometimes favor PowerShell syntax and terminology, which is Windows-centric. However, Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or in the same order throughout the document to avoid implicit Windows-first bias.
  • Ensure CLI examples are as detailed as PowerShell examples, especially in sections like querying public IPs.
  • Explicitly note that Azure CLI is cross-platform and encourage its use for Linux/macOS users.
  • Where possible, add Bash script examples for common tasks to further support Linux users.
  • Review tabbed content to ensure CLI tabs are not consistently after PowerShell tabs.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples are shown before or with equal prominence to CLI. The Application Health extension examples use both 'ApplicationHealthLinux' and 'ApplicationHealthWindows', but PowerShell examples default to 'ApplicationHealthWindows', potentially confusing Linux users. Portal instructions are platform-neutral, but PowerShell is a Windows tool and its presence throughout the doc, with no explicit mention of Linux alternatives (e.g., Bash scripts), suggests a mild Windows bias.
Recommendations
  • Ensure that Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Clarify in PowerShell examples when 'ApplicationHealthWindows' should be used versus 'ApplicationHealthLinux', or provide both variants.
  • Add explicit notes that Azure CLI is recommended for Linux/macOS users.
  • Consider including Bash or shell script snippets for Linux users where relevant.
  • Where PowerShell is used, indicate its Windows-specific nature and suggest CLI for non-Windows users.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a balanced overview of migrating to Virtual Machine Scale Sets in Flexible orchestration, referencing both Windows and Linux scenarios. However, in the 'Create scalable network connectivity' section, Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers), which may subtly prioritize Windows use cases. All tooling examples (Azure CLI, PowerShell, ARM Template) are cross-platform, and no critical migration steps are Windows-only.
Recommendations
  • When listing common outbound connectivity scenarios, alternate the order or explicitly mention Linux scenarios alongside Windows ones (e.g., 'Windows updates and Linux package manager access').
  • Ensure that examples and troubleshooting links for Linux (e.g., Linux VM activation, package manager connectivity) are provided where relevant.
  • Consider adding explicit Linux-focused migration tips or links, especially for package manager connectivity and OS-specific considerations.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
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 Template. While the CLI example is cross-platform, the PowerShell example is Windows-centric and is presented immediately after the CLI example. There is no explicit Linux/macOS bias, but PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users. The CLI example is sufficient for Linux parity, but the ordering and prominence of PowerShell may suggest a Windows-first bias.
Recommendations
  • Clearly indicate that Azure CLI is the recommended cross-platform method for Linux/macOS users.
  • Consider placing the CLI example before the PowerShell example, or labeling PowerShell as Windows-specific.
  • Add a note clarifying that PowerShell examples are intended for Windows users, and that CLI works on all platforms.
  • Optionally, provide Bash script examples for Linux users if relevant.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is primarily a changelog/news summary for Azure Disk Storage features and enhancements. While most content is platform-neutral, there are a few instances where Windows-related links or terminology are presented before Linux equivalents, and references to Windows tools (e.g., Azure PowerShell) are made without equal mention of Linux alternatives. For example, in the 'Live Resize' feature, the link points to a Windows-specific article, and in disk conversion and expansion, Windows documentation is listed before Linux. The 'LastOwnershipUpdateTime' property mentions Azure PowerShell and Azure CLI, but only links to Windows documentation.
Recommendations
  • Ensure that links to Linux documentation are provided alongside Windows documentation, especially for features that are not Windows-specific.
  • When referencing tools, mention both Azure PowerShell and Azure CLI equally, and clarify their cross-platform availability.
  • Present Linux and Windows examples in parallel, or alternate their order to avoid implicit prioritization.
  • Where possible, include macOS guidance if relevant.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, in several sections, Windows/PowerShell examples are presented before or alongside Linux equivalents, and PowerShell usage is prominent. The REST and Azure CLI examples are platform-neutral, but PowerShell is given equal or greater prominence than Bash in some areas. The extension configuration examples use both ApplicationHealthLinux and ApplicationHealthWindows, maintaining parity, but the PowerShell example for installing the extension uses ApplicationHealthWindows by default, while the CLI example uses ApplicationHealthLinux.
Recommendations
  • Ensure Linux/Bash examples are always presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • In PowerShell examples, clarify when ApplicationHealthWindows should be used versus ApplicationHealthLinux, and provide parallel Linux-focused examples.
  • Where possible, add explicit Linux-centric troubleshooting steps and highlight cross-platform commands.
  • Review sample code and ensure variable names and extension types are not Windows-centric by default.
  • Consider adding a table or section summarizing parity between Windows and Linux for extension configuration and custom metrics.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence to the CLI example and is presented immediately after it. There is no explicit Linux/macOS bias, but the ordering and inclusion of PowerShell (a Windows-centric tool) alongside CLI may subtly favor Windows users. All examples use cross-platform tools (Azure CLI, ARM templates), but PowerShell is still primarily used on Windows. No Linux-specific commands, tools, or troubleshooting are provided.
Recommendations
  • Present Azure CLI examples first, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
  • Consider including Bash shell scripting examples for disk snapshot operations, especially for automation scenarios.
  • Add troubleshooting tips or notes for Linux/macOS users if there are known issues or differences.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS environments.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before CLI in several sections. References to role assignment and policy assignment also list PowerShell before CLI. However, Linux-specific links and CLI examples are present, and the documentation is not Windows-only.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS, and consider adding Bash shell examples where relevant.
  • Ensure parity in screenshots and UI descriptions for portal steps, noting any OS-specific differences.
  • Review linked articles to confirm Linux/macOS users are not directed to Windows-only instructions.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), Windows-centric tooling is highlighted separately. The ordering of example sections sometimes places PowerShell before ARM templates, and the PowerShell example uses Windows-style syntax. There are no missing Linux examples, but the documentation could better emphasize cross-platform CLI usage and clarify that PowerShell is primarily for Windows users.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider placing Azure CLI examples before PowerShell examples to reinforce CLI as the default for Linux/macOS.
  • Add clarifying statements in PowerShell sections that it is Windows-centric.
  • Ensure that all example scripts (especially in update sections) are available in CLI format and shown first.
  • Where possible, add bash shell script snippets for Linux users, or link to Linux-specific quickstart guides.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support before Linux, but provides parity in listing supported Linux distributions and requirements. No Windows-specific tools, examples, or patterns are favored. Both Windows and Linux are covered in the support matrix and limitations. The 'Next steps' section references CLI, Portal, and PowerShell, but does not prioritize Windows tools.
Recommendations
  • Consider listing Linux operating system support before or alongside Windows to avoid perceived prioritization.
  • Ensure that CLI and PowerShell guidance is equally accessible and that Linux-specific examples are included in linked pages.
  • Explicitly mention macOS where relevant, or clarify if only Linux and Windows are supported.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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, sometimes listing PowerShell examples before CLI or giving them equal prominence. There are no missing Linux examples, but the frequent inclusion of PowerShell commands (which are more commonly used on Windows) may create friction for Linux users, especially since Azure CLI is the more native tool for Linux environments. The documentation does not reference Windows tools or patterns exclusively, and all examples are applicable to Linux VMs.
Recommendations
  • Prioritize Azure CLI examples before Azure PowerShell in all sections, as CLI is the default for Linux users.
  • Consider marking PowerShell examples as 'optional' or 'for cross-platform users' to clarify their relevance.
  • Add brief notes explaining that Azure PowerShell can be used on Linux, but Azure CLI is recommended for native Linux workflows.
  • Where possible, include Bash shell script examples for common tasks (e.g., checking agent version, troubleshooting) to further support Linux users.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux, but includes PowerShell examples for deploying the extension and troubleshooting, even though PowerShell is primarily a Windows tool. The PowerShell example is presented before the Azure CLI example, which is more commonly used on Linux. However, all core instructions and examples are provided for Linux, and Linux-specific tools and commands are included throughout.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as CLI is the primary cross-platform tool for Linux users.
  • Clarify that PowerShell examples are optional and mainly for users who prefer PowerShell on Linux or are working in cross-platform environments.
  • Consider adding Bash script examples for deployment and troubleshooting, as Bash is native to Linux.
  • Explicitly state that Azure CLI is recommended for Linux users.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific guidance. However, there is evidence of Windows bias in the deployment and troubleshooting sections: PowerShell examples are presented before Azure CLI examples, and PowerShell is referenced as a primary tool for deployment and troubleshooting, despite Linux users typically preferring Azure CLI or shell scripting. There are also warnings and notes about PowerShell-specific issues, which may not be relevant for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux.
  • Clearly indicate which sections are relevant for Windows users and which are for Linux users, especially in troubleshooting.
  • Add Bash shell scripting examples for deployment and troubleshooting, or clarify that Azure CLI commands are cross-platform.
  • Reduce PowerShell-specific warnings or move them to a dedicated Windows section.
  • Ensure all example commands use Linux-appropriate syntax (e.g., avoid PowerShell backticks in Azure CLI examples).
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes a PowerShell example for marking the VM as generalized, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, but the PowerShell example is not matched with an Azure CLI equivalent for Windows. The Linux section is comprehensive and includes links to distro-specific guides, but the Windows section could benefit from parity in Azure CLI usage.
Recommendations
  • Add Azure CLI examples for Windows VM generalization alongside the PowerShell example, so Windows users can use either tool.
  • Ensure that both Linux and Windows sections provide equivalent steps for marking the VM as generalized, using both Azure CLI and PowerShell where appropriate.
  • Consider listing both Linux and Windows examples in parallel or in a table for easier comparison.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 improvements and references Windows documentation before Linux-specific details, which may create a minor perception of Windows bias. All configuration examples, commands, and tools are Linux-centric, with only a single PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure ARM templates, not VM configuration). No critical Linux examples are missing, and Linux tools are prioritized throughout.
Recommendations
  • Move Windows Server 2016 discussion and references to a background or context section, or clarify that it's for Azure host infrastructure only.
  • Add a brief summary at the start emphasizing that the guide is Linux-focused and all examples are for Linux VMs.
  • Replace the PowerShell base64 example with a Linux equivalent (e.g., 'base64 cloud-config.txt') or provide both Windows and Linux options.
  • Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' section.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but in several places Windows terminology, tools, and examples are presented first or more prominently. PowerShell examples are included alongside CLI and REST, but Windows-specific terms (e.g., Sysprep) are mentioned before Linux equivalents. The PowerShell section uses Windows as the default in its example, while the CLI section uses Linux. Overall, Linux parity is good, but Windows is sometimes prioritized in ordering and example selection.
Recommendations
  • Alternate the order of Windows and Linux examples to avoid implicit prioritization.
  • In PowerShell sections, provide Linux examples as the default or alongside Windows examples.
  • Ensure that both Linux and Windows terminology are introduced together, e.g., mention 'waagent -deprovision' and 'Sysprep' in the same sentence.
  • Review example ordering to avoid always showing Windows first.
  • Add explicit notes clarifying parity between Linux and Windows where applicable.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and provides Linux-centric instructions and examples. However, there are minor instances of Windows bias: PowerShell is mentioned alongside Azure CLI as a management tool, and PowerShell examples/scripts are referenced in the 'Next steps' section before or alongside Linux CLI equivalents. The 'Terminology' table includes 'PowerShell cmdlets' as a term, even though the primary audience is Linux users.
Recommendations
  • In the 'Terminology' section, clarify that PowerShell can be used cross-platform, or consider omitting it if not directly relevant to Linux VM management.
  • In the 'Next steps' section, list Azure CLI quickstart and scripts before PowerShell equivalents to prioritize Linux-native tools.
  • Where PowerShell is referenced, explicitly note its cross-platform support or provide context for Linux users who may prefer CLI/bash.
  • Ensure that all examples and scripts for Linux VM management are available in bash/CLI, and PowerShell is presented as an optional alternative.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers preparation of Red Hat Enterprise Linux VHDs for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, Windows tools and patterns (Hyper-V Manager, Windows-centric terminology) are presented first in each major section and tab, and instructions for using Hyper-V Manager are often more detailed and prominent. Linux-native hypervisors (KVM, VMware on Linux, Kickstart) are covered thoroughly, but their sections appear after Hyper-V and are sometimes referenced as secondary. There are no missing Linux examples or PowerShell-heavy instructions; all critical steps are provided for Linux users.
Recommendations
  • Reorder sections so Linux-native hypervisors (KVM, VMware on Linux, Kickstart) are presented before or alongside Hyper-V instructions, rather than after.
  • Add a brief summary or table at the top outlining parity and equivalence between Windows and Linux workflows.
  • Clarify that all workflows are equally supported and that Hyper-V is not required for Linux VHD creation.
  • Where possible, avoid referencing Windows tools (Hyper-V Manager) as the default or primary method.
  • Ensure that Linux-native terminology is used consistently and that Linux instructions are not dependent on Windows tools.
GitHub Create Pull Request
Virtual Machines Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines ...ion/migrate-from-elastic-compute-cloud-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides migration guidance from Amazon EC2 to Azure Virtual Machines and covers both Windows and Linux workloads in a generic manner. However, in sections discussing image generalization and agent installation, Windows-specific instructions (Sysprep) are mentioned first, while Linux instructions (waagent) are secondary. There are no explicit Linux command-line examples or Linux-specific migration tooling details, and some steps (such as image customization) could benefit from more Linux-focused guidance. The bias is minor and does not prevent Linux users from completing the migration, but it creates slight friction due to lack of parity in examples and ordering.
Recommendations
  • Provide Linux-specific migration examples and command-line instructions (e.g., using Azure CLI, shell scripts, or Linux tools) alongside Windows/PowerShell equivalents.
  • Ensure Linux agent installation and image generalization steps are described with equal prominence and detail as Windows Sysprep.
  • Include references to Linux migration tooling (such as cloud-init, waagent configuration, or Linux image builder pipelines) where relevant.
  • Where possible, show Linux examples first or in parallel with Windows examples to reinforce parity.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. The CLI example is cross-platform, but there is no explicit mention that PowerShell is Windows-centric or that the CLI is preferred for Linux/macOS users. The ordering of examples is neutral, but the inclusion of PowerShell without clarifying its platform limitations may cause confusion for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider placing the Azure CLI example first, or labeling it as the default for Linux/macOS.
  • Add a note clarifying PowerShell's platform support and limitations.
  • Ensure that all critical tasks can be completed using Azure CLI, and highlight CLI as the preferred method for non-Windows environments.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation covers both Windows and Linux VM images, but there are several instances where Windows/PowerShell examples, links, and terminology are presented before or more prominently than their Linux/CLI equivalents. PowerShell examples are given equal prominence to Azure CLI, but Windows terminology and links (e.g., Sysprep, Windows upload VHD, specialized image creation) are sometimes referenced first. However, Linux-specific information (waagent, Linux upload VHD) is included and the overall guidance is cross-platform.
Recommendations
  • Ensure that Linux/CLI examples and links are presented alongside or before Windows/PowerShell equivalents, especially in sections where both are relevant.
  • Where possible, use neutral language (e.g., 'Azure CLI' instead of 'PowerShell') as the primary example, or provide both examples in parallel.
  • Review links and references to ensure Linux documentation is as discoverable as Windows documentation (e.g., specialized image creation links for Linux).
  • Explicitly state parity in supported features and tools for both Windows and Linux, especially in FAQ and troubleshooting sections.
GitHub Create Pull Request