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 1751-1775 of 2475 flagged pages
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent CLI or Linux/macOS instructions. No Linux tools or cross-platform alternatives are mentioned, and the only command-line guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, if available.
  • Clarify whether the PowerShell command can be run using Azure Cloud Shell (which supports PowerShell on Linux/macOS), or if it is strictly for Windows environments.
  • Mention any cross-platform tools or approaches for managing Service Fabric Infrastructure Service.
  • Explicitly state if certain operations are only supported via PowerShell, and suggest workarounds or alternatives for Linux/macOS users.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily to Azure PowerShell modules for managing Service Fabric managed clusters, with PowerShell mentioned before Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep are referenced, PowerShell is emphasized in the best practices and example links, which may create friction for Linux/macOS users who prefer CLI or scripting tools native to their platforms.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI before or equally with PowerShell in best practices to highlight cross-platform support.
  • Clarify that Azure PowerShell is available cross-platform, but also link to CLI documentation for parity.
  • Add sample commands for ARM/Bicep deployments and management where relevant.
  • Ensure that references to 'Node blade on the Azure portal' are supplemented with CLI/ARM/Bicep alternatives for automation scenarios.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as the primary means for managing Service Fabric clusters, without mentioning Linux equivalents such as Azure CLI or REST API usage. The mention of 'Windows security' as a transport security option, while not inherently biased, is not balanced by mentioning Linux-compatible authentication mechanisms.
Recommendations
  • Include Azure CLI examples or references for cluster and application management tasks alongside PowerShell.
  • Clarify that management operations can also be performed using REST APIs or Azure CLI, which are cross-platform.
  • Mention Linux-compatible authentication mechanisms (e.g., X509 certificates) more prominently when discussing security.
  • Add a note or section highlighting cross-platform management options for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but several sections and examples show a Windows bias. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) and certificate store references, with no Linux equivalent shown. The 'Next steps' section links to PowerShell scripts for Windows-centric tasks (RDP port range, admin username/password changes) without Linux/SSH alternatives. While the extension type 'ServiceFabricLinuxNode' is mentioned, practical Linux usage examples and guidance are missing.
Recommendations
  • Add Linux-specific examples for configuring Service Fabric nodes, including file paths and certificate stores.
  • Include guidance or links for Linux/macOS users on how to remotely connect to scale set instances (e.g., SSH instead of RDP).
  • Provide parity in 'Next steps' by including Linux/SSH-based instructions for changing admin credentials and port ranges.
  • Clarify where Windows-specific instructions apply and offer alternatives for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-centric deployment guide as the next step. While .NET and REST options are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS command-line examples (such as Bash or Azure CLI), nor is there mention of cross-platform tooling for cluster management.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, to provide parity for Linux/macOS users.
  • Include links to cross-platform tools or documentation (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell references.
  • Ensure that deployment and management instructions are not solely tied to Visual Studio or PowerShell, but also reference other supported environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select appropriate options.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-08 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 querying Service Fabric partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux or cross-platform CLI example is given. The example and command syntax are Windows-centric, and the documentation implicitly assumes Windows as the primary environment for management tasks.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Mention cross-platform management tools and clarify which commands are available on Linux/macOS.
  • Provide guidance or links for Linux/macOS users to achieve similar tasks, such as querying partition health.
  • Consider showing both Windows and Linux examples side-by-side to improve parity.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, several sections reference Windows-specific tools (PowerShell) and Windows OS patching, with no explicit mention of Linux equivalents or examples. In particular, the 'Upgrading OS images for cluster nodes' section links only to Windows patching guidance, and throughout, PowerShell is mentioned before Azure CLI, with no Linux-specific guidance or examples.
Recommendations
  • Add explicit references and links to Linux patching/upgrading guidance for Service Fabric clusters, if supported.
  • Provide Linux-specific examples (e.g., using Bash or Azure CLI on Linux/macOS) alongside PowerShell examples.
  • Clarify whether Service Fabric cluster upgrade and management features are supported on Linux, and if so, include relevant instructions.
  • When mentioning tools, list Azure CLI before or alongside PowerShell, and note cross-platform compatibility.
  • If certain features (like Patch Orchestration Application) are Windows-only, explicitly state this to avoid confusion.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for Service Fabric application and service manifest examples demonstrates mild Windows bias. Windows terminology (e.g., 'Administrators', 'NetworkService', 'Setup.bat', 'VotingWeb.exe') is used throughout, and references to running scripts or executables (such as .bat files) are Windows-centric. The only mention of tooling is the 'ServiceFabric PowerShell module', with no Linux CLI or cross-platform alternatives. User and group examples reference Windows system groups and accounts, and there is no explicit guidance for Linux deployments or examples using Linux conventions.
Recommendations
  • Add Linux-specific examples (e.g., using shell scripts like Setup.sh instead of Setup.bat, and referencing Linux user/group conventions).
  • Mention cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) alongside PowerShell.
  • Clarify which elements or features are supported on Linux clusters and provide guidance for Linux users where applicable.
  • Where possible, use neutral terminology for user/group names and executable formats (e.g., .exe vs. .out or generic names).
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant, with explicit notes about Windows-specific behaviors (such as 'linkOnRenewal'). Windows terminology and tooling (certificate stores, ACLing, S-channel, etc.) are used throughout, and Linux equivalents are not mentioned or provided. The documentation assumes Windows as the default platform for VM extensions and certificate handling, with no guidance for Linux-based clusters or cross-platform scenarios.
Recommendations
  • Provide equivalent Linux examples for certificate enrollment and provisioning, such as using Azure CLI or Bash scripts.
  • Mention and document the Key Vault VM extension for Linux, including its schema and behavioral differences.
  • Clarify which steps, tools, and mechanisms are Windows-specific and which are cross-platform, especially regarding certificate stores and ACLing.
  • Add troubleshooting and FAQ entries relevant to Linux clusters.
  • Where PowerShell is used, offer Azure CLI or Bash alternatives for 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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are presented first or exclusively. Linux equivalents are mentioned briefly (e.g., /var/lib/sfcerts), but lack detailed guidance or parity in examples and troubleshooting steps.
Recommendations
  • Expand Linux-specific guidance for certificate storage, retrieval, and troubleshooting (e.g., provide detailed instructions for accessing Service Fabric logs and certificate stores on Linux).
  • Include Linux/macOS equivalents for Windows API references and tools (e.g., OpenSSL commands, Linux certificate validation methods, log locations).
  • Present examples for both Windows and Linux environments side-by-side, ensuring Linux examples are not omitted or relegated to parenthetical notes.
  • Clarify any differences in certificate handling between Windows and Linux Service Fabric nodes, especially for cluster upgrades and certificate rotation.
  • Add troubleshooting steps and error codes relevant to Linux/macOS, including how to diagnose certificate issues on non-Windows platforms.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code samples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell instructions. The PowerShell examples are prominent and used for critical operations (add, remove, scale, configure placement properties), and are mentioned before or instead of cross-platform alternatives. This creates friction for Linux/macOS users, who must either use the Portal or ARM templates, but lack CLI parity.
Recommendations
  • Add Azure CLI examples for all PowerShell operations (add, remove, scale, configure placement properties, etc.), since Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where possible, include Bash shell or Azure CLI scripts alongside PowerShell, or clarify if certain operations are only possible via PowerShell.
  • Review the order of examples to avoid always presenting Windows/PowerShell first; consider alternating or grouping by platform.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-08 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 Initializer CodePackages in Service Fabric presents only Windows container examples, uses Windows-specific images (nanoserver), Windows paths (C:\), and Windows commands (cmd, echo, type, ping). There is no mention of Linux container support, nor are Linux examples or equivalents provided. The page assumes familiarity with Windows container creation and does not address Linux scenarios.
Recommendations
  • Add examples for Linux containers, using Linux-compatible images and commands.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric.
  • If supported, provide Linux path and volume mount examples alongside Windows examples.
  • Mention Linux container version compatibility and relevant documentation links.
  • If Initializer CodePackages are Windows-only, explicitly state this in the introduction.
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-08 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 Azure Service Fabric clusters on both Windows and Linux, but there is a noticeable Windows bias. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are mentioned first or in more detail, while Linux equivalents are referenced later or with less explanation. Some examples and tutorials focus on .NET applications, which are cross-platform, but the monitoring setup and event channels are described with Windows patterns first. Linux-specific instructions and tools are often referenced as 'different configuration' or linked out, rather than explained inline. The EventStore APIs are noted as Windows-only, but Linux alternatives are not clearly described. Overall, Linux users can complete the tasks, but may face friction due to less direct guidance.
Recommendations
  • Provide Linux-specific examples and instructions inline, not just as links.
  • When describing monitoring tools or event channels, present Windows and Linux approaches side-by-side.
  • Clarify Linux equivalents for Windows tools (e.g., Event Viewer vs. Syslog/LTTng) and provide sample commands or screenshots.
  • Expand Linux cluster monitoring tutorials to match the detail of Windows-focused tutorials.
  • Explicitly note when features are Windows-only and offer Linux alternatives or workarounds.
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-08 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 methods. There is little to no mention of Linux-specific tools or CLI equivalents (such as sfctl or Azure CLI), and no explicit Linux/macOS usage examples. This creates friction for non-Windows users, as PowerShell is primarily a Windows-centric tool and Service Fabric supports Linux clusters as well.
Recommendations
  • Add examples using sfctl (Service Fabric CLI) and Azure CLI for each operation, especially for deploy, upgrade, remove, and maintenance tasks.
  • Explicitly mention Linux/macOS support and provide guidance for those environments.
  • Where PowerShell is referenced, also provide the equivalent sfctl or REST command, and clarify which tools are cross-platform.
  • Consider reordering examples so that cross-platform tools (sfctl, REST, Azure CLI) are listed before or alongside PowerShell.
  • Add a section or note about managing Service Fabric applications on Linux clusters, including any differences or limitations.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-08 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 in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples featured. While there is a brief reference to Linux custom image creation, the main workflow, examples, and tooling are Windows-centric, and PowerShell is used for role assignment without a Linux CLI equivalent. Linux users may need to infer or adapt steps.
Recommendations
  • Provide explicit Linux/CLI examples for role assignment (e.g., using Azure CLI instead of only PowerShell).
  • Clarify that custom images can be Linux-based, and include sample ARM template snippets for Linux images.
  • Balance references to Windows and Linux documentation and tools throughout the page.
  • Add a section or note for Linux users outlining any differences or considerations when deploying Linux custom images.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples and walkthroughs are Windows-centric. Windows container images (nanoserver), Windows-specific commands (cmd, echo, ping, set), and PowerShell tools are used exclusively. No Linux container examples, Linux shell commands, or Linux querying methods are provided, and Windows terminology appears first throughout.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) with Linux shell commands.
  • Provide sample ServiceManifest.xml and ApplicationManifest.xml for Linux containers.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, Bash scripts) or cross-platform methods.
  • Clarify which aspects are Windows-only and which are cross-platform, to help Linux/macOS users understand applicability.
  • Consider presenting Linux and Windows examples side-by-side for parity.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides some Windows-specific examples and references (e.g., Active Directory, gMSA, BitLocker, PowerShell disk encryption), often mentioning Windows tools or features before Linux equivalents. Linux-specific guidance is sometimes missing or relegated to TODO comments, especially for disk encryption and user account management. While the page covers both Windows and Linux clusters in some sections, there is a notable tendency to prioritize Windows scenarios and omit Linux parity in critical areas.
Recommendations
  • Add explicit Linux examples and instructions for disk encryption (currently only a TODO comment).
  • Provide parity for user account management on Linux clusters, including how to run services under different accounts and secure resources.
  • Ensure that all PowerShell or Windows tool references are accompanied by Linux equivalents (e.g., Bash, CLI, or relevant Linux tools).
  • Mention Linux options alongside Windows ones, rather than after or as an afterthought.
  • Clarify which features are Windows-only and provide alternative guidance for Linux where possible.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-08 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 heavily relies on PowerShell cmdlets for examples and instructions, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line examples are PowerShell-based, and references to Visual Studio are made without alternatives for non-Windows environments. There is no guidance for Linux 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 alongside PowerShell cmdlets for all upgrade operations.
  • Explicitly mention whether PowerShell cmdlets can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Include references to cross-platform tools or scripts for Service Fabric management.
  • Provide alternatives to Visual Studio for packaging and upgrading applications, such as using the Service Fabric CLI (sfctl) or other build tools.
  • Clarify which features or steps are Windows-only and which are cross-platform.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-08 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 upgrade exhibits Windows bias by providing only PowerShell examples, referencing Windows-specific tools (http.sys), and lacking equivalent Linux CLI or SDK examples. Additionally, upgrade tutorials are linked for Visual Studio and PowerShell, both Windows-centric, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Add CLI or SDK-based examples for application upgrades that work on Linux/macOS (e.g., Azure CLI, Service Fabric CLI, REST API, or Python SDK).
  • Include explicit notes about cross-platform support and limitations, clarifying which features are Windows-only and which are available on Linux clusters.
  • Provide links or sections for Linux/macOS users, such as 'Upgrading your Application Using Service Fabric CLI' or 'Upgrading your Application Using REST API'.
  • Mention Linux-specific considerations (such as certificate handling, port management, and health checks) where relevant.
  • Ensure that examples and tutorials are not exclusively Windows-first; alternate between platforms or provide parity.
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-08 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 Linux/macOS equivalents (such as CLI or cross-platform tools) are mentioned or linked. The serialization guidance is focused on C# and .NET, which are cross-platform, but the upgrade workflow examples are Windows-first.
Recommendations
  • Add links or sections for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Mention and provide examples for upgrading Service Fabric applications from Linux/macOS environments.
  • Clarify which upgrade methods are Windows-only and suggest alternatives for Linux/macOS users.
  • Consider including a note about cross-platform support for .NET Core/.NET 5+ serialization if relevant.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) before mentioning cross-platform options (SFCTL and REST). The parameter tables and explanations are structured with PowerShell and Visual Studio examples first, and only later describe SFCTL (the CLI used on Linux/macOS). While all major options are covered, the ordering and example emphasis create a Windows-first impression.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL and REST) are presented before or alongside Windows-specific tools (PowerShell and Visual Studio).
  • Provide parameter tables and examples for SFCTL and REST in parallel with PowerShell/Visual Studio, rather than after them.
  • Add explicit notes clarifying which tools are cross-platform and which are Windows-only.
  • Include sample upgrade commands for SFCTL in the main parameter sections, not just in the 'Next steps'.
  • Consider a summary comparison table showing parameter mappings across PowerShell, Visual Studio, SFCTL, and REST.
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-08 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 on-demand backup in Azure Service Fabric is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no CLI, Bash, or Linux-native examples, nor any mention of how to perform these operations from Linux/macOS. The use of PowerShell-specific modules and commands creates friction for non-Windows users, and the documentation does not clarify cross-platform alternatives.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API calls with curl for Linux/macOS users.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • If REST API is the recommended cross-platform method, provide explicit curl or HTTP request examples for Linux/macOS.
  • Indicate any platform limitations and guide Linux/macOS users to supported tooling.
  • Consider reordering examples so that cross-platform methods (REST API, CLI) are presented 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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes backup configuration for Azure Service Fabric, which is a cross-platform technology. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are mentioned. There are no examples or guidance for Linux-based file shares (e.g., NFS, SMB on Linux), nor is there discussion of Linux authentication patterns. The documentation does not provide Linux-specific examples or parity for file share backup configuration.
Recommendations
  • Add examples for configuring file share backup storage using Linux-based file shares (e.g., NFS, SMB on Linux).
  • Include guidance for authentication to file shares from Linux nodes, such as using mount options, credentials, or Kerberos.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide relevant configuration details.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
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-08 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 restoring backups in Azure Service Fabric is heavily biased towards Windows, with all command-line examples provided exclusively in PowerShell. The prerequisite explicitly requires installation of a PowerShell module, and all REST API usage is demonstrated via PowerShell scripts. There are no Linux/macOS shell (bash/curl) examples, nor any mention of cross-platform tools or workflows. This creates friction for Linux/macOS users who may wish to automate or script these operations.
Recommendations
  • Add equivalent bash/curl examples for REST API calls, demonstrating how to trigger restore and track progress from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any platform.
  • Mention cross-platform alternatives or note any limitations for Linux/macOS users.
  • Include guidance on certificate handling for REST API calls from Linux/macOS (e.g., using OpenSSL or curl options).
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-08 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 the manual scaling sections rely exclusively on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is referenced first and exclusively in critical operational steps, while Linux users are left to infer possible approaches. No Bash, CLI, or REST API examples are provided for Linux environments, and the documentation does not clarify whether these PowerShell commands are available or supported on Linux clusters.
Recommendations
  • Add equivalent instructions and examples for Linux clusters, using Bash, Azure CLI, or REST API where appropriate.
  • Clarify whether PowerShell commands are supported on Linux clusters, and if not, provide alternative workflows.
  • Include cross-platform guidance for manual scaling operations, ensuring Linux users can follow the same procedures.
  • Present examples for both Windows and Linux environments side-by-side, or clearly indicate platform-specific steps.
GitHub Create Pull Request
← Previous Page 71 of 99 Next →