Scan Details - Linux-first Docs for Azure

240

Pages Scanned

43

Pages Flagged

240

Changed Pages

17.9%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

00:01:03 Scan started

Scan Information

Started At: 2025-08-14 00:01:03

Finished At: In Progress

Status: in_progress

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically WPF (Windows Presentation Foundation) desktop applications, with all code samples and instructions tailored exclusively for Windows environments. There are no Linux or cross-platform equivalents, and Windows-specific libraries and patterns (such as WindowInteropHelper and WPF APIs) are used throughout. No mention is made of how to achieve similar functionality on Linux or with cross-platform desktop frameworks.

Recommendations:

Add equivalent guidance and code samples for cross-platform desktop frameworks (e.g., .NET MAUI, Avalonia, or Electron) that can run on Linux.
Include instructions and examples for configuring authentication in Linux desktop environments, using appropriate libraries and UI patterns.
Clearly indicate in the introduction that the guide is Windows-specific, and provide links or references to cross-platform or Linux-specific documentation if available.
Where possible, use cross-platform APIs or highlight differences between Windows and Linux implementations.
Mention any limitations or alternative approaches for developers targeting Linux or macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell-specific commands for configuring password expiry duration, referencing the Microsoft Graph PowerShell module, and omitting equivalent CLI or scripting examples for Linux/macOS environments. All command-line automation is shown using PowerShell, and there are no Bash, Azure CLI, or cross-platform REST API examples for these tasks. The documentation assumes the use of Windows tools and does not mention or prioritize Linux alternatives.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell commands, especially for updating password policies and interacting with Microsoft Graph.
Explicitly mention that the REST API examples can be used with curl or other cross-platform tools, and provide sample curl commands.
Clarify that the PowerShell module is available on Linux/macOS via PowerShell Core, or provide installation instructions for non-Windows platforms.
Where possible, present cross-platform command-line examples before or alongside PowerShell examples to ensure parity.
Add a section or note addressing Linux/macOS administrators and their tooling options for these tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Windows-specific tools and documentation (such as Schannel and enabling TLS 1.2 in Windows environments) and omitting Linux-specific guidance or examples. There are no Linux or cross-platform instructions for checking or configuring TLS/cipher suites, and the external links and troubleshooting steps are focused on Windows.

Recommendations:

Include Linux-specific instructions or references for configuring TLS 1.2 and cipher suites (e.g., using OpenSSL, Apache/Nginx configuration).
Add examples or links for verifying TLS/cipher suites on Linux, such as using the openssl s_client command.
Balance the 'Next steps' section with Linux and cross-platform resources, not just Windows-focused articles.
Mention both Windows and Linux tools when suggesting how to test endpoint compatibility, such as testssl.sh or OpenSSL for Linux.
Ensure that troubleshooting steps and further reading cover both Windows and Linux environments equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All administrative steps for configuring AD FS are described using Windows-specific tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no equivalent instructions or references for performing these tasks on Linux or cross-platform environments, nor are there any mentions of AD FS alternatives or SAML providers that run on Linux. Troubleshooting and log access are also described solely in terms of Windows event logs.

Recommendations:

Provide equivalent instructions for configuring SAML identity providers using cross-platform or Linux-based SAML solutions (e.g., Shibboleth, SimpleSAMLphp, or Keycloak).
Include examples of how to generate and manage certificates using Linux tools (e.g., OpenSSL) in addition to or instead of Windows tools.
Offer troubleshooting guidance for SAML integration that is not specific to Windows/AD FS, such as how to access logs or debug SAML assertions on Linux-based identity providers.
Clearly indicate that the instructions are specific to AD FS/Windows, and provide links or references to documentation for integrating with SAML providers on other platforms.
Where PowerShell is used, provide equivalent command-line or script examples for Linux environments if possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for running the sample application, and by providing instructions and workflows that assume a Windows environment. There are no examples or guidance for Linux users, such as using cross-platform .NET CLI tools or alternative editors like VS Code. The documentation omits Linux-specific instructions for running or debugging the ASP.NET application.

Recommendations:

Add instructions for running the sample application using the .NET CLI (dotnet run), which works on Linux, macOS, and Windows.
Include examples for setting up and debugging the application in Visual Studio Code, a cross-platform editor.
Mention any prerequisites for Linux users, such as installing the .NET SDK and required dependencies.
Provide equivalent steps for Linux/macOS environments, such as using terminal commands instead of Visual Studio UI actions.
Clarify that Visual Studio is optional and that the sample can be run on any platform supported by .NET.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell script example for programmatically accessing Azure AD B2C audit logs, with no equivalent Linux/bash/cURL example. The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) reinforce a Windows-centric approach. There is no mention of Linux-native tools or cross-platform scripting options, and the scripting section is labeled as 'PowerShell script' without alternatives.

Recommendations:

Add a bash/cURL example for querying the Microsoft Graph API for audit logs, including authentication and pagination.
Explicitly mention that the API can be accessed from any platform and provide cross-platform code samples.
Reference Linux tools (such as jq, curl, wget) alongside PowerShell, and clarify that the process is not limited to Windows environments.
Reorganize the scripting section to present both PowerShell and bash/cURL examples, or provide a language selector for users to choose their preferred scripting environment.
Update language to avoid implying PowerShell is the only or primary method for automation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page is heavily oriented toward Visual Studio Code and Azure tools, which are cross-platform, but it implicitly assumes a Windows environment by referencing Microsoft-specific identity systems (Microsoft Entra ID, Azure RBAC), and only provides instructions and screenshots for Visual Studio Code without clarifying Linux/Mac parity. There are no explicit Linux (or Mac) command-line examples, nor is there mention of platform-specific differences or requirements. The use of keyboard shortcuts (Ctrl+Shift+P) and references to the Azure portal may be more familiar to Windows users. There is no mention of Linux-specific installation steps, troubleshooting, or alternative tools.

Recommendations:

Explicitly state that Visual Studio Code and the Azure API Center extension are supported on Windows, Linux, and Mac, and provide links to platform-specific installation instructions.
Include screenshots or notes indicating that the UI and steps are the same (or different) on Linux/Mac.
Mention any platform-specific prerequisites or troubleshooting steps, such as authentication issues or extension compatibility on Linux.
Provide alternative keyboard shortcuts for Mac (e.g., Cmd+Shift+P) where appropriate.
If any steps require use of the Azure CLI or PowerShell, provide equivalent commands for Bash/Linux environments.
Clarify that Microsoft Entra ID and Azure RBAC are cloud-based and not tied to a specific OS, to reduce the impression of Windows-centricity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation lists Azure PowerShell alongside Azure CLI as tools for reviewing deployed resources, but mentions Azure PowerShell before Azure CLI, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific examples or references, and the documentation does not provide command-line examples for either platform, missing an opportunity to demonstrate parity.

Recommendations:

List Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
Provide explicit command-line examples for both Azure CLI and Azure PowerShell, showing equivalent commands.
Mention that Azure CLI is available on Windows, Linux, and macOS, emphasizing its cross-platform nature.
If referencing PowerShell, clarify that PowerShell Core is also available cross-platform, or provide Bash examples where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Azure Portal (web UI) and Microsoft-first tools (Logic Apps, Microsoft Teams, Power Automate), with no mention of Linux-native or cross-platform alternatives. All examples and instructions are given using the Azure Portal and Microsoft ecosystem tools, with no CLI, REST API, or scripting examples that would be more platform-agnostic. There is no mention of Linux, Bash, or open-source notification/collaboration tools, and all automation is described in terms of Microsoft products.

Recommendations:

Provide equivalent instructions using Azure CLI and/or Azure PowerShell, and ensure CLI examples are cross-platform (Bash and PowerShell).
Include REST API examples for automation steps, allowing users to script workflows on any OS.
Mention and, where possible, provide examples for integrating with open-source or cross-platform notification tools (e.g., Slack, Mattermost) in addition to Microsoft Teams.
Clarify that Logic Apps and Power Automate are web-based and can be used from any OS, but also provide guidance for users who prefer to automate via code or scripts.
Add a section or callout for Linux users, highlighting any differences or additional steps required.
Reference documentation for using Azure Event Grid and Logic Apps via CLI or REST, not just the Portal.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (Git Bash from Git for Windows, Visual Studio Immediate Window) and providing troubleshooting steps that assume access to Visual Studio, a Windows-centric IDE. There are no Linux or macOS-specific instructions or examples for cloning the repository, handling credentials, or URL encoding passwords. The order of tool mentions and examples also places Windows tools and workflows first, with no parity for Linux users.

Recommendations:

Provide explicit Linux and macOS examples for cloning the repository, including credential handling and URL encoding (e.g., using `python3 -c 'import urllib.parse; print(urllib.parse.quote("password"))'` or `printf %s "password" | jq -sRr @uri`).
Mention cross-platform Git tools (e.g., native Git on Linux/macOS, or terminal usage) alongside or before Windows-specific ones.
Replace or supplement Visual Studio Immediate Window instructions with cross-platform alternatives for URL encoding passwords.
Add a note clarifying that all Git operations can be performed on Linux/macOS as well as Windows, and provide any OS-specific caveats if needed.
Ensure that references to Azure CLI and PowerShell are balanced, and provide example commands for both where relevant.

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 tooling. The only command-line example is Windows-centric, and there is no guidance for Linux or cross-platform users.

Recommendations:

Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
If PowerShell is mentioned, also provide Bash or shell script equivalents for Linux users.
Explicitly state whether the process can be performed from Linux/macOS, and provide any relevant platform-specific notes.
Reference or link to documentation on using REST APIs with curl or other Linux-native tools for certificate management.
Ensure that screenshots and instructions do not assume a Windows environment unless unavoidable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses Azure PowerShell for all setup, configuration, and management steps, with all code samples and variable paths (e.g., certificate paths) reflecting Windows conventions. There are no examples or guidance for performing the same tasks using cross-platform tools such as Azure CLI, Bicep, or ARM templates, nor are there any Linux/macOS-specific instructions or file path conventions. This creates a strong Windows and PowerShell bias, making it less accessible for users on Linux or macOS systems.

Recommendations:

Provide equivalent Azure CLI examples for all major steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include notes or examples for Linux/macOS users, especially regarding file paths (e.g., use /home/contoso/ instead of C:\Users\Contoso\).
Reference and link to ARM/Bicep template-based deployments for users who prefer declarative infrastructure-as-code approaches.
Explicitly state that all steps can be performed on Linux/macOS with Azure CLI, and highlight any differences or prerequisites.
Where PowerShell is required, clarify if Azure PowerShell Core (cross-platform) is supported, and provide installation instructions for non-Windows systems.
Add a section or callout summarizing cross-platform options for managing Azure resources, with links to relevant documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page provides code examples for configuring loggers using Azure PowerShell, Bicep, ARM templates, and REST API, but only the PowerShell example is given for command-line/scripted creation of loggers. There are no CLI (az cli), Bash, or Linux-native examples. The only imperative scripting example is PowerShell, which is primarily a Windows tool, and there is no mention of cross-platform alternatives such as Azure CLI or Bash scripts. This may make it less accessible for Linux or macOS users.

Recommendations:

Add Azure CLI (az cli) examples for creating and managing loggers, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script examples where appropriate, especially for tasks that can be automated via the command line.
When referencing scripting tools, mention cross-platform options (e.g., 'You can use Azure PowerShell or Azure CLI...') and provide parity in examples.
Explicitly state that PowerShell Core is available cross-platform if PowerShell examples are retained, or clarify which examples are Windows-only.
Consider the order of examples: present cross-platform tools (like Azure CLI) before or alongside Windows-centric tools (like PowerShell).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell cmdlet examples (e.g., New-AzApiManagementBackend), with no equivalent CLI or scripting examples for Linux environments. There is no mention of cross-platform tools such as Azure CLI or Bash scripts, and the only automation guidance is via PowerShell, which is primarily a Windows tool. This could hinder Linux or macOS users seeking parity.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlet instructions, especially for tasks like disabling certificate chain validation.
Include Bash script snippets or REST API curl examples to demonstrate cross-platform automation.
Explicitly mention that PowerShell Core is available cross-platform, or provide links to documentation for using PowerShell on Linux/macOS if PowerShell must be used.
Ensure that references to automation tools (e.g., 'You can also disable certificate chain validation by using the Backend REST API') are accompanied by concrete, cross-platform code samples.
Review all sections for implicit assumptions of a Windows environment and add clarifying notes or alternatives where needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for command-line operations, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or REST API. No Linux shell or cross-platform command-line examples are given, and the only automation tooling mentioned is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Add equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include REST API examples for operations such as setting a revision as current or updating the change log, to provide a platform-neutral automation option.
When referencing command-line tools, mention Azure CLI before or alongside PowerShell to avoid implying Windows is the primary or only supported environment.
Explicitly state that all operations can be performed from any OS using the Azure portal, Azure CLI, or REST API, and provide links or examples for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, and by not providing any Linux- or cross-platform-specific examples or guidance. The mention of Azure PowerShell before Azure CLI and the absence of explicit Linux command-line or automation examples suggest a preference for Windows-centric tools and workflows.

Recommendations:

Ensure that Azure CLI (which is cross-platform) is mentioned before or alongside Azure PowerShell in all tool lists and instructions.
Provide explicit Linux shell (bash) examples for API management tasks, especially where PowerShell is referenced.
Include notes or sections clarifying that all management operations can be performed from Linux, macOS, and Windows, and link to relevant cross-platform documentation.
Where screenshots or UI elements are shown, ensure they are not Windows-specific, or provide Linux/macOS equivalents if relevant.
Audit related documentation for similar patterns and update to maintain parity between Windows and Linux user experiences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for generating OAuth tokens and calling APIs, with no equivalent examples for Linux or cross-platform tools such as curl or Bash. The only command-line automation shown is via PowerShell, and there are no references to Linux-native tools or instructions for non-Windows environments. The use of the Azure portal is platform-agnostic, but all scripting and automation guidance assumes a Windows/PowerShell context.

Recommendations:

Provide equivalent examples using curl and Bash for generating tokens and calling APIs, which are native to Linux and cross-platform environments.
Explicitly mention that the API calls can be performed from any OS, and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash/curl).
Add a note or section on how to install and use Azure CLI (which is cross-platform) for relevant operations, if applicable.
Ensure troubleshooting and automation guidance includes steps or scripts that are not limited to Windows or PowerShell users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Windows PowerShell cmdlets and scripts for managing Azure API Management via Azure Automation. There are no examples or mentions of Linux-compatible tools (such as Azure CLI, Bash, or Python), nor are cross-platform scripting options discussed. The guidance assumes a Windows/PowerShell environment, which may exclude or disadvantage Linux users.

Recommendations:

Provide equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include Bash or Python script samples for common automation tasks.
Mention that Azure Automation supports Python runbooks and provide links or examples.
Rephrase sections to refer to 'PowerShell or other supported scripting languages' rather than only PowerShell.
Ensure that links and samples are balanced, offering both Windows/PowerShell and Linux-friendly options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation gives both Azure CLI and Azure PowerShell instructions for checking and updating tool versions, but the PowerShell example is presented alongside the CLI without explicit Linux/bash alternatives. PowerShell is a Windows-centric tool, and its mention without equivalent bash or shell commands may disadvantage Linux users. Additionally, the documentation references the Azure portal (a web UI) and REST API, but does not provide explicit Linux shell or bash script examples, nor does it clarify cross-platform usage for the CLI commands. The focus on PowerShell and lack of explicit Linux-native instructions indicate a mild Windows bias.

Recommendations:

For every PowerShell example, provide an equivalent bash or shell command for Linux/macOS users.
Clarify that Azure CLI commands are cross-platform and can be run in bash, zsh, or other shells, not just Windows Command Prompt or PowerShell.
Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide installation/update links for all platforms.
Where possible, provide sample scripts or commands in both PowerShell and bash to ensure parity.
Add a note or section addressing Linux/macOS users, highlighting any differences or considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell (and AzureAD module) instructions for provisioning the service principal, with no equivalent CLI or Bash/Linux instructions. The use of PowerShell is assumed, and there are no references to cross-platform tools such as Azure CLI or REST API alternatives. This may disadvantage users on Linux or macOS, or those who prefer not to use PowerShell.

Recommendations:

Provide equivalent instructions using Azure CLI (az) for all PowerShell commands, especially for provisioning the service principal.
Explicitly mention that the steps can be performed on any OS, and provide Bash or shell examples where possible.
Reference REST API alternatives for automation, with example curl commands.
Reorganize sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
Add a note clarifying that PowerShell is not required, and link to cross-platform setup guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure tools and services (such as Azure CLI, Azure Function App, Azure CDN) without mentioning or providing examples for equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions, and the use of Azure CLI and Azure Functions Core Tools assumes a Windows/Azure environment. No mention is made of non-Azure hosting, deployment, or CDN options, nor are there examples for Linux-native workflows.

Recommendations:

Include explicit instructions and examples for Linux environments, such as using bash scripts, Linux-native CLI tools, and deployment to non-Azure hosts.
Mention and provide examples for alternative hosting and CDN solutions (e.g., AWS S3, Google Cloud Storage, Cloudflare CDN, Nginx, Apache) alongside Azure-specific options.
Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux and macOS.
Add a section or notes highlighting how to adapt the workflow for Linux users, including common pitfalls and environment-specific considerations.
Balance the order of presentation so that Azure/Windows tools are not always mentioned first, or group alternatives together to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only the Azure PowerShell cmdlet (New-AzApiManagementUser) as the CLI-based alternative to the Azure portal for adding users. There are no examples or mentions of equivalent Linux-friendly tools such as Azure CLI, nor are there bash or cross-platform command examples. The documentation assumes familiarity with PowerShell, which is more common on Windows, and omits Linux-native workflows.

Recommendations:

Add equivalent Azure CLI commands (az apim user create) alongside PowerShell examples to provide parity for Linux and macOS users.
When referencing command-line tools, mention both PowerShell and Azure CLI, and provide examples for each.
Include bash shell examples where relevant, or clarify that the steps are cross-platform.
Avoid assuming the use of Windows-specific tools or shells; ensure all steps can be followed on Linux, macOS, and Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias, particularly in the permissions section, where only PowerShell scripts (using the Az module) are provided for role creation and assignment. There are no equivalent examples for Linux/macOS users (e.g., Bash/Azure CLI), and the use of .bat scripts is mentioned for cleanup tasks. Windows tools and patterns are referenced exclusively or before any cross-platform alternatives.

Recommendations:

Provide equivalent Azure CLI (az) commands for role creation and assignment, suitable for Linux/macOS and cross-platform users.
When referencing scripts (such as cleanup.bat), also provide Bash (.sh) alternatives or clarify if the script is compatible with Bash (e.g., via WSL or native Bash).
Avoid assuming the use of PowerShell or Windows-specific tools; where possible, present cross-platform instructions first or in parallel.
Explicitly mention platform compatibility for scripts and commands, and link to cross-platform tool documentation.
Encourage contributions of Linux/macOS examples if not available, and consider marking sections as 'Windows only' where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples, but the structure and emphasis show a Windows bias. PowerShell is given a dedicated section, and the prerequisites list Azure PowerShell as a primary tool alongside Azure CLI. There is no mention of Linux-specific shell usage, nor are there Bash or cross-platform shell examples. The CLI example is generic, but the PowerShell example is more detailed and uses Windows-centric tooling and patterns.

Recommendations:

Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide Bash/zsh example snippets where appropriate.
Clarify that Azure PowerShell is available on all platforms, but also provide Bash or Linux-native shell examples for parity.
In the prerequisites, note that Azure CLI is the recommended tool for Linux/macOS users, and provide links or notes about installing and using it on those platforms.
If showing both CLI and PowerShell, consider presenting CLI (cross-platform) examples first, or side-by-side, to avoid a Windows-first impression.
Add troubleshooting or environment setup notes for Linux users, especially for common issues or differences in file paths, permissions, or shell syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET (a Microsoft-centric, Windows-originated framework) and by providing package installation instructions that reference Visual Studio and Visual Studio Code, both of which are more commonly associated with Windows development. There are no explicit Linux or cross-platform shell instructions, and no mention of Linux-specific development environments or considerations. All command-line examples use the dotnet CLI, which is cross-platform, but the context and tooling references are Windows-centric. No Linux-specific guidance or troubleshooting is provided.

Recommendations:

Explicitly mention that the dotnet CLI commands work on Linux, macOS, and Windows, and provide example terminal commands for Bash/zsh where appropriate.
Include instructions for installing the .NET SDK on Linux (e.g., using apt, yum, or snap), or link to official cross-platform installation guides.
When referencing IDEs, mention cross-platform options (e.g., JetBrains Rider, VS Code on Linux/macOS) and provide parity in instructions.
Add a note or section on running and testing the ASP.NET Core app on Linux (e.g., using 'dotnet run' in a Bash shell), including any OS-specific caveats.
Avoid using only Visual Studio/Visual Studio Code tabs; add a 'Command Line (Bash)' or 'Linux/macOS' tab for relevant steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently presents Bash first and then PowerShell. There is a note clarifying that examples can run in either shell and that separate examples are provided where variable syntax differs. No Windows-specific tools or patterns are exclusively mentioned, and there are no missing Linux examples. However, the explicit labeling of 'Formatted for PowerShell' and the inclusion of PowerShell-specific syntax throughout the page indicate a strong focus on Windows parity, possibly even a slight Windows-first bias due to the explicit PowerShell formatting, though Bash is always listed first.

Recommendations:

Continue to provide both Bash and PowerShell examples, but clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right syntax.
Consider adding a short section or table at the top summarizing which shell to use on which platform (e.g., Bash for Linux/macOS, PowerShell for Windows), to make it clearer for cross-platform users.
If possible, provide a toggle or tabbed interface in the documentation to let users select their preferred shell (Bash or PowerShell), reducing visual clutter and making parity more obvious.
Ensure that any references to file paths, environment variables, or shell-specific behaviors are clearly explained for both platforms.
Maintain the order of examples (Bash first, then PowerShell) or alternate the order in different sections to avoid any perception of platform preference.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are explicitly labeled and formatted, potentially giving them prominence. Additionally, PowerShell examples are included immediately after Bash, which can be interpreted as a subtle 'windows_first' bias. However, Linux (Bash) examples are present and correct, and no Windows-only tools are used.

Recommendations:

Clearly label both Bash and PowerShell examples with headings such as 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make platform targeting explicit.
Present Bash and PowerShell examples in parallel tabs or side-by-side, rather than sequentially, to avoid implying priority.
Ensure that introductory text does not imply that PowerShell is the default or preferred shell.
Consider including a brief note about cross-platform compatibility of Azure CLI and how users can select the appropriate shell for their OS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. There is a slight bias toward Windows/PowerShell by explicitly formatting and labeling PowerShell commands, while not providing equivalent detail for other shells (e.g., zsh, fish) or Linux-specific environments. The documentation does not mention Linux or macOS explicitly, nor does it provide troubleshooting or environment-specific notes for non-Windows users.

Recommendations:

Clearly label Bash examples as 'Linux/macOS (Bash)' and PowerShell examples as 'Windows (PowerShell)' to make platform targeting explicit.
Consider providing a short note at the beginning of the CLI section explaining that Bash examples are for Linux/macOS and PowerShell for Windows, and that Azure CLI works cross-platform.
If possible, provide parity in detail for both environments, such as mentioning common shell differences or potential issues on Linux/macOS.
Add troubleshooting tips or links for users running Azure CLI on Linux/macOS, especially if there are known differences.
Consider including a table or tabbed interface for 'Linux/macOS (Bash)', 'Windows (PowerShell)', and possibly 'Windows (CMD)' if relevant, to make it clear which commands apply to which environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively provides instructions using the Azure portal GUI, which is a web-based interface commonly associated with Windows-centric workflows. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-native tools or workflows. This can be seen as a subtle Windows bias, as Linux users often prefer or require CLI-based instructions.

Recommendations:

Add equivalent Azure CLI examples for enabling managed identities and assigning roles, as the CLI is cross-platform and widely used on Linux.
Explicitly mention that the Azure portal is web-based and platform-agnostic, but provide alternative instructions for users who prefer command-line tools.
Where possible, include both GUI and CLI instructions side by side, ensuring parity for Linux and Windows users.
Reference documentation for both PowerShell and Azure CLI where relevant, making it clear that both are supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Visual Studio Code and its Azure API Center extension as prerequisites, which are cross-platform tools. However, there is a subtle bias in that only Visual Studio Code (and its extension) is mentioned as the tool for interacting with Azure API Center, with no mention of alternative editors or CLI tools commonly used on Linux. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility or provide Linux-centric guidance.

Recommendations:

Explicitly state that Visual Studio Code and the Azure API Center extension are available on Windows, Linux, and macOS.
Mention and provide links to alternative tools or CLI options (if available) for managing API centers, especially those commonly used on Linux.
Include a note or section on installing and using the Azure API Center extension on Linux distributions.
If Visual Studio Code is the only supported tool, clarify its cross-platform nature to avoid the impression of Windows preference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is given equal prominence to CLI, and there is no explicit mention of Linux or Bash-specific considerations. The structure and language (e.g., 'your local computer', use of PowerShell) may implicitly favor Windows users, as PowerShell is primarily a Windows tool (though available on Linux). There are no Linux- or Bash-specific examples or troubleshooting notes.

Recommendations:

Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux) and can be run in Bash or other shells.
Add a Bash-specific example or clarify that the CLI example is intended for Bash/Unix shells.
Include a note that PowerShell is available on Linux, but Bash is the default shell on most Linux distributions.
If relevant, provide troubleshooting tips or environment setup notes for Linux users.
Consider listing the CLI (Bash) example first, as it is more universally applicable across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file, but PowerShell is given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there any explicit Linux or cross-platform command-line considerations. The prerequisites section references Azure PowerShell requirements, which may reinforce a Windows-oriented workflow.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend it as the default for cross-platform users.
Add Bash-specific instructions or notes for Linux/macOS users, such as how to install Azure CLI on Linux.
Clarify that PowerShell Core is available on Linux/macOS, if PowerShell examples are to be retained, and provide installation guidance.
Consider listing Azure CLI (Bash) examples before PowerShell to reduce perceived Windows-first bias.
Add a note or section on running these commands in the Azure Cloud Shell, which is cross-platform and browser-based.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides instructions and code samples that are platform-neutral in most areas, but all interactive steps reference the Azure portal (web-based) and .NET/C# SDKs for API calls, which are most commonly used on Windows. There are no Linux-specific command-line examples (e.g., Bash, curl, or Python), and no mention of Linux tools or shell environments. The only SDK example is in C#, with no parity for Linux-preferred languages or tools. This may make the documentation less accessible for Linux users.

Recommendations:

Add equivalent examples using Linux-friendly tools such as curl or httpie for making API calls.
Provide code samples in cross-platform languages commonly used on Linux, such as Python (using boto3 or requests), in addition to .NET/C#.
Explicitly mention that the Azure portal is web-based and accessible from any OS, to clarify platform neutrality.
If referencing SDKs, include installation and usage instructions for both Windows and Linux environments.
Where possible, provide shell command examples (e.g., Bash scripts) for steps like storing secrets or calling APIs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell examples are given first and in greatest detail, with variable setup and multiple authentication scenarios. While Azure CLI (Bash) and REST examples are provided, the PowerShell (Windows) approach is consistently presented before cross-platform alternatives, and the CLI examples are less detailed. There are no explicit Linux-only or platform-specific tools, but the prominence and ordering of PowerShell content may signal a preference for Windows environments.

Recommendations:

Alternate the order of PowerShell and CLI examples, or present CLI (Bash) examples first to balance platform representation.
Expand CLI (Bash) examples to include all authentication scenarios shown in PowerShell (e.g., managed identities).
Explicitly state that both PowerShell and CLI examples are cross-platform, and clarify that Azure CLI works natively on Linux and macOS.
Where possible, provide example scripts for both Windows (PowerShell) and Linux/macOS (Bash) in parallel, especially for variable setup and automation.
Add a note or section highlighting platform neutrality and cross-platform support for all tools used.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references the Azure portal (a web-based GUI) and Microsoft Entra ID for OAuth 2.0 provider configuration, without mentioning or providing examples for command-line or cross-platform tools (such as Azure CLI, Bash scripts, or Linux-based workflows). There are no references to Linux-specific tools or environments, and all step-by-step instructions assume use of the Azure portal, which is most commonly accessed from Windows environments. No PowerShell or Windows command-line examples are present, but the lack of Linux/CLI parity is notable.

Recommendations:

Provide equivalent instructions using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
Include examples of registering applications and configuring OAuth 2.0 using Bash scripts or REST API calls, not just through the Azure portal.
Mention that the Azure portal is web-based and accessible from any OS, but explicitly state that all steps can be performed from Linux or macOS as well.
Reference or link to documentation for Linux users on installing and using Azure CLI and other relevant tools.
If possible, add a section or callout for Linux/macOS users to clarify any OS-specific considerations or alternative workflows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools or provide CLI (az CLI) examples. There are no code or command-line examples at all, but the only automation tool specifically named is Azure PowerShell, which is Windows-centric. This may give the impression that Windows tools are preferred or required, and Linux users are not directly supported.

Recommendations:

When mentioning automation tools, explicitly include cross-platform options such as Azure CLI (az), which runs natively on Linux, macOS, and Windows.
Provide example commands for both Azure PowerShell and Azure CLI when discussing automation or scripting tasks.
Avoid mentioning only Windows-centric tools (like PowerShell) without also referencing their Linux-friendly equivalents.
Consider adding bash or shell script examples for common automation scenarios, or link to documentation that demonstrates Linux-compatible workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes procedures using the Azure portal GUI, with no mention of command-line tools or scripts. Where command-line or automation might be relevant (e.g., downloading and editing OpenAPI specs, importing APIs), no examples are provided for either Windows (PowerShell) or Linux (bash/CLI). However, the only implicit platform-specific references are to the Azure portal, which is platform-agnostic but often more familiar to Windows users. There is no mention of Linux tools, CLI commands, or cross-platform automation, and no guidance for users who prefer or require non-GUI workflows.

Recommendations:

Add Azure CLI and/or Azure PowerShell examples for importing APIs, downloading OpenAPI specs, and configuring authentication, ensuring both Windows and Linux command-line users are supported.
Provide bash shell script examples for Linux users where relevant (e.g., using curl or wget to download OpenAPI specs, jq for editing JSON).
Explicitly mention that all steps can be performed on any OS via the Azure portal, but offer parity by including at least one example for both CLI and GUI workflows.
Where screenshots or instructions reference file paths or editors, include both Windows and Linux conventions.
Consider a section on automation or scripting for advanced users, with cross-platform examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on using the Azure portal and Power Platform web interfaces, which are platform-agnostic, but it implicitly assumes a Windows-centric workflow by only referencing Power Platform and Azure tools, which are most commonly used in Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), but also no mention of Linux-specific tools or workflows. There is a lack of parity for Linux users who may prefer or require CLI-based instructions.

Recommendations:

Add examples using Azure CLI for configuring CORS policies, which is cross-platform and widely used on Linux.
Explicitly mention that all steps can be performed from any OS with a supported web browser, to reassure non-Windows users.
If PowerShell or Windows-specific tools are referenced in other related articles, ensure equivalent Bash or Azure CLI examples are provided.
Include a note or section for users who prefer automation or scripting, with links to relevant cross-platform tools.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses on using the Azure portal and .NET for gRPC API import and consumption, with no mention of Linux-specific tools, command-line instructions, or cross-platform alternatives. The only client example references .NET, which is typically associated with Windows, and there are no examples for Linux environments or other languages. There is also an absence of CLI, PowerShell, or Bash examples, but the lack of any Linux or cross-platform guidance results in a Windows-first impression.

Recommendations:

Include examples for importing gRPC APIs using Azure CLI or Bash scripts to provide parity for Linux users.
Add references or links to gRPC client usage in other languages (e.g., Python, Go, Java) and on Linux systems.
Explicitly mention that the steps are platform-agnostic if that is the case, or provide separate instructions for Windows and Linux where differences exist.
Provide guidance for managing and deploying .proto files and gRPC services from Linux environments.
If .NET is used as an example, balance it with examples for other popular cross-platform frameworks.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display explicit Windows bias in terms of command-line examples or tool references, as it focuses on Azure portal steps and XML policy snippets. However, there is a lack of parity for Linux users: no CLI (Azure CLI, Bash, or cross-platform scripting) examples are provided, and all instructions are GUI-based or use XML policies, which may implicitly favor users familiar with Windows-centric Azure workflows.

Recommendations:

Add Azure CLI and/or Bash examples for key steps, such as creating named values, configuring managed identities, and setting policies.
Include cross-platform command-line instructions alongside portal-based steps to ensure Linux and macOS users can follow along without relying on the Azure portal.
Explicitly mention that all steps can be performed using the Azure CLI or ARM templates, and provide links or snippets where appropriate.
Review for any implicit assumptions about the user's operating system and clarify that the instructions are OS-agnostic where possible.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform language, but in the section on editing the hosts file for DNS testing, the Windows path is listed before the Linux/macOS equivalent. No command-line examples (PowerShell, Bash, etc.) are present, and no Windows-specific tools or patterns are emphasized elsewhere. However, the ordering of Windows before Linux in the hosts file path is a subtle form of 'windows_first' bias.

Recommendations:

List Linux/macOS and Windows hosts file paths in parallel or alternate the order to avoid implying priority.
Where possible, provide explicit examples for both Windows and Linux/macOS users, especially for common administrative tasks.
If command-line instructions are added in the future, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are included.
Review related links and references to ensure they are not disproportionately focused on Windows-only documentation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page generally uses cross-platform tools (Git, Node.js, Azure CLI) and avoids OS-specific commands. However, in Step 6, it explicitly mentions 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not mentioning Linux or macOS terminals by name. No Linux/macOS-specific examples or shell references are provided, which may make Linux users feel like an afterthought.

Recommendations:

Explicitly mention Linux and macOS terminals alongside Windows shells in instructions (e.g., 'Open your terminal (such as Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)').
Where possible, provide examples or notes for common Linux/macOS environments, especially if there are differences in command syntax or prerequisites.
Review for any subtle language that centers Windows as the default, and adjust to be more platform-neutral.
Consider adding a short section or note confirming that all commands work cross-platform, or call out any OS-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists Windows-centric tools (Azure PowerShell, Azure portal) before Linux/CLI options when describing how to create an Azure Kubernetes cluster. However, the main deployment steps and examples use cross-platform tools (kubectl, YAML), and there are no PowerShell-specific commands or Windows-only tools in the core workflow.

Recommendations:

List cross-platform or Linux-native tools (such as Azure CLI) before Windows-specific tools (Azure PowerShell, Azure portal) in prerequisite sections.
Explicitly mention that all deployment steps and commands (kubectl, YAML) are cross-platform and can be run from Linux, macOS, or Windows.
If possible, provide links or notes for Linux/macOS users on installing and using Azure CLI and kubectl.
Ensure future documentation avoids ordering that implies Windows is the primary or preferred platform.

Create pull request

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