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 176-200 of 247 flagged pages
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but PowerShell is presented first and in greater detail, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows, and the initial mention of Visual Studio (a Windows-centric IDE) further reinforces the Windows-first approach.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell, or side-by-side, to avoid implying a Windows-first workflow.
- Add bash-specific examples and clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Mention cross-platform IDEs (e.g., VS Code) alongside Visual Studio when discussing publishing/deployment.
- Explicitly state that the steps and tools are applicable to both Windows and Linux environments.
- Include troubleshooting notes or tips for Linux users where workflows may differ.
Create Pull Request
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 consistently lists PowerShell examples immediately after Bash, giving them equal prominence. However, there is a subtle Windows bias: PowerShell is featured as the only alternative to Bash, with no mention of Linux-native shells other than Bash (e.g., zsh, fish), nor any explicit Linux-specific instructions or troubleshooting. Additionally, some command explanations and environment variable conventions (e.g., use of $variable vs. $variableName) are tailored to PowerShell, which is primarily a Windows tool, though available on Linux. There are no examples using Linux-specific tools or patterns, and no troubleshooting or notes for Linux-specific scenarios (e.g., file permissions, package managers).
Recommendations
- Add explicit notes or troubleshooting steps for Linux environments, such as file permissions, package installation, or differences in CLI behavior.
- Include examples for other popular Linux shells (e.g., zsh, fish) or clarify that Bash instructions apply to all POSIX-compliant shells.
- Mention Linux package managers (apt, yum, etc.) for installing prerequisites like Azure CLI and kubectl.
- Clarify that PowerShell is available on Linux, but Bash is the default shell for most Linux distributions.
- Provide guidance for users working in native Linux environments, such as handling environment variables, file paths, and permissions.
- Consider adding a 'Linux-specific considerations' section to address common issues faced by Linux users.
App Service
Create an App Service app using an Azure Resource Manager template
...b/main/articles/app-service/quickstart-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation uses a zone pivot system to separate Windows, Linux, and Windows container instructions, providing parity in examples and template links for each platform. However, there is mild Windows bias: the Windows pivot appears first in every section, and references to deployment methods mention Azure PowerShell (a Windows-centric tool) before Linux alternatives. The template review and deployment instructions are well-matched for both platforms, but the overall structure and ordering favor Windows.
Recommendations
- Rotate or randomize the order of platform pivots so Linux is not always listed after Windows.
- When listing deployment methods, mention cross-platform tools (Azure CLI, REST API) before Windows-specific tools like Azure PowerShell.
- Ensure that any referenced samples, screenshots, or next steps are equally available for Linux and Windows, and that Linux examples are not less detailed.
- Consider adding a brief note at the top clarifying that all platforms are equally supported and that instructions are available for both.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-mcp.md
...n/articles/app-service/configure-authentication-mcp.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Microsoft Entra ID and Visual Studio Code (with GitHub Copilot) as primary examples, both of which are strongly associated with Windows development environments. There is also a focus on App Service Authentication, which is more commonly used in Windows-centric Azure workflows. No explicit Linux or cross-platform command-line examples (e.g., Bash, curl) are provided, and no mention is made of Linux-specific tools or patterns. However, there are no direct PowerShell examples or exclusive Windows command-line instructions.
Recommendations
- Include Linux-centric examples, such as using Bash or curl to interact with authentication endpoints.
- Mention Linux-friendly identity providers or tools (e.g., Keycloak, Auth0) alongside Microsoft Entra ID.
- Add explicit notes or sections for configuring MCP server authorization in Linux-based App Service environments.
- Provide parity in client registration and consent flows for Linux users, possibly referencing CLI tools available on Linux.
- Ensure that examples and scenarios are not exclusively tied to Visual Studio Code or other Windows-preferred tools.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a detailed PowerShell example first for granting Microsoft Graph permissions, which is a Windows-centric tool. Although an Azure CLI example is also included, PowerShell is presented before CLI, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The instructions reference Visual Studio for publishing, which is primarily a Windows tool, and do not mention Linux development environments or alternatives.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux users.
- Include bash shell script examples for Linux users where applicable.
- Mention Linux-compatible development tools (such as VS Code or command-line deployment) alongside Visual Studio.
- Clarify that all steps can be performed on Linux, macOS, or Windows, and note any platform-specific differences.
- Add notes or links to Linux-specific documentation for enabling managed identity and assigning permissions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/integrate-with-application-gateway.md
...vice/environment/integrate-with-application-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing validation steps such as 'validate the name resolution from a command prompt' and showing screenshots that imply Windows usage (e.g., Windows command prompt and browser). There are no explicit Linux or cross-platform CLI examples for DNS validation, nor are Linux tools (like dig, nslookup on Linux, or curl) mentioned. The instructions and screenshots focus on Azure Portal UI, which is cross-platform, but when command-line validation is referenced, it defaults to Windows terminology and visuals.
Recommendations
- Include Linux-specific examples for DNS validation, such as using 'dig', 'nslookup', or 'host' commands.
- Add screenshots or command snippets from a Linux terminal alongside Windows command prompt examples.
- Use neutral language when referring to command-line validation (e.g., 'from a terminal' instead of 'from a command prompt').
- Explicitly mention that steps can be performed from any OS and provide parity in instructions for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a C# example for generating the client secret JWT using the Microsoft.IdentityModel.Tokens NuGet package, which is Windows/.NET-centric. There are no examples or guidance for Linux-native tools or languages (such as Python, Node.js, or OpenSSL) that are commonly used on Linux platforms. The documentation does not mention or demonstrate how to perform these steps on Linux, nor does it reference Linux-specific tools or workflows.
Recommendations
- Add examples for generating the client secret JWT using cross-platform or Linux-native tools, such as Python (PyJWT), Node.js (jsonwebtoken), or OpenSSL.
- Include command-line instructions for Linux environments, such as using OpenSSL to handle the .p8 key and sign JWTs.
- Reference Linux package managers (apt, yum) for installing necessary libraries, and provide sample scripts for Bash.
- Clarify that the process is not limited to Windows/.NET and explicitly mention Linux compatibility.
- Provide parity in code samples by showing both Windows/.NET and Linux/open-source approaches side-by-side.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-continuous-deployment.md
...n/articles/app-service/deploy-continuous-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. The 'External Git' section explicitly states it is for 'Windows apps', with no mention of Linux or cross-platform scenarios. There are no Linux-specific deployment examples, nor references to Linux tools or workflows. The documentation does not clarify whether the instructions or features apply equally to Linux-based App Service apps, and omits any Linux shell or CLI examples.
Recommendations
- Clarify whether 'External Git' is supported for Linux App Service apps, and provide equivalent instructions/examples for Linux.
- Add explicit Linux deployment examples, such as using Bash, Azure CLI, or Linux-native tools.
- Ensure all features and instructions are described as cross-platform where applicable, or note any platform-specific limitations.
- Avoid language that implies Windows is the default or only supported platform unless that is technically accurate.
- Include screenshots and workflow examples for Linux-based App Service apps if the experience differs.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation-terraform.md
...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 presented as a primary tab alongside CLI, which can indicate a Windows-first approach. There are no Linux-specific shell examples (e.g., Bash) or explicit mention of Linux environments, and PowerShell is highlighted as an equal alternative to CLI, despite being Windows-centric.
Recommendations
- Add explicit Bash shell examples for Linux users, especially for variable assignment and command usage.
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI as the default for parity.
- If PowerShell is included, note its availability on Linux/macOS, or clarify its Windows-centric nature.
- Ensure that instructions for creating files and directories use cross-platform commands (e.g., 'mkdir' and 'cd') or provide alternatives for both Windows and Linux.
- Review all referenced scripts and code snippets to ensure they do not assume a Windows environment (e.g., file paths, environment variable syntax).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/managed-instance/preview-note.md
.../app-service/includes/managed-instance/preview-note.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation explicitly states that the Managed Instance feature is available only for Windows web apps, with Linux and containers not supported. There are no Linux-related examples, instructions, or parity in feature availability.
Recommendations
- Clearly indicate the roadmap or timeline for Linux and container support if available.
- Provide alternative solutions or workarounds for Linux users.
- Include a comparison table showing feature availability across Windows and Linux platforms.
- Add links to Linux-specific documentation or guidance for similar scenarios.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-1.md
...tart-python/create-app-service-visual-studio-code-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure Tools for VS Code extension, which is commonly associated with Windows environments. There are no examples or instructions for Linux users, such as alternative methods for accessing Azure resources or using VS Code on Linux.
Recommendations
- Include instructions for installing and using the Azure Tools extension on Linux.
- Mention any platform-specific differences in accessing the Azure icon or using VS Code extensions.
- Provide screenshots or examples from both Windows and Linux environments to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-2.md
...tart-python/create-app-service-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides steps for using the Azure Tools extension in VS Code without specifying platform-specific instructions. However, it implicitly assumes a Windows environment by not mentioning Linux or macOS, nor does it provide any examples or notes for users on those platforms.
Recommendations
- Explicitly state that the instructions apply to all supported platforms (Windows, Linux, macOS) if true.
- Add notes or examples for Linux users, such as differences in UI, installation, or permissions.
- Include troubleshooting tips for common Linux-specific issues (e.g., file permissions, dependency installation).
- Ensure parity in screenshots and terminology for all platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-1.md
.../quickstart-python/stream-logs-visual-studio-code-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Azure Tools for VS Code extension, which is commonly used on Windows, and does not provide alternative instructions or examples for Linux users (such as using Azure CLI or other cross-platform tools). No Linux-specific guidance or parity is offered.
Recommendations
- Add instructions for enabling streaming logs using Azure CLI, which is available on both Windows and Linux.
- Include examples for common Linux workflows, such as using terminal commands.
- Clarify that the VS Code extension is cross-platform, if applicable, or provide alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/remove-resource-group-azure-portal-2.md
...ckstart-python/remove-resource-group-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions that assume a graphical interface typical of Windows environments, without mentioning equivalent command-line or Linux-native methods for deleting a resource group. There are no examples or guidance for Linux users (e.g., using Azure CLI or shell commands).
Recommendations
- Add instructions for deleting a resource group using the Azure CLI, which works across Windows, Linux, and macOS.
- Include examples of using shell commands (bash) for Linux users.
- Clarify that the graphical interface is available on all platforms, if applicable, or specify platform differences.
- Present both GUI and CLI methods side-by-side to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-ai-agent-web-app-semantic-kernel-foundry-dotnet/configure-model-permissions.md
...c-kernel-foundry-dotnet/configure-model-permissions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses on Azure portal UI steps, which are generally platform-agnostic, but it lacks any mention of command-line alternatives. The only linked instructions are for the Azure portal, which is most commonly used on Windows. There are no examples or references to Linux tools (such as Azure CLI or Bash), nor is PowerShell mentioned, but the absence of Linux command-line instructions creates a subtle Windows-first bias.
Recommendations
- Add instructions for assigning Azure roles using Azure CLI, which is cross-platform and commonly used on Linux.
- Include Bash or shell script examples for Linux users.
- Explicitly mention that the Azure portal is accessible from any OS, and provide parity for command-line steps.
- If PowerShell is referenced elsewhere, ensure equivalent Bash/CLI examples are provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation only describes resource cleanup using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-specific tools or workflows. This can be interpreted as a subtle Windows bias, as Linux users often prefer or require CLI instructions.
Recommendations
- Add Azure CLI examples for deleting the resource group, as the CLI is cross-platform and widely used on Linux.
- Include PowerShell examples if relevant, but ensure CLI instructions are presented first or alongside them.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line operations.
- Consider adding a note or section about automating resource cleanup from Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-2.md
...core-sqldb-app/deploy-from-local-git-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions that are generic but implicitly assume a Windows-style UI (e.g., 'menu on the left side', 'top menu bar'), which may differ on Linux or cross-platform environments. There are no examples or notes about Linux-specific interfaces, nor any mention of command-line alternatives that are common on Linux systems.
Recommendations
- Add explicit notes or screenshots for Linux users, highlighting any UI differences.
- Include command-line instructions (e.g., using Azure CLI) as an alternative to GUI steps.
- Clarify whether the instructions apply identically on Linux, macOS, and Windows, or specify platform differences.
- Ensure parity by referencing both Windows and Linux environments where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md
...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure Portal (GUI), PowerShell, and Azure CLI instructions for key steps. However, PowerShell examples are given before Azure CLI, and there is no mention of Linux-specific tools or shell environments. PowerShell is a Windows-centric tool, and its precedence in the documentation may signal a Windows bias. There are no Bash or Linux shell script examples, nor any explicit references to Linux environments or considerations.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
- Add notes or sections for Linux users, such as how to install and use Azure CLI on Linux, and clarify that PowerShell Core is available cross-platform if PowerShell examples are retained.
- Consider including troubleshooting tips or environment-specific notes for Linux users, especially regarding authentication and permissions.
- Avoid assuming Visual Studio usage, as it is primarily a Windows tool; mention alternatives like VS Code or command-line deployment for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but PowerShell is presented first and in greater detail. PowerShell is traditionally associated with Windows environments, and the initial emphasis may suggest a Windows-centric workflow. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The instructions reference Visual Studio (a Windows-first IDE) for enabling managed identity, with no mention of alternatives for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) first.
- Add explicit bash shell examples where possible, especially for steps that can be performed outside PowerShell.
- Mention cross-platform IDEs (such as VS Code) and deployment methods for enabling managed identity, not just Visual Studio.
- Clarify that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide installation instructions for each platform.
- Ensure screenshots and UI instructions do not assume a Windows environment.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes steps for accessing deployment credentials but does not provide platform-specific instructions or examples. There is no mention of Linux or cross-platform tooling, and the instructions implicitly assume a generic workflow that may default to Windows users. No Linux-specific commands, tools, or considerations are provided.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) environments for using the credentials.
- Mention cross-platform Git usage, including command-line examples for both Windows and Linux.
- Clarify any differences in credential storage or usage between Windows and Linux systems.
- Include screenshots or references for both Windows and Linux UI where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
...php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions that implicitly assume a Windows environment (e.g., 'File System' logging) and does not mention Linux-specific logging options or differences. There are no examples or notes for Linux users, nor is there guidance on how these steps may differ on Linux-based App Service plans.
Recommendations
- Add explicit notes or sections describing how logging works on Linux-based App Service plans.
- Provide Linux-specific examples or clarify if the 'File System' option is available and behaves the same on Linux.
- Mention any differences in log file locations, access methods, or configuration steps for Linux.
- Ensure parity by listing both Windows and Linux options where applicable, and avoid assuming the user is on Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-outbound.md
...ain/articles/app-service/ip-address-change-outbound.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any platform-specific examples or instructions, but it implicitly assumes a Windows-centric context by referencing the Azure portal and common enterprise patterns (such as firewalls and inclusion lists) without mentioning Linux-specific tools or command-line alternatives. There are no examples for Linux environments (e.g., using CLI, iptables, or configuration files), nor is there guidance for users who may manage outbound IPs outside of GUI tools.
Recommendations
- Add examples for managing outbound IP addresses using Azure CLI and PowerShell, and ensure both are presented equally.
- Include instructions for updating outbound IP addresses in common Linux firewall tools (e.g., iptables, ufw) and configuration files.
- Mention how to automate IP address updates using shell scripts or configuration management tools (e.g., Ansible, Bash).
- Present platform-agnostic guidance first, then provide platform-specific examples for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-sidecar/common-faqs.md
...s/app-service/includes/tutorial-sidecar/common-faqs.md
Medium Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux First
Summary
The documentation page focuses on Linux scenarios, specifically mentioning 'code-based Linux apps' and the built-in Linux container as the main container. There are no Windows or PowerShell examples, nor are Windows tools or patterns referenced. The only platform-specific note is about Linux, and Windows scenarios are not discussed or illustrated.
Recommendations
- Add equivalent examples and notes for Windows-based containers, including how sidecars and volume mounts behave in Windows environments.
- Clarify whether the volume mounts feature and sidecar networking work similarly for Windows containers, or note any differences.
- Include explicit Windows container configuration steps or references if supported, or state limitations if not.
- Provide PowerShell or Windows command-line examples where relevant, alongside Linux shell examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/ip-address-change-ssl.md
...lob/main/articles/app-service/ip-address-change-ssl.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes steps using the Azure portal GUI, which is platform-agnostic but omits any command-line examples. There are no references to Linux-specific tools, shell commands, or CLI workflows, nor are there any Powershell or Windows tool references. However, the absence of Linux CLI (e.g., Azure CLI, bash) examples means Linux users do not see parity in automation or scripting options.
Recommendations
- Add Azure CLI command examples for releasing and assigning TLS/SSL IP addresses.
- Include bash shell snippets for DNS record updates using common Linux tools (e.g., dig, nsupdate).
- Explicitly mention that the steps are applicable regardless of OS, and provide links to both Powershell and bash/CLI documentation for advanced users.
- Ensure that automation options (CLI, scripting) are presented alongside GUI instructions for cross-platform parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-app-service-arc.md
...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 example. There are no Linux-specific shell examples (e.g., bash scripts), nor is there mention of Linux-native tools. The documentation does not reference Windows-only tools, but the inclusion of PowerShell examples alongside CLI may signal a Windows-centric approach, especially since PowerShell is primarily associated with Windows environments, despite its cross-platform availability.
Recommendations
- Add bash shell script examples for all resource queries to demonstrate Linux parity.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, while PowerShell is also cross-platform but more familiar to Windows users.
- Consider listing CLI (bash) examples first, as CLI is the most platform-neutral and widely used on Linux.
- Clarify in the documentation that no Windows-only tools are required and that all steps can be performed on Linux systems.
- If PowerShell is included, note its cross-platform support and provide links to installation instructions for Linux users.