Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 426-450 of 718 flagged pages
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only command example for bypassing Infrastructure Service throttling, with no mention of Linux/macOS equivalents or cross-platform alternatives. The use of Service Fabric Explorer (a GUI tool) is referenced, but command-line guidance is Windows-centric. There are no bash, CLI, or REST API examples for Linux users.
Recommendations
  • Include equivalent bash or Azure CLI commands for Linux/macOS users.
  • Document REST API or cross-platform alternatives for cluster management tasks.
  • Clarify whether the PowerShell cmdlet is available via Azure CLI or other non-Windows tools.
  • Add explicit notes about platform compatibility for all command examples.
GitHub Create Pull Request
Service Fabric Add a virtual machine scale set extension to a Service Fabric managed cluster node type ...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates notable Windows bias. The only CLI command provided is a PowerShell cmdlet (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or cross-platform alternatives. The ARM template examples exclusively use the 'KeyVaultForWindows' extension type and do not show Linux equivalents (e.g., KeyVaultForLinux). Windows-specific extension types and patterns are referenced before any Linux options, and no guidance is given for Linux/macOS users.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for adding VM extensions.
  • Include ARM template examples using Linux-compatible extension types (e.g., KeyVaultForLinux) and clarify when to use each.
  • Explicitly mention Linux/macOS support and any differences in extension configuration or behavior.
  • List both Windows and Linux extension types in documentation, with guidance on choosing the appropriate one.
  • Ensure that instructions for critical tasks (e.g., disk encryption) include Linux-specific steps or references.
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 →
Scanned: 2026-01-13 06:17
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. Azure PowerShell is referenced multiple times as the primary example for cluster management actions, with direct links to PowerShell cmdlets. There are no explicit Linux/macOS command examples or callouts for cross-platform usage, and PowerShell is mentioned before Azure CLI or other platform-neutral tools. The best practices section and examples focus on PowerShell, which is traditionally associated with Windows, despite the existence of cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for deleting, restarting, or reimaging NodeTypes/VMSS.
  • Explicitly mention that Azure CLI and Bicep are cross-platform and suitable for Linux/macOS users.
  • Reorder tool recommendations to list platform-neutral tools (Azure CLI, Bicep, ARM templates) before PowerShell.
  • Provide sample workflows or command snippets for Linux/macOS users using Azure CLI and sfctl.
  • Clarify that PowerShell is available cross-platform, but highlight CLI and sfctl as alternatives.
GitHub Create Pull Request
Service Fabric Monitoring data reference for Azure Service Fabric ...les/service-fabric/monitor-service-fabric-reference.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools (Performance Monitor), listing Windows performance counters exclusively, and omitting Linux equivalents or instructions. There are no examples or guidance for monitoring Service Fabric on Linux clusters, nor mention of Linux performance metrics or tools.
Recommendations
  • Add equivalent Linux performance counter categories and metrics (e.g., using /proc, sysstat, or collectd).
  • Include instructions or examples for collecting metrics on Linux nodes, such as using Azure Monitor agent on Linux.
  • Reference Linux monitoring tools (e.g., atop, htop, sar) alongside Windows Performance Monitor.
  • Clarify which metrics and counters are available on Linux clusters and how to access them.
  • Provide parity in documentation structure, ensuring Linux and Windows are both covered in each section.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (EventStore APIs, Diagnostics Agent, Event Viewer, ETW) are mentioned before or in more detail than their Linux equivalents. Some features, such as EventStore APIs and Diagnostics Agent, are explicitly stated to be Windows-only, with Linux alternatives referenced only briefly or in separate documentation. Examples and tutorials focus on .NET/Windows scenarios, with Linux-specific guidance often relegated to separate links or notes. Linux monitoring options are mentioned, but not with the same depth or clarity as Windows options.
Recommendations
  • Provide parallel Linux examples and tutorials for all monitoring scenarios, especially where Windows-only guides are referenced.
  • Clarify Linux equivalents for Windows tools (e.g., show how to access and query Service Fabric events on Linux clusters, including LTTng and Syslog usage).
  • Ensure that Linux monitoring configuration steps are included inline, not just as links to other pages.
  • Highlight cross-platform tools and approaches first, then discuss OS-specific details.
  • Add explicit Linux/macOS instructions for agent setup, event querying, and application logging where currently only Windows/.NET examples are given.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster using the Azure portal ...es/service-fabric/quickstart-managed-cluster-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on the Azure portal GUI and does not provide any command-line examples for certificate management, cluster deployment, or resource cleanup. The only mention of operating systems is that the deployed nodes are Windows Server 2019 VMs; there is no discussion of Linux-based clusters or how Linux/macOS users can interact with the cluster (e.g., importing certificates, accessing Service Fabric Explorer, or using CLI tools). Steps like importing certificates assume familiarity with Windows certificate stores, and there is no guidance for Linux/macOS users on equivalent procedures.
Recommendations
  • Provide command-line instructions (using Azure CLI, Bash, or PowerShell) for all major steps, including resource group creation, Key Vault setup, certificate generation, and cluster deployment.
  • Include guidance for importing and using certificates on Linux and macOS systems, such as using OpenSSL and browser certificate stores.
  • Clarify whether Service Fabric managed clusters can be deployed with Linux nodes, and if so, provide instructions and examples.
  • Explicitly mention cross-platform compatibility in prerequisites and throughout the guide.
  • Add screenshots or instructions for Linux/macOS environments where relevant (e.g., browser certificate prompts, certificate import steps).
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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (Active Directory, gMSA, BitLocker) are described in detail, while Linux equivalents are either missing, referenced only in passing, or marked as TODO. Examples and guidance for Linux users (e.g., disk encryption, service accounts) are notably absent or less prominent. Windows tools and patterns (e.g., PowerShell, BitLocker) are mentioned without Linux alternatives.
Recommendations
  • Add explicit Linux examples for service account management, including how to run services under different Linux users/groups.
  • Provide guidance and examples for encrypting disks/data at rest on Linux clusters, referencing supported Linux technologies (e.g., dm-crypt, LUKS).
  • Include Linux-specific instructions for certificate management and container security, such as how to import certificates into Linux containers.
  • Balance references to Windows-only features (Active Directory, gMSA, BitLocker) with Linux equivalents or note their absence and provide workarounds.
  • Ensure that examples and walkthroughs are provided for both Windows and Linux environments, ideally side-by-side.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric application secrets ...fabric/service-fabric-application-secret-management.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents a platform-agnostic overview but exhibits Windows bias in several areas. The only concrete scripting example for deploying secrets uses PowerShell, with no equivalent Linux CLI (e.g., Bash, sfctl) example. Windows tools and patterns (PowerShell, C#) are mentioned first and exclusively in scripting contexts. While certificate setup is split between Windows and Linux, the main body of the documentation and code samples are Windows-centric, with Linux parity implied but not demonstrated.
Recommendations
  • Add explicit Linux/Bash/sfctl examples for application deployment and parameter overrides, parallel to the PowerShell example.
  • Mention Linux tools and workflows alongside Windows tools, not just in separate setup links.
  • Clarify any platform-specific differences in manifest handling or secret injection.
  • Ensure scripting and automation guidance is provided for both platforms in all relevant sections.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing PowerShell and Visual Studio (Windows-only tools) in both structure and examples. The parameters sections for PowerShell and Visual Studio are presented first and in greater detail, with example formats specific to PowerShell (e.g., hashtable syntax). Linux/macOS equivalents (SFCTL CLI) are covered in a separate, later section, with less emphasis and no example commands. There are no explicit Linux/macOS shell examples, and the documentation does not mention cross-platform usage patterns or differences. The 'Next steps' section also lists Windows-centric tutorials before Linux equivalents.
Recommendations
  • Present SFCTL (CLI) examples and parameters alongside PowerShell/Visual Studio, not in a separate section.
  • Provide explicit Linux/macOS shell command examples for SFCTL, including parameter usage.
  • Add a table or summary comparing PowerShell, Visual Studio, and SFCTL usage for each parameter.
  • Mention platform compatibility and highlight any differences in behavior or syntax between Windows and Linux/macOS tools.
  • Ensure 'Next steps' lists Linux/macOS tutorials with equal prominence and order.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only command-line example provided for resource removal, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Windows tooling (PowerShell, Remove-AzResource) is referenced exclusively and prominently, while Linux-friendly alternatives (Azure CLI, Bash, REST via curl) are only mentioned in passing or not at all. The 'Next steps' section lists PowerShell before CLI, further reinforcing Windows-first patterns.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell commands, especially for resource removal and management.
  • Explicitly mention cross-platform tools and workflows, such as using Azure CLI or REST API via curl.
  • Reorder or parallelize 'Next steps' to show CLI and PowerShell equally, or mention CLI first to balance.
  • Clarify that all operations can be performed from Linux/macOS environments and provide links to relevant cross-platform documentation.
  • Where PowerShell is referenced, note its availability on Linux/macOS, or suggest alternatives if features differ.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through the heavy use of PowerShell cmdlets for operational examples and automation. Windows-specific tools (PowerShell) are consistently mentioned alongside .NET APIs and REST operations, but Linux equivalents (such as Azure CLI or Service Fabric CLI 'sfctl') are rarely referenced directly in the main workflow steps. In most cases, PowerShell is listed before REST or other cross-platform options, and there are no explicit Linux/macOS command examples or instructions, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI and Service Fabric CLI (sfctl) command examples for each operational step, especially for deployment, upgrade, removal, and cleanup tasks.
  • Explicitly mention cross-platform tools (CLI, REST) before or alongside PowerShell, rather than after.
  • Add Linux/macOS-specific instructions or notes where workflows differ, or where additional setup is required.
  • Provide example scripts for common Linux shell environments (bash/zsh) where automation is discussed.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing Visual Studio and PowerShell upgrade tutorials as the only explicit next steps, both of which are primarily Windows tools. There are no Linux/macOS equivalents or cross-platform CLI examples provided, and Windows-centric tools are mentioned before any alternatives.
Recommendations
  • Add explicit instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
  • Include Linux/macOS-specific examples or tutorials alongside Visual Studio and PowerShell guides.
  • Reorder the 'Next steps' section to present cross-platform options first or in parallel with Windows-specific tools.
  • Clarify which tools are Windows-only and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Service Fabric Troubleshooting application upgrades ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively using PowerShell commands and outputs for all troubleshooting examples, with no mention of Linux or cross-platform CLI equivalents. All command-line instructions rely on PowerShell cmdlets, which are traditionally Windows-centric, and there is no guidance for users running Service Fabric on Linux or macOS. The 'Next steps' section also prioritizes Visual Studio (Windows-only) and PowerShell tutorials, further reinforcing the Windows-first approach.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Add explicit instructions and troubleshooting steps for Linux-based Service Fabric clusters, including relevant commands and expected outputs.
  • Clarify which commands are Windows-only and offer alternatives for non-Windows environments.
  • Reorder or balance 'Next steps' to include Linux/macOS tooling (e.g., sfctl, REST API) alongside Windows tools.
  • Note any platform-specific limitations or differences in troubleshooting workflows.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent example for Linux/macOS users (e.g., using Azure CLI, REST API, or Service Fabric CLI). Windows-specific tools and APIs (PowerShell cmdlets, http.sys) are referenced exclusively or first, and there is no mention of Linux-compatible upgrade workflows. The troubleshooting and next steps sections also prioritize Windows tools (Visual Studio, PowerShell) without Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for application upgrade operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify which steps are platform-specific.
  • Provide troubleshooting and upgrade guidance for Linux clusters, including links to relevant documentation.
  • Avoid referencing Windows-specific APIs (e.g., http.sys) without noting their platform limitations or providing Linux context.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the backup storage section, where file share examples and authentication methods are described exclusively using Windows paths (\\StorageServer\BackupStore) and Windows authentication mechanisms. There is no mention of Linux-compatible file share paths (e.g., NFS mounts), nor are Linux authentication patterns or examples provided. The documentation also refers to 'Integrated Windows Authentication' without alternatives for Linux environments. This can create friction for Linux users deploying Service Fabric clusters outside Windows environments.
Recommendations
  • Add examples for Linux-compatible file share paths (e.g., NFS mounts like /mnt/backupstore) and clarify support for SMB/NFS on Linux clusters.
  • Document authentication options for file shares on Linux, such as using mount credentials or Kerberos, and provide example configurations.
  • Explicitly state platform compatibility for each backup storage type and clarify any limitations or required steps for Linux/macOS clusters.
  • Reorder examples to present platform-neutral or Linux options alongside Windows, rather than Windows-first.
  • Include troubleshooting or notes for Linux users regarding file share integration and authentication.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the Management subsystem section, where PowerShell cmdlets are mentioned as the primary tooling for provisioning, deploying, and managing Service Fabric applications. There is no mention of equivalent Linux/macOS tools or CLI commands, nor are cross-platform alternatives discussed. The transport subsystem also references 'Windows security' alongside X509 certificates, but does not clarify Linux support. No explicit Linux/macOS examples or parity are provided throughout the page.
Recommendations
  • Include references to cross-platform management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Add explicit examples or documentation links for Linux/macOS users to perform management tasks (provision, deploy, patch, upgrade, de-provision).
  • Clarify the transport subsystem's support for Linux security mechanisms and provide details on certificate management for non-Windows platforms.
  • Ensure that tooling and command references are presented in a platform-neutral or platform-inclusive manner.
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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for cluster upgrades without Linux alternatives. Windows-specific configuration (e.g., registry keys, Windows Update settings) is described in detail, while Linux equivalents are missing. Upgrade instructions and examples focus on Windows tools and patterns, with Linux instructions relegated to links in the 'Next steps' section.
Recommendations
  • Provide equivalent Linux shell (bash) examples for all PowerShell commands, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for VM OS upgrades (e.g., disabling unattended-upgrades or apt settings).
  • Mention Linux tools and patterns alongside Windows ones, not just in 'Next steps'.
  • Add instructions for handling Linux package formats (deb/rpm) in upgrade scenarios.
  • Ensure that Windows-specific registry/configuration advice is paired with Linux equivalents or notes.
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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Critical operational steps (such as scaling in/out nodes) are described exclusively with PowerShell commands and Windows-centric tools, with no equivalent Linux CLI or script examples. The only manual command-line instructions use PowerShell, and references to Service Fabric Explorer and related commands assume a Windows environment. Linux alternatives (e.g., Service Fabric CLI, Bash, or REST API) are not mentioned, and Windows tools/patterns are presented first and exclusively in operational sections.
Recommendations
  • Add equivalent Linux/Bash/Service Fabric CLI (sfctl) examples for all PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState).
  • Explicitly mention and link to Linux operational guides for scaling and node management.
  • Clarify which steps are OS-agnostic and which require platform-specific tooling.
  • Where C# SDK examples are given, note cross-platform compatibility and provide guidance for Linux users.
  • Reorder or parallelize instructions so that Linux and Windows approaches are presented together, not Windows-first.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows and PowerShell tools are referenced before or more prominently than Linux equivalents, especially in API and DevOps sections. Some examples and ARM templates are Windows-specific, and PowerShell is mentioned as the primary client API use case. Linux-specific instructions and examples are less detailed or referenced after Windows. Windows container networking and update scenarios are described in detail, while Linux equivalents are less emphasized.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for networking and API access.
  • Include Linux-specific ARM template samples and reference them equally with Windows ones.
  • Clarify when instructions or port rules differ for Linux clusters, and provide explicit Linux guidance.
  • Add more detail for Linux container networking scenarios, including best practices and troubleshooting.
  • Balance references to Windows and Linux in introductory and summary sections, ensuring parity in guidance and links.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned first or exclusively in several sections, with Windows examples often preceding Linux equivalents. Some features, such as Windows Defender and security baselines, are only discussed for Windows, and Linux alternatives are not provided. While Linux instructions are present for certificate encryption, other areas lack Linux parity or present Windows as the default platform.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Provide Linux equivalents or alternatives for Windows-specific tools (e.g., suggest Linux antimalware solutions where Windows Defender is discussed).
  • Avoid language that implies Windows is the default or preferred platform.
  • Add references to Linux security baselines and configuration management tools (e.g., CIS benchmarks, Ansible, Chef) where Windows DSC and baselines are mentioned.
  • Where Windows-specific features are described, explicitly state Linux support status and link to Linux documentation.
  • Balance example ordering so Linux and Windows are treated equally.
GitHub Create Pull Request
Service Fabric Set up Microsoft Entra ID for client authentication in the Azure portal ...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions and examples for configuring Microsoft Entra ID authentication for Service Fabric clusters, but all command-line connection examples use PowerShell, which is primarily a Windows tool. There are no equivalent Linux/macOS CLI examples (e.g., Azure CLI, REST API, or cross-platform SDK usage), and troubleshooting steps reference PowerShell scripts. Windows-specific options (such as configuring authentication for existing clusters) are mentioned, while Linux users are directed to do setup only before cluster creation. There is a known issue noted for Linux clusters, but no Linux-specific guidance or workarounds are provided.
Recommendations
  • Add equivalent Azure CLI or REST API examples for connecting to Service Fabric clusters with Microsoft Entra ID authentication on Linux/macOS.
  • Include instructions or references for using cross-platform SDKs (e.g., .NET Core, Python) to connect to clusters.
  • Provide troubleshooting steps for Linux users, including common issues and solutions.
  • Clarify any platform-specific limitations and offer alternative workflows for Linux/macOS users.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide parallel guidance for both Windows and Linux/macOS.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster template ...ric/service-fabric-cluster-creation-create-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for testing and deploying the Resource Manager template, referencing Windows-centric sample templates, and omitting equivalent Linux/macOS CLI instructions. The only mention of Linux is a brief note about Microsoft Entra tenant creation, with no actionable guidance or examples for Linux users.
Recommendations
  • Include Azure CLI examples for testing and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Reference or provide sample templates for Linux clusters, not just Windows-based ones.
  • Add explicit instructions or links for Linux/macOS users on how to perform certificate management and parameter population tasks.
  • Ensure that any PowerShell-specific guidance is paired with Azure CLI or Bash alternatives.
  • Clarify any platform-specific requirements or differences in the workflow.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric cluster ...vice-fabric/service-fabric-cluster-creation-via-arm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured heavily and almost always shown first, with Windows-centric examples and tools (e.g., use of c:\ paths, WindowsServer OS, ConvertTo-SecureString). While Azure CLI examples are provided and Ubuntu templates are referenced, Linux/macOS users may encounter friction due to Windows-first ordering, Windows-only tooling, and lack of explicit Linux/macOS shell examples (e.g., bash, file paths, certificate handling).
Recommendations
  • Alternate example ordering so Linux/Ubuntu is shown first in some sections.
  • Provide explicit bash examples for Linux/macOS users, including file path conventions (e.g., /home/user/certificates).
  • Clarify that PowerShell examples are for Windows, and provide equivalent bash commands for Linux/macOS.
  • Note any OS-specific requirements or differences (e.g., certificate formats, file permissions).
  • Ensure all referenced templates and commands work equally on Linux/macOS, and document any caveats.
  • Use neutral language and tooling where possible (e.g., avoid Windows-only features like ConvertTo-SecureString).
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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric concepts such as RDP port management and admin username/password changes are highlighted in the 'Next steps' section, with links to PowerShell scripts and RDP-specific instructions. The example configuration uses a Windows-style data path (D:\\SvcFab) and certificate store references, and does not provide Linux-specific paths or guidance. Linux equivalents for remote connection, user management, or file paths are missing or not mentioned.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions) and user management.
  • Provide Linux-style file paths (e.g., /var/svcfab) in configuration examples alongside Windows paths.
  • Include references to Linux tools and commands where Windows/PowerShell tools are mentioned.
  • Ensure that guidance for changing admin credentials and port ranges covers both Windows (RDP) and Linux (SSH) scenarios.
  • Reorder examples so that Windows and Linux are presented with equal prominence, or alternate which comes first.
GitHub Create Pull Request
Service Fabric Remote connect to an Azure Service Fabric cluster node ...ce-fabric-cluster-remote-connect-to-azure-cluster-node.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows (RDP) connection details and screenshots first, using Windows terminology and tools (Remote Desktop Connection), and referencing PowerShell scripts for post-connection tasks. Linux connection (SSH) is mentioned, but only briefly and after the Windows example, with no screenshots or detailed instructions.
Recommendations
  • Present Linux (SSH) connection instructions and screenshots alongside or before Windows examples to ensure parity.
  • Include references to Linux command-line tools and scripts for post-connection tasks, not just PowerShell.
  • Provide equivalent step-by-step instructions for Linux/macOS users, including troubleshooting tips and credential management.
  • Link to Linux-specific documentation for managing cluster nodes and updating SSH settings.
GitHub Create Pull Request
← Previous Page 18 of 29 Next →