247
Pages Scanned
49
Pages Flagged
247
Changed Pages
19.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-02-25 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 247
Files Completed: 247
Problematic Pages
50 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK components. All setup instructions, examples, and prerequisites are Windows-centric, with no mention of Linux/macOS alternatives or cross-platform signing methods. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, only Windows/PowerShell workflows are detailed. Linux/macOS users are left without guidance for equivalent signing tasks.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including supported signing tools and workflows.
- Clarify whether Artifact Signing supports cross-platform signing and, if so, provide guidance for non-Windows environments.
- Include sample commands for Linux (e.g., using OpenSSL, GPG, or other relevant tools if supported).
- Document any limitations or platform requirements for each integration, so users know which are Windows-only.
- For GitHub Actions and Azure DevOps, show how to use these integrations from Linux runners if possible.
Create Pull Request
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tooling references are for Visual Studio (Windows), with no mention of cross-platform alternatives like Visual Studio Code or CLI-based workflows. PowerShell and Package Manager Console commands are used exclusively, and there are no Linux/macOS-specific instructions or examples for publishing, database management, or log streaming. This creates friction for Linux/macOS users who cannot follow the steps as written.
Recommendations
- Add instructions for using Visual Studio Code and the .NET CLI for project creation, publishing, and database management.
- Provide examples for publishing ASP.NET apps to Azure App Service using the Azure CLI or GitHub Actions, which are cross-platform.
- Include SQL database management steps using Azure CLI or az sql commands instead of only Visual Studio/PowerShell.
- Offer guidance for streaming logs using Azure CLI or portal, not just Visual Studio.
- Clearly indicate which steps are Windows-only and provide Linux/macOS alternatives where possible.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tooling. All examples use PowerShell cmdlets, and certificate creation relies on Windows-only PowerShell modules (New-SelfSignedCertificate, Export-PfxCertificate). There are no Bash, Azure CLI, or Linux/macOS-compatible instructions provided, making it difficult for non-Windows users to follow the tutorial without significant adaptation.
Recommendations
- Provide equivalent Azure CLI examples for all steps, including resource creation, configuration, and cleanup.
- For certificate creation, include cross-platform alternatives (e.g., using OpenSSL for Linux/macOS) alongside PowerShell instructions.
- Clearly indicate which steps are Windows-only and offer Linux/macOS-compatible alternatives where possible.
- Add a note at the beginning clarifying that PowerShell is not required and that Azure CLI or Bash can be used for most tasks.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All migration scripts, examples, and instructions are provided exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS shell equivalents. Script installation, usage, and certificate handling are described only in PowerShell terms. There is no guidance for Linux/macOS users, and the documentation assumes a Windows-centric workflow throughout.
Recommendations
- Provide Azure CLI equivalents for all migration steps, including script installation, parameter usage, and certificate management.
- Add Bash shell examples for Linux/macOS users, especially for certificate handling and script execution.
- Clarify if the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide explicit instructions for Bash users.
- Mention cross-platform compatibility of the scripts, or provide alternative tools if PowerShell is required.
- Include a section addressing Linux/macOS users, outlining any prerequisites or limitations and offering guidance for their environments.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and neutral, but the 'Hybrid Connections' section introduces Windows bias by requiring the Hybrid Connection Manager to be installed only on Windows Server 2012 or newer. There are no Linux/macOS equivalents or instructions provided, and no mention of alternative approaches for non-Windows environments. This creates friction for Linux/macOS users wishing to use Hybrid Connections.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if possible.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative connectivity solutions for Linux/macOS users.
- Where possible, provide Linux/macOS examples or parity for any tooling or configuration steps.
- Review other sections for implicit Windows bias (e.g., screenshots, CLI instructions) and ensure cross-platform guidance is provided.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently uses Windows-based SQL Server VM examples and references SQL Server Management Studio (SSMS), a Windows-only tool, for client connectivity. No Linux or macOS alternatives (such as SQL Server on Linux, Azure SQL Edge, or cross-platform SQL clients like sqlcmd or Azure Data Studio) are mentioned. The instructions for creating the SQL Server VM default to Windows Server, and client connection steps assume a Windows environment.
Recommendations
- Include instructions for deploying SQL Server on Linux (supported on Azure VMs) or mention Azure SQL Edge for cross-platform scenarios.
- Provide examples of connecting to the SQL Server backend using cross-platform tools such as sqlcmd (available on Linux/macOS), Azure Data Studio, or other open-source SQL clients.
- Clarify that the Application Gateway TCP/TLS proxy feature works for SQL Server workloads on both Windows and Linux, if applicable.
- Add screenshots or command-line examples for Linux/macOS users where relevant.
- Mention any limitations or differences for Linux-based SQL Server deployments if they exist.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily focused on Windows PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-specific modules. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The use of Windows PowerShell terminology and tools is pervasive, and Linux alternatives are not mentioned.
Recommendations
- Add equivalent Azure CLI examples for credential asset creation and authentication, which work cross-platform.
- Clarify that Azure Automation runbooks can be authored in Python and provide a Python example for managing Azure resources.
- Mention that PowerShell Core (pwsh) is available on Linux/macOS and indicate whether the provided scripts are compatible with PowerShell Core.
- Include guidance for Linux/macOS users on how to install required modules and authenticate to Azure from their platforms.
- Reorder sections to present cross-platform options (Azure CLI, Python) before Windows PowerShell-specific instructions.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and examples, with all scripting and automation instructions provided in PowerShell. There are no Linux shell (bash) or cross-platform CLI examples for certificate management, and PowerShell is presented first and most thoroughly. The Python section is present, but only for runbook scripting, not for certificate management tasks like creation or upload. There is no mention of Linux tools or Azure CLI equivalents for certificate operations.
Recommendations
- Add Azure CLI examples for certificate creation, upload, and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include bash shell scripting examples for certificate manipulation where relevant.
- Clarify whether PowerShell Core (pwsh) is supported for these operations, and provide guidance for non-Windows environments.
- Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
- Consider referencing third-party tools or scripts for certificate handling on Linux/macOS.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for backup and restore operations, but the PowerShell (Windows-centric) examples are presented first and in greater detail. The PowerShell section includes variable setup and multiple managed identity scenarios, while the CLI section is less detailed and lacks managed identity examples. There are no Linux-specific tools or patterns mentioned, but Azure CLI (cross-platform) is included. REST API usage is also documented, which is platform-neutral.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Expand Azure CLI examples to include managed identity scenarios, matching the detail provided in PowerShell sections.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and provide any relevant Linux/macOS-specific notes or troubleshooting tips.
- Consider adding a note clarifying that PowerShell Core is available cross-platform, but Azure PowerShell usage is most common on Windows.
- Ensure parity in example depth and coverage between PowerShell and CLI sections.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides step-by-step examples for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively uses Azure PowerShell for CLI-based examples and does not mention or provide equivalent Azure CLI (az) commands, which are cross-platform and preferred by many Linux/macOS users. PowerShell is presented before ARM templates, and there are no Linux/macOS-specific instructions or references to Azure CLI, resulting in friction for non-Windows users.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all tasks, such as creating API Management instances with managed identities, updating instances, and assigning user/system identities.
- Explicitly mention that Azure CLI is supported and provide links to relevant Azure CLI documentation.
- Consider presenting Azure CLI and PowerShell examples in parallel, or at least alternate their order to avoid Windows-first bias.
- Clarify that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page prioritizes Windows examples and tools, especially in the 'Load certificates in Windows apps' section, where only Windows certificate store access is shown in detail for C# and Java. Linux-specific guidance is limited to file-based certificate loading, with no code samples for non-C# languages (Node.js, PHP, Python, Java) on Linux. Windows certificate store and related tools are discussed before Linux equivalents, and Linux guidance is often deferred to external documentation.
Recommendations
- Add explicit Linux code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from files in Azure App Service Linux environments.
- Provide Linux-focused guidance earlier in the document, or in parallel with Windows instructions, to avoid Windows-first ordering.
- Include examples of using Linux tools (such as OpenSSL or relevant libraries) for certificate management and loading.
- Clarify when Windows-specific instructions are not applicable to Linux, and provide Linux alternatives where possible.
- Expand the 'Load a certificate from a file' section to include Linux-specific nuances and security best practices.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Azure Portal and Azure CLI instructions, which are cross-platform. However, there are several subtle Windows biases: (1) Windows directory paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as primary examples, with Linux equivalents only mentioned in passing; (2) The use of Kudu DebugConsole and FTP references Windows-style paths and tools; (3) The 'Automate with scripts' section mentions Azure PowerShell alongside Azure CLI, but does not provide Bash or Linux shell script samples or parity; (4) Windows terminology and patterns (e.g., slot names, directory structure) are presented first or exclusively in some sections.
Recommendations
- Provide Linux-specific examples and directory paths (e.g., /home/site/wwwroot) alongside Windows paths wherever file operations are discussed.
- Explicitly mention Linux/macOS methods for uploading files (e.g., SCP, SFTP, Linux FTP clients) in addition to Windows FTP.
- Add Bash or Linux shell script samples in the 'Automate with scripts' section to complement Azure PowerShell.
- When referencing environment variables or paths, show both Windows (%HOME%) and Linux ($HOME) conventions.
- Clarify cross-platform compatibility of tools like Kudu DebugConsole and ensure screenshots/examples reflect both OS environments.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides environment variable references for Azure App Service across Windows and Linux, but exhibits Windows bias in several ways. Windows-specific tools (such as msbuild, Web Deploy/MSDeploy, IIS, and site extension feeds) are mentioned first or exclusively in many sections. Windows paths and conventions (e.g., D:\home, %HOME%) are often shown before Linux equivalents, and Windows-specific environment variables are more thoroughly documented. Linux build automation (Oryx) is referenced, but Windows build automation (Kudu) is described first and in more detail. Some examples and explanations default to Windows terminology, and Windows tools are referenced more frequently. However, Linux-specific settings and variables are present, and most critical features are documented for both platforms.
Recommendations
- Ensure Linux and Windows examples are presented side-by-side or in parallel, rather than Windows-first.
- Expand Linux-specific documentation, especially for build automation (Oryx), with equivalent detail to Windows/Kudu.
- Where paths or environment variables differ, always show both Windows and Linux formats (e.g., D:\home vs /home).
- Avoid referencing Windows tools (msbuild, IIS, Web Deploy) without mentioning Linux alternatives or clarifying platform applicability.
- Add more Linux/macOS-specific troubleshooting and configuration guidance where relevant.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but in the 'Next steps' section, the only hands-on tutorial linked is for Azure PowerShell, which is Windows-centric and often prioritized for Windows users. There are no equivalent Linux/CLI examples or links provided, and PowerShell is mentioned before any Linux-friendly alternatives.
Recommendations
- Add links to Azure CLI tutorials for creating autoscaling, zone-redundant Application Gateways, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Ensure that both PowerShell and CLI examples are provided in future tutorials and reference material.
- Explicitly mention that Azure CLI can be used for these operations and provide guidance or links for Linux/macOS users.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway concepts and settings. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and (2) backend server log review is linked to IIS (Windows) configuration. These references appear before any mention of Linux equivalents, and no Linux-specific troubleshooting or authentication guidance is provided.
Recommendations
- Add troubleshooting guidance for Linux-based backend servers, including links to relevant documentation for Apache, Nginx, or other common Linux web servers.
- Include examples or references for configuring authentication (such as Kerberos or NTLM) on Linux backends, or clarify if these features are Windows-only.
- When discussing backend server logs, mention both Windows (IIS) and Linux (Apache/Nginx) log locations and interpretation.
- Ensure that links and guidance for backend authentication and logging are platform-inclusive, or explicitly state if a feature is Windows-specific.
Application Gateway
Azure Application Gateway listener configuration
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not offer equivalent examples for Azure CLI, ARM templates, or REST API, which are cross-platform and commonly used on Linux/macOS. There is no mention of Linux-specific tools or guidance, and the only code snippet is Windows/PowerShell-centric.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration tasks, especially for enabling HTTP/2 support.
- Include ARM template and REST API examples where relevant, as these are platform-agnostic.
- Explicitly state that all features are available and manageable from Linux/macOS using Azure CLI or portal.
- Consider reordering or grouping examples so that cross-platform tools (CLI, REST, ARM) are presented before or alongside PowerShell.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides instructions for enabling and managing managed identities in Azure App Service and Azure Functions. While it covers multiple platforms (Azure portal, Azure CLI, Azure PowerShell, ARM templates), PowerShell examples are given their own dedicated sections and are often more detailed. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, PowerShell examples are sometimes shown before CLI equivalents, and there is no explicit mention of Bash or Linux-specific shell usage. The CLI examples are cross-platform, but the documentation does not clarify this or provide Linux/macOS-specific guidance. There are also no explicit Linux/macOS screenshots or notes about parity.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide explicit Bash shell examples where relevant.
- Reduce the prominence of PowerShell by ensuring CLI examples are shown first or equally, and note that PowerShell is Windows-centric.
- Add notes or sections for Linux/macOS users, including any differences in environment variables, shell usage, or authentication.
- Consider including screenshots or instructions for Linux/macOS where portal steps differ.
- Explicitly state platform parity for all code samples and tooling.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent Azure CLI, Bash, or ARM template examples. PowerShell is presented as the primary scripting interface, which is more familiar to Windows users. There are also references to viewing logs in Excel and Visual Studio-based tools, which are Windows-centric. No Linux/macOS-specific instructions or parity examples are provided.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where relevant.
- Mention or demonstrate how to view and process logs using Linux/macOS tools (e.g., jq, grep, awk) in addition to Excel and Power BI.
- Reference cross-platform editors (e.g., VS Code) instead of or alongside Visual Studio.
- Ensure that any downloadable tools or scripts are compatible with Linux/macOS, or clearly state platform requirements.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway health monitoring provides PowerShell-centric examples and references, particularly for custom probe configuration and advanced features (e.g., MinServers and probe match criteria). PowerShell cmdlets are used for illustrating probe matching, and the MinServers property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but the example and guidance focus on PowerShell. Linux equivalents (Azure CLI) are mentioned but not demonstrated, and PowerShell is presented first and most prominently.
Recommendations
- Add Azure CLI examples alongside PowerShell for configuring custom probes, probe match criteria, and MinServers.
- Explicitly state that all features can be managed via Azure CLI and ARM templates, and provide links or examples for Linux/macOS users.
- Where PowerShell is used for illustration, add equivalent CLI syntax and highlight cross-platform options.
- Consider showing CLI examples before or alongside PowerShell to avoid Windows-first impression.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias. Migration and registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a PowerShell-based tutorial as the primary onboarding path, rather than offering parity with Bash or cross-platform CLI options. While the core concepts and features are platform-neutral, the operational guidance favors Windows/PowerShell users.
Recommendations
- Provide Azure CLI (bash) examples alongside PowerShell for migration, registration, and unregistration tasks.
- Add links to tutorials using Azure CLI or ARM templates for Linux/macOS users in the 'Next steps' section.
- Clarify that both PowerShell and Azure CLI can be used for management, and offer guidance for cross-platform users.
- Consider including a note about cross-platform compatibility for all scripts and commands.
Application Gateway
TLS termination with Azure Key Vault certificates
...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for 'TLS termination with Azure Key Vault certificates' demonstrates a moderate Windows/PowerShell bias. While the conceptual information is cross-platform, the only detailed command-line example for configuring Key Vault integration with Application Gateway uses Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bicep/ARM template example. The documentation also refers to PowerShell steps and links to a PowerShell-specific next step, with no parallel guidance for Linux/macOS users who may prefer Azure CLI or other tools.
Recommendations
- Add equivalent Azure CLI examples alongside PowerShell for all command-line configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Where PowerShell is referenced, also mention and link to ARM/Bicep/CLI documentation if available.
- In the 'Next steps' section, provide links to CLI and ARM/Bicep guides in addition to PowerShell.
- When mentioning command-line tools, avoid implying PowerShell is the primary or only supported method.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for configuring client certificate revocation, but PowerShell is presented first and in more detail, with CLI examples being minimal. There are no explicit Linux/macOS-specific instructions or examples for certificate extraction or management, and the 'Next steps' section points only to a PowerShell-based guide. The documentation does not mention Linux-native tools (e.g., OpenSSL) for certificate handling, nor does it provide parity in step-by-step examples for Linux users.
Recommendations
- Add Linux/macOS-focused examples for certificate extraction and management, such as using OpenSSL commands to extract and prepare certificate chains.
- Ensure CLI examples are as detailed as PowerShell examples, including all relevant steps and explanations.
- In the 'Next steps' section, provide links to both PowerShell and Azure CLI (and, if possible, ARM/Bicep template) guides for mutual authentication configuration.
- When referencing tools or commands, mention cross-platform alternatives and clarify that Azure CLI is available on all major platforms.
- Consider reordering sections so that CLI and cross-platform methods are presented before or alongside PowerShell examples.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references the Windows-specific PFXImportCertStore function for PFX certificate requirements and links the next steps to a PowerShell-based configuration guide, without providing Linux/macOS equivalents or cross-platform alternatives. No Linux or OpenSSL-based certificate creation/import guidance is present, and Windows tooling is mentioned first and exclusively.
Recommendations
- Add guidance or links for creating and managing PFX certificates using OpenSSL (cross-platform) or Linux/macOS tools, not just referencing Windows APIs.
- In the 'Next steps' section, provide links to CLI (az CLI), ARM template, or Portal-based configuration guides in addition to or before PowerShell.
- Where Windows-specific APIs or tools are referenced (e.g., PFXImportCertStore), clarify that this is a Windows API and provide equivalent cross-platform instructions or references.
- Ensure that examples and walkthroughs are available for Linux/macOS users, especially for certificate preparation and Application Gateway configuration.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for Azure Automation disaster recovery is notably PowerShell-centric, with all migration scripts and runbook examples provided exclusively in PowerShell and PowerShell Workflow. There are no Linux shell (bash) or cross-platform scripting examples, nor are alternatives like Azure CLI or REST API mentioned for asset migration. Windows terminology and links (e.g., 'tabs=windows') appear first or exclusively in Hybrid Runbook Worker instructions, even though Linux is supported. This creates friction for Linux/macOS users, especially those who prefer bash or cross-platform tools.
Recommendations
- Provide equivalent migration scripts or instructions using Azure CLI and/or bash for asset migration between Automation accounts.
- Mention and link to cross-platform tools or REST API options for Automation asset management.
- When referencing Hybrid Runbook Worker installation, ensure both Windows and Linux tabs/examples are equally visible and linked.
- Clarify that PowerShell scripts can be executed from Linux/macOS environments using PowerShell Core, or provide guidance for those platforms.
- Consider including Python runbook migration options, since Python is supported in Azure Automation.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, without offering an equivalent CLI or ARM template example for Linux/macOS users. Additionally, PowerShell is presented as the primary scripting method, and Windows terminology (such as host file usage and PowerShell DSC) is referenced before Linux alternatives. However, the overall guidance is mostly platform-neutral, and Linux is acknowledged in the context of Hybrid Runbook Workers and Update Management.
Recommendations
- Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' property, alongside the PowerShell example.
- Explicitly mention that the steps can be performed from any OS using Azure CLI or portal.
- Where PowerShell DSC is referenced, clarify Linux equivalents or alternatives (such as using Python or Bash for runbooks).
- Ensure that host file and DNS configuration instructions include Linux/macOS syntax and paths (e.g., /etc/hosts).
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on PowerShell cmdlets and Windows PowerShell examples for managing credentials in Azure Automation. While Python examples are provided, there are no examples or guidance for Linux/macOS users who may want to use Bash, CLI, or other non-Windows tools. The PowerShell-centric approach may create friction for Linux/macOS users, especially since credential management is presented almost exclusively in the context of PowerShell and Windows.
Recommendations
- Add Azure CLI examples for credential asset management, where possible, to support Linux/macOS users.
- Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these cmdlets, and provide examples if so.
- Explicitly mention any limitations or alternatives for Linux/macOS users in sections that reference Windows PowerShell.
- Provide guidance or links for managing credentials via REST API or SDKs for cross-platform scenarios.
- Ensure that the 'Create a new credential asset' section includes steps for users on Linux/macOS, or at least clarifies platform requirements.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions are mentioned first and more prominently, with explicit links to Windows registry settings and PowerShell cmdlets. Several sections (data retention, backup) reference Windows PowerShell cmdlets without Linux CLI or scripting equivalents, and Windows-specific tools (PowerShell) are used for examples. Linux guidance is present but less detailed and less prominent.
Recommendations
- Provide Linux CLI or scripting equivalents for PowerShell cmdlets (e.g., az CLI, Bash, Python) when discussing data retention and backup.
- Ensure Linux examples are given equal prominence and detail as Windows examples, including links to relevant Linux documentation.
- Consider presenting platform-neutral guidance first, or alternate Windows and Linux examples to avoid 'windows_first' bias.
- Where PowerShell is referenced, clarify if az CLI or REST API alternatives exist for Linux/macOS users.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell examples for configuring secure asset encryption in Azure Automation, with REST API alternatives. However, it lacks examples or guidance for Linux/macOS users, such as Azure CLI or Bash scripting. PowerShell is presented as the primary method, and Linux-friendly tools are only mentioned briefly (in the context of revoking access), creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples for all major tasks (assigning managed identities, configuring Key Vault access policies, switching to customer-managed keys, etc.) alongside PowerShell examples.
- Explicitly mention that PowerShell Core (pwsh) is cross-platform and provide guidance for Linux/macOS users where applicable.
- Where REST API calls are shown, provide sample Bash/cURL commands to demonstrate usage from Linux/macOS environments.
- Ensure that references to PowerShell modules clarify their compatibility with PowerShell Core and non-Windows platforms.
- Consider showing CLI or REST examples before PowerShell, or at least in parallel, to reduce Windows-first bias.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell-based runbooks, with examples, screenshots, and parameter handling almost exclusively shown via PowerShell and PowerShell Workflow. PowerShell cmdlets and Windows-centric patterns (e.g., PowerShell hashtables, .NET types) are presented first and in detail, while Python runbooks (the main cross-platform alternative) receive minimal coverage and lack practical examples. There are no Linux/macOS-specific instructions or CLI examples for starting runbooks or passing parameters, and the REST API section does not clarify cross-platform usage.
Recommendations
- Add detailed examples for Python runbooks, including parameter handling and starting runbooks from Linux/macOS environments.
- Provide Azure CLI examples for starting runbooks and passing parameters, as CLI is cross-platform.
- Clarify that PowerShell examples can be run on PowerShell Core (pwsh) on Linux/macOS, and provide any necessary caveats.
- Include guidance for Linux/macOS users on prerequisites and environment setup for Azure Automation.
- Expand REST API examples to show how to invoke from Linux/macOS (e.g., using curl or HTTPie).
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows, with nearly all examples, tools, and instructions referencing PowerShell, Windows PowerShell versions, and Windows-specific cmdlets. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, but Linux support is only briefly mentioned. There are no Linux/bash examples, and Linux module management is not covered. Python module support is referenced, but only as a link to another page.
Recommendations
- Add explicit guidance and examples for Linux Hybrid Runbook Workers, including module management and limitations.
- Include bash or Python examples for relevant tasks, especially for module import and management.
- Clarify which features are Windows-only and provide Linux alternatives or workarounds where possible.
- Expand documentation on Python modules and their management within Azure Automation, including parity with PowerShell module workflows.
- Add a comparison table or section summarizing feature parity and limitations between Windows and Linux Hybrid Runbook Workers.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service plans, explicitly noting support for both Windows and Linux. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (such as PowerShell, RDP, IIS customization, .NET Framework) are described first and in detail, with a clear statement that this feature is Windows-only. The rest of the documentation does not show Windows bias: there are no Windows/PowerShell-only examples, and Linux is mentioned equally in the context of App Service plans.
Recommendations
- Clarify early in the Managed Instance section that it is Windows-only to avoid confusion for Linux users.
- Consider adding a brief note or link to Linux-specific hosting options or limitations for parity, even if Managed Instance is Windows-only.
- Ensure that any future examples or walkthroughs (e.g., scaling, cost management) include both Windows and Linux scenarios where applicable.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts and permissions. However, in the section about DNS server changes, restart instructions reference Azure PowerShell cmdlets (Stop-AzApplicationGateway and Start-AzApplicationGateway) without mentioning equivalent Azure CLI commands or portal actions. This places Windows/PowerShell tooling first and may create friction for Linux/macOS users who prefer Azure CLI or portal.
Recommendations
- Add Azure CLI examples alongside PowerShell for restarting Application Gateway after DNS changes.
- Mention that the Azure Portal can also be used for restart operations, if applicable.
- Ensure all procedural instructions reference both PowerShell and CLI (or portal) options where possible.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides troubleshooting steps for Application Gateway for Containers and includes both Linux and Windows-specific log filtering commands. However, the Windows example (using 'findstr') is presented after the Linux example (using 'grep'), and both are clearly labeled. There are no exclusive Windows tools or patterns, and all critical commands are cross-platform. The overall bias is minimal, with only minor ordering preference.
Recommendations
- Ensure both Linux and Windows examples are given equal prominence, possibly by using tabbed code blocks or parallel presentation.
- Explicitly mention macOS compatibility where relevant (since macOS uses Unix-like tools).
- Add a brief note that all kubectl commands are cross-platform and clarify any OS-specific syntax differences.
- Consider listing Windows and Linux commands side-by-side for easier comparison.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell, but PowerShell syntax is consistently shown immediately after bash, and the note on shell support mentions PowerShell first. There are no Windows-only tools or patterns, but the ordering and emphasis slightly favor Windows/PowerShell users. All steps are achievable on Linux/macOS, but minor bias exists in example ordering.
Recommendations
- Alternate the order of bash and PowerShell examples, or show bash first where appropriate.
- Explicitly mention that all steps are fully supported on Linux/macOS, not just 'can run in PowerShell or bash'.
- Add a short section or note highlighting Linux/macOS compatibility and any prerequisites (e.g., Azure CLI installation on Linux).
- Consider grouping shell examples together, or using tabs to let users select their preferred shell.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are shown immediately after Bash for every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may signal a Windows-first bias. There are no missing Linux examples, but the repeated inclusion and labeling of PowerShell commands could create friction for Linux/macOS users.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to avoid overwhelming users with both formats inline.
- Ensure Bash examples are presented first or equally, and clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a short note explaining which shell to use on each platform, helping users select the appropriate example.
- If possible, minimize duplication by referencing the shell-specific syntax only where it differs significantly.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are shown immediately after Bash for every command, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'). This creates a slight bias toward Windows users, as Linux/macOS users are not given additional context or troubleshooting tips. The Bash examples are present and correct, so Linux parity is mostly maintained.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS, and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under explicit OS tabs (e.g., 'Linux/macOS', 'Windows') for clarity.
- Add a note indicating that Azure CLI commands work cross-platform, and provide troubleshooting tips for common shell differences.
- Ensure variable naming and syntax are consistent and correct for each shell (e.g., check for variable name mismatches like $apimID vs $apicObjID).
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no explicit Linux/macOS bias. The instructions reference uploading files to Azure Cloud Shell, which is cross-platform, but do not mention Linux-specific shell usage or tools (e.g., Bash). The order of examples does not consistently favor Windows, but PowerShell is present throughout, which may create minor friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, or clarify that Azure CLI commands work in Bash and other shells.
- Mention that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- Consider providing a note or section for Linux/macOS users about uploading files and running CLI commands from their native environments.
- If PowerShell is not required, clarify that it is optional and that CLI is recommended for cross-platform scenarios.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files. However, PowerShell is presented as a primary alternative to Azure CLI, and PowerShell requirements are mentioned alongside CLI prerequisites. The examples are split into CLI and PowerShell tabs, but there is no explicit mention of Bash or Linux-specific shell environments, nor are there instructions tailored for Linux/macOS users (e.g., file path conventions, shell-specific notes). The documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Add explicit notes or examples for Bash or other Linux/macOS shell environments, especially regarding file paths and uploading files.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux/macOS shells.
- Include a brief section or note for Linux/macOS users about using Azure CLI in their native environments.
- Ensure that prerequisites and environment setup instructions mention Linux/macOS options (e.g., installing Azure CLI on Linux/macOS, using Cloud Shell from a browser).
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides command-line examples for disabling routing to a regional gateway using Azure CLI and references Azure PowerShell cmdlets. The PowerShell cmdlet (set-azapimanagement) is mentioned alongside Azure CLI, but no Linux/macOS-specific guidance or examples are provided. The Azure portal steps are platform-neutral, but in the CLI section, PowerShell is referenced before Linux alternatives, and no Bash or Linux-specific nuances are discussed.
Recommendations
- Ensure parity by providing explicit Bash/Linux/macOS examples where Azure CLI is used, including any OS-specific nuances.
- When referencing Azure PowerShell, clarify its cross-platform support or provide alternative instructions for Linux/macOS users.
- If PowerShell is mentioned, also mention Bash or other shells, and clarify that Azure CLI works on all platforms.
- Consider adding a note that all Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions Windows/PowerShell (Azure PowerShell) as an option for creating an AKS cluster before Linux alternatives (Azure CLI), but provides no actual PowerShell-specific examples. All deployment and verification steps use cross-platform tools (kubectl), and no Windows-only tools or patterns are shown. The bias is limited to listing Windows/PowerShell before Linux/CLI in the prerequisites.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly note that all deployment steps use cross-platform tools (kubectl), and that the process is OS-agnostic.
- If mentioning Azure PowerShell, also mention that it is available on Linux/macOS, or clarify its platform support.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. PowerShell is included as a primary workflow, which is Windows-centric, and is presented equally alongside CLI. There is no explicit Linux/macOS bias, but PowerShell is not natively available on most Linux/macOS systems, and no Bash or shell script examples are given. The CLI example is cross-platform, but PowerShell's inclusion and prominence may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but may require installation on Linux/macOS.
- Consider adding Bash or shell script examples for Linux/macOS users, especially for common tasks.
- Explicitly note that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- If PowerShell is used, provide guidance for Linux/macOS installation or alternatives.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for importing SOAP APIs, but PowerShell examples are given equal prominence to CLI examples, and PowerShell is a Windows-centric tool. The prerequisites list both Azure CLI and PowerShell, but does not clarify that PowerShell is cross-platform (though it is, many users associate it with Windows). The portal instructions are platform-neutral. Azure CLI is shown before PowerShell, but both are presented as tabs, so ordering bias is minimal. No Linux-specific tools or shell examples are given, but Azure CLI is the standard cross-platform tool.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid confusion.
- Consider adding a note for Linux/macOS users about installing Azure CLI and PowerShell, linking to platform-specific instructions.
- Explicitly mention that the Azure CLI example works on all major OSes, while PowerShell is also available cross-platform.
- If possible, provide a Bash shell example for invoking Azure CLI, to reinforce Linux parity.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely platform-neutral and focuses on Azure networking concepts, but there is a minor instance of Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks before any Linux/CLI alternatives are mentioned.
Recommendations
- In the 'Related content' section, add or prioritize links to equivalent Azure CLI or Azure Portal guides for connecting virtual networks, ensuring Linux/macOS users see relevant options.
- Where PowerShell is referenced, clarify that Azure CLI or Portal alternatives exist and provide links to those resources.
- Review cross-referenced articles to ensure parity in example coverage (PowerShell, CLI, Portal) and update links as needed.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured to provide parity between Windows and Linux custom container configuration in Azure App Service, using pivot sections for each OS. However, there are several areas where Windows examples, tools, and terminology are presented first or more prominently. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows-specific tools (like Kudu, IIS, .NET Framework, and Windows directory paths) are referenced before or more extensively than their Linux equivalents. Some sections (such as memory/core customization and persistent storage) show Windows details first, and troubleshooting/logging instructions often reference Windows-centric tools and paths.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally alternating or grouping by OS rather than always showing Windows first.
- Where PowerShell commands are given, ensure Bash/Azure CLI equivalents are equally detailed and not secondary.
- Expand Linux-specific troubleshooting/logging guidance to match the detail provided for Windows (e.g., Kudu, SSH, log access).
- Clarify Linux-specific directory paths and behaviors, avoiding references to Windows paths (e.g., C:\home) in Linux sections unless explicitly comparing.
- Where possible, provide Linux-first examples in sections that are not inherently Windows-centric.
- Review the use of Windows tools and terminology to ensure Linux users are not required to mentally translate instructions.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation generally provides cross-platform guidance, especially for certificate creation and management, with explicit OpenSSL (Linux/macOS) and Azure CLI examples. However, there are several instances where Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, and PowerShell examples are provided alongside Azure CLI, sometimes with PowerShell shown first. Some links for certificate export reference Windows-only documentation. These patterns may create minor friction for Linux/macOS users, but workarounds and alternatives are present.
Recommendations
- Ensure that for every mention of Windows tools (IIS, Certreq.exe), equivalent Linux/macOS instructions or links are provided, not just OpenSSL.
- When referencing certificate export, link to cross-platform guides or add explicit Linux/macOS instructions, not just Windows Server documentation.
- Present Azure CLI examples before PowerShell, or clarify that both are supported equally.
- Review FAQ and related content to ensure parity in scripting and automation examples for Linux/macOS (e.g., Bash, Azure CLI).
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides step-by-step instructions and code examples for Azure portal, Azure CLI, and Azure PowerShell. PowerShell examples are present throughout, and in some sections, the PowerShell tab appears before or alongside CLI, which may suggest a slight preference for Windows tooling. However, all critical operations are fully covered with Azure CLI commands, ensuring Linux/macOS users can complete the migration. There are no Windows-only tools or patterns, and Linux is explicitly supported by the feature being documented.
Recommendations
- Ensure that Azure CLI examples are always presented before or at the same prominence as PowerShell examples, as CLI is cross-platform.
- Consider explicitly stating that all CLI commands are fully supported on Linux/macOS to reassure non-Windows users.
- If possible, add a brief note that PowerShell Core is available cross-platform, or clarify when examples are Windows PowerShell-specific.
- Continue to avoid using Windows-only tools or terminology in general-purpose networking documentation.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.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 the PowerShell examples are prominent and detailed, which may favor Windows users. Helm installation instructions are given for both Windows and Linux, but Windows is listed first. There are no missing Linux examples, and Bash usage is acknowledged. The overall parity is good, but Windows examples and tools are often presented before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Explicitly mention Bash or Linux shell alternatives where Azure CLI is used, since Azure CLI is cross-platform.
- Consider grouping CLI and PowerShell examples together, or clarify that Azure CLI commands work on all platforms.
- Add a brief note at the start clarifying that all Azure CLI commands are cross-platform and can be run on Linux/macOS/Windows.
- For Helm installation, list Linux instructions first or equally prominent, since many Kubernetes admins use Linux/macOS.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on
...pplication-gateway-for-containers-alb-controller-addon.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is given equal prominence and is included in nearly every major step. In some sections, PowerShell examples are shown before or alongside Azure CLI, which may create friction for Linux/macOS users. However, all critical tasks can be completed using Azure CLI, and no Windows-only tools or patterns are required. There are no missing Linux examples, as Azure CLI is cross-platform and is the primary tool for most steps.
Recommendations
- Consider making Azure CLI the default or primary example in each section, with PowerShell as an optional tab for Windows users.
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Where PowerShell is used, ensure that equivalent Azure CLI commands are always provided and shown first.
- Explicitly note that PowerShell examples are for Windows environments, and CLI is preferred for Linux/macOS.
Azure App Configuration
Use variant feature flags in a Spring Boot application
...figuration/how-to-variant-feature-flags-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), but all platforms are covered. No Windows-only tools or patterns are used, and the examples are cross-platform Java/Spring Boot. No Linux/macOS examples are missing.
Recommendations
- Present Linux/macOS instructions before Windows instructions, or group them equally.
- Consider using tabbed instructions for each OS to improve clarity and parity.
- Explicitly state that the tutorial works on Windows, Linux, and macOS at the start.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup examples for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific instructions such as restarting the command prompt after using setx. While Linux/macOS examples are present, Windows commands are consistently shown first and receive more detailed instructions. The use of PowerShell and Windows command prompt is prominent, but Linux/macOS parity is maintained overall.
Recommendations
- Present Linux/macOS (bash) examples before or alongside Windows examples to avoid Windows-first bias.
- Clarify that restarting the shell may be required on all platforms, not just Windows.
- Ensure instructions for Linux/macOS are as detailed as those for Windows (e.g., how to persist environment variables across sessions).
- Consider grouping environment variable instructions by platform in a more balanced way.