App Service
806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
247 issues found
Showing 201-225 of 247 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-gateway-based-vnet-integration.md
.../app-service/migrate-gateway-based-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides step-by-step instructions for migrating App Service virtual network integration, and consistently presents Azure PowerShell examples alongside Azure CLI and portal instructions. PowerShell examples are given equal prominence to CLI and portal, but PowerShell is a Windows-centric tool, and there is no mention of Linux-specific tools or shell patterns (e.g., Bash, scripting nuances). The documentation does not reference Linux-specific commands, nor does it acknowledge differences in experience for Linux users. While Azure CLI is cross-platform, the inclusion and equal emphasis on PowerShell throughout the page reflects a subtle Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Add notes or sections highlighting any differences or considerations for Linux users, such as shell syntax, environment setup, or troubleshooting.
- Consider providing Bash script examples for common operations, or at least mention how Linux users can automate these steps.
- Review the order of examples: present Azure CLI before PowerShell to subtly prioritize cross-platform tooling.
- Where PowerShell is shown, clarify its platform requirements and suggest alternatives for Linux users.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-app-service.md
.../blob/main/articles/app-service/monitor-app-service.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by mentioning Visual Studio integration for Application Insights and listing PowerShell as a primary method for querying Azure activity logs, with no explicit mention of Linux tools or examples. There are no Linux-specific CLI or shell examples, and Windows tools are referenced before cross-platform alternatives.
Recommendations
- Include examples using Azure CLI and Bash for querying activity logs and managing monitoring features, alongside PowerShell.
- Mention cross-platform editors and IDEs (such as VS Code) in addition to Visual Studio when discussing Application Insights integration.
- Add explicit references to Linux-compatible monitoring workflows and tools where relevant.
- Ensure that any tool or method listed (e.g., PowerShell) is accompanied by its cross-platform equivalent, and present them together or with Linux-first parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md
...s/app-service/overview-authentication-authorization.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents the Windows (IIS module) architecture before the Linux/container equivalent, and references IIS modules as the native implementation. The Linux/container architecture is described as an alternative, with less direct integration. There are no explicit PowerShell-heavy examples or Windows-only CLI instructions, but the architectural explanation is Windows-first and Windows-centric. No Linux-specific tools or patterns are mentioned, and CLI examples use Azure CLI (cross-platform).
Recommendations
- Present Linux/container architecture before or alongside Windows architecture to avoid Windows-first bias.
- Provide more details about Linux/container implementation, including any relevant troubleshooting, configuration, or integration differences.
- Reference Linux-native concepts (such as NGINX/Apache modules or reverse proxy patterns) where appropriate, not just IIS.
- Include links or examples for Linux-specific scenarios, such as troubleshooting authentication in Linux containers.
- Ensure parity in architectural diagrams and explanations for both Windows and Linux/container deployments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-agent-identity.md
...b/main/articles/app-service/overview-agent-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure App Service and Azure Functions, which are traditionally associated with Windows environments, and by providing only C# code samples. There are no examples or guidance for deploying or configuring agent identity on Linux-based hosting options, nor are there any Linux-specific tools, shell commands, or deployment patterns mentioned. The documentation does not address cross-platform concerns or provide parity for Linux users.
Recommendations
- Include explicit instructions and examples for deploying .NET agent identity apps on Linux-based App Service plans and Azure Functions (e.g., using containers or Linux runtime).
- Provide Linux shell (bash) equivalents for environment variable configuration and deployment steps, alongside any PowerShell or Windows-specific instructions.
- Mention and link to documentation for Linux-based development and deployment workflows, such as using Azure CLI in bash, Docker containers, or GitHub Actions for Linux runners.
- Add notes clarifying platform compatibility, and highlight any differences or additional steps required for Linux environments.
- Offer sample code and configuration for other languages and frameworks commonly used on Linux, such as Python or Node.js, to demonstrate agent identity usage outside of C#/.NET.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-java.md
...docs/blob/main/articles/app-service/quickstart-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides separate pivots for Java Tomcat (Linux), Java SE (Windows), and Java JBoss (Windows), but both Java SE and JBoss examples are Windows-only. There are no Linux equivalents for Java SE or JBoss, and the Windows pivots are listed before Linux in those cases. This creates a bias toward Windows by omitting Linux instructions for those runtimes and prioritizing Windows examples.
Recommendations
- Provide Linux-based quickstart pivots/examples for Java SE and JBoss, if supported by Azure App Service.
- Ensure that Linux and Windows pivots are presented with equal prominence and ordering.
- Explicitly mention platform support limitations if certain runtimes are not available on Linux, to clarify the absence of Linux examples.
- Add cross-platform notes or tables summarizing which runtimes are supported on which OS, to help users quickly understand parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-bicep.md
...e-docs/blob/main/articles/app-service/samples-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for basic app deployment, but Windows-specific scenarios (such as Windows container apps and MySQL on Windows) are more prevalent and appear before or in greater detail than their Linux equivalents. There are examples for Windows containers and Windows+MySQL, but no corresponding Linux container or Linux+MySQL samples. The ordering and coverage suggest a slight Windows bias.
Recommendations
- Add examples for Linux container app deployments to match the Windows container sample.
- Include a sample for App Service app on Linux with Azure Database for MySQL to parallel the Windows+MySQL example.
- Ensure parity in the number and detail of Linux and Windows scenarios, especially for common configurations.
- Consider alternating the order of Windows and Linux examples or grouping them together for direct comparison.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-execution.md
...cs/blob/main/articles/app-service/webjobs-execution.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally describes WebJobs in a cross-platform manner, but there is subtle Windows bias: the folder structure uses Windows-style paths (e.g., 'site/wwwroot/App_Data/jobs/'), and there are no explicit Linux or cross-platform examples for job creation, folder navigation, or log access. Linux-specific troubleshooting is limited to a single bullet point about permissions, and there are no PowerShell or Windows tool examples, but the documentation does not provide parity for Linux command-line workflows or highlight Linux-first patterns.
Recommendations
- Add explicit Linux examples for folder navigation (e.g., using bash commands to access job folders and logs).
- Include sample commands for setting permissions on Linux (e.g., 'chmod +x run.sh') in the main workflow, not just troubleshooting.
- Show both Windows and Linux path formats when referencing folders.
- Provide examples of how to access logs or trigger jobs using Linux tools (curl, bash) alongside portal/Kudu instructions.
- Clarify any differences in behavior or requirements between Windows and Linux environments in relevant sections.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC permissions, but PowerShell is featured equally and sometimes before Linux-native tools. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux/OpenSSL instructions are present but not always prioritized. Some automation links reference PowerShell scripts alongside CLI, but Linux equivalents are not always given first. Overall, Linux users can complete all tasks, but Windows tools and patterns are referenced frequently and sometimes before Linux alternatives.
Recommendations
- When listing automation options, consistently show Azure CLI (cross-platform) examples before PowerShell.
- For certificate export, prioritize OpenSSL instructions and clarify that IIS/Certreq.exe are Windows-only.
- Add explicit notes or links for Linux/macOS users where Windows tools are referenced.
- Ensure screenshots and UI instructions are OS-neutral or clarify if any steps differ for Linux-hosted apps.
- Consider adding a section summarizing Linux/macOS certificate management best practices for Azure App Service.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented alongside CLI examples. In several places, PowerShell examples are given equal prominence to CLI, and the tab order is 'portal', 'cli', 'powershell', which may subtly prioritize Windows tools. However, Linux/macOS users are fully supported via Azure CLI, and no critical steps are Windows-only. There are no missing Linux examples, and no exclusive mention of Windows tools or patterns.
Recommendations
- Consider listing Azure CLI examples before Azure PowerShell to reinforce cross-platform parity.
- Explicitly note that Azure CLI is recommended for Linux/macOS users and that PowerShell is optional.
- If possible, clarify that all CLI steps are fully supported on Linux/macOS.
- Add a brief statement in the prerequisites or migration steps indicating that all procedures can be completed from Linux/macOS using Azure CLI.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are consistently shown immediately after CLI examples, and no explicit Linux/macOS shell examples are given. The CLI examples are cross-platform, but the presence of PowerShell commands (which are Windows-centric, though available cross-platform) may give the impression of Windows prioritization. No Linux-specific tools or workflows are mentioned, but critical tasks are not blocked for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on all platforms (Windows, Linux, macOS) and are the recommended cross-platform approach.
- Consider labeling PowerShell examples as 'Azure PowerShell' and noting that PowerShell Core is available cross-platform, to avoid the impression of Windows-only support.
- Add explicit bash or shell examples where appropriate (e.g., using curl or dig for DNS lookups), especially in sections like 'Find the inbound IP', to improve parity.
- Where both CLI and PowerShell are shown, consider showing CLI first and labeling it as the default/cross-platform method.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity for both Windows and Linux users regarding the Premium v4 tier, including explicit notes about feature availability. However, there is a subtle Windows-first bias: in several sections, Windows examples or instructions are presented before Linux equivalents, and Azure PowerShell (primarily used on Windows) is given equal prominence to Azure CLI, despite CLI being more cross-platform. All automation examples are provided for both Azure CLI and PowerShell, but no explicit Bash or Linux shell scripting examples are shown. The overall impact is minor, as Linux users can complete all tasks using the CLI.
Recommendations
- When listing SKU availability commands, present Linux and Windows examples together or alternate their order to avoid a Windows-first impression.
- Consider adding a simple Bash script example for automating app creation, to further support Linux users.
- Clarify in the 'Automate with scripts' section that Azure CLI is fully cross-platform and recommended for Linux/macOS users, while PowerShell is optional.
- Ensure that portal instructions and screenshots are not Windows-centric (e.g., avoid referencing Windows-only UI elements or terminology).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are always shown immediately after CLI, and there are no explicit Linux/macOS shell examples (e.g., bash scripts) for interacting with Azure outside of Azure CLI. The use of PowerShell is not strictly necessary for cross-platform users, and its inclusion immediately after CLI may suggest a Windows-first approach.
Recommendations
- Ensure that Azure CLI examples are clearly marked as cross-platform and are shown before PowerShell examples, as is currently the case.
- Consider explicitly stating that Azure CLI commands work on Windows, Linux, and macOS, and that PowerShell is optional.
- If possible, add bash or shell script examples for common tasks, or clarify that Azure CLI is the recommended cross-platform tool.
- Where PowerShell is shown, clarify that it is available cross-platform (via PowerShell Core), or provide a note for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, especially in the 'Premium v4 availability' section, where both Windows and Linux SKU availability commands are provided. However, there is a subtle 'windows_first' bias: Windows examples and instructions are consistently presented before Linux equivalents. Additionally, the 'Automate with scripts' section provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but does not mention Bash scripting or Linux-native automation tools. The Azure portal instructions are platform-neutral. No critical Linux gaps are present.
Recommendations
- When listing both Windows and Linux commands, alternate the order or explicitly state that both are equally supported.
- In the 'Automate with scripts' section, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users, and consider adding a Bash script example for Linux automation.
- Where PowerShell is shown, note that PowerShell Core is available cross-platform, or provide Bash equivalents if relevant.
- Continue to ensure that all features and instructions are clearly marked if they are Windows- or Linux-specific.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 configuration, but PowerShell (a Windows-centric tool) is given its own section and example. While Linux-specific CLI options are mentioned for SKU availability, the scripting section does not explicitly show Linux/macOS shell usage or parity. The Azure portal instructions are platform-neutral, but screenshots and navigation patterns may be more familiar to Windows users. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users in the automation section.
- Clarify that Azure CLI commands work on Linux/macOS and provide sample terminal output or usage notes for those platforms.
- Balance the scripting sections by mentioning cross-platform compatibility and avoiding the implication that PowerShell is required.
- Consider adding a note or table summarizing tool/platform compatibility for each example.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias: Windows is mentioned first in availability, PowerShell scripting is featured alongside Azure CLI, and Windows-specific terminology and tools (like PowerShell and Windows SKUs) are referenced before or more prominently than Linux equivalents. While Linux is supported and examples are present, Windows is often positioned first and receives slightly more attention.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide Bash or shell script examples alongside PowerShell for automation.
- Clearly state Linux support and parity in introductory sections.
- Where Windows-specific tools or terminology are used, offer Linux equivalents or clarify differences.
- Add explicit Linux container limitations and guidance, as is done for Windows containers.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management, but PowerShell examples are consistently present and sometimes shown first, especially in advanced scenarios. There is a notable emphasis on PowerShell for scripting, which is more commonly used on Windows. No Linux-specific tools or shell scripting examples (e.g., Bash) are provided, and the documentation does not mention platform-specific differences or considerations for Linux/macOS users. However, Azure CLI is cross-platform and included in all relevant sections, mitigating most friction.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
- Add explicit notes that Azure CLI works on Linux/macOS and Windows, while PowerShell is primarily Windows (with cross-platform support, but less common on Linux).
- Consider including Bash script examples for common tasks, or at least reference that Azure CLI commands can be used in Bash/zsh shells.
- Add a brief section clarifying that all programmatic examples (except PowerShell) are platform-agnostic, and highlight any platform-specific caveats if they exist.
- Where PowerShell is used for advanced scenarios, provide equivalent Azure CLI or REST API examples if possible.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific features and limitations (such as Windows Containers subnet sizing and Windows Server Active Directory domain join) are described in detail, while Linux-specific scenarios receive less attention. The only explicit Linux mention is in the 'Linux continuous deployment' section, which is brief and lacks parity with the Windows coverage. No Linux-specific examples, troubleshooting steps, or CLI commands are provided. Windows tools (Kudu console UI) are referenced without Linux equivalents. Examples and calculations are Windows-centric, and Windows limitations are discussed before Linux ones.
Recommendations
- Add Linux-specific examples for subnet sizing, app deployment, and troubleshooting.
- Include parity for Linux container limitations and configuration steps.
- Reference Linux equivalents for tools like Kudu (e.g., SSH, Azure CLI, or App Service diagnostics for Linux).
- Provide CLI commands and sample scenarios for Linux-based App Service plans.
- Ensure that Linux and macOS users are considered in all example and troubleshooting sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias by presenting Windows-specific instructions and tools (Kudu, CMD, PowerShell) before their Linux equivalents, and referencing Visual Studio and Windows deployment patterns more prominently. While Linux instructions are present and reasonably complete, Windows examples and tools are often mentioned first, and Windows-centric terminology (such as Kudu and Advanced Tools) is used without Linux analogues. Linux users may experience minor friction due to this ordering and emphasis.
Recommendations
- Alternate the order of Windows and Linux sections, or present both platforms in parallel where possible.
- Provide Linux equivalents for Windows-specific tools (e.g., mention SSH and Bash consoles alongside Kudu/PowerShell).
- Clarify when instructions are platform-specific and avoid assuming Visual Studio as the default tool.
- Ensure parity in example depth and detail for both platforms.
- Add more explicit references to Linux-native workflows and troubleshooting tools.
App Service
Disable Basic Authentication for Deployment
...n/articles/app-service/configure-basic-auth-disable.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows-centric deployment tools (FTP, Web Deploy, Visual Studio) are referenced throughout, and troubleshooting sections specifically mention Windows agents and 'windows-latest' in Azure Pipelines. The term 'Web Deploy' is used without explicit Linux alternatives, and Visual Studio is highlighted as a primary deployment method. However, Azure CLI examples are provided, which are cross-platform, and no sections are strictly Windows-only.
Recommendations
- Explicitly mention Linux/macOS alternatives to Web Deploy and Visual Studio, such as using zip deploy, run-from-package, or cross-platform CI/CD tools.
- Add troubleshooting guidance for Linux/macOS agents in Azure Pipelines, not just Windows agents.
- Clarify that Azure CLI commands work on all platforms and provide example commands for Linux/macOS environments where relevant.
- Where 'Web Deploy' is mentioned, note that it is a Windows-specific tool and suggest alternatives for Linux/macOS users.
- Ensure that any screenshots or step-by-step instructions in the portal are not Windows-centric (e.g., avoid showing only Windows file paths or tools).
App Service
SSH Access for Linux and Windows Containers
...ticles/app-service/configure-linux-open-ssh-session.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. The Windows container section is presented first, and it highlights the ease of SSH access for Windows containers without requiring image modifications. However, it lacks detailed instructions or examples for Windows users (e.g., no PowerShell or Windows SSH client usage is shown), while the Linux section provides extensive step-by-step guidance, CLI commands, and example outputs. There is also an absence of parity in tooling: Windows users are told browser SSH is supported, but no alternative (such as PowerShell or PuTTY) is mentioned, nor is Azure CLI SSH tunneling supported for Windows containers.
Recommendations
- Add explicit SSH client usage examples for Windows users (e.g., PowerShell, PuTTY) in the Windows container section.
- Clarify whether SSH tunneling or Azure CLI remote connection is possible for Windows containers, and if not, suggest alternatives.
- Present Linux and Windows instructions in parallel, or use a neutral order (alphabetical or user-driven pivot) to avoid 'windows_first' bias.
- Include troubleshooting steps for Windows SSH access similar to those provided for Linux.
- Ensure both platforms have equivalent detail and actionable steps.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal in all major sections. Azure PowerShell is featured as a primary tab alongside CLI and portal, despite being Windows-centric. There are no explicit Linux/macOS command-line examples (e.g., Bash, shell scripts), and PowerShell is presented as an equal alternative to CLI, which may create friction for Linux/macOS users. However, the CLI examples are cross-platform, and the documentation does note CLI as the method for some tasks that PowerShell cannot perform.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit Bash/shell examples where relevant, especially for Git operations (e.g., escaping $ in usernames).
- Consider demoting Azure PowerShell to a secondary option or noting its Windows-centric nature.
- Add notes or links for Linux/macOS users regarding any differences in credential usage or command syntax.
- Ensure screenshots and portal instructions do not assume Windows-only UI conventions.
App Service
Quickstart: Use Terraform to configure an Azure App Service Environment v3
...articles/app-service/environment/creation-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and detail as Azure CLI. PowerShell is a Windows-centric tool, and its inclusion as a primary tab may suggest Windows is a first-class platform. However, Azure CLI is cross-platform and shown first, and all Terraform commands are platform-agnostic. No Linux/macOS-specific examples or troubleshooting are provided, but Linux users can follow the CLI instructions without issue.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Add a note clarifying that PowerShell examples are for Windows users, while CLI examples are cross-platform.
- Consider adding bash shell variable assignment examples for Linux/macOS users.
- Include troubleshooting tips for Linux/macOS environments if relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-curl-commands.md
...includes/quickstart-python/deploy-zip-curl-commands.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash and PowerShell examples for deploying via Kudu, but PowerShell (Windows) is mentioned explicitly and given additional guidance, while Linux/macOS users are not given similar platform-specific notes. The order of examples also places Bash first, but the explanatory note is Windows/PowerShell-specific.
Recommendations
- Add platform-specific notes for Bash/Linux/macOS users if needed (e.g., authentication nuances, curl differences).
- Provide parity in guidance: If PowerShell users get a special note, consider if Bash users need one too.
- Clarify that both Bash and PowerShell examples are cross-platform, and explicitly mention support for Linux/macOS.
- If there are any Linux-specific tools or approaches (e.g., wget), mention them alongside curl.
App Service
Set Up Azure Arc for App Service, Functions, and Logic Apps
.../articles/app-service/manage-create-arc-environment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but consistently lists PowerShell examples immediately after Bash, and in some cases, the PowerShell examples are more detailed (e.g., base64 encoding for Log Analytics keys). There is a slight Windows-first bias in the ordering and completeness of examples, but Linux users are not blocked from completing any steps.
Recommendations
- Ensure Bash examples are as detailed as PowerShell, especially for encoding and variable handling.
- Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
- Consider listing Bash examples first throughout, or grouping examples by platform rather than alternating.
- Add notes about platform-specific behaviors (e.g., base64 flags, file path differences) where relevant.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, CLI installation).
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples shown alongside CLI and portal instructions. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion may signal a Windows-centric approach. There are no Linux-specific shell examples (e.g., Bash), nor is there explicit mention of Linux/macOS tooling or considerations. However, the CLI examples do provide parity for Linux/macOS users, and the portal instructions are platform-agnostic.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Add Bash shell script examples where appropriate, especially for steps involving scripting or automation.
- Clarify that Azure PowerShell is available on Linux/macOS (if true), or recommend CLI for non-Windows users.
- Consider listing CLI examples before PowerShell to signal platform neutrality.
- Add a note or section for Linux/macOS users highlighting any platform-specific considerations or limitations.