App Service
432
Total Pages
240
Linux-Friendly Pages
192
Pages with Bias
44.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2121 issues found
Showing 1501-1525 of 2121 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are given equal or greater prominence, including in advanced scenarios and custom rule creation. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may suggest a slight Windows bias. No Linux-specific shell (e.g., bash) or scripting examples are provided, and PowerShell examples are sometimes shown before or in parallel with CLI, reinforcing the Windows-first approach. There are no references to Windows-only tools or patterns, but the lack of Linux shell examples and the heavy use of PowerShell may disadvantage Linux users.
Recommendations
- Add bash/sh scripting examples for common scenarios, especially for advanced rule creation and multi-source rules.
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Where PowerShell examples are given, ensure Azure CLI examples are shown first or in parallel, and clarify platform compatibility.
- Consider including automation examples using Python SDK or REST API for users who prefer non-Windows environments.
- Review screenshots and UI references to ensure they do not assume Windows-specific conventions.
Create Pull Request
App Service
Use Key Vault References as App Settings
...ticles/app-service/app-service-key-vault-references.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but consistently lists the PowerShell examples after the CLI, and does not provide any Linux shell-specific examples (such as Bash scripts or Linux-native tools). The use of PowerShell, which is more familiar to Windows users, may disadvantage Linux users, especially since PowerShell is not the default shell on most Linux distributions. There are no explicit Linux-only instructions or examples, and the troubleshooting and portal navigation sections do not mention any OS-specific considerations.
Recommendations
- Add explicit Bash or shell script examples alongside Azure CLI and PowerShell, especially for Linux users.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, Cloud Shell, or other Linux environments.
- Where PowerShell is used, note that PowerShell Core is available cross-platform, but provide equivalent Bash or shell-native alternatives where possible.
- Include notes or sections that address any Linux-specific behaviors or troubleshooting steps, particularly for networking and identity configuration.
- Ensure that any references to tools or commands are not Windows-centric by default, and that Linux-first or Linux-equal examples are provided.
App Service
Configure continuous deployment
...n/articles/app-service/deploy-continuous-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'Windows apps' specifically in the 'External Git' section and not mentioning Linux apps or providing Linux-specific guidance. There are no explicit Linux examples, nor is there mention of Linux-specific deployment patterns or tools. The documentation assumes parity but does not confirm or illustrate it, and Windows terminology appears first or exclusively in some places.
Recommendations
- Explicitly mention Linux app support wherever 'Windows apps' are referenced, or clarify if steps differ for Linux.
- Provide examples or notes for deploying to Linux-based App Service apps, especially in sections like 'External Git' and authentication.
- Include references to Linux-specific deployment patterns or troubleshooting, if applicable.
- Review screenshots and UI instructions to ensure they are not Windows-centric and clarify when steps apply to both OS types.
- Add a parity statement confirming that all steps apply equally to Linux and Windows, or highlight differences where they exist.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash and PowerShell examples for deploying via Kudu, but the introductory instructions focus on navigating the Azure portal, which is more familiar to Windows users. The PowerShell example includes a specific note about quoting, giving extra attention to Windows/PowerShell usage. There is no mention of Linux-specific tools or navigation patterns, and the Bash example is presented after the general instructions, not as a primary workflow.
Recommendations
- Add explicit instructions for Linux users, such as how to access Kudu from Linux environments or via CLI.
- Include references to Linux-native tools (e.g., wget, scp) where appropriate.
- Present Bash and PowerShell examples in parallel, or alternate which is shown first.
- Clarify that the instructions apply equally to Linux and Windows users, and note any platform-specific differences.
- Consider adding a section on using Azure CLI for deployment, which is cross-platform.
App Service
Securely connect .NET apps to resources using the Entra agent identity platform
...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 .NET/C# code examples. There are no Linux-specific instructions, examples, or references to Linux-native tools, nor is there any mention of deploying or configuring agent identity scenarios in Linux environments (such as Azure App Service for Linux, Azure Functions on Linux, or container-based deployments). The documentation also omits any discussion of cross-platform considerations, shell differences, or Linux-specific environment variable configuration.
Recommendations
- Add explicit instructions and examples for deploying .NET agent apps on Azure App Service for Linux and Azure Functions on Linux.
- Include Linux shell (bash/zsh) environment variable configuration examples alongside any Windows/PowerShell equivalents.
- Mention cross-platform deployment considerations, such as differences in managed identity assignment and authentication between Windows and Linux hosting plans.
- Provide sample code or references for running the agent identity scenarios in containerized environments (Docker), which are common in Linux-based deployments.
- Clarify that the steps and code are applicable to both Windows and Linux environments, and highlight any platform-specific caveats.
- Add links to documentation for Linux-based Azure App Service and Azure Functions, and ensure parity in guidance.
App Service
Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes
...b/main/articles/app-service/migrate-app-service-arc.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is given equal prominence and is listed immediately after CLI in every case. There are no Linux shell-specific examples (e.g., Bash scripts, shell pipelines), nor is there mention of Linux-native tools. The documentation does not acknowledge platform-specific differences in running CLI commands (e.g., shell quoting, environment setup), and PowerShell—a Windows-centric tool—is featured as a primary option.
Recommendations
- Add explicit Bash shell examples for all CLI commands, including Linux-specific syntax and usage notes.
- Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide guidance for Linux users (e.g., installation, environment setup).
- If PowerShell is included, note its cross-platform availability but avoid implying it is the default or preferred option for all users.
- Consider listing Bash/Linux examples before PowerShell, or provide tabs for Bash, PowerShell, and CLI to ensure parity.
- Mention any platform-specific caveats (such as quoting differences) when presenting CLI commands.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, primarily through the mention of Visual Studio integration for Application Insights and listing PowerShell as a query method for Azure activity logs before CLI or REST API. There are no explicit Linux or Bash examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity in examples or tool references for Linux users.
Recommendations
- Add explicit examples using Azure CLI and Bash scripts alongside PowerShell where applicable, especially in sections discussing querying logs or automating monitoring tasks.
- Mention Linux-friendly development tools (such as VS Code, JetBrains IDEs) in addition to Visual Studio when discussing Application Insights integration.
- Ensure that references to command-line tools (PowerShell, CLI) are presented in a neutral order or grouped together, rather than listing Windows tools first.
- Include troubleshooting and monitoring scenarios relevant to Linux-hosted App Service apps, such as integration with syslog or Linux-native logging formats.
- Provide links or references to Linux documentation and best practices for monitoring Azure App Service.
App Service
Authentication and Authorization
...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 Windows-specific technologies (IIS modules) without providing equal detail or examples for Linux. There are no explicit PowerShell-heavy examples or missing Linux examples, but the ordering and terminology favor Windows environments.
Recommendations
- Present Linux/container architecture before or alongside Windows architecture to avoid implicit prioritization.
- Provide equivalent technical detail for Linux/container deployments, including references to relevant Linux technologies (e.g., ambassador pattern, container orchestration).
- Include examples or links for configuring authentication and authorization on Linux/container environments, not just Windows/IIS.
- Clarify any differences in configuration or troubleshooting between Windows and Linux/container environments.
- Avoid using Windows-specific terminology (e.g., IIS module) without explaining or paralleling the Linux/container approach.
App Service
Quickstart: Use Terraform to configure an Azure App Service Environment v3
...articles/app-service/environment/creation-terraform.md
Medium 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 is presented as a separate tab. There is no explicit mention of Linux-specific tools or shell environments (such as Bash), nor are Linux command-line patterns (e.g., export, echo) shown. The use of PowerShell syntax ($variable=...) may be confusing for Linux users, and the CLI examples use variable assignment syntax that is compatible with Bash but not with Windows CMD. Overall, the documentation is slightly Windows-biased by presenting PowerShell as a primary option and not explicitly addressing Linux shell environments.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps, using standard Bash syntax (e.g., export, echo, variable assignment).
- Clarify which command examples are intended for Windows CMD, PowerShell, or Bash, and provide tabs for each where appropriate.
- Mention that Azure CLI is cross-platform and can be used in Bash, PowerShell, or CMD, with examples for each.
- Ensure that variable assignment and command syntax are correct for both Linux and Windows environments.
- Consider listing Bash/Linux examples before PowerShell to avoid implicit Windows-first bias.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after CLI without explicit Linux shell examples. The documentation references Windows and Linux container availability, but does not offer Linux-specific scripting or shell examples (e.g., Bash), nor does it mention Linux-native tools. The portal instructions are platform-neutral, but the automation section leans toward Windows by including PowerShell.
Recommendations
- Add explicit Bash shell examples for Linux users alongside Azure CLI and PowerShell.
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide sample Bash usage.
- If mentioning PowerShell, note its cross-platform availability, but also provide parity with Linux shell scripting.
- Consider reordering automation examples to present Azure CLI (cross-platform) first, followed by Bash and then PowerShell.
- Reference Linux-native tools or workflows where relevant, especially in automation and scripting sections.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are frequently given, sometimes before CLI, and advanced scenarios (multi-source rules, Front Door restrictions) only show PowerShell code. There is an overall tendency to present PowerShell as a primary automation method, which is more familiar to Windows users, while Linux-native scripting (e.g., Bash, shell scripts) is not covered. No Linux-specific tools or patterns are mentioned, and the CLI examples are generic, not tailored for Linux environments.
Recommendations
- Add Bash/shell script examples for key scenarios, especially for advanced rule creation and automation.
- Ensure Azure CLI examples are always presented before or alongside PowerShell, especially in advanced sections.
- Explicitly mention that Azure CLI works natively on Linux and macOS, and provide guidance for Linux users where appropriate.
- Include notes or links about using Azure CLI in Linux environments (e.g., installation, authentication, scripting best practices).
- For multi-source and advanced scenarios, provide equivalent Azure CLI or REST API examples, not just PowerShell.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid references to Windows-only features or terminology).
App Service
Configure Sign in with Apple (Preview)
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only C# code examples (using Microsoft.IdentityModel.Tokens and CngKey, which are Windows-centric APIs) for generating the client secret JWT, without mentioning or providing equivalent Linux-friendly methods or examples (such as using OpenSSL, Python, or Node.js). There are no references to Linux tools or cross-platform approaches for JWT signing, and the documentation does not address how developers on Linux or macOS should perform these steps.
Recommendations
- Add Linux-friendly examples for generating and signing JWTs, such as using OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken).
- Mention cross-platform libraries and CLI tools that can be used for JWT creation and signing.
- Explicitly state that the provided C# example is Windows-centric and provide guidance for developers on other platforms.
- Include step-by-step instructions for generating the client secret JWT on Linux/macOS, possibly using bash scripts or other common tools.
- Ensure that all configuration steps are platform-agnostic or provide parallel instructions for both Windows and Linux environments.
App Service
Manage App Service Certificates
...s/app-service/configure-ssl-app-service-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting App Service certificates, but the PowerShell example is given its own section and is referenced in the FAQ. There are no explicit Linux-specific instructions or examples, and the PowerShell example may implicitly prioritize Windows users. The CLI example is cross-platform, but the documentation does not clarify this or provide parity guidance for Linux users.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
- Add a note or section for Linux/macOS users, clarifying that PowerShell is optional and not required.
- Where PowerShell is referenced (such as in the FAQ), also mention the CLI as an alternative for non-Windows environments.
- Consider providing bash or shell script examples for common certificate management tasks.
- Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., avoid references to Windows-specific file dialogs or paths).
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 before mentioning REST API and CLI. There are no explicit Linux-specific examples, tools, or parity notes, and Windows-centric tools are referenced without Linux alternatives.
Recommendations
- Add explicit examples for Linux users, such as using Bash, Azure CLI, or cross-platform editors (e.g., VS Code) for monitoring and diagnostics tasks.
- When listing tools or methods (e.g., PowerShell, REST API, CLI), present them in a neutral or alphabetical order, or highlight cross-platform options first.
- Include references to Linux logging and monitoring patterns, such as integration with syslog, journald, or other Linux-native tools.
- Mention and provide examples for using Azure CLI and REST API for all tasks where PowerShell is referenced.
- If Visual Studio is mentioned, also mention VS Code and other cross-platform IDEs for Application Insights integration.
App Service
Set Up Azure Arc for App Service, Functions, and Logic Apps
.../articles/app-service/manage-create-arc-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell (Windows) examples are always presented alongside Bash, never Linux-specific shell variants (e.g., zsh, fish) or macOS-specific instructions. The use of PowerShell tabs and syntax throughout the page, and the absence of explicit Linux/macOS instructions or troubleshooting, indicates a mild Windows bias. Additionally, some variable naming conventions and explanations (e.g., use of `$` for variables in PowerShell) may be more familiar to Windows users.
Recommendations
- Add explicit Linux/macOS instructions or troubleshooting notes, especially for common issues (e.g., file permissions, environment variable syntax differences).
- Include examples for other popular shells (e.g., zsh, fish) or clarify that Bash instructions are suitable for most Unix-like systems.
- Provide guidance for running Azure CLI commands on Linux/macOS, including installation and environment setup.
- Mention platform-specific nuances, such as differences in base64 encoding flags (`-w0` vs. `-b 0`) and file path conventions.
- Consider reordering examples so that Bash (Linux/macOS) instructions appear before PowerShell (Windows), or clarify parity in the introduction.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash and PowerShell examples, but the PowerShell example includes extra guidance specific to PowerShell users (about quoting the username), which is not mirrored for Bash. The initial instructions reference the Azure portal, which is platform-neutral, but the inclusion and detailed explanation for PowerShell may indicate a slight Windows bias. Bash is presented first, but the PowerShell section is more verbose and assumes a need for special handling, which can suggest a Windows-centric perspective.
Recommendations
- Provide equivalent Bash-specific guidance if there are any common pitfalls (e.g., quoting, escaping).
- Include examples for other Linux shells or CLI tools if relevant (e.g., wget, Linux-native curl usage nuances).
- Balance the depth of explanation between Bash and PowerShell sections to avoid implying one platform is primary.
- Explicitly mention cross-platform compatibility and note any differences in behavior between Windows and Linux environments.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions first and in greater detail, with explicit module installation steps. The Azure CLI example is provided, but only after the PowerShell example, and the overall scripting guidance leans toward Windows-centric tools and workflows. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side.
- Include Bash shell examples for Linux users, especially for scripting tasks.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
- Avoid assuming Visual Studio (Windows) as the default deployment tool; mention alternatives like VS Code or command-line deployments.
- Add notes or sections for Linux users, clarifying any differences in workflow or tool usage.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for key tasks, but PowerShell examples are consistently listed before Azure CLI. This ordering, along with the detailed PowerShell scripts, may suggest a subtle preference for Windows-centric tooling and workflows, especially since PowerShell is traditionally associated with Windows environments. However, Linux users are not excluded, as Azure CLI (which is cross-platform) examples are provided for all major steps. There are no examples or references that are strictly Windows-only, nor are Linux-specific tools or shell scripts missing.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and widely used in Linux environments.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, to reinforce cross-platform support.
- Where possible, provide bash shell script examples in addition to Azure CLI, to further support Linux users.
- Add a note clarifying that PowerShell Core is available cross-platform, but that Azure CLI is often the preferred choice for Linux users.
- Ensure that all screenshots and UI instructions are not Windows-specific (e.g., avoid references to Visual Studio unless alternatives are given).
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Medium 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 consistently presented alongside or immediately after CLI examples. There is no mention of Linux-specific tools or shell environments (e.g., Bash), and PowerShell is a Windows-centric tool, though it is available cross-platform. The documentation does not provide Linux shell (bash) examples, nor does it reference Linux-specific patterns or troubleshooting steps. The overall structure and example ordering (CLI, then PowerShell) may subtly prioritize Windows users, and the use of PowerShell may reinforce a Windows-centric approach.
Recommendations
- Add explicit Bash shell examples for all command-line operations, especially for Azure CLI commands, to demonstrate usage in Linux environments.
- Clarify that Azure CLI commands are cross-platform and provide guidance for running them in Bash or other Linux shells.
- Include troubleshooting steps or notes for Linux environments where relevant (e.g., file permissions, networking differences).
- If PowerShell is mentioned, note its cross-platform availability and provide links or instructions for installing PowerShell on Linux.
- Consider reordering examples to present CLI/Bash first, then PowerShell, to avoid implicit Windows prioritization.
- Reference Linux tools or patterns where appropriate (e.g., using curl, jq, or other common Linux utilities in networking scenarios).
App Service
Securely connect .NET apps to resources using the Entra agent identity platform
...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-first bias by exclusively referencing Azure App Service and Azure Functions, which are commonly associated with Windows environments, and by providing only C# code examples. There are no Linux-specific instructions, examples, or references to Linux-native tools or deployment patterns (such as Azure App Service for Linux, container-based deployment, or Bash scripting). The documentation also omits any mention of Linux-specific environment variable configuration, shell commands, or cross-platform deployment considerations, making it less accessible for Linux users.
Recommendations
- Add explicit instructions and examples for deploying .NET agent apps on Azure App Service for Linux and Linux-based Azure Functions.
- Include Linux shell (Bash) commands for environment variable configuration and deployment steps alongside any Windows/Powershell instructions.
- Provide C# code examples that highlight cross-platform compatibility and mention any platform-specific considerations.
- Reference container-based deployment options (e.g., Docker) for .NET apps, which are popular in Linux environments.
- Clarify that the steps and code samples apply equally to Linux-based hosting, and call out any differences in configuration or tooling.
- If using environment variables, show how to set them in both Windows and Linux environments (e.g., using 'set' vs 'export').
App Service
Authentication and Authorization
...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 first and only example of platform-specific integration. There are no explicit Linux or cross-platform command-line examples, and the only platform-specific tool mentioned is IIS (Windows). However, the rest of the documentation is generally platform-neutral, with configuration examples using Azure Resource Manager and az CLI, which are cross-platform.
Recommendations
- Present Linux/container architecture before or alongside Windows architecture, rather than after.
- Explicitly mention Linux equivalents to IIS modules, such as the use of Ambassador pattern and containerized middleware, and provide links to relevant Linux/container documentation.
- Include examples or references for troubleshooting and logging on Linux (e.g., where to find logs, how to enable tracing in Linux environments).
- If mentioning Windows tools (IIS), also mention Linux web server equivalents (e.g., Nginx, Apache) and clarify how authentication/authorization integrates in those environments.
- Ensure that any platform-specific instructions (such as configuration file locations, log file paths) are provided for both Windows and Linux.
- Add Linux-focused samples or tutorials in the 'Related content' section, if available.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references Windows-specific tools and features, such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps, without mentioning Linux equivalents or clarifying Linux support. There are no examples or features highlighted for Linux-based App Service environments.
Recommendations
- Include information about Kudu features and diagnostics available for Linux-based App Service apps, such as access to Docker logs, process management, and deployment options.
- Clarify which features are Windows-only and which are available on Linux, especially for items like IIS diagnostics and site extensions.
- Provide examples or documentation links relevant to Linux users, such as using the Kudu console or REST API for Linux-based apps.
- Balance the mention of Windows and Linux features/tools to ensure parity and help users on both platforms.
App Service
Quickstart: Use Terraform to configure an Azure App Service Environment v3
...articles/app-service/environment/creation-terraform.md
Medium 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, despite being primarily a Windows tool. There is no explicit mention of Linux shell equivalents (e.g., bash), and PowerShell is presented as a standard option, which may imply a Windows-centric approach. The rest of the guide is platform-neutral, but the verification steps could be improved for Linux parity.
Recommendations
- Explicitly mention that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows environments, and suggest alternatives for Linux users.
- Add bash-specific examples or notes where environment variable syntax differs between platforms.
- Ensure that all steps (including verification and cleanup) have clear, platform-neutral instructions or explicitly note platform-specific commands.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but PowerShell (a Windows-centric tool) is given its own section and example, while no equivalent Linux shell scripting (e.g., Bash) or Linux-specific automation guidance is provided. In the SKU availability section, Windows examples are listed before Linux examples, and the overall structure and screenshots focus on the Azure Portal, which is platform-agnostic but often used more heavily by Windows users. There is no mention of Linux-native tools or scripting patterns beyond Azure CLI.
Recommendations
- Add explicit Bash shell script examples for Linux users, especially for automation tasks.
- Ensure Linux examples (e.g., az CLI with Linux-specific flags) are presented before or alongside Windows/PowerShell examples.
- Include notes or links to Linux-native tools and scripting environments where relevant.
- Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and provide sample usage in a Linux terminal.
- Consider adding screenshots or walkthroughs using Linux environments (e.g., Ubuntu terminal, VS Code on Linux) to balance visual representation.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are given equal or greater prominence, including in advanced scenarios and code blocks. There is a notable presence of PowerShell-specific instructions and examples, which may be more familiar to Windows users. While Azure CLI is cross-platform and examples are present, PowerShell is a Windows-centric tool and its heavy inclusion can be seen as a Windows bias. No Linux-specific shell (e.g., Bash) or OS-specific instructions are provided, and there is no mention of Linux-native tools or patterns. The order of examples sometimes places PowerShell before CLI, and advanced scenarios (such as multi-source rules and Front Door filtering) use PowerShell exclusively, with no CLI equivalent shown.
Recommendations
- Ensure that for every PowerShell example, an equivalent Azure CLI example is provided, especially in advanced scenarios (e.g., multi-source rules, Front Door filtering).
- Where possible, provide Bash script examples for Linux users, or clarify that Azure CLI commands are fully supported on Linux/macOS.
- Explicitly state cross-platform compatibility for CLI instructions and highlight that PowerShell Core is available on Linux/macOS if relevant.
- Review the ordering of examples to present Azure CLI (cross-platform) before PowerShell, or alternate the order to avoid implicit prioritization.
- Add a section or note for Linux users, confirming that all features and instructions are supported on Linux-hosted App Service workloads and can be managed from Linux environments.