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 2176-2200 of 2475 flagged pages
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
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 Events demonstrates a Windows bias by referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the primary mechanisms for accessing events. Linux equivalents or cross-platform instructions are not mentioned, and the examples and tooling described are Windows-centric. This creates friction for Linux/macOS users who may be running Service Fabric clusters on non-Windows environments.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., syslog, journald, or custom log files).
  • Clarify whether the Windows Azure diagnostics agent is required or if there is a Linux-compatible alternative for event forwarding.
  • Include cross-platform guidance for integrating with Azure Monitor logs from Linux clusters.
  • List any differences in event access or monitoring setup between Windows and Linux Service Fabric clusters.
  • Provide REST API usage examples that work identically on all platforms.
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 →
Scanned: 2026-01-30 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 PowerShell examples for managing node tags and service requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its examples are presented before C# API usage, with no mention of Linux-friendly alternatives for command-line operations.
Recommendations
  • Add Azure CLI or REST API examples for managing node tags and service requirements, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell commands are available on Linux (via PowerShell Core), and provide installation guidance if so.
  • If PowerShell is not supported on Linux for these commands, clarify this and direct Linux users to supported alternatives.
  • Consider providing Bash or shell script examples where appropriate.
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 →
Scanned: 2026-01-30 00:00
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 workflows and referencing Windows-specific tools (e.g., F5/Ctrl+F5, right-click Publish, Visual Studio project templates). There are no examples or guidance for Linux/macOS users or cross-platform tooling, and alternative deployment methods are only briefly mentioned.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or PowerShell Core on Linux/macOS) for tasks currently described with Visual Studio.
  • Clarify which features are Visual Studio/Windows-only and offer parity instructions for non-Windows environments where possible.
  • Include sample workflows for deploying Service Fabric applications using DevOps pipelines or command-line tools on Linux/macOS.
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 →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Service Fabric reliable services app manifest examples demonstrates a mild Windows bias. Example scripts and executables use Windows conventions (e.g., .exe, .bat), and references to user accounts and groups (Administrators, NetworkService) are Windows-centric. There are no explicit Linux equivalents or examples, nor is there guidance for Linux Service Fabric clusters (e.g., using shell scripts, Linux user/group patterns). The only mention of PowerShell is in a comment, but no Linux CLI or Bash alternatives are presented.
Recommendations
  • Include Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group conventions.
  • Clarify which manifest elements and patterns are cross-platform, and note any differences for Linux clusters (e.g., user account handling, service startup scripts).
  • Provide parallel examples for Linux deployments, including sample manifests with Linux-style executables and scripts.
  • Explicitly state in relevant sections if certain features or patterns are Windows-only, and link to Linux documentation where available.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily references Windows images and provides a PowerShell example for role assignment, with limited mention of Linux equivalents. While it briefly links to Linux instructions for creating custom images and finding marketplace images, the main examples and terminology focus on Windows, and no Linux-specific CLI or shell examples are provided.
Recommendations
  • Add explicit examples and instructions for deploying Linux custom images on Service Fabric Managed Clusters.
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations, not just PowerShell.
  • Clarify in the introduction that both Windows and Linux images are supported, and structure examples to show parity.
  • Include references to Linux-specific documentation where appropriate, and ensure links are clearly labeled.
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-01-30 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 page 'Manage certificates in a Service Fabric cluster' demonstrates a notable Windows bias. PowerShell is the only scripting language used for automation examples, and references to Windows-specific tools and extension schemas (e.g., Key Vault VM extension for Windows, S-channel, CERT_RENEWAL_PROP_ID) are prevalent. The documentation does not provide equivalent Linux/macOS automation examples (such as Bash, Azure CLI, or cross-platform SDKs), nor does it mention Linux-specific certificate management patterns or VM extensions. Windows terminology and mechanisms are introduced before any cross-platform alternatives, and some features (like certificate linking) are explicitly described as Windows-only, but without guidance for Linux users.
Recommendations
  • Add automation examples using Bash and Azure CLI for certificate enrollment and management, alongside PowerShell.
  • Clarify which mechanisms (e.g., Key Vault VM extension, certificate linking) are Windows-only and provide Linux/macOS alternatives or workarounds where possible.
  • Reference and link to Linux-specific documentation for Service Fabric clusters, especially for certificate provisioning and rotation.
  • Explicitly state platform limitations for features that are not available on Linux/macOS, and suggest supported cross-platform approaches (e.g., using Azure CLI, REST API, or SDKs).
  • Include notes or sections for Linux/macOS users, outlining differences in certificate storage, access control, and automation.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides detailed conceptual and configuration guidance for X.509 certificate-based authentication in Service Fabric clusters. While it covers both Windows and Linux in some configuration examples, there is a notable Windows bias in troubleshooting and operational guidance: Windows certificate store paths and tools are mentioned first and in detail, Windows event log locations are referenced exclusively, and troubleshooting steps rely on Windows-specific tools (e.g., CAPI2 logging, Win32 CryptoAPI references). Linux equivalents for certificate storage, logging, and troubleshooting are mentioned only briefly or not at all.
Recommendations
  • Add explicit Linux/macOS troubleshooting instructions, including log file locations and relevant commands.
  • Provide Linux/macOS equivalents for certificate store paths (e.g., expand on /var/lib/sfcerts usage and management).
  • Include examples of how to inspect and manage certificates on Linux/macOS (e.g., using openssl, keytool, or systemd journal for logs).
  • Reference cross-platform APIs or tools where possible, or clarify platform-specific differences.
  • Ensure that configuration examples and operational guidance are presented for both Windows and Linux/macOS environments, or clearly indicate when a step is Windows-only.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
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 example for bypassing the Infrastructure Service, without mentioning or providing equivalent Linux/macOS command-line instructions. The use of PowerShell cmdlets and references to Service Fabric Explorer (a Windows-centric tool) further reinforce a Windows bias, making it less accessible for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Linux/macOS instructions using Service Fabric CLI (sfctl) or REST API where possible.
  • Clarify whether the PowerShell command is required, or if cross-platform alternatives exist.
  • Mention and link to cross-platform management tools (e.g., sfctl, REST API) alongside Service Fabric Explorer.
  • Add explicit notes about platform requirements for any commands or tools.
  • Ensure examples are provided for both Windows and Linux/macOS environments where supported.
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-30 00:00
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 in the 'Best practices' section, listing PowerShell before Azure CLI, and omitting explicit Linux/macOS command-line examples for key operations. While ARM, Bicep, and Azure CLI are mentioned, actionable examples and links focus on PowerShell, which is traditionally Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples and links for all key operations (e.g., deleting NodeType, restarting/reimaging scale sets) alongside PowerShell.
  • Ensure that CLI examples are shown before or alongside PowerShell, not after.
  • Clarify that Azure CLI and ARM/Bicep templates are fully cross-platform and provide sample commands for Linux/macOS users.
  • Where PowerShell is referenced, note that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), but does not mention or provide equivalent examples for cross-platform tools such as Azure CLI, Bash, or scripting for Linux/macOS users. PowerShell is referenced as the only scripting interface outside of ARM templates and the Portal, and is listed before ARM templates in some sections. There is no mention of Azure CLI, which is widely used on Linux/macOS. This creates friction for non-Windows users who may not have access to or familiarity with PowerShell.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell examples can be run on any OS using PowerShell Core, or provide Bash scripting equivalents where appropriate.
  • In each section, present Azure CLI and PowerShell examples together, or at least mention both, to avoid Windows-first ordering.
  • Clarify if any operation is only possible with PowerShell and not Azure CLI, and provide guidance for Linux/macOS users in such cases.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, using Windows-specific images (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows shell commands (cmd, type, ping). There are no Linux container examples, nor any mention of how to use Initializer CodePackages with Linux containers or Linux-based workloads, despite Service Fabric supporting both Windows and Linux containers. The examples and guidance are exclusively Windows-focused, potentially creating friction for Linux users.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands and file paths.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance for Linux users.
  • Where file paths or commands are shown, provide both Windows and Linux equivalents, or note platform-specific differences.
  • Explicitly mention any platform limitations (if Initializer CodePackages are not supported for Linux containers, state this clearly).
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Windows-specific features (Active Directory, gMSA, BitLocker) are mentioned with no Linux equivalents or with Linux options referenced only briefly or as TODOs. Examples and links often focus on Windows tools and patterns, and Linux-specific instructions (e.g., disk encryption) are missing or deferred. Windows features are sometimes described first or exclusively, creating friction for Linux users.
Recommendations
  • Add explicit Linux examples and instructions where only Windows options are described (e.g., disk encryption for Linux clusters).
  • When mentioning Windows-specific features (e.g., BitLocker, gMSA), clarify Linux alternatives or note platform limitations.
  • Ensure parity in documentation links and examples for both Windows and Linux clusters, especially for common security tasks.
  • Where possible, provide side-by-side guidance for both platforms, or clearly indicate platform-specific sections.
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-30 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, but there is a noticeable tendency to mention Windows tools, features, and examples first or in greater detail. Windows-specific tools like Event Viewer, Diagnostics Agent, and EventStore APIs are highlighted, sometimes with less detail or fewer examples for Linux equivalents. Linux monitoring is referenced, but often as a secondary note or with links out to other pages, rather than inline examples. Some sections (e.g., EventStore APIs, Diagnostics Agent) are Windows-only, but this is generally called out. However, Linux users may need to follow additional links or infer parity, which creates friction.
Recommendations
  • Provide Linux-specific examples and configuration steps inline, especially for key monitoring workflows.
  • When mentioning Windows tools (e.g., Event Viewer, Diagnostics Agent), immediately follow with Linux equivalents (e.g., Syslog, LTTng) and usage instructions.
  • Ensure that sample queries, alert rules, and setup instructions explicitly mention any differences or additional steps for Linux clusters.
  • Add more direct links to Linux-focused tutorials and documentation where parity is not possible in the main text.
  • Consider a summary table comparing Windows and Linux monitoring tools and workflows 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-01-30 00:00
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 manner, focusing on XML configuration. However, there is a notable Windows bias in the tooling recommendations: the only explicit tool mentioned for authoring manifests is Visual Studio, referencing a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and suggesting opening it in Visual Studio for IntelliSense and schema validation. Additionally, the PowerShell module is referenced for service creation, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. No Linux-specific tools, workflows, or examples are provided, and Windows tooling is mentioned first and exclusively.
Recommendations
  • Add instructions for validating and editing manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line XML validators.
  • Reference the location of Service Fabric schema files on Linux installations, if available.
  • Mention cross-platform alternatives to Visual Studio for schema validation and IntelliSense, such as VS Code with XML plugins.
  • Include examples or references for using Azure CLI or Service Fabric CLI (sfctl) for service creation and management, alongside PowerShell.
  • Clarify that PowerShell is available on Linux/macOS, or provide bash/shell equivalents for common tasks.
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET SDK methods are mentioned, there is a notable lack of Linux/macOS-specific CLI examples (such as Azure CLI or sfctl), and PowerShell is often presented as the primary or only command-line interface. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and/or Azure CLI for each lifecycle operation alongside PowerShell and .NET SDK references.
  • Clearly indicate which tools are cross-platform and which are Windows-only, helping users choose the appropriate interface.
  • Where PowerShell is referenced, provide equivalent Linux/macOS commands or links to relevant documentation for those platforms.
  • Consider reordering examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
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 upgrade topics is heavily focused on PowerShell-based workflows and examples, with all command-line instructions and code snippets using PowerShell cmdlets. There is no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API), nor are there examples for non-Windows environments. The documentation implicitly assumes users are operating in a Windows/PowerShell environment, which creates friction for Linux/macOS users who may be using Service Fabric on those platforms.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, also provide the corresponding REST API calls or CLI commands.
  • Explicitly mention platform compatibility for each tool or command, and guide users to the appropriate tool for their OS.
  • Include notes or sections for Linux/macOS users, especially for common upgrade workflows.
  • Update 'Next steps' to include tutorials for CLI-based upgrades, not just Visual Studio and PowerShell.
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-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Service Fabric application upgrades demonstrates a notable Windows bias. The only command-line example provided is in PowerShell, and all references to Service Fabric management tools are Windows-centric (PowerShell cmdlets). There are no CLI or Linux/macOS-compatible examples or instructions. Additionally, the documentation references Windows-specific components such as http.sys and error messages from the Windows HTTP Server API, without mentioning Linux equivalents or cross-platform considerations.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for application upgrades, especially for retrieving and passing application parameters.
  • Include notes or sections describing how to perform equivalent operations on Linux clusters, or clarify if certain features are Windows-only.
  • Where Windows-specific APIs or error messages are referenced (e.g., http.sys), provide Linux/macOS context or explicitly state if the limitation is Windows-only.
  • In the 'Next steps' section, add links to cross-platform upgrade tutorials (e.g., using Azure CLI, sfctl, or REST API) if available.
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-01-30 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 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 examples provided using curl or other non-Windows tools. The prerequisites and step-by-step instructions assume the use of PowerShell and related modules, which are primarily Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using cross-platform tools such as curl, az CLI, or bash scripts for REST API calls.
  • Clarify whether the PowerShell modules can be used on Linux/macOS via PowerShell Core, and provide installation instructions if so.
  • Add explicit guidance for Linux/macOS users, including any required authentication steps and certificate handling.
  • Reorder examples so that REST API usage is shown first, followed by platform-specific tooling.
  • Indicate any platform limitations or requirements for Service Fabric backup/restore operations.
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-30 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 detailed step-by-step instructions for scaling Service Fabric clusters, but consistently uses PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is presented as the default, with no Bash, CLI, or REST API examples for Linux users. The examples and manual procedures are Windows-centric, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Add equivalent instructions and examples for Linux environments, using Bash, Azure CLI, or REST API where possible.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives if available.
  • Reorder examples or provide parallel instructions for both Windows and Linux users to improve parity.
  • Reference Linux-specific documentation sections where appropriate, especially for cluster management tasks.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health, but does not offer equivalent CLI or Linux/macOS examples. The only command-line example is Windows/PowerShell-specific, and there is no mention of cross-platform tools or commands for Linux users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • When showing command-line examples, provide both PowerShell and CLI (sfctl) commands side-by-side.
  • Explicitly mention that the PowerShell cmdlets are Windows-only and link to cross-platform alternatives.
  • Review other sections for implicit assumptions of Windows environments and clarify where features or commands are platform-specific.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page prioritizes Windows-centric tools (PowerShell and Visual Studio) in both structure and example detail. PowerShell and Visual Studio parameters are described first and in greater depth, with example formats and usage, while Linux/macOS equivalents (SFCTL CLI) are covered later and with less practical guidance. There are no explicit Linux/macOS command-line examples or walkthroughs in the main body, and the SFCTL section lacks concrete usage examples. This creates friction for Linux/macOS users, who must infer parameter usage and mapping from Windows-focused sections.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL CLI) are presented before or alongside Windows-specific tools.
  • Provide concrete SFCTL CLI command examples for common upgrade scenarios, similar to the PowerShell examples.
  • Explicitly note platform compatibility for each tool (e.g., PowerShell for Windows, SFCTL for Linux/macOS/Windows).
  • Add a table or mapping showing how parameters correspond between PowerShell, Visual Studio, and SFCTL.
  • Ensure that walkthroughs and examples for Linux/macOS users are as detailed and accessible as those for Windows users.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric exhibits mild Windows bias. While the majority of the content is platform-neutral, the only example of on-premises backup storage is a Windows file share (with Windows authentication and UNC path syntax), and no Linux or cross-platform file share options (such as NFS or SMB mounting on Linux) are mentioned. Additionally, the file share example uses Windows authentication patterns and does not discuss Linux-compatible alternatives. Azure Blob storage examples are platform-neutral, but the file share section is Windows-centric.
Recommendations
  • Add examples for configuring backup storage to Linux-compatible file shares, such as NFS or SMB shares mounted on Linux nodes.
  • Clarify whether Service Fabric supports Linux-based clusters using file shares for backup, and if so, provide guidance for Linux authentication and mounting.
  • Include notes or examples for Linux/macOS users where applicable, especially in sections discussing file share paths and authentication.
  • If file share backup is Windows-only, 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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools 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 detailed upgrade commands, while Linux equivalents (e.g., Bash, shell scripts) are absent. Windows-specific configuration details (registry keys, Windows Update settings) are described without Linux alternatives or guidance. Upgrade instructions and examples focus on Windows tools and patterns, with no parity for Linux users in critical operational steps.
Recommendations
  • Add Linux/Bash equivalents for PowerShell deployment and upgrade commands, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for OS upgrades and disabling automatic updates, such as relevant systemd or apt/yum settings.
  • Present examples for both Windows and Linux side-by-side, or clearly indicate when a step is Windows-only.
  • Reference Linux documentation and tools where appropriate, not just in 'Next steps'.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-01-30 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 provides code samples for configuring Service Fabric placement policies using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. The PowerShell examples are presented for every scenario, and there is no mention of Linux-compatible tooling or workflows. This creates friction for users managing Service Fabric clusters from Linux/macOS environments.
Recommendations
  • Add equivalent Azure CLI examples for each placement policy scenario, as Azure CLI is cross-platform.
  • Document REST API or ARM template approaches for configuring placement policies, which are platform-agnostic.
  • Explicitly mention whether these operations can be performed from Linux/macOS, and provide guidance for non-Windows users.
  • If PowerShell is required, clarify if PowerShell Core (cross-platform) is supported and provide installation instructions.
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-30 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 most security best practices, including certificate management and secret encryption. However, Windows examples and tools (such as PowerShell and Windows Defender) are frequently presented first or exclusively, with Linux equivalents sometimes appearing later or in less detail. Windows-specific tools and configuration options (e.g., Windows Defender, PowerShell commands) are described in dedicated sections, while Linux alternatives are not always given equal prominence or detail.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections, rather than listing Windows first.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide Linux alternatives or clarify their absence.
  • Expand Linux-specific guidance for security baselines and antimalware, referencing common Linux security tools (e.g., SELinux, AppArmor, ClamAV) and best practices.
  • Ensure that all code samples and configuration snippets have Linux equivalents where applicable.
  • Add explicit notes when a feature or recommendation is Windows-only, to avoid confusion for Linux users.
GitHub Create Pull Request
← Previous Page 88 of 99 Next →