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 976-1000 of 2475 flagged pages
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and its usage is emphasized before cross-platform alternatives. However, the inclusion of sfctl CLI commands mitigates the bias, allowing Linux/macOS users to complete the tasks.
Recommendations
  • Present sfctl CLI examples before or alongside PowerShell examples to avoid implying Windows-first workflows.
  • Clarify that sfctl is the recommended cross-platform tool for Linux/macOS users.
  • Explicitly mention platform compatibility for each tool (e.g., 'PowerShell (Windows only)', 'sfctl CLI (cross-platform)').
  • Ensure parity in detail and explanation between PowerShell and sfctl sections.
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-23 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 PowerShell-based deployment guides in the 'Next steps' section. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor is it clarified whether PowerShell Core is supported on Linux/macOS. The overall guidance assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Add Azure CLI or Bash examples for retrieving cluster manifests and deploying/removing applications, where possible.
  • Clarify whether PowerShell Core on Linux/macOS is supported for Service Fabric operations.
  • Include links to cross-platform deployment documentation or note any limitations for non-Windows users.
  • Balance example ordering so that cross-platform approaches are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing Service Fabric application parameters across environments, but it shows a notable Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in detail, while Linux/macOS equivalents (sfctl, install.sh) are referenced later and with less explanation. There are no explicit Linux/macOS-specific examples or guidance, and the workflow is oriented toward Windows tools.
Recommendations
  • Add explicit Linux/macOS examples for parameter passing, such as using sfctl and install.sh, with step-by-step instructions.
  • Provide parity in example scripts for both PowerShell (Windows) and Bash (Linux/macOS).
  • Mention cross-platform tools and workflows before or alongside Windows-specific ones.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriately.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides container application manifest examples for Azure Service Fabric, but it is notably Windows-centric. The examples are based on the Windows Server 2016 Container Sample, and references to Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths) appear before or instead of Linux equivalents. There are no explicit Linux container manifest examples or references to Linux-specific patterns, even though Service Fabric supports Linux containers. The certificate handling section does mention Linux (PEM files), but overall, Linux users are left to infer their own adaptations.
Recommendations
  • Add explicit Linux container manifest examples, or clarify which elements are cross-platform.
  • Provide Linux-specific guidance for OS build detection (e.g., using 'uname -r' or '/etc/os-release') alongside 'winver'.
  • Include Linux file path examples (e.g., '/mnt/data') in volume bindings, not just Windows paths (e.g., 'c:\VolumeTest\Data').
  • Reference Linux container samples or link to relevant documentation.
  • Ensure that cross-platform features (such as certificate handling, resource governance, environment variables) are demonstrated for both Windows and Linux containers.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-23 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 only PowerShell-based deployment examples and references Windows-centric tools (e.g., RDP, PowerShell) without offering equivalent Linux/macOS instructions or CLI examples. Windows tools and patterns are mentioned first and exclusively, creating friction for Linux/macOS users who may prefer Azure CLI or Bash. No Linux-specific guidance is given for template deployment, VM access, or cluster management.
Recommendations
  • Add Azure CLI (az) command examples for deploying ARM templates, alongside PowerShell.
  • Include instructions for accessing VMs via SSH, not just RDP, and clarify jump box usage for Linux/macOS users.
  • Mention cross-platform tools and patterns (e.g., Bash, Azure CLI, SSH) wherever PowerShell or Windows tools are referenced.
  • Provide sample template deployment steps for Linux/macOS environments.
  • Ensure that examples and guidance are not Windows-first; present cross-platform options equally.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations, with no mention of Linux/macOS equivalents or CLI usage. All example commands and API references are Windows-centric, and there is no guidance for users managing Service Fabric clusters from Linux or macOS. This creates friction for non-Windows users, though workarounds may exist via FabricClient APIs or REST endpoints.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document how to perform replica soft delete and restore operations using FabricClient APIs in .NET Core or other cross-platform SDKs.
  • Clarify whether the PowerShell cmdlets are available only on Windows, and provide alternative instructions for Linux/macOS users.
  • Include sample commands and screenshots for Linux/macOS environments where possible.
  • Explicitly state platform limitations if certain features are Windows-only.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core service hosting in Azure Service Fabric. However, Windows tools and patterns (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before or alongside Linux-compatible options. HTTP.sys is clearly marked as Windows-only, but Windows-centric configuration steps (e.g., netsh, Endpoint configuration for HTTP.sys) are described without Linux equivalents. Visual Studio debugging is referenced as a next step, which is Windows-centric. Kestrel, the cross-platform option, is recommended for Linux, but Windows tools and patterns are prominent throughout.
Recommendations
  • Ensure that Linux/macOS users are guided toward Kestrel as the default/cross-platform option, and make this recommendation more prominent at the start of the article.
  • Where Windows-specific tools (e.g., netsh, HTTP.sys) are discussed, explicitly state that these steps are not applicable to Linux/macOS and provide alternative guidance or clarify that Kestrel should be used.
  • Add a section or callout summarizing Linux/macOS development workflow, including debugging, deployment, and configuration differences.
  • When referencing Visual Studio, mention cross-platform alternatives (e.g., VS Code, CLI tools) for Linux/macOS users.
  • Consider reordering sections so that Kestrel (cross-platform) guidance appears before HTTP.sys (Windows-only) guidance.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-23 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 examples for reporting health in Service Fabric using PowerShell, with explicit PowerShell command snippets and references to Windows paths (e.g., PS C:\>). While API and REST methods are mentioned, only PowerShell is demonstrated in depth, and there are no equivalent Linux/bash CLI examples or references to cross-platform tools. The PowerShell examples are presented before REST, and no mention is made of Azure CLI or bash scripting, which would be relevant for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for health reporting, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Mention REST as a cross-platform method earlier and provide more detailed REST examples, including sample curl commands.
  • Explicitly note any limitations or parity gaps for Linux/macOS users, and link to relevant cross-platform tooling.
  • Consider reordering sections so REST and API examples are presented before or alongside PowerShell.
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-23 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 mentioned first, with Linux equivalents referenced only briefly. There are no Linux CLI (e.g., Bash, sfctl) examples for deployment, and Windows terminology/tools appear before Linux alternatives.
Recommendations
  • Add Linux deployment examples using sfctl or Bash scripts alongside the PowerShell example.
  • Mention Linux file paths and certificate store locations earlier and more prominently, not just as a note.
  • Clarify any differences in endpoint configuration or deployment steps for Linux clusters.
  • Where possible, provide cross-platform guidance or links to Linux-specific documentation.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Visual Studio workflows, with repeated references to Visual Studio-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI screenshots. There are no examples or guidance for Linux/macOS users or CLI-based workflows. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, but no Linux-native tools or cross-platform CLI instructions are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml and ApplicationManifest.xml outside Visual Studio.
  • Provide CLI-based examples (e.g., Azure CLI, Service Fabric CLI) for deploying and configuring applications, not just PowerShell.
  • Clarify which features are Visual Studio-only and offer alternatives for non-Windows environments.
  • Include screenshots or workflow descriptions for cross-platform development environments (e.g., VS Code, JetBrains Rider).
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking). Windows terminology and patterns are presented first and in detail, while Linux-specific guidance, examples, or parity are largely absent. The Key Vault VM extension is described as Windows-specific, and there are no Bash/CLI/Linux automation examples for certificate management or provisioning. Troubleshooting and scripting sections rely exclusively on PowerShell.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment, provisioning, and automation, especially for Linux-based Service Fabric clusters.
  • Clarify which features and extensions are Windows-only and provide Linux alternatives or note limitations for Linux users.
  • Include documentation or links for Linux certificate management tools (e.g., OpenSSL, Azure CLI) and how to automate certificate provisioning on Linux nodes.
  • Explicitly state any differences in certificate management workflows between Windows and Linux clusters, and provide guidance for Linux users where possible.
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-22 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 conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology, tools, and patterns (such as certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively. Troubleshooting sections focus on Windows event logs and CAPI2 logging, with little to no guidance for Linux equivalents. While Linux is referenced (e.g., '/var/lib/sfcerts'), Windows-centric examples and APIs dominate, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Linux-specific examples for certificate storage, retrieval, and troubleshooting (e.g., using OpenSSL, Linux certificate stores, and relevant log locations).
  • When referencing certificate stores, mention both Windows and Linux paths equally and provide guidance for Linux users.
  • Include troubleshooting steps for Linux clusters, such as relevant log files, commands, and error codes.
  • Where Windows APIs (e.g., CertGetCertificateChain) are discussed, clarify the Linux equivalent behavior or implementation.
  • Balance examples and terminology so that Linux and Windows users can follow the documentation without ambiguity.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters. Windows terminology and examples are used throughout, and the only command-line example provided is in PowerShell. While there are references to Linux custom image creation and Azure CLI for browsing marketplace images, the main workflow and examples focus on Windows, with no Linux-specific deployment examples or shell commands.
Recommendations
  • Provide equivalent Linux shell (bash/CLI) examples for role assignment and image deployment.
  • Clarify in the introduction whether Linux node types are supported and, if so, include Linux-specific guidance.
  • Add ARM template examples and workflows for deploying Linux custom images, if supported.
  • Ensure that references to Linux documentation are accompanied by actionable steps for Linux users.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, but consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) as the primary tooling for resource management. While az CLI is mentioned once for deleting applications, PowerShell examples and terminology are more prominent, and no explicit Linux/macOS command examples or guidance are given. This creates friction for non-Windows users, as PowerShell is less common on Linux/macOS and az CLI is the cross-platform standard.
Recommendations
  • Provide equivalent az CLI commands for all management operations (e.g., deleting, creating, scaling resources) alongside PowerShell examples.
  • Clarify that az CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Add explicit Linux/macOS instructions or notes where appropriate, ensuring parity in examples and guidance.
  • Consider linking to az CLI documentation for Service Fabric management.
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-22 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 page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, set, ping), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based Service Fabric clusters.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide guidance or code snippets for querying deployment status using Azure CLI or Linux-native tools.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in documentation.
  • Include notes or links for Linux/macOS users on how to adapt the examples.
  • If RunToCompletion is Windows-only, explicitly state this early in the article to avoid confusion.
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-22 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 for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and sfctl references. While Azure CLI and ARM/Bicep are also mentioned, the explicit examples and guidance focus on PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Clarify that Azure CLI and sfctl are cross-platform and suitable alternatives to PowerShell.
  • Reorder tool mentions so that cross-platform tools (Azure CLI, ARM templates, Bicep) are listed before PowerShell.
  • Add sample commands for sfctl where relevant, especially 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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell-based migration steps and examples, especially in the section for migrating Service Fabric nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line instructions use PowerShell cmdlets (e.g., New-AzureRmResourceGroupDeployment, Connect-ServiceFabricCluster, Disable-ServiceFabricNode), which are Windows-centric and do not offer equivalent Bash/Azure CLI examples. Additionally, the sample template for Linux (Ubuntu) is referenced, but the migration steps and tooling remain Windows/PowerShell-focused. The documentation also uses Windows file paths (e.g., 'D:\\SvcFab') in configuration examples, further reinforcing Windows bias.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell migration steps, especially for disabling/removing nodes and updating resources.
  • Clarify which steps can be performed on Linux/macOS and which require Windows, and offer guidance for cross-platform users.
  • Include Linux file path examples (e.g., '/var/svcfab') alongside Windows paths in configuration snippets.
  • Reference and link to Linux/macOS tooling or scripts where available.
  • Ensure sample templates and walkthroughs for Linux clusters include migration instructions using cross-platform tools.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation contains evidence of Windows bias. The only tooling example for validating manifest XML schema is Visual Studio on Windows, referencing a Windows file path. There is a mention of using the ServiceFabric PowerShell module to create service instances, but no equivalent Linux CLI example is provided. Windows tools and patterns (Visual Studio, PowerShell) are mentioned exclusively or before any Linux alternatives, and no Linux/macOS-specific guidance or parity is offered.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other XML editors available on Linux/macOS).
  • Provide examples for creating service instances using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform, alongside or instead of PowerShell.
  • Reference file paths and tooling in a platform-neutral way, or provide Linux/macOS equivalents where possible.
  • Explicitly note any Windows-only steps and offer Linux/macOS 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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for 'Application lifecycle in Service Fabric' repeatedly references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) alongside .NET APIs and REST operations. PowerShell examples are given for automation and cleanup, with no equivalent Linux shell or cross-platform CLI (sfctl/Azure CLI) examples. Windows tools and cmdlets are often mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform, for each lifecycle operation (deploy, upgrade, remove, cleanup).
  • Where PowerShell cmdlets are referenced, also provide equivalent sfctl or Azure CLI commands.
  • Ensure REST API references are accompanied by practical usage examples (e.g., curl commands) for Linux/macOS users.
  • Clarify which operations can be performed using cross-platform tools and which are Windows-only.
  • Consider including bash or shell script snippets for automation tasks, especially in sections currently showing only PowerShell.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or appear first, while Linux equivalents are missing or only briefly referenced. Some examples and links are Windows-centric, and Linux guidance is often absent or relegated to TODO comments.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric applications, including container certificate access and disk encryption.
  • Ensure parity in documentation for running services under Linux user accounts, including relevant manifest examples.
  • Provide links to Linux-specific tools and patterns (e.g., disk encryption with dm-crypt/LUKS, Linux container security best practices).
  • Where Windows tools are mentioned (e.g., BitLocker, gMSA), add or reference Linux alternatives or clarify platform limitations.
  • Remove or resolve TODO comments regarding Linux disk encryption and provide actionable guidance.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage). All command-line upgrade instructions and parameter modifications are shown using Windows PowerShell cmdlets, and the PowerShell approach is presented as the default throughout. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell is assumed for all users.
Recommendations
  • Add Azure CLI examples for all upgrade operations (e.g., creating/updating services, starting upgrades, rolling back upgrades, updating parameters).
  • Include REST API sample calls for relevant operations, especially for users on Linux/macOS or those automating upgrades.
  • Clearly indicate which operations are possible via CLI or REST, and provide links to relevant cross-platform documentation.
  • Where PowerShell is referenced, add a note about cross-platform alternatives and their usage.
  • Ensure that ARM template examples are accompanied by CLI/REST deployment instructions 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-22 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 parameters and examples before Linux equivalents (SFCTL). The PowerShell and Visual Studio sections are detailed and appear first, while Linux tooling (SFCTL) is covered later and with less example depth. There are no explicit Linux CLI examples or parameter tables shown first, and the PowerShell-centric approach may create friction for Linux/macOS users.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) parameters and examples alongside or before PowerShell/Visual Studio, especially since SFCTL is cross-platform.
  • Add explicit Linux/macOS command examples using SFCTL for common upgrade scenarios, similar to the PowerShell examples.
  • Clarify that SFCTL is the recommended cross-platform CLI for Service Fabric upgrades, and highlight its parity with PowerShell.
  • Ensure that parameter tables and descriptions for SFCTL are as detailed as those for PowerShell/Visual Studio.
  • Consider a summary table comparing PowerShell, Visual Studio, and SFCTL usage for upgrade parameters, making Linux/macOS parity clear.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as primary management tools and refers to Windows security as a transport option, suggesting a Windows-centric approach. PowerShell is listed first and exclusively in the management subsystem section, with no mention of Linux-native equivalents (such as Azure CLI or REST APIs). Windows security is mentioned alongside X509 certificates, but Linux security mechanisms are not referenced. No Linux/macOS-specific examples or tools are provided.
Recommendations
  • Add examples or references to Linux/macOS management tools, such as Azure CLI or REST API usage, alongside PowerShell.
  • Clarify that Service Fabric management can be performed from Linux/macOS using cross-platform tools.
  • Mention Linux security mechanisms (e.g., SSH, certificate-based auth) where relevant, not just Windows security.
  • Ensure that tooling and API references are platform-neutral or include both Windows and Linux/macOS options.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented as primary upgrade methods, with no mention of Linux/macOS alternatives (e.g., CLI or cross-platform editors). The serialization discussion is focused on C# and .NET, which are cross-platform, but the upgrade guidance leans toward Windows workflows.
Recommendations
  • Add examples or links for upgrading applications using Azure CLI or Service Fabric CLI, which are cross-platform.
  • Mention cross-platform editors (such as VS Code) alongside Visual Studio.
  • Clarify that PowerShell examples are available for Linux/macOS, or provide Bash/CLI equivalents.
  • Explicitly note if the upgrade process is identical across platforms, or highlight any differences.
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-22 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 demonstrates Windows bias through exclusive use of PowerShell examples, references to Windows-specific tools (e.g., http.sys, Windows HTTP Server API), and lack of Linux or cross-platform CLI examples. The upgrade process is illustrated only with Windows-centric commands and concepts, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell is used, provide alternative Bash or CLI commands for Linux users.
  • Clarify which steps or concepts are Windows-only (e.g., http.sys, Windows HTTP Server API) and provide Linux-specific guidance where possible.
  • Update 'Next steps' to include tutorials for Linux/macOS users, such as upgrading applications using sfctl or REST APIs.
  • Mention platform differences explicitly and link to Linux/macOS documentation where relevant.
GitHub Create Pull Request
← Previous Page 40 of 99 Next →