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 1051-1075 of 2475 flagged pages
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only practical example for reporting and evaluating application health is given using PowerShell. There are no equivalent Linux/macOS CLI or REST API examples, despite the text mentioning REST and FabricClient APIs. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific cmdlets.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include REST API usage examples for health reporting and querying, as referenced in the text.
  • Mention and link to documentation for Linux/macOS tools (sfctl, REST) alongside PowerShell, not after or instead of.
  • Clarify which tools are available on which platforms, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell for deployment/removal and uses a PowerShell module link for downloading ServicePackages, but does not provide Linux/CLI equivalents or mention cross-platform tools. This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include Azure CLI or cross-platform command examples alongside PowerShell, especially for deployment/removal and ServicePackage download steps.
  • Link to documentation for Linux-based Service Fabric cluster management where available.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives or notes for Linux/macOS users.
  • If certain operations are only possible via PowerShell, explicitly state this and suggest workarounds or alternatives for non-Windows users.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-21 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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several places, and some examples (such as standalone cluster creation and scaling) are only given for Windows. Linux equivalents are sometimes missing or referenced less prominently. The documentation also frequently references Windows executables (e.g., FabricHost.exe) without clarifying Linux alternatives or differences, and PowerShell is often listed before CLI or REST options.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, scaling, and upgrades.
  • Mention Linux tools (e.g., Bash, sfctl CLI) before or equally with Windows tools like PowerShell.
  • Clarify differences in process management and service hosting between Windows and Linux nodes.
  • Add links to Linux-specific documentation and quickstarts where available.
  • Ensure parity in 'Next steps' and throughout the document, so Linux users can easily find relevant guidance.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-21 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 Replica Soft Delete in Service Fabric heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and administrative APIs without providing equivalent examples or guidance for Linux/macOS users. All command-line examples and API references are Windows-centric, and there is no mention of Linux tooling, CLI alternatives, or cross-platform SDK usage. This creates friction for non-Windows users, especially since Service Fabric supports Linux clusters.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, where applicable.
  • Clarify whether the PowerShell cmdlets have direct equivalents in sfctl or REST APIs and provide those examples.
  • Explicitly state if certain administrative operations are Windows-only, or provide cross-platform alternatives.
  • Include sample commands and screenshots for Linux environments, not just Windows/PowerShell.
  • Mention SDK usage in cross-platform languages (e.g., .NET Core, Java) where relevant.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. Windows file paths and certificate store names are referenced first, with Linux equivalents mentioned only briefly. No Linux CLI (e.g., Bash, sfctl) examples are provided for deployment or endpoint configuration, and Windows terminology/tools appear before Linux alternatives.
Recommendations
  • Add Linux-specific deployment examples using sfctl or Bash scripts alongside PowerShell.
  • Mention Linux file paths and certificate storage locations equally with Windows paths, not as an afterthought.
  • Provide clear guidance for Linux/macOS users on how to perform endpoint configuration and application deployment.
  • Where possible, show cross-platform commands or note differences in tooling and workflow.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a mix of JSON ARM template examples and PowerShell scripts, with a clear preference for Windows-centric tooling and patterns. The Key Vault VM extension is described as 'KeyVaultForWindows', and the linking behavior is explicitly stated as 'Only Windows'. PowerShell is the only scripting language shown for certificate enrollment. While the documentation covers Azure Service Fabric clusters in general, it assumes Windows as the default platform for VM extensions, certificate provisioning, and scripting, with no Linux-specific examples or guidance.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Linux-based clusters.
  • Clarify which steps and extensions are Windows-only, and provide Linux alternatives where available (e.g., Key Vault VM extension for Linux).
  • Include references to Linux certificate stores and provisioning mechanisms, such as using PEM files and configuring certificates in Linux VMSS nodes.
  • Ensure troubleshooting and FAQ sections address Linux scenarios and scripting options.
  • Explicitly state platform limitations and provide links to Linux-specific documentation where relevant.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides detailed explanations of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples primarily in XML and references to both Windows and Linux certificate storage paths. However, troubleshooting sections and tool references are heavily Windows-centric, mentioning Windows event logs, CAPI2 logging, Win32 CryptoAPI, and Windows certificate stores first or exclusively. Linux equivalents are mentioned briefly or as parenthetical notes, but not explained in depth or with examples.
Recommendations
  • Add explicit Linux/macOS troubleshooting guidance, including log locations, relevant commands (e.g., journalctl, syslog), and certificate management tools.
  • Provide Linux/macOS-specific examples for certificate storage, retrieval, and validation (e.g., using OpenSSL, certutil, or systemd paths).
  • Clarify differences in certificate store handling between Windows and Linux, and offer step-by-step instructions for both platforms.
  • Include references to Linux documentation and tools alongside Windows ones, not just as parentheticals.
  • Ensure that troubleshooting error codes and remediation steps are applicable to Linux/macOS, or provide platform-specific guidance.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-21 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. Windows terminology and examples are presented first and most prominently, including a PowerShell command for role assignment. While there are references to Linux custom image creation and Azure CLI usage, Windows-specific language and tools are emphasized, and Linux/macOS equivalents are not provided for all steps.
Recommendations
  • Clarify in the introduction whether Linux images are supported for Service Fabric Managed Clusters and provide parity in examples if so.
  • Add Linux/macOS command-line examples (e.g., Azure CLI or Bash) alongside PowerShell for role assignment and image management.
  • Balance terminology by referring to 'Windows or Linux custom images' where applicable, rather than only 'custom windows images'.
  • Ensure links to Linux documentation are as prominent as Windows links.
  • Explicitly state any limitations or differences for Linux images, if present.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI-based scripting example shown, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the default scripting tool for automation, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on non-Windows platforms who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples for all tasks where PowerShell is used (e.g., adding, removing, scaling node types, configuring placement properties).
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if only Windows PowerShell is supported.
  • Where possible, provide Bash or shell script examples for ARM template deployments.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Add a note clarifying platform compatibility for the provided scripts and tools.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or CLI alternatives in several sections. While the Azure CLI (az resource) is mentioned once for deleting applications, PowerShell is presented as the primary tool for most operations, and examples or guidance for Linux/macOS users are missing.
Recommendations
  • Add Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Explicitly state that Azure CLI can be used on Linux/macOS and provide sample commands.
  • Where possible, include ARM template usage examples that are platform-agnostic.
  • Clarify which management operations can be performed using cross-platform tools and which are PowerShell-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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool primarily available on Windows). There are no equivalent Linux/macOS CLI examples or guidance, and Windows-centric tooling is mentioned first and exclusively.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., using sfctl or REST API) for cluster operations.
  • Clarify whether Service Fabric Explorer is accessible cross-platform or provide alternatives for Linux/macOS users.
  • Mention cross-platform tools and commands alongside PowerShell examples.
  • Explicitly note any limitations or differences for Linux/macOS users.
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-02-21 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-based migration steps for Service Fabric clusters, especially for nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line examples are given in PowerShell, with no equivalent Azure CLI or bash examples. The sample templates referenced are mostly Windows-based, and Windows paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux tools and patterns are not mentioned, and Linux migration steps are not provided, despite Service Fabric supporting Linux node types.
Recommendations
  • Add Azure CLI/bash equivalents for all PowerShell migration commands, especially for resource deployment, node disabling/removal, and DNS updates.
  • Reference and provide Linux sample templates alongside Windows templates, ensuring parity in guidance.
  • Use OS-agnostic paths or clarify when Windows-specific paths are required; provide Linux path examples where applicable.
  • Mention Linux node type migration considerations and highlight any differences or similarities.
  • Ensure that instructions for disabling/removing nodes and updating resources are available for Linux clusters, not just Windows clusters.
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-02-21 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 demonstrates a notable Windows bias. All code examples are for Windows containers (using Windows NanoServer images and Windows CMD commands), and the only command-line querying example is via PowerShell. There are no Linux container examples, nor are Linux shell commands or tools mentioned. The documentation assumes familiarity with Windows container development and omits Linux equivalents.
Recommendations
  • Add equivalent examples for Linux containers (e.g., using Ubuntu or Alpine images and bash commands).
  • Provide instructions and sample manifests for Linux container scenarios.
  • Include Linux shell command examples (e.g., using Bash or CLI tools) for querying deployment status.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide guidance.
  • If Windows-only, explicitly state this limitation at the top of the article.
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-02-21 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 Service Fabric manifests. It recommends opening the ServiceFabricServiceModel.xsd schema file in Visual Studio, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and does not mention Linux/macOS alternatives or cross-platform tools for schema validation or authoring. Additionally, PowerShell is referenced as a way to create service instances, but no Linux CLI equivalent is provided.
Recommendations
  • Provide cross-platform instructions for schema validation and authoring, such as using VS Code or other editors on Linux/macOS.
  • Mention the location of ServiceFabricServiceModel.xsd on Linux clusters, if applicable, or clarify if schema validation is only possible on Windows.
  • Include CLI examples for creating service instances using Azure CLI or Service Fabric CLI (sfctl), not just PowerShell.
  • Avoid referencing Windows file paths exclusively; provide Linux/macOS equivalents or note platform differences.
  • Ensure tooling recommendations (e.g., Visual Studio) are balanced with cross-platform options (e.g., VS Code, XML lint tools).
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there is a noticeable Windows bias in several areas. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are mentioned first or exclusively, while Linux equivalents are referenced later or with less detail. Some examples and tutorials focus on Windows/.NET applications, and Linux-specific guidance is often relegated to links or brief notes. EventStore APIs are Windows-only, and Linux configuration is described as 'different' without concrete examples. Overall, Linux users can achieve parity, but must navigate more friction and less direct guidance.
Recommendations
  • Provide Linux-specific monitoring examples and walkthroughs alongside Windows examples, not just as links.
  • When referencing tools (e.g., Event Viewer, Diagnostics Agent), immediately mention Linux equivalents (e.g., Syslog, Azure Monitor agent) and provide parallel instructions.
  • Add explicit Linux sample code or configuration snippets for cluster and infrastructure monitoring.
  • Clarify which features are Windows-only and offer alternative approaches for Linux users where possible.
  • Ensure tutorials and sample queries are applicable to both platforms, or provide Linux-specific variants.
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-02-21 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 platform-agnostic manner, but several sections show Windows bias. Windows-specific features (such as Active Directory domain accounts and gMSA) are mentioned before Linux equivalents or without Linux alternatives. Disk encryption is referenced only via BitLocker and PowerShell, with Linux disk encryption left as a TODO. Some examples and explanations focus on Windows tools and patterns, and Linux-specific guidance is missing or deferred.
Recommendations
  • Add explicit Linux examples and guidance where only Windows is mentioned, especially for disk encryption and user account management.
  • Ensure Linux equivalents (such as Linux disk encryption methods, Linux user/group management) are described alongside Windows features.
  • Where Windows tools (e.g., PowerShell, BitLocker, AD accounts, gMSA) are referenced, provide links or instructions for Linux alternatives (e.g., LUKS for disk encryption, Linux service accounts).
  • Review examples and ensure both Windows and Linux scenarios are covered, or clarify when a feature is Windows-only.
  • Update TODOs to include actionable Linux guidance rather than leaving them as placeholders.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are mentioned in nearly every lifecycle phase, often before or instead of Linux-friendly alternatives. There is no explicit mention of Linux/macOS command-line equivalents (such as Azure CLI or sfctl), and no Linux-specific examples or guidance are provided. The [!INCLUDE [links to azure cli and service fabric cli](./includes/service-fabric-sfctl.md)] is present, but actual usage examples or parity are missing throughout the main content.
Recommendations
  • Add explicit examples and instructions using Azure CLI and sfctl for each lifecycle phase (deploy, upgrade, remove, etc.), ensuring Linux/macOS users can follow along without PowerShell.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI/sfctl commands side-by-side.
  • Clarify which tools are cross-platform and which are Windows-only, and link to Linux/macOS-specific guidance where available.
  • Review all code snippets and procedural steps to ensure Linux/macOS users are not left out or forced to infer their own equivalents.
  • Consider reordering examples so that cross-platform tools (Azure CLI/sfctl/REST) 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-02-21 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 numerous PowerShell cmdlet examples for Service Fabric application upgrades, with no equivalent CLI or Linux/macOS instructions. All command-line examples use PowerShell syntax, and references to tooling (such as Visual Studio) are Windows-centric. There is no mention of Service Fabric CLI (sfctl), Bash, or cross-platform alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include Bash or generic shell command examples where applicable, alongside PowerShell.
  • Mention cross-platform tools and workflows, such as using sfctl or Azure portal, in addition to Visual Studio and PowerShell.
  • Clarify which features or commands are Windows-only, and provide guidance for Linux/macOS users where parity exists.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No equivalent Linux/macOS upgrade examples or tooling are mentioned. The core serialization guidance is platform-neutral, but the 'Next steps' section directs users to Windows-first workflows.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using Linux/macOS-compatible tools (e.g., Azure CLI, REST API, or cross-platform SDKs).
  • Explicitly mention if PowerShell Core is supported on Linux/macOS, and provide relevant examples if so.
  • Provide parity by including upgrade tutorials for Linux environments, or clarify if Service Fabric application upgrades are Windows-only.
  • If Visual Studio is Windows-only for Service Fabric upgrades, suggest alternative IDEs or command-line options for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio upgrade parameters first and in greater detail, with tables and examples, before mentioning the cross-platform Service Fabric CLI (sfctl). PowerShell is emphasized throughout, and parameter tables are labeled 'PowerShell, Visual Studio' even when CLI equivalents exist. Linux/macOS users must scroll past Windows-focused content to reach CLI information, and CLI parameters are described with less detail and fewer examples.
Recommendations
  • Reorganize the page to present upgrade methods in a neutral order (e.g., PowerShell, Visual Studio, SFCTL, REST), or start with cross-platform tools like SFCTL.
  • Add equivalent parameter tables and examples for SFCTL, matching the detail given for PowerShell.
  • Clarify that PowerShell is Windows-only and highlight SFCTL as the recommended cross-platform tool for Linux/macOS users.
  • Provide example upgrade commands for SFCTL, including parameter usage, similar to PowerShell examples.
  • Consider grouping upgrade methods by platform (Windows vs. cross-platform) or clearly marking which tools are platform-specific.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-21 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 on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples and instructions using PowerShell modules and commands. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The Service Fabric Explorer UI is mentioned, but the primary automation and scripting guidance is Windows-centric.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Mention any cross-platform CLI tools (e.g., Azure CLI, sfctl) that can be used for backup operations, and provide examples.
  • Clarify whether the PowerShell module is available or supported on PowerShell Core for Linux/macOS, and if so, provide installation instructions.
  • Consider restructuring sections so that REST API usage is shown in a cross-platform way (e.g., curl), not only via PowerShell.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, specifically using the Microsoft.ServiceFabric.Powershell.Http module and PowerShell scripting. All code examples are provided in PowerShell, with no equivalent examples for Linux/macOS users (e.g., Bash, curl, or cross-platform CLI tools). The prerequisite section also requires installation of a PowerShell module, and REST API calls are demonstrated only via PowerShell. There is no mention of Linux-compatible tools or instructions for users on non-Windows platforms.
Recommendations
  • Add REST API examples using curl or HTTPie for cross-platform compatibility.
  • Document how to authenticate and make Service Fabric REST calls from Linux/macOS (e.g., using client certificates).
  • Mention and provide guidance for Azure CLI or other cross-platform tools if available.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all restore operations, or if REST calls can be made directly from any OS.
  • Include a section or note for Linux/macOS users outlining supported workflows and any limitations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST API usage. However, in the 'File share' backup storage section, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described, with no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts) or authentication methods. There are no examples or guidance for Linux users on configuring file share backup storage.
Recommendations
  • Add examples and instructions for configuring file share backup storage from Linux nodes, including SMB/CIFS mount paths and authentication options.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide guidance on Linux-compatible file share paths and credential handling.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
  • If file share backup storage is Windows-only, explicitly state this to avoid confusion for Linux users.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides several PowerShell-based examples and instructions for scaling operations (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/bash/CLI commands or guidance. This creates friction for Linux users, who may not have access to PowerShell or may be unfamiliar with its usage. The documentation does mention Linux clusters in the 'Next steps' section, but operational guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or bash commands for all PowerShell examples, especially for node management tasks (e.g., disabling/removing nodes).
  • Explicitly note if certain operations must be performed from a Windows environment, and suggest alternatives or workarounds for Linux users.
  • Add links or references to Linux-specific Service Fabric management documentation where available.
  • Clarify in each example whether the command is cross-platform or Windows-only.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux Resource Manager template samples, but several sections show Windows bias. PowerShell is used for deployment and upgrade examples, with no equivalent Bash or Linux-native commands. Windows-specific tools and registry keys are referenced for VM patching, while Linux equivalents are missing. Windows configuration properties are shown, but Linux VM configuration is not. Upgrade instructions use Windows MSI packages and PowerShell, with no Linux (DEB) example provided.
Recommendations
  • Add Bash or Azure CLI examples for deployment and upgrade tasks alongside PowerShell.
  • Include Linux VM configuration properties (e.g., osProfile.linuxConfiguration) in template snippets.
  • Provide Linux-specific guidance for patch management (e.g., disabling automatic updates on Linux VMs).
  • Show how to manually upgrade clusters using Linux tools and DEB packages, not just Windows MSI and PowerShell.
  • Ensure that for every Windows registry or configuration reference, a Linux equivalent (if applicable) is mentioned.
GitHub Create Pull Request
← Previous Page 43 of 99 Next →