245
Pages Scanned
48
Pages Flagged
245
Changed Pages
19.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:11
Scan Information
Started At: 2026-02-21 00:00:11
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 245
Files Completed: 245
Problematic Pages
48 issues found
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
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation (New-SelfSignedCertificate, Export-PfxCertificate), and does not provide equivalent Bash, Azure CLI, or Linux/macOS-compatible instructions. Windows-specific file paths (e.g., c:\appgwcert.pfx) and certificate store locations are used. There is no mention of Linux/macOS alternatives or cross-platform guidance, making the tutorial strongly Windows-centric.
Recommendations
- Add Azure CLI examples for each step, especially for resource creation and configuration.
- Provide Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL).
- Use generic file paths or explain how to adapt paths for Linux/macOS.
- Include notes or sections for Linux/macOS users, clarifying any differences or limitations.
- Consider offering a Bash script version of the tutorial alongside the PowerShell version.
Create Pull Request
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 heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell is used for all command-line examples, and Windows installation methods (MSI, Setup.exe, winget) are emphasized. There are no Linux/macOS equivalents or guidance for non-Windows users, even though some integrations (GitHub Actions, Azure DevOps, SDK) could be cross-platform.
Recommendations
- Clearly indicate if SignTool integration is Windows-only, and provide alternative signing workflows for Linux/macOS users where possible.
- For cross-platform integrations (GitHub Actions, Azure DevOps, SDK), add explicit Linux/macOS setup instructions and examples.
- If Artifact Signing supports non-Windows signing tools (e.g., OpenSSL, GPG, or other CLI tools), document their usage.
- For PowerShell-heavy sections, offer Bash or shell script equivalents for Linux/macOS users.
- Add a section summarizing platform support and limitations up front, so users know if Windows is required for certain integrations.
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 configuration examples primarily using Azure PowerShell, with PowerShell commands shown first and in more detail than Azure CLI. There is no mention of Linux/macOS-specific tools or workflows, and the CLI example is minimal. The 'Next steps' section links only to a PowerShell guide, omitting Linux-focused or CLI-based guides. Azure portal support is noted as unavailable, but Linux users are not given parity in guidance or examples.
Recommendations
- Provide Azure CLI examples with equal detail and prominence as PowerShell, including step-by-step instructions.
- Add links to Linux/macOS-focused guides for configuring mutual authentication, or explicitly mention that Azure CLI can be used cross-platform.
- In 'Next steps', include links to CLI and ARM template guides, not just PowerShell.
- Where PowerShell is referenced, clarify that Azure CLI is available and suitable for Linux/macOS users.
- Consider including sample certificate extraction commands using OpenSSL (common on Linux/macOS) alongside any Windows-specific tools.
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 heavily features PowerShell examples for all procedural steps, with no equivalent examples for Azure CLI, Bash, or other Linux/macOS-friendly tools. PowerShell is presented as the primary scripting interface, and REST API examples are included, but Linux-native workflows (such as Azure CLI or Bash scripting) are not covered. This creates friction for Linux/macOS users, who must translate PowerShell steps or rely on REST API calls without guidance.
Recommendations
- Add Azure CLI examples for all procedural steps (e.g., assigning managed identities, configuring Key Vault access policies, reconfiguring encryption keys).
- Include Bash scripting samples where appropriate, especially for automation scenarios.
- Present Azure CLI and PowerShell examples side-by-side, or at least mention Azure CLI as an alternative.
- Clarify that PowerShell examples work cross-platform (if true), or note any Windows-specific limitations.
- Link to Azure CLI documentation for relevant commands (e.g., az automation account, az keyvault).
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 and Windows-centric tools and patterns. All CLI examples are given in PowerShell, with no Bash, Linux, or macOS shell equivalents. The creation and management of credentials are described exclusively using PowerShell cmdlets, and the phrase 'Windows PowerShell' is used explicitly. Python examples are provided, but there are no Linux-native shell or CLI examples for credential management. The documentation assumes familiarity with PowerShell and Windows concepts, which creates friction for Linux/macOS users.
Recommendations
- Add Bash/CLI examples for credential management where possible, such as using Azure CLI (az) commands.
- Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used instead of Windows PowerShell.
- Explicitly mention Linux/macOS support and limitations for credential assets in Azure Automation.
- Provide guidance or links for Linux/macOS users on how to interact with Azure Automation credentials outside of PowerShell.
- If PowerShell is required, note that PowerShell Core is available cross-platform and provide installation instructions.
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
missing_linux_example
windows_first
Summary
The documentation provides detailed instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples are exclusively in Azure PowerShell, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred by many Linux/macOS users. The PowerShell instructions are presented before ARM template examples, and there is no guidance for Linux-native tools or workflows.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (creating resource groups, API Management instances, managed identities, updating instances).
- Explicitly mention that Azure PowerShell can be used on Linux/macOS, but provide parity with Azure CLI for users who prefer Bash or native Linux tools.
- Consider showing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
- Link to Azure CLI documentation and samples for API Management and managed identities.
- Clarify that ARM templates are platform-agnostic and can be deployed from any OS.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating certificate operations, but PowerShell is mentioned equally or slightly more prominently. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and PowerShell is listed as a primary automation option. Linux tools (OpenSSL) are mentioned for certificate creation/export, but Windows tools are referenced first or equally, and some links point to Windows documentation. There is no section that is Windows-only, but Windows patterns and tooling are visible throughout.
Recommendations
- Ensure Linux equivalents are always mentioned alongside Windows tools (e.g., for certificate export, link to OpenSSL documentation before or equally with Windows tools).
- Provide Bash or shell script examples for automation, not just PowerShell and Azure CLI.
- Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS users.
- When referencing certificate export, include step-by-step OpenSSL instructions before Windows-specific tools.
- Review FAQ and automation sections to ensure Linux/macOS parity in examples and links.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page for Azure App Service backups is generally cross-platform, but there are several areas where Windows bias is evident. Windows directory paths (e.g., `%HOME%`, `D:\home\site\wwwroot`) are used as primary examples, and tools like Kudu DebugConsole and FTP are referenced with Windows-centric paths. PowerShell is mentioned alongside Azure CLI for automation, but Linux shell examples are not provided. The documentation often presents Windows patterns first, with Linux equivalents mentioned later or not at all.
Recommendations
- Provide Linux/macOS directory path examples (e.g., `/home/site/wwwroot`) alongside Windows paths.
- Clarify that tools like Kudu DebugConsole and FTP are available and usable from Linux/macOS environments, and provide relevant instructions.
- Include bash or shell script samples for automation, not just Azure CLI and PowerShell.
- When referencing environment variables or file paths, show both Windows and Linux formats.
- Ensure screenshots and instructions in the portal are not Windows-centric unless the feature is Windows-only.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and focuses on Azure App Service networking features, which apply to both Windows and Linux hosted apps. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux support or alternatives. This creates friction for Linux users who may need to use Hybrid Connections but are not provided guidance or examples for their platform.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux, and provide installation instructions or alternatives for Linux hosts if supported.
- Explicitly state platform limitations for features that are Windows-only, such as Gateway-required virtual network integration, to avoid confusion.
- Where possible, provide Linux-specific examples or note parity for features that are cross-platform.
- Add a note or link to documentation about Hybrid Connection Manager support for Linux, or explain why it is Windows-only if that is the case.
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 demonstrates a moderate Windows bias. Windows-specific instructions and code samples (especially for certificate loading) are presented first and in greater detail, with C# and Java examples focused on the Windows certificate store. Linux guidance is present but less prominent, and non-Windows language examples (Node.js, PHP, Python, Java) are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, user profile loading) are emphasized, while Linux equivalents are less thoroughly explained.
Recommendations
- Provide Linux examples alongside Windows examples in each relevant section, not just in container-specific tabs.
- Include code samples for loading certificates in popular languages (Node.js, Python, Java, PHP) on both Windows and Linux, rather than referring users to external documentation.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or use tabbed content for all major OSes.
- Clarify any differences in certificate handling between Windows and Linux up front, and provide guidance for cross-platform scenarios.
- Expand on Linux-specific environment variables and best practices, similar to the detail given for Windows.
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 page covers environment variables and app settings for Azure App Service, supporting both Windows and Linux platforms. However, there are several instances where Windows-specific paths, tools, and terminology are presented first or exclusively. Windows paths (e.g., D:\home) are often shown before Linux equivalents, and Windows-specific tools like Web Deploy/MSDeploy and IIS are referenced without always providing Linux alternatives. Some sections (such as Kudu build automation) focus heavily on Windows, with Linux (Oryx) relegated to a separate tab. Examples and explanations frequently default to Windows conventions, creating friction for Linux/macOS users.
Recommendations
- Ensure all environment variable descriptions provide both Windows and Linux path examples, with Linux shown equally or first where appropriate.
- Where Windows tools (e.g., Web Deploy/MSDeploy, IIS, site extensions) are mentioned, explicitly note Linux alternatives or limitations.
- For build automation, provide equal detail for Oryx (Linux) as for Kudu (Windows), including environment variables and usage examples.
- Avoid defaulting to Windows terminology (e.g., %HOME%, D:\home) in general explanations; use platform-neutral language or show Linux equivalents alongside.
- Add Linux/macOS-specific troubleshooting tips and examples where Windows-specific guidance is given.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI or Bash example for Linux/macOS users. The only command-line automation shown is via PowerShell, and there are references to tools like Excel and Visual Studio, which are primarily Windows-centric. There is no mention of Azure CLI, Bash, or cross-platform scripting alternatives.
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 snippets where automation is discussed, or at least reference that Azure CLI can be used from any OS.
- When mentioning tools for log analysis (e.g., Excel, Visual Studio), also mention cross-platform alternatives such as jq, pandas (Python), or open-source log viewers.
- Ensure that references to PowerShell are clearly marked as Windows-specific, and provide links or guidance for Linux/macOS users.
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 exclusively demonstrates the configuration using a SQL Server VM running Windows Server and recommends SQL Server Management Studio (SSMS) as the client tool, both of which are Windows-centric. There are no examples or guidance for deploying a SQL Server VM on Linux or connecting from Linux/macOS clients, nor are cross-platform SQL client tools mentioned.
Recommendations
- Include instructions for deploying SQL Server on a Linux VM in Azure, or clarify that Linux is supported if applicable.
- Mention and provide examples for connecting to the SQL Server via cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other open source tools.
- Add notes or links for Linux/macOS users regarding SQL authentication setup and client connectivity.
- If SSMS is Windows-only, recommend alternative tools for Linux/macOS users.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all migration instructions, examples, and tooling based exclusively on PowerShell. There are no references to Azure CLI, Bash, or cross-platform scripting alternatives, nor are Linux/macOS usage patterns or prerequisites mentioned. The guidance assumes a Windows/PowerShell environment throughout, which creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Provide Azure CLI equivalents for all migration steps, including configuration migration, certificate handling, and traffic migration.
- Include Bash script examples and instructions for Linux/macOS users, especially for certificate manipulation and script installation.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which is cross-platform), and explicitly mention this as an option for non-Windows users.
- Add a section outlining Linux/macOS prerequisites and environment setup for running migration scripts.
- Where possible, link to Azure CLI documentation and tools for Application Gateway management.
- Consider providing downloadable Bash or Python scripts for migration tasks, or note limitations if PowerShell is required.
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 shows moderate Windows bias. Migration guidance and tutorials reference Azure PowerShell scripts and provide PowerShell-centric instructions, with no mention of Bash, Linux CLI, or cross-platform alternatives. The registration/unregistration steps for the Basic SKU use Azure CLI, but the commands shown are PowerShell-style (e.g., Set-AzContext), which is not standard Bash or Linux Azure CLI syntax. Additionally, the 'Next steps' section links primarily to PowerShell-based tutorials, with no Linux/Bash alternatives or parity.
Recommendations
- Provide Bash/Linux Azure CLI command examples alongside PowerShell commands, especially for registration/unregistration and migration tasks.
- Link to or create tutorials that use cross-platform Azure CLI (az) commands, not just PowerShell.
- Clarify which commands are PowerShell-specific and offer equivalent Bash/Linux syntax where possible.
- Ensure migration scripts and guidance are available for Linux/macOS users, not just Windows/PowerShell.
- In 'Next steps', include links to Linux/Bash tutorials or documentation for creating and managing Application Gateway.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 frequently references Azure PowerShell scripts as the primary migration tooling. There are no examples or mentions of Azure CLI or Bash alternatives, nor guidance for Linux/macOS users. PowerShell is a Windows-native tool, and its prominence creates friction for users on other platforms. Additionally, the documentation does not clarify cross-platform compatibility or provide Linux/macOS-specific instructions.
Recommendations
- Add Azure CLI examples and scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly state whether the PowerShell scripts can be run on Linux/macOS (using PowerShell Core), and provide installation guidance if so.
- Provide Bash or shell script alternatives where feasible.
- Mention Azure Portal as a platform-agnostic option for migration steps, if available.
- Ensure that migration instructions are not solely dependent on Windows tools.
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
powershell_heavy
windows_first
Summary
The documentation page provides a conceptual overview of end-to-end TLS on Azure Application Gateway. While the main content is platform-neutral, the 'Next steps' section directs users exclusively to a PowerShell-based configuration guide, implying Windows as the primary platform for hands-on tasks. No Linux or cross-platform CLI examples or links are provided, and Windows-specific terminology (e.g., PFXImportCertStore) is referenced before any Linux equivalents.
Recommendations
- Add links to equivalent Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway, ensuring Linux/macOS users have clear, supported paths.
- Include examples or references for certificate management and conversion using cross-platform tools (e.g., OpenSSL) alongside Windows-specific tools.
- Mention that PowerShell is available cross-platform, but clarify if the referenced guide is Windows-only or provide guidance for PowerShell Core on Linux/macOS.
- Where Windows APIs or formats (like PFXImportCertStore) are mentioned, briefly note Linux/macOS alternatives or relevant documentation.
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 is heavily focused on PowerShell scripts and workflows for migration and disaster recovery tasks, with no mention of Bash, Python, or CLI alternatives. All migration examples and instructions are PowerShell-based, and the tabs and links default to Windows/PowerShell terminology. While the page claims applicability to both Linux and Windows VMs, Linux users are left without platform-native scripting guidance, creating friction for those not using PowerShell.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for migration tasks, or at least mention if PowerShell Core (pwsh) is supported cross-platform.
- Clarify whether PowerShell Core scripts can be executed on Linux Hybrid Runbook Workers, and provide explicit Linux instructions if so.
- Add examples or links for Python runbooks or other cross-platform automation options.
- Reorder or balance examples so Linux and Windows approaches are presented equally, or in parallel tabs.
- Explicitly state any limitations or requirements for Linux users (e.g., if only PowerShell is supported, clarify that PowerShell Core is required and provide installation guidance).
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-specific instructions and PowerShell cmdlets are mentioned first or exclusively in several sections (e.g., retention and backup). Windows registry settings and PowerShell tools are referenced without Linux equivalents, and Windows examples precede Linux ones in some areas.
Recommendations
- Add parity for Linux in retention and backup sections by referencing Linux CLI or scripting methods (e.g., Azure CLI, Bash, Python) for managing and exporting resources.
- Where PowerShell cmdlets are mentioned, also provide equivalent Azure CLI or REST API commands for Linux/macOS users.
- Ensure Linux instructions are presented alongside Windows instructions, not after or below them.
- Clarify when a feature or tool is Windows-only, and provide alternative guidance for Linux users where possible.
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 and Windows terminology appear first in some sections, such as referencing the Log Analytics agent for Windows before Linux. However, the overall guidance is mostly platform-neutral, and Linux is mentioned where relevant (e.g., Log Analytics agent support, Update Management for Windows and Linux).
Recommendations
- Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' to ensure Linux/macOS users can follow along without relying on PowerShell.
- Where possible, present cross-platform options (PowerShell, CLI, Portal) together, or list CLI/portal methods before PowerShell.
- Clarify that the PowerShell example is just one option, and link to documentation for CLI/ARM/REST alternatives.
- Ensure screenshots and instructions are not Windows-centric unless the feature is Windows-only.
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 usage for Azure Automation authentication with Microsoft Entra ID. All code examples, module references, and credential handling are presented exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS scripting alternatives. Windows-specific tools and patterns (PSCredential, PowerShell modules) are referenced throughout, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
- Add Azure CLI examples for authentication and credential management in Azure Automation.
- Provide guidance for Linux/macOS users on how to create and manage credential assets using the Azure portal or CLI.
- Mention cross-platform PowerShell Core compatibility and clarify if scripts work on Linux/macOS environments.
- Include notes or links to relevant Linux/macOS documentation for Azure Automation and Microsoft Entra ID integration.
- Where possible, show Bash or Python alternatives for runbook automation.
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_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. Nearly all code examples, parameter handling, and automation scenarios are shown using PowerShell or C#, with no equivalent examples for Linux/macOS shells (e.g., Bash, Azure CLI). The only non-PowerShell runbook type discussed is Python, but even there, examples are minimal and lack parity with PowerShell sections. There are no Bash or Azure CLI examples for starting runbooks or passing parameters, and the workflow for Linux/macOS users is not addressed. The documentation assumes PowerShell as the primary interface for both authoring and invoking runbooks.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, showing equivalent workflows to the PowerShell cmdlets.
- Include Bash shell examples for interacting with the REST API (e.g., using curl or httpie) to start runbooks and pass parameters.
- Provide guidance for Linux/macOS users on installing and using Azure PowerShell (if required), or clarify when PowerShell Core (cross-platform) is supported.
- Expand the Python runbook section with more detailed examples, including parameter handling and invocation from non-Windows environments.
- Clearly indicate when features or cmdlets are Windows-only, and suggest cross-platform alternatives where available.
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 features PowerShell cmdlets and examples, with all certificate management tasks (creation, retrieval, deployment) demonstrated exclusively using PowerShell. There are no examples or guidance for Linux/macOS users on how to perform equivalent tasks using bash, Azure CLI, or other cross-platform tools. PowerShell is presented as the primary and default method, and Linux alternatives are not mentioned or provided.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deployment) to provide parity for Linux/macOS users.
- Include bash or shell script examples where relevant, especially for uploading certificates or interacting with Azure Automation.
- Clarify that PowerShell examples are cross-platform if applicable (e.g., PowerShell Core), or specify Windows-only limitations.
- Mention any limitations or differences for Linux/macOS users, and provide links to relevant documentation for those platforms.
- Reorder sections or add tabs so that Azure CLI or Python examples are shown alongside or before PowerShell examples.
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell modules and cmdlets, with all examples and instructions using PowerShell syntax and tools. Windows-specific modules and features (such as internal cmdlets only available on Windows Hybrid Runbook Workers) are described in detail, while Linux equivalents are either not mentioned or explicitly noted as unsupported. There are no examples or guidance for managing Python modules beyond a brief reference, and no mention of Linux-native automation tools or workflows.
Recommendations
- Provide equivalent examples and instructions for Python runbooks, including how to manage Python modules and packages in Azure Automation.
- Clarify which features are Windows-only at the start of each relevant section, and offer Linux alternatives or workarounds where possible.
- Include explicit guidance for Linux Hybrid Runbook Workers, such as supported module types, limitations, and best practices.
- Add examples using cross-platform tools (e.g., Azure CLI) where applicable, or reference them as alternatives to PowerShell.
- Where PowerShell is required, note compatibility with PowerShell Core (pwsh) on Linux/macOS, and highlight any differences.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent
...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation covers Azure Change Tracking and Inventory for both Windows and Linux, but certain sections (notably registry key tracking) are exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to Linux configuration files or directories). Windows terminology and tools (registry keys, Windows services) are discussed in detail, while Linux-specific concepts (daemons, config files) are only briefly mentioned or omitted. Examples and screenshots do not show Linux-specific scenarios, and Windows registry tracking is described extensively without Linux parity.
Recommendations
- Add examples and details for tracking Linux-specific configuration changes, such as monitoring /etc files, systemd service changes, or package manager logs.
- Include screenshots or walkthroughs that demonstrate Linux file change tracking and inventory features.
- Clarify which features are Windows-only and which are cross-platform, to help Linux users understand applicability.
- Provide parity in documentation for Linux daemons and configuration tracking, similar to the Windows registry section.
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
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is featured equally alongside CLI, and is presented after CLI. PowerShell is a Windows-centric tool, but Azure CLI is cross-platform. There are no Linux-specific examples or notes, but the CLI example is sufficient for Linux/macOS users. The prerequisites list both Azure CLI and PowerShell, but do not clarify platform differences or recommend CLI for Linux/macOS users.
Recommendations
- Add a note in the prerequisites section clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider providing a Bash shell example (even if identical to CLI) to reinforce Linux parity.
- Explicitly state that all CLI commands work on Linux/macOS, and PowerShell is optional for those platforms.
- If possible, link to guidance for installing Azure CLI on Linux/macOS.
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 consistently presents PowerShell examples immediately after CLI, and in some cases, Windows-specific installation instructions (e.g., Helm via winget) are given before Linux equivalents. The PowerShell examples are Windows-centric, and the CLI examples are cross-platform but shown first. There are no Linux-specific Azure CLI workarounds or Bash-specific notes beyond Helm installation. The bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- Ensure Linux installation instructions are presented with equal prominence and detail as Windows instructions.
- Add explicit Bash/Linux example tabs for Azure CLI usage, clarifying that CLI commands work on Linux/macOS and in Azure Cloud Shell.
- Consider showing Azure CLI (cross-platform) examples first, and PowerShell (Windows-only) examples second.
- Where PowerShell is mentioned, clarify its Windows focus and suggest CLI for Linux/macOS users.
- Expand Linux/macOS troubleshooting notes where relevant (e.g., permissions, package managers).
Azure App Configuration
Quickstart for adding feature flags to Spring Boot with Azure App Configuration
...p-configuration/quickstart-feature-flag-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). All other instructions, code samples, and tooling are cross-platform (Java, Maven, Spring Boot). No Windows-only tools or patterns are used, and Linux/macOS instructions are present and correct.
Recommendations
- Present environment variable instructions for Linux/macOS first, or group all OS instructions together without preference.
- Explicitly state that all steps are cross-platform unless otherwise noted.
- Consider adding a note that Maven and Spring Boot are fully supported on Linux/macOS.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but PowerShell examples are presented first and in greater detail. The PowerShell section precedes the CLI section, and the CLI section is not referenced in the main portal-based workflow. There are no Linux/macOS-specific examples or notes, but the CLI commands are cross-platform. Portal instructions are platform-neutral, but scripting guidance leans toward Windows/PowerShell.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is primarily for Windows users.
- Add brief notes or links for Bash scripting or Linux/macOS shell usage where relevant.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
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 both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and the note about Azure CLI usage mentions PowerShell first. There are no Windows-only tools or patterns, but the ordering and explicit PowerShell examples indicate a mild Windows bias. All steps are achievable on Linux/macOS, but Windows users may find the examples slightly more tailored to their environment.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them under clear headings for each platform.
- Explicitly state that all steps are cross-platform and supported on Linux/macOS.
- Add a brief note clarifying that Visual Studio Code and Azure CLI are available on Linux/macOS, and that all commands can be run in Bash shells.
- Consider providing a single Bash example with a link to PowerShell syntax, unless both are truly necessary.
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
Summary
The documentation provides instructions and examples primarily using the Azure portal and Azure CLI, with a brief mention of Azure PowerShell. The PowerShell cmdlet is referenced after the CLI example, and no Windows-specific tools or patterns are prioritized. All provided command-line examples use Azure CLI, which is cross-platform. There are no PowerShell-heavy sections, nor are Windows tools or patterns mentioned exclusively or before their Linux equivalents. The documentation is largely neutral, but the PowerShell reference could be seen as a minor 'windows_first' bias.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- If referencing PowerShell, consider also referencing Bash or other Linux-native shells where appropriate.
- Add explicit notes or links for Linux/macOS users if there are platform-specific considerations.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, with PowerShell (Windows) variants shown immediately after Bash. While Linux Bash examples are present, PowerShell examples are given equal prominence, potentially implying Windows is a primary platform. No Linux-specific tools or patterns are missing, but the PowerShell variants may create a perception of Windows-first bias.
Recommendations
- Clearly label Bash and PowerShell examples as 'Linux/macOS' and 'Windows', respectively, to help users identify their relevant platform.
- Consider showing Bash (Linux/macOS) examples first, followed by PowerShell (Windows) examples, to reinforce platform parity.
- Add a brief note explaining that Azure CLI commands work on both Linux/macOS (Bash) and Windows (PowerShell), and clarify any syntax differences.
- If possible, provide a single cross-platform example using Azure CLI, with notes on syntax differences, rather than duplicating commands.
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 given alongside Bash, and in some cases, PowerShell formatting is explicitly called out, which may create a slight Windows bias. The Bash examples are present and correct, but PowerShell examples are shown immediately after, sometimes with more explanation. There is no exclusive use of Windows tools, and Linux users can complete all tasks without friction.
Recommendations
- Ensure Bash examples are always shown first, as Bash is the default shell for most cross-platform CLI users.
- Clearly label PowerShell examples as 'Windows/PowerShell' and Bash as 'Linux/macOS/Bash' to help users quickly identify their relevant section.
- Consider separating Bash and PowerShell examples into distinct tabs or sections, rather than showing both inline, to reduce confusion.
- Review explanations to ensure Bash/Linux usage is not treated as secondary or less detailed.
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 option alongside CLI, and there is a slight Windows-first bias in the ordering and inclusion of PowerShell-specific instructions. No Linux/macOS-specific guidance or troubleshooting is provided, but Azure CLI is cross-platform and included.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a brief note clarifying that Azure PowerShell is primarily used on Windows, while Azure CLI works on Linux/macOS.
- Consider showing Azure CLI examples first, or labeling them as the recommended method for non-Windows environments.
- Include troubleshooting tips for Linux/macOS users, such as file path conventions or Cloud Shell usage.
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. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a main example may indicate a mild Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which may not be necessary for Linux/macOS users. However, the CLI example is present and shown before PowerShell, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding a note that Azure PowerShell is available on Linux/macOS, but CLI is generally recommended for non-Windows environments.
- If possible, provide bash shell scripting examples alongside PowerShell for parity.
- Explicitly mention that all CLI commands work on Linux/macOS, and link to relevant platform-specific installation guides.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance via pivot sections, but Windows-specific information and examples (such as PowerShell commands, Windows parent images, IIS/.NET Framework details, and Windows directory paths) are often presented first or in greater detail. PowerShell examples are included alongside Bash, but Linux-specific tools (e.g., SSH setup, Docker Compose) are sometimes less prominent or appear later. Some sections (like customizing container memory and compute cores) use Windows terminology and tools, and Windows-specific features (like IIS integration) are described in detail, while Linux equivalents are less emphasized.
Recommendations
- Ensure Linux examples and guidance are presented with equal prominence and detail as Windows, especially in shared sections.
- Where PowerShell commands are given, provide equivalent Bash or Linux shell commands first or side-by-side.
- Expand Linux-specific guidance (e.g., parent images, troubleshooting, persistent storage) to match Windows detail.
- Clarify when features or instructions are Windows-only, and provide Linux alternatives or explicit notes when not applicable.
- Review the order of examples and tools to avoid Windows-first bias; alternate or parallelize Windows and Linux instructions.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are prominent and often provided, which can be associated with Windows environments. In some sections, PowerShell is listed before CLI, and PowerShell-specific notes are included. There is no explicit mention of Linux/macOS-specific instructions or shell examples (e.g., Bash), but Azure CLI commands are cross-platform. The documentation does not use Windows-only tools or patterns, and the Azure CLI is included throughout, ensuring Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell examples for token retrieval (e.g., using curl) alongside PowerShell examples.
- Where PowerShell is used, note its availability on Linux/macOS (via PowerShell Core), or provide equivalent Bash/Unix shell instructions.
- Consider listing Azure CLI examples before PowerShell to emphasize cross-platform support.
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, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, in the 'Related content' section, a PowerShell-based guide is referenced before any mention of Linux/CLI alternatives, which may subtly prioritize Windows users. No explicit Windows-only tools, commands, or examples are present in the main content.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or Bash guides for connecting virtual networks, ensuring Linux/macOS users see parity.
- Where PowerShell is referenced, clarify that Azure CLI and portal options are available and provide links to those alternatives.
- Review other cross-referenced documentation to ensure Linux/macOS examples are given equal prominence.
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
windows_first
powershell_heavy
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. Azure PowerShell examples are consistently included and shown alongside Azure CLI, but there is no evidence of Windows-only tools or patterns being prioritized. However, PowerShell is a Windows-centric tool (though available cross-platform), and its inclusion may be seen as a mild Windows bias. The CLI examples are platform-neutral and always present. The order of examples (portal, CLI, PowerShell) puts Windows tools last, not first, so the bias is minimal. No critical steps are Windows-only, and Linux/macOS users can complete all tasks using the Azure portal or CLI.
Recommendations
- Explicitly note that Azure PowerShell is available cross-platform to reduce perceived Windows bias.
- Consider adding Bash shell scripting examples for Azure CLI usage to further emphasize Linux parity.
- Clarify that all CLI examples work on Linux/macOS and Windows equally.
- If possible, link to documentation about installing Azure CLI and Azure PowerShell on Linux/macOS.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Low 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) references to Windows-specific authentication protocols (NTLM, Kerberos) and links to Windows/IIS documentation for troubleshooting, and (2) Windows authentication guidance is provided before any mention of Linux equivalents or generic approaches. No PowerShell or Windows command-line examples are present, and most configuration is described in terms of Azure portal/API, which is cross-platform.
Recommendations
- When referencing authentication troubleshooting, include guidance for Linux-based backend servers (e.g., Apache, NGINX) and generic Kerberos/NTLM configuration.
- Provide links to platform-agnostic authentication documentation or Linux-specific resources alongside Windows/IIS links.
- Clarify that NTLM/Kerberos passthrough is relevant for Windows environments, and suggest alternatives or note limitations for Linux-based backends.
- Ensure troubleshooting steps and examples are not exclusively Windows-focused, and add parity for Linux/macOS 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 largely platform-neutral, focusing on Azure networking concepts and permissions. However, there is a minor bias in the section describing how to restart the Application Gateway after DNS changes, where only Azure PowerShell cmdlets ([Stop-AzApplicationGateway] and [Start-AzApplicationGateway]) are mentioned, with no Azure CLI or Linux/macOS example provided. Azure PowerShell is most commonly used on Windows, so mentioning it exclusively can create friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples alongside PowerShell for operations such as restarting the Application Gateway (e.g., az network application-gateway stop/start).
- When referencing Azure tools or commands, provide both PowerShell and CLI options, or explicitly state that both are supported.
- Ensure that any procedural instructions (such as changing subnets or restarting resources) include cross-platform guidance.
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 guidance for Application Gateway for Containers and includes both Linux and Windows-specific instructions for filtering logs. However, the Windows example (using 'findstr') is presented after the Linux example (using 'grep'), and both are clearly labeled. The overall content is platform-neutral, but there is a slight bias in the explicit separation and labeling of Windows and Linux commands, with the Linux example shown first. No critical troubleshooting steps are Windows-only, and all commands are available for Linux/macOS users.
Recommendations
- Ensure parity by always providing both Linux and Windows command examples side-by-side or in tabs, as done here.
- Consider adding macOS-specific notes if there are any subtle differences (though in this case, Linux commands work on macOS).
- Maintain clear labeling for platform-specific instructions to avoid confusion.
- If possible, provide a cross-platform command (e.g., using kubectl with built-in filtering) to minimize OS-specific steps.
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
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and shows Windows command-line examples first. However, all platforms are covered, and there are no Windows-only tools or missing Linux examples.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows/PowerShell, or group them in tabs for parity.
- Explicitly state that all steps are cross-platform and supported on Windows, macOS, and Linux.
- Where possible, use platform-agnostic instructions or highlight platform differences only when necessary.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides monitoring guidance for Azure App Configuration and includes instructions for using the Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell instructions are presented as a separate tab and explicitly reference 'Windows PowerShell' and opening a Windows PowerShell command window. Additionally, in the Azure CLI section, the phrase 'open a command console application such as Windows PowerShell' is used, listing Windows PowerShell first and not mentioning Linux/macOS terminal alternatives. There are no Linux/macOS-specific examples or explicit parity in tool recommendations.
Recommendations
- In CLI instructions, mention cross-platform terminals (e.g., 'open a terminal such as Windows PowerShell, Command Prompt, or a Bash shell on Linux/macOS').
- Clarify that Azure CLI works on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
- In PowerShell instructions, note that PowerShell Core (pwsh) is available cross-platform and provide examples for both Windows PowerShell and PowerShell Core.
- Consider adding Bash script examples or referencing Bash usage for Linux/macOS users.
- Avoid language that implies Windows tools are the default or only option.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (export), and uses 'cmd' syntax for build/run/curl commands. However, Linux/macOS equivalents are present, and the overall guidance is cross-platform.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Use generic shell syntax for build/run/curl commands (e.g., 'mvn clean package', 'mvn spring-boot:run', 'curl ...') without 'cmd' code block, or clarify that these commands work on all platforms.
- Explicitly state that the instructions are applicable to all supported operating systems.
- Consider using tabs or sections for platform-specific instructions to improve clarity.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (using 'setx' and PowerShell) before Linux/macOS ('export'), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the overall tutorial is cross-platform, with CLI and Maven commands usable on all OSes.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Use neutral language to indicate all OSes are supported, e.g., 'On Windows, use... On Linux/macOS, use...'
- Consider grouping environment variable instructions by platform in a tabbed or clearly separated format.
- Add explicit notes that all CLI commands (Azure CLI, Maven, curl) work on Linux/macOS as well as Windows.
Azure Cache For Redis
Deploy Azure Cache for Redis using Bicep
...s/azure-cache-for-redis/redis-cache-bicep-provision.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific considerations or alternatives to PowerShell, and the CLI examples do not reference Bash or shell scripting, which are common on Linux/macOS. The order of examples is neutral (CLI first), but the presence of PowerShell throughout may create friction for Linux/macOS users unfamiliar with it.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add notes indicating that PowerShell is primarily for Windows users, while CLI works on all platforms.
- Consider including Bash shell scripting examples or links for Linux/macOS users.
- Explicitly state that all tasks can be completed using Azure CLI on 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 sometimes appears before Linux-native alternatives. Azure PowerShell is primarily a Windows tool, and its inclusion as a main option alongside Azure CLI (which is cross-platform) may create friction for Linux/macOS users. There are no Linux-specific examples or explicit mentions of Linux/macOS compatibility, and PowerShell examples are presented in tabs, sometimes before CLI. However, all critical tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Make Azure CLI the default or primary example in all sections, as it is cross-platform and preferred for Linux/macOS users.
- Clearly indicate that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or guidance for Linux/macOS users where PowerShell is mentioned, clarifying that Azure CLI is fully supported.
- Consider removing PowerShell examples from sections where they do not add value for non-Windows users, or move them to secondary position.
- Add a brief section in prerequisites noting that Azure CLI is recommended for Linux/macOS, and provide installation links.