Scan Details - Linux-first Docs for Azure

1563

Pages Scanned

33

Pages Flagged

1563

Changed Pages

2.1%

% Pages Flagged

Scan Information

Started At: 2025-09-10 00:00:07

Finished At: 2025-09-10 00:32:49

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides PowerShell-specific instructions and examples (e.g., using the Microsoft Graph PowerShell module and cmdlets like Update-MgDomain) without offering equivalent command-line examples for Linux/macOS users. There is an implicit assumption that administrators will use Windows tools, and no cross-platform alternatives (such as Azure CLI, Bash, or REST API with curl) are mentioned. This limits accessibility for non-Windows users.

Recommendations:

Provide equivalent examples using Azure CLI and/or REST API with curl for Linux/macOS users, especially for operations currently shown only with PowerShell.
Explicitly mention that PowerShell Core is cross-platform, if relevant, and provide installation instructions for non-Windows systems.
Where possible, present REST API examples alongside PowerShell, and show how to invoke them from different platforms.
Review all step-by-step instructions to ensure they are not dependent on Windows-only tools or interfaces, or provide alternatives where necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by providing certificate creation instructions only via PowerShell (a Windows-centric tool) and omitting equivalent Linux/macOS command-line examples (e.g., OpenSSL). There are no references to Linux-native tools or cross-platform approaches for key tasks such as certificate generation, which may hinder non-Windows users.

Recommendations:

For every PowerShell-based example (such as certificate creation), provide equivalent Linux/macOS instructions using OpenSSL or other cross-platform tools.
Explicitly mention that certificate/key generation can be performed on any OS, and provide links or code snippets for Linux/macOS users.
Where possible, use neutral, cross-platform language and tools in examples, or at least present Windows and Linux options side by side.
Add a section or callout for Linux/macOS users, highlighting any OS-specific considerations or recommended tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically referencing a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no Linux or cross-platform alternatives mentioned, and all instructions and screenshots are Windows-specific. No guidance is provided for running or developing the sample on Linux or macOS, nor are any cross-platform frameworks or tools suggested.

Recommendations:

Provide equivalent instructions and examples for running the sample on Linux and macOS, such as using .NET Core/MAUI or Avalonia UI for cross-platform desktop apps.
Include steps for using alternative IDEs like VS Code or JetBrains Rider, which are available on Linux and macOS.
Offer guidance for restoring NuGet packages and running the application from the command line using dotnet CLI, which is cross-platform.
Add screenshots and walkthroughs for non-Windows environments, or clarify the Windows-only scope if no alternatives exist.
Mention any limitations or requirements for running the sample on platforms other than Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, with no mention of equivalent Azure CLI, Bash, or Linux-native methods. The use of PowerShell and lack of Linux/Unix command-line alternatives indicate a Windows-centric bias.

Recommendations:

Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
Include Bash or Linux shell command examples where applicable, especially for certificate management tasks.
Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows users.
Ensure that any references to tools or commands are accompanied by their Linux/macOS equivalents or alternatives.
Review the documentation for other areas where Windows-specific terminology or screenshots could be replaced or supplemented with cross-platform guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias towards Windows environments by exclusively referencing the Azure portal (a web GUI), REST API, Bicep, and ARM templates for configuration, with no mention of Linux-native command-line tools or shell scripting. There are no CLI (az), PowerShell, Bash, or Linux-specific instructions or examples. The workflow assumes use of the Azure portal or infrastructure-as-code tools, which are platform-agnostic but often more familiar to Windows users. The absence of Azure CLI or Bash examples makes it less accessible for Linux users or those preferring command-line automation.

Recommendations:

Add Azure CLI (az) command examples for all major configuration steps, including creating loggers, assigning roles, and enabling diagnostics.
Include Bash shell script snippets for automation scenarios, especially for Linux users.
Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide cross-platform command-line alternatives.
If PowerShell is referenced in other related docs, ensure Bash or Azure CLI equivalents are also provided.
Clarify in the prerequisites and throughout the guide that the instructions are not limited to Windows and can be executed from Linux/macOS environments using CLI tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for command-line operations, specifically for disabling certificate chain validation. There are no equivalent examples for Linux environments (e.g., Bash, Azure CLI), and the use of PowerShell cmdlets assumes a Windows-centric workflow. No Linux-native tools or cross-platform command-line instructions are mentioned.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for tasks like disabling certificate chain validation.
Include Bash shell examples where appropriate, or clarify if the steps are platform-agnostic.
Explicitly mention cross-platform compatibility for all command-line instructions, and note any OS-specific requirements.
Reference Linux tools or workflows (e.g., OpenSSL for certificate management) alongside Windows tools.
Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Microsoft Entra ID (formerly Azure AD) and the Azure portal, which are Windows-centric tools. All configuration steps reference the Azure portal UI and Microsoft-specific workflows, with no mention of Linux command-line alternatives (such as Azure CLI, REST API, or Terraform). There are no examples or instructions for performing equivalent tasks on Linux or via cross-platform tools, and no mention of open-source OAuth providers or non-Microsoft environments.

Recommendations:

Include Azure CLI and REST API examples for all configuration steps, as these are cross-platform and commonly used on Linux.
Reference open-source OAuth 2.0 providers (e.g., Keycloak, Auth0, Okta) and provide example configuration steps for at least one non-Microsoft provider.
Add instructions for configuring OAuth 2.0 in API Management using infrastructure-as-code tools (e.g., Terraform, Bicep), which are platform-agnostic.
Explicitly state that the Azure portal is web-based and accessible from any OS, but offer alternatives for users who prefer command-line or automated workflows.
Provide troubleshooting steps or notes for Linux users, such as environment variable handling, file paths, or authentication methods that differ from Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for command-line operations, with no mention or examples of cross-platform tools such as Azure CLI (az), Bash, or scripting on Linux/macOS. The PowerShell approach is presented as the default and only command-line method, and installation instructions reference Windows-centric tools. There are no Linux or macOS-specific instructions or parity examples, and no mention of Bash, shell, or cross-platform scripting alternatives.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash/shell script examples where appropriate, especially for ARM template deployments.
Explicitly mention that Azure CLI and PowerShell are both supported, and clarify when a step is platform-agnostic.
Provide installation instructions or links for Azure CLI on Linux and macOS, not just PowerShell.
Reorder sections or provide parallel examples so that Linux/macOS users do not feel secondary to Windows users.
Where screenshots or UI steps are shown, note any platform differences or limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page generally maintains platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows file path (%SystemDrive%\drivers\etc\hosts) is mentioned before the Linux/macOS equivalent (/etc/hosts). Additionally, the only external link for 'Creating a record in DNS' points to a legacy Windows Server article, with no Linux or cross-platform DNS guidance provided. There are no command-line examples (PowerShell, Bash, etc.), but the DNS and hosts file examples are Windows-centric.

Recommendations:

List Linux/macOS hosts file path before or alongside the Windows path, or present both together in a neutral way.
Provide links to cross-platform or Linux DNS configuration documentation (e.g., BIND, dnsmasq, or Azure DNS CLI/Bash guides) in addition to or instead of Windows-only resources.
Where external documentation is referenced, ensure parity by including Linux and macOS equivalents, not just Windows Server.
If providing file paths or instructions, use a table or bullet points to show all major OSes equally.
Consider adding CLI or script examples (e.g., Azure CLI, Bash) for common tasks to further improve cross-platform usability.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by exclusively mentioning the Azure PowerShell cmdlet (New-AzApiManagementUser) as the CLI tool for adding users, without referencing equivalent Azure CLI commands or REST API methods that are platform-agnostic. There are no Linux-specific examples or instructions, and the only automation example provided is PowerShell-based, which is most commonly used on Windows.

Recommendations:

Include Azure CLI examples for adding users to the developer portal, as Azure CLI is cross-platform and widely used on Linux and macOS.
Reference REST API methods for user management, providing curl or httpie examples that work on any OS.
Clearly indicate that PowerShell is available on Linux and macOS, but provide parity by listing Azure CLI and REST API options first or alongside PowerShell.
Add a note or section highlighting cross-platform tooling for managing API Management users, ensuring Linux users are not excluded.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for role assignment and management tasks, and references to Windows batch scripts (.bat) for cleanup operations. There are no equivalent examples or instructions for Linux/macOS users, such as Bash scripts or Azure CLI commands. Windows tools and patterns (PowerShell, .bat files) are mentioned exclusively and before any cross-platform alternatives, which may hinder Linux user experience.

Recommendations:

Provide equivalent Azure CLI or Bash script examples for role assignment and management tasks alongside PowerShell scripts.
Include instructions for running cleanup operations using Bash (.sh) scripts for Linux/macOS environments.
Clearly indicate cross-platform compatibility for all scripts and commands, and specify any OS-specific requirements.
Where possible, use platform-agnostic tools (e.g., Azure CLI) in examples before or alongside Windows-specific tools.
Add notes or sections specifically addressing Linux/macOS workflows for common administrative tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples for Azure CLI and Azure PowerShell, with the PowerShell section being Windows-centric. The prerequisites mention Azure CLI and Azure PowerShell, but there is no explicit mention of Linux or Bash-specific guidance, nor are there examples tailored for Linux environments. The PowerShell example assumes a Windows environment, and no alternative is provided for Linux users who may not have access to PowerShell or prefer Bash scripting.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide Bash-specific variable syntax if needed.
Add a Bash shell example alongside the PowerShell example, or clarify that the Azure CLI example is intended for Bash/Unix shells.
Mention installation and usage of Azure CLI and PowerShell on Linux, including links to relevant setup guides.
Avoid assuming PowerShell is the default scripting environment; clarify when examples are Windows-specific.
If PowerShell Core (cross-platform) is supported, note this and provide Linux/macOS usage notes.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples and referencing the Az PowerShell module throughout. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and all automation steps are presented in a Windows-centric manner. The documentation does not mention or provide parity for Linux or cross-platform command-line tools, making it less accessible to users on non-Windows systems.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the PowerShell examples can be run on PowerShell Core on Linux/macOS, if applicable, or clarify any platform limitations.
Provide Bash shell script examples where relevant, especially for common automation scenarios.
Reorganize sections so that cross-platform solutions (such as Azure CLI) are presented before or alongside PowerShell examples, rather than only after.
Include a table or section comparing PowerShell and Azure CLI commands for restoring deleted apps, to help users choose the tool that fits their environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on Windows environments, specifically IIS servers. Only Windows-based migration assistants and PowerShell scripts are mentioned, with no mention of Linux-based .NET hosting environments (such as Kestrel or Apache/Nginx), nor any Linux migration tools or examples. The documentation assumes the source environment is always Windows, omitting guidance for Linux users.

Recommendations:

Add equivalent migration guidance for .NET apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
Include Linux-specific migration tools or scripts, or clarify if such tools are not available.
Provide Linux shell (bash) script examples alongside PowerShell examples.
Mention and document migration paths for .NET Core/ASP.NET Core apps running on Linux.
List Linux migration scenarios and any differences or limitations compared to Windows.
Ensure that tool download links and documentation are available for both Windows and Linux environments, or explicitly state platform support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates subtle Windows bias by referencing Windows-specific tools (such as web.config and iisnode) without providing equivalent Linux guidance or examples. While there is a brief mention of Linux in the Node.js section (regarding PM2), most configuration and troubleshooting advice (e.g., for auto-healing and Node.js settings) assumes a Windows-based environment or omits Linux-specific instructions. Linux-native configuration files and patterns are not discussed, and Windows-centric terminology appears first or exclusively.

Recommendations:

For features like auto-healing, provide Linux-specific configuration guidance (e.g., how to configure auto-healing for Linux-based App Service, or clarify if web.config is not applicable).
When referencing iisnode or web.config for Node.js apps, include equivalent instructions for Linux-based App Service (such as using PM2, environment variables, or other Linux-native process managers and configuration files).
Ensure that all examples and troubleshooting steps are provided for both Windows and Linux environments, or clearly indicate when a feature is platform-specific.
Where Windows tools or patterns are mentioned, provide Linux equivalents either alongside or before the Windows examples to ensure parity and avoid Windows-first bias.
Add explicit notes or links to Linux documentation where platform differences exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows a mild Windows bias: Windows-specific terminology and tools (such as PowerShell) are mentioned before or more prominently than Linux equivalents. For example, the Azure PowerShell section is given equal prominence to Azure CLI, but there is no mention of Bash scripting or Linux shell automation. In the 'Premium V3 availability' section, the Windows SKU command is listed before the Linux SKU command. There are no explicit Linux shell or scripting examples, and the automation section does not mention Linux-specific tooling or patterns.

Recommendations:

Alternate the order of Windows and Linux examples (e.g., show Linux commands first in some sections).
Include Bash or shell script examples alongside PowerShell, especially in automation sections.
Explicitly mention Linux as a supported platform in automation and scripting contexts, not just in availability.
Where possible, provide parity in screenshots and UI walkthroughs for both Windows and Linux users.
Clarify that Azure CLI commands are cross-platform and can be run in Bash or other shells, not just in Cloud Shell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring Key Vault references, but consistently lists PowerShell examples immediately after CLI, with no mention of Linux-specific shell commands (e.g., Bash) or Linux-native tools. There are no explicit Linux command-line examples, and the only mention of Linux is in a note about networking configuration, not in practical usage or setup steps. This creates a subtle bias toward Windows and PowerShell users, and may leave Linux users without clear, platform-native guidance.

Recommendations:

Add Bash-specific examples alongside Azure CLI and PowerShell, especially for scripting identity assignment and app configuration.
Explicitly mention that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
Where PowerShell is shown, consider also showing equivalent Bash or shell script snippets for Linux users.
Include troubleshooting steps or tips that are relevant to Linux environments (e.g., checking environment variables, file permissions).
Clarify any platform-specific differences in behavior, especially for Linux-hosted apps, beyond the brief note about Flex Consumption plan networking.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for advanced resource discovery and scenario analysis. While general guidance uses REST API and Azure CLI (which are cross-platform), all provided automation scripts for identifying impacted resources are PowerShell-based, with no Bash, shell, or Linux-native alternatives. The documentation refers to 'open PowerShell' and provides only PowerShell script download/run instructions, implicitly prioritizing Windows environments. There are no explicit Linux or macOS instructions or examples for these tasks.

Recommendations:

Provide equivalent Bash or shell scripts for all PowerShell scripts, or at least mention how Linux/macOS users can achieve the same results.
When referencing downloadable scripts, clarify if they are cross-platform or provide alternatives for non-Windows users.
Instruct users on how to use Azure CLI or REST API for resource discovery tasks where possible, as these are cross-platform.
Avoid phrases like 'Open PowerShell' without also mentioning terminal or shell for Linux/macOS users.
Explicitly state OS compatibility for any scripts or tools, and link to cross-platform documentation where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. Windows-related information and examples are often presented before Linux equivalents. PowerShell scripting is given equal prominence to Azure CLI, but no Linux shell (bash) scripting examples are provided. Portal instructions and screenshots are Windows-centric, and there is no mention of Linux-specific tools or workflows beyond the Azure CLI. The documentation does not provide parity in automation or troubleshooting examples for Linux users.

Recommendations:

Present Linux and Windows information in parallel, or alternate which comes first to avoid a 'windows_first' impression.
Add bash shell scripting examples for automating tasks (e.g., using Azure CLI in bash), not just PowerShell.
Include Linux-specific troubleshooting or deployment guidance where relevant.
Clarify when instructions or screenshots are platform-agnostic or provide Linux-specific alternatives if there are differences.
Where PowerShell is mentioned, explicitly note that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows installation and usage instructions are consistently presented before Linux equivalents, and Windows-specific tools (GUI, MSI installer) are described in detail, while Linux users are limited to CLI and manual installation. Troubleshooting examples use PowerShell commands without Linux alternatives. Some features (like the GUI) are only available on Windows, and this is noted, but Linux parity is not addressed. Linux instructions are present but less detailed and sometimes lack direct equivalents to Windows workflows.

Recommendations:

Present Linux and Windows instructions side-by-side or in parallel tabs, rather than always listing Windows first.
Provide Linux equivalents for all troubleshooting commands (e.g., use 'nc', 'telnet', or 'ss' for connectivity checks instead of only PowerShell).
Expand Linux installation instructions to include common package managers (yum, dnf, zypper) and clarify supported distributions.
Offer a Linux GUI alternative or roadmap, or clarify if/when one will be available.
Ensure all screenshots and examples have Linux counterparts where possible.
Explicitly mention any feature gaps between Windows and Linux, and provide workarounds or alternatives for Linux users.
Include more Linux-centric troubleshooting steps and examples, such as using systemd for service management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by referencing Visual Studio as the primary development tool and omitting explicit instructions or examples for Linux users. While Visual Studio Code is mentioned (which is cross-platform), there are no details about running the sample on Linux, nor are there instructions for using Linux-specific tools or terminal commands beyond 'git clone'. The instructions for building and running the sample assume Visual Studio or Visual Studio Code, but do not clarify how to use the .NET CLI or other Linux-native workflows. There are no PowerShell-specific examples, but the overall guidance is Windows-centric.

Recommendations:

Add explicit instructions for Linux users, such as using the .NET CLI (e.g., 'dotnet build', 'dotnet run') to build and run the sample projects.
Include Linux-specific prerequisites, such as installing the .NET SDK on Ubuntu or other distributions.
Clarify that Visual Studio Code is cross-platform and provide steps for running the sample on Linux and macOS.
Add troubleshooting notes for common Linux issues (e.g., HTTPS development certificates, file permissions, path length limitations).
Ensure all screenshots and UI references are either generic or include Linux/VS Code equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing certificate management steps that link only to Windows-specific instructions, and by omitting Linux or cross-platform alternatives for key tasks such as obtaining and uploading certificates. Additionally, the application code samples and configuration steps are focused on ASP.NET/OWIN (Windows-centric technologies), with no mention of Linux-compatible frameworks or deployment scenarios.

Recommendations:

Provide parallel instructions and links for obtaining and uploading certificates on Linux (e.g., using OpenSSL and Azure CLI/PowerShell cross-platform).
Include examples or references for configuring and running sample applications (such as the header-demo-app and OIDC app) on Linux environments.
When referencing code samples (e.g., ASP.NET/OWIN), mention equivalent approaches for popular Linux-friendly frameworks (such as Node.js, Python Flask/Django, or Java Spring) and link to relevant documentation.
Ensure all referenced documentation (such as 'obtain a certificate' and 'upload the certificate') includes tabs or sections for Linux/macOS, not just Windows.
Explicitly state that the procedures are cross-platform where applicable, and highlight any platform-specific differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio Code and its Azure Functions extension as the primary development environment, and by mentioning the use of the Azure portal, terminal, or command prompt without explicitly referencing Linux or macOS alternatives. There are no explicit Linux-specific instructions or examples, and the workflow assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Explicitly mention that Visual Studio Code and the Azure Functions extension are cross-platform, and provide installation instructions for Linux and macOS.
Include alternative instructions or notes for deploying and running Azure Functions using native Linux/macOS terminals and tools (e.g., bash, zsh), not just 'terminal' or 'command prompt'.
Provide examples of environment variable management and local.settings.json creation for Linux/macOS users, including common CLI commands.
Clarify that the Azure portal is web-based and accessible from any OS, and provide screenshots or notes that are OS-agnostic.
If referencing command-line operations, include both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) equivalents where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, without mentioning or providing alternatives for Linux-based web servers. There are no Linux-specific instructions, examples, or references to common Linux tools or environments. All application setup and testing guidance is centered on Windows technologies, with no parity for Linux users.

Recommendations:

Provide parallel examples for Linux-based web servers (e.g., Apache, Nginx) alongside IIS, including setup and configuration steps.
Reference Linux-compatible application environments and tools where relevant, not just Windows/IIS.
Include troubleshooting tips and configuration guidance for both Windows and Linux back-end applications.
When mentioning IIS, add a note or section for Linux users with equivalent instructions.
Ensure that any sample code, screenshots, or walkthroughs are not exclusively Windows-centric.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal (web UI) for all steps and does not provide any command-line examples. There is no mention of platform-specific tools, but where command-line or scripting could be relevant (e.g., downloading and editing OpenAPI specs, importing APIs), no examples are given for PowerShell, Windows CMD, Bash, or Linux CLI tools. The lack of CLI instructions or examples means that users on Linux or macOS are not provided parity with Windows users, who might expect PowerShell or CMD instructions. The documentation implicitly assumes a GUI-first, Windows-centric workflow by referencing the Azure portal and omitting cross-platform CLI alternatives.

Recommendations:

Add CLI examples for importing APIs using Azure CLI and/or PowerShell, and ensure both Windows and Linux/macOS commands are shown.
Include instructions for downloading and editing OpenAPI specifications using cross-platform tools (e.g., curl, wget, nano, vi, notepad).
Explicitly mention that all steps can be performed on any OS via the Azure portal, but provide parity by showing how to accomplish tasks using CLI tools available on Linux/macOS.
Where screenshots are shown, clarify that the portal is accessible from any OS and consider including CLI output or code snippets for automation scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all steps and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by not mentioning or demonstrating CLI-based workflows (such as Azure CLI or Bash scripting), which are commonly used on Linux and macOS. There are no Linux-specific instructions, nor are cross-platform command-line alternatives provided.

Recommendations:

Add Azure CLI examples for each major step (e.g., app registration, credential provider creation, API configuration), ensuring commands work on Linux, macOS, and Windows.
Explicitly mention that all portal steps can be performed from any OS, but provide CLI alternatives for automation and parity.
Include sample scripts in Bash (and optionally PowerShell) for common tasks, such as registering an app or configuring API Management.
Reference Azure CLI documentation and provide links for users who prefer command-line or automated workflows.
Review all screenshots and instructions to ensure they do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes using the Azure Portal (a web interface) for all operations and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but also no mention of Linux, CLI, or cross-platform automation. The lack of Azure CLI, Bash, or REST API examples means Linux and automation-focused users are underserved. The instructions implicitly assume a GUI-first (and thus often Windows-first) workflow, which can be a subtle form of bias.

Recommendations:

Add equivalent instructions for enabling and managing Defender for APIs using the Azure CLI (az), which is cross-platform and widely used on Linux.
Include REST API examples for onboarding/offboarding APIs to Defender for APIs, allowing for automation and platform independence.
If PowerShell examples are ever added, ensure Bash or CLI equivalents are provided alongside.
Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight and document command-line and automation options for Linux users.
Consider a 'Choose your platform' section at the start, linking to instructions for Portal, CLI, PowerShell, and REST API.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses on assessing .NET web apps for migration to Azure App Service but does not mention or provide examples for Linux-based .NET web apps. The references and linked resources implicitly assume a Windows/IIS/ASP.NET context, with no explicit mention of Linux hosting scenarios or tools relevant to Linux environments.

Recommendations:

Include explicit references to assessing .NET web apps hosted on Linux (e.g., ASP.NET Core on Kestrel/Nginx/Apache).
Provide examples or guidance for both Windows (IIS) and Linux (Kestrel, Nginx, Apache) hosting environments.
Mention any differences or additional considerations when assessing Linux-hosted .NET apps for Azure App Service migration.
Add links to documentation or tools relevant for Linux-based .NET app assessment and migration.
Ensure parity in terminology and examples so that Linux users feel equally supported.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates bias by only providing instructions for enabling DDoS protection using the Azure Portal (a GUI tool most accessible from Windows) and referencing a PowerShell-based guide for enabling DDoS IP Protection. There are no CLI (az cli), Bash, or Linux-native instructions or examples, and the only automation example points to PowerShell, which is primarily a Windows tool.

Recommendations:

Add equivalent instructions for enabling DDoS protection using Azure CLI (az cli) commands, which are cross-platform and commonly used on Linux and macOS.
Provide Bash script examples where automation is discussed, or at least reference Bash/CLI alternatives alongside PowerShell.
When linking to automation guides (such as enabling DDoS IP Protection), include links to both PowerShell and Azure CLI documentation, ensuring Linux users have clear, first-class guidance.
Explicitly mention that the Azure Portal is web-based and cross-platform, but also provide command-line alternatives for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily describes deploying an ARM template using the Azure Portal, and only briefly mentions alternative methods (Azure PowerShell, Azure CLI, REST API) without providing any examples or commands. There are no explicit examples for Linux users (e.g., Bash or CLI commands), and the mention of PowerShell precedes Azure CLI, which is more cross-platform. No Linux-specific tools or terminal instructions are provided.

Recommendations:

Provide explicit Azure CLI (bash) command examples for deploying the ARM template, alongside or before PowerShell examples.
Include step-by-step instructions for deploying the template using the Azure CLI, suitable for Linux/macOS users.
When listing alternative deployment methods, mention Azure CLI before PowerShell to emphasize cross-platform support.
Add examples for reviewing and cleaning up resources using Azure CLI commands, not just via the Azure Portal.
Consider a table or section comparing deployment methods (Portal, CLI, PowerShell, REST) with links or inline examples for each.

Create pull request

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 often presented first or given special emphasis (e.g., in advanced scenarios). There is a notable presence of PowerShell-specific code blocks outside of the tabbed CLI/PowerShell sections, and no mention of Linux-native tools or shell scripting (e.g., Bash). While Azure CLI is cross-platform, the documentation does not explicitly provide Bash or Linux shell examples, and PowerShell is sometimes highlighted as the default scripting interface.

Recommendations:

Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in advanced scenarios.
Where PowerShell examples are given outside of tabbed sections, provide equivalent Bash/Azure CLI examples.
Clarify that Azure CLI commands can be run natively on Linux/macOS and in Bash, not just in Cloud Shell.
Avoid implying that PowerShell is the default or preferred scripting environment for all users.
Consider including Bash script snippets for common scenarios to improve accessibility for Linux users.
Review screenshots and UI instructions to ensure they are not Windows-centric, though this page appears neutral in that regard.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by omitting explicit Linux-specific instructions or examples. All command-line examples use the Azure CLI, which is cross-platform, but there are no references to Linux-specific tools, shell environments, or differences in experience. The only DNS test example uses nslookup, which is available on both platforms, but no mention is made of dig (commonly used on Linux). All portal navigation and screenshots are platform-agnostic, but the absence of Linux- or macOS-specific notes or examples may leave Linux users without tailored guidance.

Recommendations:

Include explicit Linux and macOS command-line examples where relevant, especially for DNS validation (e.g., show both nslookup and dig).
Add notes about cross-platform compatibility for Azure CLI commands, including any differences in installation or usage between Windows, Linux, and macOS.
Where testing connectivity or DNS, provide example commands for both Windows (nslookup, PowerShell) and Linux/macOS (dig, host, nslookup).
If referencing tools or utilities, clarify their availability and installation on different operating systems.
Consider adding a section or callout for Linux/macOS users, highlighting any unique steps or considerations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation contains a subtle Windows bias in the form of a key link to API protection instructions that explicitly uses a Windows-specific tab in its URL (secure-rest-api.md?tabs=windows&pivots=b2c-custom-policy#using-oauth2-bearer). This suggests that Windows instructions are the default or primary guidance, with no mention of Linux or cross-platform alternatives. No PowerShell, Windows-only tools, or CLI examples are present, but the linked documentation may reinforce a Windows-first perspective.

Recommendations:

Ensure that all referenced links (such as to API protection guides) either default to a cross-platform or neutral tab, or explicitly mention both Windows and Linux options.
If the linked documentation provides platform-specific instructions, clarify in this document that equivalent steps are available for Linux/macOS users and provide direct links or notes.
Review all external documentation references for similar platform-specific defaults and adjust to promote parity.
Consider adding a brief note in the prerequisites or relevant sections stating that all steps can be performed on Windows, Linux, or macOS, and link to platform-appropriate instructions where necessary.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧