← Back to Dashboard
231
Pages Scanned
79
Pages Flagged
231
Changed Pages
34.2%
% Pages Flagged

Scan Information

Started At: 2026-01-31 00:00:10

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 231

Files Completed: 231

Problematic Pages

79 issues found
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation and feature list are exclusively focused on Windows Server. All supported operating systems listed are Windows-only, and security sections reference Windows-specific tools (Active Directory, Kerberos, group Managed Service Accounts) without Linux equivalents or guidance. No Linux examples, instructions, or supported OS versions are provided.
Recommendations
  • Clarify in the introduction that Linux support is not available for standalone clusters, or update the documentation to include Linux instructions and supported OS versions if/when Linux support is added.
  • If Linux support is planned, provide equivalent security guidance for Linux clusters (e.g., certificate management, authentication options, Linux user/service accounts).
  • Explicitly state the current Windows-only limitation in the 'Supported operating systems' section to avoid confusion.
  • Remove or update the description to accurately reflect the current platform support.
GitHub Create Pull Request
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 page for Azure Service Fabric reverse proxy is Windows-focused, as the reverse proxy feature is explicitly stated to be unavailable for Linux clusters. All examples, configuration details, and usage scenarios assume a Windows environment, with no Linux equivalents or alternatives provided. This creates a notable barrier for Linux users, who cannot use the reverse proxy feature at all.
Recommendations
  • Clearly state at the top of the documentation that reverse proxy is not available for Linux clusters, and provide guidance or links to alternative service discovery and communication patterns for Linux-based Service Fabric clusters.
  • If possible, mention any roadmap or workarounds for Linux users, or direct them to relevant documentation for Linux-compatible approaches.
  • Consider adding a comparison table or section outlining feature parity between Windows and Linux clusters for Service Fabric, so users can quickly assess platform limitations.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High 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 page focuses exclusively on configuring Service Fabric application upgrades using Visual Studio and PowerShell, both of which are Windows-centric tools. All examples and instructions assume use of Visual Studio (Windows-only) and PowerShell (primarily Windows, though available on Linux with limitations). There is no mention of Linux/macOS workflows, CLI alternatives, or cross-platform tools for upgrading Service Fabric applications.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Clarify whether Service Fabric application upgrades can be performed from Linux/macOS environments and, if so, provide relevant guidance.
  • If Visual Studio and PowerShell are required, explicitly state that these instructions are Windows-specific and link to any available cross-platform alternatives.
  • Include a section or links for Linux/macOS users on how to perform equivalent upgrade operations.
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
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation generally covers both Windows and Linux Service Fabric clusters, but there is a noticeable Windows bias in several areas. Windows/PowerShell tools and terminology are mentioned first or exclusively in some sections (e.g., Client API described as 'used by PowerShell', DevOps section references classic PowerShell tasks, and ARM template example is for Windows). Some operational examples and references (such as netsh commands, Patch Orchestration Application, and Windows container specifics) focus on Windows, with Linux equivalents either missing or less detailed. Linux-specific guidance is present but often secondary.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell commands where relevant, especially for networking and cluster management tasks.
  • Include ARM template samples for Linux clusters, or clarify differences in NSG setup for Linux clusters.
  • In sections referencing Windows tools (e.g., netsh, Patch Orchestration Application), add Linux equivalents or note if not applicable.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention both in parallel when describing features or requirements).
  • Clarify which recommendations or rules are Windows-only and which apply to Linux, to reduce ambiguity.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for on-demand backup in Azure Service Fabric demonstrates a notable Windows bias. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no CLI, Bash, or Linux-native examples provided, nor is there guidance for running these operations from Linux/macOS environments. The documentation assumes the use of Windows tools and patterns throughout, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or REST API calls with curl for Linux/macOS users.
  • Clarify whether the PowerShell module is required for all platforms, and if so, provide installation instructions for PowerShell Core on Linux/macOS.
  • Add notes or sections explicitly addressing how to perform these operations from non-Windows environments.
  • Where possible, show REST API usage with generic tools (e.g., curl, httpie) rather than only PowerShell's Invoke-WebRequest.
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 both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric formats and tools (XML manifests, PowerShell) are consistently presented first and in greater detail, with PowerShell being the only CLI example shown. There are no Linux shell or CLI examples, and the use of 'WindowsServer' in XML examples may cause confusion for Linux cluster operators.
Recommendations
  • Provide explicit Linux/Unix parity by including bash/CLI examples (e.g., using sfctl or REST API) alongside PowerShell for service creation and updates.
  • Clarify that ClusterConfig.json applies to both Windows and Linux standalone clusters, and provide examples or notes for Linux-specific scenarios if any differences exist.
  • When showing XML configuration, clarify if/when it is Windows-only, and provide equivalent Linux configuration steps if available.
  • Alternate the order of examples or explicitly state cross-platform applicability to avoid the impression that Windows is the default or only supported platform.
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 Service Fabric application upgrades is heavily focused on PowerShell-based workflows and examples, which are most relevant to Windows environments. All command-line examples use PowerShell cmdlets, and there is no mention of Linux CLI equivalents (such as Azure CLI, REST API, or Service Fabric CLI). The documentation assumes the reader is using Windows tooling, creating friction for Linux/macOS users who may need to perform similar upgrade operations.
Recommendations
  • Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for common upgrade operations, especially for creating/updating services and managing upgrades.
  • Clearly indicate which commands are Windows-only and provide guidance for Linux/macOS users on alternative workflows.
  • Include links to cross-platform tooling documentation (e.g., sfctl, Azure CLI) in relevant sections.
  • Reorder or balance examples so that Windows and Linux workflows are presented with equal prominence.
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 ⚠️ missing_linux_example
Summary
The documentation provides a detailed conceptual overview of Cluster Resource Manager integration with Service Fabric cluster management. However, the only command-line example shown uses PowerShell (Get-ServiceFabricPartitionHealth), with no equivalent CLI or Linux/macOS example provided. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that the PowerShell example is for Windows, and provide alternative commands for Linux/macOS users.
  • Add a short section or note clarifying cross-platform management options for Service Fabric clusters.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation demonstrates several Windows biases: PowerShell is the only CLI example given for setting DNS names, and there are no Linux CLI (e.g., Bash, Azure CLI) equivalents. The ApplicationManifest.xml example implicitly assumes Visual Studio, a Windows-centric tool, and does not mention Linux development workflows. The limitations section notes Linux support is restricted, but the documentation does not provide Linux-specific guidance or parity for key tasks such as enabling DNS service or setting DNS names outside ARM templates. Windows tools and patterns are mentioned first or exclusively in several sections.
Recommendations
  • Add Linux CLI examples (e.g., Bash, Azure CLI, REST API) for tasks such as setting DNS names and enabling DNS service.
  • Clarify how Linux users can set DNS names for services, especially for non-containerized workloads (if/when supported).
  • Provide guidance for Linux development workflows, including alternatives to Visual Studio and ApplicationManifest.xml editing on Linux.
  • Explicitly state limitations for Linux and offer workarounds or links to Linux-specific documentation where possible.
  • Balance example ordering so that Linux and Windows approaches are presented equally.
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 in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line/script examples are exclusively in PowerShell, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). The documentation also presents PowerShell examples before mentioning Linux support, and does not clarify how Linux users should perform these tasks, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API for configuring auto scaling policies, especially for Linux/macOS users.
  • Explicitly state which steps or tools are Windows-only and provide alternative instructions for Linux environments.
  • Reorder examples or provide parallel Windows and Linux instructions to avoid Windows-first bias.
  • Clarify if PowerShell Core (cross-platform) is supported, and if so, provide usage notes.
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 shows a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tooling. There are no examples or instructions for Linux environments, and the linked 'scale a standalone cluster' page is Windows Server-specific, further reinforcing the bias.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management tasks.
  • Clarify whether standalone clusters can be managed on Linux, and if so, provide guidance for Linux users.
  • Where PowerShell cmdlets are referenced, include alternative commands for Linux/macOS environments.
  • Explicitly state any platform limitations if standalone clusters are Windows-only, to avoid confusion.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI (sfctl) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. Additionally, the documentation references administrative actions primarily via PowerShell before mentioning programmatic APIs, reinforcing a Windows-first approach.
Recommendations
  • Add Linux CLI (sfctl) or bash examples alongside PowerShell for all administrative actions, such as creating or updating services.
  • Explicitly mention cross-platform management tools (e.g., sfctl, REST API) and provide usage examples.
  • Where PowerShell is referenced, clarify its platform limitations and direct Linux/macOS users to alternative tools.
  • Ensure that code samples and instructions are presented in a platform-neutral order, or grouped by platform.
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
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 Service Fabric reliable services app manifest examples demonstrates a moderate Windows bias. Examples reference Windows tools and patterns (such as .bat scripts, EXE programs, and Windows account types like NetworkService and Administrators), and mention PowerShell as a way to create service instances. There are no explicit Linux equivalents or examples (e.g., shell scripts, Linux user/group patterns, or Linux-specific deployment notes), and Windows terminology appears first and exclusively throughout the manifest examples.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and referencing ELF binaries instead of only .exe files.
  • Document Linux-compatible account types and group patterns, clarifying how principals map to Linux environments (e.g., using 'root', 'nobody', or custom service users).
  • Include notes or sections on deploying Service Fabric applications on Linux clusters, highlighting any differences in manifest configuration, resource governance, or security policies.
  • When mentioning tools (e.g., PowerShell), also reference Linux alternatives (such as Azure CLI or Bash scripts) for creating service instances.
  • Clarify which features or manifest elements are cross-platform and which are Windows-only, to help users understand applicability.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module), but does not mention or provide examples for Linux/macOS command-line tools or scripting environments. PowerShell is highlighted as the only CLI example, which is Windows-centric, and there are no references to Bash, CLI, or cross-platform alternatives.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API calls.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions if so.
  • If the Fault Analysis Service can be accessed via REST APIs, include sample curl commands or links to API documentation.
  • Explicitly state platform requirements and limitations for each usage method.
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 ⚠️ missing_linux_example
Summary
The documentation provides extensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, it gives detailed HTTP.sys examples and configuration steps (including references to Windows-only tools like netsh and Windows HTTP Server API) before clarifying that HTTP.sys is Windows-only. There are no explicit Linux/macOS development or deployment examples, and Windows-specific configuration steps (such as endpoint reservation) are described in detail, while Linux equivalents or considerations are omitted.
Recommendations
  • Add explicit Linux/macOS development and deployment examples, especially for Kestrel, to demonstrate parity and clarify platform-specific steps.
  • Clearly mark Windows-only sections (e.g., HTTP.sys) at the beginning, and provide alternative instructions for Linux users where applicable.
  • Include troubleshooting notes or configuration guidance for running Service Fabric Reliable Services with ASP.NET Core on Linux clusters.
  • Provide links or references to Service Fabric Linux documentation, and clarify any differences in endpoint configuration or port management on Linux.
  • When listing options, mention cross-platform (Kestrel) first, and make Windows-only options secondary.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. While it discusses Service Fabric's cross-platform certificate-based authentication, it consistently references Windows-specific tools, APIs, and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI1/CNG providers, and Windows event logs) before or instead of Linux equivalents. Troubleshooting and configuration examples focus on Windows, with only brief or parenthetical mentions of Linux paths. There are no explicit Linux/macOS command-line examples or troubleshooting steps.
Recommendations
  • Add explicit Linux/macOS examples for certificate storage, retrieval, and troubleshooting (e.g., show how to locate certificates in /var/lib/sfcerts, use OpenSSL or Linux-native tools for diagnostics).
  • When referencing certificate stores, always mention both Windows and Linux equivalents side-by-side, not just as a parenthetical note.
  • Provide Linux/macOS-specific troubleshooting steps, such as relevant log file locations, commands to check certificate permissions, and how to manage private keys.
  • If referencing Windows APIs (e.g., CertGetCertificateChain), clarify the Linux equivalent or note if the behavior is abstracted in Service Fabric.
  • Include examples of how to create or rotate certificates using cross-platform tools (e.g., OpenSSL) rather than only referencing Windows certificate providers.
  • Mention any platform-specific limitations or differences explicitly, so Linux/macOS users are aware of what applies to them.
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-based examples and references to Windows-specific tooling (such as the Key Vault VM extension for Windows and S-channel APIs). While the overall guidance is Azure-centric and Service Fabric clusters can run on both Windows and Linux, the hands-on examples, troubleshooting scripts, and extension documentation are almost exclusively Windows-focused. There is little to no mention of Linux equivalents, and Windows patterns/tools are presented first and in detail.
Recommendations
  • Add Linux-specific examples for certificate provisioning and management, such as using Azure CLI, Bash scripts, or Linux-compatible VM extensions.
  • Explicitly document any differences or limitations for Service Fabric clusters running on Linux nodes, especially regarding certificate autorollover and VM extensions.
  • Reference or link to Key Vault VM extension documentation for Linux, if available, and clarify any platform-specific behaviors (e.g., linking on renewal is Windows-only).
  • Provide troubleshooting steps and automation scripts using cross-platform tools (Azure CLI, REST API) alongside PowerShell.
  • Indicate clearly when a feature or example is Windows-only, and suggest Linux alternatives where possible.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only command for bypassing Infrastructure Service throttling, with no equivalent example for Linux/macOS users. The use of PowerShell and Service Fabric Explorer (a Windows-centric tool) is presented without alternatives or parity for Linux environments, which may create friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Provide equivalent command-line instructions for Linux/macOS users, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where possible.
  • Clarify whether the PowerShell command can be run from Azure Cloud Shell (which supports PowerShell and Bash) or if there are REST API alternatives.
  • Mention if Service Fabric Explorer is accessible via browser and platform-agnostic, or suggest alternatives for Linux users.
  • Add notes or links to cross-platform management tools for Service Fabric clusters.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides examples and guidance that prioritize Azure PowerShell for cluster management tasks, with explicit links to PowerShell cmdlets for deleting, restarting, and reimaging node types. While Azure CLI and sfctl are mentioned in the utility table, the best practices section exclusively highlights PowerShell examples and does not provide equivalent Azure CLI or sfctl command examples, which are more commonly used on Linux/macOS. This creates friction for non-Windows users who may not use PowerShell.
Recommendations
  • Include Azure CLI and sfctl command examples alongside PowerShell in the best practices section for all major operations (delete, restart, reimage).
  • Clarify that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, sfctl) are presented before or alongside PowerShell, rather than PowerShell-only examples.
  • Add explicit guidance for Linux/macOS users on how to perform these tasks without PowerShell.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on custom Windows images, presenting PowerShell commands for role assignment, and referencing Windows/PowerShell resources before Linux equivalents. While it mentions Linux custom images and provides a link to Linux instructions, all concrete examples and command-line instructions are Windows-centric. No Linux CLI or shell examples are provided for key steps like role assignment.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations alongside PowerShell commands.
  • Include explicit Linux-focused examples for deploying custom images, not just links to external Linux documentation.
  • Clarify which steps are OS-agnostic and which are Windows-specific, to help Linux/macOS users navigate the process.
  • Ensure that references to Windows and Linux documentation are balanced and presented together when relevant.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no equivalent examples for Bash, Azure CLI, or other Linux/macOS-friendly tools. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer using Azure CLI.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly mention that PowerShell examples can be run cross-platform using PowerShell Core, or provide guidance for Linux/macOS users.
  • Where possible, provide Bash scripting examples for ARM template deployments, or reference Azure CLI documentation for template deployment.
  • Clarify in each section that the ARM template approach is platform-agnostic and can be used from any OS.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric demonstrates a notable Windows bias. All examples use Windows containers (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows command syntax (cmd, echo, type, ping). There is no mention of Linux containers, Linux file paths, or Linux shell commands. The example explicitly references Windows container compatibility and assumes familiarity with Windows container development, with no Linux equivalent provided.
Recommendations
  • Add parallel examples using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images) to demonstrate Initializer CodePackages for Linux workloads.
  • Show Linux file path conventions (e.g., /workspace/log.txt) and Linux shell commands (e.g., bash, echo, cat, sleep) in the example manifests.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples for Linux users.
  • If there are limitations or differences for Linux containers, explicitly document them to help users understand platform parity.
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 clusters for Azure Service Fabric monitoring, but there are several instances where Windows tools (such as Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, and Linux equivalents are referenced later or require additional navigation. Some example/tutorial links are Windows/.NET-focused, and Linux-specific configuration is often described in less detail or deferred to other pages. PowerShell is referenced as an automation option, but Linux CLI or shell alternatives are not explicitly highlighted.
Recommendations
  • Ensure that Linux monitoring tools and workflows (such as Syslog, LTTng, Linux-specific agents) are described with equal prominence and detail as Windows tools.
  • Provide Linux-specific examples and step-by-step guides alongside Windows/PowerShell examples, especially for cluster monitoring and event collection.
  • When referencing automation, mention Linux CLI/bash alternatives in addition to PowerShell.
  • In tutorial links, offer parity for Linux (e.g., a tutorial for monitoring .NET Core apps on Linux clusters, not just .NET Framework/.NET on Windows).
  • Where Windows tools are mentioned (Event Viewer, Diagnostics Agent), immediately follow with Linux equivalents and configuration steps.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as primary management tools for Service Fabric, without mentioning Linux equivalents (such as CLI or REST API usage). The transport subsystem notes security via 'Windows security' alongside X509 certificates, but does not clarify Linux support or alternatives. No explicit Linux management examples or parity are provided.
Recommendations
  • Add references to Linux-compatible management tools, such as Azure CLI or REST APIs, for cluster and application lifecycle operations.
  • Clarify whether PowerShell cmdlets are cross-platform or provide Linux-specific instructions/examples where appropriate.
  • Expand on security mechanisms in the transport subsystem to specify how Linux nodes authenticate and communicate (e.g., clarify X509 certificate usage for Linux).
  • Ensure examples and tooling references include both Windows and Linux options, or note platform limitations explicitly.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of equivalent Azure CLI commands or Linux/macOS workflows. While az resource is mentioned once, the majority of examples and guidance are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples for all management operations (e.g., creating/deleting applications, services, and application type versions).
  • Clearly indicate when both PowerShell and Azure CLI can be used, and provide syntax for both where possible.
  • Add notes or links for Linux/macOS users on how to perform these operations using the Azure CLI.
  • Review the use of 'Az PowerShell cmdlet' as the default recommendation and balance with CLI alternatives.
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 ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809), Windows-specific commands (cmd, set, exit), and reference Windows-only container compatibility. Query instructions are provided only for PowerShell and C#, with no mention of Linux CLI or cross-platform alternatives. There are no Linux container examples, nor guidance for Linux-based Service Fabric clusters.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and Service Fabric clusters running on Linux.
  • Provide instructions for querying deployment status using Linux tools (e.g., Service Fabric CLI, sfctl) or REST API.
  • Present examples for both Windows and Linux platforms, or explicitly state platform limitations if Windows-only.
  • If RunToCompletion is Windows-only, add a clear note at the top to inform Linux users.
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 as primary examples for operational tasks (deploy, upgrade, remove, cleanup). While REST API and .NET SDK methods are mentioned, PowerShell is given equal or greater prominence, and there is little to no mention of Linux/macOS-specific CLI tools (such as sfctl) or shell scripting examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native CLI tools.
Recommendations
  • Add Linux/macOS-friendly examples using sfctl and Azure CLI for all operational tasks (deploy, upgrade, remove, cleanup).
  • Explicitly mention cross-platform alternatives wherever PowerShell cmdlets are referenced.
  • Reorder examples so that REST API, sfctl, and Azure CLI are presented before or alongside PowerShell, to avoid Windows-first bias.
  • Provide sample shell scripts or command lines for common lifecycle operations on Linux/macOS.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates moderate Windows bias. It references Visual Studio and PowerShell as primary upgrade tools in the 'Next steps' section, both of which are traditionally Windows-centric. No Linux/macOS equivalents (such as CLI or cross-platform IDEs) are mentioned, and Windows tools are listed before alternatives. The content focuses on C# and .NET serialization, which are cross-platform, but the upgrade guidance is Windows-oriented.
Recommendations
  • Include instructions or links for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Mention cross-platform IDEs (such as VS Code) or provide guidance for non-Visual Studio users.
  • Add explicit notes or sections for Linux/macOS users, clarifying supported upgrade workflows and tools.
  • Ensure that PowerShell examples are supplemented with CLI or bash equivalents where possible.
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 page generally covers Service Fabric application security in a cross-platform manner, but there are several sections where Windows-specific patterns, tools, or examples are mentioned first or exclusively. For example, running services under Active Directory domain accounts and group managed service accounts (gMSA) is described only for Windows clusters, with no Linux equivalents or alternatives suggested. Disk encryption is referenced with a link to a PowerShell-based Windows guide, while Linux disk encryption is only mentioned as a TODO. Some examples and terminology (e.g., NetworkService, BitLocker) are Windows-centric, and Linux-specific security practices are not equally represented.
Recommendations
  • Add Linux-specific examples and instructions where Windows-only features are described (e.g., disk encryption, service accounts).
  • Where features are Windows-only (e.g., AD DS integration, gMSA), explicitly state that Linux alternatives are not available, and suggest best practices for Linux clusters.
  • Ensure that cross-platform features (such as certificate management, container security, and API gateway usage) include both Windows and Linux usage patterns and examples.
  • Update TODOs (such as 'Encrypt disks on Linux clusters?') with actual guidance or links to relevant documentation.
  • Where possible, provide Linux-first or side-by-side examples to improve parity and reduce friction for non-Windows users.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page on Service Fabric application upgrade parameters demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are presented first and in greater detail, with explicit parameter tables and examples. SFCTL (cross-platform CLI, especially for Linux) is covered later and with less depth. There are no explicit Linux/macOS command examples or screenshots, and the parameter tables for PowerShell/Visual Studio are more extensive and detailed than those for SFCTL. The 'Next steps' section lists Windows upgrade tutorials before Linux equivalents.
Recommendations
  • Present SFCTL (Service Fabric CLI) examples and parameter tables alongside PowerShell/Visual Studio, not after them.
  • Provide explicit Linux/macOS command-line examples using SFCTL, including sample upgrade commands.
  • Balance parameter documentation so SFCTL coverage matches PowerShell/Visual Studio in detail and clarity.
  • In 'Next steps', list Linux/SFCTL tutorials before or alongside Windows tutorials.
  • Add notes clarifying cross-platform applicability where relevant.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Service Fabric application upgrade displays a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are native to Windows and not directly usable on Linux/macOS. References to Windows-specific tools (PowerShell, http.sys) are present, and alternative Linux/macOS workflows or CLI examples are missing. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, with no mention of cross-platform tools like Azure CLI or Service Fabric CLI (sfctl).
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform, alongside PowerShell examples.
  • Explicitly mention Linux/macOS support and provide guidance for those environments where applicable.
  • Where Windows-specific APIs or tools (e.g., http.sys) are referenced, clarify their platform limitations and suggest alternatives for Linux clusters.
  • Include links to Linux/macOS upgrade tutorials or documentation if available.
  • Reorder or balance 'Next steps' to include cross-platform tools before or alongside Windows-centric ones.
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 describes periodic backup configuration for Azure Service Fabric, including options for Azure Blob Storage and file shares. While Azure Blob Storage is cross-platform, the file share backup storage examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file share options (such as NFS or SMB mounting on Linux). There are no Linux/macOS-specific examples or guidance for configuring file share backups, which may create friction for users running Service Fabric clusters on Linux.
Recommendations
  • Add examples and instructions for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB/CIFS) and authentication methods.
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide sample configuration and troubleshooting steps for Linux environments.
  • If file share backup is Windows-only, explicitly state this in the documentation to avoid confusion for Linux users.
  • Ensure that any references to authentication methods (e.g., Integrated Windows Authentication) are accompanied by Linux alternatives or a note about platform support.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows and Windows-centric tooling (e.g., Microsoft.ServiceFabric.Powershell.Http Module, PowerShell cmdlets, and certificate thumbprint usage). All command-line examples use PowerShell syntax, with no mention of Linux/macOS equivalents (such as Bash, curl, or cross-platform Service Fabric CLI tools). There is no guidance for users on non-Windows platforms, which may create friction for those managing Service Fabric clusters from Linux or macOS.
Recommendations
  • Add equivalent examples using Bash, curl, or other cross-platform tools for REST API calls.
  • Document how to authenticate and interact with Service Fabric REST APIs from Linux/macOS, including certificate management.
  • Mention and provide guidance for using Service Fabric CLI (sfctl), which is cross-platform, where applicable.
  • Clarify any platform limitations (if certain modules/tools are Windows-only) and suggest alternatives for non-Windows users.
  • Ensure that prerequisites and installation steps include Linux/macOS options where possible.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation frequently references PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for cluster scaling operations, but does not provide equivalent Linux CLI or REST API examples. The instructions for manual scaling are PowerShell-centric, which may create friction for users managing Linux-based Service Fabric clusters. There is also an implicit assumption that users will use Windows tooling for cluster management, with no mention of Linux-native alternatives.
Recommendations
  • Provide equivalent Linux CLI (e.g., sfctl) or REST API examples for all PowerShell commands used in scaling operations.
  • Clarify which commands and procedures are applicable to both Windows and Linux clusters, and note any differences.
  • Add explicit instructions or links for managing Service Fabric clusters on Linux, including how to perform node disablement and removal.
  • Where possible, show both Windows (PowerShell) and Linux (sfctl/CLI/REST) examples side-by-side.
  • Reference Linux management tools earlier in relevant sections, not only in 'Next steps'.
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 consistently provides PowerShell examples for configuring Service Fabric placement policies, with no mention of Linux/macOS CLI equivalents (such as Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for users managing Service Fabric clusters from Linux or macOS environments. Additionally, PowerShell examples are presented immediately after C# code samples, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for each placement policy configuration.
  • Explicitly mention cross-platform management options for Service Fabric clusters, including links to relevant documentation for Linux/macOS users.
  • Clarify whether PowerShell examples are applicable on Linux/macOS (via PowerShell Core), and provide guidance if there are platform-specific limitations.
  • Consider reordering or balancing example order so that cross-platform options are not always shown after Windows-centric ones.
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 for Service Fabric Cluster Resource Manager - Application Groups provides command-line examples exclusively using PowerShell cmdlets, which are native to Windows environments. There are no equivalent examples for Linux/macOS users, such as Bash scripts, Azure CLI, or REST API usage. This creates friction for users managing Service Fabric clusters from non-Windows platforms, as they must translate PowerShell commands or rely on C# code samples.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usage, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include REST API request examples for relevant operations (e.g., creating/updating applications, querying load information), which can be used from any OS.
  • Explicitly mention cross-platform management options and link to documentation for Service Fabric management from Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and provide installation guidance if so.
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 a dedicated section and is used for cluster upgrade commands, which are Windows-centric. Windows-specific configuration details (e.g., registry keys, Windows Update settings) are discussed without Linux equivalents or parity. The upgrade instructions use PowerShell and reference MSI packages, with no Linux shell or DEB package examples. Windows VM configuration is described in detail, while Linux VM configuration is not covered. However, links to both Windows and Linux cluster creation guides are provided.
Recommendations
  • Include Linux shell (bash) examples for cluster upgrades, especially for operations currently shown only in PowerShell.
  • Provide Linux VM configuration best practices alongside Windows-specific registry and update settings.
  • Add DEB package upgrade instructions and Linux-specific commands where MSI/PowerShell are referenced.
  • Ensure that configuration snippets (e.g., disabling automatic updates) have Linux equivalents or clarify when they are Windows-only.
  • Balance example order so Linux and Windows are presented equally, or clarify when a section is Windows-specific.
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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but Windows-specific tools and examples (such as PowerShell commands and Windows Defender) are often presented first or exclusively. Some sections, like Windows Defender configuration, are Windows-only by nature and are correctly flagged as such. However, in other areas, Windows commands (PowerShell) are shown before Linux equivalents, and Windows-centric tools (e.g., Azure Desired State Configuration, Windows security baselines) are emphasized without mentioning Linux alternatives.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections, rather than listing Windows first.
  • Where Windows-specific tools are mentioned (e.g., Desired State Configuration, Windows Defender), add notes or links to equivalent Linux approaches (such as Ansible, Chef, or Linux-native security baselines).
  • Ensure that Linux users are provided with clear guidance and examples for all major security tasks, not just links to separate documents.
  • Add explicit statements when a feature or recommendation is Windows-only, to clarify intent and avoid confusion.
  • Consider including more Linux-focused best practices, such as SELinux/AppArmor, Linux firewall configuration, and Linux-native monitoring/antimalware solutions.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page generally describes Service Fabric node types and VM scale sets in a cross-platform manner, but there are signs of Windows bias. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) without showing a Linux equivalent. The 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials—these are Windows-centric tasks and tools, with no mention of Linux/SSH equivalents. Linux-specific guidance is minimal or absent, and Windows patterns (RDP, PowerShell, Windows file paths) are presented first or exclusively.
Recommendations
  • Include Linux-specific examples for configuration, such as showing a Linux-style dataPath (e.g., /var/svcfab) alongside the Windows example.
  • Add links or guidance for Linux users on how to connect to cluster nodes (e.g., SSH instructions) and manage credentials, not just RDP/PowerShell.
  • Balance the 'Next steps' section by providing equivalent Linux management tasks and scripts, or clarify which steps are Windows-only.
  • Explicitly state when a feature or example is Windows-specific, and provide Linux alternatives where possible.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services, but does not offer equivalent Linux CLI (sfctl) or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of Linux-native tooling or cross-platform command-line alternatives for these operations.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script snippets for common operations where possible.
  • Explicitly mention that PowerShell examples are for Windows, and provide guidance for Linux/macOS users on how to perform the same tasks.
  • Consider adding a table or section comparing PowerShell and sfctl usage for key Service Fabric 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 both C# and PowerShell examples for managing Service Fabric metrics, but only PowerShell is shown for command-line usage, with no Linux/macOS CLI equivalents (such as Azure CLI or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. The documentation does not mention or demonstrate how to perform these tasks using cross-platform tools, nor does it clarify whether PowerShell Core is supported on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI or REST API examples for service creation and metric management, which are cross-platform.
  • Clarify whether PowerShell Core is supported for these commands on Linux/macOS, and provide installation guidance if so.
  • Explicitly mention any platform limitations for Service Fabric management tools.
  • Consider reordering examples so that cross-platform options are shown before or alongside PowerShell.
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 provides detailed PowerShell examples for managing node tags and service tag requirements, but does not include equivalent CLI/bash or Linux-native examples. PowerShell is primarily a Windows tool, and its usage is presented before C# API examples. There is no mention of Linux/macOS command-line alternatives for these tasks, despite Service Fabric supporting Linux clusters.
Recommendations
  • Add examples using Azure CLI or REST API calls for managing node tags and service tag requirements, which are cross-platform.
  • If Service Fabric supports Linux-native management tools (e.g., bash scripts, SFCTL), include those examples alongside PowerShell.
  • Explicitly state whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide guidance for non-Windows users.
  • Reorder examples so that cross-platform or API-based approaches are presented before or alongside PowerShell.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Update-ServiceFabricService), which are Windows-centric tools. There are no CLI (e.g., Azure CLI, sfctl) or bash examples for Linux/macOS users, nor is there guidance for cross-platform management. This creates friction for non-Windows users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using cross-platform tools such as Azure CLI or sfctl where possible.
  • Explicitly document whether PowerShell cmdlets are supported on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
  • If only PowerShell is supported, clearly state this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Include bash or shell script examples for common operations, or reference cross-platform Service Fabric management documentation.
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 covers security for both Azure-hosted and standalone Windows Service Fabric clusters, but examples and links for standalone clusters are exclusively Windows-focused. There are no instructions or references for securing standalone Linux clusters, and Windows terminology and links are presented first or exclusively in several sections.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters running on Linux, if supported.
  • Include Linux-specific examples for certificate creation, installation, and configuration (e.g., using OpenSSL, Linux file paths, and permissions).
  • Clarify in each section whether the instructions apply to both Windows and Linux, or only Windows, to avoid confusion.
  • If standalone Linux clusters are not supported, state this clearly to set expectations for Linux users.
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
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally maintains platform neutrality. However, in several sections, Windows-centric tools (PowerShell) are mentioned before or instead of Linux equivalents. The section on OS image upgrades links only to Windows patching guidance, and PowerShell is referenced as a management tool alongside Azure CLI, but Linux-specific tools or examples are not provided. There is an implicit prioritization of Windows patterns and tools, which may create friction for Linux users.
Recommendations
  • When mentioning PowerShell, also provide Bash/Azure CLI examples or clarify cross-platform support.
  • For OS image upgrades, include or link to Linux node patching guidance if Service Fabric supports Linux clusters.
  • Explicitly state when steps or tools apply to both Windows and Linux clusters, or clarify any platform limitations.
  • Add examples or references for Linux management workflows where appropriate (e.g., Bash scripts, Linux CLI usage).
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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mentioning or providing equivalent Azure CLI commands, which are cross-platform and preferred on Linux/macOS. The application packaging workflow is described using Visual Studio, a Windows-centric tool, with no alternative instructions for packaging on Linux/macOS. No Linux or CLI examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK commands) instead of or in addition to Visual Studio.
  • Explicitly mention that all steps can be performed on Linux/macOS, and link to relevant cross-platform tooling.
  • Where screenshots or UI steps are shown, clarify if there are differences for Linux/macOS users or provide alternative guidance.
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 page provides a general overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several places, and Windows terminology (e.g., Windows service, FabricHost.exe) is used without always clarifying Linux equivalents. Examples and links for cluster creation and upgrades focus on Windows, with Linux standalone clusters explicitly noted as unsupported. Linux tools and workflows are referenced but often after Windows, and some sections lack Linux-specific examples or guidance.
Recommendations
  • Present Windows and Linux options side-by-side when discussing tools, commands, and workflows (e.g., PowerShell vs. CLI).
  • Add Linux-specific examples and links where only Windows instructions are given (e.g., cluster creation, upgrades).
  • Clarify when features or tools are Windows-only, and provide alternative guidance for Linux users.
  • Mention Linux equivalents (e.g., systemd services, Linux CLI tools) when describing Windows services and executables.
  • Ensure that getting started and next steps sections include Linux paths and resources.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.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 exhibits mild Windows bias by prioritizing PowerShell and Visual Studio examples, mentioning Windows-centric tools and workflows first, and lacking explicit Linux/macOS command-line examples (e.g., Bash, shell scripts) for parameter passing and deployment. While sfctl and Jenkins are mentioned, the examples and workflow descriptions are predominantly Windows-oriented.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as Bash scripts using sfctl.
  • Present cross-platform tools (sfctl, Jenkins) before or alongside Windows tools (PowerShell, Visual Studio) in workflow descriptions.
  • Include sample shell script snippets for Linux users to mirror the PowerShell examples.
  • Clarify which steps are platform-agnostic and which are Windows-specific, to help users on all platforms navigate the documentation.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits moderate Windows bias. References and links to upgrade instructions and configuration customization are directed to Windows Server-specific documentation (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md). The Patch Orchestration Application is described only for Windows. There are no explicit Linux examples, nor is there mention of Linux-specific upgrade or patching guidance, despite Service Fabric standalone clusters supporting both Windows and Linux.
Recommendations
  • Add explicit guidance and examples for upgrading Service Fabric standalone clusters running on Linux, including links to Linux-specific documentation if available.
  • Clarify which features or tools (such as Patch Orchestration Application) are Windows-only, and provide Linux alternatives or state if none exist.
  • Ensure that configuration and upgrade instructions reference both Windows and Linux where applicable, or clearly indicate platform limitations.
  • Where possible, provide cross-platform examples or note differences in procedures between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation mentions both Windows Server and Linux as supported platforms for Service Fabric clusters, but it highlights that standalone clusters are not available on Linux. The page does not provide Linux-specific examples or guidance, and Windows is mentioned first throughout. The lack of Linux standalone cluster support is a product limitation, but the documentation could better clarify Linux usage scenarios and alternatives.
Recommendations
  • Explicitly state the limitations for Linux (i.e., standalone clusters not supported) early in the document.
  • Provide guidance or links for deploying Service Fabric clusters on Linux within Azure, including any differences in management or feature support.
  • Include a comparison table summarizing feature parity and limitations between Windows and Linux clusters.
  • Add Linux-specific examples or references where applicable, especially for Azure-hosted clusters.
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 presents PowerShell as the primary CLI example for creating services with the Exclusive Process model, without providing equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). The references to service management operations (creating, querying, reporting health, restarting) are all linked to PowerShell cmdlets, and the 'Next steps' section specifically mentions PowerShell for managing application instances. There is no mention of Linux-native tools or cross-platform command-line alternatives, nor are examples for Linux/macOS users provided.
Recommendations
  • Add Azure CLI or REST API command examples for service creation and management, demonstrating cross-platform usage.
  • Clarify in the documentation that PowerShell examples are applicable on Windows, and provide guidance for Linux/macOS users on how to perform equivalent operations.
  • Include links to Service Fabric SDK documentation for Linux/macOS, if available, and note any platform-specific limitations.
  • Where PowerShell cmdlets are referenced, provide REST API or Azure CLI equivalents in parallel.
  • In the 'Next steps' section, mention cross-platform management options, not just PowerShell.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 mentions both Windows and Linux support for Service Fabric and highlights cross-platform capabilities. However, there is a subtle Windows bias: Windows development is described first, with emphasis on Visual Studio and PowerShell integration, while Linux development is mentioned second and less prominently. No explicit Linux command-line examples or Linux-specific tooling are shown, and the quickstart link points to a .NET (typically Windows-first) example. There are no Linux shell or deployment examples, and the documentation does not provide parity in example depth or tooling coverage.
Recommendations
  • Present Windows and Linux development options with equal prominence and detail.
  • Include Linux shell (bash) and command-line examples alongside PowerShell examples.
  • Add quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development.
  • Highlight Linux-specific tools (e.g., Yeoman, Eclipse) with example usage.
  • Ensure that deployment and management instructions include both Windows and Linux workflows.
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 ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without providing equivalent guidance or examples for Linux-based Service Fabric clusters. There is no mention of Linux event logging mechanisms or how Linux users can access or forward Service Fabric events, which may create confusion or friction for Linux users.
Recommendations
  • Add explicit guidance or examples for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-compatible logging solutions.
  • Clarify whether the described event access methods (e.g., EventStore REST APIs) are cross-platform and, if so, highlight these as the recommended approach for Linux clusters.
  • If certain features (like ETW/Windows Event logs or the Windows Azure diagnostics agent) are Windows-only, clearly state their platform limitations and provide Linux alternatives where possible.
  • Consider including a table or section comparing event access methods on Windows vs. Linux clusters.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is a cross-platform feature. However, the only concrete example of reporting and evaluating health uses Windows PowerShell cmdlets (Send-ServiceFabricApplicationHealthReport, Get-ServiceFabricApplicationHealth), with no equivalent CLI, REST, or Linux/macOS example. This creates friction for Linux/macOS users, as the PowerShell tools are Windows-centric and not available natively on Linux clusters. The documentation also mentions PowerShell before REST or other cross-platform APIs when discussing how to send health reports.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or SDKs (e.g., Python, .NET Core) for reporting and querying health, especially for Linux/macOS users.
  • Explicitly mention which tools are available on Linux clusters and provide links to cross-platform tooling.
  • When listing ways to report health, mention REST API and SDKs before or alongside PowerShell to avoid implying PowerShell is the primary or only method.
  • Consider adding a note clarifying tool availability and platform support for health reporting commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.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 on Azure Service Fabric hosting activation and deactivation life cycle demonstrates a moderate Windows bias. The 'Next steps' section exclusively references PowerShell for deployment/removal tasks, and the only example for downloading a ServicePackage in advance links to a PowerShell cmdlet. There are no Linux shell or cross-platform CLI examples, and Windows tools (PowerShell) are mentioned before any Linux alternatives, which are absent.
Recommendations
  • Add equivalent Linux/macOS instructions using Azure CLI or Service Fabric CLI (sfctl) for deployment and package management tasks.
  • Provide bash or shell script examples alongside PowerShell where possible.
  • Clarify in the 'Next steps' section that PowerShell is one option, and link to cross-platform alternatives if available.
  • Where cmdlets are referenced, note their platform compatibility and suggest alternatives for non-Windows users.
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 frequently references PowerShell for deployment and management tasks, and links to PowerShell-based workflows before mentioning alternatives. There is an implicit assumption of Windows tooling (e.g., Visual Studio, PowerShell) as the primary interface, with limited mention of Linux/macOS equivalents or cross-platform CLI usage.
Recommendations
  • Add explicit examples and instructions for deploying and managing Service Fabric clusters using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Include references to Linux/macOS development workflows, such as using VS Code or command-line tools, alongside Visual Studio.
  • When mentioning retrieval of cluster manifests, provide examples for REST API and .NET Core/.NET 5+ usage, and clarify which tools are cross-platform.
  • Ensure that links to PowerShell documentation are accompanied by links to equivalent CLI or REST documentation where available.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The examples are explicitly based on the 'Windows Server 2016 Container Sample', and references to Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows-style file paths like 'c:\VolumeTest\Data') are present. There is no mention of Linux equivalents, nor are Linux-specific manifest samples or guidance provided. While some features (like certificate handling) acknowledge both Windows and Linux behaviors, the overall focus and examples are Windows-centric, creating friction for Linux users.
Recommendations
  • Provide equivalent Linux-based manifest examples, referencing Linux container samples if available.
  • Include instructions for determining OS build/version on Linux (e.g., using 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Show Linux-style file paths (e.g., '/mnt/volume/data') in volume mount examples.
  • Clarify which features and manifest elements are cross-platform, and note any Windows-only limitations.
  • Link to Linux container documentation or samples where appropriate.
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 for 'Networking patterns for Azure Service Fabric' demonstrates a notable Windows bias. All deployment and management examples use PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS workflows. The only command-line examples are Windows-centric (PowerShell, RDP, Windows-style file paths), and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users attempting to follow the documentation.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include notes or sections for Linux/macOS users, such as how to deploy templates using Bash or Azure CLI.
  • Replace or supplement Windows-style file paths (e.g., C:\SFSamples\...) with platform-agnostic or Linux-style paths.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide SSH examples.
  • Clarify which steps are platform-agnostic and which are Windows-specific, to help users on other operating systems.
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 page provides extensive PowerShell examples and references for health reporting in Service Fabric, with no equivalent Linux/macOS CLI examples (such as Bash, sfctl, or Azure CLI). PowerShell commands are shown before REST API usage, and there is no mention of Linux tooling or cross-platform command-line approaches for interacting with Service Fabric health reporting. This creates friction for users on Linux/macOS, who must infer or research alternative methods.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for health reporting tasks shown in PowerShell.
  • Include Azure CLI examples where possible, especially for REST-based operations.
  • Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Reorder or parallelize examples so REST/sfctl/Azure CLI approaches are shown alongside PowerShell, not after.
  • Clarify any platform limitations for Service Fabric tooling, and link to cross-platform tool documentation.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is notably Windows-focused, referencing Visual Studio-specific workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and omitting any mention of Linux/macOS development environments or deployment tooling. All examples and process descriptions assume usage of Visual Studio on Windows, with no guidance for Linux/macOS users or cross-platform alternatives.
Recommendations
  • Add explicit statements clarifying that StartupServices.xml is only supported for Visual Studio deployments on Windows, and is not available for Linux/macOS environments.
  • Provide alternative guidance or links for Linux/macOS users, such as using ARM templates, Service Fabric CLI, or PowerShell Core (if supported cross-platform) for service deployment and configuration.
  • Include a comparison table or section outlining differences in workflow between Windows (Visual Studio) and Linux/macOS environments for Service Fabric application deployment.
  • Mention supported cross-platform tools (e.g., Service Fabric CLI, Azure DevOps pipelines) and clarify which features are Windows-only.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents, REST APIs, or cross-platform tooling. The documentation assumes the use of PowerShell and Windows-centric Service Fabric management tools, omitting guidance for Linux-based Service Fabric clusters or users managing clusters from non-Windows environments.
Recommendations
  • Include equivalent examples for Linux environments, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Explicitly state whether the described PowerShell cmdlets are available or supported on Linux/macOS, and provide alternatives if not.
  • Add notes or sections clarifying how Linux users can perform soft delete, restore, and query operations (e.g., via sfctl, REST API, or SDKs).
  • Where possible, provide cross-platform code snippets or command examples, and avoid assuming PowerShell as the default management interface.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page provides examples and deployment instructions primarily using Windows-centric tools and patterns, such as PowerShell cmdlets (e.g., New-ServiceFabricApplication) and Windows file paths. Linux equivalents are mentioned only briefly (e.g., certificate store location), and no Linux-specific deployment commands or examples are provided. The use of PowerShell for application deployment and references to Windows SDK installation paths suggest a Windows-first approach, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/macOS deployment instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for application deployment.
  • Include Linux file paths and certificate management details alongside Windows paths where relevant.
  • Present cross-platform examples side-by-side or clarify which steps are platform-specific.
  • Reference Linux/macOS tools and patterns (e.g., bash scripts, sfctl) where PowerShell is currently used.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.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 PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but there is a tendency to present PowerShell (Windows) examples before CLI (cross-platform) ones, and some sections (such as querying public IPs) offer more detailed PowerShell examples than CLI. In some cases, PowerShell examples are given without explicit Linux/macOS CLI equivalents, and there are no bash scripting examples for advanced tasks. The documentation does not mention Linux-specific tools or patterns, and the order of examples sometimes favors Windows/PowerShell first.
Recommendations
  • Ensure CLI (az) examples are always present and as detailed as PowerShell examples, especially for querying and updating resources.
  • Present CLI examples before PowerShell examples to emphasize cross-platform parity.
  • Add bash scripting examples for advanced tasks where PowerShell scripts are shown.
  • Explicitly mention that CLI commands work on Linux/macOS and Windows, and clarify any platform-specific limitations.
  • Where REST API or ARM template examples are given, provide CLI commands to perform equivalent operations if possible.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides example commands for both Azure CLI and Azure PowerShell, but in several sections, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and sometimes appears before Linux-specific details. The Azure Resource Manager template section references both Linux and Windows getting started articles, but the PowerShell examples are detailed and prominent, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Ensure that Azure CLI examples are shown first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Where PowerShell examples are given, explicitly note that PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS.
  • Add Bash shell script examples where appropriate, especially for scale set management tasks.
  • In update/expansion sections, provide full Azure CLI command sequences alongside PowerShell, not just a single command.
  • Consider a tabbed format for CLI, PowerShell, and REST API, with CLI as the default tab.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.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 is focused on Linux, but there are several instances of Windows bias: PowerShell is used heavily for deployment examples, and troubleshooting instructions reference Azure PowerShell before Azure CLI. There are also references to Windows-centric tools and patterns, such as the use of PowerShell and a link to a Windows VM access policy guide. While Azure CLI examples are present, PowerShell is often shown first or exclusively in some troubleshooting sections.
Recommendations
  • Prioritize Azure CLI examples over PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Where PowerShell is referenced, always provide an equivalent Azure CLI or Bash example.
  • In troubleshooting sections, list Azure CLI commands before PowerShell, or present both together.
  • Remove or clarify references to Windows-specific guides (e.g., access policy configuration for Windows VMs) and link to Linux-specific guides where possible.
  • Explicitly mention that PowerShell is available on Linux/macOS, or recommend Azure CLI for Linux users.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.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 creating VMs from generalized images, but the PowerShell sections are heavily focused on Windows VM creation. In several PowerShell examples, the use of Set-AzVMOperatingSystem -Windows is shown by default, and there is no equivalent example for Linux VM creation using PowerShell. Additionally, the PowerShell examples consistently show Windows configuration first and exclusively, while CLI examples are more Linux-focused. The REST and Portal sections provide parity for both OS types, but PowerShell users on Linux/macOS may find the guidance lacking.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • Include comments or notes in PowerShell sections to clarify how to adapt examples for Linux VMs.
  • Where PowerShell is used, show both Windows and Linux VM creation patterns, or link to Linux-specific PowerShell guidance.
  • Ensure that introductory text in PowerShell sections does not imply Windows is the only supported OS.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.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 PowerShell examples for configuring VM vCore customization, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux/macOS shell example (e.g., Bash). The CLI example uses Ubuntu as the image, but does not show Linux-specific verification steps or mention Linux tooling for post-deployment validation. The PowerShell section is detailed and uses Windows-centric SDK objects, which may be less familiar to Linux/macOS users. The order of examples (CLI, then PowerShell) is reasonable, but the lack of Linux/macOS shell-specific instructions and verification creates mild friction for non-Windows users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for post-deployment verification of vCPU and SMT settings.
  • Include instructions or commands (e.g., lscpu, nproc) to verify CPU configuration inside a Linux VM after deployment.
  • Clarify that Azure CLI works cross-platform and can be run from Linux/macOS, and provide guidance for those environments.
  • Consider reducing the emphasis on PowerShell SDK object manipulation, or provide equivalent automation examples for Linux (e.g., using az CLI with JSON templates or shell scripting).
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.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 both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are notably more detailed, including full network setup and VM configuration, while the CLI examples are more minimal. PowerShell is a Windows-centric tool, and the documentation does not provide equivalent Linux shell scripting examples (e.g., Bash with Azure CLI), nor does it mention Linux-specific patterns or tools. In several sections, PowerShell examples are given with more context and steps than CLI, and the PowerShell tabs appear before Portal tabs, suggesting a Windows-first approach. There are no explicit Linux shell script examples or guidance for Linux/macOS users beyond the CLI commands.
Recommendations
  • Provide full Bash shell script examples using Azure CLI, matching the detail level of the PowerShell examples (including network setup, NIC creation, etc.).
  • Add notes or guidance for Linux/macOS users regarding environment setup, authentication, and scripting best practices.
  • Ensure parity in example complexity and completeness between PowerShell and CLI sections.
  • Consider reordering tabs so CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low 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 shows minor Windows bias. In the 'ContainerImagesToSkip' setting, Windows base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as defaults, and Windows examples are given before Linux equivalents. Linux images (e.g., alpine) are only referenced in an example, not as defaults. No PowerShell-specific or Windows-only tooling is referenced, and the configuration examples are platform-neutral.
Recommendations
  • Explicitly mention common Linux base images (e.g., ubuntu, alpine) in the 'ContainerImagesToSkip' section, either as additional defaults or in examples.
  • Clarify that the configuration applies equally to Linux and Windows containers, and provide examples for both.
  • Add a note or table listing typical base images for both Windows and Linux, and how to configure skipping them.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-specific tooling (Visual Studio, file paths like C:\Program Files\...) and mentioning the ServiceFabric PowerShell module for service creation, without providing Linux/macOS equivalents or alternatives. However, the core manifest concepts and examples are platform-neutral XML and do not prevent Linux/macOS users from completing the described tasks.
Recommendations
  • When suggesting tools for authoring or validating manifests, mention cross-platform alternatives (e.g., VS Code, xmllint) alongside Visual Studio.
  • Include Linux/macOS file paths or clarify that the referenced .xsd schema is available on all platforms and where to find it.
  • When referencing the ServiceFabric PowerShell module, also mention the Service Fabric CLI (sfctl) or other cross-platform deployment tools.
  • Explicitly state that the manifest authoring and deployment process is supported on Linux/macOS clusters, and link to relevant cross-platform guides.
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, but there is a slight Windows-first bias in the ordering and emphasis of examples and scenarios. Windows-specific tools (e.g., Mirantis Container Runtime, IIS lift-and-shift) are mentioned in detail, while Linux equivalents are referenced but not elaborated upon. The Linux quickstart is listed first in some places, but Windows scenarios and tools receive more detailed coverage.
Recommendations
  • Ensure Linux and Windows examples are presented with equal detail and prominence.
  • Expand on Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the detail given to Windows/IIS.
  • Include more explicit Linux tooling references (e.g., containerd, podman) if relevant.
  • Where possible, alternate the order of Linux and Windows examples to avoid implicit prioritization.
  • Provide links to Linux container documentation (e.g., Docker on Linux, Linux container security best practices) alongside Windows links.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page exhibits mild Windows bias by referencing the Service Fabric SDK schema location using a Windows file path and implicitly assuming Windows tooling. There are no explicit Linux/macOS examples, and the directory/file structure examples use Windows-style conventions. However, the content does not exclude Linux users, and Service Fabric itself supports Linux clusters and guest executables in non-Windows environments.
Recommendations
  • Include Linux/macOS equivalents for SDK schema locations (e.g., /opt/microsoft/servicefabric/schemas/...)
  • Clarify that Service Fabric guest executables can be packaged and deployed from Linux/macOS environments, and provide relevant instructions or links.
  • Add examples or notes for Linux/macOS users regarding directory structure and file paths.
  • Mention cross-platform command-line tools or alternatives to Visual Studio for packaging and deployment.
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. PowerShell examples are presented first and in greater detail, which may signal a Windows-first approach. However, the CLI examples (sfctl) are cross-platform and allow Linux/macOS users to perform the same tasks. There are no Linux-specific shell examples (e.g., bash), and no mention of Linux-specific considerations, but the CLI coverage mitigates most friction.
Recommendations
  • Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider presenting CLI (sfctl) examples before PowerShell, or side-by-side, to avoid Windows-first impression.
  • Add a brief note or example showing how to install and use sfctl on Linux/macOS.
  • Clarify any platform-specific limitations (e.g., 'Isolation' directive is Windows-only) in the relevant sections.
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 cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a subtle Windows bias in the 'Node' definition, where Windows-specific tools and processes (FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned without Linux equivalents or clarification. The order of mention and examples tends to favor Windows terminology first, and references to EXE/DLL files in code packages are Windows-centric, even though Linux is supported. There are no explicit Linux examples or tools described, and Linux terminology is less visible.
Recommendations
  • Clarify that FabricHost.exe, Fabric.exe, and FabricGateway.exe have Linux equivalents or describe the Linux process model for nodes.
  • When describing code packages, mention Linux binary formats (such as ELF binaries) alongside EXE/DLL files.
  • Provide examples or notes for Linux-specific deployment or operational patterns where relevant.
  • Ensure that references to guest executables and containers explicitly mention Linux support and provide parity in examples.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but shows mild Windows bias in several areas. Windows-specific scenarios (activation, updates) are listed before Linux equivalents (package managers) in the networking section, and no Linux-specific migration examples or references (such as SSH, cloud-init, or Linux VM images) are provided. All CLI and API examples are generic and not OS-specific, but the lack of explicit Linux migration guidance may create friction for Linux users.
Recommendations
  • Add explicit Linux migration scenarios, such as steps for migrating Linux VMs (e.g., handling SSH keys, cloud-init configuration, Linux disk attachment).
  • In networking sections, mention Linux package manager connectivity before or alongside Windows activation and updates.
  • Provide example commands or references for both Windows and Linux VM images when discussing VM creation.
  • Where VM extensions are discussed, mention popular Linux extensions (e.g., Azure VM Agent for Linux, custom script extension) alongside Windows equivalents.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are consistently presented alongside CLI and Portal, and in some sections, PowerShell is shown before ARM template examples. This may create a subtle Windows-first impression, especially since PowerShell is primarily a Windows tool (though available on Linux/macOS). No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the Azure CLI commands are cross-platform and suitable for Linux/macOS users. There are no critical sections that are Windows-only, and all tasks can be completed using the CLI or Portal.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and are the recommended cross-platform approach.
  • Consider adding a brief note in the introduction or CLI sections highlighting CLI parity for Linux/macOS users.
  • If possible, provide Bash script snippets or mention that CLI commands can be run in Bash, zsh, etc.
  • Ensure PowerShell is not presented as the primary or default automation tool unless the feature is Windows-specific.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets, but there is a notable Windows bias. PowerShell examples are given equal prominence to Bash, and Windows-specific extension types (ApplicationHealthWindows) are shown before Linux equivalents (ApplicationHealthLinux) in several places. The PowerShell example is more detailed than the Bash example, and Windows tooling (PowerShell) is presented as a primary method alongside Azure CLI and REST, rather than as a secondary or alternative option. In extension configuration JSON, Windows extension types are listed first. However, Linux users can still complete all tasks, and CLI/Bash examples are present.
Recommendations
  • List Linux extension types (ApplicationHealthLinux) before Windows types (ApplicationHealthWindows) in JSON and REST examples, or show both explicitly.
  • Ensure Bash/Linux examples are as detailed and robust as PowerShell/Windows examples, especially for server setup and scripting.
  • Where both CLI and PowerShell examples are given, consider presenting CLI (cross-platform) first, then PowerShell (Windows-specific).
  • Clarify in extension configuration tables and examples that both Linux and Windows are supported, and provide explicit Linux-focused sample values.
  • Add troubleshooting steps or notes for Linux-specific issues if any exist.
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 page is focused on Linux VM time sync in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and links to Windows documentation before delving into Linux-specific mechanisms. No Windows-only tools or examples are given, and all configuration and troubleshooting steps are Linux-centric.
Recommendations
  • Move the Windows Server 2016 time sync discussion to a background or infrastructure section, making it clear it's context for Azure hosts, not actionable for Linux VM admins.
  • Begin the page with Linux-specific time sync concepts and configuration options.
  • Ensure that 'Next steps' and reference links prioritize Linux resources over Windows ones, unless specifically relevant to Azure host infrastructure.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are given equal prominence as CLI, and in some sections (e.g., ARM template deployment and VM deallocation), PowerShell is used as the default scripting language, which is more native to Windows. Additionally, in step-by-step instructions, RDP (Windows) is mentioned before SSH (Linux), and screenshots are Windows-centric. There are no missing Linux examples, and Linux-specific considerations (such as Secure Boot validation with SBInfo) are included.
Recommendations
  • Where scripting is required (e.g., deallocation, template deployment), provide both PowerShell and Bash/Azure CLI examples, or clarify that PowerShell can be used cross-platform.
  • Alternate the order of RDP/SSH mentions, or mention SSH first when discussing Linux VMs.
  • Include screenshots from both Windows and Linux VM contexts, or use more generic images.
  • Explicitly state that PowerShell can be used on Linux/macOS, or recommend Bash/CLI alternatives for Linux users.
  • Where possible, clarify that all steps apply equally to Linux and Windows VMs, and highlight any OS-specific caveats.
GitHub Create Pull Request