Scan Details - Linux-first Docs for Azure

1713

Pages Scanned

23

Pages Flagged

1713

Changed Pages

1.3%

% Pages Flagged

Scan Information

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

Finished At: 2025-09-12 00:37:20

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

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for configuring password expiry duration, referencing the Microsoft Graph PowerShell module, and omitting equivalent instructions or examples for Linux or cross-platform environments (such as Bash, Azure CLI, or REST API via curl). The documentation assumes the use of Windows tools and patterns, and does not mention or prioritize Linux-compatible alternatives.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux and macOS users, especially for tasks currently demonstrated only with PowerShell.
Include REST API examples using curl or similar cross-platform tools for all operations shown with PowerShell.
When referencing tools or commands, mention both Windows and Linux options, or clarify if the instructions are cross-platform.
Reorder sections or examples to present cross-platform or Linux-compatible instructions before or alongside Windows/PowerShell examples.
Explicitly state the platform requirements for each example, and link to official documentation for installing required tools on both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and by providing a link to IIS setup instructions. There are no equivalent examples or instructions for Linux-based web servers (such as Apache or Nginx), nor are Linux tools or patterns mentioned. The documentation assumes the use of Windows environments for application testing and setup, which may exclude or disadvantage Linux users.

Recommendations:

Provide parallel examples and setup instructions for common Linux web servers (e.g., Apache, Nginx) alongside the IIS example.
Include links to official documentation for setting up test applications on Linux.
When referencing application setup, use neutral language (e.g., 'a web application such as IIS, Apache, or Nginx') rather than only mentioning Windows tools.
Ensure that any configuration steps or screenshots that are OS-specific are balanced with Linux equivalents.
Explicitly state that the solution is platform-agnostic where possible, and clarify any steps that are unique to Windows or Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio. All instructions, screenshots, and prerequisites are tailored to Windows environments, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for running or developing the sample on Linux or macOS.

Recommendations:

Provide equivalent instructions for running the sample on Linux (and macOS), such as using .NET Core cross-platform capabilities and alternative IDEs like VS Code or JetBrains Rider.
Include Linux/macOS prerequisites (e.g., .NET SDK installation, compatible editors, and command-line build/run instructions).
Offer screenshots and workflow steps for Linux/macOS environments to ensure parity.
Mention and link to any cross-platform sample applications (e.g., using Avalonia or MAUI instead of WPF) if available, or clarify Windows-only limitations.
Explicitly state platform requirements and suggest alternatives for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias, primarily in the certificate creation section where only PowerShell is mentioned for generating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) for certificate generation. The rest of the documentation is largely platform-neutral, focusing on Azure portal steps and XML configuration, but the lack of Linux or cross-platform tooling in key security setup steps may hinder non-Windows users.

Recommendations:

Add Linux and cross-platform examples for generating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
Wherever PowerShell is referenced, provide equivalent Bash or shell commands for Linux/macOS users.
Explicitly mention that certificate generation can be performed on any OS, and link to official documentation for OpenSSL or other cross-platform tools.
Review other sections for any implicit assumptions of Windows environments (e.g., file paths, tool usage) and clarify or generalize as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash/cURL or Python). PowerShell is primarily associated with Windows, and while it is available on Linux, it is not the default or most common scripting environment for Linux users. No mention is made of alternative tools or approaches more familiar to Linux administrators.

Recommendations:

Add a Bash/cURL example for querying the Microsoft Graph API to retrieve audit logs, demonstrating how to authenticate and download logs using common Linux tools.
Provide a Python script example, as Python is widely used and cross-platform.
Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation instructions or a note for non-Windows users.
Reorder or supplement the scripting section to present both Windows (PowerShell) and Linux (Bash/cURL or Python) options, or present a cross-platform solution first.
Reference CLI tools (such as Azure CLI or Microsoft Graph CLI) if available, and provide examples for those as well.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by providing only Azure PowerShell examples for disabling certificate chain validation, with no equivalent CLI or Linux-native instructions. The use of PowerShell cmdlets is highlighted, and there are no Bash, Azure CLI, or cross-platform scripting examples. This may hinder users working on Linux or macOS environments.

Recommendations:

Provide equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for backend configuration tasks.
Include Bash shell script examples or instructions for Linux/macOS users.
Explicitly mention that PowerShell Core is cross-platform if PowerShell must be used, and provide installation guidance for non-Windows systems.
Where possible, use REST API examples with curl or HTTPie to demonstrate platform-agnostic approaches.
Review all sections to ensure that Linux and macOS users are equally supported in step-by-step instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for custom role creation and assignment, without offering equivalent Azure CLI (cross-platform) or Bash examples. References to tools and links mention PowerShell before Azure CLI, and the only code sample is in PowerShell, which is primarily a Windows-centric tool. There are no Linux/Bash or cross-platform CLI examples, which may disadvantage users on non-Windows systems.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell code samples, especially for custom role creation and assignment.
When listing tools (Azure portal, PowerShell, Azure CLI, REST API), alternate the order or list Azure CLI before PowerShell to avoid 'windows_first' bias.
Explicitly mention that all operations can be performed using Azure CLI and provide links to relevant CLI documentation.
Include Bash or shell script examples where appropriate to ensure Linux parity.
Add a note clarifying that PowerShell Core is cross-platform, but still provide CLI/Bash alternatives for users who prefer them.

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 migrating from Windows environments, specifically IIS servers, and make extensive reference to PowerShell scripts. There are no Linux or cross-platform migration scenarios, tools, or examples provided. The documentation assumes the source environment is Windows and does not mention Linux-based .NET hosting (e.g., Kestrel, Apache, Nginx) or provide guidance for those users.

Recommendations:

Include migration guidance and examples for .NET apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
List Linux-compatible tools or scripts for discovery, assessment, and migration, or clearly state their absence and provide alternatives.
Provide Bash or cross-platform CLI examples alongside PowerShell scripts.
Mention Linux migration scenarios in tool descriptions and documentation tables, not just Windows/IIS.
Clarify in the introduction that the current tools are Windows/IIS-focused and link to Linux migration resources if available.
Add a section or FAQ addressing migration from Linux environments and any limitations or workarounds.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias, particularly in the 'Memory resources' and 'Node.js apps' sections. The use of 'web.config' and references to 'iisnode' are Windows/IIS-specific, with no equivalent Linux guidance or examples. While there is a brief mention of using PM2 for Node.js on Linux, the overall pattern is to present Windows-centric tools and configuration first or exclusively, with Linux alternatives either missing or less detailed.

Recommendations:

For 'Memory resources', provide Linux-specific configuration guidance (e.g., using environment variables or startup scripts) alongside or before 'web.config' for auto-healing.
In the 'Node.js apps' section, add information about configuring Node.js apps on Linux App Service (e.g., using PM2, ecosystem.config.js, or other process managers) and clarify when 'iisnode' is relevant versus Linux-native approaches.
Wherever Windows-specific tools or files (like 'web.config' or 'iisnode') are mentioned, add parallel Linux-native examples or note the differences in configuration between Windows and Linux App Service plans.
Review the order of presentation to avoid always listing Windows/Windows tools first; consider starting with platform-agnostic or Linux examples where appropriate.
Ensure troubleshooting and best practices sections include Linux-specific diagnostics and management options, not just those available via Windows/IIS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing Windows/Powershell options before Linux/CLI equivalents, providing detailed PowerShell examples, and referencing Windows-centric tools and navigation patterns. While Linux and Azure CLI are mentioned, Windows options are often presented first or more prominently, and there is heavier emphasis on PowerShell scripting.

Recommendations:

Present Linux and Windows options in parallel or alternate which is shown first, to avoid always prioritizing Windows.
Provide equal depth and detail for Azure CLI (cross-platform) and Azure PowerShell examples.
Where possible, use neutral language and screenshots that apply to both Windows and Linux users, or clearly indicate differences.
Include explicit Linux navigation or shell instructions where relevant, not just Azure CLI commands.
Ensure that all automation and scripting sections give equal weight to cross-platform tools (e.g., bash scripts, Azure CLI) as to PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows terminology and tools (such as PowerShell) are presented prominently, and in some cases, before their Linux equivalents. While Azure CLI examples are provided (which are cross-platform), the PowerShell section is given equal prominence, and there are no explicit Linux shell (bash) script examples. The UI instructions and screenshots are based on the Azure Portal, which is platform-agnostic, but there is a lack of explicit Linux command-line or automation guidance. Additionally, the 'availability' section lists Windows before Linux, and there is no mention of Linux-specific considerations or tools outside of the Azure CLI flag.

Recommendations:

Add explicit Linux shell (bash) script examples alongside PowerShell for automation tasks.
When listing availability or features, avoid presenting Windows before Linux unless there is a technical reason; consider grouping or alternating order.
Clarify that Azure CLI commands work on both Windows and Linux, and provide sample bash scripts for common workflows.
Include Linux-specific notes or troubleshooting tips where relevant, especially in automation and deployment sections.
Ensure parity in example depth and detail between Windows (PowerShell) and Linux (bash/CLI) automation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code, and by not providing explicit Linux or cross-platform instructions for running or building the sample application. There are no terminal or shell commands shown for Linux environments, nor are there any mentions of Linux-specific tools or considerations. The only command-line example is a generic Bash git clone, but all build/run instructions assume the use of Visual Studio or Visual Studio Code without clarifying Linux compatibility or providing dotnet CLI commands.

Recommendations:

Explicitly mention that the sample can be built and run on Linux and macOS using the .NET CLI (dotnet build, dotnet run), not just through Visual Studio/VS Code.
Provide step-by-step instructions for Linux users, including terminal commands for restoring dependencies, building, and running the application using the dotnet CLI.
Include notes about any platform-specific requirements or differences (such as HTTPS certificate setup on Linux/macOS).
List prerequisites for Linux (and optionally macOS), such as installing the .NET SDK and any required dependencies.
Ensure screenshots and instructions are not exclusively tailored to Windows environments.

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 omitting equivalent Linux or cross-platform guidance. For example, the steps to obtain and upload certificates for SAML configuration link to documentation with a 'tabs=windows' parameter, and there are no Linux or cross-platform alternatives or notes. Additionally, the only application code sample provided is for ASP.NET MVC (a Windows-centric technology), with no mention of Linux-compatible frameworks or deployment options.

Recommendations:

Provide explicit Linux (and macOS, if possible) instructions or links for certificate generation and management, such as using OpenSSL or Linux-native tools.
Update links to certificate management documentation to include both Windows and Linux tabs, or add a note clarifying Linux alternatives.
Include code samples or references for cross-platform or Linux-friendly application frameworks (e.g., Node.js, Python Flask, Java Spring) in addition to ASP.NET MVC.
When referencing sample applications, ensure at least one is easily runnable on Linux (e.g., the Docker header-demo-app is a good start, but clarify how to run it on Linux).
Review all step-by-step instructions to ensure parity for Linux users, especially in areas involving file manipulation, certificate creation, and application deployment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Visual Studio Code and Azure Functions extensions, which are cross-platform, but the workflow and terminology (e.g., 'command prompt', 'Visual Studio Marketplace') are more familiar to Windows users. There are no explicit Linux/macOS shell examples or references to Linux-specific tools or workflows. The instructions for running and deploying the API mention 'terminal or command prompt' generically, but all step-by-step guidance and screenshots are based on the Azure Portal and Visual Studio Code UI, with no CLI or Linux-native workflow examples. There is no mention of Bash, zsh, or Linux package managers, nor are there any screenshots or commands shown from a Linux environment.

Recommendations:

Add explicit examples and instructions for Linux users, such as using Bash or zsh in the terminal.
Include CLI-based alternatives (e.g., Azure CLI, az functionapp commands) for creating and deploying Azure Functions, alongside Visual Studio Code instructions.
Reference Linux package managers or installation steps for required tools (e.g., how to install Azure Functions Core Tools on Ubuntu).
Provide screenshots or terminal output examples from a Linux environment.
Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and provide links or notes for Linux/macOS installation and usage.
Avoid Windows-centric terminology like 'command prompt' unless also mentioning 'terminal' or 'shell' for Linux/macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently lists Bash first and PowerShell second. There are no exclusive Windows-only tools or steps, but the presence of PowerShell examples throughout, and the explicit mention that Azure CLI commands can run in PowerShell or Bash, introduces a mild Windows bias. All tooling and instructions are otherwise cross-platform (Azure CLI, azd, Visual Studio Code), and Linux users are not excluded, but the parity in example prominence could be improved.

Recommendations:

Alternate the order of Bash and PowerShell examples throughout the documentation, or present both equally (e.g., side-by-side tabs).
Explicitly state that all tools and steps are fully supported on Linux, macOS, and Windows.
Where possible, provide a single cross-platform command (e.g., using environment-agnostic syntax) before splitting into shell-specific variants.
Add a brief section or callout confirming that Visual Studio Code and Azure CLI are available and supported on Linux, macOS, and Windows.
If referencing Visual Studio Code, clarify that it is cross-platform and provide links to Linux/macOS installation guides as well.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on the Azure portal and Microsoft Entra ID (formerly Azure AD), which are Microsoft-centric tools and services. All step-by-step instructions and screenshots are based on the Azure portal UI, with no mention of command-line alternatives (such as Azure CLI, PowerShell, or REST API), nor any examples for Linux-based workflows or non-Microsoft OAuth 2.0 providers. There are no references to Linux tools, shell commands, or cross-platform approaches for registering applications or configuring OAuth 2.0, making the documentation less accessible to Linux users or those preferring automation and scripting.

Recommendations:

Provide equivalent instructions using Azure CLI and/or REST API, which are cross-platform and can be run on Linux, macOS, and Windows.
Include examples for registering applications and configuring OAuth 2.0 using command-line tools (e.g., az ad app create, az ad app permission, etc.), not just the Azure portal.
Mention and, where possible, demonstrate how to use non-Microsoft OAuth 2.0 providers (such as Google, Okta, Auth0) to illustrate broader applicability.
Add a section or callout for Linux users, highlighting any differences or additional steps required when working outside the Windows ecosystem.
Ensure that any screenshots or UI references are supplemented with text-based, scriptable alternatives for automation and CI/CD scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions exclusively through the Azure Portal UI and does not include any command-line examples. There is no mention of PowerShell or Windows-specific tools, but there is also a complete absence of Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples. All example paths and screenshots are based on the Azure Portal, which is platform-agnostic but may be more familiar to Windows users. The lack of CLI or script-based instructions can disadvantage Linux users or those who prefer automation.

Recommendations:

Add Azure CLI examples for importing and configuring Azure OpenAI APIs in API Management, as the Azure CLI is cross-platform and widely used on Linux.
Include Bash script snippets for downloading and editing the OpenAPI specification, in addition to the manual text editor instructions.
Explicitly mention that all steps can be performed on any OS via the Azure Portal, but provide parity with CLI-based workflows for users on Linux or those preferring automation.
If PowerShell examples are ever added, ensure equivalent Bash/Azure CLI examples are provided alongside.

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. There are no references to Windows-specific tools like PowerShell, but the lack of CLI instructions (such as Azure CLI or Bash) means Linux users do not see parity. The workflow implicitly assumes a GUI-first (and thus, often Windows-first) approach, which can disadvantage users on Linux or those who prefer automation.

Recommendations:

Add equivalent Azure CLI commands for all steps, especially for creating app registrations, configuring credential providers, and setting API Management policies.
Provide Bash shell examples for relevant steps, such as using curl or az commands.
Explicitly mention that all steps can be performed on any OS via the Azure portal, but highlight CLI alternatives for Linux/macOS users.
Include a section or callout for automation and scripting, referencing cross-platform tools.
Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-only UI elements if possible).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by exclusively referencing the Azure portal (a web UI), Azure CLI, and REST API for configuration, but does not provide any OS-specific command-line examples. However, in the 'Test in virtual network' section, only the nslookup utility is mentioned for DNS validation, which is available on both Windows and Linux, but no explicit Linux or cross-platform shell examples are provided. There are no PowerShell-specific commands or Windows-only tools, but the absence of Linux-specific or cross-platform shell examples (e.g., bash, curl, dig) and the lack of explicit mention of Linux environments or tools indicate a subtle Windows-first and missing Linux example bias.

Recommendations:

Include explicit Linux and cross-platform command-line examples (e.g., using dig, curl, or bash scripts) alongside nslookup.
When referencing Azure CLI, clarify that it is cross-platform and provide sample commands in both Windows (cmd/PowerShell) and Linux (bash) syntax where relevant.
Add troubleshooting and validation steps using common Linux tools (e.g., dig, host, curl) to ensure parity.
Explicitly mention that all steps can be performed from Linux environments, and provide any OS-specific notes if differences exist.
Where screenshots or UI steps are shown, consider adding CLI/automation alternatives that are equally accessible from Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily demonstrates deployment using the Azure Portal UI and briefly mentions Azure PowerShell, Azure CLI, and REST API as alternatives, but does not provide any concrete command-line examples for any platform. There is a subtle Windows-first bias in the order of tool mentions (PowerShell before CLI), and the absence of explicit Linux/macOS command-line examples or screenshots. The documentation does not show any PowerShell or Windows-specific commands, but also does not provide parity for Linux users.

Recommendations:

Add explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
When listing alternative deployment methods, mention Azure CLI before PowerShell to avoid implying a Windows-first workflow.
Include at least one example of deploying the template using the Azure CLI, with sample commands and expected output.
If referencing PowerShell, also provide Bash/Linux shell equivalents for all command-line operations.
Add screenshots or terminal snippets from both Windows and Linux environments if possible, or use neutral/abstracted terminal screenshots.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses on assessing .NET web apps for migration to Azure App Service but does not mention Linux-based .NET hosting, Linux tools, or provide any Linux-specific guidance or examples. The implicit assumption is that the reader is working in a Windows environment, which is common for legacy ASP.NET apps, but modern .NET Core/ASP.NET Core apps are often hosted on Linux. There is no discussion of Linux assessment tools, patterns, or considerations.

Recommendations:

Explicitly mention that both Windows and Linux hosting are supported on Azure App Service, and clarify which assessment steps apply to each.
Include examples or notes for assessing .NET Core/ASP.NET Core apps running on Linux, including any differences in migration blockers or readiness checks.
Reference Linux-native tools or commands (such as Bash scripts or Linux CLI) where appropriate, alongside any Windows/Powershell examples.
Add a section or links addressing Linux-specific migration considerations, such as file system differences, case sensitivity, and environment variable handling.
Ensure parity in documentation by providing Linux and Windows assessment workflows side-by-side where relevant.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a mild 'windows_first' bias by linking to API protection instructions that default to a Windows-specific tab (e.g., '?tabs=windows') when referencing further documentation. However, the main content itself is largely platform-neutral, focusing on Azure AD B2C policy XML and REST API patterns without explicit use of Windows-only tools or commands. There are no PowerShell-heavy sections, exclusive Windows tools, or missing Linux examples in the main body.

Recommendations:

When linking to further documentation (such as 'secure-rest-api.md?tabs=windows'), ensure that links are either platform-neutral or explicitly mention both Windows and Linux options.
If the linked documentation contains platform-specific instructions, provide a brief note or alternative link for Linux/macOS users.
Review all referenced guides and ensure parity in examples and instructions for both Windows and Linux environments.
Consider adding a short section or note clarifying that the described steps and API interactions are OS-agnostic, and can be performed from any platform.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows file path is mentioned before the Linux/macOS equivalent. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present. However, the ordering of operating systems in the hosts file path reference subtly prioritizes Windows.

Recommendations:

List Linux/macOS and Windows hosts file paths in parallel or alternate the order to avoid implicit prioritization.
Where file paths or commands are referenced, provide both Windows and Linux/macOS examples side by side.
Review related links to ensure they do not disproportionately reference Windows-specific documentation (e.g., the 'Creating a record in DNS' link points to a Windows 2000 Server article; consider adding a Linux/BIND equivalent or a cross-platform Azure DNS guide).

Create pull request

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