251
Pages Scanned
51
Pages Flagged
251
Changed Pages
20.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-16 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
51 issues found
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation, resource management, and cleanup. It references Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) and assumes a Windows environment (e.g., certificate store paths, file paths like c:\appgwcert.pfx). No Bash, Azure CLI, or Linux/macOS-compatible instructions or examples are provided, and Windows tools are mentioned before any cross-platform alternatives (which are absent).
Recommendations
- Add Azure CLI examples for each step, as Azure CLI is cross-platform and works on Linux/macOS.
- For certificate creation, provide Linux/macOS alternatives (e.g., using OpenSSL) alongside Windows PowerShell examples.
- Clarify which steps are Windows-specific and which can be performed on any OS, and provide guidance for Linux/macOS users.
- Use generic file paths or explain path differences for non-Windows systems.
- Mention that Azure PowerShell can be used on Linux/macOS, but provide installation and usage instructions for those platforms.
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, particularly SignTool, MSI installers, WinGet, and PowerShell commands. All setup instructions and examples are for Windows environments, with no mention of Linux/macOS equivalents or cross-platform alternatives. While other integrations (GitHub Actions, Azure DevOps, SDK) are listed, their setup is not detailed here, and the primary walkthrough is Windows-only.
Recommendations
- Add explicit guidance for Linux/macOS users, including whether Artifact Signing can be used from these platforms and how.
- If SignTool is Windows-only, clarify this early and direct Linux/macOS users to supported cross-platform integrations (e.g., GitHub Actions, SDK).
- Provide example workflows for GitHub Actions, Azure DevOps, and SDK usage on Linux/macOS, including installation and invocation steps.
- Mention any limitations or alternative signing tools for non-Windows environments.
- Reorganize the page to present cross-platform options before or alongside Windows-specific instructions.
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
windows_tools
missing_linux_example
Summary
The documentation page provides detailed, step-by-step code examples for Windows environments (Windows certificate store, C#, Java), but Linux examples are limited to C# file loading and lack parity for other languages. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized, and Windows instructions are generally given before Linux equivalents. References to Linux for Node.js, PHP, Python, and Java are deferred to external documentation, creating friction for Linux users.
Recommendations
- Add code examples for loading certificates in Linux environments for Node.js, PHP, Python, and Java directly in the documentation.
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid Windows-first ordering.
- Include more details about Linux-specific certificate handling, such as permissions, file formats, and common pitfalls.
- Clarify when a feature or example is Windows-only, and provide Linux alternatives where possible.
- Expand on the use of environment variables for certificate paths in Linux containers, with practical code samples.
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 script example for configuring public network access flags, without offering a Linux/macOS equivalent (such as Azure CLI or REST API). Additionally, PowerShell and Windows terminology appear first or exclusively in some sections, though Linux is mentioned in agent support. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI and/or REST API examples alongside PowerShell scripts for configuration tasks.
- Where possible, mention cross-platform tools (e.g., Azure CLI, Bash) before or alongside Windows/PowerShell tools.
- Clarify that PowerShell examples are for Windows users, and provide guidance for Linux/macOS users.
- Ensure screenshots and portal instructions are platform-neutral, or note any platform-specific differences.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation heavily references Azure PowerShell scripts for migration tasks, with no mention of Azure CLI or Bash alternatives. All migration automation examples and guidance are PowerShell-centric, which is typically associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default/only automation tool for migration.
Recommendations
- Add Azure CLI examples and scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly mention that PowerShell can be used cross-platform, or provide Bash-compatible scripts.
- Include guidance for Linux/macOS users on how to perform migration steps without PowerShell.
- Present both PowerShell and CLI/Bash options side-by-side in migration sections.
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 is heavily focused on PowerShell cmdlets and Windows-centric tools (e.g., PSCredential, PowerShell modules), with Windows PowerShell examples and terminology used throughout. While Python examples are provided, there are no Linux/bash or cross-platform shell examples. Windows tools and patterns are mentioned first and exclusively in several sections, and the creation of credentials via CLI is only shown for Windows PowerShell.
Recommendations
- Add examples for creating and managing credential assets using Azure CLI or REST API, which are cross-platform and usable from Linux/macOS.
- Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported for these operations, and provide examples if so.
- Mention or link to any Linux/macOS-compatible automation options, if available.
- Where possible, avoid referring to 'Windows PowerShell' exclusively and use 'PowerShell' if the cmdlets are compatible across platforms.
- Provide parity in credential management examples for Python, Azure CLI, and REST API.
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 heavily features PowerShell examples for all procedural steps, with no equivalent Bash/Azure CLI examples provided. PowerShell is presented as the primary scripting interface, and references to installing the Azure Az PowerShell module are made without mention of cross-platform alternatives. REST API examples are included, but the lack of Azure CLI or Bash scripting guidance creates friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for all procedural steps currently shown only in PowerShell.
- Mention that PowerShell Core and Azure Az PowerShell module are cross-platform, but also provide Bash/CLI alternatives.
- Reorder sections to present REST API and CLI examples alongside PowerShell, not after.
- Reference Azure CLI installation and usage for Linux/macOS users where PowerShell module installation is mentioned.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides detailed instructions and code samples for Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples use Azure PowerShell, which is primarily a Windows-centric tool, and there are no equivalent Azure CLI (cross-platform) examples. PowerShell is mentioned first and exclusively for scripting, creating friction for Linux/macOS users who typically use Azure CLI. No Linux-specific tools or patterns are referenced.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (creating, updating, and assigning managed identities).
- Mention Azure CLI as an alternative to PowerShell in introductory sections.
- Ensure that scripting instructions are platform-neutral or provide guidance for both Windows and Linux/macOS users.
- Consider referencing Bash or shell scripting where appropriate, especially for automation scenarios.
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 for gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, and Linux/macOS equivalents are not provided. Windows tools and patterns are mentioned first or exclusively, creating friction for cross-platform users who may need to troubleshoot from Linux VMs or environments.
Recommendations
- Clarify early in the document that gateway-required virtual network integration is Windows-only, and that troubleshooting steps are primarily for Windows environments.
- Where troubleshooting steps involve Windows tools (e.g., PowerShell Test-NetConnection, netstat -aon), provide Linux/macOS equivalents (e.g., nc, curl, ss, netstat, telnet) for users working with Linux VMs or hybrid environments.
- Add explicit notes or sections for Linux users, even if the integration feature itself is Windows-only, since network troubleshooting may occur from Linux hosts.
- Ensure that examples for connectivity testing and network diagnostics are cross-platform where possible, or clearly indicate if a step is Windows-specific.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux environments. 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 often mentioned first or exclusively, with Linux equivalents sometimes missing or appearing later. Some sections (such as build automation) default to Windows/Kudu explanations before Linux/Oryx, and Windows-specific configuration details are more verbose. Examples and explanations frequently use Windows conventions, and Windows tools are referenced without always providing Linux alternatives.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are shown alongside Windows ones, not just as parentheticals.
- When referencing Windows tools (e.g., msbuild, Web Deploy), provide Linux alternatives or clarify their applicability.
- Balance explanations for build automation: present Oryx (Linux) and Kudu (Windows) equally, and avoid defaulting to Windows-first.
- Where possible, provide Linux-specific troubleshooting and configuration guidance, not just Windows.
- Review sections for Windows-centric terminology (e.g., applicationHost.config, IIS) and clarify scope/applicability.
- Add explicit notes or tables indicating which settings are Windows-only, Linux-only, or cross-platform.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for Azure Application Gateway diagnostic logs provides a detailed PowerShell example for enabling logging, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is PowerShell, 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, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash scripting examples for log retrieval and processing.
- Mention or link to cross-platform log conversion tools (e.g., Python-based converters) instead of only Visual Studio/C# tools.
- Ensure that references to data visualization tools include Linux/macOS-compatible options (e.g., Jupyter, matplotlib, etc.) alongside Excel and Power BI.
- Where possible, present CLI examples before or alongside PowerShell examples to signal 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
Summary
The documentation page consistently uses Windows-based SQL Server VM examples and references SQL Server Management Studio (SSMS), a Windows-only client, for connectivity testing. There are no examples or guidance for Linux-based SQL Server VMs or for connecting from Linux/macOS clients. The Windows VM is presented as the default backend, and Windows tools are referenced exclusively.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
- Provide examples of connecting to the SQL Server via cross-platform clients such as Azure Data Studio, sqlcmd, or other CLI tools available on Linux/macOS.
- Mention that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, and clarify any OS-specific requirements.
- Add screenshots or command-line examples relevant to Linux/macOS environments.
- Explicitly state that the procedure is applicable regardless of the backend OS, unless there are Azure limitations.
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 includes a 'Next steps' section that highlights an Azure PowerShell tutorial for creating an autoscaling, zone redundant application gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example or link is provided. The PowerShell example is mentioned before any Linux-friendly alternatives, which may create friction for non-Windows users.
Recommendations
- Add links or examples for Azure CLI and ARM template approaches to create autoscaling, zone redundant Application Gateway v2.
- Ensure that Linux/macOS users are provided with parity in guidance and examples, especially in 'Next steps' and tutorial sections.
- Consider listing Azure CLI or cross-platform options before or alongside PowerShell examples to avoid implicit Windows-first bias.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway concepts and configuration. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and (2) backend authentication troubleshooting links point to IIS and Windows-specific resources. These Windows references appear before any mention of Linux equivalents or generic guidance, potentially creating friction for Linux users seeking similar troubleshooting information.
Recommendations
- Add troubleshooting guidance and links for Linux-based authentication mechanisms (e.g., Kerberos on Linux, Apache/Nginx configuration) alongside Windows/IIS references.
- Include examples or references for backend server log review on Linux systems (such as Apache, Nginx, or other common web servers) in the troubleshooting section.
- When referencing authentication protocols, clarify that NTLM and Windows Authentication are Windows-specific, and provide guidance for Linux-based alternatives where applicable.
- Ensure that troubleshooting steps are not exclusively tied to Windows documentation, but also mention cross-platform approaches.
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 is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions provided. The guidance assumes a Windows/PowerShell environment, which creates friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
- Include Bash shell examples and instructions for script execution, especially for users leveraging Azure Cloud Shell or running locally on Linux/macOS.
- Explicitly state PowerShell requirements and offer guidance for installing PowerShell Core on Linux/macOS, or recommend using Azure Cloud Shell for cross-platform compatibility.
- Add a section comparing PowerShell and Azure CLI approaches, highlighting any limitations or differences.
- Where possible, offer downloadable scripts in both PowerShell and Bash/Azure CLI formats.
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 evidence of Windows bias, primarily through the use of Azure PowerShell scripts and references to PowerShell Gallery for migration tasks. Additionally, the 'Next steps' section links first to a PowerShell-based tutorial for creating an autoscaling Application Gateway, rather than providing parity with Azure CLI or ARM template examples. There are no Linux-specific examples or explicit mention of cross-platform tooling, and PowerShell is presented as the primary automation method.
Recommendations
- Add Azure CLI examples alongside PowerShell scripts for migration and management tasks.
- Provide ARM template or Bicep deployment examples for platform-neutral automation.
- Ensure that tutorials and 'Next steps' include both PowerShell and Azure CLI options, with clear indications of cross-platform compatibility.
- Mention that Azure CLI is available on Linux/macOS and can be used for all management tasks.
- Where PowerShell is referenced, clarify if Azure CLI or other tools can achieve the same outcome.
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 page for Azure Automation disaster recovery is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages. All migration instructions and runbook examples are PowerShell-based, and there is no mention of Bash, Python, or CLI alternatives. While the page states applicability to both Linux and Windows VMs, the practical guidance and tooling are Windows-centric.
Recommendations
- Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI for Linux users.
- Include guidance on how Linux users can import, execute, or adapt runbooks without relying on PowerShell.
- Mention any limitations or considerations for Linux environments explicitly, and offer workarounds or alternatives.
- Where possible, show both PowerShell and Linux-native (e.g., Bash, Python) examples side-by-side.
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 Azure PowerShell, with Azure CLI examples included but less detailed. PowerShell is featured first and more extensively, and the 'Next steps' section directs users to a PowerShell-specific guide. There is no mention of Linux/macOS-specific tools or workflows, and the CLI example is minimal compared to PowerShell. Portal support is noted as unavailable, but no Linux-focused guidance (e.g., Bash scripting, OpenSSL usage) is provided.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including full configuration workflows.
- Include guidance or references for Linux/macOS users, such as using Bash or OpenSSL for certificate management.
- Reorder examples so that CLI and PowerShell are presented with equal prominence, or alternate which comes first.
- Add a 'Next steps' link to a CLI-focused guide, not just PowerShell.
- Clarify that both PowerShell and CLI are cross-platform, but highlight any OS-specific considerations.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but Windows instructions (with links and explicit steps) are mentioned first and in more detail. PowerShell cmdlets are referenced for several backup and retention operations, but equivalent Linux/CLI/REST examples are not provided. Some operations (like exporting runbooks or DSC configurations) only mention PowerShell cmdlets, with no Linux-native or cross-platform alternatives. This creates friction for Linux/macOS users, though most tasks are still possible via the portal or other means.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks and DSC configurations.
- List Linux and Windows instructions in parallel or in separate, clearly labeled sections to avoid 'Windows first' ordering.
- Where PowerShell cmdlets are referenced, add notes or links to equivalent Linux-compatible tools or scripts, or clarify if the operation is only possible via PowerShell.
- For asset backup/retrieval, clarify cross-platform limitations and suggest workarounds for Linux/macOS users.
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 is heavily focused on PowerShell and Windows-centric tooling, with nearly all examples, screenshots, and code snippets using PowerShell or referencing Windows concepts. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. The REST API and SDK sections are platform-neutral, but the practical guidance for local execution and parameter passing is almost exclusively Windows/PowerShell-oriented.
Recommendations
- Add examples for starting runbooks from Linux/macOS using Azure CLI, Bash, or Python scripts.
- Provide guidance on how to pass parameters using Azure CLI (az automation runbook start) and include sample commands.
- Expand the Python runbook section with more detailed examples, including parameter passing and execution from Linux/macOS environments.
- Mention cross-platform tools and clarify which instructions are Windows-specific.
- Include notes or tables summarizing parity between PowerShell and CLI/SDK approaches for parameter assignment.
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-centric tools and patterns. All code examples use PowerShell, and references are made to Windows PowerShell modules and cmdlets. There are no examples or guidance for users who may wish to use Azure Automation with Python runbooks or other cross-platform scripting options, nor is there mention of Bash/CLI alternatives. The documentation refers to 'Windows PowerShell' specifically and does not clarify cross-platform compatibility.
Recommendations
- Add examples using Azure CLI or Python runbooks to demonstrate cross-platform automation.
- Clarify whether the PowerShell modules and cmdlets used are compatible with PowerShell Core (pwsh) on Linux/macOS, or if they are Windows-only.
- Where possible, use 'PowerShell' instead of 'Windows PowerShell' unless the feature is truly Windows-only, and note any platform limitations.
- Provide links or references to documentation for using Azure Automation with Python or other supported languages.
- Explicitly state if certain features or modules are Windows-only, so Linux/macOS users are aware of limitations.
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 workflows for certificate management in Azure Automation, with all CLI examples provided in PowerShell. There are no Bash, Linux CLI, or cross-platform shell examples for certificate upload or management. PowerShell is presented first and as the primary method, with Python examples only for certificate retrieval in runbooks, not for certificate creation or upload. There is no mention of Linux-native tools or workflows for certificate management.
Recommendations
- Add Azure CLI (az) examples for certificate management, including upload, retrieval, and deletion.
- Provide Bash or shell script examples for certificate manipulation and upload, especially for Linux/macOS users.
- Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for these cmdlets, and if so, provide guidance for cross-platform usage.
- Mention any limitations or alternatives for Linux/macOS users if PowerShell is required.
- Consider including references to OpenSSL or other Linux-native certificate tools for preparing certificates before upload.
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 patterns, with most examples, instructions, and tooling referencing Windows PowerShell, Az/AzureRM modules, and Windows-specific cmdlets. Linux Hybrid Runbook Worker support is mentioned only to note limitations, and there are no Linux or cross-platform examples for module management. Python module support is referenced but not detailed. All portal and PowerShell instructions assume Windows environments and tools.
Recommendations
- Add explicit guidance and examples for Linux Hybrid Runbook Workers, including how to manage modules and any differences in module import, execution, and limitations.
- Provide parity in examples for module management using cross-platform tools (e.g., Azure CLI, REST API), or clarify which steps are Windows-only.
- Include a section summarizing which features are Windows-only and which are supported on Linux/macOS, with links to Linux-specific documentation.
- Expand documentation for Python modules and other non-PowerShell module types, including import and management instructions.
- Where possible, show Linux/macOS command-line equivalents or note limitations for non-Windows users.
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 generally describes Azure Change Tracking and Inventory as supporting both Windows and Linux. However, in the section on tracking registry keys, only Windows registry keys are discussed, with no mention of Linux equivalents (such as configuration files or daemon/service changes). The registry section is extensive and Windows-specific, and there are no Linux-specific examples or tables. Throughout the document, Windows terminology and tools (like registry keys) are given prominence, and Linux-specific details are comparatively sparse.
Recommendations
- Add a section or table describing Linux-specific tracking capabilities, such as monitoring changes to key configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or Linux service/daemon changes.
- Provide Linux-specific examples or screenshots where appropriate, especially in sections that currently focus on Windows (e.g., registry tracking).
- Clarify in the registry section that this feature is Windows-only, and provide a parallel explanation for what is tracked on Linux systems.
- Ensure that Linux and Windows examples are presented with equal prominence throughout the documentation.
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, particularly in the section on setting up a local SQL Server instance using Docker. PowerShell scripts are provided for database setup and validation, with no equivalent Bash or shell examples for Linux/macOS users. The instructions and troubleshooting steps reference Windows tools and folder structures first, and do not offer explicit Linux/macOS alternatives. While Docker is cross-platform, the use of PowerShell and lack of Bash examples creates friction for non-Windows users.
Recommendations
- Provide Bash/zsh shell script equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
- Explicitly mention that the Docker setup works on Linux/macOS, and clarify any OS-specific differences (such as file paths or Docker command syntax).
- Add troubleshooting guidance for Linux/macOS users, including how to locate the mssql-tools folder and run sqlcmd.
- Ensure that instructions for editing files (like local.settings.json) and running Azure Functions Core Tools are OS-neutral or include platform-specific notes.
- Where possible, show both Windows and Linux/macOS command examples side-by-side.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers Azure App Service plans for both Windows and Linux, with most sections being OS-neutral. However, the 'Managed Instance on Azure App Service (preview)' section is Windows-only and is described before any Linux-specific equivalents (if any exist), and Windows-specific features (like PowerShell scripts, RDP, IIS customization) are mentioned without Linux alternatives. The rest of the page is balanced, but Windows features are highlighted first in the Managed Instance section.
Recommendations
- Clearly label Windows-only sections (such as Managed Instance) to avoid confusion.
- If Linux equivalents exist (e.g., for OS customization, networking, or storage), mention them or link to relevant documentation.
- Add a brief note in the Managed Instance section clarifying that Linux users should refer to other hosting options.
- Ensure that links to pricing and feature tables include both Windows and Linux details.
- Consider adding a summary table comparing Windows and Linux plan features/capabilities.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides troubleshooting steps for Application Gateway for Containers with a clear focus on cross-platform usage. However, in the section for collecting logs, Windows-specific CLI examples (using findstr) are presented alongside Linux (using grep), with Windows shown second. The overall guidance is mostly platform-neutral, but the presence of Windows-specific command examples and explicit tab separation for Windows/Linux indicates some Windows bias.
Recommendations
- Ensure Linux and macOS examples are given equal prominence and clarity as Windows examples.
- Consider providing macOS-specific notes if there are any differences from Linux.
- Where possible, present platform-neutral commands first, and only add platform-specific notes where necessary.
- If using tabbed examples, ensure both tabs are equally detailed and easy to find.
- Add a brief note clarifying that most commands work on both Linux and macOS, and highlight any exceptions.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but PowerShell examples are presented first and in greater detail. The CLI examples are present and use Bash-compatible syntax, ensuring Linux parity. However, there are no explicit Linux/macOS-specific notes or examples, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. The portal instructions are platform-neutral, but the ordering and emphasis on PowerShell suggest a mild Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by Linux/macOS users.
- Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Consider including sample Bash scripts or referencing Linux/macOS terminal usage where relevant.
- Mention that PowerShell Core is available cross-platform, but Azure CLI is generally more native for Linux/macOS users.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown immediately after bash, and the note about CLI usage mentions PowerShell before bash. There are no Windows-only tools or patterns, but the ordering and explicit inclusion of PowerShell examples may subtly prioritize Windows users. All tools and workflows (Azure CLI, Azure Developer CLI, Visual Studio Code) are cross-platform, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Alternate the order of bash and PowerShell examples, or present bash first to match the default shell on Linux/macOS.
- Clarify that all CLI commands work equally well on Linux/macOS, and explicitly mention cross-platform compatibility.
- Consider adding a brief section or callout for Linux/macOS users, confirming that all steps are supported on their platforms.
- Where possible, use generic shell syntax or highlight bash as the default for cross-platform users.
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 PowerShell examples are shown immediately after Bash for each step, indicating a mild Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is present, ensuring Linux parity. However, PowerShell formatting and variable assignment are highlighted, which may subtly prioritize Windows users.
Recommendations
- Clearly label Bash and PowerShell examples, possibly using tabs or headings for each platform.
- Consider showing Bash (Linux/macOS) examples first, or alternating order to avoid implicit prioritization.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows.
- Ensure that all CLI commands are cross-platform and do not rely on Windows-specific syntax or features.
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 mentioned alongside CLI throughout, and the PowerShell example is given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, even though Azure CLI is cross-platform. No Linux-specific tools or shell examples are provided, but the CLI example is sufficient for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider providing Bash shell context or notes for Linux/macOS users (e.g., file path conventions, uploading files to Cloud Shell).
- Clarify that PowerShell is optional and primarily for Windows users, while CLI works everywhere.
- Add a note about using Cloud Shell (which supports both Bash and PowerShell) for cross-platform parity.
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 the PowerShell example is given equal prominence to the CLI example. The prerequisites list Azure CLI before Azure PowerShell, but both are included. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands. The PowerShell example is Windows-centric, but Azure CLI is cross-platform. The portal instructions are platform-agnostic. The bias is minor, mainly due to the inclusion of PowerShell as a primary example and lack of explicit Linux guidance.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Add a note clarifying that PowerShell is available on Linux/macOS, or indicate that the PowerShell example is primarily for Windows users.
- Consider including a Bash shell example for Azure CLI usage to reinforce Linux parity.
- Mention any OS-specific considerations for file paths or authentication if relevant.
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 PowerShell examples are always shown immediately after Bash, and are labeled as 'Formatted for PowerShell' rather than as a distinct tab. This may slightly favor Windows users, especially since PowerShell is more common on Windows. However, Linux/macOS users are not blocked, as Bash examples are present and complete.
Recommendations
- Consider using tabbed code blocks for Bash and PowerShell to make it clearer for users to select their preferred shell.
- Explicitly mention that Bash examples are suitable for Linux/macOS and WSL users, while PowerShell examples are for Windows.
- Ensure that all examples are tested and work as shown on both Linux/macOS (Bash) and Windows (PowerShell).
- If possible, provide a short note about using Azure CLI in Cloud Shell, which supports both Bash and PowerShell.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence to CLI, and the PowerShell example is included directly after the CLI example. There is no explicit Linux/macOS bias, but the presence of PowerShell examples and references may create a slight Windows bias, as PowerShell is more commonly associated with Windows environments. However, Azure CLI is cross-platform and shown first, mitigating the impact.
Recommendations
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform use.
- Add a note clarifying that PowerShell Core (pwsh) is available on Linux/macOS, and the PowerShell example works there as well.
- Consider including Bash shell examples if relevant, or clarify that Azure CLI commands can be run in Bash on Linux/macOS.
- If possible, add a section or callout for Linux/macOS users to ensure parity and clarity.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides step-by-step instructions primarily using the Azure Portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no Windows-specific tools or patterns are prioritized. All examples and instructions are cross-platform (Azure Portal and Azure CLI), and the PowerShell mention is not exclusive or prioritized. There are no Windows-only examples, tools, or patterns, and Linux parity is maintained throughout.
Recommendations
- Ensure that all CLI examples are explicitly noted as cross-platform.
- If referencing PowerShell, clarify its platform compatibility (PowerShell Core runs on Linux/macOS).
- Consider adding a note that Azure CLI is available on Windows, Linux, and macOS for clarity.
- If possible, provide Bash shell script examples for Linux users in addition to Azure CLI commands.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and its example is given equal prominence. There is no explicit mention of Linux/macOS-specific tools or workflows, and PowerShell is presented as a standard option, which may create friction for Linux users who typically use Bash or other shells.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit instructions for installing and using it on those platforms.
- Mention that Azure PowerShell can be installed and used on Linux/macOS, or note its Windows-centric nature.
- Consider providing Bash shell examples alongside PowerShell where scripting is involved.
- Add a brief note about cross-platform compatibility for each tool, especially for CLI and PowerShell sections.
- If possible, include troubleshooting tips for Linux/macOS users (e.g., file path differences, authentication nuances).
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 generally cross-platform and does not focus on Windows-specific tools, commands, or patterns. However, in the 'Related content' section, the example for connecting virtual networks refers specifically to a PowerShell-based guide before any CLI or Linux-native alternatives, which is a minor instance of Windows-first ordering.
Recommendations
- In the 'Related content' section, add or reference equivalent guides for connecting virtual networks using Azure CLI or ARM templates, and consider listing these before or alongside the PowerShell example.
- Wherever PowerShell is referenced, ensure that Azure CLI or cross-platform alternatives are also mentioned, especially in introductory or example lists.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance, but Windows-specific information and examples are often presented first, and PowerShell commands are frequently included alongside Bash/Azure CLI. Windows tools and concepts (such as IIS, .NET Framework, and Windows directory paths) are referenced more prominently and in greater detail. Linux parity is generally maintained, but Windows bias is evident in ordering and depth.
Recommendations
- Ensure Linux and Windows sections are equally detailed, especially regarding persistent storage, environment variables, and diagnostic logging.
- Present Linux and Windows examples side-by-side or alternate which comes first to avoid 'windows_first' bias.
- Expand Linux-specific troubleshooting and advanced configuration guidance to match Windows depth.
- Where possible, provide Linux-native command-line examples (e.g., Bash, Docker) before PowerShell, or at least equally.
- Clarify when features or settings differ between Windows and Linux, and link to Linux-specific resources where available.
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 code examples for Azure CLI, Azure PowerShell, and the Azure portal. While both CLI and PowerShell are supported, PowerShell examples are included throughout, and in some sections, PowerShell is listed after CLI but before or alongside portal instructions. The presence of PowerShell examples and the 'devx-track-azurepowershell' metadata may indicate a slight Windows bias, as PowerShell is more commonly used on Windows (though it is cross-platform). However, all critical steps are covered with Azure CLI and portal instructions, ensuring Linux/macOS users can complete the migration without issue.
Recommendations
- Continue to ensure all examples are provided for both Azure CLI and PowerShell, with clear indication that PowerShell Core is cross-platform.
- Consider explicitly stating that Azure PowerShell examples work on PowerShell Core (available on Linux/macOS) to reduce perceived Windows bias.
- Where possible, list Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- If any step is only possible via PowerShell, provide alternative guidance or clarify platform requirements.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation generally provides cross-platform guidance for managing TLS/SSL certificates in Azure App Service, with most steps performed in the Azure Portal or using platform-agnostic tools (Azure CLI, OpenSSL). However, there are some signs of Windows bias: PowerShell examples are given alongside Azure CLI, and Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with Linux equivalents not explicitly described. In some automation and export scenarios, Windows tools are referenced first or exclusively.
Recommendations
- When mentioning certificate export using IIS or Certreq.exe, also provide explicit Linux/macOS alternatives (e.g., OpenSSL commands for exporting PFX from PEM/CRT and key files).
- In automation sections, ensure that Azure CLI examples are shown before PowerShell, or clarify that both are equally supported.
- Where screenshots or UI steps are shown, clarify that the process is the same across platforms, or note any OS-specific differences.
- Add links or notes for Linux/macOS users on how to generate and manage certificates using OpenSSL or other common tools.
- In the FAQ and automation sections, ensure parity by providing Bash/CLI scripts where PowerShell is shown.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
minor_windows_path_patterns
Summary
The documentation provides both Windows and Linux guidance for Azure App Service backups, but there are several subtle Windows biases. Windows paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are referenced first or exclusively in some sections. Kudu DebugConsole and FTP instructions use Windows-style paths. PowerShell is mentioned alongside Azure CLI, but Linux shell scripting is not. The documentation does mention Linux apps and containers, but Windows examples and terminology are often presented first or more prominently.
Recommendations
- Where file paths are referenced (e.g., %HOME%, D:\home\site\wwwroot), add Linux equivalents (/home/site/wwwroot) and clarify for cross-platform users.
- When describing access via Kudu DebugConsole or FTP, provide Linux path syntax and note differences for Linux-hosted apps.
- In the 'Automate with scripts' section, add Bash/shell scripting examples or clarify that Azure CLI works equally well on Linux/macOS.
- Review screenshots and instructions to ensure they are not Windows-centric, or add Linux-specific visuals where appropriate.
- Where environment variables are referenced, explain both Windows (%HOME%) and Linux ($HOME) conventions.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are prominent and often provided, which may imply a Windows bias. In some sections, PowerShell is listed before other options, and PowerShell-specific notes are included. The CLI examples are cross-platform, but PowerShell is not available on all Linux/macOS systems by default. The documentation does not exclusively use Windows tools, but PowerShell is emphasized more than necessary for a cross-platform audience.
Recommendations
- Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
- Clarify that PowerShell examples are optional and provide guidance for Linux/macOS users on installing PowerShell if needed.
- Where possible, provide Bash shell examples for Linux/macOS users, especially for token retrieval and scripting.
- Add explicit notes about cross-platform compatibility for each tool, highlighting CLI and ARM templates as platform-neutral.
- Review and balance the order and prominence of PowerShell and CLI examples to avoid implying Windows is preferred.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, ensuring parity for users on Linux, macOS, and Windows. However, PowerShell examples are given equal prominence throughout, and Windows-specific installation instructions for Helm (using winget) are presented before Linux instructions. There is a slight preference for Windows-first ordering and PowerShell-heavy patterns, but Linux users can complete all tasks without friction.
Recommendations
- Consider listing Linux installation instructions for Helm before Windows instructions, or present both equally.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where possible, highlight Bash usage for Azure CLI and Helm commands, reinforcing Linux/macOS parity.
- Ensure that any references to PowerShell are clearly marked as Windows-specific, and that Bash alternatives are always provided.
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 steps, but PowerShell examples are given equal prominence and are presented as a primary option alongside CLI. Azure PowerShell is a Windows-centric tool, and its inclusion as a first-class option (with full code blocks and tabs) may create friction for Linux/macOS users, especially since PowerShell is less commonly used on those platforms. However, all critical steps are covered with Azure CLI, which is cross-platform, and there are no Windows-only tools or commands required. The documentation does not exclusively mention Windows tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
- Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Present Azure CLI examples first in all tabbed sections to reinforce cross-platform parity.
- Add a note indicating that Azure CLI is available and supported on Windows, Linux, and macOS, while PowerShell is mainly for Windows.
- If possible, reduce PowerShell prominence or move it to a secondary position in tabbed examples.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are several areas where Windows is prioritized or Linux is underrepresented. Windows-specific tools and configuration steps (such as Visual Studio, PowerShell, and Windows CLI commands) are often mentioned before or more prominently than their Linux equivalents. Some examples and instructions are Windows-first, and Linux-specific guidance is sometimes relegated to tabs or brief notes. In a few places, Linux-specific deployment or configuration steps are referenced but not shown in full, and PowerShell is mentioned as a primary automation tool alongside Azure CLI, but Bash or Linux shell equivalents are not always provided.
Recommendations
- Ensure that all command-line examples (especially for deployment, configuration, and debugging) are shown for both Windows (PowerShell/CMD) and Linux (Bash), either side-by-side or in clearly labeled tabs.
- When listing tools or methods (e.g., Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell), avoid always listing Windows-centric tools first; alternate or group by OS.
- Where PowerShell is mentioned, provide Bash or shell script equivalents for Linux/macOS users.
- In sections where configuration or deployment steps are shown for Windows, ensure that Linux equivalents are equally detailed and visible.
- Explicitly call out any OS-specific limitations or differences, and provide links to Linux/macOS-specific guidance where appropriate.
- Review the order of presentation in tables and lists to avoid reinforcing a Windows-first perspective.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and the curl example is shown using Windows command prompt syntax first. However, all critical steps are covered for Linux/macOS users, and the tools and instructions are cross-platform.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or group them equally.
- Clarify that Maven and Visual Studio Code are cross-platform tools.
- Show curl examples using bash syntax, or note that curl works identically on all platforms.
- Consider adding explicit notes about cross-platform compatibility where relevant.
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, listing it before alternatives (e.g., Bash or Terminal), which subtly prioritizes Windows tools. There are no Linux/macOS-specific examples or explicit mentions of their usage, and screenshots are portal-based (cross-platform).
Recommendations
- Clarify that Azure CLI works on Windows, Linux, and macOS, and provide examples of opening a terminal on Linux/macOS (e.g., Bash, Terminal.app) alongside Windows PowerShell.
- Add a note in the PowerShell section that it is Windows-specific, and suggest Azure CLI as the recommended cross-platform alternative for Linux/macOS users.
- Consider providing Bash script examples for common tasks, or at least mention that Bash and other shells are supported for CLI commands.
- Reorder or balance the mention of command consoles so that Linux/macOS options are not secondary to Windows PowerShell.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (export), and uses 'cmd' syntax for Maven and curl commands, but does include Linux/macOS equivalents. No critical Windows-only tools or patterns are used, and Linux users can complete all steps.
Recommendations
- Present Linux/macOS environment variable instructions first, or side-by-side with Windows.
- Use generic shell syntax for build/run/test commands (e.g., 'mvn ...', 'curl ...') instead of 'cmd' block, or clarify that these commands work cross-platform.
- Explicitly state that all steps are cross-platform and provide any OS-specific caveats if needed.
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 (setx and PowerShell) before Linux/macOS (export), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the overall workflow is cross-platform, with Azure CLI used throughout. The bias is mostly in ordering and example prominence.
Recommendations
- Present Linux/macOS and Windows environment variable instructions side-by-side or in parallel sections, rather than Windows-first.
- Use generic shell commands (e.g., export) as the primary example, with OS-specific notes as needed.
- Explicitly mention that all steps can be performed on Linux/macOS unless there are exceptions.
- Consider removing or minimizing Windows-specific command prompt instructions unless they are essential.
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 deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence and are presented alongside CLI examples, which may imply a Windows bias since PowerShell is primarily used on Windows. Azure CLI is cross-platform, but PowerShell is not as commonly used on Linux/macOS, and no explicit Linux/macOS instructions or shell examples are provided.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying PowerShell examples are primarily for Windows users.
- Consider showing Azure CLI examples first, as they are more universally applicable.
- Optionally, provide bash shell script examples for Linux/macOS users.
- Mention that Azure CLI can be installed and used on all major operating systems.
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 provides a comprehensive reference for Azure Functions app settings, covering both Windows and Linux scenarios. However, there are minor signs of Windows bias: Windows-specific syntax (e.g., %HOME% in AzureWebJobs_TypeScriptPath) is used in examples, and some settings (like WEBSITE_NODE_DEFAULT_VERSION) are labeled 'Windows only' without immediately offering Linux equivalents or clarifying Linux alternatives. Additionally, when discussing tools for programmatic management of settings, Azure CLI and Azure PowerShell are mentioned, but Linux-native tools (such as Bash scripts or REST calls via curl) are not referenced. Most examples and explanations are OS-neutral, and Linux-specific settings are documented, but Windows terminology and patterns sometimes appear first or exclusively.
Recommendations
- Where settings are Windows-only, explicitly state Linux alternatives or clarify if not applicable.
- For settings like AzureWebJobs_TypeScriptPath, provide Linux path examples alongside Windows ones.
- When recommending tools for managing settings, mention Linux-native options (e.g., Bash/curl) in addition to Azure CLI and PowerShell.
- Ensure that examples and explanations for app settings consistently show both Windows and Linux syntax where relevant.
- Review the order of presentation for settings and examples to avoid defaulting to Windows-first unless the feature is Windows-only.