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 1526-1550 of 2121 flagged pages
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 Windows bias by providing only C# code examples that rely on Windows-specific APIs (such as CngKey and ECDsaCng), and by referencing Azure PowerShell and Azure CLI in the management caution note before mentioning any Linux alternatives. There are no examples or guidance for generating the client secret JWT using Linux tools, open-source cross-platform libraries, or command-line utilities commonly available on Linux systems.
Recommendations
- Add examples for generating the client secret JWT using cross-platform tools such as OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken), which are widely available on Linux.
- Provide sample shell commands or scripts for Linux environments to extract and use the .p8 key file.
- Mention Linux-native management tools (such as Azure CLI on Linux) explicitly and clarify their parity with Windows tools.
- Ensure that code samples do not rely solely on Windows-specific libraries or APIs, or provide equivalent alternatives for Linux and macOS users.
- Include a note or section on platform compatibility for all steps, especially those involving cryptographic operations.
Create Pull Request
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 it lists the Azure portal and Azure CLI first, followed by Azure PowerShell. There are no explicit Linux-specific instructions or examples, but the CLI examples are cross-platform. However, the PowerShell example is included as a primary method, which may suggest a slight Windows/PowerShell bias, especially since there is a FAQ entry specifically about exporting with PowerShell. There are no references to Windows-only tools or patterns, but the lack of explicit Linux shell (e.g., Bash, OpenSSL) examples or troubleshooting tips may disadvantage Linux users.
Recommendations
- Add explicit Bash/Linux shell examples for exporting and handling certificates, such as using curl or OpenSSL to process the downloaded .pfx file.
- Clarify that Azure CLI commands work cross-platform and can be run on Linux, macOS, and Windows.
- Include troubleshooting tips or notes for Linux/macOS users, such as how to install and use the Azure CLI and handle .pfx files on non-Windows systems.
- If mentioning PowerShell, also mention that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
- Ensure that any references to file paths or environment variables are platform-neutral or provide both Windows and Linux/macOS examples.
App Service
Custom Container CI/CD from GitHub Actions
...articles/app-service/deploy-container-github-action.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows container workflow examples using GitHub Actions, with clear separation via pivots. However, in several places, Windows-specific tools (such as Azure PowerShell) are mentioned alongside cross-platform tools (Azure CLI and portal), and Windows authentication patterns (publish profile, PowerShell) are described in detail. In credential generation and service principal creation, Azure PowerShell is listed as an option before Linux-native alternatives, and the publish profile workflow is rooted in a Windows-centric deployment model. The documentation does not exhibit strong bias, but Windows tools and patterns are presented on equal footing or sometimes before Linux equivalents, which may subtly reinforce Windows as the default or primary platform.
Recommendations
- When listing authentication or credential generation options, mention Azure CLI (cross-platform) before Azure PowerShell (Windows-centric) to reinforce Linux parity.
- Clarify which tools and steps are platform-agnostic and which are Windows-specific, especially in credential generation and deployment steps.
- In the publish profile sections, note that this is a legacy/Windows-centric pattern and recommend service principal or OpenID Connect for Linux-first workflows.
- Add explicit notes or callouts in the authentication and deployment sections to highlight Linux-native workflows and best practices.
- Ensure that all example workflows and code snippets are presented with Linux-first ordering or with clear parity between Linux and Windows, especially in introductory and summary sections.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given equal prominence to Azure CLI, and the narrative often references Visual Studio and Windows-centric workflows before mentioning cross-platform alternatives. The portal instructions implicitly assume familiarity with Windows environments, and there is no mention of Linux-specific tooling or shell environments (e.g., Bash, zsh). While Azure CLI is included, which is cross-platform, there are no explicit Linux examples, nor are Linux-specific considerations (such as authentication or environment setup) discussed.
Recommendations
- Add explicit Linux/Bash examples and clarify that Azure CLI commands work on Linux and macOS, not just Windows.
- Include references to Linux-native editors and deployment workflows (e.g., VS Code on Linux, deployment from Bash/zsh).
- Mention Linux-specific authentication steps if they differ (e.g., az login with device code on headless servers).
- Balance PowerShell and CLI examples by occasionally leading with CLI/Bash instructions.
- Add a note about cross-platform compatibility for all command-line instructions.
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. While Azure CLI examples are provided, the initial focus and depth favor PowerShell, which is primarily a Windows-centric tool. There are no Linux shell (bash) or cross-platform scripting examples, nor is there mention of Linux-specific considerations or parity in tooling.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Include bash shell script examples for Linux users, especially for steps involving environment variables and scripting.
- Add notes or sections highlighting Linux-specific workflows or considerations when managing managed identities and Microsoft Graph permissions.
- 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 references do not assume a Windows environment (e.g., Visual Studio), and mention alternatives for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-cli.md
...es/tutorial-nodejs-mongodb-app/deploy-local-git-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell is given equal prominence as Bash, which may suggest a Windows bias. The use of PowerShell tabs and variable syntax can be more familiar to Windows users, and there is no explicit mention of Linux-specific considerations or parity. However, Linux users are not excluded, as Bash examples are present.
Recommendations
- Ensure that Bash examples are presented first, as Bash is the default shell on most Linux and macOS systems.
- Add a short note clarifying that Bash examples apply to Linux/macOS and PowerShell examples to Windows, to help users choose the correct tab.
- Consider including additional Linux-specific tips, such as handling environment variables or authentication nuances on Linux systems.
- If there are platform-specific caveats (e.g., file path formats, credential storage), mention them explicitly for both Windows and Linux.
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 demonstrates mild Windows bias in its architecture section, where Windows (IIS module) is described before Linux/container equivalents, and the Windows-specific technology (IIS module) is mentioned by name. However, the page does provide Linux/container details and does not use Windows-only tools or examples elsewhere. No PowerShell-heavy or missing Linux example bias is present, and CLI examples use cross-platform Azure CLI.
Recommendations
- Present Linux/container architecture details before or alongside Windows details, rather than after.
- Avoid referring to Windows-specific technologies (e.g., IIS module) without equal mention of Linux/container equivalents.
- Include explicit examples or links for Linux/container deployments where configuration or troubleshooting may differ.
- Ensure that any referenced samples or tutorials include Linux/container scenarios, not just Windows/IIS.
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 command-line steps, but PowerShell examples are consistently presented alongside Bash, with no parity for Linux-specific shell environments (e.g., zsh, fish) or explicit mention of Linux distributions. The use of PowerShell as the only alternative to Bash suggests a Windows-centric approach, and there is no mention of Linux-specific tooling or troubleshooting. Additionally, some variable naming conventions and explanations (such as use of `$` for variables in PowerShell) may be more familiar to Windows users.
Recommendations
- Explicitly mention Linux as a supported platform and provide examples or notes for common Linux distributions (Ubuntu, CentOS, etc.), especially where commands or tooling may differ.
- Add troubleshooting notes for Linux users, such as file permission issues, shell differences, or package manager commands for installing prerequisites.
- Include examples for other popular shells (e.g., zsh, fish) or clarify that Bash examples are applicable to most Linux environments.
- Where PowerShell is used, clarify that it is available cross-platform, but also provide guidance for users who may not have PowerShell installed (e.g., default Ubuntu environments).
- Review variable naming and scripting conventions to ensure they are not overly tailored to Windows/PowerShell users.
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 (such as Bash scripts), nor is there any mention of Linux-native tools or patterns. The documentation does not reference Windows-specific tools, but the inclusion of PowerShell throughout and the lack of Linux shell examples indicates a subtle Windows bias.
Recommendations
- Add Bash shell examples for all CLI commands, demonstrating usage in a typical Linux environment.
- Clarify that Azure CLI commands can be run on both Windows and Linux, and provide guidance for Linux users where appropriate.
- Consider listing CLI/Bash examples before PowerShell to reflect the cross-platform nature of Azure and Kubernetes.
- Explicitly mention Linux compatibility and provide troubleshooting tips for Linux users where command syntax or environment may differ.
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 given equal prominence to CLI. However, there is no mention of Linux-specific tools or shell environments (e.g., Bash), and PowerShell is traditionally a Windows-centric tool, though it is now cross-platform. The documentation does not reference Linux-specific patterns, nor does it acknowledge differences in experience for Linux users. The ordering of examples (CLI before PowerShell) is neutral, but the inclusion of PowerShell throughout and the absence of Linux/Bash-specific guidance suggests a subtle Windows bias.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash on Linux and provide Bash-specific syntax or notes where appropriate.
- Clarify that PowerShell examples are cross-platform, but also provide Bash alternatives for common operations.
- Add troubleshooting notes or tips for Linux users, especially regarding environment setup and authentication differences.
- Include references to Linux-native tools or workflows (e.g., using SSH, Bash scripting) where relevant.
- Ensure that documentation does not assume familiarity with Windows concepts or tools, and provide parity in guidance for Linux environments.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by mentioning Visual Studio integration with Application Insights and listing PowerShell as a primary method for querying Azure activity logs, without equal mention or prioritization of Linux tools or workflows. There are no explicit Linux or Bash examples, and Windows-centric tools are referenced before cross-platform or Linux alternatives.
Recommendations
- Add explicit examples for querying Azure activity logs using Bash/CLI alongside PowerShell.
- Mention integration options for Application Insights with popular Linux-based development environments (e.g., VS Code, JetBrains IDEs) in addition to Visual Studio.
- Ensure references to cross-platform tools (Azure CLI, REST API) appear before or alongside Windows-specific tools like PowerShell.
- Include troubleshooting and monitoring scenarios/examples that use Linux-native tools and commands.
- Clarify that all monitoring features are available and supported on both Windows and Linux App Service plans.
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 bias toward Windows environments by exclusively referencing Azure App Service and Azure Functions, which are traditionally Windows-centric, and by providing only .NET/C# code samples. There are no examples or guidance for Linux-specific deployment scenarios, such as using Azure App Service for Linux, container-based deployments, or cross-platform command-line tooling. The documentation does not mention Linux tools, shell commands, or provide parity for Linux users in setup or configuration steps.
Recommendations
- Add explicit instructions and examples for deploying .NET agent apps to Azure App Service for Linux, including any differences in managed identity assignment and environment variable configuration.
- Include Linux shell (bash) commands for relevant steps, such as setting environment variables, deploying with Azure CLI, or managing identities.
- Provide parity in code samples by including examples for other .NET-supported platforms (e.g., .NET on Linux containers) and clarify any platform-specific considerations.
- Reference cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools, and ensure that documentation does not assume a Windows development environment.
- Highlight any differences in authentication, identity assignment, or resource access between Windows and Linux hosting environments.
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 the PowerShell tab is present and detailed, which can suggest a Windows-centric approach. The PowerShell examples are given equal prominence as Azure CLI, but PowerShell is primarily a Windows tool (though now cross-platform). There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific patterns or tools. The order of tabs places Azure CLI first, which is more cross-platform, but the inclusion and detail of PowerShell examples may indicate a slight Windows bias.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps, especially for users who may not use PowerShell.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide guidance for Linux users where appropriate.
- If PowerShell is included, note that it is available cross-platform, but also provide equivalent Bash commands for parity.
- Consider adding a section or tab specifically for Linux users, highlighting any differences or additional steps.
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 provides step-by-step instructions for both Azure Portal (GUI), PowerShell, and Azure CLI. However, PowerShell examples are given before Azure CLI, and there is no mention of Linux-specific tools or patterns (e.g., Bash scripts, Linux shell usage, or Linux-specific considerations). PowerShell is a Windows-centric tool, and its precedence in the documentation may signal a Windows bias. There are no explicit Linux examples or references to Linux environments, even though Azure CLI is cross-platform.
Recommendations
- Provide explicit Bash or Linux shell script examples alongside PowerShell, especially for command-line operations.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant (e.g., authentication, environment setup).
- Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform.
- Mention Linux tools (such as curl, jq, or bash scripting) where appropriate, especially for automation scenarios.
- Add a note or section for Linux users, including any differences in workflow or troubleshooting tips.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
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 dedicated section and example, while Linux-native scripting options (such as Bash or shell scripts) are not mentioned. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux SKU availability, suggesting a Windows-first ordering. No Linux-specific tools or patterns (e.g., Bash scripts, deployment via Linux terminal) are discussed, and screenshots and instructions focus on the Azure Portal, which is platform-agnostic but often associated with Windows usage.
Recommendations
- Add Linux/Bash shell script examples for automating App Service plan creation and scaling, alongside Azure CLI and PowerShell.
- Ensure Linux SKU availability commands are presented before or alongside Windows commands, not after.
- Explicitly mention that Azure CLI commands can be run natively on Linux/macOS terminals, not just in Cloud Shell.
- Include notes or examples for deploying and managing App Service plans from Linux environments, such as using Bash scripts or integrating with Linux-based CI/CD pipelines.
- Balance the prominence of PowerShell and CLI examples, or provide parity for Linux-native scripting approaches.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
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 is featured prominently and is given equal or greater weight than Azure CLI. PowerShell examples are shown for advanced scenarios (multi-source rules, Front Door filtering) without corresponding Bash or Linux-native scripting examples. The documentation assumes familiarity with PowerShell syntax and patterns, which are most common on Windows. There are no explicit Bash, shell script, or Linux-native command examples outside of Azure CLI, and PowerShell is presented as a first-class option throughout, suggesting a Windows-centric approach.
Recommendations
- Add Bash/shell script equivalents for all PowerShell examples, especially in advanced scenarios.
- Clarify that Azure CLI works cross-platform and highlight its parity with PowerShell for Linux users.
- Where PowerShell is shown, provide a corresponding Bash/Azure CLI snippet side-by-side.
- Explicitly mention Linux usage in programmatic sections, e.g., how to use Azure CLI from Linux terminals.
- Consider reordering examples to show Azure CLI (cross-platform) before PowerShell (Windows-centric) in each tab group.
- Add notes or links for Linux users on installing and using Azure CLI and Azure PowerShell Core (if relevant) on Linux.
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 page demonstrates Windows bias by referencing Azure PowerShell and Azure CLI management experiences before mentioning any Linux alternatives. The only code example for generating the client secret JWT uses C# and the Microsoft.IdentityModel.Tokens NuGet package, which is most commonly used on Windows. There are no examples or guidance for generating the JWT using Linux-native tools (such as OpenSSL, Python, or Node.js), nor is there mention of Linux-specific workflows or shell commands.
Recommendations
- Add Linux-native examples for generating the client secret JWT, such as using OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken).
- Explicitly mention that the configuration steps can be performed on both Windows and Linux, and provide parity in tooling references.
- Include shell commands and scripts for Linux environments where appropriate, especially for file manipulation and JWT signing.
- Reference cross-platform libraries and tools, and avoid implying that Windows tools or PowerShell are required or preferred.
- If Azure CLI is mentioned, clarify that it is cross-platform and provide example usage on Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-app-service-certificate.md
...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 PowerShell examples for exporting certificates, but the PowerShell example is given its own dedicated section, and PowerShell is referenced in the FAQ. There are no explicit Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools and patterns (such as PowerShell), which may disadvantage Linux users. The Azure CLI example is cross-platform, but Linux-specific nuances or alternative tools are not discussed.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if necessary (such as file permissions or environment variables).
- Add Linux shell (bash) examples for common certificate management tasks, especially for exporting and handling certificates, to demonstrate parity.
- Avoid referencing PowerShell in FAQs or troubleshooting sections as the default, or provide equivalent CLI/bash guidance.
- Where screenshots or UI steps are shown, clarify that the steps are platform-agnostic or note any differences for Linux users.
- Consider including a table or section summarizing which tools (Azure CLI, PowerShell, portal) are available and supported on each OS.
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 narrative and instructions reference the Azure portal UI, which is primarily accessed on Windows. The PowerShell example includes a specific note about quoting, giving it more attention than the Bash example. There is no mention of Linux-specific tools or command-line patterns beyond Bash, and the order of examples places Bash first, but the instructions themselves do not clarify cross-platform differences or alternatives to the Azure portal for Linux users.
Recommendations
- Add explicit instructions for accessing Kudu and deployment endpoints from Linux environments, such as using Azure CLI or direct URLs.
- Include Linux-native tools or workflows (e.g., wget, scp) as alternatives to PowerShell and Bash.
- Clarify that the Azure portal and Kudu are accessible from any OS/browser, and mention any platform-specific caveats.
- Balance example details (e.g., quoting, authentication) for both Bash and PowerShell, ensuring parity in troubleshooting tips.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-create-arc-environment.md
.../articles/app-service/manage-create-arc-environment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell is given equal prominence throughout, which is uncommon for Linux-focused workflows. There is a slight Windows-first bias in the use of PowerShell, which is primarily a Windows shell, and in the explicit inclusion of PowerShell examples for every command, even though the Azure CLI and Kubernetes tools are cross-platform and Bash is the standard on Linux. There are no examples or notes for Linux-specific environments, nor are there troubleshooting tips for Linux users. The documentation does not mention Windows-only tools, but the parity of PowerShell and Bash may suggest a slight preference for Windows users.
Recommendations
- Make Bash the default or primary example, with PowerShell as an optional tab for Windows users.
- Add explicit notes or troubleshooting sections for Linux environments (e.g., differences in base64 encoding, file paths, or permissions).
- Clarify that PowerShell examples are intended for Windows users, and Bash for Linux/macOS.
- Include examples for common Linux distributions (e.g., Ubuntu, CentOS) where relevant, especially for prerequisites and environment setup.
- Remove unnecessary PowerShell examples for steps that are identical in Bash and PowerShell, or collapse them into a single cross-platform example where possible.
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 consistently lists PowerShell examples immediately after CLI, without any Linux shell-specific examples (e.g., Bash scripts, shell pipelines). There is no mention of Linux-native tools or patterns, and the structure implicitly prioritizes Windows tooling by including PowerShell in every example section. Additionally, while the migration target is Linux-only, the documentation does not provide Linux shell alternatives for management tasks.
Recommendations
- Add explicit Bash/shell examples for resource queries, especially for users on Linux or macOS.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux environments (e.g., installation, authentication).
- Consider reordering examples to list CLI (cross-platform) first and PowerShell second, or provide a Linux-specific tab.
- Include troubleshooting or management steps using Linux-native tools (kubectl, bash scripts) where appropriate.
- Explicitly state that PowerShell is optional and not required for Linux users.
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 provides step-by-step instructions for migration using the Azure portal, Azure CLI, and Azure PowerShell. However, PowerShell examples are given equal prominence to CLI, and the documentation does not mention Linux-specific tools or shell environments (e.g., Bash, Cloud Shell, or scripting on Linux). PowerShell is a Windows-centric tool, and its inclusion alongside CLI without clarification may imply a Windows-first approach. There are no Linux-specific examples, nor is there guidance for Linux users on alternative scripting or automation approaches.
Recommendations
- Clarify that Azure CLI commands can be run cross-platform (Windows, Linux, macOS), and recommend CLI for Linux users.
- Add explicit Bash shell examples for Linux users, especially for scripting and automation steps.
- Mention that PowerShell Core is available on Linux, but provide guidance for users who prefer native Bash or shell scripting.
- Include notes or tabs indicating which instructions are best suited for Windows vs. Linux environments.
- Where possible, avoid implying PowerShell is the default or preferred automation tool for all users; highlight CLI and Bash parity.
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 demonstrates 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 workflows. There are no Linux-specific examples, and Windows-centric tools are referenced before cross-platform or Linux alternatives.
Recommendations
- Include examples using Azure CLI and Bash scripts alongside PowerShell for querying activity logs and managing monitoring features.
- Mention integration options for popular Linux development environments (e.g., VS Code, JetBrains IDEs) in addition to Visual Studio.
- Add references to Linux-native monitoring tools or workflows (such as syslog, journald, or open-source log shippers) where relevant.
- Ensure that cross-platform tools (CLI, REST API) are listed before or alongside Windows-specific tools like PowerShell.
- Provide explicit guidance for users deploying and monitoring App Service from Linux environments.
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 focuses exclusively on Azure App Service and Azure Functions, with all code and deployment examples oriented toward .NET (C#) applications. There is no mention of Linux-specific deployment patterns, tools, or configuration steps, nor are there any examples for Linux-based environments or cross-platform command-line usage. The documentation implicitly assumes a Windows-centric workflow, especially in its references to App Service and Azure Functions, which are often associated with Windows hosting, and in the lack of Linux or cross-platform alternatives for environment configuration, deployment, or identity management.
Recommendations
- Add explicit instructions and examples for deploying and configuring agent identity on Linux-based App Service plans and Azure Functions (e.g., using Linux containers or Python/Node.js stacks).
- Provide cross-platform command-line examples (e.g., Azure CLI, Bash scripts) for identity creation, blueprint configuration, and environment variable setup, alongside any PowerShell or Windows-specific instructions.
- Clarify which steps and code samples are applicable to both Windows and Linux hosting environments, and note any differences or additional requirements for Linux.
- Include references to Linux tools and patterns (such as systemd for background agents, or environment variable configuration via appsettings.json or .env files) where relevant.
- Ensure parity in troubleshooting and deployment guidance for both Windows and Linux platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
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 standalone PowerShell code blocks outside the tabbed CLI/PowerShell/ARM/Bicep sections. PowerShell is a Windows-centric tool, and its heavy use may indicate a Windows bias. Additionally, in advanced scenarios (multi-source rules, Azure Front Door restriction), only PowerShell examples are shown, with no equivalent Azure CLI or Linux shell examples. However, the main tabbed code sections do include Azure CLI, which is cross-platform, and ARM/Bicep templates, which are OS-neutral.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI example, especially in advanced scenarios (multi-source rules, Azure Front Door restriction).
- Where PowerShell is used outside tabbed sections, add Azure CLI (bash) examples side-by-side.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider adding bash script examples for common tasks to further support Linux users.
- Review screenshots and UI instructions for any Windows-specific references and clarify that the Azure portal is web-based and OS-neutral.