251
Pages Scanned
46
Pages Flagged
251
Changed Pages
18.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-13 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
46 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, especially SignTool, PowerShell, and Windows SDK. All setup instructions, prerequisites, and examples are Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives for Artifact Signing. The use of MSI installers, WinGet, and PowerShell commands further reinforces the Windows bias. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their setup is not detailed, and the primary walkthrough is Windows-only.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including how to use Artifact Signing with cross-platform tools.
- Document any available CLI or SDK-based signing workflows that work on Linux/macOS, or clarify platform limitations.
- Provide parity in setup steps for non-Windows environments, such as using .NET Core CLI, zip/tar installers, or alternative signing tools.
- Clarify in the prerequisites and introduction whether SignTool integration is Windows-only, and highlight cross-platform options where possible.
- Expand the GitHub Actions and Azure DevOps sections with step-by-step examples for Linux/macOS runners.
Create Pull Request
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there are several instances where Windows-specific tools, paths, and conventions are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, and Windows-specific environment variables. Some examples and explanations use Windows-centric terminology or tools (e.g., msbuild, Web Deploy/MSDeploy, applicationHost.config) without always providing Linux equivalents or parity. While Linux-specific sections (Oryx, Linux containers) are present, Windows examples and tools are often listed first or in greater detail. Some settings are described with Windows paths or behaviors, and Linux alternatives are not always equally explained.
Recommendations
- Ensure Linux examples and paths are provided alongside Windows examples, especially for environment variables referencing file paths.
- When mentioning Windows tools (e.g., msbuild, Web Deploy/MSDeploy), provide Linux alternatives or clarify if the feature is Windows-only.
- Balance the order of presentation so Linux and Windows are equally represented, or use neutral language where possible.
- Expand explanations for Linux-specific build automation (Oryx) and deployment scenarios to match the detail given for Windows/Kudu.
- Add explicit notes or tables indicating which settings are platform-specific, and provide links to Linux documentation where relevant.
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 is generally platform-neutral in its conceptual explanations, but the only linked tutorial for creating an autoscaling, zone-redundant Application Gateway uses Azure PowerShell. This may create friction for Linux/macOS users who typically use Azure CLI or ARM templates, and PowerShell is often associated with Windows environments.
Recommendations
- Add links or examples for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM/Bicep templates.
- Ensure that step-by-step guides and tutorials are available for Linux/macOS users, not just PowerShell/Windows.
- Where PowerShell is referenced, clarify that it is cross-platform, or provide alternative commands for CLI users.
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 mild Windows bias, primarily through the use of Azure PowerShell scripts and references to PowerShell Gallery for migration tasks. CLI examples are labeled as 'azurecli-interactive', but the commands shown are PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), which are not cross-platform Azure CLI commands. Additionally, the 'Next steps' section links first to a PowerShell-based tutorial for creating an autoscaling application gateway, rather than a cross-platform CLI or portal-based guide.
Recommendations
- Provide equivalent Azure CLI (az) commands for registration, migration, and management tasks alongside PowerShell examples.
- Clearly distinguish between Azure PowerShell and Azure CLI in code blocks and instructions.
- Offer Linux/macOS-friendly instructions and examples, especially for migration and setup tasks.
- Include links to portal-based tutorials or cross-platform guides in the 'Next steps' section.
- Ensure that PowerShell is not presented as the default or only option for critical operations.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page provides both Windows and Linux guidance for TLS upgrades, but Windows instructions are referenced first and in more detail (with links to registry settings and PowerShell cmdlets), while Linux guidance is limited to a Python script and OpenSSL references. Throughout the data retention and backup sections, Windows PowerShell cmdlets are used exclusively for examples and asset management, with no equivalent Linux CLI or scripting examples provided. This creates friction for Linux users, especially those managing Automation assets or DSC nodes, as they must infer or research Linux alternatives.
Recommendations
- Provide Linux CLI or scripting examples (e.g., Azure CLI, Bash) alongside PowerShell cmdlets for asset management, runbook export/import, and DSC node operations.
- Include links to Linux-specific documentation or tools where PowerShell cmdlets are referenced.
- Ensure Linux guidance is given equal prominence and detail, not just as a secondary note or after Windows instructions.
- Clarify when certain operations are Windows-only, and offer Linux alternatives when possible.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC permissions, but PowerShell is featured equally and referenced in automation FAQs. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows-specific export instructions are given, and PowerShell is listed alongside CLI for automation, but Linux alternatives are not always equally explained or referenced first.
Recommendations
- Provide Linux/macOS-specific instructions and examples wherever Windows tools (IIS, Certreq.exe, PowerShell) are mentioned, such as for certificate export.
- Ensure OpenSSL instructions are as detailed as Windows tool instructions, including troubleshooting and compatibility notes.
- Feature Azure CLI examples before PowerShell, as CLI is cross-platform.
- Add explicit guidance for Linux/macOS users in automation sections, including shell scripting and certificate management.
- Where screenshots or UI steps reference Windows-specific terminology, clarify that the steps are identical for Linux-hosted apps.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is generally cross-platform, describing App Service plans for both Windows and Linux. However, the Managed Instance section is Windows-only and presented without a Linux equivalent or alternative. Additionally, some links and feature tables (such as pricing details) default to Windows, and there are no Linux-specific examples or guidance for Linux users, which may create friction for those seeking parity.
Recommendations
- Clearly label Windows-only features (such as Managed Instance) and provide guidance or alternatives for Linux users where possible.
- Include links to Linux-specific documentation (e.g., App Service on Linux pricing details, feature support matrix).
- Add examples or notes for Linux App Service plans, especially where feature availability or configuration differs.
- Ensure that feature tables and plan comparisons explicitly state OS applicability, and avoid defaulting to Windows unless the feature is truly Windows-only.
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 demonstrates a moderate Windows bias. Windows-specific instructions and code samples (especially for certificate store access) are presented first and in greater detail, with C# and Java examples for Windows but only C# for Linux. Non-Windows languages (Node.js, PHP, Python, Java) are not covered with direct examples for Linux, and users are referred to external documentation. Windows certificate store patterns and tools are described in detail, while Linux approaches are less emphasized.
Recommendations
- Provide direct code examples for Linux for all major supported languages (Node.js, Python, Java, PHP), not just C#.
- Present Linux and Windows instructions/examples in parallel or with equal prominence, rather than Windows-first.
- Clarify any differences in certificate handling between Windows and Linux up front.
- Include more detailed guidance for Linux users on best practices for certificate storage and access.
- Where possible, avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, without offering equivalent CLI or Bash instructions. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool. Additionally, the PowerShell section appears before the Azure portal instructions, further emphasizing Windows-first bias. There are no examples using Azure CLI or Bash, which are cross-platform and preferred by many non-Windows users.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, alongside PowerShell.
- Include Bash script snippets or instructions where relevant.
- Present cross-platform (CLI) instructions before or alongside PowerShell examples.
- Explicitly note that PowerShell is available cross-platform, but recommend CLI for Linux/macOS users.
- Ensure tool recommendations (e.g., Excel, Power BI) are balanced with open-source or cross-platform alternatives.
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, there are instances where Windows-specific tools and concepts (such as references to Kerberos, NTLM, Service Principal Names, and IIS Windows Authentication) are mentioned without Linux equivalents or guidance. Additionally, troubleshooting and authentication examples reference Windows patterns first, with no mention of Linux alternatives for Kerberos or NTLM, potentially creating friction for Linux users.
Recommendations
- Add guidance or references for configuring Kerberos and NTLM authentication on Linux-based backend servers, or clarify if these features are Windows-only.
- When mentioning backend authentication troubleshooting, provide links or notes for Linux-based authentication mechanisms (e.g., Samba, MIT Kerberos, mod_auth_kerb for Apache).
- If IIS/Windows Authentication is referenced, clarify its scope and provide parity for popular Linux web servers (Apache, Nginx) where possible.
- Explicitly state if certain authentication features (NTLM, Kerberos passthrough) are only supported for Windows backends, to avoid confusion.
- Ensure troubleshooting guidance includes both Windows and Linux backend server log review instructions.
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 for configuring Azure Application Gateway TCP/TLS proxy demonstrates Windows bias by exclusively referencing Windows-based SQL Server VMs and recommending SQL Server Management Studio (SSMS) as the client tool, which is Windows-only. There are no examples or instructions for deploying a Linux-based SQL Server VM or connecting from Linux/macOS clients (e.g., using sqlcmd or Azure Data Studio). Windows-specific patterns and tools are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Add instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative to Windows Server.
- Include examples of connecting to the SQL Server backend using cross-platform tools such as sqlcmd or Azure Data Studio, which are available on Linux and macOS.
- Mention Linux/macOS client options and provide relevant screenshots or command-line examples.
- Clarify that the procedure is applicable to both Windows and Linux SQL Server VMs unless there are Azure limitations.
- If using SSMS is not required, recommend cross-platform tools in the 'Connect to the SQL server' section.
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
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and downloadable scripts provided in PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS shell examples or instructions provided. The guidance assumes the user is operating in a PowerShell environment, which is native to Windows but only optionally available on Linux/macOS.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration and traffic migration.
- Include Bash shell examples and instructions for Linux/macOS users, especially for tasks like downloading certificates, running scripts, and managing resources.
- Clarify that Azure Cloud Shell supports both PowerShell and Bash, and offer guidance for users who prefer Bash.
- Explicitly state platform requirements for the scripts, and if PowerShell is required, provide installation instructions for PowerShell Core on Linux/macOS.
- Where scripts are only available in PowerShell, consider developing and publishing cross-platform alternatives or note any limitations.
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 page provides configuration instructions and examples for mutual authentication on Azure Application Gateway, with a clear emphasis on Azure PowerShell. PowerShell examples are shown first and in more detail, while Azure CLI examples are present but less comprehensive. There are no Linux/macOS-specific instructions or examples, and the 'Next steps' section directs users to a PowerShell-focused guide, potentially creating friction for Linux/macOS users who rely on Azure CLI or ARM templates.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step instructions for all major configuration tasks.
- Add explicit guidance for Linux/macOS users, such as using Azure CLI or ARM/Bicep templates for mutual authentication configuration.
- In the 'Next steps' section, include links to CLI and ARM template guides, not just PowerShell.
- Where possible, clarify that PowerShell is cross-platform, but also highlight CLI/ARM options for users who prefer them.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions provided in PowerShell. There are no Linux/macOS equivalents or CLI alternatives given, and Windows patterns (e.g., certificate creation, file paths) are used throughout. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-only cmdlets.
Recommendations
- Provide Azure CLI examples alongside PowerShell for each step, as Azure CLI is cross-platform.
- Offer Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL).
- Use generic file paths or note differences for Linux/macOS users.
- Explicitly mention that PowerShell Core is available cross-platform, and clarify which steps require Windows-only tools.
- Link to relevant Linux/macOS documentation for certificate management and Azure resource creation.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently references Azure PowerShell scripts as the primary or sole migration tooling, with no mention of Azure CLI, Bash, or cross-platform alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity guidance. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration steps, especially for configuration and public IP retention.
- Explicitly state whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation guidance if so.
- Include Bash or shell script examples where possible, or link to community-supported alternatives.
- Clarify any limitations or requirements for non-Windows users in the migration process.
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 examples, with all certificate management operations (creation, retrieval, deployment) shown exclusively via PowerShell. There are no Linux/bash/CLI examples for certificate management, and PowerShell is presented first in most sections. While Python examples are provided for runbooks, all administrative tasks are PowerShell-centric, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for certificate creation, retrieval, and management where possible.
- Include bash or shell script snippets for uploading certificates, especially for users on Linux/macOS.
- Clarify if PowerShell examples are cross-platform (PowerShell Core), or provide guidance for Linux/macOS users.
- Present examples in a more balanced order (e.g., CLI, PowerShell, Python) rather than always PowerShell first.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples, parameter handling, and workflow descriptions are based on PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). There is minimal coverage for Python runbooks, and no examples or guidance are provided for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. The SDK and REST API sections are platform-neutral, but the practical examples and instructions are overwhelmingly Windows/PowerShell-oriented.
Recommendations
- Provide CLI (az) examples for starting runbooks and passing parameters, which are cross-platform.
- Add explicit guidance and examples for Linux/macOS users, such as using Bash scripts or Python to call the REST API or SDK.
- Expand the Python runbook section with parameter passing examples and clarify how Linux users can invoke runbooks.
- Mention that PowerShell Core (pwsh) is available on Linux/macOS and provide examples using it, or clarify any limitations.
- Balance the order of examples so that platform-neutral methods (REST API, SDK, CLI) are presented before or alongside PowerShell.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages (such as Bash or Python). All migration instructions and runbook examples are PowerShell-based, and references to gallery scripts are exclusively for PowerShell. While the page states applicability to both Linux and Windows VMs, Linux users are left without platform-native guidance or parity in scripting options.
Recommendations
- Provide Bash or Python script examples for asset migration, or clarify if PowerShell Core (cross-platform) is required and supported for Linux users.
- Explicitly mention whether PowerShell Core can be used on Linux for these migration tasks, and provide installation instructions if so.
- Add guidance or links for Linux users to install and use PowerShell Core, or offer alternative migration approaches using Azure CLI or REST API.
- Include notes or examples for running migration scripts on Linux Hybrid Runbook Workers, not just Windows.
- Clarify any limitations or requirements for Linux users in the prerequisites section.
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 and module references are for PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting. The process for creating credential assets and managing Azure resources is only shown using PowerShell cmdlets, and the 'Windows PowerShell' terminology is used explicitly. Linux/macOS users are not provided with equivalent instructions or examples.
Recommendations
- Add Azure CLI examples for credential asset creation and authentication flows where possible.
- Clarify which steps are PowerShell-specific and provide Bash or cross-platform alternatives if supported.
- Use 'PowerShell' (which is cross-platform) instead of 'Windows PowerShell' unless referring to Windows-only modules.
- Explicitly mention platform compatibility for each approach, and link to Linux/macOS guidance where relevant.
- Provide a note if certain features are only available via PowerShell, and suggest alternatives for Linux/macOS users.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tools and patterns. All CLI examples are provided in PowerShell, with explicit references to Windows PowerShell and PSCredential objects. There are no examples or guidance for Linux/macOS shell environments (e.g., Bash, CLI), nor is there mention of cross-platform alternatives for credential management outside of Python runbooks. The PowerShell/Windows approach is presented first and in greater detail than Python, and no parity is offered for Linux-native scripting or automation tools.
Recommendations
- Add Azure CLI examples for credential management tasks, where supported.
- Clarify whether PowerShell examples work cross-platform (PowerShell Core on Linux/macOS) or are Windows-only.
- Explicitly mention any limitations or alternatives for Linux/macOS users, especially for runbook authoring and credential retrieval.
- Provide Bash or other shell script examples if possible, or state that only PowerShell and Python are supported for these operations.
- Reorder or balance example sections so Python and PowerShell are presented with equal prominence.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent
...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation covers both Windows and Linux support for Azure Change Tracking and Inventory, but certain sections (notably registry key tracking) are Windows-specific and lack equivalent Linux examples or discussion. Windows terminology and features (registry keys, Windows services) are described in detail, while Linux-specific features (such as daemon/service tracking or configuration file monitoring) are not given the same depth or examples. The order of presentation often places Windows concepts first or exclusively.
Recommendations
- Add explicit examples of Linux daemon/service tracking, including typical monitored files or directories (e.g., /etc/systemd/system, /etc/init.d).
- Provide a table or section listing Linux-specific configuration files or directories commonly tracked, similar to the Windows registry key table.
- Clarify which features are Windows-only and which are cross-platform, and provide parity in explanations and screenshots.
- Include Linux command-line examples or references where appropriate, especially for enabling and configuring Change Tracking on Linux VMs.
- Add screenshots or walkthroughs for Linux file change tracking, not just Windows.
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 a moderate Windows bias in the local SQL Server setup section. PowerShell is used exclusively for scripting the Docker-based SQL Server instance, and no equivalent Bash or shell script is provided for Linux/macOS users. The troubleshooting and validation steps also assume PowerShell usage. While Docker and SQL Server are cross-platform, the examples and instructions are presented primarily from a Windows/PowerShell perspective, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash shell script examples for setting up the SQL Server Docker container, creating the database, and validating the installation.
- Explicitly mention that all Docker commands can be run from Bash on Linux/macOS, and show the syntax differences where relevant.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, Docker group membership).
- Where PowerShell is used for variable assignment and command composition, show how to do the same in Bash.
- Clarify that Visual Studio Code and Azure Functions Core Tools are fully supported on Linux/macOS, and link to installation guides for those platforms.
Azure Functions
Azure Functions Core Tools reference
...cles/azure-functions/functions-core-tools-reference.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is generally cross-platform, but there are several areas where Windows-specific tools, behaviors, and issues are mentioned before Linux equivalents or without Linux parity. Examples include references to PowerShell managed dependencies, Windows build issues for Python apps, and default behaviors that assume Windows environments (such as certificate creation for HTTPS). Windows-specific terminology (like 'command prompt') and tools are referenced more frequently, and Windows issues are discussed in detail, while Linux/macOS guidance is less prominent.
Recommendations
- Ensure Linux/macOS-specific instructions and caveats are provided wherever Windows-specific issues are mentioned (e.g., Python packaging/build guidance).
- Where Windows tools or behaviors are referenced (such as certificate creation, command prompt, PowerShell), add equivalent Linux/macOS instructions or clarify cross-platform differences.
- When discussing managed dependencies or worker runtimes, clarify Linux/macOS support and provide examples for those platforms.
- Review the order of examples and tool references to avoid consistently mentioning Windows first; alternate or group by platform where appropriate.
- Add explicit notes or links for Linux/macOS users where friction or workarounds are required.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but PowerShell examples are presented first and in greater detail. Portal instructions are generic and cross-platform, but scripting guidance gives prominence to Windows/PowerShell usage before CLI, which is more native to Linux/macOS. No Linux-specific tools or patterns are mentioned, and there are no bash or shell script examples beyond Azure CLI.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and link to installation guides for each.
- Consider adding bash or shell script examples for common tasks, or reference how to use Azure CLI in shell scripts.
- Add a note clarifying that PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI examples for both bash and PowerShell throughout, with PowerShell examples consistently shown after bash. There is no exclusive use of Windows/PowerShell, nor are Windows tools or patterns mentioned before Linux equivalents. The Azure CLI is cross-platform, and the documentation explicitly notes that commands can run in either shell, providing syntax for both. No Linux/macOS functionality is missing.
Recommendations
- Continue providing both bash and PowerShell examples to maintain parity.
- Consider alternating the order of examples (sometimes showing PowerShell first) to avoid any perception of Windows-first bias.
- Explicitly state in the prerequisites that all CLI commands are supported on Linux, macOS, and Windows for clarity.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are presented immediately after Bash in every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'). This creates a mild Windows bias, as Linux/macOS users may perceive the PowerShell examples as unnecessary or confusing. However, Bash examples are present and complete, so Linux users can follow the instructions without issue.
Recommendations
- Consider grouping Bash and PowerShell examples under explicit tabs or sections labeled 'Linux/macOS (Bash)' and 'Windows (PowerShell)' for clarity.
- If possible, present Bash examples first, as Azure CLI is cross-platform and Bash is the default shell for many users.
- Add a brief note explaining that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
- Ensure that Bash examples are always complete and not dependent on PowerShell-specific syntax.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is presented as a primary option alongside CLI, and there is no mention of Linux/macOS-specific shell environments or considerations. The instructions for uploading files reference Azure Cloud Shell generically, but do not clarify OS-specific steps or highlight Bash usage. PowerShell is a Windows-centric tool, though it is now cross-platform; its prominence may create friction for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash-specific instructions or examples where relevant.
- Clarify that PowerShell is available cross-platform, but highlight Bash as the default shell for Linux/macOS users in Azure Cloud Shell.
- Consider adding a note or section for Linux/macOS users, including tips for file uploads and environment setup.
- Ensure that CLI examples are shown first or equally with PowerShell to avoid Windows-first impression.
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 provides Azure CLI and Azure PowerShell examples for disabling routing to a regional gateway, but only mentions PowerShell as an alternative to Azure CLI. There are no Linux/macOS-specific examples or explicit parity guidance. Azure portal instructions are platform-neutral, but command-line guidance could imply Windows bias by referencing PowerShell before other options.
Recommendations
- Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for automation regardless of OS.
- Add Bash shell examples or clarify that Azure CLI commands are identical on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, or provide links to Linux/macOS installation guides for PowerShell if referenced.
- Where PowerShell is referenced, also reference Bash or other common shells to reinforce parity.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally accessible.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given alongside Bash for every command, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may create a perception of Windows bias. There are no Linux-specific tools or workflows mentioned, but Bash examples are present, ensuring Linux parity.
Recommendations
- Ensure Bash examples are shown first, as Bash is the default shell for most Linux and macOS users.
- Clearly label Bash and PowerShell sections, possibly using tabs or headings, to avoid confusion.
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS, and PowerShell for Windows.
- If possible, provide a single Bash example unless there is a PowerShell-specific need.
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 alternative alongside CLI, and there is no mention of Linux-specific shell environments (e.g., Bash) or macOS. The prerequisites section includes Azure PowerShell requirements, which are more relevant to Windows users, and PowerShell is shown as a first-class option, potentially creating friction for Linux/macOS users who may prefer Bash or other shells.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell examples are provided.
- Add Bash shell examples or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- In prerequisites, highlight cross-platform installation instructions for Azure CLI and PowerShell Core.
- Consider listing Azure CLI (Bash) examples first, as CLI is more universally accessible.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for backup and restore operations, with PowerShell examples appearing before CLI and REST examples. While Azure CLI and REST API options are also documented, PowerShell is given prominence and more detailed scripting, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer Bash scripting. However, all critical operations are also covered via Azure CLI and REST, ensuring Linux parity.
Recommendations
- Present Azure CLI examples before PowerShell or in parallel, to avoid Windows-first ordering.
- Expand Azure CLI sections to include managed identity scenarios, matching the detail provided in PowerShell examples.
- Explicitly note that Azure CLI and REST API are fully cross-platform and recommended for Linux/macOS users.
- Consider adding Bash scripting examples for common automation scenarios.
- Clarify that PowerShell is not required for Linux/macOS users and highlight CLI/REST parity.
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 CLI and Azure PowerShell, with PowerShell being Windows-centric. Both tools are cross-platform, but PowerShell is more commonly associated with Windows, and its inclusion may signal a Windows bias. The structure presents Azure CLI and PowerShell examples separately, but PowerShell is given equal prominence, which may create friction for Linux/macOS users. No Linux-specific shell or tool examples (e.g., Bash scripting) are provided, and PowerShell requirements are listed alongside CLI prerequisites.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide guidance for Linux/macOS users if needed.
- Consider adding Bash or shell script examples for Linux/macOS users, or explicitly state that Azure CLI commands are suitable for all platforms.
- Reorder examples to show Azure CLI first, as it is more universally available across platforms.
- Add a note explaining the parity between Azure CLI and PowerShell 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 example commands for Azure CLI and Azure PowerShell in parallel, but PowerShell examples are always present and often shown after CLI, which can be interpreted as a slight Windows-first bias. There is no explicit Linux/macOS example section, and PowerShell is a Windows-native tool (though available cross-platform). However, all critical steps are covered with Azure CLI, which is fully supported on Linux/macOS, and there are no tasks that require Windows-only tools.
Recommendations
- Clarify in the introduction or relevant sections that Azure CLI commands are fully supported on Linux and macOS.
- Consider adding a short note that PowerShell Core is available cross-platform, or clarify that the PowerShell examples work on all supported platforms.
- If possible, add explicit bash/shell script examples for common Linux/macOS workflows, or at least mention that Azure CLI is the recommended tool for Linux/macOS users.
- Ensure that the order of examples does not consistently favor Windows tools (e.g., sometimes show CLI before PowerShell, or group them as 'cross-platform').
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 for all critical steps, ensuring parity for Windows and Linux users. However, PowerShell examples are given equal prominence throughout, and Windows-specific installation instructions for Helm (using winget) are presented before Linux instructions. The Azure CLI examples are cross-platform, but the documentation sometimes leads with Windows/PowerShell options or mentions Windows tools first.
Recommendations
- Ensure Linux installation instructions for tools (like Helm) are presented before or alongside Windows instructions, rather than after.
- Clearly state that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Consider adding explicit Bash shell examples for steps where Azure CLI is used, to reinforce Linux parity.
- Where PowerShell is used, clarify its cross-platform availability, but note that Linux users may prefer Bash.
- Review tab ordering and section headings to avoid implicit Windows-first bias.
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 clear parity between Linux and Windows users in log collection. However, the Windows example (using 'findstr') is presented after the Linux example (using 'grep'), and both are given equal prominence. All other commands and instructions are platform-neutral (kubectl, helm), and there are no Windows-specific tools or patterns used exclusively. The bias is minor, limited to the ordering of examples and the explicit inclusion of Windows/PowerShell syntax.
Recommendations
- Continue to provide both Linux and Windows command examples for log filtering.
- Consider presenting both examples side-by-side or in a tabbed interface to avoid implicit prioritization.
- Ensure that any future troubleshooting steps involving file manipulation or scripting also include macOS/Linux equivalents if Windows-specific commands are used.
- Explicitly mention macOS compatibility where relevant, as macOS users typically use the same commands as Linux.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on
...pplication-gateway-for-containers-alb-controller-addon.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured as a first-class option in several sections, and Windows-specific PowerShell commands are given equal prominence to cross-platform CLI commands. In some sections (e.g., prerequisites, enabling workload identity, deleting resource group), PowerShell examples are shown immediately after CLI, which may subtly prioritize Windows workflows. However, all critical tasks can be completed using Azure CLI, which is cross-platform, and kubectl is used for cluster verification, ensuring Linux/macOS parity.
Recommendations
- Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Where possible, show Azure CLI examples first, as it is cross-platform.
- Add explicit notes indicating that Azure PowerShell commands are for Windows environments, and CLI commands are for all platforms.
- Ensure that all PowerShell examples are matched by equivalent CLI examples, and vice versa.
- Consider removing PowerShell examples from sections where CLI is sufficient, or move them to a separate appendix or tab for Windows users.
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 setting instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific commands (setx, PowerShell) with detailed restart instructions. Linux/macOS instructions are present and correct, but are listed after Windows examples. The use of Visual Studio Code is mentioned as cross-platform, and all core Java/Maven steps are platform-neutral.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before or alongside Windows examples, rather than after.
- Clarify that all commands (except setx) are cross-platform, and highlight any platform-specific caveats.
- Consider grouping environment variable instructions by platform with clear headings, or use tabs for each OS.
- Ensure validation steps (e.g., printing env vars) are shown for all platforms, not just Windows.
- Mention alternative editors (e.g., IntelliJ IDEA, Eclipse) alongside Visual Studio Code for broader parity.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides monitoring instructions for Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. In the CLI section, Windows PowerShell is mentioned as the primary example of a command console, and PowerShell instructions are given their own dedicated section. The CLI instructions mention PowerShell first as a local console option, and the PowerShell section explicitly instructs users to open a Windows PowerShell command window. There are no Linux/macOS-specific shell examples or explicit mentions of Bash or other Linux-native tools. However, the Azure CLI instructions are cross-platform and can be used on Linux/macOS, and the portal instructions are platform-agnostic.
Recommendations
- In the CLI section, mention Bash or Terminal as alternative consoles for Linux/macOS users, not just Windows PowerShell.
- Clarify that Azure CLI commands work on all platforms (Windows, Linux, macOS) and provide Bash/Terminal as an example.
- In the PowerShell section, note that PowerShell Core is cross-platform, and provide guidance for Linux/macOS users if relevant.
- Consider adding explicit Bash shell examples or notes for Linux/macOS users where appropriate.
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 setting instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). All major steps and examples are cross-platform, and Linux/macOS instructions are present, but Windows commands are listed first. No Windows-only tools or PowerShell-heavy bias is present.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows (cmd/PowerShell), or group them equally.
- Explicitly state that all steps are cross-platform and supported on Windows, Linux, and macOS.
- Consider adding a note that Maven and Java are cross-platform, and that the instructions apply regardless of OS.
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, and uses Windows-specific commands (setx, PowerShell syntax) with Linux/macOS instructions given last. All other steps and tooling are cross-platform, and the Azure CLI is used for resource management, which is available on all platforms.
Recommendations
- Present Linux/macOS and Windows environment variable instructions side-by-side or in tabs, rather than listing Windows first.
- Use cross-platform shell commands (e.g., export) as the primary example, or clarify that the order is arbitrary.
- Explicitly mention that all Azure CLI commands work on all platforms.
- Consider adding a note that the tutorial is fully cross-platform and tested on Linux/macOS as well as Windows.
Azure Cache For Redis
Deploy Azure Cache for Redis using Bicep
...s/azure-cache-for-redis/redis-cache-bicep-provision.md
Low Priority
View Details â
Detected Bias Types
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 shown alongside CLI examples in all sections, and PowerShell is a Windows-centric tool. The CLI examples are cross-platform, but PowerShell is presented as an equal option, which may create minor friction for Linux/macOS users. There is no explicit Linux/macOS bias or missing Linux example, but the presence of PowerShell throughout may subtly favor Windows users.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples first in each section to emphasize platform neutrality.
- Add a note indicating that PowerShell is primarily for Windows users, while CLI works on all major OSes.
- Optionally, provide Bash shell script examples for common tasks to further improve Linux parity.
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 (setx, PowerShell) before Linux/macOS (export), and uses 'cmd' syntax for build/run/curl commands, but does include Linux/macOS equivalents. No critical steps are Windows-only, and Linux users can complete the quickstart.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or side-by-side.
- Use generic shell syntax (e.g., $ export ...) for commands where possible, or clearly label OS-specific sections.
- For build/run/curl commands, clarify that these work on all platforms with Maven and curl installed.
- Consider using code block labels like 'bash', 'powershell', 'cmd', etc., to improve clarity.
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
powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for running C# Azure Functions in an isolated worker process, but there are several instances where Windows tools, commands, and examples are mentioned first or exclusively. Windows-specific tools (Visual Studio, PowerShell) are often listed before their Linux equivalents, and some CLI instructions are Windows-centric. However, Linux options (Azure CLI, Visual Studio Code, containers) are also covered, and critical tasks can be completed on Linux/macOS. The bias is mostly in ordering and tool emphasis, not in functional gaps.
Recommendations
- Ensure Linux and macOS examples are presented alongside Windows examples, ideally in parallel or with equal prominence.
- When listing tools or methods, alternate the order or use neutral phrasing (e.g., 'Visual Studio Code or Visual Studio').
- Add explicit Linux/macOS instructions where only Windows commands are shown, especially for PowerShell or Visual Studio steps.
- Highlight cross-platform tools (Azure CLI, VS Code, Core Tools) before Windows-only tools.
- Add tabs or sections for Linux/macOS where only Windows instructions are present.
- Clarify when a tool or step is Windows-only, and provide Linux/macOS alternatives where possible.
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
powershell_heavy
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 settings and examples (such as WEBSITE_NODE_DEFAULT_VERSION, AzureWebJobs_TypeScriptPath using Windows-style paths, and PowerShell settings) are presented without always giving Linux equivalents or alternatives. Windows tools (Azure PowerShell) are mentioned before Azure CLI in some guidance. Some examples (e.g., path syntax) use Windows conventions first. Overall, Linux and macOS users can complete all tasks, but may encounter minor friction or need to adapt examples.
Recommendations
- Where path examples are given (e.g., AzureWebJobs_TypeScriptPath), provide both Windows and Linux/macOS syntax.
- When referencing tools for managing app settings, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform.
- For settings that are Windows-only, clearly label them as such and provide Linux alternatives or clarify if not applicable.
- Ensure that examples and sample values are balanced between Windows and Linux (e.g., WEBSITE_TIME_ZONE shows both, which is good).
- Review PowerShell-specific sections to ensure Linux users are not confused; clarify when settings are only relevant to PowerShell workloads.
Azure Functions
Deployment technologies in Azure Functions
...s/azure-functions/functions-deployment-technologies.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides a broad overview of Azure Functions deployment technologies, but there is a mild bias toward Windows in the ordering and examples. Windows-specific tools (Visual Studio, Windows-only deployment options) are often mentioned first or exclusively, and some deployment methods (Source control, Local Git, FTPS) are labeled as 'Windows-only' without Linux equivalents or workarounds being clearly described. While Linux options are present and discussed, Windows tools and patterns (such as Kudu, Visual Studio) are referenced before their Linux counterparts, and Linux-specific instructions are sometimes less detailed.
Recommendations
- Ensure Linux deployment methods are given equal prominence and ordering in tables and lists.
- Provide explicit Linux/macOS command-line examples and tool recommendations alongside Windows/Visual Studio instructions.
- Clarify alternative Linux workflows for Windows-only deployment technologies (e.g., Source control, Local Git, FTPS), or link to relevant Linux documentation.
- Add more detail about Linux-specific deployment nuances, especially for remote build, container deployments, and troubleshooting.
- Where Windows tools are referenced (e.g., Visual Studio), also mention cross-platform tools (e.g., VS Code, Azure Functions Core Tools) with equal depth.
Azure Functions
Azure Functions networking options
...ticles/azure-functions/functions-networking-options.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI, PowerShell, and portal examples for configuring Azure Functions networking, but PowerShell examples are included alongside CLI and portal, which may favor Windows users. The Hybrid Connections feature is Windows-only, but this is clearly stated and justified. In some sections, Windows and Linux subnet sizing recommendations are given, but Windows is mentioned first. Overall, Linux parity is mostly maintained, but minor ordering and example biases exist.
Recommendations
- When providing automation examples, ensure that Azure CLI (cross-platform) examples are always present and shown before PowerShell.
- Explicitly note Linux/macOS compatibility in automation sections.
- Where subnet sizing recommendations are given, list Linux and Windows equally or alternate order.
- Consider adding bash or shell script examples where relevant.
- Ensure screenshots and portal instructions are not Windows-centric (they appear neutral here).