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-12 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
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with all examples and instructions tailored for Windows environments. There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and Windows-centric patterns (e.g., certificate creation, file paths) are used throughout.
Recommendations
- Add Azure CLI examples alongside PowerShell for each step, especially for resource creation and configuration.
- Provide Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Use generic file paths or note platform-specific differences where relevant.
- Mention that Azure PowerShell can be used cross-platform, but highlight any Windows-only cmdlets or steps.
- Consider linking to Linux/macOS tutorials or documentation for similar tasks.
Create Pull Request
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration instructions and examples for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell. PowerShell examples are given first and in more detail, while Azure CLI examples are present but less comprehensive. There is no mention of Linux-specific tools or workflows, and the 'Next steps' section directs users to a PowerShell-focused guide, omitting Linux or macOS parity. This creates friction for Linux/macOS users who may prefer CLI or ARM/Bicep templates.
Recommendations
- Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions.
- Provide ARM template and Bicep configuration examples for mutual authentication, as these are cross-platform.
- Include explicit guidance for Linux/macOS users, such as using Azure CLI or REST API, and link to relevant documentation.
- In 'Next steps', offer links to both PowerShell and CLI/ARM/Bicep guides, not just PowerShell.
- When referencing certificate extraction or management, mention cross-platform tools (e.g., OpenSSL) and provide examples for Linux/macOS.
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
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS (export), and uses Windows-specific commands (setx, PowerShell syntax) with only a brief Linux/macOS example. The Windows instructions are more detailed (mentioning restart of command prompt), while the Linux/macOS instructions are minimal and lack equivalent detail. There are no screenshots or step-by-step UI instructions that are OS-specific, but the CLI and environment variable setup sections show a clear Windows-first bias.
Recommendations
- Present Linux/macOS and Windows environment variable instructions side-by-side or in tabs, giving equal prominence and detail.
- For each command, provide both Windows (cmd, PowerShell) and Linux/macOS (bash/zsh) equivalents, with notes about session persistence (e.g., setx vs export).
- Clarify that 'export' only sets variables for the current shell session, and suggest adding to ~/.bashrc or ~/.zshrc for persistence, mirroring the Windows 'setx' behavior.
- Add Linux/macOS-specific screenshots or notes where relevant, or explicitly state when steps are identical across platforms.
- Consider using cross-platform tools (like Azure CLI) for all automation steps, and avoid assuming a Windows shell as default.
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 given equal prominence and referenced in multiple places. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux alternatives are not described in detail. Windows-specific certificate generation/export methods are referenced before Linux/OpenSSL equivalents in some sections. However, OpenSSL is covered for Linux/macOS users, and Azure CLI is included for automation. The overall bias is moderate, with some friction for Linux/macOS users but no critical gaps.
Recommendations
- Ensure Linux/macOS certificate export instructions (using OpenSSL) are as detailed and prominent as Windows/IIS instructions.
- Where PowerShell is referenced, always provide equivalent Azure CLI or Bash examples, and consider showing CLI first.
- Clarify that OpenSSL steps are suitable for Linux/macOS, and link to official OpenSSL documentation for further guidance.
- Add troubleshooting tips for Linux/macOS users, such as handling certificate chain issues or .pfx compatibility.
- Review FAQ and automation sections to ensure Linux/macOS parity in scripting guidance.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logging, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The PowerShell method is presented before portal-based instructions, and no mention is made of Azure CLI or other cross-platform tools. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic solutions.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used by Linux/macOS users.
- Present CLI/Bash examples alongside PowerShell, or before PowerShell, to ensure parity and inclusivity.
- Explicitly mention that PowerShell is Windows-centric and provide guidance for Linux/macOS users.
- Include references to relevant tools or scripts for Linux/macOS environments, such as Bash or Python.
- Where possible, use generic REST API examples or links to Azure REST documentation.
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 loading) are presented first and in greater detail, with C# and Java examples focused on the Windows certificate store. Linux-specific guidance is less prominent and less detailed, with non-Windows languages (Node.js, PHP, Python) being deferred to external documentation. The use of Windows tools and patterns (certificate store, environment variables) is emphasized, and Linux parity is only partially addressed.
Recommendations
- Provide Linux-specific code samples for all supported languages (e.g., Java, Python, Node.js, PHP) directly in the documentation, not just C#.
- Present Windows and Linux instructions/examples in parallel or in clearly separated tabs, rather than Windows-first.
- Expand explanations of Linux certificate handling, including how to access certificates from the file system in common languages.
- Clarify any differences in certificate management between Windows and Linux environments up front.
- Link to or include sample scripts for Linux shell (bash) where relevant, not just Azure CLI or PowerShell.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a general overview of Azure App Service plans, mentioning both Windows and Linux as supported operating systems. However, in the 'Managed Instance on Azure App Service (preview)' section, the examples and features are exclusively Windows-focused, with no Linux equivalent or parity. Additionally, links such as 'App Service plan details' point to Windows-specific pricing by default, and there are no Linux-specific examples or guidance throughout the page.
Recommendations
- Add explicit examples and guidance for Linux-based App Service plans, including supported features, pricing, and scaling considerations.
- Where features are Windows-only (such as Managed Instance), clearly label them as such and provide links or notes about Linux alternatives or limitations.
- Ensure that documentation links (e.g., pricing details) reference both Windows and Linux options, or clarify when a link is Windows-specific.
- Include parity tables or comparison charts that show which features are available on Windows vs. Linux App Service plans.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and references (e.g., IIS, applicationHost.config) are frequently mentioned first or exclusively. Windows-centric terminology and examples (such as referencing Windows time zones, Windows container settings, and legacy Windows build automation via Kudu) appear before or more prominently than Linux equivalents. Linux-specific details (such as Oryx build automation, Linux container settings, and Linux paths) are present but often secondary or less detailed.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are shown alongside Windows paths, not just in parentheses.
- Present Linux build automation (Oryx) and deployment options with equal prominence to Windows/Kudu/MSDeploy.
- Where Windows tools or settings are referenced (e.g., msbuild, Web Deploy), provide Linux alternatives or clarify applicability.
- Where possible, list Linux and Windows settings in parallel tables or sections, rather than Windows-first.
- Expand Linux-specific documentation (e.g., for custom containers, logging, caching, and build automation) to match Windows detail.
- Avoid referencing Windows-only features (e.g., applicationHost.config, IIS) in general sections unless clearly marked as Windows-specific.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides a link in the 'Next steps' section to a tutorial for creating an autoscaling, zone redundant application gateway using Azure PowerShell, which is a Windows-centric tool. There are no equivalent examples or links for Linux/macOS users (e.g., Azure CLI or ARM templates), and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, which is cross-platform.
- Include ARM/Bicep template examples for infrastructure-as-code parity.
- In 'Next steps', ensure that PowerShell tutorials are accompanied by CLI or template-based alternatives, or clearly indicate platform applicability.
- Consider a brief note clarifying that PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific tools and patterns are referenced (Kerberos documentation and Windows Authentication configuration in IIS), and Windows terminology (Service Principal Name, NTLM, Kerberos) is used without mentioning Linux equivalents or alternatives. Additionally, Windows authentication is discussed before any mention of non-Windows authentication methods, creating a 'windows_first' bias.
Recommendations
- Add guidance or links for troubleshooting authentication issues on Linux-based backend servers (e.g., using Apache, NGINX, or Samba for Kerberos/NTLM).
- Include references to Linux authentication documentation or tools where relevant, such as mod_auth_kerb for Apache or sssd for Kerberos.
- Clarify that NTLM and Kerberos are cross-platform protocols and provide examples or troubleshooting steps for Linux environments.
- When referencing backend server logs, mention both Windows (IIS) and Linux (Apache/Nginx) log locations and formats.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively demonstrates the configuration using a Windows-based SQL Server VM and recommends SQL Server Management Studio (SSMS) as the client tool, which is Windows-only. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS-compatible SQL client tools. The Windows VM and SSMS are mentioned first and exclusively, creating friction for Linux/macOS users who wish to follow the guide.
Recommendations
- Add instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2019/2022).
- Include examples of connecting to the SQL Server via cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible SQL clients.
- Clarify that the Application Gateway TCP/TLS proxy feature is not limited to Windows SQL Server backends and can be used with Linux-based SQL Server instances.
- Provide screenshots or command-line examples relevant to Linux/macOS environments where possible.
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 for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based workflows, with all migration scripts, examples, and installation instructions centered around PowerShell. There are no CLI (az), Bash, or Linux-native examples or alternatives provided, and the use of PowerShell Gallery and PowerShell modules is assumed throughout. This creates friction for Linux/macOS users who may prefer or require Bash, Azure CLI, or other cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or clarify if PowerShell is required for specific operations.
- Include Bash or shell script examples for common tasks, such as retrieving resource IDs, uploading certificates, and running migration scripts.
- Document how to run PowerShell scripts on Linux/macOS (e.g., using PowerShell Core), and note any platform-specific limitations or requirements.
- If migration scripts are only available in PowerShell, explicitly state this and provide guidance for Linux/macOS users on installing and using PowerShell Core.
- Consider offering downloadable scripts in other languages (e.g., Python, Bash) or providing REST API equivalents for advanced 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 moderate Windows bias. Migration instructions and registration/unregistration steps are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a tutorial that is PowerShell-focused, suggesting Windows as the primary platform for operational tasks. Azure CLI is referenced, but the commands shown are PowerShell cmdlets, not cross-platform Bash CLI commands.
Recommendations
- Provide equivalent Azure CLI (bash) examples for registration, unregistration, and migration tasks alongside PowerShell examples.
- Ensure tutorials and linked guides include both PowerShell and Azure CLI/Bash instructions.
- Clarify that Azure CLI commands can be run on Linux/macOS and provide explicit examples for those platforms.
- Review linked migration scripts and ensure Linux/macOS users are supported or alternative instructions are given.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no examples or guidance for users who may prefer or require Azure CLI, Bash, or other cross-platform tools. The exclusive mention of PowerShell (a tool with strong Windows associations, despite cross-platform support) and lack of Linux/macOS-specific migration guidance creates friction for non-Windows users.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for all migration steps currently covered by PowerShell scripts.
- Explicitly state whether the PowerShell scripts are supported and tested on Linux/macOS (PowerShell Core), and provide troubleshooting tips if there are known issues.
- Add Bash or shell script examples for common migration tasks, or link to cross-platform tooling where available.
- Reorder sections or add callouts to clarify that migration can be performed from any OS, not just Windows, if that is the case.
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 mention of Linux-native scripting tools (such as Bash or Python) or cross-platform alternatives. All migration examples and instructions are PowerShell-based, and there are no Linux-specific examples or guidance for users who may prefer or require non-Windows tooling. While the page states applicability to both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (pwsh) is fully supported on Linux/macOS for these tasks.
- Explicitly mention and provide examples for executing migration scripts from Linux/macOS environments, including any prerequisites or limitations.
- Add guidance for Linux users on installing required PowerShell modules and executing runbooks from Linux-based Automation accounts.
- Where possible, highlight cross-platform compatibility of PowerShell scripts (e.g., PowerShell Core) and note any Windows-specific limitations.
- Consider including links or references to Linux-native tools or Azure CLI alternatives if available.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently. Several backup and retention operations reference Windows PowerShell cmdlets without equivalent Linux CLI or scripting examples. The Linux example for TLS upgrade is present, but other sections (e.g., asset export, DSC node removal) only mention Windows tools.
Recommendations
- Provide Azure CLI or Bash examples alongside PowerShell cmdlets for backup and retention operations.
- Include Linux-specific instructions for exporting runbooks, DSC configurations, and managing assets.
- Ensure tables and lists mention Linux options with equal prominence to Windows.
- Where PowerShell is referenced, clarify if cross-platform PowerShell (pwsh) can be used, or provide alternatives.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation heavily focuses on Windows-specific tools and workflows, particularly SignTool, with all setup instructions, prerequisites, and examples tailored for Windows environments. PowerShell and Windows Package Manager (winget) are used exclusively for installation steps. There are no Linux/macOS equivalents or guidance for cross-platform users, even though Artifact Signing is also available via GitHub Actions, Azure DevOps, and SDKs, which could be used on non-Windows systems.
Recommendations
- Add explicit guidance and examples for Linux/macOS users, especially for SDK-based signing and GitHub Actions/Azure DevOps integrations.
- Clarify which integrations are Windows-only and which are cross-platform.
- Provide installation instructions for .NET 8.0 Runtime and Artifact Signing SDK/dlib for Linux/macOS.
- Include sample commands for signing artifacts on Linux/macOS using the SDK or other supported tools.
- Reorganize the documentation to present cross-platform options before Windows-specific ones, or clearly separate them.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-specific tools and patterns, with all code examples and module references using PowerShell. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform scripting). The term 'Windows PowerShell' is used, and no mention is made of alternatives for non-Windows environments, despite Azure Automation supporting Python runbooks and cross-platform modules.
Recommendations
- Add equivalent examples using Azure CLI and/or Python runbooks, which are supported in Azure Automation and are cross-platform.
- Clarify when 'PowerShell' refers to cross-platform PowerShell Core vs. Windows PowerShell, and provide guidance for non-Windows users.
- Mention that Azure Automation supports Python runbooks and link to relevant documentation.
- Where possible, provide Bash/Azure CLI snippets for credential management and authentication.
- Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'PowerShell' to indicate cross-platform compatibility.
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 CLI instructions and code samples provided only for PowerShell. There are no Linux shell (bash) or cross-platform CLI examples for certificate management, and PowerShell is presented first and most extensively. While Python examples are included, they are specific to Azure Automation runbooks and do not address certificate management from Linux/macOS environments outside of runbooks.
Recommendations
- Add Azure CLI or Bash examples for certificate management tasks, such as uploading, retrieving, and deleting certificates.
- Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
- Mention any limitations or alternative approaches for Linux/macOS users who may not have access to Windows PowerShell.
- Ensure parity in example ordering by presenting cross-platform options before or alongside PowerShell.
- Document certificate requirements (such as provider) in a way that is agnostic to OS-specific tooling.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell and Windows-centric tools and patterns, with most examples, screenshots, and workflows centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). Linux/macOS users are not provided with equivalent CLI or shell examples, and PowerShell is assumed as the primary interface for parameter passing and runbook invocation. Python runbooks are mentioned, but only briefly, and no Linux-native shell (bash) or cross-platform CLI examples are provided for starting runbooks or passing parameters.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, which are cross-platform and commonly used on Linux/macOS.
- Include bash shell examples for invoking REST API endpoints, demonstrating how Linux users can start runbooks and pass parameters.
- Clarify that PowerShell Core (pwsh) is cross-platform, and provide explicit instructions/examples for Linux/macOS users where relevant.
- Expand the Python runbook section with more detailed examples, including parameter passing from Linux/macOS environments.
- Where screenshots or UI instructions are given, note any platform differences or limitations.
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 and Windows-centric tooling, with all CLI examples using PowerShell cmdlets and references to Windows PowerShell. The creation and management of credentials are described exclusively with PowerShell commands, and Windows terminology (e.g., PSCredential) is used throughout. Python examples are provided, but there are no Bash, Linux CLI, or cross-platform shell examples. The documentation does not mention or demonstrate how Linux/macOS users can interact with credential assets outside of Python runbooks.
Recommendations
- Add examples using Azure CLI (az) for credential management, if supported.
- Clarify whether PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide guidance for non-Windows environments.
- Explicitly state platform requirements for PowerShell cmdlets and modules (e.g., Az modules, Orchestrator.AssetManagement.Cmdlets).
- Include a section or note for Linux/macOS users on how to manage credentials, or acknowledge any limitations.
- If credential management is only possible via PowerShell, make this clear and suggest alternatives for Linux/macOS users (such as using the Azure portal or Python runbooks).
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium 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 platform-neutral, the PowerShell section is Windows-specific and is presented as a main option. Additionally, in the Azure CLI instructions, Windows PowerShell is mentioned as a typical command console application, which may imply Windows as the default environment. Linux/macOS equivalents (such as Bash or Terminal) are not mentioned, and PowerShell examples are not flagged as Windows-only, potentially creating friction for non-Windows users.
Recommendations
- Explicitly mention Bash/Terminal as alternatives to Windows PowerShell for Azure CLI usage.
- Clarify that PowerShell instructions are Windows-specific and provide guidance for Linux/macOS users (e.g., using Azure CLI or PowerShell Core if supported).
- Ensure that CLI instructions are presented as the default cross-platform option, with PowerShell as an additional, Windows-specific alternative.
- Add notes or links for Linux/macOS users where relevant, especially in sections referencing Windows tools.
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 exhibits Windows bias in certain sections. Examples and explanations for registry tracking are exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to Linux configuration files or system directories). Windows terminology and concepts (registry keys, Windows services) are presented in detail, while Linux-specific examples (daemons, config files) are not provided. The order of presentation often puts Windows concepts first or exclusively.
Recommendations
- Add Linux-specific examples for change tracking, such as monitoring changes to /etc directory, systemd service files, or other common Linux configuration files.
- Include a table or section outlining Linux daemon/service tracking, similar to the Windows registry key table.
- Clarify which features are Windows-only and which are cross-platform, especially in sections like registry tracking.
- Provide Linux command-line or portal examples alongside Windows ones for enabling and configuring Change Tracking and Inventory.
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 demonstrates a notable Windows/PowerShell bias in the local SQL Server setup section. PowerShell is used exclusively for Docker commands, and no equivalent Bash or shell script examples are provided for Linux/macOS users. The troubleshooting steps and validation commands also use PowerShell syntax, and the initial suggestion for local SQL Server mentions Windows before Docker. While Docker is cross-platform, the lack of Linux/macOS-specific instructions or examples creates friction for non-Windows users.
Recommendations
- Provide Bash shell script equivalents for all PowerShell commands, especially for Docker setup and validation steps.
- Explicitly mention and demonstrate how to run Docker and SQL Server setup on Linux/macOS, including any required permissions or differences.
- Reorder instructions or add parallel sections so that Linux/macOS users see their options presented equally or first.
- Include troubleshooting notes relevant to Linux/macOS environments (e.g., file permissions, Docker networking).
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 for Azure Functions Core Tools is generally cross-platform, but there are several subtle Windows biases. Windows tools and behaviors (such as .pfx certificate handling, trusted certificate creation, and PowerShell managed dependencies) are mentioned without Linux/macOS equivalents or with Windows-specific caveats shown first. The documentation references Windows behaviors and issues (e.g., Python packaging on Windows for Linux deployment) before Linux/macOS, and some options (like managed dependencies) are PowerShell-specific. There are no explicit Linux/macOS command examples or troubleshooting tips, and Windows terminology (e.g., 'command prompt') is used throughout.
Recommendations
- Add explicit Linux/macOS examples and troubleshooting tips alongside Windows-specific notes.
- Where Windows-only features or behaviors are described (e.g., certificate creation, Python packaging), provide equivalent Linux/macOS instructions or clarify differences.
- Avoid using Windows terminology (e.g., 'command prompt') as the default; use 'terminal' or clarify OS-specific terms.
- Mention cross-platform tools and patterns equally, and ensure Linux/macOS users are not left to infer their workflow.
- For PowerShell-specific features, clarify their scope and provide alternatives for Bash/zsh users where possible.
Azure Functions
Azure Functions networking options
...ticles/azure-functions/functions-networking-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring virtual network triggers, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS-specific guidance or troubleshooting, and Hybrid Connections are described as Windows-only without alternative Linux approaches. Some subnet sizing guidance distinguishes Windows and Linux, but overall, Windows tools and patterns are referenced as much or more than Linux equivalents, and Linux users may need to infer their own workflows.
Recommendations
- Provide explicit Linux/macOS guidance for automation and troubleshooting steps, including Bash or CLI-only workflows.
- Clarify that Azure CLI commands work cross-platform and highlight them as the preferred method for Linux/macOS users.
- When listing automation examples, show CLI/Bash first, then PowerShell, or group them by OS.
- For Hybrid Connections, explicitly state alternatives or workarounds for Linux users, or link to relevant Linux documentation.
- Add troubleshooting steps for Linux/macOS environments, especially for network issues.
- Ensure screenshots and portal instructions are OS-neutral or note any Windows-specific UI differences.
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. However, PowerShell (a Windows-centric tool) is featured equally alongside Azure CLI, and the documentation references Azure PowerShell requirements in the prerequisites. There is minor bias in that PowerShell is presented as a primary option, which may create friction for Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool for deployment, listing CLI examples first.
- Clarify that Azure PowerShell is available on Linux/macOS, but recommend Azure CLI for non-Windows users.
- Add a Bash shell example for deploying the ARM template using Azure CLI, to further improve Linux parity.
- Explicitly mention that all steps can be completed on Linux/macOS using Azure CLI and Azure Cloud Shell.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd, PowerShell) before Linux/macOS (bash), but includes all relevant examples for each platform. Build/run/test instructions use cross-platform tools (Maven, curl) and do not show Windows-specific tools or patterns.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group all OS instructions together for parity.
- Explicitly mention that Maven and curl commands are cross-platform and work on Linux/macOS as well as Windows.
- Consider adding a short note clarifying that all steps are applicable to Linux/macOS unless otherwise stated.
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 in each step, and the PowerShell formatting is explicitly called out. There are no Linux-specific tools or patterns mentioned, but the presence of PowerShell examples throughout and their prominence may suggest a mild Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples with OS context (e.g., 'For Linux/macOS' and 'For Windows') to help users quickly identify relevant instructions.
- Consider showing Bash examples first, or alternating which example appears first, to avoid implicit prioritization.
- Add a note clarifying that Bash examples are for Linux/macOS terminals and PowerShell examples are for Windows, to improve clarity for cross-platform users.
- Ensure parity in explanations, and avoid unnecessary PowerShell-specific syntax unless required.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell examples are shown immediately after Bash in every step, and the PowerShell formatting is explicitly called out. There is no explicit Linux/macOS example or mention, and PowerShell is primarily a Windows shell, though it is now cross-platform. The Bash examples are generic, but the PowerShell examples may create a perception of Windows bias, especially as PowerShell is not the default shell on most Linux/macOS systems.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell examples are for Windows users.
- Consider labeling the code blocks as 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for clarity.
- If possible, provide explicit instructions or notes for Linux/macOS users, such as how to run Azure CLI commands in their default environments.
- Ensure that Bash examples are shown first, or at least equally, to avoid 'windows_first' bias.
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 shown first in each example section. While Azure CLI and REST API examples are also included, the PowerShell examples are more extensive and appear before CLI and REST, which may create friction for Linux/macOS users who typically use Bash and CLI tools. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained, but the ordering and detail favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Ensure CLI examples are as detailed as PowerShell examples, including managed identity scenarios.
- Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
- Consider adding a note at the top clarifying that all operations can be performed from Linux/macOS using CLI or REST.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available cross-platform) and the explicit PowerShell example may create a perception of Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI example, and PowerShell requirements are listed alongside CLI prerequisites. However, no critical steps are Windows-only, and Linux/macOS users can use the Azure CLI or portal to complete all tasks.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide installation instructions for Linux/macOS if not already included.
- Consider mentioning Bash or shell scripting alternatives for Azure CLI usage, especially for users on Linux/macOS.
- If possible, indicate that all CLI commands are fully supported on Linux/macOS and provide links to relevant platform-specific documentation.
- Ensure that the order of examples does not imply Windows preference (e.g., list CLI first, then PowerShell).
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 shells throughout, with PowerShell examples consistently shown second. There is a clear effort to support both Linux/macOS and Windows users, and no Windows-specific tools or patterns are prioritized. However, the presence of PowerShell examples alongside bash may be interpreted as a minor 'windows_first' bias, since PowerShell is primarily a Windows shell (though now available cross-platform). No Linux examples are missing, and no Windows-exclusive tools are mentioned.
Recommendations
- Continue providing both bash and PowerShell examples to ensure parity.
- Consider clarifying that PowerShell examples are also valid for Linux/macOS, since PowerShell Core is cross-platform.
- Explicitly state that all CLI commands work on Linux, macOS, and Windows, to reassure non-Windows users.
- If possible, provide a note on how to install Azure CLI and extensions on Linux/macOS, or link to relevant setup guides.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI throughout, and the PowerShell example is given equal prominence. There is a minor bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the page metadata includes 'devx-track-azurepowershell', suggesting a focus on PowerShell. However, Azure CLI (cross-platform) is also fully supported and shown first in the deployment section.
Recommendations
- Ensure Azure CLI examples are always shown first, as it is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Add a note explicitly stating that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell snippets or instructions for Linux/macOS users, especially for file operations (e.g., saving/uploading the Bicep file).
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, which are cross-platform. However, in the section on disabling routing to a regional gateway, Azure PowerShell is mentioned alongside Azure CLI and REST API, but no Linux-specific tools or shell examples (such as Bash scripting or references to Linux-native automation) are provided. Azure CLI is shown first, but PowerShell is referenced in the same sentence, which may create a slight impression of Windows-first bias. There are no explicit Windows-only tools or patterns, and no critical steps are Windows-only.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands to reinforce Linux parity.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- If referencing PowerShell, also mention that Azure CLI is preferred for Linux/macOS users.
- Consider including links or notes about using Azure CLI in Bash or Zsh shells 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, Azure PowerShell, and the Azure portal in parallel. However, PowerShell examples are always present and shown alongside CLI, which may be perceived as Windows-centric. The PowerShell examples are not explicitly marked as Windows-only, and their presence may suggest a slight Windows-first bias. However, Azure CLI is fully cross-platform and is given equal prominence. No critical steps are Windows-only, and Linux users can complete all tasks using the CLI or portal.
Recommendations
- Clearly indicate that Azure PowerShell is available cross-platform (Windows, macOS, Linux) to reduce perceived Windows bias.
- Consider listing Azure CLI examples before PowerShell examples, as CLI is the default for many Linux/macOS users.
- Explicitly state that all operations can be performed from any OS using Azure CLI or the portal.
- If possible, add a short note explaining the equivalence of CLI and PowerShell for all supported platforms.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but the PowerShell examples are prominent and detailed, and Windows-specific installation instructions (e.g., Helm via winget) are given before Linux equivalents. The Helm installation section gives Windows instructions first and highlights Windows tools like winget, while Linux instructions are present but less emphasized. There are no missing Linux examples for critical steps, but Windows tools and patterns are sometimes mentioned before Linux equivalents.
Recommendations
- Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
- Expand Linux installation instructions for tools (e.g., mention package managers like apt, yum, or snap for Helm, not just the curl script).
- Explicitly state that all Azure CLI commands are cross-platform and can be run on Linux/macOS/Windows.
- Where PowerShell is used, clarify that Azure CLI is the preferred cross-platform option, and PowerShell is optional for Windows users.
- Add macOS-specific instructions where relevant, especially for Helm installation.
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 (a Windows-centric tool) is given equal prominence and sometimes appears before Linux-native alternatives. The use of PowerShell is unnecessary for most Linux/macOS users, and the documentation does not explicitly clarify that Azure CLI is cross-platform while PowerShell is primarily Windows-focused. There are no missing Linux examples, but the inclusion of PowerShell may create confusion or friction for non-Windows users.
Recommendations
- Clarify in the prerequisites and code tabs that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Present Azure CLI examples first in all code tab sections, as it is the default for Linux/macOS and Windows.
- Consider removing PowerShell examples or placing them in a secondary section for Windows users, to avoid implying parity.
- Add brief notes indicating that PowerShell is optional and not required for Linux/macOS users.
- Ensure all instructions and tooling references are equally accessible from Linux/macOS (e.g., avoid referencing Windows-only tools unless necessary).
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 both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented immediately after the Linux example (using grep), and both are clearly labeled. The rest of the troubleshooting steps use standard Kubernetes CLI commands that are cross-platform. There is no exclusive use of Windows tools, nor are Windows patterns mentioned before Linux equivalents elsewhere. The bias is minor and limited to the order and labeling of log filtering examples.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, perhaps using tabbed code blocks or side-by-side formatting.
- Consider showing Linux and Windows examples together, or defaulting to Linux first given the Kubernetes ecosystem's Linux-centric nature.
- Add a note clarifying that all kubectl commands work on both platforms, and only the log filtering command differs.
- If possible, provide macOS-specific notes (though macOS is typically similar to Linux).
Azure App Configuration
Quickstart for adding feature flags to Spring Boot with Azure App Configuration
...p-configuration/quickstart-feature-flag-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd, PowerShell) before Linux/macOS (bash), but includes all platforms. No Windows-only tools or patterns are used, and Linux/macOS users are not missing any critical information.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows (cmd, PowerShell) to avoid implicit Windows prioritization.
- Consider grouping all OS instructions together or using tabs for each OS to make parity clearer.
- Explicitly state that the instructions are cross-platform and that all major OSes are supported.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific commands (setx, PowerShell) with detailed restart instructions. Linux/macOS instructions are present but appear after Windows examples. The rest of the tutorial is cross-platform, with Maven and Java code applicable to all OSes.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before or alongside Windows examples, rather than after.
- Clarify that Maven and Java steps are cross-platform and can be run on any OS.
- Consider grouping environment variable instructions by OS in a table or tabs for parity.
- Add explicit notes that all steps (except environment variable setup) are OS-agnostic.
- Avoid language like 'restart the command prompt' that is Windows-specific; instead, use 'restart your terminal' for cross-platform clarity.
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 the PowerShell section appears first and is more detailed. Portal instructions are platform-agnostic, but scripting examples prioritize PowerShell, which is more familiar to Windows users. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform and included. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI or portal.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is available cross-platform but is often associated with Windows.
- Consider adding Bash script examples for common tasks, or clarifying that Azure CLI commands can be run in Bash, Zsh, or other shells.
- Add a note in scripting sections to guide Linux/macOS users to Azure CLI as the recommended option.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides a generally cross-platform guide for running C# Azure Functions in an isolated worker process, but there are several areas where Windows bias is evident. Windows-specific tools (Visual Studio, PowerShell) are often mentioned before Linux equivalents, and some CLI instructions are presented with Windows-centric language or ordering. PowerShell is referenced as a deployment option alongside Azure CLI, but Linux Bash is not explicitly mentioned. In performance optimization and deployment sections, Windows examples and terminology are presented first or in greater detail. However, Linux support is present throughout, and most critical workflows are covered for both platforms.
Recommendations
- Ensure Linux/Bash examples are provided alongside PowerShell, especially in deployment and configuration sections.
- Present cross-platform CLI instructions (Azure CLI, dotnet CLI) before Windows-specific tools like PowerShell.
- Where possible, use neutral language and ordering (e.g., 'Windows and Linux') instead of 'Windows' first.
- Explicitly mention Linux/macOS support in sections where only Windows tools are referenced.
- Add links or references to Linux-specific guides or troubleshooting where relevant.
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 generally covers both Windows and Linux scenarios, but there are minor signs of Windows bias. Some settings (e.g., AzureWebJobs_TypeScriptPath) use Windows-style paths in examples, and Windows-specific settings (WEBSITE_NODE_DEFAULT_VERSION) are called out. In a few places, Windows behaviors are described before Linux equivalents (e.g., hierarchical delimiters in app settings). Recommendations for using Azure CLI or Azure PowerShell are given, but Linux-native tools (like Bash or shell scripting) are not mentioned. Overall, Linux parity is strong, but Windows examples and terminology appear first or exclusively in minor cases.
Recommendations
- Where sample paths are shown (e.g., AzureWebJobs_TypeScriptPath), provide both Windows and Linux path examples.
- When discussing reserved delimiters in app settings, clarify Linux behavior equally and provide explicit examples for both OSes.
- When recommending tools for programmatic configuration (Azure CLI, PowerShell), mention Bash or other Linux-native scripting options.
- Ensure that Linux-specific settings and behaviors are described with equal prominence and clarity as Windows equivalents.
- Review sample values and screenshots to ensure they are not Windows-centric unless the setting is Windows-only.
Azure Cache For Redis
Deploy Azure Cache for Redis using Bicep
...s/azure-cache-for-redis/redis-cache-bicep-provision.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Azure Cache for Redis using Bicep. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments. PowerShell examples are given equal prominence alongside CLI, and there is no explicit mention of Linux/macOS-specific considerations or alternative shell environments. However, the CLI examples are present and shown first in each section, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a note indicating that Azure PowerShell is available on Linux/macOS, but CLI is generally more common in those environments.
- Consider including Bash shell scripting examples for automation, or explicitly mention that all CLI commands work on Linux/macOS.
- If possible, add a brief section about running Bicep deployments from Linux/macOS terminals, including installation links for Azure CLI and Bicep.
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 Windows bias. Windows-specific deployment options (such as source control, local Git, FTPS) are mentioned as 'Windows-only' in the availability table, and Windows tools (Visual Studio, references to Kudu/SCM) are often listed before Linux equivalents. Examples and instructions tend to mention Windows tools and features first, with Linux-specific instructions appearing later or in separate sections. However, Linux deployment options are described and supported, and critical tasks can be completed on Linux/macOS.
Recommendations
- Ensure that Linux/macOS examples are provided alongside Windows ones, especially for CLI commands and tool usage.
- Where possible, list cross-platform tools (Azure CLI, Core Tools, VS Code) before Windows-only tools (Visual Studio).
- Clarify when a tool or method is cross-platform, and provide explicit instructions for Linux/macOS users.
- Add more Linux/macOS-specific troubleshooting tips and deployment scenarios, especially for remote build and container deployments.
- Consider balancing the order of examples and tool mentions so Linux users do not feel secondary.