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 101-125 of 2475 flagged pages
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on configuring Service Fabric application upgrades using Visual Studio and PowerShell, both of which are Windows-centric tools. All examples and instructions assume use of Visual Studio (Windows-only) and PowerShell (primarily Windows, though available on Linux with limitations). There is no mention of Linux/macOS workflows, CLI alternatives, or cross-platform tools for upgrading Service Fabric applications.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
- Clarify whether Service Fabric application upgrades can be performed from Linux/macOS environments and, if so, provide relevant guidance.
- If Visual Studio and PowerShell are required, explicitly state that these instructions are Windows-specific and link to any available cross-platform alternatives.
- Include a section or links for Linux/macOS users on how to perform equivalent upgrade operations.
Create Pull Request
Service Fabric
Azure Service Fabric reverse proxy
...articles/service-fabric/service-fabric-reverseproxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Service Fabric reverse proxy clearly states that the reverse proxy feature is not available for Linux clusters. All examples, configuration notes, and usage scenarios are written with Windows clusters in mind, and there are no Linux equivalents or workarounds provided. The page does not offer guidance for Linux users, nor does it clarify alternative approaches for Linux clusters.
Recommendations
- Add a prominent note at the top of the page clarifying that reverse proxy is Windows-only and suggest alternative communication patterns for Linux clusters.
- Provide links or references to Linux-compatible Service Fabric features or third-party solutions for service discovery and HTTP routing.
- If possible, update the documentation when Linux support for reverse proxy becomes available, or maintain a comparison table of feature parity between Windows and Linux clusters.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation and supported OS list indicate that standalone clusters are currently Windows-only. The security section references Windows-specific tools and patterns (Kerberos, Active Directory, group Managed Service Accounts) without Linux equivalents or guidance. No Linux examples, instructions, or supported OS are provided, and Windows terminology is used throughout.
Recommendations
- Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not available yet.
- Remove or update statements suggesting Linux parity unless Linux support is imminent.
- If/when Linux support is added, provide equivalent Linux security guidance (e.g., certificate management, authentication patterns) and Linux-specific examples.
- Explicitly state the lack of Linux support in the 'Supported operating systems' section to avoid confusion.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer and ARM-managed resources. It consistently recommends Az PowerShell cmdlets for operations (e.g., Remove-AzResource, AzSF PowerShell cmdlets) and references them before or instead of Azure CLI equivalents. While Azure CLI (az resource) is mentioned once for deleting applications, PowerShell is emphasized throughout, and Linux/macOS users may find the instructions less accessible or unclear, especially since PowerShell is not the default shell on those platforms.
Recommendations
- Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for operations like unprovisioning application type versions and creating services/applications.
- Clearly indicate when both PowerShell and Azure CLI can be used, and offer examples for each.
- Mention that PowerShell Core is cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Structure examples so that CLI and PowerShell are presented side-by-side, or at least alternate which is shown first.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides PowerShell examples for removing Service Fabric application resources and references PowerShell as a primary tool for deployment/removal, with no equivalent CLI or Linux/macOS instructions. PowerShell is mentioned before CLI in the introduction, and the 'Next steps' section lists PowerShell before CLI. There are no explicit Linux/macOS examples or guidance, creating friction for non-Windows users.
Recommendations
- Provide Azure CLI examples alongside PowerShell for resource removal and management tasks.
- Explicitly mention cross-platform tools (such as Azure CLI and Service Fabric CLI) in relevant sections, not just in 'Next steps'.
- Clarify which steps and tools are platform-agnostic and which are Windows-specific.
- Add notes or links for Linux/macOS users on how to perform equivalent operations.
- Ensure that CLI examples are given equal prominence to PowerShell throughout the documentation.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and workflows first and in greater detail, with Linux/CLI (sfctl) information appearing later and less prominently. Examples and parameter tables are heavily focused on PowerShell and Visual Studio, with minimal direct CLI/Linux guidance or examples. No explicit Linux command examples are provided in the main parameter sections, and Windows tools are mentioned before their Linux equivalents.
Recommendations
- Add explicit Linux/CLI (sfctl) command examples alongside PowerShell examples in parameter tables.
- Reorganize the documentation so that CLI/sfctl instructions are presented equally and not after Windows tools.
- Clarify which tools are cross-platform and which are Windows-only, to help Linux/macOS users navigate options.
- Include a summary table mapping parameters between PowerShell, Visual Studio, and sfctl for easy comparison.
- Consider providing a Linux/macOS workflow section or highlighting Linux-specific considerations.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples presented. While there is a brief mention of Linux custom image creation, the main content and examples focus on Windows, and the PowerShell command for role assignment is given without a Linux CLI equivalent.
Recommendations
- Provide equivalent Azure CLI examples for Linux/macOS users, especially for role assignments.
- Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and, if so, include relevant examples and guidance.
- Balance the order of Windows and Linux references (e.g., mention Linux custom image creation before or alongside Windows).
- Explicitly state any platform limitations (e.g., if only Windows images are supported for Service Fabric Managed Clusters, clarify this to avoid confusion).
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication' as the default for file share access. There are no explicit Linux or macOS file share examples, and Windows authentication is discussed before username/password alternatives. No PowerShell or Windows command-line examples are present, but the file share section is Windows-centric.
Recommendations
- Add examples for file share backup storage using SMB mounts on Linux (e.g., /mnt/backupstore or guidance for mounting CIFS shares).
- Clarify whether Linux clusters can use file share backup storage, and if so, provide instructions for configuring access from Linux nodes.
- Mention Linux authentication mechanisms (e.g., username/password, Kerberos, etc.) where relevant.
- Consider including a note about cross-platform compatibility for file share backup storage.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters and references both PowerShell and Azure CLI for management tasks. However, in the section 'Upgrading OS images for cluster nodes', the only linked guidance is for patching Windows operating systems, with no mention or link to Linux node patching. Additionally, the phrase 'Patch the Windows operating system in your Service Fabric cluster' is used without clarifying if Linux clusters are supported or providing equivalent Linux guidance. Examples and tool mentions (PowerShell/Azure CLI) are presented together, but Windows-specific patching is prioritized.
Recommendations
- Add explicit guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
- Clarify whether the patching guidance is Windows-only, and provide Linux parity or state Linux limitations.
- Ensure that examples and instructions for certificate management, port opening, and other cluster operations include both PowerShell and Azure CLI, with explicit Linux/macOS compatibility notes.
- Where possible, avoid phrases like 'Patch the Windows operating system' without mentioning Linux, or add a note about Linux support status.
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 →
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 examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. The C# API examples are cross-platform, but scripting and command-line guidance is Windows-biased.
Recommendations
- Add Azure CLI or Bash examples for managing node tags and service requirements, highlighting cross-platform usage.
- Include REST API example requests for tag management, as REST is platform-neutral.
- Clarify which PowerShell commands are available on Linux/macOS (if any), or note their Windows-specific nature.
- Consider reordering examples so that cross-platform methods (REST, CLI) are shown before or alongside PowerShell.
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux/macOS examples or links to equivalent Linux documentation, even though Service Fabric standalone clusters can be run on Linux. Windows terminology and guides are mentioned exclusively, creating friction for Linux users.
Recommendations
- Add links to Linux-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-linux.md', 'service-fabric-cluster-config-upgrade-linux.md') if available.
- Mention Linux support explicitly where applicable, and clarify which features/tools are Windows-only.
- Provide Linux/macOS examples or instructions alongside Windows ones, especially for cluster upgrades and configuration.
- Include information about patch orchestration or OS patching for Linux nodes if supported.
Service Fabric
Networking patterns for Azure Service Fabric
...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page for 'Networking patterns for Azure Service Fabric' exhibits a notable Windows bias. All deployment and management command-line examples use PowerShell (New-AzResourceGroup, New-AzResourceGroupDeployment, Get-AzPublicIpAddress), with no mention of Azure CLI, Bash, or cross-platform alternatives. File paths and command prompts are Windows-style (e.g., C:\SFSamples\...), and even network troubleshooting examples use Windows commands (ping from C:> prompt). There are no Linux/macOS-specific instructions or parity examples, which may create friction for users on those platforms.
Recommendations
- Provide Azure CLI equivalents for all PowerShell deployment commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash shell examples and Linux/macOS file path formats where relevant.
- When demonstrating network troubleshooting, offer Linux equivalents (e.g., ping 10.0.0.5 from a Bash prompt) alongside Windows commands.
- Clarify that PowerShell examples are for Windows users and direct Linux/macOS users to appropriate alternatives.
- Consider reordering or balancing examples so that Windows and Linux approaches are presented with equal prominence.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Azure Service Fabric application resource model exhibits several Windows biases. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. The packaging step references Visual Studio, a Windows-centric IDE, and does not mention alternatives for Linux/macOS. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
- Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
- Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
- Mention and link to cross-platform IDEs (e.g., VS Code) or command-line alternatives for application packaging.
- Clearly indicate which steps are Windows-only and provide Linux/macOS equivalents where possible.
- Consider reordering examples so that cross-platform options are presented first or equally.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or examples. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators seeking parity.
Recommendations
- Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
- Provide Linux-specific examples or clarify any differences in event collection and diagnostics configuration for Linux-based Service Fabric clusters.
- Mention cross-platform monitoring tools and how they can be used to access Service Fabric events regardless of OS.
- If certain features are Windows-only, explicitly state this to avoid confusion for Linux users.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDK usage. The focus on PowerShell and lack of Linux-specific guidance creates friction for non-Windows users.
Recommendations
- Add examples for using the Fault Analysis Service from Linux/macOS environments, such as Bash scripts, CLI commands, or REST API usage.
- Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) and how to install/use them on Linux/macOS.
- Clarify whether the Fault Analysis Service APIs and features are accessible from Linux-based development environments, and provide relevant guidance.
- If PowerShell is required, note that PowerShell Core is cross-platform and provide installation/use instructions for Linux/macOS.
Service Fabric
Introduction to the Service Fabric Infrastructure Service
.../articles/service-fabric/infrastructure-service-faq.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer without mentioning Linux/macOS alternatives or CLI equivalents. The example and tooling guidance assume Windows environments, creating friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI or REST API examples for bypassing Infrastructure Service.
- Mention cross-platform tools or interfaces (e.g., Service Fabric CLI, REST endpoints) alongside Service Fabric Explorer.
- Clarify whether the PowerShell command is required or if alternatives exist for Linux/macOS users.
- Provide guidance or links for Linux/macOS users to perform the same operations.
Service Fabric
Manage certificates in a Service Fabric cluster
...vice-fabric/cluster-security-certificate-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides extensive PowerShell-based examples and references to Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel), with no equivalent Linux/CLI/Bash examples or explicit mention of Linux-based certificate provisioning agents. The focus is on Windows-centric deployment and automation patterns, which may create friction for Linux users managing Service Fabric clusters.
Recommendations
- Add equivalent Azure CLI and/or Bash examples for certificate enrollment and management, especially for Key Vault operations.
- Document the availability (or lack thereof) of the Key Vault VM extension for Linux, and provide guidance for Linux-based provisioning agents if available.
- Clarify any platform-specific limitations or differences in certificate management for Service Fabric clusters running on Linux nodes.
- Where PowerShell is used, provide side-by-side Azure CLI or REST API equivalents.
- Explicitly state if certain features (like S-channel or certificate linking) are Windows-only, and suggest Linux alternatives or workarounds.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples 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 scripting examples. PowerShell is presented as the primary scripting option, which is Windows-centric. There is no explicit mention of Linux/macOS alternatives or cross-platform CLI tools, and PowerShell is referenced before any Linux-friendly tools in all relevant sections.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify if only Windows PowerShell is supported.
- Consider including Bash script snippets or references for ARM template deployment using az CLI.
- Where possible, note any limitations or differences for Linux/macOS users, especially if certain features are only available via PowerShell.
- Review and update section ordering so that cross-platform tools (Azure CLI, ARM templates) are presented before Windows-specific tools (PowerShell).
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides best practice examples and links primarily for Azure PowerShell, with PowerShell-based actions mentioned before Azure CLI or cross-platform alternatives. While Azure CLI and ARM templates are listed in a table, step-by-step examples and direct links in the best practices section focus on PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Add parallel Azure CLI examples and links for all PowerShell commands shown, especially for common tasks like deleting or restarting NodeTypes.
- In the best practices section, mention Azure CLI and ARM templates alongside PowerShell, not after.
- Where possible, provide code snippets or command references for both PowerShell and CLI in each example.
- Clarify that Azure CLI and ARM templates are fully supported and cross-platform.
Service Fabric
Migrate an Azure Service Fabric cluster to availability zone support
...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only PowerShell-based command-line examples for critical migration steps, with no equivalent CLI, Bash, or Linux-native instructions. This creates friction for Linux/macOS users managing Service Fabric clusters, especially since Service Fabric supports both Windows and Linux node types. The ARM template examples are OS-neutral, but all imperative migration steps are shown using Windows PowerShell cmdlets.
Recommendations
- Add equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource deployment, node disabling, and resource cleanup.
- Where possible, provide Bash script snippets or clear instructions for Linux/macOS users.
- Explicitly note if any steps are only possible via PowerShell, and suggest alternatives or workarounds for non-Windows users.
- Reference the Azure CLI documentation alongside PowerShell documentation for resource management tasks.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation covers Service Fabric application security in a generally platform-agnostic manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned without Linux equivalents or with Linux options listed second. Some example links and instructions (e.g., disk encryption, running services under accounts) are Windows-focused, and Linux guidance is sometimes missing or relegated to TODO comments.
Recommendations
- Provide explicit Linux examples and instructions alongside Windows ones, especially for disk encryption, service account configuration, and certificate management.
- Ensure Linux tools and patterns (e.g., Linux disk encryption, user/group management) are mentioned equally and not only as TODOs.
- Where Windows-specific features are discussed (e.g., gMSA, BitLocker), clarify Linux alternatives or limitations.
- Add links to Linux-focused documentation and examples where possible.
- Review example ordering so Linux and Windows are presented with equal prominence.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently uses PowerShell cmdlets (e.g., New-ServiceFabricService, Start-ServiceFabricApplicationUpgrade) for all command-line examples and workflows, with no mention of Linux/macOS equivalents such as Azure CLI, REST API, or Service Fabric CLI (sfctl). All concrete examples and guidance are PowerShell-centric, which may create friction for users managing Service Fabric clusters from Linux/macOS environments.
Recommendations
- Add equivalent examples using Azure CLI (az sf), Service Fabric CLI (sfctl), or REST API where possible, especially for common operations like service creation, upgrades, and parameter changes.
- Explicitly mention cross-platform tools and their usage alongside PowerShell, clarifying when certain operations are only possible via PowerShell.
- Where PowerShell is required, note its availability on Linux/macOS and provide installation guidance or alternatives.
- Include links to Linux/macOS-specific documentation or guides for Service Fabric management.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell cmdlets as the primary management interface for Service Fabric, and mentions Windows security as a transport option before X509 certificates. There are no explicit Linux or cross-platform management examples or tools mentioned, and PowerShell is presented as the default for provisioning and lifecycle management.
Recommendations
- Explicitly mention cross-platform management tools (such as Azure CLI, REST APIs, or Service Fabric CLI) alongside PowerShell.
- Clarify which management operations can be performed on Linux/macOS and provide corresponding examples.
- Add references to Linux-compatible authentication mechanisms (e.g., X509 certificates) before or alongside Windows security.
- Ensure that administrative APIs are described in a platform-neutral way, or provide links to Linux/macOS documentation.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there is a notable Windows bias. Windows-specific tools and patterns (e.g., EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, while Linux equivalents are referenced later or less prominently. Some examples and tutorials focus on Windows/.NET, and Linux-specific guidance is often limited to links or brief notes. Linux users may need to consult additional pages for full parity, and some features (like EventStore APIs) are Windows-only.
Recommendations
- Provide Linux-specific examples and step-by-step instructions alongside Windows examples, especially for cluster and infrastructure monitoring.
- Ensure Linux configuration guidance (e.g., Syslog integration, LTTng event channels) is as detailed and prominent as Windows guidance.
- Clarify which features are Windows-only and offer alternative approaches for Linux where possible.
- Add sample queries and alert rules relevant to Linux clusters and containers.
- Balance tutorial links and references so Linux users can easily find equivalent walkthroughs.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page on RunToCompletion semantics for Service Fabric presents examples and guidance exclusively for Windows containers, referencing Windows-specific container images and command syntax. PowerShell is the only CLI tool mentioned for querying deployment status, and Windows tools/patterns (e.g., cmd, Windows container images) are used throughout. There are no Linux container examples or equivalent Linux tooling references, despite Service Fabric supporting Linux containers.
Recommendations
- Add examples using Linux container images (e.g., Ubuntu or Alpine) and Linux shell commands.
- Include instructions for querying deployment status using Linux CLI tools (such as sfctl or REST API).
- Clarify in the introduction whether RunToCompletion semantics are supported on Linux, and provide parity guidance if so.
- Present Windows and Linux examples side-by-side, or at least mention Linux equivalents where applicable.