251
Pages Scanned
50
Pages Flagged
251
Changed Pages
19.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-18 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
51 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
missing_linux_example
windows_tools
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-native tools. All examples use PowerShell cmdlets, and certificate creation relies on New-SelfSignedCertificate, a Windows-specific command. There are no Bash, Azure CLI, or Linux/macOS-compatible instructions, making it difficult for non-Windows users to follow the tutorial.
Recommendations
- Provide Azure CLI (az) equivalents for all resource creation and configuration steps.
- Include Bash or cross-platform scripting examples alongside PowerShell.
- For certificate creation, suggest OpenSSL commands for Linux/macOS users.
- Clarify which steps are Windows-only and offer alternatives where possible.
- Add a note about PowerShell Core availability on Linux/macOS, but also highlight Azure CLI as a preferred cross-platform tool.
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 is heavily focused on Windows, with all setup instructions, prerequisites, and examples tailored exclusively to Windows environments. It assumes the use of Windows tools (SignTool.exe, MSI installers, WinGet, PowerShell) and does not provide equivalent instructions or examples for Linux or macOS users. Alternative integrations (GitHub Actions, Azure DevOps, SDK) are mentioned but not documented in detail on this page.
Recommendations
- Add explicit guidance or examples for Linux/macOS users where possible, especially for SDK-based signing or CI integrations.
- Clarify early in the document if SignTool-based integration is Windows-only, and direct Linux/macOS users to supported alternatives (e.g., GitHub Actions, SDK).
- Provide parity in documentation for non-Windows platforms, such as step-by-step guides for using Artifact Signing via GitHub Actions or the SDK on Linux/macOS.
- If certain integrations are Windows-only, clearly label those sections as such and provide links to cross-platform alternatives.
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: Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used throughout, and Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions and screenshots reference Windows directories. The 'Automate with scripts' section lists Azure PowerShell samples before CLI samples, and PowerShell is mentioned as a scripting option, which is more Windows-centric. Linux-specific paths (/home) are mentioned but always after Windows equivalents. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux tools for file upload (such as SCP or SFTP).
Recommendations
- Include Linux/macOS file path examples alongside Windows paths (e.g., /home/site/wwwroot).
- Show both Windows and Linux environment variable usage (e.g., $HOME vs %HOME%).
- Provide Bash shell examples for CLI usage and file uploads (e.g., using SCP/SFTP).
- Clarify that Kudu DebugConsole and FTP are accessible from any OS, and show Linux/macOS usage.
- List Azure CLI samples before PowerShell samples, or present them together.
- Add screenshots or instructions for Linux/macOS users where relevant.
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 patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and references to credential objects (PSCredential) are tied to Windows/PowerShell concepts. There are no examples or guidance for Linux/macOS shell users (e.g., Bash, CLI), nor is there mention of cross-platform alternatives. The Python section is present, but only for runbooks, not for asset management or CLI usage. The portal instructions are platform-neutral, but all scripting is Windows/PowerShell-oriented.
Recommendations
- Add Azure CLI examples for credential asset management (creation, retrieval, deletion) to provide parity for Linux/macOS users.
- Clarify whether credential assets can be managed via Azure CLI or REST API, and provide links or examples if available.
- Explicitly state if PowerShell is required for certain operations, and mention cross-platform PowerShell Core compatibility where relevant.
- Include a note or section for Linux/macOS users, outlining any limitations or alternative approaches.
- Expand Python examples to include asset creation and management, not just credential retrieval in runbooks.
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_tools
windows_first
Summary
The documentation page on enabling end-to-end TLS for Azure Application Gateway is generally platform-neutral in its conceptual explanations. However, there are notable signs of Windows/PowerShell bias: (1) PowerShell is the only automation/configuration tool explicitly referenced for configuring SNI, and the only 'Next steps' link is to a PowerShell-based guide; (2) The only API reference for certificate format support is to a Windows-specific function (PFXImportCertStore); (3) ARM templates are mentioned, but only after PowerShell, and no Linux/macOS CLI (e.g., Azure CLI, Bash) or portal-based workflows are highlighted; (4) There are no Linux/macOS-specific examples or parity guidance.
Recommendations
- Add Azure CLI (cross-platform) examples and references for configuring Application Gateway TLS/SNI settings, alongside or before PowerShell.
- Provide links to documentation for configuring end-to-end TLS using the Azure Portal and/or ARM/Bicep templates, not just PowerShell.
- Reference platform-agnostic certificate handling guidance (e.g., OpenSSL commands for creating/managing PFX files) rather than only linking to Windows API documentation.
- Ensure that 'Next steps' includes links to Linux/macOS-friendly guides (e.g., Azure CLI, Portal) and not just PowerShell.
- Clarify that all configuration steps can be performed from any OS using Azure CLI or Portal, where applicable.
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 Windows-centric workflows, with exclusive use of PowerShell cmdlets and terminology. There is minimal mention of Linux or cross-platform scenarios, and Linux-specific guidance is largely absent. Some features and internal cmdlets are explicitly unavailable on Linux Hybrid Runbook Workers, but the documentation does not provide Linux alternatives or equivalent workflows.
Recommendations
- Add explicit guidance and examples for Linux Hybrid Runbook Workers, including supported module types and any differences in usage.
- Where features are Windows-only (e.g., internal cmdlets), clearly indicate Linux alternatives or workarounds, or link to relevant Linux documentation.
- Include Python and cross-platform module management examples where possible, especially in sections about importing and managing modules.
- Clarify which instructions apply to all platforms and which are Windows-specific, to help Linux/macOS users avoid confusion.
- Provide a summary table or section outlining feature parity and limitations between Windows and Linux Hybrid Runbook Workers.
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_tools
Summary
The documentation provides detailed instructions and code samples for using Azure PowerShell to manage managed identities in API Management, but does not offer equivalent examples for Azure CLI or bash scripting. This creates a bias toward Windows/PowerShell users, as Linux/macOS users are expected to adapt PowerShell commands or use the portal/ARM templates without command-line parity.
Recommendations
- Add Azure CLI examples for all tasks currently demonstrated with Azure PowerShell, including creating and updating API Management instances with managed identities.
- Explicitly mention that Azure CLI can be used on all platforms and provide links to relevant CLI documentation.
- Where possible, show both PowerShell and CLI code blocks side-by-side or with tabs, allowing users to select their preferred environment.
- Clarify in the introduction that both PowerShell and CLI are supported, and link to cross-platform installation guides.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There is no mention of Bash or Linux-specific shell usage, nor are Linux/macOS-specific considerations discussed. The prerequisites list Azure PowerShell alongside Azure CLI, which may confuse Linux/macOS users since PowerShell is less commonly used on those platforms. The CLI example is cross-platform, but the PowerShell example is Windows-centric, and no explicit Linux/macOS parity guidance is provided.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows. Consider linking to installation instructions for Linux/macOS if PowerShell is recommended.
- Provide Bash or shell script examples for the Azure CLI usage, highlighting cross-platform compatibility.
- Explicitly note that Azure CLI is fully supported on Linux/macOS, and that PowerShell is optional.
- Add a short section or note for Linux/macOS users, confirming that all steps can be completed using Azure CLI and the Azure portal.
- If PowerShell is not required, consider demoting its prominence or moving it after the CLI example.
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 examples and concepts (certificate store, C#/.NET code, Windows-MY store, Windows containers) are presented first and in greater detail, with Linux equivalents appearing later or being referenced less directly. Non-Windows languages (Node.js, PHP, Python, Java) are not given explicit code examples, and Linux-specific instructions are sometimes deferred to external documentation. Windows-specific tools and patterns (certificate store, environment variables, user profile loading) are discussed in depth, while Linux guidance is more generic and less comprehensive.
Recommendations
- Provide explicit code examples for Linux environments and popular languages (Node.js, Python, PHP, Java) for loading certificates, rather than referring users to external documentation.
- Present Linux and Windows instructions side-by-side or in parallel tabs to ensure parity and reduce friction for Linux users.
- Expand Linux container guidance to match the detail given for Windows containers, including environment variable usage and file path handling.
- Clarify when instructions are Windows-specific and offer Linux alternatives where possible.
- Add more detailed explanations for Linux certificate handling, including common pitfalls and best practices.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command) are Windows-centric, and Linux/macOS equivalents are not provided. The use of Windows tools and terminology is prevalent, and Linux users are excluded from actionable steps, even in troubleshooting sections.
Recommendations
- Clearly state early in the document that gateway-required virtual network integration is Windows-only, and provide guidance for Linux users to use regional virtual network integration.
- Where troubleshooting steps are given (e.g., Test-NetConnection), offer Linux/macOS equivalents (such as 'nc', 'telnet', or 'curl' commands) for users who may be troubleshooting from a Linux VM.
- Add explicit links or sections for Linux users, directing them to supported alternatives and migration paths.
- Ensure that any example commands or tools are accompanied by cross-platform alternatives where relevant, especially in sections not strictly limited by Windows-only features.
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
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for automating certificate management, but PowerShell is mentioned prominently and linked alongside CLI. Windows tools such as IIS and Certreq.exe are referenced for certificate export, with only brief mention of OpenSSL for Linux/macOS users. Windows-specific tooling is mentioned before Linux alternatives, and links to Windows documentation are provided for certificate export. However, Linux-compatible instructions (OpenSSL) are present, and the overall guidance is not Windows-exclusive.
Recommendations
- Ensure Linux/macOS equivalents are always provided alongside Windows tools (e.g., for certificate export, link to OpenSSL documentation and provide step-by-step OpenSSL instructions before or alongside Windows tools).
- When listing automation options, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is Windows-centric.
- Add explicit notes or sections for Linux/macOS users where Windows tools (IIS, Certreq.exe) are referenced, including alternative methods.
- Provide links to Linux/macOS certificate management documentation and tools.
- Review screenshots and UI instructions to ensure they are not Windows-specific unless the feature is Windows-only.
Medium 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 present throughout, and in some sections (such as 'Add a user-assigned identity'), PowerShell is given its own tab even when Azure CLI is more cross-platform. Additionally, PowerShell is referenced in CLI sections (e.g., 'azurepowershell-interactive' code block for az CLI), and PowerShell is listed as a language example for token retrieval, while Bash or Linux shell equivalents are missing. Azure CLI is present, but PowerShell is sometimes mentioned first or more prominently.
Recommendations
- Ensure that Azure CLI examples use proper shell syntax and are labeled as 'bash' or 'shell' where appropriate, not 'azurepowershell-interactive'.
- Add Bash/Linux shell examples for token retrieval from the REST endpoint, alongside PowerShell.
- Where PowerShell is given its own tab, ensure that Bash or Linux shell equivalents are also provided, especially for scripting scenarios.
- Review the order of examples and tabs to ensure Azure CLI (cross-platform) is listed before PowerShell (Windows-centric) where possible.
- Clarify that Azure CLI is fully supported on Linux/macOS and highlight any limitations or differences if present.
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 across both Windows and Linux platforms. However, there is a noticeable Windows bias: Windows-specific examples (such as directory paths like `D:\home`), tools (Kudu, Web Deploy/MSDeploy), and terminology (IIS, applicationHost.config) are often mentioned first or exclusively. Some settings and explanations default to Windows conventions, with Linux alternatives appearing later or in less detail. Several environment variables and features are described primarily in the context of Windows, with Linux equivalents sometimes missing or less emphasized.
Recommendations
- Ensure Linux examples (e.g., `/home` paths, Linux deployment tools) are presented alongside Windows examples, not just as secondary notes.
- Where Windows tools (e.g., Web Deploy/MSDeploy, Kudu) are discussed, provide clear Linux alternatives (e.g., Oryx, ZIP deploy, FTP, Git) and link to relevant Linux documentation.
- When describing environment variables, show both Windows and Linux values/formats in tables and explanations.
- Avoid defaulting to Windows terminology (e.g., 'applicationHost.config', 'D:\home') without also referencing Linux equivalents.
- Add Linux/macOS-specific troubleshooting tips and configuration notes 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 Azure CLI, Bash, or cross-platform instructions. It also references viewing logs in Excel and Visual Studio-based log converter tools, which are primarily Windows-centric. There are no Linux/macOS-specific or cross-platform alternatives provided for these tasks.
Recommendations
- Add 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 appropriate.
- Mention cross-platform tools for viewing and converting logs, such as jq for JSON processing, csvkit for CSV conversion, or Python scripts.
- Reference open-source or platform-agnostic log analysis tools in addition to Excel and Visual Studio.
- Clearly indicate when a tool or workflow is Windows-only and provide alternatives 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, but there are subtle signs of Windows bias. References to troubleshooting NTLM and Kerberos authentication link to Windows and IIS documentation, and Windows Authentication configuration is mentioned in the context of backend troubleshooting. Additionally, Windows tools and terminology (e.g., Service Principal Name, IIS, Windows Authentication) are referenced before any Linux equivalents, with no mention of Linux authentication mechanisms or troubleshooting guidance for Linux-based backends.
Recommendations
- Add troubleshooting guidance and documentation links for Linux-based authentication mechanisms (such as SPNEGO, mod_auth_kerb, or Samba for NTLM/Kerberos).
- Include examples or references for configuring backend authentication on popular Linux web servers (e.g., Apache, Nginx) alongside IIS/Windows examples.
- When discussing backend logs and authentication, mention both Windows and Linux approaches, and provide links to relevant Linux documentation.
- Ensure that terminology and guidance are inclusive of both Windows and Linux backend environments.
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_tools
Summary
The documentation heavily relies on PowerShell scripts and workflows for migration tasks, with no equivalent examples or guidance for Linux-native tools or scripting languages (e.g., Bash, Python). All migration instructions and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page states applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
- Provide Bash or Python script examples for migrating Automation account assets, or at least mention how Linux users can accomplish the same tasks.
- Include instructions for importing and executing runbooks using Linux-friendly tools or Azure CLI.
- Clarify whether PowerShell Core (pwsh) is supported on Linux for these scripts, and provide guidance for Linux users to install and use PowerShell if required.
- Add explicit notes or sections for Linux/macOS users, highlighting any differences or prerequisites.
- Where possible, offer Azure CLI alternatives to PowerShell commands.
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
windows_tools
Summary
The documentation exclusively demonstrates the configuration using a Windows-based SQL Server VM and recommends SQL Server Management Studio (SSMS), a Windows-only tool, for client connectivity. There are no examples or guidance for Linux-based SQL Server VMs, nor are cross-platform SQL client tools mentioned. The instructions and screenshots focus solely on Windows environments, potentially creating friction for Linux/macOS users.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
- Mention and provide examples for connecting to SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux-compatible SQL clients.
- Clarify that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, if applicable.
- Add screenshots or text-based examples for Linux/macOS users where relevant.
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 and references for both Azure PowerShell and Azure CLI, but PowerShell is presented first and in more detail, with CLI examples being less comprehensive. The 'Next steps' section only links to a PowerShell-based guide, and there is no mention of Linux/macOS-specific tools or workflows. There are no explicit Linux/macOS command-line examples (e.g., using OpenSSL for certificate extraction), and the documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Include Linux/macOS-friendly instructions for certificate extraction and management (e.g., using OpenSSL commands).
- Provide 'Next steps' links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
- Clarify that all configuration steps can be performed on Linux/macOS using Azure CLI or REST API.
- Where possible, add screenshots or instructions for cross-platform tools (e.g., Visual Studio Code, Azure Cloud Shell) rather than assuming a Windows environment.
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 is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided. The guidance assumes the user is using PowerShell locally or in Azure Cloud Shell, and all script downloads are from the PowerShell Gallery. This creates friction for Linux/macOS users who may prefer Bash or Azure CLI, and may not have PowerShell installed or be familiar with its syntax.
Recommendations
- Provide Azure CLI (az) equivalents for all migration steps, including resource ID retrieval, certificate management, and gateway creation.
- Add Bash script examples for downloading and running migration scripts, or clarify if the scripts are cross-platform (PowerShell Core) and can be run on Linux/macOS.
- Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS if PowerShell is required.
- Include guidance for using Azure Cloud Shell (Bash) and Azure CLI for users who do not want to use PowerShell.
- Add a section comparing PowerShell and Azure CLI approaches, and link to Azure CLI documentation for Application Gateway management.
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_tools
windows_first
Summary
The documentation page for Azure Application Gateway v2 shows evidence of Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, and the registration/unregistration steps for the Basic SKU preview use Azure CLI commands that are presented in a PowerShell-like syntax (e.g., Set-AzContext). Additionally, the 'Next steps' section links to a tutorial that is PowerShell-focused. There are no explicit Linux/bash examples or references to Linux-native tools, and Windows/PowerShell patterns are mentioned first and exclusively.
Recommendations
- Provide equivalent bash/Linux shell examples for Azure CLI commands, as Azure CLI is cross-platform.
- Mention that Azure CLI commands can be run in bash or other shells, not just PowerShell.
- Offer migration guidance using Azure CLI or ARM templates, not only PowerShell scripts.
- Ensure tutorials and 'Next steps' include Linux/macOS-friendly instructions and links.
- Clarify that Azure CLI is available on Linux/macOS and provide links to installation guides for those platforms.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation repeatedly references and relies on Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no examples or guidance for users who prefer or require Azure CLI, ARM templates, or other cross-platform tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, especially for configuration migration and public IP retention.
- Explicitly state whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation guidance if so.
- Include ARM/Bicep template examples or REST API alternatives for users who prefer infrastructure-as-code or scripting.
- Add a note clarifying tool requirements and offering alternatives for non-Windows users.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation frequently presents Windows/PowerShell guidance and tools first, with several sections referencing Windows registry settings and PowerShell cmdlets for data management and backup. Linux guidance is present but less detailed, and Linux equivalents for some PowerShell cmdlets are missing. This creates friction for Linux users, who may need to infer or research equivalent steps.
Recommendations
- Provide explicit Linux command-line examples (e.g., using Azure CLI, Bash, or Python) alongside or before Windows/PowerShell examples.
- Include Linux-specific instructions for tasks currently only described with PowerShell cmdlets, such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations.
- Where possible, reference cross-platform tools (e.g., Azure CLI, REST API) rather than Windows-only tools.
- Balance the order of presentation so Linux and Windows guidance are given equal prominence.
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 and Windows-specific tools. All code examples and instructions use PowerShell cmdlets, with no mention of Bash, CLI, or Linux/macOS alternatives. The credential asset creation is described only via the Azure portal or Windows PowerShell, and the runbook example is PowerShell-only. There is no guidance for Linux/macOS users or for using cross-platform tools like Azure CLI.
Recommendations
- Add equivalent examples using Azure CLI and Bash for credential asset creation and runbook authentication.
- Clarify whether Azure Automation supports Python or Bash runbooks for these authentication scenarios, and provide examples if so.
- Mention cross-platform alternatives to PowerShell modules where available, such as Azure CLI or REST API usage.
- Explicitly state any limitations for Linux/macOS users if PowerShell is required, and link to installation instructions for PowerShell Core on non-Windows platforms.
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 is heavily focused on PowerShell and Windows-centric patterns, with nearly all examples, screenshots, and code snippets using PowerShell or Windows tools. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is presented as the primary interface for automation, even though Azure Automation supports Python runbooks and REST API/SDK methods that are cross-platform. Linux users may find it difficult to translate PowerShell-centric instructions to their environment.
Recommendations
- Add bash/CLI examples for starting runbooks and passing parameters, especially for REST API usage.
- Clarify that PowerShell instructions can be run on Linux/macOS via PowerShell Core, and provide guidance for installing PowerShell on those platforms.
- Include Python examples for parameter passing, not just a link to another tutorial.
- Provide explicit instructions for using Azure CLI to start runbooks and assign parameters, highlighting cross-platform compatibility.
- Mention that SDK and REST API methods are platform-agnostic, and show sample usage from Linux/macOS environments.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for managing certificates in Azure Automation heavily emphasizes PowerShell cmdlets and Windows-centric tooling. All detailed examples for certificate creation and management use PowerShell, with no equivalent Bash, CLI, or Linux-native tooling shown. PowerShell is presented first and in depth, while Python examples are limited to certificate retrieval and lack parity for creation or management. There is no mention of Linux/macOS workflows or tools for certificate management in Azure Automation.
Recommendations
- Add Azure CLI examples for certificate creation, retrieval, and management, where possible.
- Provide guidance for Linux/macOS users on preparing and uploading certificates (e.g., using openssl, Azure CLI, or REST API).
- Include Bash or shell script examples for certificate operations, especially for uploading .pfx/.cer files.
- Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide alternatives if not.
- Ensure Python examples cover certificate creation and management, not just retrieval.
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 provides extensive PowerShell-based examples for all major configuration steps, with REST API alternatives, but does not offer Azure CLI or Bash examples. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent command-line workflows, which may create friction for those not using Windows or PowerShell.
Recommendations
- Add Azure CLI examples for all major steps (assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
- Where PowerShell is referenced, clarify that the Azure Az PowerShell module is cross-platform and provide Bash/CLI equivalents where possible.
- Reorder sections or add callouts to make it clear that REST and CLI options are equally supported.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST, and link to relevant CLI documentation.
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, ARM template, or REST API example. While the page covers both Windows and Linux scenarios (e.g., Hybrid Runbook Worker, Update Management), the scripting example is Windows-centric. Additionally, PowerShell is presented as the primary automation method, which may create friction for Linux/macOS users who prefer Bash, Azure CLI, or other tools.
Recommendations
- Add Azure CLI, ARM template, or REST API examples for configuring 'publicNetworkAccess' to ensure Linux/macOS users can follow along without relying on PowerShell.
- Where possible, provide Bash or cross-platform scripting alternatives alongside PowerShell examples.
- Explicitly state that PowerShell is not required and that equivalent actions can be performed using other tools.
- Review other sections for implicit Windows-first language and ensure parity in tool recommendations.
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
missing_linux_example
Summary
The documentation describes Azure Change Tracking and Inventory as supporting both Windows and Linux, but several sections (notably registry key tracking) focus exclusively on Windows features and terminology. There are no Linux-specific examples or equivalent explanations for Linux configuration tracking (such as monitoring /etc files or systemd units). Windows registry keys are listed in detail, while Linux configuration tracking is not covered with similar depth.
Recommendations
- Add examples and explanations for Linux configuration tracking, such as monitoring changes to important files (e.g., /etc/passwd, /etc/ssh/sshd_config) or tracking Linux daemons (systemd services).
- Include a table or section listing typical Linux files and directories that can be monitored, similar to the registry key table for Windows.
- Clarify which features are Windows-only and which are cross-platform, to help Linux users understand applicability.
- Provide Linux-specific screenshots or walkthroughs where possible, especially for file change tracking and inventory.
- Mention Linux equivalents (e.g., systemd units, cron jobs, configuration files) when discussing Windows services and registry keys.
Azure Functions
Quickstart: Create a Durable Functions app that uses the MSSQL storage provider
...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell-based examples for setting up a local SQL Server instance in Docker, and references SQL Server Express as an option for local development specifically on Windows. While it notes PowerShell can be installed on Linux/macOS, all setup commands are given in PowerShell syntax, with no equivalent bash or shell script examples. The SQL Server Express option is described as 'on your local Windows computer', and Windows terminology (e.g., Visual Studio Code prompts, screenshots) is used throughout. Linux/macOS users must adapt the PowerShell commands or use bash equivalents, which are not provided.
Recommendations
- Provide bash/zsh shell script examples for Docker-based SQL Server setup, alongside PowerShell.
- Clarify that SQL Server Express is available on Linux/macOS, or recommend Docker as the cross-platform default.
- Add explicit instructions or links for Linux/macOS users on how to run the setup commands in their native shell.
- Ensure screenshots and UI instructions are not Windows-specific, or add notes for Linux/macOS differences.
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 an equal alternative to Azure CLI, and there is a slight bias in the order of presentation: PowerShell requirements are mentioned alongside CLI requirements, and PowerShell examples are given equal prominence. There are no Linux-specific instructions, but Azure CLI is cross-platform and the examples are not Windows-exclusive. No Windows-only tools or patterns are mentioned, and the documentation does not prevent Linux/macOS users from completing the task.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a brief note clarifying that Azure PowerShell is primarily for Windows, while Azure CLI works on all platforms.
- Consider showing Azure CLI examples first, as it is the default for cross-platform usage.
- If possible, add a short section about using Cloud Shell (which is platform-agnostic) for deployments.
Azure Cache For Redis
Scale an Azure Cache for Redis instance
...n/articles/azure-cache-for-redis/cache-how-to-scale.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides scaling instructions for Azure Cache for Redis using the Azure portal, Azure PowerShell, and Azure CLI. PowerShell examples are given for every operation alongside Azure CLI, and PowerShell is mentioned before CLI in most sections. There are no Linux/macOS-specific examples or explicit references to Linux tools or shell environments. However, Azure CLI is cross-platform and all CLI examples are present, so Linux/macOS users can complete all tasks. The bias is mainly in the prominence and ordering of PowerShell (a Windows-centric tool) and the lack of explicit Linux shell examples.
Recommendations
- Ensure Azure CLI examples are always given equal prominence and ordering alongside PowerShell.
- Add explicit Bash shell examples or notes clarifying that Azure CLI commands work on Linux/macOS.
- Consider mentioning that PowerShell Core is cross-platform, but Azure CLI is the preferred tool for Linux/macOS users.
- Where possible, add sample Bash scripts for automation scenarios.
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 deploying and managing Azure Cache for Redis using Bicep. However, PowerShell examples are given equal prominence to CLI, and there is no explicit mention of Linux/macOS compatibility or alternative shell usage. Azure PowerShell is more commonly used on Windows, and its inclusion without clarifying cross-platform support may create friction for Linux/macOS users. The CLI examples are present and shown first, but the documentation does not explicitly state that Azure CLI is fully cross-platform or recommend it for non-Windows users.
Recommendations
- Add a note clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Explicitly state that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Consider adding a section or callout for Linux/macOS users, highlighting CLI usage and any relevant differences.
- Ensure that examples and instructions do not imply PowerShell is required for non-Windows users.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell throughout, with Bash examples consistently shown first. There are no Windows-specific tools or patterns, and Linux parity is maintained in all command examples. The only minor bias is the ordering of Bash before PowerShell, which favors Linux/macOS users rather than Windows.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or clarify that Bash is shown first for consistency.
- Explicitly state that all CLI commands work equally on Windows, Linux, and macOS.
- If possible, provide a brief note on how to run Azure CLI in different environments (Windows CMD, PowerShell, Bash, etc.) for completeness.
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 included immediately after Bash, and some variable naming (e.g., $apimID) in PowerShell is inconsistent with Bash ($apicObjID), which may cause confusion. There is a slight bias toward Windows/PowerShell users by always providing PowerShell examples, even though Bash is sufficient for cross-platform use.
Recommendations
- Clarify that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash).
- Consider grouping PowerShell examples in a collapsible section or tab, making Bash the default.
- Ensure variable names are consistent between Bash and PowerShell examples to avoid confusion.
- Explicitly state that Bash examples are recommended for cross-platform compatibility.
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 indicate a slight Windows bias. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples in parity with Bash may create a perception of Windows preference.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to avoid implying parity or priority.
- If possible, show Bash examples first, as Bash is the default shell for most Linux/macOS users.
- Clarify that Azure CLI works cross-platform and that Bash examples are suitable for Linux/macOS users.
- Add a brief note explaining that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
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 Azure PowerShell examples for deploying the ARM template. However, PowerShell is highlighted as a primary method alongside CLI, and PowerShell requirements are mentioned before Linux equivalents. There is minor Windows bias in the ordering and prominence of PowerShell, but Linux users can complete all tasks using Azure CLI.
Recommendations
- Ensure Azure CLI examples are presented before PowerShell, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, while PowerShell is primarily for Windows users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell scripting examples for advanced scenarios, if relevant.
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 primarily uses Azure Portal and Azure CLI for instructions, which are cross-platform. However, in the section about disabling routing to a regional gateway, Azure PowerShell is mentioned as an option alongside REST API and Azure CLI, but no Linux-specific tools or shell examples (such as Bash scripts) are provided. Azure CLI is shown first and is cross-platform, but PowerShell is referenced without explicit parity for Linux/macOS users. There are no Windows-only tools or patterns, and no evidence of missing Linux examples for critical tasks.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS, or provide Bash shell script examples where appropriate.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- If referencing PowerShell, consider linking to documentation about using PowerShell Core on Linux/macOS.
- Ensure that any command-line instructions are clearly marked as cross-platform, and avoid implying PowerShell is Windows-only.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
minor_content_duplication
Summary
The documentation provides both Windows and Linux instructions using zone pivots, but there is a tendency to present Windows-specific details and PowerShell examples before or alongside Linux/Bash equivalents. Some sections, such as persistent storage and environment variables, repeat similar instructions for both platforms but often list Windows (and PowerShell) first. There are also Windows-specific tools and patterns (e.g., references to C:\home, IIS, .NET Framework, and PowerShell) that are more prominently described, while Linux equivalents are sometimes less detailed or appear after the Windows sections.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence, alternating which comes first or grouping by platform.
- Where both Bash and PowerShell commands are provided, consider listing Bash (Linux/macOS) first, or clearly labeling both as equally supported.
- Expand Linux-specific details where Windows-specific features (like IIS or .NET Framework) are described, or provide clear notes when a feature is Windows-only.
- Review for minor content duplication (e.g., persistent storage sections) and clarify differences between platforms to avoid confusion.
- In general sections (not under explicit platform pivots), avoid defaulting to Windows terminology (e.g., C:\home) without immediately providing the Linux equivalent (/home).
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 create friction for Linux/macOS users. Additionally, PowerShell examples are given equal prominence to CLI, which can be seen as a mild Windows bias. However, there are no Windows-only tools or patterns, and the CLI example is present and functional for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning that Azure PowerShell can be installed on Linux/macOS, but CLI is generally more common for non-Windows environments.
- If possible, provide Bash shell scripting examples alongside PowerShell, or highlight CLI usage for Linux/macOS users.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is listed alongside CLI in every example. The PowerShell examples are not strictly Windows-only, but the documentation consistently presents PowerShell examples, which may create a perception of Windows bias. However, Linux/macOS users can fully complete all tasks using Azure CLI or portal, and no critical steps are Windows-only.
Recommendations
- Consider listing Azure CLI examples before Azure PowerShell to emphasize cross-platform parity.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
- If possible, provide Bash shell script examples for common migration tasks to further support Linux users.
- Clarify that all steps can be completed on any OS using Azure CLI or portal.
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 for most tasks, but PowerShell examples are included throughout, which is primarily a Windows tool. In several sections, PowerShell examples are presented alongside CLI, sometimes before or at parity with CLI. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for PowerShell commands. However, the main workflow is based on Azure CLI, which is cross-platform, and all critical steps can be completed using CLI. PowerShell is offered as an alternative, but not exclusively.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider grouping PowerShell examples in a separate section or tab labeled 'Windows/PowerShell' to avoid confusion.
- Add explicit notes indicating that all CLI commands are fully supported on Linux/macOS.
- If possible, mention that PowerShell Core is available cross-platform, but usage is less common on Linux/macOS.
- Ensure that CLI examples are always shown first, with PowerShell as an optional alternative.
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 examples for log filtering. However, the Windows example (using 'findstr') is presented immediately after the Linux example (using 'grep'), and both are given equal prominence. The rest of the documentation uses cross-platform tools (kubectl, helm) and shell syntax, with no Windows-specific tools or patterns dominating. The bias is minor, mainly in the order and presence of Windows-specific CLI examples.
Recommendations
- Ensure that Linux and Windows examples are given equal prominence, possibly by using tabbed sections or clear separation.
- Consider presenting Linux examples first, as Kubernetes and container workloads are most commonly run on Linux.
- Add explicit macOS notes if any commands differ, though in this case they do not.
- Clarify that all commands are cross-platform except for log filtering, and provide guidance for PowerShell users if relevant.
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
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is featured equally or sometimes first. Helm installation instructions are split by Windows and Linux, but Windows is listed first and only the Windows-specific 'winget' tool is mentioned, while Linux gets a generic curl install. There are no Bash or Linux-native alternatives for Azure CLI steps, and PowerShell is referenced as a primary tool, which is more Windows-centric. Some minor friction exists for Linux users due to Windows-first ordering and lack of explicit Bash examples for Azure CLI commands.
Recommendations
- List Linux installation instructions before Windows, or at least equally.
- Add explicit Bash examples for Azure CLI commands where possible, especially for steps involving environment variables and scripting.
- Mention Linux package managers (e.g., apt, yum, snap) for Helm installation alongside curl.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash or Zsh shells.
- Consider adding a note that Azure PowerShell is available on Linux/macOS, but Bash is the typical shell for Linux users.
- Where possible, provide Bash script examples for multi-step Azure CLI operations.
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
minor_windows_tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific commands (setx, PowerShell) with more detailed instructions (e.g., 'restart the command prompt') than for Linux/macOS. However, Linux/macOS instructions are present and complete. The use of Visual Studio Code is highlighted as cross-platform, and all core steps (Maven, Java, Azure Portal) are OS-agnostic.
Recommendations
- Present environment variable instructions for Linux/macOS before or alongside Windows examples, or use tabs to separate OS instructions.
- Provide equal detail for Linux/macOS steps (e.g., mention restarting the terminal if needed, how to check env vars).
- Where possible, use OS-neutral language and avoid implying Windows as the default (e.g., 'If you use Windows...' instead of listing Windows first).
- Consider using tabbed code blocks for OS-specific commands to improve clarity and parity.
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 instructions for Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. In the CLI section, Windows PowerShell is mentioned first as an example of a command console application, and the PowerShell section exclusively references Windows PowerShell, with no mention of Bash or Linux/macOS-specific shells. The CLI instructions do not clarify that Bash or other shells are equally supported, and screenshots and step-by-step instructions are portal-centric, which is cross-platform but may implicitly favor Windows users by referencing Windows PowerShell more prominently.
Recommendations
- Clarify that Azure CLI commands work equally well in Bash, zsh, or other Linux/macOS shells, not just Windows PowerShell.
- In the CLI section, mention Bash or other Linux/macOS shells alongside Windows PowerShell when referencing command console applications.
- Add explicit instructions or notes for Linux/macOS users where relevant, such as opening a terminal and running Azure CLI commands.
- Consider providing PowerShell Core (pwsh) examples, which are cross-platform, or note that PowerShell examples are for Windows unless otherwise specified.
- Ensure screenshots and instructions do not assume Windows-specific UI elements unless necessary.
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
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific commands (setx, PowerShell syntax) alongside bash. All major steps are cross-platform, but Windows instructions are presented first, which may create minor friction for Linux/macOS users.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows/PowerShell, or group them equally.
- Clarify that all commands are cross-platform and ensure parity in example order.
- Consider using tabbed sections for OS-specific instructions to reduce clutter and bias.
- Explicitly mention that Maven and Java instructions are OS-agnostic.
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, PowerShell) before Linux/macOS (bash), and uses Windows terminology (command prompt) in build/run steps. However, Linux/macOS equivalents are included and the examples are cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group them equally.
- Use 'terminal' or 'shell' instead of 'command prompt' to be platform-neutral.
- Clarify that Maven and curl commands are cross-platform and can be run on any OS.
- Consider adding explicit notes that all steps are supported on Linux/macOS unless otherwise stated.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides comprehensive coverage of Azure Functions app settings, with examples and explanations for both Windows and Linux. However, there are minor signs of Windows bias: some settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are marked as Windows-only, and Windows-style paths (e.g., %HOME%\typescript) are used in examples without Linux equivalents. PowerShell-specific settings are detailed, and Azure PowerShell is mentioned as a recommended tool for managing settings, with no equivalent Linux CLI emphasis. In some cases, Windows terminology or tools are referenced before Linux alternatives.
Recommendations
- For settings with OS-specific values (e.g., WEBSITE_TIME_ZONE, AzureWebJobs_TypeScriptPath), provide both Windows and Linux examples side-by-side.
- When referencing tools for managing app settings, mention Azure CLI equally with Azure PowerShell, and provide cross-platform command examples.
- Where Windows paths or conventions are shown, add Linux equivalents (e.g., /home/typescript).
- For PowerShell-specific settings, clarify their scope and provide parity for other language runtimes where applicable.
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 (cmd 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 Maven and curl examples suitable for all OSes.
Recommendations
- Present Linux/macOS export commands before or alongside Windows commands to avoid Windows-first ordering.
- Clarify that all CLI commands (Azure CLI, Maven, curl) work identically on Linux/macOS.
- Consider grouping environment variable instructions by OS, or using tabs for Windows, Linux, and macOS.
- Add explicit notes that Visual Studio Code and Java tooling are cross-platform.
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. Portal instructions are generic and platform-agnostic, but scripting sections show a mild Windows bias by prioritizing PowerShell and not mentioning Bash or Linux-specific CLI nuances. There are no Linux-specific examples or notes about CLI usage on Linux/macOS, but CLI coverage is present.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Add notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is primarily for Windows users.
- Consider including Bash shell script examples or highlighting any OS-specific considerations for CLI usage.
- Explicitly state that all portal instructions are OS-agnostic and accessible from any browser.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for running C# Azure Functions in an isolated worker process. However, there are several instances where Windows-specific tools, commands, and examples are mentioned first or exclusively, such as PowerShell and Visual Studio, with Linux equivalents appearing later or less prominently. Some CLI commands and deployment instructions are shown for both platforms, but Windows tools (Visual Studio, PowerShell) are often listed before Linux alternatives (VS Code, Azure CLI). Additionally, certain sections (e.g., ReadyToRun, debugging, deployment requirements) provide Windows-specific guidance before Linux, and PowerShell is referenced as a primary automation tool.
Recommendations
- Ensure Linux and macOS examples are given equal prominence and ordering alongside Windows examples, especially in 'Getting Started', deployment, and debugging sections.
- Where PowerShell or Visual Studio are mentioned, always provide equivalent Azure CLI and VS Code instructions, and consider listing them first or in parallel.
- Add explicit Linux/macOS command-line examples for all critical operations (e.g., deployment, debugging, performance optimizations).
- Clarify any platform-specific limitations or differences, and link to Linux/macOS-specific guides where available.
- Review the ordering of sections and examples to avoid implicit Windows-first bias.