Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 351-375 of 2475 flagged pages
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides manifest examples and explanations for Azure Service Fabric container applications. The examples and narrative are based on the Windows Server 2016 Container Sample, and several sections reference Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths). There are no explicit Linux manifest examples, and Linux-specific patterns or differences are not discussed. While some notes mention Linux (e.g., certificate handling), the overall focus and examples are Windows-centric.
Recommendations
  • Add equivalent Linux-based manifest examples, referencing the Linux container sample repository.
  • Include notes or sections highlighting differences in configuration, file paths, and OS build detection for Linux clusters.
  • Mention Linux-specific Service Fabric container features or limitations where relevant.
  • Provide links to Linux documentation and samples alongside Windows references.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based deployment instructions and examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. Command-line examples and guidance are exclusively PowerShell, and Windows-centric concepts (such as RDP and Windows directory paths) are used throughout. There are no Linux/macOS equivalents or alternative instructions, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Provide Bash shell command equivalents for template deployments.
  • Mention cross-platform tools (e.g., Azure Cloud Shell) that work on Linux/macOS.
  • Clarify that Service Fabric clusters can be managed from any OS, and provide guidance for Linux/macOS users.
  • Replace or supplement Windows-specific instructions (e.g., RDP, Windows directory paths) with cross-platform alternatives (e.g., SSH, generic paths).
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned first or exclusively. Linux support is discussed, but Linux-specific instructions and examples are missing, especially for non-containerized services and for enabling DNS service outside ARM templates.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing services, especially for Linux clusters.
  • Clarify how Linux users can perform tasks currently shown with PowerShell or ApplicationManifest.xml, including any limitations.
  • Provide guidance for enabling DNS service on Linux clusters outside ARM templates, if possible.
  • Explicitly state any tasks that cannot be performed on Linux, and offer alternative approaches or workarounds where feasible.
  • Include editor-agnostic instructions (not just Visual Studio) for ApplicationManifest.xml edits.
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. This creates friction for Linux/macOS users, as the upgrade process and parameter configuration are described only in the context of Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for configuring upgrade parameters and health policies using tools available on Linux/macOS, such as sfctl (Service Fabric CLI).
  • Mention that Visual Studio and PowerShell are Windows-only, and provide links or references to Linux/macOS-compatible workflows.
  • Present cross-platform alternatives before or alongside Windows-specific instructions to improve parity.
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows a moderate Windows bias. While it does mention Linux equivalents in a few places (e.g., Linux certificate path), most operational and troubleshooting guidance is Windows-centric. Examples and troubleshooting steps reference Windows certificate stores, Windows event logs, and Windows-specific APIs (e.g., Win32 CryptoAPI), with Linux alternatives only briefly mentioned or omitted. No Linux/macOS-specific troubleshooting or operational examples are provided.
Recommendations
  • Provide explicit Linux/macOS equivalents for certificate storage and retrieval (e.g., detail how Service Fabric on Linux locates and loads certificates, including file paths and permissions).
  • Add troubleshooting steps for Linux clusters, such as relevant log file locations, commands to inspect certificates (e.g., using openssl or Linux file system paths), and how to check for private key accessibility.
  • When referencing Windows event logs or APIs, include analogous Linux/macOS methods (e.g., syslog, journald, or Service Fabric logs on Linux).
  • Where possible, show both Windows and Linux configuration examples side by side, or clearly indicate when a step is platform-specific.
  • Clarify any differences in certificate provider support or limitations on Linux/macOS (e.g., CAPI1/CNG equivalents, if any).
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting alternatives. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently presented, sometimes before or instead of cross-platform options, indicating a Windows-first bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all operations (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Where possible, provide Bash scripting or REST API examples to further increase platform parity.
  • Review the order of examples to avoid consistently presenting Windows tools first unless there is a technical reason.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is used exclusively for scripting examples, and the Key Vault VM extension discussed is Windows-specific. The documentation references Windows certificate store concepts and S-channel APIs, and troubleshooting steps are given only in PowerShell. There is no mention of Linux-specific certificate provisioning tools, scripting, or VM extensions, nor are Linux/macOS examples provided. Windows terminology and mechanisms are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS scripting examples (e.g., Bash, Azure CLI) for certificate enrollment and management.
  • Clarify which mechanisms (such as Key Vault VM extension) are Windows-only, and provide Linux alternatives (e.g., Azure CLI, custom scripts, or Linux VM extensions).
  • Mention Linux certificate store locations and how Service Fabric on Linux nodes handles certificate provisioning and autorollover.
  • Include troubleshooting steps for Linux clusters, using relevant tools and commands.
  • Where possible, present cross-platform guidance or explicitly state platform limitations.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While Linux is referenced in links and image creation, the main content and examples are Windows-centric, and the PowerShell command for role assignment is provided without a Linux CLI equivalent.
Recommendations
  • Add explicit Linux-focused examples and clarify Linux support for custom images in Service Fabric Managed Clusters.
  • Provide Azure CLI commands for role assignment alongside PowerShell examples.
  • Include ARM template snippets or guidance for deploying Linux-based custom images, if supported.
  • Clarify in the introduction whether Linux node types are supported, and if so, provide parity in instructions and examples.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell command examples for migration steps, especially in the 'Basic SKU' scenario, without offering equivalent CLI or Bash examples. The PowerShell examples are presented as the only option for resource deployment and node management, which creates friction for Linux/macOS users. Additionally, the sample template for Ubuntu clusters is referenced, but no Linux-native command-line instructions are given. Windows/PowerShell patterns are mentioned first and exclusively in critical migration steps.
Recommendations
  • Add Azure CLI or Bash script equivalents for all PowerShell examples, especially for resource deployment, node disabling, and removal.
  • Explicitly note that PowerShell commands can be run cross-platform via Azure Cloud Shell, but provide native CLI/Bash alternatives for Linux/macOS users.
  • Where sample templates reference Ubuntu, include Linux-native instructions for deployment and cluster management.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
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 Azure Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd.exe) in all code samples. Querying deployment status is demonstrated only via PowerShell and C# APIs, with no mention of Linux tools or Bash equivalents. There is no guidance or example for Linux containers, Linux command syntax, or querying from Linux environments.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux command syntax (bash/sh) in ServiceManifest.xml.
  • Provide guidance for querying deployment status from Linux environments, such as using Azure CLI, Bash scripts, or REST APIs.
  • Clarify RunToCompletion support for Linux containers and guest executables, including any limitations or differences.
  • Present Linux examples alongside Windows examples, or indicate if RunToCompletion is Windows-only.
  • Include links or references to Linux container documentation for Service Fabric.
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its guidance for authoring manifest files. It explicitly recommends opening the Service Fabric XSD schema file in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and does not mention Linux or cross-platform alternatives for schema validation or authoring manifests. The only tool and workflow described for authoring manifests is Windows/Visual Studio-centric, and this guidance appears before any mention of Linux or cross-platform options (which are not mentioned at all).
Recommendations
  • Provide instructions or recommendations for validating and authoring Service Fabric manifest files on Linux/macOS, such as using cross-platform editors (e.g., VS Code with XML extensions) and how to obtain the XSD schema file on non-Windows systems.
  • Clarify where the schema file can be found or downloaded for Linux/macOS environments.
  • Mention cross-platform tools for XML validation and intelli-sense, or link to relevant resources.
  • Ensure that any file paths or tool recommendations are either cross-platform or alternatives are given for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation frequently references PowerShell cmdlets for Service Fabric operations, often listing them before or alongside .NET API and REST options. There is a lack of explicit Linux/CLI examples, and no mention of Linux-specific tools or workflows. While REST and .NET APIs are cross-platform, the prominence of PowerShell and absence of Linux CLI (sfctl) usage or examples creates friction for Linux/macOS users.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) command examples for each major operation (deploy, upgrade, remove, test, etc.), especially in sections currently listing only PowerShell.
  • Where PowerShell is referenced, clarify its Windows-specific nature and provide Linux/macOS alternatives.
  • Reorder examples so that cross-platform tools (REST, sfctl) are listed before or alongside Windows-specific tools.
  • Include links or references to Linux/macOS documentation and workflows for Service Fabric application lifecycle management.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and detail. PowerShell and Visual Studio are discussed first and in greater depth, with SFCTL (the cross-platform CLI) relegated to a later section. Parameter tables and examples are more detailed for PowerShell/Visual Studio, and Windows tools are referenced before Linux equivalents. There are no explicit Linux/macOS command examples or screenshots, and SFCTL/Linux is not given equal prominence.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/REST) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equivalent parameter tables and usage examples for SFCTL and REST, matching the detail given to PowerShell/Visual Studio.
  • Add explicit Linux/macOS command-line examples and clarify which tools are cross-platform.
  • Where possible, use neutral language (e.g., 'using PowerShell, Visual Studio, or SFCTL') instead of always listing Windows tools first.
  • Ensure that 'Next steps' and tutorial links for Linux/SFCTL are given equal prominence and not listed after Windows tutorials.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several instances where Windows tools, terminology, and examples are presented first or in greater detail. Windows-specific tools (Event Log, ETW, EventStore APIs) are mentioned before Linux equivalents, and Linux configuration details are sometimes referenced only via links. Some sections lack explicit Linux examples or guidance, especially for platform diagnostics and agent setup.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal detail and prominence as Windows equivalents.
  • Add explicit Linux-focused examples and walkthroughs for configuring diagnostics, collecting logs, and querying events (not just links to other pages).
  • When mentioning Windows tools (e.g., Event Log, ETW), immediately provide Linux alternatives (e.g., LTTng, Syslog) and clarify differences in workflow.
  • In summary/setup sections, list Linux options alongside Windows, rather than focusing on Windows tools first.
  • Expand Linux agent setup instructions and provide sample queries or troubleshooting steps for Linux clusters.
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-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a generally platform-agnostic manner, but several sections show Windows bias. Windows-specific tools and concepts (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned before or instead of Linux equivalents. Some examples and links are Windows-centric, and Linux guidance is sometimes missing or relegated to brief mentions. Disk encryption for Linux clusters is noted as a TODO, indicating incomplete Linux parity.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric applications, including disk encryption and user account management.
  • Ensure Linux-specific tools and patterns (e.g., Linux user/group management, certificate handling, disk encryption with dm-crypt/LUKS) are documented alongside Windows equivalents.
  • Provide parity in examples, such as showing both Windows and Linux approaches for configuring security principals, running services under different accounts, and managing secrets.
  • Complete the TODO section for 'Encrypt disks on Linux clusters' with concrete instructions.
  • Review all sections for Windows-first ordering and ensure Linux options are presented equally.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily relies on PowerShell cmdlets for all upgrade operations, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All code examples and walkthroughs use PowerShell syntax, and references to Visual Studio (a Windows-centric IDE) are prominent. There is no guidance for Linux/macOS users on how to perform these tasks using Azure CLI, REST API, or other cross-platform tools.
Recommendations
  • Add Azure CLI or REST API examples for key operations (creating/upgrading/removing services, application upgrades, rollbacks).
  • Explicitly mention whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core) or if alternatives exist for Linux/macOS users.
  • Provide links to documentation for Linux/macOS users, or add a section outlining upgrade workflows for non-Windows environments.
  • Include sample scripts or commands for Bash or Azure CLI where possible.
  • Clarify any Windows-only limitations for Service Fabric management tools, and suggest workarounds or alternatives.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
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 upgrades demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are referenced exclusively. There are no Linux or cross-platform CLI examples (such as Azure CLI or Service Fabric CLI), and Windows terminology and tools are mentioned first and throughout. This creates friction for Linux/macOS users, who may not have access to PowerShell or http.sys and may need to find alternative methods.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or Azure CLI for application upgrades.
  • Clearly indicate which features or steps are Windows-only, and provide Linux/macOS alternatives where possible.
  • Include guidance for Linux/macOS users on how to retrieve application parameters and perform upgrades.
  • Mention cross-platform considerations for HTTPS endpoints, such as how certificate management differs on Linux.
  • Balance references to PowerShell with references to other tools or APIs (e.g., REST API, sfctl).
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows environments. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The REST API is only demonstrated via PowerShell scripts, and Windows-specific certificate handling is referenced. No Linux or macOS equivalents are mentioned, and PowerShell is assumed throughout.
Recommendations
  • Add Bash/curl examples for REST API calls, including certificate handling for Linux/macOS.
  • Mention cross-platform alternatives to PowerShell for interacting with Service Fabric APIs.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS.
  • Provide guidance for Linux/macOS users on connecting to clusters and authenticating (e.g., using OpenSSL, curl, or Azure CLI).
  • Explicitly state if certain steps are Windows-only, and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides several manual scaling instructions that rely exclusively on PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or cross-platform alternatives. There are no CLI or REST API examples for these critical operations, and no guidance for Linux users on how to perform these tasks, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell-based instructions, especially for node disablement and removal.
  • Explicitly mention if certain operations must be performed from a Windows environment, and provide workarounds or alternatives for Linux/macOS users.
  • Where possible, reference Service Fabric cross-platform tools (e.g., sfctl) and provide example commands.
  • Clarify platform requirements in each section that uses platform-specific tooling.
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-03-06 00:00
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, such as certificate creation and secret encryption, but Windows examples (PowerShell) are often presented first and in greater detail. Windows-specific tools and features (Windows Defender, PowerShell commands, DSC, Windows security baselines) are mentioned exclusively or before Linux equivalents. Some sections (Windows Defender, DSC) are Windows-only by nature, but others (like secret encryption) could improve parity by balancing example order and detail.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate which comes first to avoid 'windows_first' bias.
  • Where possible, provide Linux equivalents for Windows tools (e.g., mention Linux antivirus solutions or baseline tools if relevant).
  • Clarify when sections are Windows-only and provide links to Linux alternatives or note their absence.
  • Ensure Linux examples are as detailed and prominent as Windows examples, especially in critical workflows (e.g., secret encryption).
  • Add explicit notes when a feature or tool is not available on Linux, and suggest best practices for Linux users.
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 →
Scanned: 2026-03-06 00:00
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, but does not offer equivalent Linux/macOS CLI (e.g., sfctl) or REST API examples. All code snippets for service configuration use PowerShell, and PowerShell is presented immediately after C# code, with no mention of Linux-native tools or cross-platform alternatives. This creates friction for Linux/macOS users who cannot use PowerShell natively and must seek out alternative methods.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for placement policy configuration, as these are platform-agnostic.
  • Clearly indicate which tools are Windows-only and provide guidance for Linux/macOS users on equivalent workflows.
  • Consider reordering examples so that cross-platform methods (sfctl, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but when discussing file share backup storage, it exclusively references Windows-style file shares (\\StorageServer\BackupStore) and Integrated Windows Authentication. No Linux or SMB/NFS examples or guidance are provided for non-Windows clusters or file share setups. There are no PowerShell or Windows-first command examples, but the file share section assumes a Windows environment.
Recommendations
  • Add guidance or examples for configuring file share backup storage using SMB/NFS on Linux clusters, including path formats and authentication methods.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide Linux-specific instructions.
  • Mention any limitations or alternatives for Linux/macOS users regarding file share storage.
  • If only Windows file shares are supported, explicitly state this to avoid confusion for Linux users.
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-03-06 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for advanced operations (e.g., cluster upgrades) without Linux/bash equivalents. Windows-specific configuration (e.g., registry keys, Windows Update settings) is discussed in detail, while Linux-specific instructions for comparable scenarios are missing. The order of presentation and focus on Windows tools and patterns may create friction for Linux/macOS users.
Recommendations
  • For every PowerShell example, provide a bash/Azure CLI equivalent where possible, especially for advanced operations like cluster upgrades.
  • When discussing OS-specific configuration (e.g., disabling automatic updates), include Linux equivalents (such as disabling unattended-upgrades or using cloud-init for Linux VMs).
  • Clarify when a step or configuration is Windows-only, and provide parallel Linux guidance or explicitly state if not applicable.
  • Balance the order of examples (e.g., alternate between Windows and Linux, or present both together) to avoid a 'Windows-first' impression.
  • Link to Linux-specific documentation or scripts where available, especially for cluster management and upgrades.
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. There is no mention of Linux-compatible tools or workflows, which creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API examples for application management tasks, which are platform-agnostic.
  • Explicitly mention whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core) or if they are Windows-only.
  • Provide Bash or shell script examples where applicable.
  • Clarify any platform restrictions for Service Fabric management tools.
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 →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux-native tooling or cross-platform CLI options. Additionally, PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation does note that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux users.
  • Explicitly mention cross-platform alternatives to PowerShell for managing Service Fabric clusters (e.g., Azure CLI, REST API).
  • Clarify which PowerShell commands are available on Linux (if any), or provide guidance for Linux users.
  • Consider including a note or section for Linux/macOS users outlining recommended tools and workflows.
GitHub Create Pull Request
← Previous Page 15 of 99 Next →