277
Pages Scanned
89
Pages Flagged
277
Changed Pages
32.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-03 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 277
Files Completed: 277
Problematic Pages
91 issues found
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 explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and configuration guidance are implicitly Windows-centric. There are no Linux-specific instructions, examples, or parity notes, and the guidance for containers and local clusters assumes Windows environments.
Recommendations
- Clearly state at the top that reverse proxy is Windows-only, and link to Linux alternatives or roadmap if available.
- Add guidance for Linux users about alternative approaches for service discovery and communication in Service Fabric clusters.
- If reverse proxy support for Linux is planned, provide a status update or expected timeline.
- For container scenarios, clarify that the instructions are Windows-specific and provide Linux container guidance if/when available.
Create Pull Request
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples are provided for Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST APIs, or cross-platform tools. The page assumes the user is on Windows, and does not mention or provide alternatives for Linux/macOS environments.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
- Mention and link to any Linux/macOS-compatible Service Fabric SDKs or management tools.
- Clarify early in the documentation if Visual Studio and PowerShell are required, and provide alternative guidance for non-Windows users if possible.
- Include sample upgrade commands for Linux shells (bash) and describe how Linux/macOS users can configure upgrade parameters.
- If certain features are Windows-only, explicitly state this to help set expectations for Linux/macOS users.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page frequently references PowerShell cmdlets and Windows-centric tools for managing the Service Fabric application lifecycle. While REST API and .NET methods are mentioned, PowerShell examples are consistently provided, and Linux equivalents (such as Azure CLI or sfctl commands) are missing or not highlighted. The page does not provide explicit Linux/macOS command examples, and Windows tools are often listed before REST or cross-platform options.
Recommendations
- Add Azure CLI and sfctl command examples alongside PowerShell cmdlets for all lifecycle operations.
- Clearly indicate which tools are cross-platform and which are Windows-only.
- Where PowerShell is referenced, provide equivalent Linux/macOS instructions or links.
- Reorder examples so that cross-platform tools (REST, CLI, sfctl) are listed before or alongside Windows tools.
- Include a section or note about managing Service Fabric applications from Linux/macOS environments.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides several PowerShell-based examples and instructions for scaling operations, particularly for disabling and removing nodes. These examples are given without Linux equivalents (such as Bash/CLI commands), and PowerShell is referenced as the primary/manual method for cluster operations. Additionally, Windows tooling and patterns (PowerShell cmdlets) are mentioned first and exclusively, creating friction for Linux users who may need to perform similar tasks using different tools.
Recommendations
- Add equivalent Linux/Bash/Azure CLI examples for node management operations (e.g., disabling/removing nodes).
- Explicitly mention cross-platform tools or provide links to Linux-specific guidance where PowerShell is referenced.
- Clarify whether PowerShell cmdlets are supported on Linux clusters, or provide alternative approaches for Linux environments.
- Reorder examples to show both Windows and Linux methods, or indicate parity where possible.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation for changing Azure Service Fabric cluster settings exhibits mild Windows bias. Windows-specific terminology (e.g., 'certificate store', 'NTLM', 'MY', 'LocalMachine'), references to Windows-only features (such as Windows Update), and default values that differ between Windows and Linux are present. Windows concepts (like certificate store names and NTLM authentication) are mentioned without clear Linux equivalents or guidance. Some settings (e.g., ContainerNetworkSetup) have different defaults for Windows and Linux, but Linux-specific guidance is minimal. There are no explicit Linux configuration examples or clarifications for Linux users, and Windows terminology is used throughout, sometimes without explanation for Linux users.
Recommendations
- Add explicit Linux configuration examples and clarify Linux-specific settings, especially where defaults differ (e.g., ContainerNetworkSetup, certificate store paths).
- Document Linux equivalents for Windows concepts such as certificate stores (e.g., explain how 'MY' maps to Linux certificate locations or how to configure certificates on Linux nodes).
- Where Windows-only features are mentioned (e.g., Windows Update, NTLM authentication), clearly indicate if/how they apply to Linux, or provide Linux alternatives.
- Review parameter descriptions to ensure Linux users can easily map Windows terminology to their environment (e.g., clarify certificate store names, file paths, and authentication mechanisms).
- Consider adding a section or table summarizing key differences between Windows and Linux Service Fabric clusters.
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 presents several security concepts for Azure Service Fabric applications, but exhibits mild Windows bias. Windows-specific features (such as running services under AD domain accounts or gMSA) are mentioned before Linux equivalents, and some examples (e.g., disk encryption) reference Windows tools (BitLocker, PowerShell) with Linux alternatives marked as TODO or missing. There are references to both Windows and Linux clusters, but Linux-specific guidance is less detailed or omitted in some sections.
Recommendations
- Add Linux-specific examples and instructions where currently missing, especially for disk encryption and service account management.
- Ensure parity in example ordering: mention Linux and Windows options together, or alternate which is presented first.
- Provide links to Linux documentation or tools (e.g., dm-crypt/LUKS for disk encryption, Linux user/group management for service accounts).
- Clarify when features are Windows-only and provide Linux alternatives or workarounds where possible.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides code examples primarily in C# and PowerShell, with PowerShell being a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, sfctl) provided. Additionally, administrative actions are described using PowerShell cmdlets before mentioning their programmatic equivalents, which may create friction for Linux users. However, the page does acknowledge platform differences in the 'Choosing a platform' section, and Service Fabric itself is cross-platform.
Recommendations
- Add Linux-specific command-line examples using sfctl or Bash scripts alongside PowerShell examples.
- Mention Linux tools and workflows (e.g., sfctl, REST API) when describing administrative actions.
- Ensure that examples and instructions are presented in a platform-neutral way or provide both Windows and Linux alternatives.
- Clarify when a tool or example is Windows-only and suggest Linux equivalents where possible.
Service Fabric
Azure Service Fabric hosting model
...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. Windows tools (PowerShell) are mentioned first and exclusively for command-line operations, creating friction for Linux/macOS users who must seek alternative methods. REST API and .NET client examples are included, but no Linux-native CLI or bash examples are provided.
Recommendations
- Add Azure CLI or Bash examples for creating and managing Service Fabric services, especially for operations shown in PowerShell.
- Explicitly mention cross-platform tools and workflows where possible, such as REST API usage from curl or other Linux-friendly tools.
- Clarify which operations can be performed from Linux/macOS and provide links or references to relevant documentation.
- Consider reordering examples so that cross-platform methods (REST, Azure 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
windows_tools
missing_linux_example
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It primarily references Windows Server-specific upgrade guides and tools, such as the Patch Orchestration Application for Windows, and links to documentation with 'windows-server' in the URL. There are no explicit Linux examples or references to Linux-based standalone clusters, and Linux upgrade/configuration paths are not discussed.
Recommendations
- Clarify early in the document whether standalone clusters are supported on Linux, and if not, state this explicitly to avoid confusion.
- If Linux-based standalone clusters are supported, provide equivalent upgrade and configuration instructions for Linux, including relevant examples and links.
- When referencing tools or applications (e.g., Patch Orchestration Application), mention if Linux alternatives exist or clarify their absence.
- Avoid using 'windows-server' URLs as the only upgrade/configuration references unless the feature is truly Windows-only; otherwise, provide Linux documentation links as well.
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 â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page primarily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI commands, or cross-platform SDK usage, nor are Linux-specific instructions or examples provided. The focus on PowerShell and Windows tooling creates friction for Linux/macOS users, especially since Service Fabric supports Linux clusters and cross-platform management.
Recommendations
- Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, where applicable.
- Clarify whether the PowerShell APIs are available or have equivalents on Linux/macOS, and provide guidance for those platforms.
- Mention FabricClient usage in a cross-platform context, including sample code or instructions for .NET Core or other SDKs.
- Explicitly state any limitations or differences for Linux clusters regarding replica soft delete.
- Ensure API documentation links include both PowerShell and REST/CLI/SDK alternatives.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but lacks equivalent Linux CLI or scripting examples. Windows deployment and configuration options (such as portal-based enabling and ApplicationManifest.xml usage) are described in detail, while Linux-specific limitations are mentioned but not accompanied by alternative instructions or examples. The order of presentation often favors Windows-first approaches, and Linux users may need to infer their own methods or workarounds.
Recommendations
- Add CLI or Bash examples for Linux users, such as using Azure CLI or REST API to set DNS names and enable DNS service.
- Clarify how Linux users can configure DNS service without the portal, with step-by-step instructions.
- Provide guidance for Linux clusters regarding ApplicationManifest.xml alternatives or container deployment methods.
- Explicitly state which PowerShell commands are Windows-only and offer Linux equivalents where possible.
- Include a summary table comparing Windows and Linux support/features, with links to Linux-specific documentation.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. Windows/PowerShell commands are shown before or alongside CLI, and some feature registration steps are only shown with PowerShell. Additionally, Resource Manager template deployment examples use PowerShell syntax, which is not cross-platform. There are no explicit Linux/macOS-specific instructions or parity for feature registration or template deployment.
Recommendations
- Add Bash/Linux/macOS equivalents for feature registration (e.g., using Azure CLI instead of PowerShell).
- Provide cross-platform instructions for deploying Resource Manager templates (e.g., using Azure CLI's 'az deployment group create' command).
- Ensure that any PowerShell-only steps are accompanied by CLI alternatives.
- Clarify that PowerShell steps can be run in Azure Cloud Shell (which supports Bash and PowerShell) to reduce friction for non-Windows users.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides a Windows-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd"â¯"sas-URI" --blob-type PageBlob') and does not offer an equivalent Linux/macOS command. The AzCopy invocation uses Windows paths and executable naming, and the Linux/macOS usage (with azcopy or ./azcopy and UNIX-style paths) is missing. While the rest of the CLI examples are cross-platform, the critical upload step is Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Mention that AzCopy is available for Linux/macOS and provide download/install links for those platforms.
- Clarify path conventions and executable naming for different OSes (AzCopy.exe vs azcopy or ./azcopy).
- Consider showing both Windows and Linux/macOS examples side-by-side for key steps.
Service Fabric
X.509 Certificate-based Authentication in a Service Fabric Cluster
...ticles/service-fabric/cluster-security-certificates.md
Medium Priority
View Details â
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 (e.g., certificate stores like LocalMachine\My), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are given either exclusively or before Linux equivalents. Linux paths and behaviors are mentioned briefly (e.g., /var/lib/sfcerts), but Windows concepts dominate, and Linux/macOS troubleshooting guidance is largely absent.
Recommendations
- Provide Linux/macOS equivalents for certificate store locations, certificate management, and troubleshooting steps (e.g., relevant log files, commands, and tools).
- Include examples and instructions for certificate validation and presentation rules on Linux, such as using OpenSSL or Linux-native certificate stores.
- Clarify which settings, APIs, and error codes are platform-specific, and offer cross-platform guidance where possible.
- Expand troubleshooting guidance to cover Linux/macOS scenarios, including how to diagnose certificate issues using Linux tools.
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation contains a warning that specifically references opening the Service Fabric XSD schema file in Visual Studio using a Windows file path (C:\Program Files\...), which is a Windows-only tool and path. There is no mention of equivalent tools or instructions for Linux/macOS users. Additionally, the only tooling guidance is Windows-centric and appears early in the article.
Recommendations
- Provide instructions or suggestions for Linux/macOS users on how to validate the Service Fabric manifest XML schema, such as using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools (e.g., xmllint, xmlstarlet).
- Mention the location of the schema file on Linux clusters, if applicable, or provide a download link.
- Avoid referencing only Windows file paths and tools; include cross-platform alternatives where possible.
- If Visual Studio is not available on Linux/macOS, recommend VS Code or other editors that support XSD validation.
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
Summary
The documentation page provides PowerShell examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. While the main deployment workflow is based on Azure Resource Manager templates (which are cross-platform), the only concrete command-line example is PowerShell, and PowerShell is mentioned before CLI alternatives. There is no explicit Linux CLI example (such as Azure CLI or Bash), and PowerShell is presented as the default scripting environment.
Recommendations
- Add Azure CLI examples for application removal and management alongside PowerShell, especially for tasks like deleting resources.
- Mention cross-platform tools (such as Azure CLI and Service Fabric CLI) equally or before PowerShell in relevant sections.
- Clarify that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide Bash/CLI equivalents.
- Where possible, link to documentation for both PowerShell and CLI workflows.
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (nanoserver), Windows paths, and Windows command syntax. There are no examples or guidance for Linux containers or Linux-based workloads, nor is there any mention of Linux compatibility or equivalent patterns.
Recommendations
- Add examples demonstrating Initializer CodePackages with Linux container images (e.g., Ubuntu, Alpine) and Linux command syntax.
- Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and sample manifests.
- Include notes or sections addressing any limitations or differences for Linux-based Service Fabric clusters.
- Present Windows and Linux examples side-by-side, or at least mention Linux support and provide links to relevant documentation.
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 page provides best practice examples primarily using Azure PowerShell, with PowerShell-based tools mentioned first and in detail. While Azure CLI and ARM/Bicep are listed, PowerShell is emphasized in guidance and linked examples. There is no explicit Linux/macOS example or mention of cross-platform command usage, and the CLI is not demonstrated in the main workflow.
Recommendations
- Add explicit Azure CLI examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging VMSS) alongside PowerShell examples.
- Mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Reorder tool recommendations to avoid always listing PowerShell first; alternate or group by platform neutrality.
- Clarify that all ARM-backed tools (including CLI and Bicep) are equally recommended for Linux/macOS users.
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 primarily references Az PowerShell cmdlets for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI commands in several sections. PowerShell examples are given first and exclusively in some cases, creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples alongside PowerShell cmdlets for all management operations, as Azure CLI is cross-platform.
- Clarify that Az PowerShell cmdlets can be used on Linux/macOS (if true), or provide guidance for Linux/macOS users.
- Ensure that ARM template usage instructions are platform-neutral and include links to relevant documentation for all OSes.
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
windows_first
missing_linux_example
Summary
The documentation provides extensive PowerShell-based migration steps for Service Fabric clusters, especially in the 'Basic SKU' migration scenario. All operational examples (disabling nodes, removing nodes, updating DNS) are given exclusively in PowerShell, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, the sample templates referenced for Standard SKU scenarios are Windows-based, and Windows paths (e.g., 'D:\\SvcFab') are used in configuration examples. Linux options are mentioned in passing (e.g., a sample template for Ubuntu), but no operational guidance or CLI examples are provided for Linux/macOS users.
Recommendations
- Add Azure CLI or Bash equivalents for all PowerShell migration steps, especially for node disablement, removal, and DNS updates.
- Provide explicit Linux/macOS instructions for connecting to Service Fabric clusters and managing nodes.
- Reference and link to Linux sample templates more prominently, and provide operational walkthroughs for those scenarios.
- Avoid using Windows paths in configuration examples unless they are required; if so, clarify Linux alternatives.
- Ensure that migration steps are platform-agnostic or provide parallel guidance for both Windows and Linux users.
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 generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several instances where Windows tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some sections (e.g., EventStore APIs) are Windows-only, but this is clearly stated. There are more detailed examples and links for Windows monitoring solutions, while Linux-specific guidance is often limited to a brief mention or a link. PowerShell is referenced for automation, but Linux CLI or Bash alternatives are not provided. The overall bias is moderate, as Linux users can complete most tasks, but may need to search for equivalent tools or instructions.
Recommendations
- Provide Linux-specific examples and step-by-step instructions alongside Windows ones, especially for cluster monitoring and log collection.
- Mention Linux tools (such as LTTng, Syslog) equally and provide links to relevant tutorials or documentation.
- When referencing automation via PowerShell, also mention Bash/CLI alternatives for Linux/macOS users.
- Ensure Linux configuration steps are as detailed as Windows ones, including troubleshooting and sample queries.
- Clarify which features are Windows-only and provide alternative solutions or workarounds for Linux clusters where possible.
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
windows_tools
missing_linux_example
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images (nanoserver), and assumes familiarity with Windows container workflows. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux/macOS equivalents or CLI tools. There are no examples or guidance for Linux containers or cross-platform scenarios, despite Service Fabric supporting Linux containers.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu-based images) to demonstrate RunToCompletion semantics for non-Windows environments.
- Include instructions for querying deployment status using cross-platform tools such as Azure CLI or REST APIs, not just PowerShell.
- Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide code samples and considerations for Linux users.
- Present examples for both Windows and Linux containers, or note any limitations if Linux support is partial.
- Avoid assuming Windows container familiarity; provide links or guidance for Linux container workflows where relevant.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is the only command-line interface shown for upgrade operations, and Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are referenced exclusively. There are no examples or guidance for Linux-based Service Fabric clusters or cross-platform CLI usage. Additionally, Windows tools and patterns are mentioned first or exclusively throughout the article.
Recommendations
- Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Where PowerShell cmdlets are shown, provide parallel sfctl commands or REST API examples.
- Clarify when a feature or limitation is Windows-only (e.g., http.sys certificate handling), and provide Linux-specific notes or alternatives where applicable.
- Include a section or callouts for Linux/macOS users, especially for common upgrade tasks.
- Update 'Next steps' to include Linux-compatible upgrade tutorials (e.g., using sfctl or REST API).
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but several sections show Windows bias. PowerShell and Windows-specific tools are referenced more prominently, and Windows examples or terminology often appear before Linux equivalents. Some explanations (e.g., Client API port usage) focus on PowerShell, and ARM template samples are Windows-centric. Linux examples are present but less emphasized.
Recommendations
- Where PowerShell is mentioned for cluster management or API access, add equivalent CLI or Bash examples for Linux users.
- Provide ARM template samples for Linux clusters alongside Windows samples.
- Clarify when guidance applies to both Windows and Linux, and avoid defaulting to Windows terminology (e.g., 'Client API used by PowerShell'âmention CLI or SDK usage as well).
- Ensure reverse proxy and container networking guidance includes Linux-specific considerations and examples.
- When referencing tools (e.g., 'netsh'), provide Linux equivalents (e.g., 'ss', 'netstat', or 'lsof').
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally presents Windows-specific tools and examples (such as PowerShell commands and Windows Defender) before or in greater detail than their Linux equivalents. In some sections, Windows-only features are described without Linux alternatives or with less detail for Linux users. For example, the encryption of secrets section provides detailed PowerShell commands for Windows, while Linux instructions are present but less emphasized. Windows Defender and security baselines are discussed without equivalent Linux security guidance. Some sections mention Windows tools or patterns without always providing Linux parity.
Recommendations
- Ensure that Linux examples are presented alongside Windows examples, ideally with equal prominence and detail.
- Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide Linux equivalents (e.g., bash/openssl for encryption, Linux security best practices, or common Linux antimalware solutions) or explicitly state if no equivalent exists.
- Avoid presenting Windows examples or tools first by default; alternate the order or present both together.
- Expand sections like 'Windows security baselines' and 'Windows Defender' to include Linux security hardening recommendations, such as CIS Linux benchmarks, common Linux antimalware tools, or links to relevant Azure Linux VM security documentation.
- In summary tables or lists, clearly indicate which guidance applies to Windows, Linux, or both.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or examples. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users, who would typically use Azure CLI or REST APIs. There is no guidance or parity for Linux users to accomplish the same tasks.
Recommendations
- Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Mention REST API endpoints or provide sample requests for relevant operations.
- Explicitly note if certain operations are only possible via PowerShell or C# and provide alternatives or workarounds for Linux/macOS users.
- Include a section clarifying tool support and platform compatibility for Service Fabric management.
Service Fabric
On-demand backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively uses PowerShell for all command-line examples and module instructions. There are no examples or instructions for Linux/macOS users, such as Bash, CLI, or cross-platform REST calls. The documentation assumes the use of Windows tools and patterns, creating friction for non-Windows users.
Recommendations
- Add Azure CLI or Bash examples for triggering backups and tracking progress, especially for REST API calls.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS, or provide alternatives.
- Include explicit instructions for Linux/macOS users on how to authenticate and connect to Service Fabric clusters (e.g., using certificates with curl or Azure CLI).
- Mention cross-platform tools or REST API usage outside of PowerShell, and provide sample requests using curl or HTTPie.
- Where possible, provide parity in examples so Linux/macOS users can follow the same workflow.
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 for configuring periodic backups in Azure Service Fabric is largely platform-neutral, focusing on REST API usage and JSON configuration. However, the 'File share' backup storage section exclusively references Windows-style UNC paths (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning or providing examples for Linux-compatible file share paths (such as SMB mounts on Linux) or authentication methods. Windows authentication is discussed first and exclusively, which may create friction for Linux users seeking parity.
Recommendations
- Add examples and guidance for configuring file share backup storage using Linux-compatible paths and authentication methods (e.g., SMB mounts, NFS, or Azure Files with Linux authentication).
- Clarify whether file share backup storage is supported on Linux clusters, and if so, provide relevant instructions.
- Mention alternatives for Linux users if Integrated Windows Authentication is not available, such as username/password or Azure Files with SAS tokens.
- Consider including a note about platform compatibility for each storage option.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric demonstrates notable Windows bias. All command-line examples use PowerShell, including module installation, cluster connection, and REST API calls. There are no equivalent examples for Linux/macOS users (e.g., Bash, curl, Azure CLI). The documentation references the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric, and does not mention cross-platform alternatives or clarify if REST API calls can be made from other environments. This creates friction for Linux/macOS users who may need to restore backups but lack guidance.
Recommendations
- Add Bash/curl examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made from any platform.
- Mention Azure CLI or other cross-platform tools if available for Service Fabric backup/restore operations.
- Explicitly state platform requirements for each tool or command, and provide alternatives where possible.
- Add a section for Linux/macOS users outlining the restore process and any limitations.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but when it comes to cluster upgrades, only PowerShell commands are shown, which are Windows-specific. Additionally, registry key and Windows Update settings are discussed without Linux equivalents or guidance. There are no Linux shell (bash) or cross-platform upgrade examples, and some configuration snippets are Windows-focused.
Recommendations
- Add Linux/bash equivalents for cluster upgrade operations, or clarify if these operations are only supported on Windows.
- When discussing disabling updates or configuring OS settings, provide Linux-specific instructions or explicitly state if not applicable.
- Balance PowerShell examples with bash/CLI examples where possible, especially for critical management tasks.
- Clearly indicate when a step or command is Windows-only, and provide links or guidance for Linux users.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All CLI examples are PowerShell-based, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or REST API). PowerShell examples are presented immediately after the C# code, and no cross-platform command-line guidance is given. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples for each placement policy configuration, where possible.
- Include REST API or ARM template snippets for configuring placement policies, to provide platform-neutral options.
- Explicitly mention whether PowerShell commands can be run on Linux/macOS (using PowerShell Core), or clarify if they are Windows-only.
- Provide guidance for Linux/macOS users on how to configure placement policies using available tools.
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 â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are exclusively in PowerShell, which is primarily a Windows tool. There are no equivalent Linux/macOS command-line examples (e.g., Bash, Azure CLI, or REST API). The documentation also presents PowerShell examples before mentioning any cross-platform alternatives, and does not clarify Linux support for these operations, despite Service Fabric supporting Linux containers.
Recommendations
- Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
- Clarify which operations and tools are supported on Linux clusters, especially for containerized workloads.
- Mention REST API options for configuring scaling policies, if available.
- Explicitly state any limitations or differences for Linux users in relevant sections.
- Consider reordering examples so that cross-platform methods (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
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 â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux shell (e.g., Bash/CLI) examples. PowerShell is Windows-centric, and the absence of Azure CLI or Bash examples creates friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for creating and updating Service Fabric services with MoveCost settings, if supported.
- If PowerShell is the only supported scripting interface, explicitly state this and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell or cross-platform PowerShell).
- Clarify any platform limitations for Service Fabric management tools.
- Consider including REST API examples, which are platform-agnostic.
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 â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is featured prominently, and there is no reference to cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add examples using Azure CLI or REST API for configuring service sensitivity and maximum load, if supported.
- Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core), or provide guidance for Linux/macOS users.
- If certain operations are only possible via PowerShell, explicitly state this limitation and suggest alternatives or workarounds.
- Consider including Bash or shell script examples if relevant APIs are available.
- Document any GUI or portal-based configuration options for users on non-Windows platforms.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first and more frequently. PowerShell is the only CLI example shown for service creation and updates, with no Linux CLI or Bash equivalents. The XML configuration is labeled as 'WindowsServer', and while JSON examples are given for standalone (cross-platform) deployments, there is no explicit mention of Linux-specific tools or patterns. The bias is mostly in the ordering and CLI example selection.
Recommendations
- Add Bash/CLI examples for service creation and updates (e.g., using sfctl or Azure CLI) alongside PowerShell.
- Clarify that ClusterManifest.xml is for Windows clusters, and highlight Linux configuration patterns (e.g., use of ClusterConfig.json for Linux).
- Present JSON (cross-platform) configuration examples before or alongside Windows XML examples.
- Mention Linux node types and any relevant differences in cluster setup.
- Provide links or references to Linux-specific Service Fabric documentation where appropriate.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health information, but does not include equivalent examples for Linux or cross-platform environments. The only command-line example is Windows/PowerShell-specific, and there is no mention of Linux tools or Service Fabric CLI (sfctl), which is the recommended cross-platform tool.
Recommendations
- Add equivalent Linux/cross-platform examples using the Service Fabric CLI (sfctl), e.g., show how to retrieve partition health with sfctl partition health.
- Explicitly mention that the PowerShell example is for Windows and provide guidance for Linux/macOS users.
- Where possible, prefer cross-platform tools in documentation examples or present both Windows and Linux options side by side.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details â
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 exclusively uses PowerShell for CLI examples. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API examples), and PowerShell is presented before any mention of cross-platform tools. This creates friction for Linux/macOS users, as Service Fabric can be managed from non-Windows environments using Azure CLI or REST APIs, but these options are not shown.
Recommendations
- Add Azure CLI examples for creating and managing Service Fabric services and metrics, as Azure CLI is cross-platform.
- Include REST API examples for metric management, which are usable from any OS.
- Clarify which PowerShell commands are available cross-platform (PowerShell Core) and which are Windows-only.
- Present CLI examples in a more OS-neutral way, e.g., show Azure CLI first or alongside PowerShell.
- Explicitly mention Linux/macOS management options in the relevant sections.
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 provides detailed PowerShell examples for managing node tags and service tag requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for non-Windows users. The C# API examples are platform-neutral, but command-line guidance is Windows-centric.
Recommendations
- Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
- Include REST API usage examples for tag operations, highlighting cross-platform compatibility.
- Clarify whether PowerShell commands are available on Linux/macOS (via PowerShell Core), or provide alternative instructions if not.
- Explicitly mention any limitations or differences for Linux/macOS clusters, if applicable.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for adding/removing nodes. There are no Linux-specific examples, tools, or instructions provided, despite Service Fabric standalone clusters being theoretically deployable on non-Windows environments.
Recommendations
- Include Linux-specific instructions and examples for scaling standalone clusters, such as using CLI tools or scripts compatible with Linux.
- Document equivalent Linux commands or REST API approaches for querying and updating cluster manifests and configurations.
- Clarify whether standalone Service Fabric clusters are supported on Linux, and if so, provide parity in guidance and tooling.
- If Windows-only tools are required, explicitly state this limitation and provide guidance for Linux users where possible.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page discusses securing Azure Service Fabric clusters, covering both Azure-hosted and standalone Windows clusters. However, it repeatedly provides detailed guidance and links for Windows Server standalone clusters, while omitting equivalent instructions or links for Linux standalone clusters. Windows security options (Kerberos, Windows accounts) are described, but Linux-specific security patterns (such as Linux user accounts, certificate management, or integration with Linux authentication mechanisms) are not mentioned. The structure and examples consistently prioritize Windows, with Linux clusters only briefly referenced.
Recommendations
- Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
- Include Linux-specific examples for certificate creation, installation, and management (e.g., using OpenSSL, Linux file paths, and permissions).
- Clarify whether Linux standalone clusters support Windows security (Kerberos) or if only certificate-based security is available.
- Provide parity in recommendations and best practices for Linux environments, such as using Linux CA tools or integrating with Linux authentication systems.
- Ensure that references to 'standalone clusters' consistently specify whether instructions apply to Windows, Linux, or both.
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
missing_linux_example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, sections such as 'Upgrading OS images for cluster nodes' and references to Patch Orchestration Application (POA) specifically mention Windows and link only to Windows patching documentation. Additionally, examples for managing certificates and opening application ports mention PowerShell/Azure CLI but do not clarify Linux/macOS parity or provide explicit Linux/macOS examples. Windows terminology (NTLM, FileStoreService) is referenced without Linux equivalents or clarifications.
Recommendations
- Add explicit Linux/macOS examples alongside PowerShell/Azure CLI instructions, or clarify that Azure CLI commands are cross-platform.
- Include links or guidance for patching Linux-based Service Fabric clusters, if supported.
- Clarify when features or instructions are Windows-specific and provide Linux alternatives or note limitations.
- Ensure documentation for certificate management, port opening, and node property configuration includes cross-platform tooling and examples.
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 the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Linux/macOS workflows. Application packaging instructions rely on Visual Studio, a Windows-centric tool, and do not provide alternative methods for Linux/macOS users. The sample application is .NET-based, but the packaging and deployment steps are presented in a Windows-first manner.
Recommendations
- Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
- Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
- Mention alternative editors or IDEs for Linux/macOS (e.g., VS Code) and how to package applications without Visual Studio.
- Clearly indicate when steps are Windows-only and offer Linux/macOS alternatives where possible.
- Consider including sample scripts or workflows for Linux/macOS environments.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation covers Azure Service Fabric concepts for both Windows and Linux, but there is a notable Windows bias. Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., Windows service, FabricHost.exe) is used throughout. Examples and links for creating clusters and standalone clusters are Windows-first or Windows-only, with Linux standalone clusters explicitly unsupported. PowerShell is referenced as a primary management tool, with CLI and REST APIs mentioned but not emphasized. Linux parity is acknowledged, but Linux-specific instructions and examples are sparse or missing.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and health monitoring.
- Mention Linux tools (e.g., Bash, Linux CLI usage) before or equally with Windows tools like PowerShell.
- Clarify which features are Windows-only and which are cross-platform, and provide links to Linux documentation where available.
- Add explicit guidance for Linux users in sections about application lifecycle, monitoring, and diagnostics.
- Include Linux-focused quickstarts and tutorials in the 'Next steps' section.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples are provided as an alternative, but there is no explicit mention of Linux/macOS compatibility or guidance for non-Windows users. There are no Linux-specific examples or notes about using sfctl on Linux/macOS, and PowerShell is a Windows-centric tool (though available cross-platform, it is less commonly used on Linux).
Recommendations
- Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
- Provide example commands for Linux/macOS environments (e.g., using Bash or zsh).
- Mention installation instructions for sfctl on Linux/macOS.
- Consider listing CLI examples before PowerShell, or at least equally, to avoid Windows-first impression.
- Add notes about PowerShell Core availability on Linux/macOS if relevant.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details â
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 is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
- Include REST API examples for health reporting and querying, which are platform-agnostic.
- Mention that PowerShell examples are specific to Windows and provide links or instructions for Linux/macOS alternatives.
- Ensure that all critical tasks demonstrated with PowerShell are also shown with cross-platform tools.
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 for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. Windows tools and patterns are referenced first and exclusively.
Recommendations
- Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, or Azure Monitor integration for Linux).
- Mention Linux-native monitoring tools or patterns where applicable, such as using Log Analytics agents for Linux or integrating with Linux-based log collectors.
- Clarify which features or instructions are Windows-only and provide Linux equivalents or note limitations for Linux clusters.
- Provide example commands or configuration snippets for both Windows and Linux environments.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path, mentions Visual Studio as a packaging tool without listing Linux alternatives, and does not provide Linux/macOS-specific guidance or examples. There are no explicit PowerShell examples, but Windows tools and patterns are mentioned first and exclusively. No Linux packaging tools or directory paths are shown, and the sample directory structure uses a Windows executable (.exe) as the example.
Recommendations
- Add Linux/macOS-specific instructions for packaging and deploying guest executables, including example directory paths and file extensions.
- Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) alongside Visual Studio, and clarify which steps are possible on Linux/macOS.
- Provide sample manifests and directory structures using non-Windows binaries (e.g., .sh, .out) and note any platform-specific requirements.
- Reference the location of schema files for Service Fabric SDK on Linux/macOS, if available.
- Explicitly state if Visual Studio is required or if alternatives exist for Linux/macOS users.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the main 'Next steps'. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI, Bash, or cross-platform scripts), and no mention of Linux-specific workflows or tools, despite Service Fabric supporting Linux clusters.
Recommendations
- Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying applications, highlighting cross-platform workflows.
- Include links to Linux/macOS documentation or guides for Service Fabric cluster management.
- Present .NET, REST, and cross-platform options alongside PowerShell, rather than PowerShell-first.
- Clarify that PowerShell examples are applicable on Linux/macOS via PowerShell Core, if relevant, or provide alternative commands.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides Service Fabric container application manifest examples that are based on a Windows Server 2016 container sample. Windows-specific tools and patterns (such as 'winver' and Windows path formats) are referenced before or instead of Linux equivalents. There is little to no mention of Linux-specific guidance or parity in the manifest examples or explanations, despite Service Fabric supporting Linux containers.
Recommendations
- Provide equivalent manifest examples or notes for Linux-based Service Fabric clusters and containers.
- When referencing OS-specific commands (e.g., 'winver'), also mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r').
- Clarify when features or settings are Windows-only, and highlight any differences or limitations for Linux clusters.
- Use platform-neutral path formats or provide both Windows and Linux path examples where relevant (e.g., for volume mounts).
- Explicitly state whether the manifest examples are portable to Linux clusters, and if not, provide Linux-specific samples.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. The only command-line deployment example is given in PowerShell, and the use of Windows file paths and certificate store names (e.g., 'C:\Program Files\...', 'MY' store) is prevalent. While there is a brief note about the Linux certificate store location, Linux-specific deployment commands or examples are missing. Windows tools and patterns are referenced first and more thoroughly.
Recommendations
- Provide equivalent Linux CLI examples (e.g., using Azure CLI or sfctl) alongside PowerShell commands for deploying applications with ApplicationParameters.
- Clarify how to specify certificate stores and paths for Linux clusters, including more explicit examples.
- When referencing file paths or tools, include both Windows and Linux equivalents where applicable.
- Consider reordering or parallelizing examples so that Linux and Windows usage are presented with equal prominence.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows, which are Windows-centric. While sfctl (a cross-platform CLI) is mentioned, Windows tools and patterns (PowerShell, Visual Studio, Deploy-FabricApplication.ps1) are listed first and described in more detail, with less explicit guidance for Linux/macOS users.
Recommendations
- Provide Linux/macOS-specific examples and workflows, such as using sfctl and install.sh, with step-by-step instructions.
- Ensure parity in documentation by describing how to use parameter files and scripts on Linux/macOS, not just in Visual Studio or PowerShell.
- List cross-platform tools (sfctl, install.sh) before Windows-specific tools to avoid implicit prioritization.
- Clarify which scripts or tools are available and supported on Linux/macOS, and provide links to relevant documentation.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash/CLI). PowerShell is presented as the primary scripting interface, and Windows-style paths/prompts are used. REST and API options are mentioned, but practical Linux-oriented command-line examples are missing.
Recommendations
- Add Azure CLI or Bash script examples for health reporting and cluster connection, demonstrating parity with PowerShell.
- Explicitly mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) and provide usage instructions for Linux/macOS.
- Clarify which PowerShell commands are available via cross-platform PowerShell Core, and note any Windows-only limitations.
- Reorder or balance examples so that REST/CLI approaches are shown before or alongside PowerShell, to avoid Windows-first impression.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific build and deployment actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI elements. There are no examples or guidance for Linux/macOS users, nor mention of cross-platform tooling or alternatives to Visual Studio. The only alternative deployment methods referenced are ARM templates and PowerShell cmdlets, but these are not explained in detail or shown with Linux-compatible tools.
Recommendations
- Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
- Provide examples using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) for deployment and configuration.
- Clarify which features are Visual Studio/Windows-only and suggest Linux/macOS alternatives where possible.
- Include sample workflows for editing and deploying StartupServices.xml on Linux/macOS environments.
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 usage instructions for the Fault Analysis Service in Service Fabric, mentioning C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST API) are provided. There is no mention of Linux-compatible tools or patterns, nor guidance for Linux/macOS users on how to use the Fault Analysis Service.
Recommendations
- Add examples for using the Fault Analysis Service via Azure CLI, REST API, or Bash scripts, if available.
- Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
- If PowerShell Core (cross-platform) is supported, mention it explicitly and provide relevant examples.
- Include information about any limitations or prerequisites for Linux/macOS users.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page introduces benchmarking tools for both Windows (DiskSpd) and Linux (FIO), but Windows tools and patterns are mentioned first and more prominently. The examples and setup instructions reference Windows terminology (e.g., host caching, volume names) without providing equivalent Linux commands or examples. There is no explicit Linux example or guidance, creating friction for Linux users.
Recommendations
- Provide explicit Linux examples alongside Windows examples, including FIO command lines and Linux-specific setup instructions.
- Ensure Linux tools (FIO) are mentioned equally and not after Windows tools.
- Clarify any differences in disk configuration steps for Linux VMs (e.g., how to stripe disks and configure caching in Linux).
- Add sample scripts or command lines for Linux users to replicate the benchmarking process.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell code samples. There are no Linux VM image examples or explicit instructions for Linux VMs, despite the article stating applicability to both Linux and Windows VMs. Additionally, the 'Quickstart' link in the portal section references creating a Windows VM, and Windows terminology is used by default in several places.
Recommendations
- Add Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in all CLI and PowerShell code blocks.
- Explicitly mention that the steps are identical for Linux VMs, or highlight any differences (such as disk partitioning/formatting commands) for Linux.
- Provide a 'Quickstart: Create a Linux virtual machine in the Azure portal' link alongside the Windows quickstart.
- Ensure variable names and instructions are OS-neutral (e.g., avoid using only Windows usernames/passwords).
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux coverage, but Windows examples and tools (WSFC, CSV, Windows clustering templates) are presented first and in greater detail. Windows-specific clustering patterns and terminology (WSFC, CSV) are described before Linux equivalents, and Windows workloads are listed before Linux workloads. Linux examples are present but less detailed, and Linux-specific utilities (sg_persist, fence_scsi) are mentioned only briefly. The performance throttling examples also start with Windows scenarios before Linux.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
- Expand Linux workload examples to match the detail and variety of Windows workloads.
- Provide more detailed Linux-specific guidance, including step-by-step examples for Pacemaker, Corosync, and clustered filesystems.
- Include Linux-specific templates or links, similar to the Windows SoFS and SAP templates.
- Ensure Linux tools/utilities (sg_persist, fence_scsi) are described with usage examples, not just mentioned.
- Balance performance throttling examples so Linux scenarios are as prominent as Windows scenarios.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are primarily Windows-centric. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and gives installation instructions using cmd.exe and PowerShell. While Azure CLI examples are included (which are cross-platform), PowerShell is presented first and in greater detail. There are no explicit Linux shell (bash) or macOS-specific instructions for REST API tooling, and the reliance on Chocolatey for 'armclient' excludes Linux/macOS users from easy installation.
Recommendations
- Add bash/Linux/macOS installation instructions for 'armclient' or recommend cross-platform alternatives (such as using curl or az CLI for REST calls).
- Provide parity in scripting examples for Linux users, such as using bash scripts or az CLI for all scenarios shown in PowerShell.
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Clarify that 'armclient' can be installed via .NET Core or provide a Docker image for Linux/macOS users if Chocolatey is not available.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements as a limitation for shared disks across all disk types. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any guidance or limitations for Linux-based shared disk scenarios. Additionally, proximity placement group documentation is linked to a Windows-specific page, even though PPGs are not exclusive to Windows VMs.
Recommendations
- Add information about shared disk limitations and supported clustering solutions for Linux (e.g., Pacemaker, Corosync, or other Linux HA stacks).
- Include links to Linux clustering documentation and clarify whether shared disks are supported with Linux-based clusters.
- Update proximity placement group links to reference both Windows and Linux VM documentation, or use a generic PPG page.
- Explicitly state if certain limitations only apply to Windows Server Failover Cluster, and provide Linux equivalents or note their absence.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented first and in greater detail, with multiple code blocks and screenshots, while Azure CLI examples (more natural for Linux users) are shown after. There is no explicit mention of Linux-native tools for interacting with Azure resources (e.g., Python SDK, REST API), and the PowerShell section may create friction for Linux users unfamiliar with PowerShell on Linux.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is more commonly used on Linux.
- Add a brief note clarifying that PowerShell commands can be run on Linux, but Azure CLI is the default for Linux environments.
- Expand Azure CLI examples to match the detail and coverage of the PowerShell section.
- Consider including REST API or Python SDK examples for advanced Linux users.
- Explicitly mention that all PowerShell commands can be run on Linux, but CLI is recommended for Linux users.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides parity for both Linux and Windows VM image creation with Azure Image Builder, including Bicep and ARM template examples. However, there are several areas where Windows-specific tools (PowerShell, WindowsRestart, WindowsUpdate customizers) and instructions are emphasized, sometimes before Linux equivalents. SHA256 checksum generation is shown with PowerShell first, and Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are less prominent. Some sections (e.g., restart customizer) note the absence of Linux equivalents. PowerShell commands and tools are referenced more frequently, and sometimes before Linux/CLI alternatives.
Recommendations
- Ensure Linux and macOS examples (e.g., shell commands, checksum generation) are shown alongside or before Windows/PowerShell examples.
- Provide more detailed Linux customizer examples, including advanced shell scripting and error handling.
- Where Windows-only customizers exist (e.g., WindowsRestart), clarify Linux alternatives or explicitly state limitations.
- Balance the order of examples so Linux and Windows are treated equally, or alternate which is shown first.
- Reference Linux tools (e.g., sha256sum, wget, curl) equally with Windows tools (PowerShell, Invoke-WebRequest).
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
While the documentation is focused on Linux VMs, it frequently uses PowerShell cmdlets (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) for examples and instructions, which are Windows-centric tools. PowerShell examples are provided in detail and often before or in greater depth than Azure CLI examples. REST API and ARM template examples also use Windows-style script syntax (e.g., Write-Host, .ps1 files) without Linux/bash equivalents. Some explanations reference Windows-specific behaviors (such as 'Secondary Logon' service), and there are missing Linux/bash script examples in several sections.
Recommendations
- Provide equivalent bash/Linux shell script examples for REST API and ARM template sections (e.g., use 'echo' or bash scripts instead of 'Write-Host' or .ps1).
- Expand Azure CLI examples to match the depth and breadth of PowerShell examples, including advanced scenarios like parameter passing, output streaming, and sequential execution.
- Clarify that PowerShell cmdlets can be used cross-platform, but also highlight native Linux tools (bash, sh) and Azure CLI as primary options for Linux users.
- Ensure that script examples and explanations use Linux conventions (e.g., .sh files, bash syntax) where appropriate, especially in sections about Linux VMs.
- Move Azure CLI examples before PowerShell examples to prioritize Linux-native tooling.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides general information about Azure Service Fabric node types and VM scale sets, with some references to both Windows and Linux nodes. However, the JSON snippet example uses a Windows-style file path (D:\\SvcFab) for the dataPath property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-centric tasks. There are no explicit Linux/macOS examples or guidance for equivalent SSH access or Linux file paths, creating a mild Windows bias.
Recommendations
- Provide Linux/macOS examples alongside Windows examples, such as using '/var/svcfab' for dataPath.
- Add guidance or links for SSH access to Linux nodes, not just RDP/PowerShell for Windows.
- Clarify which tasks are Windows-only and offer Linux alternatives where possible.
- Include sample ARM template snippets for both 'ServiceFabricNode' (Windows) and 'ServiceFabricLinuxNode' (Linux) with relevant property values.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias toward Windows in some sections: Windows container runtimes are listed in greater detail, Windows scenarios (such as IIS lift-and-shift) are described first, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned. Linux is covered, but Windows examples and tools are sometimes presented before Linux equivalents.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid 'Windows first' bias.
- Expand Linux-specific scenarios (e.g., Apache, NGINX, Python apps) alongside Windows/IIS examples.
- Mention Linux container runtimes (e.g., containerd, Podman) if relevant, not just Docker.
- Ensure that quickstart/tutorial links for Linux and Windows are equally prominent and described.
- Clarify when features or scenarios are Windows-only to avoid confusion.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows operating system support for application consistency before Linux, but otherwise provides parity in listing both Windows and Linux support. No Windows-only tools, examples, or patterns are given, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell documentation equally, without favoring Windows tools.
Recommendations
- Consider listing Linux operating system support before Windows, or presenting both in a single table or section to avoid 'Windows first' bias.
- Ensure that linked 'CLI' and 'PowerShell' guides provide Linux and macOS examples where applicable.
Virtual Machine Scale Sets
Networking for Azure Virtual Machine Scale Sets
...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) show PowerShell commands first or exclusively. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
- Ensure CLI examples are always presented alongside PowerShell, and consider showing CLI examples first to avoid implicit Windows-first bias.
- Where possible, add Bash shell examples for common Linux workflows, especially for querying resources.
- Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Review all sections to ensure no critical task is only documented with PowerShell.
Virtual Machine Scale Sets
Orchestration modes for Virtual Machine Scale Sets in Azure
...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides orchestration mode concepts for Azure Virtual Machine Scale Sets and is intended to be platform-neutral, supporting both Linux and Windows VMs. However, there are subtle signs of Windows bias: the only explicit command-line example uses Azure CLI but does not show Linux shell syntax (e.g., bash), and the mention of Azure Site Recovery is qualified as 'via PowerShell' without mentioning Linux alternatives or parity. Additionally, the documentation sometimes refers to Windows and Linux together, but Windows is often mentioned first or more prominently.
Recommendations
- Provide explicit Linux shell (bash) examples alongside Azure CLI and PowerShell examples, especially for critical operations.
- Clarify Azure Site Recovery support for Linux VMs and document any Linux-specific steps or limitations.
- Ensure parity in mentioning both Windows and Linux in feature tables and descriptions, avoiding Windows-first ordering unless justified.
- Where extensions or tooling are referenced (e.g., Application Health Extension), note any Linux-specific considerations or installation steps.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for configuring disk restrictions, but references to PowerShell and Windows-centric links appear before Linux equivalents. The custom RBAC role section links to a PowerShell-focused guide, and the Network access policy section mentions PowerShell alongside CLI, but the PowerShell link is listed first. There are no Linux-specific command examples or explicit parity in example ordering.
Recommendations
- Ensure that CLI (Linux/macOS-friendly) examples and links are presented before or alongside PowerShell/Windows examples.
- Add explicit Linux/macOS command examples where possible, especially for custom RBAC role creation and disk configuration.
- Link to general (platform-neutral) documentation for custom roles, not just PowerShell guides.
- Clarify that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page mentions Windows base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in container image cleanup, but does not mention Linux base images or provide examples relevant to Linux containers. The examples and explanations focus on Windows images first, and there is no explicit guidance for Linux container scenarios.
Recommendations
- Add examples and explanations for Linux base images (e.g., 'mcr.microsoft.com/linux', 'docker.io/library/ubuntu') in the 'ContainerImagesToSkip' setting.
- Clarify whether the cleanup process applies equally to Linux containers and Windows containers, and provide Linux-specific guidance if needed.
- Include sample configurations or notes for clusters running Linux containers, ensuring parity in documentation.
- Explicitly mention that the feature is cross-platform (if applicable), or clarify any platform limitations.
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
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page for Service Fabric Reliable Services app manifest examples exhibits mild Windows bias. Windows concepts (such as 'NetworkService', 'Administrators', '.bat' files, and EXE executables) are referenced throughout, and Windows terminology is used for user accounts and groups. The only script example is a Windows batch file (Setup.bat), and EXE executables are assumed. There is a mention of using the ServiceFabric PowerShell module to create service instances, with no Linux CLI equivalent. However, the manifest XML itself is cross-platform, and no critical steps are Windows-only.
Recommendations
- Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) in SetupEntryPoint.
- Mention Linux user/group equivalents or clarify how Service Fabric handles principals on Linux nodes.
- Provide CLI examples for Linux (e.g., Azure CLI or Service Fabric CLI) alongside PowerShell references.
- Clarify that EXE/NetworkService/Administrators are Windows-specific and provide Linux alternatives where applicable.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
Although the page introduction claims Service Fabric clusters run on both Windows Server and Linux, the content and supported operating systems section clarify that Linux is not yet supported for standalone clusters. All examples, security options, and OS lists are Windows-centric, with no Linux-specific guidance or parity.
Recommendations
- Clarify at the top that standalone clusters are currently Windows-only, despite the initial mention of Linux.
- Remove or revise the description to avoid implying Linux support where none exists.
- Add a roadmap or link to Linux support documentation if/when available.
- Ensure that future updates include Linux-specific instructions, examples, and security guidance when Linux support is added.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is generally platform-neutral, but there are subtle signs of Windows bias. Windows-specific terminology (such as referencing 'auto-start Windows service, FabricHost.exe') is used in the definition of nodes, and Windows executables (EXE/DLL) are mentioned as typical code packages. Windows containers are mentioned before Linux containers in some sections. However, Linux support is acknowledged, and most concepts are described in a generic way.
Recommendations
- Clarify that 'FabricHost.exe' and related Windows services have Linux equivalents, or explicitly state how node management differs on Linux clusters.
- When mentioning code packages, note that Linux executables (such as ELF binaries or scripts) are equally supported.
- In sections discussing containers, mention Linux containers first or equally, and clarify that Docker containers are supported on Linux and Windows.
- Where Windows-specific terminology is used, add a note or parenthetical to explain the Linux equivalent or behavior.
- Consider adding explicit Linux examples or references where Windows tools or patterns are mentioned.
Virtual Machine Scale Sets
Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview)
...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and in some sections, PowerShell examples reference Windows-specific extension names (e.g., ApplicationHealthWindows). In the PowerShell example for adding the Application Health extension, only the Windows extension is shown, while the CLI example uses the Linux extension. The ordering of tabs sometimes puts PowerShell before CLI, and the PowerShell section assumes familiarity with Windows tooling. There are no explicit Linux/macOS gaps, but the documentation could be clearer about cross-platform parity and extension types.
Recommendations
- Clarify in PowerShell examples how to use Application Health extensions for both Windows and Linux VMSS (e.g., show ApplicationHealthLinux as well as ApplicationHealthWindows).
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users, and consider listing CLI before PowerShell in tab order.
- Add a note explaining that PowerShell is available cross-platform, but Windows users may be more familiar with it.
- Where extension types differ (ApplicationHealthWindows vs ApplicationHealthLinux), provide both examples or guidance for each OS.
- Ensure all screenshots and portal steps are OS-agnostic or clarify if any are Windows-specific.
Virtual Machine Scale Sets
Spot Placement Score
...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides example usage for Azure portal, REST API, Azure CLI, and Azure PowerShell. While all major cross-platform interfaces are covered, the PowerShell example is presented last, and there is no evidence of exclusive Windows/PowerShell bias or omission of Linux equivalents. Azure CLI (cross-platform) is included, and REST API instructions are platform-neutral. The order of examples (CLI before PowerShell) slightly favors Linux parity, but the portal instructions are inherently platform-agnostic. No Windows-specific tools or patterns are mentioned, and no critical steps are Windows-only.
Recommendations
- Maintain parity by ensuring Azure CLI and REST API examples are kept up-to-date alongside PowerShell.
- Explicitly note that Azure CLI and REST API are fully supported on Linux/macOS.
- Consider adding sample scripts for Linux shell environments (bash) to demonstrate REST API usage, if relevant.
- Continue to avoid Windows-specific terminology or tools unless the feature is Windows-only.
Virtual Machine Scale Sets
Attach or detach a virtual machine to or from a Virtual Machine Scale Set
...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move), but consistently presents PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may signal Windows bias, especially since Linux users typically use Bash/CLI. Additionally, PowerShell examples are shown immediately after CLI, rather than being separated or clearly marked as Windows-only. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), and no critical steps are Windows-only.
Recommendations
- Clearly label PowerShell examples as 'Windows only' or 'for Windows users', and Azure CLI examples as 'for Linux/macOS users'.
- Consider providing Bash script examples where appropriate, or clarify that Azure CLI is cross-platform and preferred for Linux/macOS.
- If possible, reorder examples so Azure CLI is shown before PowerShell, or group PowerShell examples in a separate section for Windows users.
- Add a note explaining that Azure PowerShell is primarily for Windows environments, while Azure CLI is cross-platform.
Virtual Machine Scale Sets
Automatic OS image upgrades with Azure Virtual Machine Scale Sets
...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and configuration methods for automatic OS image upgrades in Azure Virtual Machine Scale Sets. However, there is a mild Windows bias in some areas: Windows-specific properties are mentioned first in requirements, PowerShell examples (which are Windows-centric) are presented before Azure CLI (cross-platform) examples, and ARM template snippets default to Windows images. There are no missing Linux examples, and Linux support is clearly documented, but Windows patterns and tools are sometimes prioritized.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- In ARM template and Bicep snippets, provide both Windows and Linux image examples, or use a Linux image as the default.
- Where Windows-specific properties are discussed (e.g., enableAutomaticUpdates), clarify Linux equivalents or explicitly state when they are not applicable.
- Ensure all sections referencing tools or commands include Linux-friendly options or clarify platform neutrality.
Virtual Machine Scale Sets
Configure rolling upgrades on Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and sometimes after CLI. There are no Linux-specific examples (e.g., Bash scripting), but Azure CLI is cross-platform and is shown first in most cases. The PowerShell sections are prominent, but do not prevent Linux/macOS users from completing any task, as all operations can be performed via Azure CLI or ARM templates.
Recommendations
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform option.
- Consider adding Bash shell scripting examples for common automation scenarios, or clarifying that Azure CLI commands can be used in Bash scripts.
- If PowerShell is shown, clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but CLI is generally preferred for Linux/macOS users.
- Ensure that CLI examples are always shown before PowerShell, and that the documentation does not imply PowerShell is required.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics in rolling upgrades on Virtual Machine Scale Sets. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell scripts and Azure PowerShell cmdlets are given equal prominence to Bash and Azure CLI, but Windows tools and patterns (e.g., PowerShell HTTP server, Windows extension type) are sometimes mentioned first or exclusively in certain code blocks. REST API examples also default to Windows extension types. Overall, Linux parity is present but not always prioritized.
Recommendations
- Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples in all code tabs and sections.
- Use ApplicationHealthLinux as the default extension type in generic sample code and REST API payloads, or provide both Linux and Windows variants.
- Clarify in each section that both Linux and Windows are supported, and highlight any differences explicitly.
- Add troubleshooting steps and sample output for both Linux and Windows, not just Windows.
- Review REST API and PowerShell sample payloads to ensure Linux examples are included and not overshadowed by Windows defaults.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is generally cross-platform, explicitly stating applicability to both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before their Linux equivalents. For example, application-consistent backup coordination is described first with Windows tools, and only later is fsfreeze for Linux mentioned, with less detail. SQL Server (Windows) backup scenarios are described in more depth than Oracle or other Linux-based databases. The comparison table also highlights Windows-specific benefits before Linux equivalents.
Recommendations
- Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze and mention other Linux application-consistent backup solutions).
- When discussing database backup scenarios, include examples for Linux-based databases (e.g., Oracle, PostgreSQL) with links to relevant documentation.
- Ensure that Linux tools and patterns are mentioned alongside Windows tools, not after or as an afterthought.
- Where possible, add Linux-specific example commands or workflows for backup and disaster recovery.
- Review the comparison table and scenario descriptions to ensure Linux parity in benefits and operational considerations.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally cross-platform and neutral, but there is a minor instance of Windows bias: in the section about B-Series VMs for development and test environments, the guidance 'Use at least B2 for Windows machines' is given, while no equivalent recommendation is made for Linux machines. Additionally, Windows and Linux pricing links are presented together, but Windows is listed first. No PowerShell-heavy examples, Windows-only tools, or missing Linux examples are present.
Recommendations
- Provide equivalent guidance for Linux VM sizing if relevant (e.g., 'Use at least B2 for Linux machines' or clarify if Linux has different requirements).
- Ensure that recommendations for VM types, disk choices, and automation tools are explicitly applicable to both Windows and Linux, or clarify differences.
- Alternate the order of Windows and Linux links or present them together to avoid subtle Windows-first bias.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally provides parity between Windows and Linux, with clear references to both Azure PowerShell and Azure CLI for enabling encryption features. However, there is a mild 'windows_first' bias: PowerShell/Windows links and instructions are often listed before their Linux/CLI counterparts. Additionally, some references (such as to PowerShell for revoking access) appear before CLI, and the automatic key rotation walkthrough links only to a PowerShell-based guide, with no direct Linux/CLI equivalent linked in that section.
Recommendations
- Alternate the order of PowerShell and CLI/portal links throughout the documentation, or list CLI first in some sections to balance the presentation.
- Where a step-by-step guide is linked for PowerShell (e.g., automatic key rotation), ensure a corresponding CLI/Linux guide is linked alongside it if available.
- In sections referencing both PowerShell and CLI (such as revoking access), present both options together or in parallel, rather than PowerShell first.
- Consider adding explicit Linux/macOS/CLI code snippets or walkthroughs in sections that currently only link to Windows/PowerShell guides.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are often presented before CLI, and references to PowerShell are slightly more prominent. However, Linux parity is generally maintained, with CLI instructions and Linux-specific links included in 'Next steps'.
Recommendations
- Ensure Azure CLI examples are presented alongside or before PowerShell examples, especially in sections relevant to cross-platform users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, to reinforce cross-platform applicability.
- Add Bash or shell script examples where appropriate, especially for disk operations, to further assist Linux users.
- Review tab ordering and section headings to avoid subtle Windows-first presentation.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is primarily a changelog/news summary for Azure Disk Storage features and enhancements. While most content is platform-neutral, there are a few instances where Windows-specific links or references are listed before Linux equivalents, and some links point to Windows-specific documentation (e.g., 'expand-disks' and 'find-unattached-disks'). However, Linux parity is generally maintained, and most features are applicable to both Windows and Linux workloads.
Recommendations
- Ensure that links to both Windows and Linux documentation are provided wherever relevant, and avoid listing Windows links first unless the feature is Windows-only.
- Where features are cross-platform, provide examples or links for both Windows and Linux usage.
- Review linked documentation to confirm Linux parity and update summaries to mention Linux support when applicable.
- Consider adding a brief note clarifying platform applicability for each feature, especially when linking to platform-specific guides.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear applicability to both. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement and Windows image sizing) are mentioned before Linux equivalents, and PowerShell is listed before CLI in the section on customer managed keys. Linux examples and tools are present but sometimes appear after Windows ones.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
- When listing tooling (e.g., PowerShell, CLI), alternate the order or group them together as 'PowerShell/CLI/SDK' without preference.
- Add explicit Linux image sizing examples alongside Windows ones in all relevant sections.
- Where possible, provide Linux-specific operational details (e.g., swap file placement) in parity with Windows-specific notes.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are consistently presented immediately after CLI, and sometimes with more detail. There is minor 'windows_first' bias in referencing PowerShell alongside CLI as a primary management tool, despite the Linux focus. However, all examples, screenshots, and guidance are tailored for Linux VMs, and Linux-specific tools (like waagent) are highlighted. No critical Linux gaps are present.
Recommendations
- Consider presenting Azure CLI examples before PowerShell in all sections, as CLI is more universal across platforms.
- Explicitly note that Azure PowerShell can be run on Linux/macOS, but CLI is often preferred for Linux workflows.
- Where possible, provide Bash shell script examples for common tasks (e.g., checking agent logs, troubleshooting) alongside CLI.
- Review for any subtle language implying PowerShell is the default or preferred tool for Linux VM management, and clarify parity.
- Add links or notes about using Azure CLI and PowerShell on Linux/macOS, including installation instructions.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples for deploying the extension, and PowerShell is mentioned before Azure CLI in some sections. This may create minor friction for Linux users, as PowerShell is not a native Linux tool, though Azure CLI and ARM template examples are also present. There is a brief mention of a Windows extension, but it is appropriately separated and not the focus of the page.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clearly indicate that PowerShell examples are primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider adding Bash script examples for common operations, as Bash is native to Linux.
- Ensure troubleshooting sections prioritize Azure CLI and Bash commands over PowerShell.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is focused on Linux, but in several sections, Windows-oriented tools (PowerShell) are presented first or in greater detail than Linux-native alternatives. Azure PowerShell deployment instructions and troubleshooting are shown before Azure CLI, even though CLI is more cross-platform and native to Linux. Some PowerShell-specific warnings and examples are included, but Linux-specific shell or scripting guidance is minimal.
Recommendations
- Present Azure CLI examples and troubleshooting before PowerShell, as CLI is more native to Linux.
- Add Linux shell (bash) scripting examples for deploying the extension, especially for automation scenarios.
- Clarify that PowerShell instructions are optional for Linux users and highlight CLI as the preferred method.
- Include troubleshooting steps using Linux-native tools (journalctl, systemctl, etc.) for extension status.
- Ensure all JSON and deployment examples use Linux file path conventions and avoid Windows-specific syntax (e.g., backslashes).
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before CLI equivalents. Resource Manager template instructions also reference PowerShell and CLI, but PowerShell is sometimes prioritized. However, Azure CLI (cross-platform) is well-represented, and Linux-specific context is clear throughout.
Recommendations
- Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform and native to Linux.
- Where possible, clarify that PowerShell can be used on Linux/macOS (via Azure Cloud Shell or local installation), to reduce perceived Windows bias.
- Expand Linux-native tooling references (e.g., bash, shell scripting) where relevant, especially for disk management or backup operations.
- Avoid referencing PowerShell-specific parameters or behaviors before CLI equivalents unless necessary.
- Consider adding a brief note at the start of each section explaining that both CLI and PowerShell are supported on Linux, but CLI is often preferred for Linux users.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers preparing and uploading a Red Hat Enterprise Linux VHD for Azure, with detailed instructions for multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While Linux-centric throughout, the structure and ordering of sections consistently present Hyper-V (a Windows technology) instructions first for each RHEL version, followed by KVM, VMware, and Kickstart. This ordering may subtly signal Windows/Hyper-V as the default or preferred environment, despite full Linux support and parity in examples.
Recommendations
- Reorder hypervisor sections so that Linux-native options (KVM, Kickstart) appear before Hyper-V, or present all options in a neutral order (alphabetical or by popularity).
- Explicitly state that all hypervisor options are equally supported, and that users can choose based on their environment.
- Add a short introductory note clarifying that Hyper-V is not required, and that Linux-native workflows are fully supported.
- Consider grouping instructions by workflow (e.g., 'Linux-native', 'Windows/Hyper-V', 'VMware') to avoid implicit prioritization.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. No PowerShell or Windows tool examples are given for Linux configuration, but a PowerShell command is shown for base64 encoding cloud-init (which is relevant for Azure users on any OS). All configuration guidance, tools, and examples are Linux-centric.
Recommendations
- Move or minimize the Windows Server 2016 discussion in the introduction, focusing first on Linux-specific mechanisms and their interaction with Azure infrastructure.
- Clarify that the PowerShell example for base64 encoding is for Azure users on Windows, and provide a Linux equivalent (e.g., 'base64 cloud-config.txt') for parity.
- Ensure that Linux guidance and examples are always presented before or alongside any Windows infrastructure references, unless Windows context is essential for understanding Azure's host time source.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_reference
Summary
The documentation is generally balanced and covers both Linux and Windows VM scenarios. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first (e.g., MBR/GPT partitioning), Windows-specific tools are referenced (e.g., Azure PowerShell), and some explanations use Windows-centric language (drive letters, Sysprep, etc.) before mentioning Linux equivalents. Linux examples and terminology are present, but occasionally appear after Windows references.
Recommendations
- Ensure Linux and Windows examples/tools are presented together or Linux-first where appropriate.
- When referencing partitioning (MBR/GPT), include links to Linux documentation or mention Linux partitioning tools.
- Where drive letters are discussed, clarify Linux device paths alongside Windows terminology.
- For upload instructions, ensure both Azure CLI (Linux) and PowerShell (Windows) links are equally prominent.
- When mentioning cluster managers, list Linux options (e.g., Pacemaker) before or alongside Windows options (e.g., WSFC).