245
Pages Scanned
50
Pages Flagged
245
Changed Pages
20.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:32
Scan Information
Started At: 2026-02-23 00:00:32
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 245
Files Completed: 245
Problematic Pages
50 issues found
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate) for all steps, including certificate creation, resource deployment, and cleanup. There are no Bash, Azure CLI, or Linux/macOS-compatible examples provided. The certificate creation step relies on Windows-only PowerShell cmdlets, making it difficult for Linux/macOS users to follow the tutorial without external workarounds.
Recommendations
- Add Azure CLI (az) examples for all resource creation and management steps, as Azure CLI is cross-platform.
- Provide Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL).
- Mention that Azure PowerShell can be installed and used on Linux/macOS, but clarify any limitations (especially for certificate creation).
- Where possible, present both PowerShell and CLI/Bash examples side-by-side.
- Explicitly note any steps that are Windows-only and offer Linux/macOS alternatives or workarounds.
Create Pull Request
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell is used for all command-line examples, and Windows installation methods (MSI, Setup.exe, winget) are emphasized. No Linux/macOS equivalents or cross-platform guidance are provided for SignTool integration, and there is no mention of alternative signing tools or workflows for non-Windows users.
Recommendations
- Clearly indicate if SignTool integration is Windows-only; if not, provide equivalent instructions for Linux/macOS users, including supported signing tools and setup steps.
- For GitHub Actions, Azure DevOps, and SDK integrations, add explicit cross-platform examples and clarify OS compatibility.
- If PowerShell is not available on Linux/macOS for these tasks, suggest alternative shell commands or tools.
- Add a section summarizing platform support for each integration, so users know which are Windows-only and which are cross-platform.
- Where possible, provide Linux/macOS installation instructions for .NET runtime and any required libraries.
- Highlight any limitations or workarounds for Linux/macOS users.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides a PowerShell-based tutorial link for creating an autoscaling, zone-redundant Application Gateway, without offering equivalent Linux/macOS CLI or ARM template examples. The PowerShell example is listed as the only explicit 'how-to' in the 'Next steps' section, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI and/or ARM template tutorials for creating autoscaling, zone-redundant Application Gateway.
- List Azure CLI and PowerShell options side-by-side in the 'Next steps' section to ensure parity.
- Explicitly mention that PowerShell is available cross-platform, but also provide native CLI examples for Linux/macOS users.
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
missing_linux_example
Summary
The documentation page provides a conceptual overview of end-to-end TLS on Azure Application Gateway. While the main content is platform-neutral, the 'Next steps' section exclusively links to a PowerShell-based configuration guide, implying Windows-centric tooling. No Linux or cross-platform CLI (Azure CLI, Bash) configuration examples or links are provided, and Windows-specific certificate formats (PFX) are referenced with links to Windows API documentation before mentioning cross-platform alternatives.
Recommendations
- Add links to equivalent Azure CLI or Bash-based configuration guides for end-to-end TLS setup.
- Include examples or references for certificate creation and management using cross-platform tools (e.g., OpenSSL) instead of only referencing Windows PFX and Wincrypt APIs.
- Ensure that Linux/macOS users are provided with parity in guidance for configuring Application Gateway, including certificate preparation and upload.
- In the 'Next steps' section, offer multiple options (PowerShell, Azure CLI, ARM templates) for configuration, not just PowerShell.
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, with all code examples and module references using PowerShell. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. Windows terminology and tools are mentioned exclusively and before any Linux alternatives, which are absent.
Recommendations
- Add equivalent Azure CLI examples for credential asset creation and runbook authentication.
- Clarify which steps are platform-agnostic and which require Windows-specific tooling.
- Provide guidance for Linux/macOS users on how to authenticate to Azure Automation using Microsoft Entra ID, including references to Bash or Python SDKs where possible.
- Mention cross-platform PowerShell Core (pwsh) compatibility and any limitations.
- Include a note on how Linux users can use Azure Automation, and link to relevant documentation.
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 tool, without mentioning or providing equivalent CLI (az CLI) or Linux/macOS-friendly alternatives. All migration automation examples and recommendations are PowerShell-centric, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide az CLI (Azure Command-Line Interface) examples and scripts for migration tasks alongside PowerShell scripts.
- Explicitly mention that PowerShell Core is cross-platform, and provide instructions for installing and running migration scripts on Linux/macOS.
- Add guidance or links for Linux/macOS users to alternative migration approaches or tools.
- Ensure that all script references clarify platform compatibility and offer parity for non-Windows environments.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., retention and backup), while Linux equivalents are missing or less detailed. Linux is acknowledged in the TLS upgrade section, but PowerShell is the only scripting example for backup/export tasks, and references to Linux tools for managing Automation assets are lacking.
Recommendations
- Provide Linux/CLI/REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
- Include references to Azure CLI and/or az automation commands where possible, not just PowerShell.
- In tables and instructions, present Linux and Windows guidance with equal prominence, or group by platform rather than listing Windows first.
- For asset backup/recovery, clarify options for Linux/macOS users, including any limitations or alternative workflows.
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 for using Azure portal, Azure PowerShell, and ARM templates to manage identities in Azure API Management. However, it exclusively uses Azure PowerShell for CLI-based examples, with no mention of Azure CLI (az), Bash, or Linux/macOS shell equivalents. The PowerShell installation instructions and sample code are Windows-centric, creating friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all identity creation and management tasks.
- Include instructions for installing and using Azure CLI on Linux/macOS.
- Mention Bash scripting or provide sample Bash commands where appropriate.
- Clarify that PowerShell can be used cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance via zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in greater detail. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows-specific concepts (such as IIS, .NET Framework, and C:\home directory) are described in depth. Some sections (e.g., customizing memory, CPU, health ping) show Windows-focused tables and PowerShell examples before Linux equivalents, even when the feature is cross-platform.
Recommendations
- Ensure Linux examples and explanations are presented with equal prominence and detail as Windows, especially for cross-platform features.
- Where possible, show Linux/Bash examples first or side-by-side with Windows/PowerShell to avoid implicit prioritization.
- Expand Linux-specific guidance (e.g., persistent storage, environment variable injection, diagnostic log access) to match the depth of Windows sections.
- Clarify when features or settings are Windows-only, and provide Linux alternatives or explicit notes when features differ.
- Review and balance the use of PowerShell and Windows tools; ensure Linux tools (e.g., Bash, SSH, Docker Compose) are equally represented.
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 primarily focused on gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. However, troubleshooting and connectivity examples (such as Test-NetConnection and netstat -aon) are given using Windows/PowerShell commands, with no Linux/macOS equivalents or guidance. Windows tools and patterns are mentioned exclusively, and Linux users are told the feature is unavailable for their workloads, but no migration or alternative troubleshooting guidance is provided for Linux users.
Recommendations
- Clearly state early in the document that gateway-required virtual network integration is Windows-only, and direct Linux users to regional virtual network integration or other supported alternatives.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (such as nc, curl, or netstat) for users working with regional virtual network integration or other scenarios.
- Add a section summarizing Linux limitations and migration paths, linking to regional virtual network integration documentation.
- Ensure that all example commands and tools are either cross-platform or alternatives are provided for Linux/macOS users.
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 provides detailed, step-by-step code examples for Windows apps and containers, including C# and Java code for accessing certificates via the Windows certificate store. Linux guidance is limited to brief C# file-loading examples, with no equivalent code samples for other languages (Node.js, PHP, Python, Java) on Linux. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized and explained first, while Linux instructions are less comprehensive and often refer users to external language documentation.
Recommendations
- Add explicit Linux code examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from /var/ssl/certs and /var/ssl/private.
- Provide more detailed guidance on Linux certificate handling, including file formats, permissions, and environment variable usage.
- Balance the order of presentation so Linux and Windows examples are given equal prominence, possibly using tabs or parallel sections.
- Clarify any differences in certificate management between Windows and Linux, including potential pitfalls or best practices.
- Where possible, avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
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 role assignment, but PowerShell is presented as a primary automation method in several places. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and the PowerShell example is given equal prominence to Azure CLI. The FAQ and automation sections list PowerShell before Linux-native alternatives. However, Linux tooling (OpenSSL) is also covered, and Azure CLI is included for most tasks, so Linux users are not blocked but may experience friction.
Recommendations
- Ensure that Azure CLI examples are always presented before or alongside PowerShell, especially in automation sections.
- Expand certificate export instructions for Linux/macOS users, including more detailed OpenSSL guidance and troubleshooting.
- Add explicit notes or links for Linux/macOS users when referencing Windows-only tools (IIS, Certreq.exe), suggesting alternative workflows.
- In FAQ and automation sections, list Azure CLI and Linux-native tools first, or provide parity in example ordering.
- Clarify when a step is Windows-only and provide Linux/macOS alternatives where possible.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Azure portal and Azure CLI instructions for backup and restore, 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 in examples and explanations, and Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions and screenshots also use Windows paths. The mention of Azure PowerShell as a scripting option is present, but no Linux shell (bash) or macOS-specific scripting samples are referenced. Windows file system patterns and terminology are used before Linux equivalents, and Linux paths are only briefly mentioned in a table. Overall, Linux/macOS users can complete the tasks, but the documentation is somewhat Windows-centric.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide bash shell scripting samples where PowerShell is referenced.
- Add screenshots or instructions showing Linux/macOS directory structures and tools (e.g., using SCP or SFTP instead of FTP for uploading files).
- When referencing Kudu DebugConsole, clarify that it is accessible from any OS and show both Windows and Linux path conventions.
- In tables and explanations, list Linux/macOS information before or alongside Windows information to avoid 'windows_first' bias.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section specifies that the relay agent (Hybrid Connection Manager) must be installed on Windows Server 2012 or newer. No Linux or macOS equivalent is mentioned, nor is it stated if Linux is unsupported or if alternatives exist. This creates friction for Linux users wishing to use Hybrid Connections.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, or explicitly state if it is Windows-only.
- If Linux/macOS support exists, provide installation instructions and examples for those platforms.
- If Windows-only, suggest alternative approaches for Linux users (e.g., VPN, VNet Integration) and link to relevant documentation.
- Review other sections for platform-specific tooling and ensure parity or clear guidance for Linux/macOS users.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, supporting both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths (e.g., 'D:\home') and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS, applicationHost.config) are mentioned frequently and often before their Linux equivalents. Windows-centric terminology and examples (such as referencing `%HOME%` and `.dll` extensions) appear throughout, while Linux-specific details are sometimes relegated to notes or parentheticals. Build automation and deployment sections prioritize Windows (Kudu) before Linux (Oryx), and Windows tools are described in greater detail. Some settings reference Windows behaviors or files without always providing Linux alternatives.
Recommendations
- Ensure Linux examples and paths (e.g., '/home') are shown alongside Windows ones, not just in parentheticals.
- Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide equivalent Linux tooling or clarify if not applicable.
- Present Linux and Windows build automation sections in parallel or with equal prominence.
- Add Linux/macOS-specific troubleshooting notes where only Windows errors are described.
- Clarify when environment variables or settings are Windows-only, and provide Linux alternatives or explicitly state if not applicable.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is a PowerShell cmdlet, and references to log conversion tools are tied to Visual Studio and C#, which are Windows-centric. There is no mention of Azure CLI or Bash scripting, nor are Linux/macOS-friendly tools or workflows discussed.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, alongside the PowerShell example.
- Mention Bash scripting or cross-platform approaches for log management.
- Reference log conversion tools that do not require Visual Studio or C#, or provide alternatives for Linux/macOS users.
- Ensure that instructions for viewing and analyzing logs include cross-platform tools (e.g., jq, csvkit, Python scripts) in addition to Excel and Power BI.
- Where possible, present Windows and Linux/macOS methods side-by-side, or clarify that PowerShell can be used on Linux/macOS if relevant.
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 backend settings. However, in the 'Troubleshooting 4xx Errors with Dedicated Backend Connections' section, Windows authentication mechanisms (NTLM and Kerberos) and IIS configuration are referenced, with links to Windows and IIS documentation. These references appear before any mention of Linux equivalents or alternatives, and no Linux authentication guidance is provided. Additionally, the troubleshooting guidance is Windows-centric, potentially creating friction for Linux users.
Recommendations
- Add troubleshooting guidance for Linux-based backend servers, such as Apache, NGINX, or other common Linux web servers.
- Include links to documentation for configuring authentication (e.g., Kerberos) on Linux backends.
- Clarify that NTLM and IIS are Windows-specific and provide alternative authentication mechanisms for Linux environments.
- Ensure examples and troubleshooting steps are balanced between Windows and Linux backend scenarios.
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 instructions for mutual authentication on Azure Application Gateway. While the feature itself is cross-platform, the documentation exhibits Windows bias by prioritizing PowerShell examples and references, mentioning PowerShell before Azure CLI, and linking to a PowerShell-specific 'Next steps' guide. Azure CLI examples are present but less detailed, and there are no explicit Linux/macOS-specific guidance or examples. Portal support is noted as unavailable, but no Linux-native tools or workflows are discussed.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step CLI workflows.
- Link to both PowerShell and Azure CLI guides in the 'Next steps' section, or create a Linux/macOS-focused configuration guide.
- Explicitly mention that all CLI commands are cross-platform and can be run on Linux/macOS.
- Add notes or examples for certificate extraction and management using Linux-native tools (e.g., openssl) where relevant.
- Ensure that references to PowerShell do not precede CLI or are presented in parallel, to avoid Windows-first impression.
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 page demonstrates a notable Windows bias. It exclusively uses Windows Server as the backend SQL VM example and references SQL Server Management Studio (SSMS), a Windows-only client, for connectivity testing. No Linux or cross-platform alternatives (such as SQL Server on Linux, Azure Data Studio, or command-line tools) are mentioned. All screenshots and instructions assume Windows environments, and Linux users are not provided with equivalent guidance.
Recommendations
- Include instructions and examples for deploying SQL Server on Linux (supported by Azure SQL VM images).
- Provide alternative client connection methods, such as using Azure Data Studio (cross-platform) or sqlcmd (available on Linux/macOS).
- Add notes or sections for Linux/macOS users, including screenshots and step-by-step guidance.
- Mention that SSMS is Windows-only and suggest cross-platform tools for non-Windows users.
- Ensure backend pool configuration examples reference both Windows and Linux SQL Server VMs.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for all migration steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code examples, installation instructions, and operational guidance assume the use of PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux/macOS users, and no CLI or REST API equivalents are provided. This creates friction for users on non-Windows platforms and may prevent them from easily completing the migration.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all major migration steps, including configuration cloning and public IP retention.
- Explicitly state whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation/setup instructions for those platforms.
- Include Bash or shell script examples where possible, or at least reference how Linux/macOS users can perform the same tasks.
- Add a section or callout for Linux/macOS users, summarizing their options and any platform-specific caveats.
- If certain steps are only possible with PowerShell, clarify this and provide guidance on using Azure Cloud Shell (which is cross-platform) as an alternative.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias, primarily through the use of Azure PowerShell and Azure CLI examples that utilize PowerShell syntax. The migration script is only mentioned as available via PowerShell, and the 'Next steps' tutorial links to a PowerShell-based guide. There are no explicit Linux/bash examples or references to cross-platform CLI usage, and PowerShell is presented as the default scripting environment. However, the core content and features described are platform-agnostic, and Linux users can generally use Azure CLI or ARM templates for equivalent tasks.
Recommendations
- Provide Azure CLI examples using bash syntax alongside PowerShell examples, especially for registration and migration tasks.
- Clarify that Azure CLI commands can be run on Linux/macOS and provide explicit bash examples.
- Link to tutorials or migration guides that use Azure CLI in bash or ARM templates, not just PowerShell.
- Mention that the migration script may require PowerShell and suggest alternatives for Linux/macOS users if available.
- Ensure 'Next steps' includes cross-platform options, not only PowerShell-based tutorials.
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 disaster recovery operations, with no equivalent examples or guidance for Linux-native tools (such as Bash, CLI, or Python). All migration scripts and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page claims applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
- Provide Bash or Azure CLI script examples for migrating Automation account assets.
- Include guidance for using Python runbooks or scripts, which are supported in Azure Automation and more common in Linux environments.
- Explicitly mention any limitations or workarounds for Linux users, such as how to execute PowerShell scripts from Linux (using PowerShell Core), or alternative approaches.
- Add parity in runbook import instructions for Python or Bash runbooks, if supported.
- Clarify if PowerShell Core (cross-platform) is supported for these scripts, and provide instructions for Linux/macOS users.
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 a Linux/macOS equivalent (such as Azure CLI or REST API). Additionally, PowerShell is presented as the primary scripting method, which may create friction for Linux/macOS users. However, the overall guidance is platform-neutral, and most steps are performed in the Azure Portal, which is accessible from any OS.
Recommendations
- Add Azure CLI and/or REST API examples for configuring 'publicNetworkAccess', alongside the PowerShell script.
- Explicitly mention that the Azure Portal steps are OS-agnostic.
- Where PowerShell is used, clarify if it can be run cross-platform (e.g., PowerShell Core), or provide alternative commands for Bash/CLI users.
- Ensure any references to agents/tools (e.g., Log Analytics agent) include both Windows and Linux instructions or links.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily features PowerShell cmdlets and examples, with all certificate management tasks (creation, retrieval, deployment) shown exclusively via PowerShell. There are no Linux/bash/CLI examples for certificate management, and PowerShell is presented first and most extensively. While Python examples are provided for runbook usage, all administrative tasks are PowerShell-centric, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, removal, etc.) alongside PowerShell examples.
- Include bash or shell script snippets for common certificate operations, especially for uploading and managing certificates.
- Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core), and provide guidance for Linux/macOS users if so.
- Present examples in a more balanced order (e.g., CLI, PowerShell, Python) or clearly indicate platform requirements for each method.
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 heavily emphasizes PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are PowerShell-based, with no equivalent Bash, Azure CLI, or Linux-native scripting examples. The 'Create a new credential asset' section only offers Windows PowerShell guidance, and PowerShell cmdlets are described before Python functions. There is no mention of Linux/macOS shell alternatives or cross-platform CLI usage.
Recommendations
- Add Azure CLI examples for credential asset management, where possible.
- Clarify whether credential management is possible from Linux/macOS and provide guidance or limitations.
- Include Bash or shell scripting examples for relevant operations.
- Explicitly state if PowerShell is required for certain tasks, and provide cross-platform PowerShell Core guidance if applicable.
- Reorder sections or add parity so that Python and cross-platform options are presented alongside PowerShell.
- Mention any limitations or workarounds for Linux/macOS users.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell examples for configuring secure asset encryption in Azure Automation, with PowerShell commands shown first and in detail. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash), and PowerShell is referenced as the primary tool for tasks like assigning managed identities and configuring Key Vault access policies. REST API examples are included, but Linux-native tooling is not covered.
Recommendations
- Add Azure CLI examples alongside PowerShell for all major configuration steps (e.g., assigning managed identities, configuring Key Vault access policies, switching to customer-managed keys).
- Explicitly mention that PowerShell commands can be run cross-platform (on Linux/macOS) if using PowerShell Core, or clarify any Windows-specific requirements.
- Provide Bash or Azure CLI scripts for Linux/macOS users to ensure parity.
- Reorder sections so that REST API and CLI examples are not always secondary to PowerShell.
- Reference Azure CLI documentation and modules where relevant.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tooling, with most examples, screenshots, and parameter handling described in terms of PowerShell, PowerShell Workflow, and graphical runbooks (which are also PowerShell-based). Windows/PowerShell tools and patterns are mentioned first and most frequently, while Python runbooks (the main cross-platform option) receive minimal coverage and lack detailed examples. There are no Linux-specific CLI examples or references to Bash/Az CLI workflows for assigning parameters, and the PowerShell-centric approach may create friction for Linux/macOS users.
Recommendations
- Add detailed examples for Python runbooks, including parameter handling and invocation from Linux/macOS environments.
- Include Az CLI examples for starting runbooks and passing parameters, demonstrating cross-platform workflows.
- Clarify that PowerShell examples are applicable on Linux/macOS when using PowerShell Core, or provide explicit guidance for those platforms.
- Balance the order of examples so that Python and Az CLI are not always secondary to PowerShell.
- Mention any limitations or differences for Linux/macOS users, especially regarding graphical runbooks or PowerShell-specific features.
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 for managing modules in Azure Automation is heavily focused on PowerShell and Windows-centric workflows. Most examples, instructions, and module references are for PowerShell, with explicit mentions of Windows PowerShell versions and cmdlets. Internal cmdlets and certain module features are unavailable on Linux Hybrid Runbook Workers, but this is noted. There are no Linux/bash examples, and Linux-specific guidance is minimal or missing. Python module support is mentioned but not detailed. The portal instructions and PowerShell Gallery workflows are also Windows-oriented.
Recommendations
- Add explicit Linux Hybrid Runbook Worker guidance, including limitations and supported module types.
- Provide bash or Python examples for module management where possible, especially for custom modules.
- Clarify which features are cross-platform and which are Windows-only, ideally with a summary table.
- Expand the 'Python modules' section to include practical examples and parity with PowerShell workflows.
- Add links or references to Linux-specific documentation for Azure Automation, if available.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service plans for both Windows and Linux, mentioning both operating systems early and clarifying feature parity. However, the 'Managed Instance' section is Windows-only and is described before any Linux-specific advanced options, which may subtly prioritize Windows scenarios. No PowerShell-heavy or Windows tools bias is present, and Linux examples are not missing, but Windows-specific features are highlighted first in advanced hosting options.
Recommendations
- Add a comparable section for advanced Linux hosting options (if available), or clarify that Managed Instance is Windows-only and mention Linux alternatives if they exist.
- Ensure links and feature tables consistently reference both Windows and Linux plan details.
- Consider adding explicit Linux-specific guidance or examples where relevant, especially for scaling, pricing, and plan selection.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (export), and uses 'command prompt' terminology. However, all critical steps include Linux/macOS equivalents, and build/run/test instructions are cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples.
- Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt'.
- Clarify that Maven and curl commands are cross-platform.
- Consider grouping OS-specific instructions together for clarity.
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 Azure CLI examples for both Bash and PowerShell, with Bash shown first in nearly all cases. There are no Windows-specific tools or patterns prioritized, and Linux parity is maintained throughout. Visual Studio Code is recommended, which is cross-platform, and all CLI commands are compatible with Linux/macOS. No critical steps are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Explicitly mention that all tools (Azure CLI, Azure Developer CLI, Visual Studio Code) are cross-platform.
- Consider adding a short note confirming Linux/macOS compatibility for all steps, to reassure non-Windows users.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell (Windows) examples are given alongside Bash, and PowerShell-specific formatting is explicitly called out. Bash examples are shown first, but the presence of PowerShell examples indicates a mild Windows bias. No Linux-specific tools or patterns are missing, and the Azure CLI commands work cross-platform.
Recommendations
- Clarify that both Bash and PowerShell examples are cross-platform (PowerShell Core runs on Linux/macOS).
- Consider explicitly mentioning that Bash examples are suitable for Linux/macOS, and PowerShell for Windows (or PowerShell Core on other OSes).
- If possible, provide a brief note about running Azure CLI commands in Bash on Linux/macOS and in PowerShell on Windows.
- Ensure parity by not implying PowerShell is Windows-only, since PowerShell Core is cross-platform.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell examples are shown for every CLI command, which is primarily a Windows shell. Bash examples are presented first, but PowerShell examples are given equal prominence, which may suggest a slight Windows bias. No Linux-specific tools or patterns are missing, and the Azure CLI commands are cross-platform.
Recommendations
- Clarify that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS.
- Consider grouping Bash and PowerShell examples under separate tabs for clarity.
- Explicitly mention that Bash examples work on Linux/macOS and Windows (if Bash is installed), while PowerShell is primarily for Windows.
- If possible, provide a note about cross-platform compatibility of Azure CLI.
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, but PowerShell is featured equally alongside CLI. There is a slight Windows bias as PowerShell is traditionally associated with Windows, and the PowerShell example is given immediately after the CLI example. However, both methods are clearly presented, and Azure CLI is cross-platform. No Linux/macOS-specific tools or patterns are missing, but there are no explicit Bash or Linux shell examples.
Recommendations
- Clarify that Azure CLI works on Linux/macOS and Windows, and is recommended for cross-platform users.
- Consider adding a Bash shell example for Linux users, even if it simply wraps Azure CLI commands.
- Mention that PowerShell Core is available on Linux/macOS, to avoid implying PowerShell is Windows-only.
- If relevant, note that the Azure portal and Cloud Shell are platform-agnostic.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files. However, PowerShell is presented as a primary option alongside Azure CLI, and there are references to Azure PowerShell requirements. While Azure CLI is cross-platform, PowerShell is more commonly associated with Windows, and its inclusion may create a slight Windows bias. There are no Linux-specific examples or explicit mentions of Linux/macOS tools or workflows.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is available on Linux/macOS, but Azure CLI is generally more common for non-Windows environments.
- Consider providing bash shell examples or instructions for Linux/macOS users, especially for file operations (e.g., saving/uploading the Bicep file).
- Ensure that prerequisites and environment setup instructions include Linux/macOS guidance where 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 examples, but when mentioning scripting tools for managing API Management instances, it lists Azure PowerShell before Azure CLI and REST API. The PowerShell cmdlet ('set-azapimanagement') is referenced alongside CLI and REST API, but no Linux/macOS-specific guidance or parity is provided. However, the CLI examples are present and usable on Linux/macOS, and no critical steps are Windows-only.
Recommendations
- When listing scripting tools, mention Azure CLI and REST API before PowerShell, or group them equally.
- Add explicit notes that Azure CLI is cross-platform and usable on Linux/macOS.
- Provide sample scripts or command-line snippets for both Azure CLI and PowerShell where appropriate.
- If referencing PowerShell, clarify that Azure CLI is recommended for Linux/macOS users.
- Ensure screenshots and portal instructions are not Windows-specific (e.g., avoid referencing Windows-only UI elements).
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions Windows tools (Azure PowerShell) alongside Azure CLI and Azure Portal for creating an AKS cluster, but does not provide any PowerShell-specific examples or commands. All deployment and verification steps use kubectl, which is cross-platform. The only minor bias is listing Azure PowerShell before Azure Portal, but Linux parity is otherwise maintained.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as CLI is more commonly used across platforms.
- Explicitly mention that kubectl commands work on Windows, Linux, and macOS terminals.
- If possible, clarify that Azure PowerShell is optional and provide links to Linux/macOS installation instructions for Azure CLI and kubectl.
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 inclusion of Azure PowerShell (which is most commonly used on Windows) and its example may create a mild Windows bias. Additionally, PowerShell is listed alongside CLI in the prerequisites and workflow, and its example is presented immediately after the CLI example, rather than being clearly separated or marked as Windows-specific. No Linux/macOS-specific tools or workflows are mentioned, and there is no explicit guidance for Linux users regarding PowerShell usage.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Add a note for Linux/macOS users about installing and using Azure PowerShell, or recommend using Azure CLI as the preferred cross-platform tool.
- Consider presenting Azure CLI examples first, as it is the most universally accessible for all platforms.
- Explicitly state that all CLI commands work on Linux/macOS, and provide troubleshooting tips for non-Windows environments if needed.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a first-class option alongside CLI. The prerequisites list Azure CLI and Azure PowerShell equally, and the PowerShell example is given its own section. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for PowerShell, which may cause confusion for non-Windows users. However, the Azure CLI example is present and fully functional for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add a note in the prerequisites section indicating that Azure PowerShell is best supported on Windows, while Azure CLI is cross-platform.
- Consider providing Bash shell examples or highlighting CLI usage for Linux/macOS users.
- Explicitly state that all Azure CLI commands are supported on Linux/macOS.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, there is a minor instance of Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, without mention of Linux/macOS CLI alternatives. No PowerShell commands or Windows-specific tools are used in the main content, and all guidance is applicable to any OS.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or Bash-based guides for connecting virtual networks, ensuring Linux/macOS users are equally supported.
- Where PowerShell is referenced, clarify that Azure CLI or portal-based approaches are also available and provide links.
- Review cross-referenced articles to ensure parity in example scripts and tooling 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
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI and Azure PowerShell examples for all procedural steps, with PowerShell examples present for every operation. While Azure CLI is cross-platform, the inclusion of PowerShell (which is historically Windows-centric, though now cross-platform) may still signal a Windows-first approach. In all code example tabs, PowerShell is always present, and in some cases, PowerShell appears before Bash or Linux-native alternatives. There are no Linux- or macOS-specific tools or shell scripts provided, and no explicit Bash examples are shown. However, the CLI examples do ensure Linux/macOS users can complete all tasks.
Recommendations
- Add explicit Bash shell examples (where applicable) alongside Azure CLI and PowerShell to demonstrate parity and comfort for Linux/macOS users.
- Clarify in the introduction that Azure CLI commands are fully supported on Linux/macOS, and that PowerShell Core is available cross-platform, to reduce perceived Windows bias.
- When listing code tabs, consider ordering as: Azure portal, Azure CLI, Bash (if applicable), then PowerShell, to avoid a Windows-first impression.
- Where PowerShell is used, note that PowerShell Core is available for Linux/macOS, or provide Bash equivalents for common scripting tasks.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, ARM templates, and portal instructions for most tasks. However, PowerShell examples are often shown alongside or before CLI examples, and PowerShell is referenced heavily. In some cases, PowerShell is used for both Windows and cross-platform scenarios, but the CLI examples (which are more universal for Linux/macOS) are not always given equal prominence. There are no Windows-only tools or patterns, but PowerShell is emphasized, which may create friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, as CLI is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, but recommend Azure CLI for Linux/macOS users where possible.
- Add explicit notes or links for Linux/macOS users, especially where PowerShell is used, to highlight CLI alternatives.
- Where PowerShell is not supported (e.g., user-assigned identity for App Service), clarify alternatives for Linux/macOS users.
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 in nearly every section, and are often presented immediately after CLI examples. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion throughout the guide may signal a Windows bias. Additionally, PowerShell examples are sometimes given equal prominence to CLI, rather than being secondary or in a dedicated Windows section.
Recommendations
- Clearly indicate that Azure CLI is the recommended, cross-platform tool for Linux/macOS users, and Azure PowerShell is primarily for Windows users.
- Consider grouping PowerShell examples in a dedicated 'Windows/PowerShell' tab or section, rather than interleaving them throughout the guide.
- For each task, ensure the Azure CLI example is shown first, and PowerShell is presented as an alternative for Windows users.
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS, and that PowerShell is optional for Windows environments.
- Review the use of PowerShell in resource group deletion and cluster updatesâif CLI covers all scenarios, PowerShell can be moved to a supplemental section.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always shown immediately after CLI, and Windows-specific installation instructions for Helm are presented before Linux. The PowerShell examples are extensive and detailed, which may suggest a slight preference for Windows users. However, Linux parity is generally maintained, and all critical steps are achievable via CLI or Bash. The only minor bias is the ordering and emphasis of Windows tools.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples, or clarify that Azure CLI is cross-platform and preferred for Linux/macOS.
- Present Linux Helm installation instructions before Windows, or group them equally.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Bash, and highlight Bash as a primary shell for non-Windows users.
- Consider adding macOS-specific Helm installation instructions for completeness.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally provides cross-platform guidance, with most examples using standard Kubernetes CLI commands. In the section for collecting logs, both Linux and Windows command examples are provided, but the Linux example is shown first, followed by the Windows example. No significant bias is present, and Linux users are fully supported.
Recommendations
- Maintain the current approach of providing both Linux and Windows command examples where platform-specific differences exist.
- Consider using tabbed code blocks or clearer headings to further emphasize parity and ease of use for both platforms.
- Continue to ensure that all critical troubleshooting steps include Linux/macOS-compatible instructions.
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 and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell and Windows Command Prompt examples. However, Linux/macOS instructions are present and equally detailed. The overall bias is minor, mostly in ordering and example prominence.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or group all OS instructions equally.
- Use neutral language when referencing code editors (e.g., mention Visual Studio Code's cross-platform support without highlighting Windows first).
- Ensure all CLI commands and examples are provided for Linux/macOS and Windows, with equal visibility.
- Consider using tabs or collapsible sections for OS-specific instructions to reduce perceived bias.
Azure App Configuration
Use variant feature flags in a Spring Boot application
...figuration/how-to-variant-feature-flags-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (Command Prompt and PowerShell) before Linux/macOS, but includes all relevant examples for each platform. No critical steps are Windows-only, and build/run instructions are cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before Windows examples, or group all OS instructions together without implied priority.
- Explicitly state that all steps are cross-platform and clarify any OS-specific nuances if present.
- Consider using a tabbed or parallel layout for OS-specific instructions to avoid perceived prioritization.
Azure App Configuration
Quickstart for adding feature flags to Spring Boot with Azure App Configuration
...p-configuration/quickstart-feature-flag-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), but all platforms are covered. No Windows-specific tools or patterns are used elsewhere, and Maven build/run instructions are platform-neutral.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or group all OS instructions together for parity.
- Explicitly state that all commands work cross-platform unless otherwise noted.
- Consider adding a note that Maven and Java are cross-platform, to reassure non-Windows users.
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 Windows-specific commands (setx, PowerShell) with more detail. Linux/macOS instructions are present but appear after Windows examples. The rest of the tutorial uses cross-platform tools (Azure CLI, Maven, curl) and is generally platform-neutral.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Clarify that 'setx' is Windows-only and offer an equivalent for Linux/macOS (e.g., editing ~/.bashrc or using export).
- Consider grouping environment variable instructions by platform in a tabbed format for clarity.
- Ensure parity in explanations for all platforms, avoiding extra detail for Windows unless necessary.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides monitoring 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 main option. Additionally, references to 'Windows PowerShell' and mentioning PowerShell after CLI (but not Bash or Linux-specific shells) indicate a mild Windows bias. The CLI instructions do mention that Azure CLI can be run in Cloud Shell or locally, including Windows PowerShell, but do not explicitly reference Bash or Linux shells. All screenshots and portal instructions are platform-neutral.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash, zsh, or other Linux/macOS shells, not just Windows PowerShell.
- Add example CLI instructions for Bash or Linux/macOS terminal environments, or clarify that CLI commands are identical across platforms.
- Consider adding a note in the PowerShell section that PowerShell Core is cross-platform, and clarify if the instructions are compatible with PowerShell Core on Linux/macOS.
- Ensure parity by referencing Linux/macOS environments equally when describing command-line options.