Scan Details - Linux-first Docs for Azure

227

Pages Scanned

23

Pages Flagged

227

Changed Pages

10.1%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

21:17:21 Scan started

Scan Information

Started At: 2025-07-13 21:17:21

Finished At: In Progress

Status: cancelled

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily uses generic command shell instructions for most steps, but in the final 'Run your SPA application' section, it provides a PowerShell-specific command example (npm ./index.js), which is not valid on Linux/macOS shells. There are no explicit Linux/macOS instructions or clarifications, and no mention of platform differences, leading to a subtle Windows/PowerShell bias.

Recommendations:

Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples, especially for running Node.js applications (e.g., 'node index.js' instead of 'npm ./index.js').
Clarify that the instructions are cross-platform and specify any platform-specific differences where relevant.
Avoid using PowerShell-specific syntax unless necessary, or always accompany it with the equivalent bash command.
Explicitly mention that the steps work on Windows, Linux, and macOS, and provide troubleshooting tips for each platform if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on WPF, a Windows-only technology, and all code samples are in C# using Windows-specific APIs (e.g., WindowInteropHelper). There are no examples or mentions of Linux or cross-platform desktop application frameworks, nor any guidance for developers targeting non-Windows environments. The documentation assumes a Windows development environment and does not provide parity for Linux users.

Recommendations:

Add equivalent guidance and code samples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
Include instructions and examples for configuring authentication in Linux desktop applications using Azure AD B2C.
Clarify in the introduction that the guidance is specific to WPF/Windows, and provide links or references to cross-platform alternatives.
If possible, provide MSAL usage examples in a cross-platform context (e.g., .NET Core/MAUI) that work on Linux.
Mention any platform-specific limitations or requirements explicitly, and suggest alternatives for non-Windows developers.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (Server Manager, AD FS Management), providing only GUI-based instructions for AD FS configuration, and omitting any Linux-based or cross-platform alternatives. There are no PowerShell or command-line examples, but all setup steps assume a Windows Server environment with AD FS, and no mention is made of how to achieve similar outcomes on Linux or with non-Windows identity providers. The documentation also introduces Windows-specific concepts and tools before any platform-agnostic configuration steps.

Recommendations:

Add command-line (PowerShell and, if possible, cross-platform CLI) instructions for AD FS configuration to supplement or replace GUI steps.
Explicitly state that AD FS is a Windows Server feature, and provide guidance or links for integrating with non-Windows OpenID Connect providers (e.g., Keycloak, IdentityServer, or cloud-based IdPs) for Linux users.
Where possible, generalize the instructions to apply to any OpenID Connect provider, and provide a parallel example using a popular Linux-compatible IdP.
Include a section or note for Linux administrators explaining the lack of AD FS support on Linux and suggesting alternatives for similar integration.
Reorder or supplement examples so that platform-agnostic or Linux-friendly options are presented alongside or before Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias: all administrative steps for configuring AD FS are described using Windows-only tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux or cross-platform alternatives or notes, and Windows-specific patterns are always presented first and exclusively. Troubleshooting and configuration guidance assumes a Windows environment throughout.

Recommendations:

Explicitly note that AD FS is a Windows Server technology and clarify platform requirements early in the documentation.
Where possible, provide equivalent SAML identity provider configuration steps for common Linux-based SAML providers (e.g., Shibboleth, SimpleSAMLphp) or link to relevant guides.
For certificate creation and management, include Linux/OpenSSL command-line examples alongside any Windows-specific instructions.
For troubleshooting, suggest generic SAML troubleshooting tools (such as SAML-tracer browser extension, or logs from Linux SAML IdPs) in addition to Windows Event Viewer.
If PowerShell is required, clarify that these steps are only for AD FS on Windows, and suggest alternative approaches for non-Windows environments where feasible.
Consider adding a section or links for users who wish to integrate with non-Windows SAML providers, outlining the differences and additional considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the section on revoking a consumer user's session. It exclusively provides instructions and examples for using Microsoft Graph PowerShell in 'Windows PowerShell', without mentioning cross-platform alternatives or providing equivalent Linux/macOS command-line guidance. The use of 'Windows PowerShell' and lack of Bash/CLI/Cloud Shell examples may hinder Linux and macOS users.

Recommendations:

Clarify that Microsoft Graph PowerShell is cross-platform and can be used in PowerShell Core on Linux and macOS, not just 'Windows PowerShell'.
Provide explicit instructions and examples for running Microsoft Graph PowerShell on Linux/macOS (e.g., using pwsh).
Offer alternative examples using Azure CLI or direct Microsoft Graph API calls with curl or httpie, which are platform-agnostic.
Avoid language that implies Windows is required (e.g., 'In your Windows PowerShell'), and instead use neutral phrasing such as 'In your terminal' or 'In PowerShell'.
Add a note or section for Linux/macOS users, highlighting any platform-specific considerations or prerequisites.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio (a Windows-centric IDE), .sln solution files, and Web.config XML configuration, all of which are typical of Windows/.NET development. There are no instructions or examples for Linux-based development environments, editors, or deployment scenarios. No mention is made of cross-platform .NET Core/ASP.NET Core, nor are there any Linux command-line or editor alternatives provided.

Recommendations:

Include instructions for opening and editing the project using cross-platform editors such as VS Code or JetBrains Rider, and clarify that .NET projects can be developed on Linux and macOS as well as Windows.
Provide examples for updating configuration using appsettings.json (used in .NET Core/ASP.NET Core) in addition to Web.config, or clarify the applicability to .NET Framework vs .NET Core.
Offer command-line instructions using the dotnet CLI (e.g., 'dotnet build', 'dotnet run') for building and running the sample, rather than assuming Visual Studio usage.
Explicitly mention that the sample and approach are applicable to Linux and macOS environments, and provide any necessary caveats or adjustments.
If any steps are specific to Windows (such as using Visual Studio), provide equivalent steps for Linux (e.g., using VS Code, nano, or vim to edit files).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as ASP.NET MVC, OWIN middleware, and .NET code samples) without providing equivalent Linux or cross-platform alternatives. Certificate management and application examples are oriented toward Windows environments, and there is a lack of explicit Linux-based instructions or examples for key steps such as application development, certificate creation, and configuration.

Recommendations:

Provide Linux-based examples for certificate creation and management (e.g., using OpenSSL commands) alongside or instead of Windows-centric instructions.
Include sample applications and code snippets that use cross-platform frameworks (such as Node.js, Python Flask/Django, or Java Spring) in addition to or instead of ASP.NET MVC/OWIN.
Reference Linux-compatible tools and workflows for application deployment and configuration, such as using Docker containers, shell scripts, or Linux-native editors.
Ensure that all steps (especially those involving file manipulation, certificate handling, and application configuration) have clear instructions for both Windows and Linux users.
Where possible, use platform-agnostic language and avoid assuming the reader is using Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by referencing Visual Studio (a primarily Windows tool) as the publishing method for the API, without mentioning cross-platform alternatives or providing Linux/macOS deployment instructions. There are no examples or guidance for deploying the API from non-Windows environments, and the only linked deployment instructions are for Visual Studio. This may hinder Linux or macOS users from following the tutorial seamlessly.

Recommendations:

Include alternative deployment instructions for the API using cross-platform tools such as the Azure CLI, GitHub Actions, or command-line dotnet publish and az webapp deploy commands.
Provide explicit Linux/macOS deployment steps or reference documentation that covers these platforms.
When referencing tools like Visual Studio, also mention Visual Studio Code and/or command-line methods that work on all major operating systems.
Ensure that all steps that involve tooling or commands have parity between Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell scripts for critical steps such as creating self-signed certificates and generating random keys, without offering equivalent Linux/macOS commands or guidance. The use of PowerShell and references to Visual Studio (a Windows-centric tool) further reinforce this bias, making it less accessible for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Bash/OpenSSL commands for creating self-signed certificates and generating random strings, ensuring Linux and macOS users can follow the tutorial.
Include explicit notes or sections for cross-platform compatibility, clarifying how each step can be performed on Windows, Linux, and macOS.
Mention and demonstrate the use of cross-platform tools (such as VS Code, Azure CLI, or OpenSSL) alongside Windows-specific tools like PowerShell and Visual Studio.
Where PowerShell is used, offer alternative scripts or command-line instructions for Bash/zsh.
Review all steps for hidden Windows assumptions (e.g., file paths, certificate stores) and document Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Visual Studio, Azure Storage Explorer) and workflows without providing Linux equivalents or alternatives. There are no command-line examples or instructions for Linux users, and the only publishing workflow mentioned is via Visual Studio, which is primarily a Windows application. The documentation also references Azure Storage Explorer, which, while cross-platform, is often associated with Windows, and does not mention alternative CLI tools or methods for Linux users.

Recommendations:

Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or VS Code, including command-line examples.
Explicitly mention and provide examples for Linux and macOS users, such as using the 'az storage' CLI for blob uploads and CORS configuration.
When referencing tools like Visual Studio or Azure Storage Explorer, clarify their cross-platform availability or suggest alternatives (e.g., VS Code, azcopy, Azure CLI).
Include shell (bash) command examples for common tasks like uploading files to Azure Blob Storage, setting CORS, and managing app settings.
Ensure that all steps that can be performed via the Azure Portal are also described for CLI/automation scenarios, which are common on Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell-based instructions for enabling Saviynt to delete users, explicitly requiring installation of the Microsoft Graph PowerShell module on a Windows workstation or server. There are no equivalent instructions or examples for Linux or cross-platform environments, and no mention of alternative tools (such as Azure CLI or Microsoft Graph CLI) that are available on Linux and macOS. This may limit accessibility for users operating in non-Windows environments.

Recommendations:

Provide equivalent instructions using cross-platform tools such as Azure CLI or Microsoft Graph CLI, which are supported on Linux and macOS.
Explicitly state that the PowerShell module can be used on PowerShell Core, which is available on Linux and macOS, if applicable.
Include Linux/macOS-specific setup steps or command-line examples where relevant.
Avoid language that restricts steps to 'Windows workstation or server' unless strictly necessary; instead, use 'workstation' or 'machine' and clarify OS compatibility.
Add a note or table summarizing tool availability and compatibility across operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric, focusing exclusively on a WPF (Windows Presentation Foundation) desktop application and requiring Visual Studio 2019, which is only available on Windows. There are no instructions, examples, or mentions of Linux or cross-platform alternatives for building or running the sample application. The tooling and workflow described (Visual Studio, WPF, F5 debugging) are all Windows-specific, and there is no guidance for Linux users.

Recommendations:

Provide equivalent instructions for Linux users, such as using .NET Core cross-platform desktop frameworks (e.g., Avalonia or MAUI) if possible.
Include examples for building and running the sample application using the .NET CLI, which is available on Linux and macOS.
Mention and link to cross-platform IDEs or editors (e.g., VS Code, JetBrains Rider) and provide steps for using them.
If the sample is inherently Windows-only (WPF), clearly state this limitation at the top and suggest alternatives or similar samples for Linux users.
Consider providing a cross-platform sample application alongside the WPF sample to ensure parity for non-Windows developers.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell script to monitor directory quota usage, with no equivalent example for Linux or cross-platform shells. The script uses Windows-specific cmdlets (Invoke-RestMethod, New-Object), and there is no mention of alternatives (such as Bash with curl or Python). This presents a clear Windows/Powershell bias and may hinder Linux or macOS users.

Recommendations:

Provide a Bash (curl) or Python example for Linux/macOS users to call the Microsoft Graph API and retrieve the directory quota.
Explicitly mention that the PowerShell script is for Windows, and offer equivalent instructions for other platforms.
Use cross-platform tools or note any platform-specific requirements.
Consider using the Microsoft Graph CLI or Azure CLI, which are cross-platform, as alternative examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell (Windows) examples are given immediately after the Bash ones, and are explicitly labeled as 'Formatted for PowerShell.' There is no explicit mention of Linux or macOS environments, and the Bash examples are not clearly labeled as 'Linux/macOS.' The documentation does not provide parity in guidance or troubleshooting for Linux users, and the structure may imply a Windows-first approach.

Recommendations:

Explicitly label Bash examples as 'Linux/macOS' and PowerShell examples as 'Windows' to clarify platform relevance.
Present Bash (Linux/macOS) examples before PowerShell (Windows) examples to avoid a Windows-first impression.
Add a brief note at the start of the CLI section explaining which example to use based on the user's operating system.
Ensure troubleshooting tips or environment-specific notes are included for both Windows and Linux/macOS users.
Consider providing a tabbed interface for Bash and PowerShell examples, so users can easily select their platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows-specific guidance first in at least one key area, and by omitting explicit Linux or cross-platform examples or instructions. Specifically, the link to securing REST APIs for technical profiles points to a documentation page with a 'tabs=windows' parameter, indicating Windows-first or Windows-only instructions. There are no PowerShell scripts or Windows tools directly shown, but the lack of Linux or cross-platform parity in referenced links and examples may hinder non-Windows users.

Recommendations:

Ensure that all referenced documentation links (such as those for securing REST APIs) either default to a cross-platform view or provide clear tabs for both Windows and Linux, with neither prioritized by default.
Explicitly mention that the steps and examples are platform-agnostic where possible, or provide parallel instructions for Linux/macOS environments if any step is platform-dependent.
Audit all external documentation links to confirm that Linux and macOS users are equally supported and not directed to Windows-specific instructions by default.
If any scripts or command-line examples are added in the future, provide both PowerShell (Windows) and Bash (Linux/macOS) versions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on ASP.NET Core and C# code, referencing project structures and files (e.g., Startup.cs, appsettings.json) that are typical of Windows/.NET development environments. There are no examples or guidance for Linux or cross-platform development environments, nor are there any mentions of command-line tools or workflows outside the Windows/.NET ecosystem.

Recommendations:

Include explicit notes or examples for developers working on Linux or macOS, such as how to locate and edit configuration files, or how to run and debug ASP.NET Core applications using the dotnet CLI.
Mention that ASP.NET Core is cross-platform and provide links or references to official guidance for developing and deploying on Linux and macOS.
If relevant, provide bash or shell command equivalents for any setup or configuration steps that might otherwise be performed in Windows-specific tools.
Clarify that the instructions and code samples apply to any platform where .NET Core is supported, not just Windows.
Consider including a section or callout box highlighting any platform-specific considerations (e.g., file paths, environment variables) for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal web UI for configuration and does not provide any command-line examples. There are no explicit references to Windows-only tools like PowerShell, but the workflow assumes a graphical interface that is most familiar to Windows users. There is no mention of Linux command-line tools (such as Azure CLI), nor are there any CLI-based instructions or examples for Linux or cross-platform users.

Recommendations:

Add Azure CLI examples for all major steps, such as registering applications, creating secrets, and configuring identity providers. Ensure these examples are cross-platform.
Explicitly mention that all portal steps can be performed from any OS with a web browser, to clarify that the instructions are not Windows-specific.
Where possible, provide REST API or scripting alternatives for automation and parity with non-Windows environments.
Include a section or callout for Linux/macOS users, highlighting any differences or additional steps if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by specifically mentioning Windows Hello as the primary example of biometric authentication, both in the introduction and in the scenario walkthrough. Windows Hello is referenced before any mention of biometric options on other platforms, and there are no explicit examples or tool references for Linux or macOS biometric authentication. The documentation does not provide parity in naming or describing Linux (or other OS) equivalents, nor does it offer platform-agnostic guidance.

Recommendations:

Include explicit references to biometric authentication methods available on Linux (such as fprintd, or biometric support in GNOME/KDE environments) and macOS (Touch ID, Face ID).
When describing scenarios, alternate or parallelize examples so that Windows, Linux, and macOS users see their platforms represented equally (e.g., 'After logging in with a Windows computer using Windows Hello, a Linux computer using fprintd, or a Mac using Touch ID...').
Avoid listing Windows tools or features (like Windows Hello) before mentioning cross-platform or other OS equivalents.
Add a section or table summarizing supported biometric authentication methods across different operating systems, with links to relevant setup guides for each.
Ensure screenshots or UI walkthroughs are not exclusively Windows-centric, or provide equivalents for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits mild Windows bias, most notably in the SAML application registration link, which includes a '?tabs=windows' query parameter, suggesting that Windows-specific instructions or tabs are prioritized or shown by default. There are no explicit Linux or cross-platform examples or tabs mentioned, and no Linux-specific tools or instructions are referenced.

Recommendations:

Ensure that all platform-specific instructions (Windows, Linux, macOS) are equally represented in relevant sections and tabs.
Where tabs or pivots are used (e.g., '?tabs=windows'), provide equivalent Linux and macOS tabs, and consider making the default tab platform-neutral or based on user agent detection.
Explicitly mention cross-platform tools and workflows (such as using the Azure CLI or REST API) alongside any platform-specific instructions.
Review all linked tutorials to ensure Linux users are not disadvantaged or required to adapt Windows-specific steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples, tools, or patterns. However, it assumes the use of Visual Studio Code (VS Code) as a prerequisite without mentioning Linux-specific alternatives or considerations. There are no OS-specific instructions, scripts, or screenshots, and no mention of PowerShell or Windows-only tools. The documentation is largely platform-neutral but lacks explicit Linux parity guidance or examples.

Recommendations:

Explicitly state that Visual Studio Code is cross-platform and provide installation links or instructions for Linux and macOS users.
Mention that all XML editing and Azure portal steps can be performed on Linux, macOS, or Windows.
If any command-line or scripting steps are added in the future, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) examples.
Include a note clarifying that the process is OS-agnostic and does not require Windows.
If screenshots are used, consider including examples from both Windows and Linux environments, or use neutral browser-based screenshots.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild 'windows_first' bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) version, with no explicit mention of Linux. No other sections show Windows-specific tools, PowerShell, or missing Linux examples.

Recommendations:

Explicitly mention Linux alongside iOS/macOS for Unix-like environments in the signature hash generation step (e.g., 'For Linux/macOS:').
Consider presenting cross-platform or Linux instructions before or alongside Windows instructions to avoid the impression of Windows primacy.
Where possible, clarify that the non-Windows command works for both Linux and macOS, not just iOS.
Review other documentation pages linked from this one to ensure Linux parity in all prerequisite and follow-up steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or tooling, but it also does not include any command-line or scripting examples at all. This omission means there is no explicit Windows bias, but there is a lack of parity in that neither Windows (e.g., PowerShell) nor Linux (e.g., Bash/cURL) approaches are demonstrated. Readers are left without practical, platform-agnostic examples for interacting with the Microsoft Graph API.

Recommendations:

Add practical examples for deleting and exporting user data using both PowerShell (for Windows users) and Bash/cURL (for Linux/macOS users).
Ensure that any command-line examples are provided in both Windows and Linux formats, or use platform-agnostic tools where possible.
Explicitly mention that the Microsoft Graph API can be accessed from any OS, and link to relevant SDKs or CLI tools for different platforms.
If using screenshots or UI walkthroughs, ensure they are not Windows-specific or provide Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples or tool references (such as PowerShell or Windows-specific tools). However, it is biased toward GUI-based instructions via the Azure Portal and does not provide any CLI-based examples (such as Azure CLI, Bash, or scripting), which are commonly used on Linux and cross-platform environments. There are no instructions or examples for performing these tasks using command-line tools that are available and popular on Linux.

Recommendations:

Add equivalent instructions for registering applications, granting permissions, and creating client secrets using the Azure CLI (az commands), which is cross-platform and widely used on Linux.
Provide sample scripts or command-line snippets for automating these tasks in Bash or shell environments.
Explicitly mention that all steps can be performed via CLI and link to relevant CLI documentation.
Ensure parity by including both portal (GUI) and CLI/script-based workflows in all sections where management actions are described.

Create pull request

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