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 776-800 of 2475 flagged pages
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools Minor Windows Examples
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there is a noticeable Windows bias. PowerShell and Windows-specific tools are referenced more frequently and often appear before Linux equivalents. Some examples and links are Windows-centric, and certain explanations (such as port usage and DevOps tasks) focus on Windows/PowerShell scenarios. Linux is supported and mentioned, but parity in examples and tool references could be improved.
Recommendations
  • Ensure Linux CLI examples are provided alongside PowerShell examples, especially in sections referencing PowerShell APIs or tasks.
  • When referencing tools (e.g., 'netsh'), include Linux equivalents (e.g., 'ss', 'netstat', or 'lsof') for port range checks.
  • Balance the order of Windows and Linux guidanceβ€”avoid consistently listing Windows first.
  • Expand Linux-specific guidance for DevOps and operational tasks, not just mention ARM templates.
  • Where possible, clarify which features or steps are identical or different between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation page covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there are several signs of Windows bias: Windows terminology and tools (e.g., certificate store names like 'My', references to NTLM authentication, and links to Windows-specific documentation such as CertGetCertificateChain on MSDN) appear throughout. Windows-centric language and defaults (e.g., 'LocalMachine', 'MY', 'FindByThumbprint') are used in parameters, sometimes without clear Linux equivalents or guidance. While Linux is mentioned in some settings (e.g., ContainerNetworkSetup, LinuxExternalExecutablePath), Windows patterns are often presented first or exclusively, and references to Windows-only features (like Windows Update, NTLM, and log file settings) are not always clearly marked as platform-specific. There are also references to Windows-specific concepts (e.g., 'Windows Fabric Replicator', 'fabric.exe', 'ServiceFabricAdministrators' group) without Linux alternatives or parity notes.
Recommendations
  • For each parameter or feature that is Windows-specific, clearly mark it as such and provide Linux/macOS equivalents or guidance where possible.
  • When referencing certificate stores, clarify Linux equivalents (e.g., file system paths, openssl usage) and provide examples for both platforms.
  • Where Windows terminology (e.g., 'MY', 'LocalMachine', 'FindByThumbprint') is used, add Linux-specific instructions or mapping.
  • For authentication mechanisms (e.g., NTLM), explicitly state platform limitations and provide Linux alternatives if available.
  • When linking to external documentation (e.g., MSDN), provide Linux-relevant links or explanations.
  • Ensure that Linux/macOS settings and patterns are presented alongside Windows, not after or omitted.
  • Add explicit notes or tables indicating which settings are cross-platform and which are platform-specific.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, with some evidence of Windows bias. The JSON snippet uses a Windows-style file path (D:\\SvcFab) as the default example for the 'dataPath' property, and the 'Next steps' section links primarily to PowerShell scripts for Windows-specific tasks (changing RDP port range, admin username/password), without Linux equivalents or guidance. Windows terminology and tools (RDP, PowerShell) are mentioned first or exclusively, even though Service Fabric supports both Windows and Linux nodes.
Recommendations
  • Provide Linux-specific examples for 'dataPath' (e.g., /var/svcfab) alongside Windows paths.
  • Add links or instructions for performing cluster VM management tasks (such as changing SSH port/user/password) on Linux nodes, not just Windows (RDP/PowerShell).
  • Clarify which tasks are Windows-only and which are cross-platform, and offer Linux/macOS alternatives where possible.
  • Balance examples and guidance so that Linux users can easily follow and complete the same tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is presented as the only scripting option, and there is no mention of Linux-native tools or commands for managing Service Fabric auto scaling. The documentation does note that resource monitoring is supported for containerized applications on Linux, but practical Linux usage examples are missing.
Recommendations
  • Add Bash or Linux CLI examples for configuring scaling policies, using Service Fabric CLI (sfctl) or REST APIs.
  • Explicitly mention cross-platform tools and workflows for Linux/macOS users.
  • Clarify which PowerShell commands are available on PowerShell Core (cross-platform) vs. Windows PowerShell.
  • Provide guidance or links for Linux users to achieve the same tasks as shown in PowerShell examples.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users, as Service Fabric also supports Linux clusters. There is no guidance or parity for Linux users on how to perform these operations.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal), as Azure CLI is cross-platform.
  • If Service Fabric supports Bash scripts or REST API for these operations, provide those examples.
  • Explicitly mention any differences or limitations for Linux clusters, if applicable.
  • Include a note clarifying which tools are supported on Linux and how Linux users can achieve the same tasks.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying cluster health, but does not offer equivalent Linux/macOS CLI or REST API examples. This creates friction for non-Windows users, as Service Fabric supports cross-platform management but only Windows tooling is demonstrated.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API sample calls for health queries, as these are platform-agnostic.
  • Mention that PowerShell is one option, but highlight cross-platform alternatives for cluster management tasks.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json, Template.json) configurations. However, Windows-specific XML examples and PowerShell commands are presented first and more frequently, with no Linux shell or CLI equivalents. The use of WindowsServer in the XML example and PowerShell for service management may create friction for Linux users, though JSON-based configuration is also covered. No critical Linux functionality is missing, but parity in examples and tooling is lacking.
Recommendations
  • Add examples for Linux-based Service Fabric clusters, such as referencing Linux node configuration in ClusterManifest.xml or ClusterConfig.json.
  • Provide Azure CLI or REST API examples for service creation and updates, alongside PowerShell and C#.
  • Clarify that PowerShell commands are Windows-specific and suggest cross-platform alternatives where available.
  • Include explicit notes or sections for Linux/macOS users, highlighting any differences or limitations.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but only PowerShell is used for command-line/service creation examples. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform alternatives shown, and PowerShell is presented before any mention of Linux-compatible tooling. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and Azure CLI, but the documentation does not reflect this.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention and link to Linux-specific Service Fabric tools (e.g., sfctl) where relevant.
  • Clarify which PowerShell commands are available on Linux (PowerShell Core) and which are Windows-only.
  • Present cross-platform CLI examples (Azure CLI, sfctl) before or alongside PowerShell to improve parity.
  • Explicitly note any limitations or differences for Linux clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, with PowerShell (a Windows-centric tool) shown first and no Linux CLI or scripting examples (such as Azure CLI, Bash, or REST API). This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent Azure CLI or REST API examples for creating and updating services with MoveCost, as these are cross-platform.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script alternatives where possible.
  • Explicitly mention if certain operations are only possible via PowerShell or C# SDK, and provide guidance for Linux/macOS users.
  • Consider including a table or section summarizing which tools are supported on which platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The documentation also references PowerShell before C# APIs and omits mention of cross-platform tools or commands.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), and provide installation guidance if relevant.
  • Include Bash or shell script examples where possible, or clarify if certain operations are only possible via PowerShell or C# APIs.
  • Consider referencing cross-platform management tools before or alongside PowerShell to improve parity.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all CLI/API examples for dynamic operations use PowerShell cmdlets, which are Windows-centric. There are no examples using cross-platform tools (e.g., Azure CLI, REST API, or Linux-native scripting), nor is it clarified whether Linux users can perform equivalent operations. This creates friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using Azure CLI (if available), REST API, or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly state if certain operations (e.g., PowerShell cmdlets) are only available on Windows, and provide Linux/macOS alternatives or workarounds.
  • Include notes or links to cross-platform management documentation for Service Fabric.
  • If PowerShell Core (pwsh) is supported cross-platform for these cmdlets, clarify and provide usage guidance.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the patch orchestration application is described only for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting both Windows and Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add links and examples for Linux-specific upgrade and configuration procedures, such as 'service-fabric-cluster-upgrade-linux.md' and 'service-fabric-cluster-config-upgrade-linux.md' if available.
  • Clarify which features (like Patch Orchestration Application) are Windows-only, and provide Linux alternatives or explicitly state limitations.
  • Ensure that references to configuration files and procedures are applicable to both Windows and Linux, or provide separate guidance where they differ.
  • Where possible, provide cross-platform examples or note differences in commands/tools between Windows and Linux clusters.
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-27 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 noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several sections, and Windows terminology (such as Windows services and executables) is used without always providing Linux equivalents. Standalone cluster creation and upgrade instructions are Windows-only, with Linux standalone clusters explicitly unsupported. Some examples and tooling references (e.g., PowerShell cmdlets, Service Fabric Explorer) are Windows-centric, and Linux-specific workflows or examples are often missing or referenced second.
Recommendations
  • Where possible, provide Linux equivalents alongside Windows instructions, especially for cluster management, health monitoring, and lifecycle operations.
  • Mention cross-platform tools (e.g., CLI, REST APIs) before or alongside Windows tools like PowerShell.
  • Add explicit Linux examples for cluster creation, management, and application lifecycle, or clarify when features are Windows-only.
  • Highlight Linux support and parity in programming models and container orchestration.
  • Ensure that references to tooling (e.g., Service Fabric Explorer, Visual Studio) include alternatives for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and links to Windows Server-specific scaling guides. There are no examples or guidance for Linux-based standalone clusters, nor are Linux tools or commands mentioned.
Recommendations
  • Include examples and instructions for scaling standalone Service Fabric clusters on Linux, if supported.
  • Mention Linux equivalents for cluster manifest querying and configuration upgrades (e.g., using CLI, REST API, or other tools).
  • Add links to Linux-specific documentation or clarify if standalone clusters are Windows-only.
  • If Linux is not supported for standalone clusters, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently references Windows Server clusters and Windows security options, often providing links and examples for Windows scenarios but omitting equivalent Linux guidance. Certificate-based security is described as cross-platform, but explicit Linux instructions, links, or examples are missing. Windows authentication (Kerberos) is discussed, but Linux authentication approaches are not mentioned. The structure and links prioritize Windows clusters, with Linux clusters only briefly referenced.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate generation, installation, and cluster configuration (e.g., using OpenSSL, Linux file paths, and relevant tools).
  • Clarify which security features and recommendations apply equally to Linux clusters, and highlight any differences or limitations.
  • Include parity in 'Next steps' and reference Linux cluster creation and security documentation if available.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page provides general guidance on upgrading Azure Service Fabric clusters and mentions tools like PowerShell and Azure CLI for management tasks. However, it references Windows-specific upgrade procedures (such as Patch Orchestration Application and patching Windows OS images) and links to a Windows-focused patching guide without mentioning Linux equivalents or providing Linux-specific guidance. Examples and instructions for cluster management (certificates, ports, etc.) mention PowerShell/Azure CLI but do not clarify Linux support or provide Linux-specific examples. The Windows patching topic is discussed before any mention of Linux, and Linux cluster node patching is omitted.
Recommendations
  • Add explicit guidance or links for patching Linux-based Service Fabric clusters, if supported.
  • When referencing PowerShell/Azure CLI, clarify that Azure CLI is cross-platform and provide Linux/macOS command examples where relevant.
  • If Service Fabric supports Linux clusters, include instructions or links for Linux node OS upgrades and management tasks.
  • Ensure parity in examples and tool recommendations for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-27 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 code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, and Linux users are not given parity in operational guidance. The only Linux-specific mention is in the 'Choosing a platform' section, which describes implementation differences but does not provide actionable Linux usage examples.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for scaling operations (e.g., creating/removing services, updating instance counts).
  • Mention and link to Linux-compatible tools for Service Fabric management (such as sfctl or Azure CLI).
  • Ensure administrative instructions are not Windows/PowerShell exclusive; provide cross-platform guidance.
  • Where PowerShell is used, clarify if the operation can be performed with Linux tools and provide those examples.
  • Consider restructuring examples so Linux and Windows approaches are presented side-by-side or equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets (e.g., New-ServiceFabricService), with no equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or cross-platform tools). All operational instructions reference PowerShell modules, and there is no mention of Linux-native workflows or tools. This creates friction for non-Windows users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples for all service creation and management operations, as Azure CLI is cross-platform.
  • Explicitly mention if certain operations can only be performed with PowerShell, and provide alternative REST API or SDK examples where possible.
  • Include Bash or shell script examples where appropriate, or clarify the cross-platform compatibility of the Service Fabric tools.
  • Update the 'Next steps' section to reference Linux/macOS-compatible management guides, not just PowerShell.
  • Where PowerShell is referenced, add a note about cross-platform PowerShell Core support, if applicable.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric container application manifest examples exhibits Windows bias by referencing Windows Server 2016 Container Sample manifests as the basis for its examples, and by providing Windows-specific instructions (e.g., using 'winver' to get OS build version). There is no explicit mention of Linux container manifest samples, nor are Linux-specific instructions or examples provided. While some sections acknowledge Linux (e.g., certificate handling differences), the overall focus and examples are Windows-centric.
Recommendations
  • Add equivalent Linux container manifest examples or reference Linux container sample manifests.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside Windows instructions.
  • Clarify which features and manifest settings are supported on Linux clusters, and note any differences.
  • Provide links to Linux-specific Service Fabric container documentation or samples where available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows deployment and configuration paths (e.g., ApplicationManifest.xml, Visual Studio) are described in detail, while Linux-specific instructions are limited and often mentioned as secondary or with caveats. There are no Linux CLI (e.g., Bash, Azure CLI) examples for enabling or configuring DNS service, and Linux limitations are highlighted without offering workarounds or alternatives.
Recommendations
  • Add Linux-specific examples for configuring DNS service, such as using Azure CLI or Bash scripts.
  • Provide instructions for setting DNS names in Linux deployments (e.g., Docker Compose, YAML manifests) alongside PowerShell and ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service if portal access is unavailable, including step-by-step guidance for ARM templates or CLI.
  • Include parity in example ordering (Windows and Linux) and tools used.
  • Mention any Linux-specific tools or workflows for Service Fabric management where relevant.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-27 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 reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform clusters, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Provide REST API examples for health reporting and querying, as these are platform-agnostic.
  • Explicitly mention that PowerShell is one option and link to documentation for Linux/macOS users.
  • Ensure that all critical workflows are demonstrated for both Windows and Linux environments.
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-27 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 and retrieving the cluster manifest. It mentions Visual Studio (a Windows-centric tool) for publishing, and links to PowerShell-based deployment guides as the next step. While .NET and REST are briefly mentioned as alternatives, Windows tools and patterns are presented first and most prominently, with no explicit Linux/macOS command-line examples or tooling references.
Recommendations
  • Add examples and links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform .NET Core tools to retrieve the cluster manifest and deploy applications.
  • Include guidance for configuring and managing Service Fabric clusters from non-Windows environments.
  • Provide parity in 'Next steps' by linking to documentation for Linux/macOS workflows, not just PowerShell.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio where relevant.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page shows a moderate Windows bias. PowerShell and Visual Studio are mentioned first and in more detail when describing how to pass parameters during application creation. The PowerShell cmdlet is listed before the cross-platform sfctl tool, and Visual Studio (a Windows-centric IDE) is emphasized, including its integration with Azure DevOps and a PowerShell deployment script. Linux/macOS equivalents are mentioned (sfctl, Jenkins), but with less detail and after the Windows tools.
Recommendations
  • Present sfctl (the cross-platform CLI) before PowerShell, or give them equal prominence.
  • Provide example commands for both PowerShell and sfctl, with equivalent detail.
  • Mention cross-platform editors (e.g., VS Code) and deployment workflows, not just Visual Studio.
  • Expand on Jenkins or other non-Windows CI/CD options with concrete examples.
  • Clarify which tools are cross-platform and which are Windows-only.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples exhibits mild Windows bias. It references Windows-specific concepts (such as local admin accounts, NetworkService, and Setup.bat), and mentions the ServiceFabric PowerShell module as a way to create service instances, without providing Linux CLI equivalents or examples. Executable examples use Windows file extensions (.exe, .bat), and Windows account types are referenced before any Linux alternatives. No explicit Linux or cross-platform examples are provided.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of .bat files in SetupEntryPoint.
  • Mention Linux account types and how RunAsPolicy maps to Linux user/group management.
  • Provide Azure CLI or Service Fabric CLI (sfctl) examples for creating service instances, alongside PowerShell.
  • Clarify which features are cross-platform and which are Windows-only, especially for security principals and resource governance.
  • Where possible, show both Windows and Linux manifest snippets or highlight differences.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based deployment instructions and examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible commands. Windows-centric tools (PowerShell, RDP) are referenced exclusively and appear before any Linux alternatives. There are no Linux/macOS-specific instructions or parity examples for cluster deployment or management, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for template deployment, resource group creation, and querying resources.
  • Include Bash shell command equivalents where applicable, especially for pinging and accessing VMs.
  • Mention SSH as an alternative to RDP for accessing jump boxes or VMs in the virtual network.
  • Clarify that Service Fabric can be managed from Linux/macOS and provide links or examples for cross-platform tooling.
  • Consider reordering examples so that cross-platform methods (Azure CLI, SSH) are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
← Previous Page 32 of 99 Next →