250
Pages Scanned
51
Pages Flagged
250
Changed Pages
20.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-19 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 250
Files Completed: 250
Problematic Pages
52 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored to Windows environments. Installation steps rely on Windows Package Manager (winget), MSI installers, and PowerShell commands. There are no Linux/macOS equivalents or instructions for using Artifact Signing with non-Windows signing tools. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their setup is not detailed, and Windows is prioritized throughout.
Recommendations
- Add explicit instructions and examples for using Artifact Signing on Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or Linux equivalents if available).
- Provide parity for installation steps, such as using package managers like apt, yum, or Homebrew, and shell script examples instead of only PowerShell.
- Clarify which integrations are cross-platform and provide detailed setup guides for GitHub Actions, Azure DevOps, and SDK usage on Linux/macOS.
- Mention any limitations or Windows-only aspects up front, and link to Linux/macOS guidance where applicable.
Create Pull Request
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 examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to Azure CLI, but no Linux/macOS-specific shell examples (e.g., Bash) or guidance are provided. The prerequisites list both Azure CLI and Azure PowerShell, but does not clarify that PowerShell is cross-platform or offer Linux-specific instructions. The portal instructions are platform-neutral, but the command-line guidance is biased toward Windows/PowerShell users.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide installation instructions for Linux/macOS.
- Add Bash shell examples for Azure CLI usage, highlighting Linux/macOS compatibility.
- Explicitly state that all Azure CLI commands are supported on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
- Consider mentioning alternative shells (e.g., zsh, fish) for Linux/macOS users where relevant.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell-based examples for all key configuration steps, with REST API alternatives, but does not include Azure CLI or bash examples. PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users who typically use Azure CLI or bash. References to PowerShell modules and cmdlets are frequent and precede any mention of other tools.
Recommendations
- Add Azure CLI examples for all major configuration steps, including assigning managed identities, configuring Key Vault access policies, and updating Automation account encryption settings.
- Where PowerShell is referenced, provide equivalent bash/CLI commands or scripts.
- Explicitly mention that PowerShell Core is cross-platform if PowerShell must be used, and provide installation guidance for non-Windows users.
- Reorder sections or provide parallel examples so that Linux/macOS-friendly tools (like Azure CLI) are not secondary.
- Clarify in prerequisites that all steps can be performed from Linux/macOS using CLI or REST, not just PowerShell.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., data retention, backup, DSC node removal, runbook export), while Linux equivalents are missing or only briefly referenced. Linux guidance is present for TLS configuration, but not for other management or export tasks.
Recommendations
- Provide Linux/CLI/REST API equivalents for PowerShell cmdlets such as Unregister-AzAutomationDscNode, Get-AzAutomationRunbookContent, and Export-AzAutomationDscConfiguration.
- When describing export or backup procedures, include az CLI or REST API examples alongside PowerShell.
- In tables and lists, present Linux and Windows options with equal prominence, or group them together rather than listing Windows first.
- Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for Linux users where possible.
- Add explicit Linux examples for asset management and DSC node removal, or link to relevant Linux documentation.
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows, with most examples, instructions, and screenshots referencing Windows tools, cmdlets, and portal UI. Linux Hybrid Runbook Worker support is mentioned only to note limitations, and there are no Linux-specific examples or guidance. Python module support is referenced but not detailed. The internal cmdlets and module management instructions are Windows-oriented, and Linux users are left without parity in critical areas.
Recommendations
- Add explicit instructions and examples for managing modules on Linux Hybrid Runbook Workers, including any supported workflows or limitations.
- Provide parity for module import, update, and deletion using Linux tools (e.g., Bash, Azure CLI) where possible.
- Include Linux/macOS-specific guidance for authoring and packaging custom modules, noting any differences in file structure or compatibility.
- Clarify which features are Windows-only and which are cross-platform, and provide links or references to Linux-specific documentation where available.
- Expand the Python module section to include more details and examples, especially for Linux users.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are several areas where Windows tools, commands, or patterns are mentioned first or exclusively. Windows-specific configuration (such as .NET Framework settings) is often described before Linux equivalents, and some CLI examples default to Windows-centric syntax or ordering. Azure PowerShell is listed as a primary provisioning method, while Linux-native tools (like Bash or shell scripting) are not highlighted. In some sections, Linux-specific nuances are only mentioned in passing or as secondary notes.
Recommendations
- Ensure that all command-line examples (especially for deployment, configuration, and debugging) include both Windows and Linux syntax, with equal prominence.
- When listing tools or provisioning methods (e.g., Azure CLI, PowerShell), alternate the order or provide parallel examples for both Windows and Linux users.
- Where PowerShell is referenced, provide Bash or shell script equivalents for Linux/macOS users.
- In sections where Windows-specific configuration is discussed (such as .NET Framework or ReadyToRun), ensure Linux configuration is equally detailed and not relegated to a secondary position.
- Add explicit Linux/macOS troubleshooting and environment setup guidance where relevant, especially for local development and debugging.
- Review the order of presentation in tables and lists to avoid consistently putting Windows tools or workflows first.
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
windows_first
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 (which is cross-platform and preferred by many Linux/macOS users). PowerShell is a Windows-native tool (though cross-platform now, but less common on Linux/macOS), and the documentation refers to installing and using it without mentioning CLI alternatives. The PowerShell sections are presented before ARM template examples, and there are no Bash or Azure CLI equivalents. This creates friction for Linux/macOS users who may not have or want to use PowerShell.
Recommendations
- Add Azure CLI examples for all tasks currently demonstrated with PowerShell, including creating resource groups, managed identities, and API Management instances.
- Explicitly mention that Azure CLI can be used as an alternative to PowerShell, and link to relevant Azure CLI documentation.
- Consider presenting Azure CLI and PowerShell examples side-by-side or in tabs, so users can easily select their preferred tool.
- Clarify that ARM templates are platform-agnostic and can be deployed from any OS, but still provide imperative (CLI) examples for parity.
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 for Azure App Service, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, and Linux/macOS equivalents are not provided. The use of Windows tools and commands without Linux alternatives creates friction for cross-platform users, especially those troubleshooting from Linux VMs or environments.
Recommendations
- Clarify early that the feature is Windows-only for App Service, but troubleshooting steps may apply to cross-platform scenarios (e.g., VMs in the virtual network).
- Provide Linux/macOS equivalents for troubleshooting commands, such as using 'nc' (netcat), 'telnet', or 'ss' for TCP connectivity, and 'lsof' or 'netstat' for port listening.
- When referencing PowerShell commands, add a note or example for Linux users (e.g., 'On Linux, use nc hostname port' or 'ss -ltn').
- Ensure that any guidance for VM-level troubleshooting is platform-neutral or includes both Windows and Linux/macOS instructions.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the section on Hybrid Connections requires installation of Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users who may need to access on-premises resources via Hybrid Connections. No PowerShell-heavy or Windows-first ordering is observed, but the lack of Linux guidance for Hybrid Connections is notable.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest Linux-friendly alternatives for outbound connectivity (such as VPN, ExpressRoute, or other Azure features).
- Where tools or features are Windows-specific, add a note about platform limitations and link to relevant Linux/macOS documentation or guidance.
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
missing_linux_example
Summary
The documentation page provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux platforms. However, there are several instances where Windows-specific tools, paths, and terminology are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and site extension feeds. Some settings and examples use Windows conventions (e.g., `%HOME%`, `.dll` extensions, references to `applicationHost.config`) before or instead of Linux equivalents. While Linux-specific variables and sections are present (e.g., Oryx build automation, Linux container settings), Windows terminology and examples often appear first or are more detailed, and some Linux-specific settings lack equivalent examples or explanations.
Recommendations
- Ensure Linux paths and conventions (e.g., `/home`, `/etc`) are mentioned alongside Windows paths wherever relevant.
- Provide Linux-specific examples and explanations for settings that currently only reference Windows tools or patterns (e.g., Web Deploy, site extensions, logging paths).
- Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
- Clarify when a setting is Windows-only or Linux-only, and provide parity where possible.
- Expand Linux build automation and deployment examples to match the detail provided for Windows/Kudu.
- Avoid referencing Windows tools (e.g., IIS, MSDeploy) in general sections unless explicitly noting their platform specificity.
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 presents Windows-specific certificate loading methods and code examples first, with detailed instructions for accessing certificates via the Windows certificate store in C# and Java. Linux guidance is limited to brief C# file-loading examples, and other languages (Node.js, PHP, Python, Java) are referenced only generically, without concrete Linux examples. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized throughout, while Linux equivalents are less detailed and appear later in the document.
Recommendations
- Provide concrete Linux examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided.
- Include Linux-specific guidance earlier in the document, alongside Windows instructions, to improve parity.
- Expand on Linux container certificate handling, including sample code for accessing certificates via environment variables.
- Clarify differences in certificate management between Windows and Linux, and offer troubleshooting tips for Linux users.
- Balance the order of presentation so Linux and Windows instructions are equally prominent.
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 Azure PowerShell examples for RBAC permissions, but PowerShell is presented as a primary automation option alongside CLI. In the certificate export section, Windows-specific tools (IIS and Certreq.exe) are mentioned for generating/exporting certificates, with only a brief reference to OpenSSL for Linux/macOS users. Windows tools and patterns are referenced before Linux equivalents, and links to Windows documentation are provided for certificate export. There are no Linux/macOS-specific walkthroughs or screenshots, and PowerShell is given equal prominence to CLI for automation, despite CLI being more cross-platform.
Recommendations
- Add explicit Linux/macOS instructions and examples for certificate generation and export, including OpenSSL commands and troubleshooting.
- Provide links to Linux/macOS documentation for certificate management, not just Windows Server docs.
- Present Azure CLI as the primary automation method, with PowerShell as an alternative for Windows users.
- Include Linux/macOS screenshots or clarify that the portal experience is identical across platforms.
- Mention cross-platform tools (like OpenSSL) before Windows-specific tools in relevant sections.
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 example for Azure CLI, Bash, or other cross-platform tools. It also references tools like Excel and Visual Studio for log analysis and conversion, which are primarily Windows-centric, without mentioning Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-specific tools.
Recommendations
- Add Azure CLI and/or Azure Cloud Shell examples for enabling diagnostic logging, as these are cross-platform and widely used by Linux/macOS users.
- When mentioning log analysis, include Linux/macOS-friendly tools such as jq, csvkit, or open-source alternatives to Excel (e.g., LibreOffice Calc), and note that Power BI has web-based options.
- For log conversion, reference cross-platform scripting options (e.g., Python scripts) or provide guidance for users not using Visual Studio.
- Where possible, present examples in a platform-neutral way or provide both Windows and Linux/macOS command-line options.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and IIS configuration, without mentioning Linux equivalents or alternatives. Additionally, Windows tools and patterns are mentioned first or exclusively in these troubleshooting sections, potentially creating friction for Linux users.
Recommendations
- When discussing authentication troubleshooting (NTLM/Kerberos), add references or guidance for Linux-based backend servers, such as Samba, Apache, or NGINX configurations for Kerberos.
- Include links or notes about how to review logs or configure authentication on Linux web servers (e.g., Apache, NGINX) in addition to IIS.
- Clarify that NTLM is Windows-specific, but Kerberos can be used cross-platform, and provide Linux guidance where applicable.
- Ensure troubleshooting steps are not solely focused on Windows tools and documentation.
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 biased toward Windows/PowerShell environments. All migration scripts, examples, and instructions are exclusively provided for Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all code samples are PowerShell cmdlets. There is no parity for Linux/macOS users who prefer Azure CLI or Bash scripting, nor is there guidance for running these scripts in cross-platform environments.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration.
- Add Bash shell examples for script installation and execution, especially for users on Linux/macOS.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide instructions for both environments.
- Mention any limitations or requirements for Linux/macOS users, such as PowerShell Core compatibility or prerequisites.
- Consider linking to cross-platform migration tools or providing guidance for users who do not have access to PowerShell.
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 for mutual authentication on Azure Application Gateway primarily using PowerShell, with CLI examples included but PowerShell shown first and in more detail. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash scripting, OpenSSL usage for certificate extraction), and the 'Next steps' section directs users to a PowerShell-focused guide. This may create friction for Linux/macOS users who do not use PowerShell as their primary tool.
Recommendations
- Ensure all configuration examples are provided for both Azure PowerShell and Azure CLI, and consider showing CLI (cross-platform) examples first or equally.
- Add Linux/macOS-specific instructions or examples for certificate extraction and management (e.g., using OpenSSL commands).
- In 'Next steps', provide links to both PowerShell and CLI-based guides for mutual authentication setup.
- Clarify that all features can be configured using CLI and REST API, and provide parity in documentation depth for these methods.
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 mild Windows bias, primarily through the use of Azure PowerShell scripts for migration and registration examples, and by referencing PowerShell gallery resources. While Azure CLI commands are shown for preview registration, they use PowerShell cmdlets, which may confuse Linux/macOS users. There are no explicit Linux/macOS examples or mentions of Bash or cross-platform CLI usage. The 'Next steps' section links to a PowerShell-based tutorial, and the migration script is PowerShell-only, creating friction for non-Windows users.
Recommendations
- Provide Bash/Azure CLI examples alongside PowerShell for registration, migration, and management tasks.
- Clarify whether the PowerShell migration script can be run on Linux/macOS (using PowerShell Core), or provide a cross-platform alternative.
- Link to tutorials or guides that use Azure CLI or ARM templates for deployment and migration.
- Explicitly mention cross-platform compatibility where applicable, and avoid implying PowerShell is the only supported method.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page repeatedly references Azure PowerShell scripts as the primary migration tooling, without mentioning equivalent CLI (az) or Bash/Linux shell options. All migration automation examples and guidance are PowerShell-centric, and there are no Linux/macOS-friendly alternatives or examples. This creates friction for users on non-Windows platforms.
Recommendations
- Add Azure CLI (az) examples or scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly mention whether migration scripts can be run cross-platform (e.g., PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
- Provide Bash or shell script alternatives where possible, or clarify limitations.
- List both PowerShell and CLI options side-by-side in migration instructions to ensure parity.
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 demonstrates notable Windows bias. The SQL Server VM is created using a Windows Server image, and the only SQL client example provided is SQL Server Management Studio (SSMS), a Windows-only tool. There are no instructions or examples for Linux-based SQL Server VMs or for connecting from Linux/macOS clients (e.g., sqlcmd, Azure Data Studio). The documentation assumes Windows environments throughout, creating friction for Linux/macOS users.
Recommendations
- Provide instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2022).
- Include examples for connecting to the SQL Server via cross-platform tools such as sqlcmd or Azure Data Studio.
- Mention Linux/macOS alternatives for SQL client connectivity and clarify any differences in configuration.
- Add screenshots or CLI steps relevant to Linux environments where appropriate.
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 is generally platform-neutral in its conceptual explanation of TLS on Azure Application Gateway. However, the 'Next steps' section directs users specifically to a PowerShell-based configuration guide, implying Windows as the primary platform for hands-on tasks. There is no mention of Linux/macOS CLI or Azure Portal equivalents in the 'Next steps', and PowerShell is referenced before any cross-platform alternatives.
Recommendations
- Add links to equivalent configuration guides using Azure CLI (which is cross-platform) and Azure Portal UI.
- Mention that PowerShell is available on Linux/macOS, but also provide Azure CLI examples for Linux users.
- In 'Next steps', list cross-platform options (Azure CLI, Portal) before or alongside PowerShell.
- Ensure that any referenced tools or commands are not Windows-exclusive, or provide Linux/macOS alternatives.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) for all steps, including certificate creation. No Bash, Azure CLI, or Linux/macOS-compatible instructions are provided. The prerequisites and all examples assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all steps, especially resource creation and configuration.
- For certificate creation, include Linux/macOS-compatible commands (e.g., using OpenSSL) alongside PowerShell examples.
- Clarify that Azure PowerShell can be used cross-platform, but highlight any Windows-only steps and offer alternatives.
- Add notes or sections for Linux/macOS users, including how to install Azure PowerShell or Azure CLI on their platforms.
- Consider reordering examples so that cross-platform tools (Azure CLI, OpenSSL) are shown first or alongside PowerShell.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page provides disaster recovery guidance for Azure Automation, which applies to both Linux and Windows VMs. However, all migration examples and scripts are PowerShell-based, with no mention of Bash, Python, or cross-platform alternatives. Instructions and links for Hybrid Runbook Worker installation use Windows tabs/paths first, and Linux-specific guidance is not surfaced or referenced. The documentation assumes PowerShell as the default tooling, which creates friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (pwsh) is fully supported on Linux/macOS for these tasks.
- Add explicit Linux/macOS instructions and examples for Hybrid Runbook Worker installation and management.
- Mention PowerShell Core compatibility and installation steps for Linux/macOS users, including any prerequisites.
- Where possible, offer ARM template or REST API alternatives for migration tasks.
- Ensure that documentation tabs or sections show Linux examples first or equally alongside Windows examples.
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 is heavily focused on PowerShell and Windows-specific tools and patterns. All code examples and module references are PowerShell-based, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The process for creating credential assets and authenticating to Azure is described only using PowerShell cmdlets, and the only automation script provided is a PowerShell workflow. There are no Linux/macOS-specific instructions or examples.
Recommendations
- Add equivalent examples using Azure CLI (az) for credential management and authentication, which are cross-platform.
- Provide Bash or Python runbook examples for Azure Automation, or clarify if only PowerShell runbooks are supported.
- Explicitly state platform limitations if Azure Automation only supports PowerShell for these scenarios.
- Mention cross-platform PowerShell (pwsh) if the instructions are compatible, or clarify if only Windows PowerShell is supported.
- List Linux/macOS prerequisites or alternatives where possible, such as using Azure CLI to manage credentials.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, without offering an equivalent CLI or ARM template example for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, creating friction for non-Windows users. However, the overall guidance is platform-neutral, and Azure Automation supports both Windows and Linux Hybrid Runbook Workers.
Recommendations
- Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' property, alongside the PowerShell example.
- Explicitly mention that the configuration steps can be performed from any OS using Azure CLI, REST API, or portal.
- Where PowerShell is used, provide cross-platform alternatives or clarify if the step is Windows-specific.
- Ensure screenshots and instructions reference both Windows and Linux scenarios where applicable.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily focuses on PowerShell examples and Windows-centric tooling, with nearly all code snippets, parameter handling, and automation workflows demonstrated using PowerShell or PowerShell Workflow. There is minimal coverage of Python runbooks, and no examples or guidance are provided for Linux/macOS users on how to interact with Azure Automation runbooks using native shell tools (e.g., Bash, CLI), nor is there parity in examples for starting runbooks from Linux environments. The REST API and SDK sections are platform-neutral, but the practical, step-by-step guidance is overwhelmingly Windows/PowerShell oriented.
Recommendations
- Add examples for starting runbooks using Azure CLI (az automation runbook start) from Bash or Linux/macOS terminals.
- Provide sample Bash scripts for passing parameters to runbooks, including JSON parameter handling.
- Expand the Python runbook section with more detailed examples, including parameter parsing and invocation from Linux/macOS.
- Explicitly mention cross-platform alternatives to PowerShell for Linux/macOS users, and clarify any limitations.
- Include notes or tables summarizing which features/tools are available on Windows, Linux, and macOS.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and Windows-centric tooling for certificate management in Azure Automation. All detailed command-line examples are PowerShell-based, with no mention of Linux shell (bash) or cross-platform CLI equivalents. PowerShell examples are presented first and are the only option for tasks like certificate creation and deployment, while Python examples are limited to certificate retrieval in runbooks. There are no Linux/macOS-specific instructions or examples for certificate management outside of Python runbooks.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide cross-platform parity.
- Mention whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and clarify any limitations.
- Include bash or shell script examples for uploading certificates, or reference relevant Azure CLI documentation.
- Explicitly state if certain tasks are only possible via PowerShell and provide guidance for Linux/macOS users.
- Reorder examples so that cross-platform solutions (Azure CLI, REST API) are presented alongside or before PowerShell.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tools and patterns. All credential management examples and cmdlets are PowerShell-based, with explicit references to Windows PowerShell and PSCredential objects. The only non-Windows section is for Python runbooks, but there are no Linux shell (bash) or cross-platform CLI examples. The portal instructions are platform-neutral, but all scripting and automation guidance assumes Windows/PowerShell environments.
Recommendations
- Add examples using Azure CLI (az) for credential asset management, which is cross-platform.
- Clarify whether credential assets can be managed or accessed from Linux/macOS environments, and provide guidance if possible.
- Include bash or shell scripting examples where applicable, or explicitly state limitations if PowerShell is required.
- Mention PowerShell Core (pwsh) compatibility for cross-platform users, and provide examples using pwsh if supported.
- Add a section summarizing platform support for Azure Automation credential assets, including any Linux/macOS limitations.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for 'What's New in Azure Automation' demonstrates a moderate bias towards Windows and PowerShell. Most examples and feature announcements reference PowerShell runbooks, often before Python equivalents. PowerShell versions and module retirements are highlighted more frequently and in greater detail. While Linux is mentioned (e.g., Hybrid Runbook Worker support for Windows and Linux), examples and guidance are predominantly PowerShell-focused, and Windows terminology appears first in several places.
Recommendations
- Ensure that Python runbook updates and examples are given equal prominence alongside PowerShell announcements.
- When listing supported platforms (Windows and Linux), alternate the order or explicitly state parity.
- Provide more examples or links for Linux-specific scenarios, such as shell scripting or Linux tools in Automation.
- Include guidance or references for managing Automation assets from Linux/macOS environments (e.g., using Azure CLI or Python).
- Highlight Python package management and troubleshooting in parity with PowerShell module updates.
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 page exhibits moderate Windows bias. PowerShell is used for all local database setup commands, and Windows-centric tools (SQL Server Express) are mentioned before their Linux equivalents. While Docker is used for cross-platform database hosting, only PowerShell scripts are provided for setup, with no Bash or Linux-specific instructions. The troubleshooting section also assumes familiarity with Windows/Docker Desktop. Linux/macOS users must adapt the PowerShell commands or use alternatives, which creates friction.
Recommendations
- Provide equivalent Bash shell commands for Docker-based SQL Server setup, especially for Linux/macOS users.
- Mention Linux-native SQL Server installation options (e.g., apt/yum install for SQL Server tools) alongside SQL Server Express.
- Clarify that PowerShell commands are cross-platform, but offer Bash alternatives for common scenarios.
- Add explicit instructions or links for Linux/macOS users to install and use sqlcmd and Docker.
- Reorder sections to avoid Windows-first bias (e.g., mention Docker-based SQL Server before SQL Server Express).
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 both Windows and Linux support for Azure Change Tracking and Inventory, but several sections show Windows bias. Registry key tracking is exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to configuration files or systemd units). Windows terminology and tools (registry, Windows services) are mentioned first or exclusively, while Linux-specific examples (e.g., tracking changes to /etc files or Linux daemons) are not provided. There are no PowerShell-heavy examples, but the lack of Linux-specific guidance and examples creates friction for Linux users.
Recommendations
- Add examples and explanations for tracking Linux-specific changes, such as monitoring /etc configuration files, systemd service units, or other relevant Linux artifacts.
- Provide parity in examples: when showing Windows registry tracking, also show how Linux configuration changes are tracked.
- Clarify which features are Windows-only and which are cross-platform, to set user expectations.
- Include screenshots or walkthroughs for Linux scenarios, not just Windows.
- Mention Linux tools and terminology (e.g., systemd, init scripts, config files) alongside Windows tools.
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 Windows-centric and is presented alongside CLI in all code tabs. The PowerShell examples are not strictly necessary for Linux/macOS users, and their inclusion may suggest a Windows-first mindset. However, the CLI examples are always present and appear before PowerShell, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and Linux-specific guidance is not missing.
Recommendations
- Consider clarifying that Azure PowerShell is available cross-platform, but Azure CLI is generally preferred for Linux/macOS users.
- Optionally, reorder code tabs to show Azure CLI before Azure PowerShell, emphasizing CLI as the default for non-Windows environments.
- Add a brief note in the prerequisites or migration steps indicating that all operations can be performed from Linux/macOS using Azure CLI.
- If possible, provide explicit guidance for Linux/macOS users in troubleshooting or post-migration sections (e.g., how to verify connectivity using Linux tools).
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 filtering logs. However, the Windows example (using 'findstr') is presented immediately after the Linux example (using 'grep'), and the Windows section is clearly labeled but not prioritized over Linux. The rest of the guide uses cross-platform tools (kubectl, helm) and shell commands that work on both Linux and Windows. No Windows-specific tools or patterns are used exclusively, and Linux parity is generally maintained.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence, possibly using tabbed sections or side-by-side formatting.
- Explicitly state that all kubectl and helm commands are cross-platform unless otherwise noted.
- Consider adding macOS-specific notes if there are any subtle differences (e.g., default shell, file redirection).
- If possible, clarify that 'grep' and 'findstr' are platform-specific and provide guidance for users on how to install or use these tools on their respective OS.
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
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown after Bash, and there is no exclusive use of Windows tools or patterns. The only minor bias is that PowerShell (Windows) examples are always shown second, not first, which is the opposite of a typical Windows bias. All instructions are cross-platform, and Visual Studio Code is used as the recommended editor, which is also cross-platform.
Recommendations
No significant changes are needed. The documentation already provides parity for Linux/macOS and Windows users. If desired, clarify in the prerequisites that all command-line steps work on both Linux/macOS and Windows, and continue to provide both Bash and PowerShell examples where syntax differs.
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 immediately after Bash, and the PowerShell formatting is explicitly called out, which can create a perception of Windows bias. There are no Linux-specific tools or patterns mentioned, but the Bash examples are present, ensuring Linux parity. The bias is minor and mostly in the ordering and explicit labeling of PowerShell.
Recommendations
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows' for clarity.
- Alternate the order of examples or provide tabs for Bash and PowerShell to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported and that Bash is suitable for Linux/macOS users.
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 presented as a primary option alongside CLI, and there is minor bias in the order and prominence of PowerShell, which is more commonly used on Windows. No Linux-specific tools or shell examples (such as Bash scripting or references to Linux-native deployment methods) are included, but the Azure CLI example is cross-platform and sufficient for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and is the recommended cross-platform tool.
- Consider adding a Bash shell example for deploying the ARM template, or clarify that the CLI example can be run in Bash or other Linux shells.
- Ensure that PowerShell is not presented as the default or primary method unless there is a Windows-specific requirement.
- Add a note for Linux/macOS users about using Azure CLI in their native terminal environments.
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 examples for deployment and configuration tasks, but when mentioning programmatic options for disabling regional gateways, it lists Azure PowerShell before Azure CLI and REST API. The PowerShell cmdlet is referenced by name, but no Linux-specific shell or tool is highlighted. However, the Azure CLI is used for all command-line examples, which is cross-platform. There are no Windows-only tools or patterns, and no missing Linux examples for critical tasks.
Recommendations
- When listing programmatic options, mention Azure CLI before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- If referencing PowerShell, clarify that Azure PowerShell is available on Linux/macOS, or provide Bash equivalents where relevant.
- Avoid listing PowerShell as the first option unless the task is Windows-specific.
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 alongside Azure CLI, and PowerShell is mentioned before CLI in most sections. There are no Linux-specific examples or explicit references to Linux/macOS tools, but Azure CLI is cross-platform and is included throughout. The documentation does not use Windows-only tools (e.g., cmd.exe), but the prominence of PowerShell (which is historically Windows-centric, though now cross-platform) and its placement before CLI may create minor friction for Linux/macOS users.
Recommendations
- Consider mentioning that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Where PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions.
- Provide explicit examples or notes for Linux/macOS users, such as shell command equivalents or environment-specific tips.
- In sections listing both PowerShell and CLI, alternate the order or present CLI first to reduce perceived Windows bias.
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 (bash), and uses 'cmd' syntax highlighting for Maven and curl commands, which may imply Windows-first bias. However, Linux/macOS equivalents are present, and all critical steps are cross-platform.
Recommendations
- Present Linux/macOS and Windows environment variable instructions side-by-side or in parallel, rather than Windows first.
- Use appropriate syntax highlighting for shell commands (e.g., 'bash' for Linux/macOS, 'powershell' for PowerShell, 'cmd' for Windows) to clarify which platform each command is for.
- Explicitly state that Maven and curl commands are cross-platform and can be run in any terminal.
- Consider grouping platform-specific instructions under clear headings (e.g., 'Windows', 'macOS/Linux') for improved clarity.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always shown after the Bash examples. There is a slight bias towards Windows/PowerShell users, but Linux/macOS users are fully supported with Bash examples.
Recommendations
- Clarify in the tab headers that Bash is for Linux/macOS and PowerShell is for Windows, to help users quickly find the relevant examples.
- Consider using explicit tabbed sections for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to improve parity and discoverability.
- Ensure that variable names and code snippets are consistent between Bash and PowerShell examples to avoid confusion.
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, but PowerShell is given equal prominence to Azure CLI, which is more cross-platform. There is a slight bias in mentioning Azure PowerShell requirements alongside Azure CLI, and PowerShell is a Windows-centric tool, though it is available on Linux/macOS. The examples and instructions are not Windows-exclusive, but PowerShell is presented as a primary option rather than a secondary or Windows-specific alternative.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Explicitly note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for non-Windows environments.
- Consider listing Azure CLI examples first, followed by PowerShell as an alternative, to reduce perceived Windows bias.
- Add a brief note about using Cloud Shell, which is platform-agnostic, for both CLI and PowerShell tasks.
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_tools
windows_first
Summary
The documentation includes a related link to connecting virtual networks using PowerShell, which is a Windows-centric tool, and lists this before mentioning Linux-equivalent approaches. However, the main content is otherwise platform-neutral, focusing on Azure resource configuration rather than OS-specific commands or tools.
Recommendations
- Add equivalent Azure CLI or Azure Cloud Shell examples or links for connecting virtual networks, as these are cross-platform and widely used by Linux/macOS users.
- When referencing PowerShell-based guides, also reference or link to documentation for performing the same tasks with Azure CLI or ARM templates.
- Consider reordering related content so that cross-platform tools (Azure CLI, ARM templates) are mentioned before or alongside PowerShell.
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, the PowerShell section is Windows-centric and is given equal prominence to CLI. There is no explicit Linux/macOS bias, but PowerShell is primarily used on Windows, and its inclusion may suggest a Windows preference. Additionally, PowerShell is mentioned before Linux-native shell examples (e.g., Bash), and there are no Bash or Linux-specific examples provided.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage, demonstrating cross-platform compatibility.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and highlight this in the CLI section.
- Consider mentioning PowerShell Core (pwsh) for Linux/macOS users if PowerShell examples are retained.
- If possible, reorder examples to show Azure CLI (cross-platform) before PowerShell (Windows-centric) or clarify their parity.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions using pivot sections, but in shared/general sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. PowerShell commands are frequently included alongside Bash, and some sections (like persistent storage and environment variables) mention Windows-specific tools and paths first. However, Linux parity is generally maintained, and Linux-specific instructions are present where needed.
Recommendations
- In shared sections, alternate the order of Bash and PowerShell examples, or present Bash (Linux/macOS) first to avoid implicit Windows prioritization.
- Where possible, clarify when a command or tool is cross-platform, and avoid defaulting to Windows terminology or paths in general guidance.
- Ensure that all features and examples have clear Linux/macOS equivalents, and that Linux-specific nuances are equally detailed.
- Review for subtle language that assumes Windows-first workflows (e.g., mentioning C:\home before /home in shared sections).
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 shown alongside or before CLI examples, and PowerShell is referenced in some CLI tabs (e.g., az identity create). There is a mild 'windows_first' bias in some sections, as PowerShell is presented as a primary scripting option, even though Azure CLI is cross-platform. No critical tasks are Windows-only, and Linux/macOS users can complete all steps using Azure CLI or ARM templates.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, especially in tabbed sections.
- Clarify that Azure PowerShell is cross-platform, but highlight Azure CLI as the preferred option for Linux/macOS users.
- Remove PowerShell references from CLI tab examples (e.g., az identity create is shown as azurepowershell-interactive).
- Add explicit notes or guidance for Linux/macOS users where PowerShell is not supported or less common.
- Consider adding Bash script examples for common tasks, especially in sections where PowerShell is heavily used.
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, with PowerShell examples clearly labeled and separated. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections (such as prerequisites), PowerShell examples are shown immediately after CLI, sometimes without explicit Linux/macOS guidance. There are no Linux-specific examples or explicit mentions of Linux/macOS compatibility for PowerShell commands. The documentation does not use Windows-only tools, but the inclusion of PowerShell may cause confusion for Linux/macOS users, especially since PowerShell is not pre-installed on those platforms.
Recommendations
- Clarify that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is cross-platform (Linux/macOS/Windows).
- Add explicit notes or tabs indicating which examples are suitable for Linux/macOS users.
- Consider providing Bash shell examples where relevant, especially for commands involving environment variables.
- Mention that PowerShell is available for Linux/macOS, but CLI is the recommended tool for those platforms.
- Ensure that all critical steps can be completed using Azure CLI, and highlight CLI as the default for cross-platform users.
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
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured equally and sometimes before Linux/Bash alternatives. Windows-specific installation instructions (e.g., using winget for Helm) are given before Linux instructions, and PowerShell is referenced as a primary tool. There is no missing Linux example for critical steps, but Windows tools and patterns (PowerShell, winget) are mentioned first or exclusively in some sections.
Recommendations
- Ensure Linux/Bash examples are always presented alongside PowerShell, and consider showing Bash/Linux first or equally.
- For Helm installation, provide explicit macOS instructions (e.g., Homebrew) and mention them alongside Linux and Windows.
- Avoid referencing Windows tools (like winget) before Linux alternatives; present all OS options together.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or Cloud Shell.
- Where PowerShell is used, explicitly note that Bash equivalents exist and are supported.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd, PowerShell) before Linux/macOS (bash), and includes Windows-specific commands (setx, PowerShell) with detailed restart instructions. Linux/macOS instructions are present and correct, but are listed after Windows examples. The use of Visual Studio Code is mentioned as cross-platform, and all other steps (Maven, Java, curl) are platform-neutral.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before or alongside Windows examples, rather than after.
- Clarify that all commands are available for all platforms, and avoid implying Windows is the default or primary environment.
- Consider grouping environment variable instructions by platform in a tabbed format (Windows, Linux/macOS) for parity.
- Add notes about validating environment variables on Linux/macOS (e.g., 'echo $VAR') as is done for Windows.
- Ensure that restart instructions for environment variable changes are given for all platforms, not just Windows.
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. While the Azure CLI section is cross-platform, the PowerShell section is Windows-specific and is presented as a primary option alongside CLI and portal. Additionally, the CLI instructions mention Windows PowerShell as an example of a command console application, which may subtly reinforce Windows as the default environment. There are no Linux/macOS-specific examples or explicit parity checks, and screenshots are all from the Azure portal (which is platform-agnostic).
Recommendations
- Clarify that Azure CLI works equally well on Linux/macOS and provide example commands for Bash or zsh.
- In CLI instructions, mention Linux/macOS terminal applications (e.g., 'open a terminal such as Terminal on macOS or GNOME Terminal on Linux') alongside Windows PowerShell.
- Consider adding a note in the PowerShell section that PowerShell Core is available cross-platform, or clarify that Windows PowerShell is Windows-only.
- Ensure parity by providing troubleshooting tips or environment-specific notes for Linux/macOS users where relevant.
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) alongside bash. However, Linux/macOS instructions are present and complete. No Windows-only tools or patterns are used elsewhere, and the build/run instructions are cross-platform.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows/PowerShell, or group them equally.
- Clarify that 'setx' is not available on Linux/macOS and that restarting the shell is only needed for Windows.
- Consider using tabbed sections for OS-specific instructions to improve parity and clarity.
- Explicitly mention that Maven and Spring Boot commands are cross-platform.
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 mentioning Linux/macOS equivalents. Windows-specific commands (setx, PowerShell syntax) are given more prominence and detail, while Linux/macOS instructions are brief and listed last. All other steps (Azure CLI, Maven, curl) are cross-platform, and the page explicitly mentions Visual Studio Code as a cross-platform editor.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Use a table or side-by-side layout for environment variable setup commands for all platforms.
- Clarify that Azure CLI, Maven, and curl commands work on all platforms.
- Consider including screenshots or explicit shell prompts for Linux/macOS where Windows screenshots are shown.
- Ensure parity in detail and explanation for Linux/macOS commands.
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
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Azure Cache for Redis using Bicep. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric, and the documentation presents both options equally. However, PowerShell examples are given alongside CLI in every section, and there is no explicit mention that PowerShell is primarily used on Windows, nor are Linux/macOS-specific instructions or considerations provided. The CLI examples are shown first, which helps mitigate bias, but the presence of PowerShell throughout may confuse Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Add a note indicating Azure CLI is cross-platform and preferred for non-Windows environments.
- Consider including bash shell-specific instructions or troubleshooting tips for Linux/macOS users.
- Ensure that all steps can be completed using Azure CLI alone, and highlight this for Linux/macOS users.
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
Summary
The documentation is largely cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are minor instances of Windows bias: Windows-specific tools (Azure PowerShell) are mentioned before Azure CLI, and some examples (such as path syntax for AzureWebJobs_TypeScriptPath) use Windows-style paths. Additionally, the explanation of reserved delimiters in app setting names describes Windows behavior first, and the Windows-only setting WEBSITE_NODE_DEFAULT_VERSION is presented without a Linux equivalent. Overall, Linux parity is strong, but Windows is occasionally prioritized in examples and tool recommendations.
Recommendations
- When recommending tools for managing app settings, mention Azure CLI before or alongside Azure PowerShell, as Azure CLI is cross-platform.
- Where path examples are given (e.g., AzureWebJobs_TypeScriptPath), provide both Windows and Linux path syntax, or use a neutral example.
- For settings that are OS-specific (like WEBSITE_NODE_DEFAULT_VERSION), clarify the Linux equivalent or explicitly state that Linux uses a different mechanism (e.g., linuxFxVersion).
- In explanations of delimiters (double-underscore vs colon), present Linux behavior first or equally, and clarify differences.
- Review all examples and ensure Linux/macOS scenarios are equally represented, especially in sample values and tool usage.