← Back to Dashboard
231
Pages Scanned
80
Pages Flagged
231
Changed Pages
34.6%
% Pages Flagged

Scan Information

Started At: 2026-02-02 00:00:07

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

80 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images, Windows file paths, and Windows command syntax (cmd.exe). There are no Linux container examples, nor is there any mention of how to use Initializer CodePackages with Linux containers or Linux file systems. The documentation assumes familiarity with Windows container development and does not provide Linux parity.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands and file paths.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance and examples.
  • If there are limitations or differences for Linux containers, explicitly document them.
  • Present both Windows and Linux examples side-by-side where possible to improve accessibility for non-Windows users.
GitHub Create Pull Request
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 the 'Supported operating systems' section clarify that Linux is not yet supported for standalone clusters. The security sections reference Windows-specific features (Kerberos, Active Directory, group Managed Service Accounts), and there are no Linux-specific instructions, examples, or tools mentioned. Windows tools and patterns are referenced exclusively, and Linux is only mentioned as a future possibility.
Recommendations
  • Clarify Linux support status earlier in the document to avoid confusion.
  • Add a prominent note at the top stating that standalone clusters are currently Windows-only.
  • Remove or rephrase references to Linux in the introduction and description until Linux support is available.
  • When Linux support is added, provide equivalent Linux examples, instructions, and security guidance.
  • Consider linking to Service Fabric on Linux documentation (if available) for users interested in non-Windows deployments.
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 instructions, and usage scenarios assume a Windows environment, with no Linux equivalents or alternatives provided.
Recommendations
  • Clearly state at the beginning of the documentation that reverse proxy is not available for Linux clusters, and provide links or guidance for Linux users on alternative approaches for service discovery and communication.
  • If possible, mention any roadmap or plans for Linux support, or direct Linux users to relevant Service Fabric features that are available on Linux.
  • Consider adding a comparison table or section outlining feature parity and limitations between Windows and Linux clusters for Service Fabric networking and reverse proxy capabilities.
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 primarily references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no 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 or macOS users who typically use Azure CLI or Bash.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for common operations like creating, deleting, and scaling resources.
  • Clarify when Az PowerShell is required versus when Azure CLI can be used, and provide links to relevant Azure CLI documentation.
  • Add explicit notes or examples for Linux/macOS users, ensuring parity in instructions and tooling.
  • Where possible, provide ARM template examples that are platform-agnostic.
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 demonstrates a notable Windows bias. PowerShell cmdlets are referenced throughout as primary examples for operational tasks (deploy, upgrade, remove, cleanup), often listed before REST API or .NET methods. There is little to no mention of Linux-specific tools, shell commands, or cross-platform CLI usage (such as Azure CLI or sfctl), despite Service Fabric supporting Linux clusters. This may create friction for Linux/macOS users who do not use PowerShell or Windows-centric tooling.
Recommendations
  • Add equivalent Linux/macOS examples using Azure CLI and sfctl for all operational steps (deploy, upgrade, remove, cleanup).
  • Ensure REST API and cross-platform CLI commands are presented before or alongside PowerShell cmdlets, not after.
  • Explicitly state cross-platform support and clarify which tools are available on Linux/macOS.
  • Where PowerShell is used, provide alternative shell or CLI commands for Linux users.
  • Add notes or links to Linux-specific documentation where relevant.
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 PowerShell is featured prominently and exclusively as the CLI example. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API examples), and PowerShell is presented before any mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples where appropriate, especially for service creation and metric updates.
  • Explicitly mention platform compatibility for PowerShell commands and suggest alternatives for non-Windows users.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Clarify whether Service Fabric management tasks can be performed equally well from Linux/macOS, and link to relevant documentation.
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 describes the Azure Service Fabric hosting activation and deactivation lifecycle in a platform-neutral way, but the only explicit example or next-step guidance for deploying/removing applications is via PowerShell, which is primarily a Windows tool. There are no Linux/macOS CLI or script examples, nor are Linux tools or patterns mentioned. The link for downloading a ServicePackage in advance also points to a PowerShell cmdlet, with no Linux equivalent provided.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl) for deployment and package management.
  • Include links to documentation for Linux-based Service Fabric clusters and their management tools.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternative commands for bash/shell environments.
  • Ensure that next steps and code samples cover both Windows and Linux workflows equally.
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 provides both Windows and Linux guidance for key security tasks, but Windows examples and tools (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively, with Linux equivalents sometimes referenced later or less prominently. Windows-specific tools and configuration patterns (e.g., PowerShell commands, Windows Defender configuration) are described in detail, while Linux alternatives are less emphasized or omitted in some sections.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections to ensure equal visibility.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Add more Linux-focused security baseline recommendations and reference common Linux security tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where appropriate.
  • Ensure that instructions for deploying certificates, configuring ACLs, and encrypting secrets are equally detailed for both platforms.
  • Clarify platform-specific limitations or differences to help users understand which guidance applies to their environment.
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 discusses Service Fabric clusters on both Windows Server and Linux, but it notes that standalone clusters are not available on Linux. The page generally presents Windows as the default or primary platform, with Linux mentioned as a secondary consideration. There are no Linux-specific examples or guidance, and the limitations for Linux are referenced only via a link, not explained directly.
Recommendations
  • Explicitly state the limitations for Linux clusters in the main content, not just via a link.
  • Provide a summary table or section outlining feature parity and gaps between Windows and Linux clusters.
  • Include Linux-specific guidance or examples where relevant, or clarify when features are Windows-only.
  • Ensure that Linux is mentioned equally in benefits and limitations sections, not just as an afterthought.
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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Windows (ClusterManifest.xml) and cross-platform (ClusterConfig.json) configuration examples, but all imperative command-line examples are given only in PowerShell, with no Linux CLI or Bash equivalents. The only explicit infrastructure example for local clusters uses <WindowsServer> in ClusterManifest.xml, and PowerShell is used for service management, which may create friction for Linux users. However, the core concepts and JSON-based configuration are cross-platform.
Recommendations
  • Add CLI/Bash examples for service creation and updates, using Service Fabric CLI (sfctl), which is supported on Linux/macOS.
  • Clarify when examples (such as <WindowsServer> in ClusterManifest.xml) are Windows-specific, and provide Linux equivalents (e.g., <Linux> infrastructure blocks) where appropriate.
  • Where PowerShell is used, add a note or alternative showing how to accomplish the same task on Linux using sfctl or REST API.
  • Ensure that imperative examples (service creation, updates) are shown for both Windows (PowerShell) and Linux (CLI/Bash/sfctl).
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 demonstrates a Windows bias by primarily referencing Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There is no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-specific tools or examples provided. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout/stderr, syslog, or Azure Monitor integration for Linux nodes).
  • Mention and provide examples of how to access and analyze events on Linux-based Service Fabric clusters.
  • Clarify any differences in event logging and diagnostics configuration between Windows and Linux clusters.
  • If certain features are Windows-only, explicitly state this to inform Linux users of any limitations.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for 'Networking patterns for Azure Service Fabric' demonstrates a moderate Windows bias. All command-line examples use PowerShell, with no Bash, Azure CLI, or Linux/macOS shell equivalents. The workflow and deployment instructions are written from a Windows-centric perspective (e.g., file paths like C:\SFSamples\...), and RDP is referenced as the remote access method, which is primarily a Windows protocol. There are no explicit instructions or examples for Linux/macOS users, nor are alternative tools or commands mentioned.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell commands for template deployment and resource management.
  • Include Linux/macOS file path examples where relevant, or use platform-neutral paths.
  • Mention SSH as an alternative to RDP for accessing VMs, especially for Linux-based clusters.
  • Clarify that the instructions apply to both Windows and Linux node types where appropriate, or note any differences.
  • Add a brief section or callout for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is notably Windows-centric, focusing exclusively on Visual Studio tooling and workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. There is no mention of Linux/macOS development environments, nor are alternative workflows or tools provided for non-Windows platforms. Examples and instructions are tailored to Windows users, with references to PowerShell and Visual Studio, and no Linux equivalents or parity guidance.
Recommendations
  • Explicitly state that StartupServices.xml is only supported for Visual Studio deployments on Windows, and clarify limitations for Linux/macOS users.
  • Provide alternative instructions or workflows for Linux/macOS users, if possible, or link to documentation for ARM/cmdlet-based deployments that work cross-platform.
  • Add a section comparing Windows and Linux/macOS development experiences for Service Fabric applications, highlighting any feature gaps.
  • If Linux/macOS support is not possible for this feature, make this clear early in the documentation to set expectations.
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 in a gallery. While CLI examples are generally cross-platform and default to Linux VM creation (using SSH keys), the PowerShell examples are Windows-centric: they use Windows-specific cmdlets and always configure the VM OS as Windows, with no PowerShell example for Linux VM creation. Additionally, in the PowerShell sections, the VM configuration uses Set-AzVMOperatingSystem -Windows, and there is no mention of how to create a Linux VM using PowerShell. REST and CLI examples do show both Linux and Windows options, but PowerShell guidance is Windows-first and Windows-only.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • In PowerShell sections, clarify how to create either Linux or Windows VMs, and provide both code samples.
  • In introductory text for PowerShell, mention Linux support and link to Linux-specific guidance if available.
  • Review the order of examples to ensure Linux and Windows parity in all scripting sections.
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. However, the PowerShell example is given equal prominence to the CLI example, and the CLI example uses Ubuntu as the image, but does not show any Linux-specific post-deployment steps or verification. There are no Linux shell (bash) examples for checking the resulting vCPU configuration inside the VM, nor are there instructions for Linux users to verify or interact with the settings post-deployment. The PowerShell section is detailed and uses Windows-centric SDK objects, while Linux users are not given parity in terms of OS-level verification or scripting.
Recommendations
  • Add Linux shell (bash) examples for verifying vCPU and SMT status inside the VM after deployment (e.g., using lscpu or /proc/cpuinfo).
  • Include a section with Linux-specific post-deployment steps to confirm the configuration.
  • Provide parity in scripting examples, such as showing how to automate VM creation and verification using bash scripts.
  • Clarify that the Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation instructions for each OS.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page provides extensive PowerShell examples and references to Windows-specific tooling and patterns (such as certificate store locations, ACLing, and Key Vault VM extension for Windows). While the core certificate management concepts are platform-neutral, the hands-on examples, troubleshooting, and automation scripts are almost exclusively presented using Windows-centric tools and PowerShell, with little to no mention of Linux equivalents or cross-platform approaches. Windows terminology and mechanisms (e.g., S-channel, certificate store, ACLing) are explained in detail, while Linux alternatives are absent or implied.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for certificate enrollment, provisioning, and rotation.
  • Explicitly document how certificate provisioning and management works for Service Fabric clusters running on Linux VMs/VMSS, including any differences in certificate store handling, permissions, and automation.
  • Reference and link to Key Vault VM extension documentation for Linux, if available, or clarify limitations.
  • When discussing certificate stores, ACLing, and linking, provide Linux-specific guidance (e.g., file permissions, OpenSSL usage) where relevant.
  • Ensure troubleshooting and FAQ sections include Linux scenarios and commands.
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 for deploying custom images on Azure Service Fabric Managed Clusters demonstrates a Windows bias. The introductory section and examples refer specifically to 'custom windows images', and the only command-line example provided uses PowerShell (New-AzRoleAssignment), with no equivalent Azure CLI or Linux shell example. While there are references to Linux custom image creation and Azure CLI for browsing images, actionable steps and examples are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands for role assignment and other operations.
  • Clarify whether Linux-based custom images are supported for Service Fabric Managed Clusters and, if so, include explicit instructions and examples for Linux images.
  • Balance references to Windows and Linux in introductory and instructional text, ensuring Linux users are equally addressed.
  • Add notes or sections for Linux/macOS users, including shell command equivalents and relevant links.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, without mentioning Linux/macOS equivalents or cross-platform CLI alternatives. The use of PowerShell cmdlets and lack of Bash/Azure CLI examples may create friction for Linux/macOS administrators.
Recommendations
  • Include equivalent Azure CLI or REST API instructions for bypassing Infrastructure Service operations, if available.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Add notes or examples for Linux/macOS users, especially for cluster management tasks.
  • Indicate platform requirements for commands, so users know if a Windows environment is necessary.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples in XML. However, there is a notable Windows bias in troubleshooting guidance and tool references. Windows-specific certificate store paths and troubleshooting tools (e.g., CAPI2 logging, Win32 CryptoAPI references) are mentioned first or exclusively, while Linux equivalents are only briefly referenced or omitted. Some error codes and remediation steps are Windows-centric, and there is little guidance for Linux/macOS users on equivalent certificate management or troubleshooting.
Recommendations
  • Provide Linux/macOS-specific troubleshooting steps and log file locations, such as where Service Fabric logs certificate errors on Linux nodes.
  • When referencing certificate stores (e.g., LocalMachine\My), always mention the Linux equivalent path (e.g., /var/lib/sfcerts) in parallel, not as an afterthought.
  • Include examples of how to inspect, install, and manage certificates on Linux (e.g., using OpenSSL or Linux-native tools) alongside Windows methods.
  • Reference Linux/macOS error messages and common issues, and provide guidance for resolving them.
  • Avoid referencing only Windows APIs (e.g., Win32 CryptoAPI) without mentioning the equivalent mechanisms or libraries used on Linux.
  • If certain features or troubleshooting steps are Windows-only, explicitly state so and provide alternative guidance for Linux/macOS where possible.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). All scripting/automation examples outside ARM templates use PowerShell, which is primarily a Windows tool. There is no mention of Azure CLI or cross-platform scripting alternatives, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell examples require Azure PowerShell module and are best suited for Windows, and provide guidance for Linux/macOS users.
  • Consider adding Bash or cross-platform scripting examples where appropriate.
  • In sections where only PowerShell is supported (e.g., removing a primary node type), clarify if this is a platform limitation or just a documentation gap.
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 demonstrates a moderate Windows bias by prioritizing Azure PowerShell examples and references, listing PowerShell before Azure CLI, and not providing explicit Linux/macOS command-line examples for key operations. While ARM templates, Bicep, and Azure CLI are mentioned (which are cross-platform), the only concrete example links for deleting, restarting, and reimaging node types use Azure PowerShell, with no equivalent Azure CLI or REST API examples. This may create friction for Linux/macOS users who prefer CLI or scripting over PowerShell.
Recommendations
  • Add Azure CLI examples and links for all key operations (deleting, restarting, reimaging node types) alongside PowerShell examples.
  • Explicitly mention that Azure CLI and ARM templates are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, provide equivalent CLI or REST API documentation links.
  • Consider ordering examples and tool references so that cross-platform options (CLI, ARM, Bicep) appear before Windows-specific tools.
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 ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, set, ping), with no mention of Linux container equivalents. PowerShell is the only CLI example given for querying deployment status, and Windows tools/patterns are referenced exclusively. There is no guidance or parity for Linux-based Service Fabric clusters or Linux containers.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) with equivalent shell commands.
  • Provide instructions and examples for querying deployment status using Linux tools (e.g., Bash, Service Fabric CLI on Linux).
  • Clarify in the introduction whether RunToCompletion semantics are supported for Linux containers and clusters, and if not, explicitly state this limitation.
  • If supported, include cross-platform code samples and highlight differences or requirements for Linux users.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show subtle Windows bias. Examples and references often prioritize Windows tools or features (e.g., Active Directory, BitLocker, gMSA) and mention Windows-specific patterns before Linux equivalents. Some security features (like disk encryption) link only to Windows/PowerShell guides, and Linux options are left as TODOs or not described. Linux users may need to search elsewhere for parity.
Recommendations
  • Provide Linux-specific examples and links for disk encryption and other security features where only Windows/PowerShell instructions are given.
  • Ensure that references to OS-specific features (e.g., gMSA, AD accounts) are clearly marked as Windows-only, and offer Linux alternatives or clarify their absence.
  • Include Linux-first or cross-platform examples in sections about running services under different accounts, managing secrets, and securing containers.
  • Complete TODOs regarding Linux disk encryption and other missing Linux documentation.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence where both are supported.
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 of Windows bias. Windows-specific tools (Event Viewer, ETW, Diagnostics Agent) are mentioned and explained in detail, sometimes before their Linux equivalents (LTTng, Syslog). Some examples and tutorials focus on .NET applications (which are cross-platform, but the tutorial is Windows-oriented), and configuration steps for Linux are referenced but not shown inline. In a few places, Windows monitoring solutions are described first or in more detail, and Linux alternatives are only briefly mentioned or deferred to other pages.
Recommendations
  • Provide Linux-specific examples and configuration steps inline, not just as links to other pages.
  • Ensure that Linux monitoring tools (LTTng, Syslog, Azure Monitor agent) are described with equal detail and prominence as Windows tools (ETW, Event Viewer, Diagnostics Agent).
  • Include sample code and tutorials for Linux-based Service Fabric applications (e.g., using Application Insights or logging frameworks on Linux).
  • When listing monitoring solutions or workflows, present Windows and Linux options side-by-side, or clearly indicate which steps are OS-specific.
  • Add explicit PowerShell and Bash/CLI equivalents for automation examples.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page primarily describes Service Fabric application and service manifests in a platform-neutral way, focusing on XML schema and concepts. However, there is a notable Windows bias in the tooling recommendations: the warning box suggests using Visual Studio and a local Windows file path to validate the manifest schema, with no mention of Linux/macOS alternatives. Additionally, the PowerShell module is referenced for service creation before mentioning other methods, which may imply Windows-first workflows.
Recommendations
  • Include instructions or tooling recommendations for Linux/macOS users, such as using VS Code, JetBrains Rider, or other XML schema validation tools available cross-platform.
  • Provide equivalent Linux/macOS file paths or clarify how to obtain the ServiceFabricServiceModel.xsd schema on non-Windows systems.
  • Mention cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) for service creation and management alongside PowerShell.
  • When referencing PowerShell, explicitly note alternative approaches for Linux/macOS users.
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, with all command-line examples using PowerShell cmdlets. There is no mention of Linux/macOS equivalents, such as Service Fabric CLI (sfctl), nor are there bash or shell script examples. The documentation assumes users are operating in a Windows/PowerShell environment, creating friction for Linux/macOS users who may use different tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that PowerShell cmdlets are for Windows environments and provide links or references to Linux/macOS documentation.
  • Include bash or shell script snippets where appropriate, especially for common upgrade tasks.
  • Clarify which features or commands are cross-platform and which are Windows-only.
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 presents PowerShell and Visual Studio (Windows-centric tools) parameters and examples before introducing SFCTL (cross-platform CLI) and REST options. The parameter tables and explanations are heavily focused on PowerShell and Visual Studio, with detailed examples and descriptions, while SFCTL (the main Linux/macOS tool) is covered in a separate, shorter section with less detail and no explicit Linux/macOS command examples. There are no Linux/macOS-specific usage examples or parity in parameter explanation order, which may create friction for non-Windows users.
Recommendations
  • Reorder sections so SFCTL (cross-platform CLI) is presented before or alongside PowerShell/Visual Studio, emphasizing its use for Linux/macOS users.
  • Provide explicit SFCTL command-line examples for common upgrade scenarios, similar to the PowerShell examples.
  • Include a table mapping PowerShell/Visual Studio parameters to their SFCTL/REST equivalents for clarity.
  • Add notes or callouts indicating which tools are recommended for Linux/macOS users.
  • Ensure parameter descriptions for SFCTL are as detailed as those for PowerShell/Visual Studio, including example values and usage patterns.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides next steps that highlight upgrading applications using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No equivalent Linux/macOS upgrade instructions or tooling (such as Azure CLI or Service Fabric CLI) are mentioned or linked. The main content is focused on C# and .NET serialization, which is cross-platform, but the upgrade workflow guidance is Windows-first.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are supported on Linux and macOS.
  • Provide examples or tutorials for application upgrades on Linux/macOS environments.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
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_first
Summary
The documentation page on Azure Service Fabric architecture references PowerShell cmdlets as a primary management interface and mentions Windows security as an option for transport security before X509 certificates. No Linux-specific management tools or examples (such as Bash, CLI, or Linux security mechanisms) are mentioned, and Windows-centric tooling is presented first in relevant sections.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux/macOS, or provide Bash/CLI examples where appropriate.
  • When discussing security, highlight X509 certificates as the default cross-platform mechanism and note any Windows-specific options as alternatives.
  • Add notes or links to Linux/macOS management documentation for Service Fabric clusters.
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, with all command-line examples using PowerShell syntax and modules. There is no mention of Linux/macOS equivalents, nor are cross-platform REST API invocation examples (e.g., curl, Python) provided. The prerequisite steps and all automation instructions assume the use of Windows tools and environments, which may create friction for users managing Service Fabric clusters from Linux or macOS.
Recommendations
  • Add equivalent examples using cross-platform tools (e.g., curl, Python requests) for REST API calls.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made directly from any OS.
  • Provide guidance for Linux/macOS users on authentication (e.g., certificate handling) and cluster connection.
  • Explicitly state OS requirements or limitations if PowerShell is mandatory, or provide alternatives where possible.
  • Reorder or balance examples so that REST API usage is shown before or alongside PowerShell, emphasizing platform neutrality.
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 page provides detailed step-by-step instructions for scaling Service Fabric clusters, but the manual scaling procedures rely heavily on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or REST API examples. There is no mention of Service Fabric CLI (sfctl) or bash scripting, and the only command-line examples are Windows PowerShell. This creates friction for Linux users, who must find their own way to perform these operations. Additionally, the documentation references Windows tools first and does not provide parity for Linux environments in critical operational steps.
Recommendations
  • Add equivalent Linux instructions using sfctl (Service Fabric CLI) for all PowerShell-based steps, including node disabling, querying, and removal.
  • Provide bash or shell script examples alongside PowerShell for manual scaling operations.
  • Explicitly mention REST API alternatives for cluster management where applicable.
  • Clarify which commands are cross-platform and which are Windows-only, and provide links to Linux-specific documentation where available.
  • Ensure that all operational guidance (not just cluster creation) is platform-neutral or has Linux parity.
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 presents several examples and references that are Windows-centric, such as defaulting to Windows-style file paths (e.g., D:\SvcFab), referencing RDP port changes and admin credential updates (Windows remote access patterns), and linking to PowerShell scripts for cluster VM management. There is minimal coverage or examples for Linux users, and Linux-specific patterns (like SSH access or Linux file paths) are not mentioned or are secondary.
Recommendations
  • Include Linux-specific examples for file paths (e.g., /var/svcfab) in the Service Fabric extension settings.
  • Add guidance and links for SSH-based remote connection to Linux nodes, alongside or before RDP/PowerShell instructions.
  • Provide parity in script references, such as Bash/CLI scripts for changing admin credentials and port ranges on Linux VMs.
  • Clarify which instructions or examples apply to Windows, Linux, or both, to help users navigate platform differences.
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 ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is the only command-line example provided, and Windows-specific tools (PowerShell cmdlets, http.sys) are referenced exclusively. There are no Linux or cross-platform CLI examples, and the upgrade process is described using Windows-centric terminology and APIs. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both primarily Windows tools, with no mention of Linux equivalents or Service Fabric CLI usage.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include notes or sections clarifying differences in upgrade procedures for Linux clusters, if any.
  • Reference Linux-compatible tools and workflows in the 'Next steps' section, such as upgrading via sfctl or REST API.
  • Where Windows-specific APIs (e.g., http.sys) are mentioned, clarify their applicability and provide Linux alternatives or caveats.
  • Ensure that code samples and walkthroughs are available for both Windows and Linux environments.
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 reference the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no CLI, Bash, or cross-platform examples provided, and Linux/macOS users are not given alternative instructions for performing backups or REST API calls. The documentation assumes use of Windows tools and patterns throughout, making it less accessible for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or curl for REST API calls to support Linux/macOS users.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any platform.
  • Provide guidance on authentication and certificate handling for REST API calls from Linux/macOS environments.
  • Indicate platform requirements for each tool or command, and suggest alternatives where possible.
  • Consider reordering examples so that cross-platform methods (e.g., REST API via curl) are presented before or alongside PowerShell examples.
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 presents backup storage options including Azure Blob Storage and File Share. The File Share examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file sharing methods (e.g., NFS, SMB mounting on Linux, or Linux authentication patterns). There are no examples or guidance for configuring on-premises backup storage for Linux clusters, nor any mention of Linux-specific tools or patterns. The documentation implicitly assumes Windows environments for on-premises scenarios.
Recommendations
  • Add examples and instructions for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB mounts on Linux).
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide authentication and path examples for Linux.
  • Explicitly mention any limitations or differences for Linux clusters in backup configuration and storage options.
  • Where authentication is discussed, include Linux-relevant patterns (e.g., Kerberos, username/password for SMB, NFS exports).
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 featured prominently and exclusively for several key operations (e.g., manual cluster upgrade). Windows-specific tools and registry settings are mentioned without Linux equivalents or guidance. Windows configuration details (e.g., disabling Windows Update via registry and template) are given before any Linux-specific advice, and Linux upgrade procedures are not covered in detail.
Recommendations
  • Provide Linux-specific examples for manual cluster upgrades, including equivalent shell commands (e.g., Bash) and package formats (deb, rpm).
  • Include instructions or references for disabling automatic updates and managing upgrades on Linux VMs, such as using apt or yum/dnf.
  • Balance PowerShell and CLI examples by offering Bash or shell script alternatives where possible, especially for cluster management tasks.
  • Clarify which steps are Windows-only and provide Linux alternatives or explicitly state when a step does not apply to Linux.
  • Add links or sections for Linux VM configuration best practices in Service Fabric clusters.
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 provides several examples and references that prioritize Windows and PowerShell, such as mentioning PowerShell APIs for client connections, referencing Windows-specific ARM templates, and describing Windows container networking scenarios. Linux equivalents are sometimes mentioned, but often after Windows, and Linux-specific examples or CLI commands are sparse or missing. The documentation also references Windows update orchestration and PowerShell-heavy DevOps tasks without Linux parity.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for cluster management and networking tasks.
  • Include Linux-specific ARM template samples and links, not just Windows-focused ones.
  • Clarify when features or recommendations apply to both Windows and Linux, and explicitly note any differences.
  • Add Linux container networking scenarios and troubleshooting tips, not just Windows container notes.
  • Reference Linux DevOps workflows (e.g., Azure CLI, bash scripts) in addition to PowerShell for operational tasks.
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, without offering equivalent CLI or script examples for Linux/macOS users. 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
  • Provide equivalent Azure CLI or REST API examples for each placement policy configuration, as these are cross-platform and widely used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform these tasks, including any supported tools or scripts.
  • If PowerShell is required for certain operations, clarify this and provide guidance or alternatives for non-Windows users.
  • Consider reordering examples or providing cross-platform instructions first, followed by Windows-specific details.
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 provides command-line examples exclusively using PowerShell cmdlets for Service Fabric application management tasks, with no mention of Linux shell equivalents or cross-platform CLI tools. This creates friction for Linux/macOS users, as PowerShell is traditionally a Windows-centric tool and not the default shell on Linux. There is no guidance on using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform options.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include Azure CLI or REST API examples for application management tasks where possible.
  • Explicitly note PowerShell examples are for Windows users, and provide links or instructions for Linux/macOS users to perform the same actions.
  • Consider reordering examples so that cross-platform options are presented 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 offer equivalent command-line examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API usage). PowerShell is presented first and exclusively as the shell-based method, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for managing node tags and service tag requirements, as these are cross-platform.
  • If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide usage notes.
  • Consider including Bash script examples or direct REST API calls for common operations.
  • Explicitly state platform compatibility for each method (PowerShell, C#, REST API) to guide users on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific instructions for scaling. There are no examples or guidance for Linux-based clusters, nor are Linux-native tools or commands mentioned.
Recommendations
  • Add equivalent Linux instructions for scaling standalone clusters, including examples using Bash, CLI, or REST API if available.
  • Clarify whether standalone clusters can be run on Linux, and if so, provide parity in documentation for Linux environments.
  • Reference Linux-native tools or commands (e.g., sfctl, Service Fabric CLI) where appropriate.
  • If scaling standalone clusters is Windows-only, explicitly state this limitation early in the documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides code examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, the PowerShell examples are Windows-specific, and there are no equivalent Linux CLI or bash examples. The documentation does not mention Linux tooling or provide guidance for Linux users on how to perform these operations, despite Service Fabric supporting containerized workloads on Linux. Windows/PowerShell examples are presented first and exclusively, which may create friction for Linux users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include bash or shell script examples for Linux users where applicable.
  • Explicitly mention how Linux users can perform auto scaling configuration, especially for containerized workloads.
  • Clarify any Windows-only limitations for PowerShell commands and point Linux users to alternative tooling.
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 the Cluster Resource Manager integration with Service Fabric cluster management. However, the only concrete example given for interacting with health reports uses a PowerShell cmdlet (Get-ServiceFabricPartitionHealth), with no mention of Linux/macOS equivalents or cross-platform CLI tools. 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.
  • Add a note clarifying that PowerShell examples are for Windows, and provide guidance for Linux/macOS users.
  • Where possible, show both Windows (PowerShell) and Linux/macOS (sfctl or REST API) commands side-by-side for parity.
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 with move cost, but does not offer equivalent examples for Linux environments (such as Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of Linux-native tools or cross-platform command-line alternatives, and PowerShell is presented before C# code samples.
Recommendations
  • Add Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are applicable on Linux (e.g., via PowerShell Core), or provide Bash equivalents if possible.
  • Clarify any platform-specific requirements for Service Fabric management commands, and link to cross-platform tooling documentation.
  • Consider presenting cross-platform examples (CLI, REST) before or alongside PowerShell to improve parity.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# API. PowerShell is featured as the primary CLI example, with no mention of Linux/macOS CLI alternatives (e.g., Azure CLI, REST API, or cross-platform Service Fabric CLI). This creates friction for Linux/macOS users who cannot use PowerShell natively. The C# API is also Windows-centric due to Service Fabric SDK support patterns.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Mention REST API options for programmatic configuration where possible.
  • Clarify if PowerShell examples require Windows or if cross-platform PowerShell Core is supported.
  • Explicitly state platform requirements for each method (e.g., 'PowerShell examples require Windows or PowerShell Core').
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 shows notable Windows bias. References and links are primarily or exclusively to Windows Server-specific guides (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 Linux-specific instructions, examples, or links, despite Service Fabric standalone clusters supporting both Windows and Linux. This creates friction for Linux users seeking upgrade guidance.
Recommendations
  • Add explicit instructions and links for upgrading Service Fabric standalone clusters running on Linux.
  • Provide Linux-specific examples for configuration changes and cluster upgrades.
  • Clarify which steps or tools are Windows-only and offer Linux alternatives where available.
  • Include references to Linux patch orchestration or manual patching guidance if POA is not available for Linux.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples and instructions using PowerShell and Azure CLI for cluster management tasks, such as managing certificates and opening application ports. While Azure CLI is cross-platform, PowerShell is traditionally Windows-centric, and the documentation mentions PowerShell before Azure CLI in multiple places. Additionally, the section on OS image upgrades references patching Windows operating systems specifically, with no mention of Linux node patching or parity.
Recommendations
  • Provide explicit Linux/macOS examples where PowerShell is mentioned, such as using Bash or Azure CLI commands on Linux.
  • Clarify when Azure CLI instructions are cross-platform and provide sample commands for Linux/macOS terminals.
  • If Service Fabric supports Linux clusters, include guidance or links for patching/upgrading Linux node OS images.
  • Where possible, avoid listing PowerShell before Azure CLI, or present both options equally.
  • Add notes or links for Linux-specific documentation if available, especially in sections referencing OS patching.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use in administrative examples creates friction for Linux users. The documentation also references Windows-specific behaviors (e.g., kernel driver logging) before Linux equivalents, but does acknowledge platform differences.
Recommendations
  • Add equivalent Linux CLI (sfctl) or Bash examples alongside PowerShell commands for service creation and updates.
  • Explicitly mention Linux administrative workflows and tools where PowerShell is referenced.
  • Where platform-specific differences exist, provide clear guidance or links to Linux documentation.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows-specific ones.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there are several instances of Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services) are mentioned first or exclusively in some sections, and examples or instructions for Linux users are often missing or less prominent. The documentation references Windows services and executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without clarifying Linux equivalents or processes. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly noted as unsupported. In lifecycle management and health monitoring, PowerShell and Windows-centric tools are listed before CLI or cross-platform options.
Recommendations
  • Where possible, provide Linux-specific instructions, examples, and tool references alongside Windows ones.
  • Clarify Linux equivalents for Windows services and executables, or note differences in architecture/processes.
  • Ensure CLI and cross-platform tools are presented equally or before Windows-only tools like PowerShell.
  • Add explicit guidance or links for Linux cluster creation and management, even if only to clarify current limitations.
  • Highlight differences and parity between Windows and Linux throughout, referencing the differences documentation as needed.
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 Azure Service Fabric, but Windows development tools (Visual Studio, PowerShell) are described first and in more detail, while Linux equivalents (Eclipse, Yeoman) are mentioned briefly. There are no concrete Linux-specific examples or walkthroughs, and the primary quickstart link points to a .NET/Windows-centric guide. This creates friction for Linux/macOS users seeking parity in development experience.
Recommendations
  • Provide parallel Linux/macOS examples and walkthroughs, especially in quickstart and getting started sections.
  • Include links to Linux/macOS-specific quickstart guides and documentation (e.g., service-fabric-quickstart-java.md or service-fabric-get-started-linux.md).
  • Describe Linux development tools and workflows (Eclipse, Yeoman, CLI) with equal detail as Windows tools (Visual Studio, PowerShell).
  • Ensure that example commands and screenshots are shown for both platforms where relevant.
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 discusses security for Azure Service Fabric clusters and standalone clusters, but consistently references Windows Server clusters for standalone scenarios. Links and examples for standalone clusters are exclusively for Windows, with no mention of Linux equivalents or guidance for securing standalone Linux clusters. Windows-specific tools (e.g., MakeCert.exe, Windows Server certificate service) are mentioned, and Windows authentication is described, but there is no coverage of Linux authentication or certificate management tools. The concept of Linux clusters is acknowledged, but practical instructions are missing.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters on Linux, including certificate management and authentication options.
  • Provide Linux-specific examples for certificate creation and installation (e.g., using OpenSSL or Linux certificate authorities).
  • Mention Linux authentication mechanisms or clarify if only certificate-based security is supported for Linux clusters.
  • Ensure parity in step-by-step instructions and references for both Windows and Linux standalone clusters.
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 command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and screenshots reinforce this. No Linux/macOS alternatives or instructions are provided for key steps such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Provide guidance for uploading application packages to Azure Storage using Azure CLI or azcopy, which are available on Linux/macOS.
  • Clarify which steps are platform-agnostic and which require Windows, and offer alternatives where possible.
  • Reorder examples so that cross-platform options are presented first or in parallel with Windows-specific instructions.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.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 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 suggest a Windows-first approach. However, the CLI commands (sfctl) are cross-platform and allow Linux/macOS users to perform the same tasks. No Linux-specific tools or shell examples are given, and PowerShell is a Windows-centric tool, though it is available on other platforms.
Recommendations
  • Clarify that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider presenting sfctl examples before PowerShell, or side-by-side, to emphasize Linux/macOS parity.
  • Explicitly mention that PowerShell commands are primarily for Windows users, while sfctl is recommended for Linux/macOS.
  • Provide example shell commands (bash/zsh) for common Linux workflows, if relevant.
  • Add a note about PowerShell Core availability on Linux/macOS, if PowerShell usage is intended to be cross-platform.
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 only PowerShell-based examples for reporting and evaluating Service Fabric health, with no equivalent Linux/macOS CLI or REST API examples. The example section uses Windows PowerShell cmdlets exclusively, and there is no mention of Service Fabric CLI (sfctl) or REST API usage, which are the primary tools for Linux/macOS users. This creates friction for non-Windows users attempting to follow the documentation.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and the standard tool for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic and useful for automation.
  • Explicitly mention that PowerShell examples are for Windows and provide links or inline examples for Linux/macOS users.
  • Update the 'How to report and check service health' and related links to clarify cross-platform tooling and provide parity in examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation covers both Windows and Linux clusters, but several sections show Windows bias. PowerShell is the only CLI example given for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. The ApplicationManifest.xml example assumes Visual Studio, a Windows-centric tool, and does not mention Linux workflows or editors. Enabling DNS service through the Azure portal is only available for Windows clusters, but this limitation is mentioned. Overall, Linux users are left to infer or research their own methods for several key tasks.
Recommendations
  • Provide Linux/Bash/Azure CLI examples for setting DNS names and managing services, especially for common tasks currently shown only with PowerShell.
  • Mention Linux-friendly editors and workflows for editing ApplicationManifest.xml (e.g., VS Code, nano, vim).
  • Clarify Linux-specific steps for enabling DNS service, including ARM template modifications and limitations, with explicit guidance.
  • Where features are Windows-only, make this clear at the start of each section to avoid confusion.
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 provides PowerShell examples and references PowerShell cmdlets for managing Service Fabric services, with no equivalent CLI or Linux/macOS instructions. PowerShell is a Windows-centric tool, and the absence of Azure CLI, Bash, or cross-platform examples creates friction for users on Linux or macOS. The C# example is cross-platform, but operational guidance (e.g., service creation, querying, health reporting) is PowerShell-focused.
Recommendations
  • Add Azure CLI examples for service creation and management tasks, as Azure CLI is cross-platform.
  • Include Bash or shell script equivalents where appropriate.
  • Clarify which management operations can be performed using REST APIs, and provide sample REST calls.
  • Explicitly note PowerShell examples are for Windows, and link to Linux/macOS alternatives.
  • Ensure references to management tools are not exclusively PowerShell; mention cross-platform options where available.
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 provides examples and tooling references that prioritize Windows-centric workflows, such as PowerShell cmdlets and Visual Studio integration, with limited or less prominent coverage of Linux/macOS equivalents. While sfctl and Jenkins are mentioned, the examples and explanations are weighted toward Windows tools and patterns, and Linux/macOS users may need to infer or research their own workflows.
Recommendations
  • Provide explicit Linux/macOS command-line examples for common tasks, such as using sfctl and shell scripts for application deployment.
  • Include a section or table comparing Windows and Linux/macOS workflows for managing Service Fabric applications across environments.
  • Highlight cross-platform tools (like sfctl) earlier and more prominently, ensuring parity in example depth and clarity.
  • Add links or references to Linux/macOS-specific documentation or community resources.
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 for Azure Service Fabric container application manifest examples exhibits a moderate Windows bias. The examples and explanations are based on the Windows Server 2016 Container Sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths) are mentioned first or exclusively. There is little to no explicit mention of Linux equivalents, and no Linux-specific manifest samples or guidance are provided, even though Service Fabric supports Linux containers.
Recommendations
  • Include parallel Linux-based manifest examples, or clarify which elements differ for Linux clusters.
  • Add notes or sections explaining how to obtain OS build/version information on Linux (e.g., using 'cat /etc/os-release' or 'uname -r').
  • Provide Linux file path examples (e.g., '/mnt/VolumeTest/Data') alongside Windows paths.
  • Clarify any differences in certificate handling, volume drivers, or container isolation modes between Windows and Linux clusters.
  • Reference Linux container samples in addition to the Windows Server 2016 Container Sample.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric image store connection string frequently references PowerShell and Windows-centric workflows, such as retrieving the cluster manifest via PowerShell and publishing through Visual Studio. There are no examples or explicit instructions for Linux/macOS users, nor are cross-platform CLI alternatives (e.g., Azure CLI, Bash) mentioned. The 'Next steps' section links only to PowerShell-based deployment guidance, further reinforcing a Windows-first perspective.
Recommendations
  • Add examples for retrieving the cluster manifest using Azure CLI, Bash, or REST API, and clarify which methods work cross-platform.
  • Include deployment instructions for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell and Visual Studio workflows.
  • Mention and link to documentation for cross-platform tools where available, ensuring parity in guidance for non-Windows environments.
  • Explicitly state platform requirements for any Windows-only steps, and provide alternatives for other operating systems where possible.
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 ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples shows moderate Windows bias. It references Windows-specific concepts (such as running services as local admin, NETWORKSERVICE, and .bat scripts), and mentions using the ServiceFabric PowerShell module for service creation. Examples and explanations use Windows-centric tools and patterns (e.g., .exe and .bat files), with no Linux-specific equivalents or guidance. Linux support for Service Fabric is not acknowledged, and Linux/macOS users may need to infer how to adapt these instructions.
Recommendations
  • Add explicit notes or examples for Linux Service Fabric clusters, such as using shell scripts (.sh) instead of .bat files, and referencing Linux service accounts.
  • Mention Linux-compatible tools for deploying and managing Service Fabric applications (e.g., Service Fabric CLI, sfctl) alongside PowerShell.
  • Clarify which manifest elements and patterns are cross-platform, and which are Windows-only.
  • Provide guidance on running services under Linux user accounts, and how to configure RunAsPolicy for Linux environments.
  • Where .exe or .bat files are referenced, include Linux equivalents (.sh, ELF binaries) in examples.
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 detailed coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, HTTP.sys (Windows-only) is described first and in greater detail, with explicit code samples and endpoint configuration steps. The documentation notes HTTP.sys is Windows-only, but does not provide equivalent Linux/macOS-specific troubleshooting, deployment, or configuration guidance. Kestrel (cross-platform) is covered well, but Windows-specific tools (e.g., netsh) and patterns are mentioned without Linux alternatives. There are no explicit Linux/macOS code samples or platform-specific notes for non-Windows users.
Recommendations
  • Reorder sections so that Kestrel (cross-platform) is described before HTTP.sys (Windows-only), emphasizing its suitability for Linux/macOS.
  • Add explicit Linux/macOS deployment notes, including any Service Fabric configuration steps or troubleshooting tips unique to those platforms.
  • Where Windows tools (e.g., netsh) are mentioned, clarify that these are not required for Kestrel and provide Linux/macOS equivalents or state when they are not applicable.
  • Include example code snippets or configuration files for Linux/macOS environments, especially for ServiceManifest.xml and endpoint configuration.
  • Add a summary table or decision tree at the top to help users quickly identify which web server and configuration to use based on their OS.
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_first ⚠️ windows_tools
Summary
The documentation page provides several examples and deployment instructions using PowerShell commands and Windows file paths, such as 'PS C:\>' and references to 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'. Linux equivalents are mentioned only briefly (e.g., the certificate store path), and there are no Linux/macOS CLI examples or deployment instructions. The documentation assumes familiarity with Windows tooling and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Include Linux/macOS equivalents for PowerShell deployment commands, such as Azure CLI or Service Fabric CLI (sfctl) examples.
  • Document Linux/macOS file paths and installation locations for Service Fabric SDK and schema files.
  • Provide explicit instructions or examples for deploying Service Fabric applications on Linux clusters, including endpoint configuration and certificate management.
  • Ensure that references to tools and commands are cross-platform or clearly indicate platform-specific sections.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page generally describes Service Fabric concepts in a cross-platform manner, but some terminology and examples are Windows-centric. Specifically, the 'Node' definition references an auto-start Windows service (FabricHost.exe) and Windows executables before mentioning Linux support. The code package section also emphasizes EXE/DLL files, which are Windows formats, and only later clarifies that guest executables can run on Windows or Linux. Windows-specific tools and patterns (Windows service, EXE/DLL) are mentioned first, with Linux equivalents implied but not detailed.
Recommendations
  • When describing nodes, clarify how Service Fabric runs on Linux (e.g., mention the equivalent Linux processes/services alongside Windows services).
  • In the code package section, explicitly state Linux executable formats (e.g., ELF binaries) and how Service Fabric handles them.
  • Provide examples or explanations for both Windows and Linux wherever platform-specific terminology (services, executables) is used.
  • Ensure that cross-platform parity is clear in all sections, especially where Windows-specific terms are introduced.
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 in Service Fabric exclusively references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations, with no mention of equivalent CLI commands, REST APIs, or Linux/macOS-compatible tooling. All operational examples and API references are Windows/PowerShell-centric, and there are no Linux-specific instructions or parity examples.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI or REST API equivalents for managing replicas (removal, restoration, querying).
  • Document how to perform these operations on Linux-based Service Fabric clusters, if supported.
  • Clarify if certain APIs or administrative tasks are only available via PowerShell, and provide alternative guidance for non-Windows users.
  • Add explicit notes or tables indicating platform/tool compatibility for each administrative operation.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with explicit Windows command-line syntax and references to PowerShell cmdlets. There are no equivalent examples or guidance for Linux/macOS users, such as Bash, CLI, or cross-platform scripting. PowerShell is presented before REST, and REST is only briefly mentioned, with no concrete Linux-friendly walkthroughs. This creates friction for non-Windows users, who must infer how to perform these tasks without direct examples.
Recommendations
  • Add equivalent Bash or Azure CLI examples for health reporting tasks, especially for sending reports and querying health status.
  • Clarify which PowerShell commands (if any) are available on Linux/macOS, or provide alternatives if not.
  • Expand REST API usage sections with step-by-step Linux/macOS-friendly instructions, including sample curl commands.
  • Explicitly mention cross-platform options and limitations for Service Fabric management and health reporting.
  • Consider reordering examples so REST or CLI options are shown before or alongside PowerShell.
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 page for the Fault Analysis Service overview in Azure Service Fabric demonstrates a moderate Windows bias. PowerShell is the only command-line example provided, and there is no mention of Linux or cross-platform command-line alternatives (such as Bash, CLI, or REST API usage). The documentation refers to installing the Service Fabric SDK and using PowerShell modules, but does not clarify whether equivalent tooling or instructions exist for Linux/macOS users. The C# example is platform-neutral, but the operational guidance is Windows/PowerShell-centric.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, such as using Bash, Azure CLI, or REST API to interact with the Fault Analysis Service.
  • Clarify whether the Service Fabric SDK and PowerShell modules are available or supported on Linux/macOS, and provide alternative steps if not.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally, or at least mention cross-platform options before Windows-specific ones.
  • Include a note about platform support and limitations for the Fault Analysis Service, so users are aware of any OS-specific constraints.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page focuses exclusively on configuring Service Fabric application upgrades using Visual Studio and PowerShell, both of which are primarily Windows tools. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives, CLI usage, or cross-platform tooling. This creates friction for users on non-Windows platforms, as the upgrade workflow is presented as Windows-centric.
Recommendations
  • Add instructions for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where applicable.
  • Include examples for configuring upgrade parameters and health policies via command-line or configuration files, not just through Visual Studio dialogs.
  • Clarify which steps are Windows-only and provide alternative guidance for Linux/macOS users, such as using VS Code or other editors for manifest editing.
  • Reference official documentation for Service Fabric management on Linux clusters, if available.
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 PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) examples. In some sections, only PowerShell is shown for querying public IPs, with CLI mentioned but not exemplified. There are also cases where Windows tools (PowerShell) are referenced more heavily than Linux/macOS equivalents, and some example queries (e.g., for public IPs) lack explicit Linux/macOS CLI parity.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Ensure every PowerShell example has an equivalent Azure CLI example, especially for querying and managing resources.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide bash syntax where appropriate.
  • Where possible, add Linux/macOS-specific notes or troubleshooting tips if there are platform differences.
  • Review tab ordering so that CLI is not deprioritized after PowerShell.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation occasionally references Windows-specific scenarios (e.g., Windows VM activation, Windows updates) before Linux equivalents and does not provide Linux-specific examples or parity in some sections. While Linux is mentioned (e.g., access to Linux package managers), examples and troubleshooting links are more detailed for Windows. There are no CLI or script examples that demonstrate Linux-specific migration or configuration patterns, and PowerShell is mentioned alongside Azure CLI, but no Bash or Linux shell examples are provided.
Recommendations
  • Provide Linux-specific migration examples, such as using Bash scripts or Linux CLI workflows.
  • Include troubleshooting links for common Linux scenarios (e.g., SSH connectivity, package manager access) similar to the Windows VM activation troubleshooting link.
  • Ensure that references to OS-specific requirements (e.g., updates, activation) mention both Windows and Linux in equal detail.
  • Add explicit Linux-focused guidance for outbound connectivity (e.g., apt/yum updates, SSH key management).
  • Where PowerShell is referenced, also provide equivalent Bash or shell script examples for Linux/macOS users.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and ARM templates. While the CLI and ARM template sections are cross-platform, PowerShell examples are given equal prominence and detail, and in some cases, appear before Linux-specific guidance. The ARM template section references both Linux and Windows getting started articles, but the CLI and PowerShell sections do not clarify OS context. No explicit Linux shell (bash) examples are provided, and PowerShell (Windows-centric) is presented as a primary method alongside CLI.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, especially for Azure CLI commands.
  • Clarify that Azure CLI commands are cross-platform and can be run from Linux/macOS terminals.
  • Where PowerShell is shown, provide equivalent bash commands or note that PowerShell Core is available cross-platform.
  • In step-by-step sections, alternate or parallelize examples for Linux and Windows, rather than presenting PowerShell as a default.
  • Ensure that links to 'getting started' articles for Linux and Windows are equally visible and not Windows-first.
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 significantly more detailed, including full networking setup and resource creation, while CLI examples are minimal. PowerShell is a Windows-centric tool, and its prominence and depth compared to CLI may create friction for Linux/macOS users. Additionally, the PowerShell examples are shown before CLI in some sections, and there are no Bash or Linux shell-specific examples for tasks like networking setup, which are only covered in PowerShell.
Recommendations
  • Expand Azure CLI examples to include full resource creation steps (networking, NIC, NSG, etc.) similar to PowerShell, using Bash syntax and variables.
  • Ensure CLI examples are as comprehensive as PowerShell, so Linux/macOS users have parity in guidance.
  • Consider adding explicit Bash scripts for common Linux/macOS workflows, especially for networking setup.
  • Where possible, present CLI examples before PowerShell, or clarify that both are fully supported and provide equivalent coverage.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight Windows-first bias in some sections, such as listing Windows container runtimes in more detail and referencing IIS/ASP.NET MVC scenarios (which are Windows-specific) before Linux examples. Windows tools (IIS, Mirantis Container Runtime, DockerEE) are mentioned explicitly, while Linux is referenced more generically (just 'Docker'). Linux examples and tutorials are present and linked, but Windows scenarios and tools tend to be described with more specificity.
Recommendations
  • Ensure Linux container runtimes are described with equal specificity as Windows (e.g., mention supported Docker versions, alternatives if any).
  • When listing container scenarios, provide Linux-specific examples (e.g., Apache/Nginx lift-and-shift, Python/Node.js workloads) alongside Windows/IIS scenarios.
  • Balance the order of presenting Windows and Linux examples/tutorials, or alternate their placement to avoid perceived prioritization.
  • Expand on Linux-specific capabilities or limitations where relevant, matching the detail given to Windows features.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management shows a mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned exclusively in the default skip list, and no Linux container image examples (e.g., Ubuntu, Alpine) are provided. The examples and explanations focus on Windows images first, with Linux images only referenced generically in a regex example. There are no explicit Linux-specific configuration examples or guidance.
Recommendations
  • Include examples of Linux container images (e.g., 'docker.io/library/ubuntu:latest', 'mcr.microsoft.com/dotnet/runtime') in the ContainerImagesToSkip setting.
  • Clarify that the cleanup and management features apply equally to Linux containers, if applicable.
  • Add a note or section describing any differences in behavior or configuration for Linux-based Service Fabric clusters.
  • Provide parity in documentation by showing both Windows and Linux container management scenarios.
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 demonstrates a mild Windows bias by referencing Windows file paths (e.g., installation of schemas to C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) and mentioning Visual Studio as a primary tool for packaging and deploying guest executables. There is no explicit mention of Linux equivalents for SDK installation paths, packaging tools, or alternative development environments, and Windows-centric patterns are presented first.
Recommendations
  • Add information about installing the Service Fabric SDK and locating schema files on Linux/macOS systems.
  • Include examples or references for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) or on Linux/macOS environments.
  • Mention alternative development environments (such as VS Code or command-line utilities) for users not on Windows.
  • Clarify that Service Fabric supports guest executables on both Windows and Linux clusters, and provide links to Linux-specific documentation where appropriate.
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 (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics responses and installing the application health extension. However, there are several instances of Windows bias: PowerShell examples are often presented before or alongside Linux equivalents, Windows extension types (ApplicationHealthWindows) are shown first in some code blocks, and Windows-specific tools (PowerShell cmdlets) are given equal prominence to cross-platform CLI commands. The REST API and Azure CLI examples are cross-platform, but some sections (such as the PowerShell install and response server) are more detailed than their Linux counterparts.
Recommendations
  • Ensure Linux and Windows examples are presented with equal detail and prominence; consider alternating which is shown first.
  • In code samples where both ApplicationHealthLinux and ApplicationHealthWindows are referenced, clarify which to use for each OS and provide explicit examples for both.
  • Add more troubleshooting and verification steps for Linux environments, such as systemd service setup or firewall configuration.
  • Where PowerShell scripts are provided, ensure Bash/Linux equivalents are equally comprehensive.
  • Review sample outputs and ensure they do not default to Windows extension types unless contextually appropriate.
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 given equal prominence to CLI examples, and in some sections (such as the restart operation), PowerShell is shown after CLI but with detailed scripting. There is a slight 'windows_first' bias in that PowerShell is featured as a primary method alongside CLI, and no explicit mention is made of Linux/macOS shell environments (e.g., Bash), though the Azure CLI commands are cross-platform. No Windows-only tools or patterns are exclusively mentioned, and all tasks can be completed using Azure CLI, which works on Linux/macOS. There are no missing Linux examples, but the documentation could clarify CLI parity and avoid implying PowerShell is required.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is optional.
  • Consider mentioning Bash or shell scripting for Linux/macOS users where appropriate.
  • Add a note in the PowerShell sections that these commands are for users who prefer PowerShell, and that all operations can be performed using Azure CLI on any OS.
  • Ensure that CLI examples are shown first or equally with PowerShell to avoid perceived prioritization of Windows environments.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides detailed, Linux-specific guidance and examples. However, the introductory section and overview spend several paragraphs describing Windows Server 2016 time sync improvements and Windows infrastructure before discussing Linux-specific mechanisms. All technical instructions, examples, and configuration steps are Linux-centric, with no PowerShell or Windows tool bias in the practical guidance.
Recommendations
  • Move the Windows Server 2016 time sync discussion to a background or reference section, or summarize it more briefly before focusing on Linux-specific details.
  • Begin the page with Linux VM time sync concepts and Azure-specific mechanisms, referencing Windows infrastructure only as necessary for context.
  • Ensure that Linux instructions and examples are always presented first and most prominently on Linux-focused documentation pages.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation is generally Linux-focused, as expected for the Key Vault VM Extension for Linux. However, there are several instances where Windows-centric tools and patterns (notably Azure PowerShell) are presented prominently or before Linux-native alternatives. PowerShell deployment instructions are detailed and appear before Azure CLI examples, and troubleshooting guidance references Azure PowerShell before Azure CLI. There is also a reference to a Windows VM access policy guide in the template deployment section, which may confuse Linux users.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Clarify that Azure PowerShell is optional and primarily for Windows users; highlight CLI as the recommended approach for Linux.
  • In troubleshooting sections, show Azure CLI commands first, and add Bash scripting examples where appropriate.
  • Remove or clarify references to Windows-specific documentation (e.g., access policy guides for Windows VMs) and link to Linux-relevant guides.
  • Add explicit notes about tool compatibility (e.g., Azure PowerShell on Linux) if PowerShell instructions are retained.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence despite PowerShell being primarily a Windows tool. The CLI example (cross-platform) is shown first, which is positive, but the inclusion of PowerShell may create a slight Windows-centric impression. No Linux-specific tools or shell examples are provided, but the CLI is sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding a brief Bash shell example for parsing CLI output, if relevant.
  • Explicitly state that PowerShell is primarily for Windows users, and CLI is recommended for cross-platform usage.
  • Ensure that future documentation does not assume PowerShell as the default for automation unless the audience is Windows-focused.
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 example tooling: PowerShell examples are given alongside CLI and ARM template, but PowerShell is a Windows-centric tool and is presented before Linux-native alternatives. Additionally, in the portal instructions, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access. There are no missing Linux examples, and Linux-specific validation (SBInfo tool) is called out in best practices.
Recommendations
  • Present SSH (Linux) and RDP (Windows) access instructions in parallel or with equal prominence.
  • Clarify that PowerShell can be used cross-platform, or provide Bash scripting examples for Linux users where appropriate.
  • Consider listing CLI and template methods before PowerShell, as these are more platform-neutral.
  • Continue to highlight Linux-specific validation steps, as done with SBInfo.
GitHub Create Pull Request