Security

231
Total Pages
188
Linux-Friendly Pages
43
Pages with Bias
18.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

90 issues found
Showing 26-50 of 90 flagged pages
Security Design secure applications on Microsoft Azure ...s/blob/main/articles/security/develop/secure-design.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references the Microsoft Security Development Lifecycle (SDL) with links to Windows documentation, mentions remote PowerShell access as a management interface, and frequently highlights Microsoft-specific tools and services (e.g., Entra ID, Azure Key Vault, Azure DevOps) without Linux/macOS alternatives or parity notes. Examples and links are often Windows/.NET-centric, and Linux-specific tools, workflows, or command-line examples are absent. While the content is generally platform-agnostic in its security advice, the framing and tool recommendations favor Windows and Microsoft ecosystems, which may create friction for Linux/macOS users.
Recommendations
  • Include Linux/macOS equivalents or alternatives for management interfaces (e.g., Azure CLI, Bash, SSH) alongside PowerShell references.
  • Provide examples or links for cross-platform SDKs and tools, explicitly noting Linux/macOS compatibility.
  • Add references to open-source, platform-neutral security tools (e.g., OWASP ZAP, HashiCorp Vault) where appropriate.
  • Ensure that quickstarts, tutorials, and API references highlight cross-platform support and provide parity for Linux/macOS users.
  • Balance references to Windows-specific documentation with links to platform-neutral or Linux/macOS guides.
GitHub Create Pull Request
Security Authentication - Microsoft Threat Modeling Tool - Azure | Microsoft Docs ...ecurity/develop/threat-modeling-tool-authentication.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows authentication is recommended first and often exclusively for SQL Server, with references to Windows-specific tools (e.g., Windows Server certificate service, MakeCert.exe). Examples and configuration patterns (WCF, MSMQ) are Windows-centric, with little to no mention of Linux/macOS equivalents or cross-platform alternatives. There are no explicit Linux/macOS authentication examples, and Windows terminology and tools are referenced before or instead of platform-neutral options.
Recommendations
  • Add Linux/macOS authentication examples for SQL Server (e.g., Kerberos, PAM, or SQL authentication from Linux clients).
  • Mention and provide parity for certificate management tools on Linux (e.g., OpenSSL, certbot) alongside Windows Server certificate service.
  • Include cross-platform configuration patterns for WCF/MSMQ, or note their Windows-only nature and suggest alternatives for Linux/macOS.
  • When listing authentication mechanisms, present platform-neutral options first (e.g., client certificates, OAuth, OpenID Connect) and clarify which are Windows-specific.
  • Where Windows authentication is recommended, explicitly state alternatives for non-Windows environments.
  • Provide references to Linux/macOS documentation or guides for Azure authentication scenarios.
GitHub Create Pull Request
Security Communication security for the Microsoft Threat Modeling Tool ...develop/threat-modeling-tool-communication-security.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many examples and recommendations are tailored to Windows-centric technologies (e.g., ASP.NET, WCF, SQL Server Management Studio, web.config/URL Rewrite, ServicePointManager, SMB clients for Windows). Code samples are provided only in C#/.NET, and configuration instructions often reference Windows tools or patterns first or exclusively. There is a lack of Linux/macOS-specific guidance, especially for tasks like enforcing HTTPS, certificate pinning, and SMB access, which may differ significantly on non-Windows platforms.
Recommendations
  • Provide equivalent Linux/macOS examples for enforcing HTTPS (e.g., using Nginx/Apache config for redirects and HSTS).
  • Include code samples in cross-platform languages (e.g., Python, Node.js) for certificate pinning and HTTPS enforcement.
  • Mention Linux-compatible SMB clients (e.g., mount.cifs with SMB3) and provide configuration steps for Linux environments.
  • Reference Linux database tools (e.g., sqlcmd, Azure Data Studio) for SQL Server encryption validation.
  • Clarify when recommendations are Windows-specific and offer alternatives for other platforms.
  • Add explicit notes or sections for Linux/macOS deployment scenarios, especially for Azure services.
GitHub Create Pull Request
Security Authorization - Microsoft Threat Modeling Tool - Azure | Microsoft Docs ...security/develop/threat-modeling-tool-authorization.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While most sections are generic and platform-agnostic, examples and configuration snippets for WCF and ASP.NET Web API are Windows/.NET-centric, referencing Windows roles, Windows groups, and Windows configuration files (machine.config, app.config). There are no equivalent examples for Linux/macOS platforms or cross-platform frameworks, and Windows terminology (e.g., 'Builtin\Administrators') is used without alternatives. No Linux-specific tools, patterns, or configuration methods are mentioned, and the order of presentation favors Windows technologies.
Recommendations
  • Provide equivalent examples for Linux/macOS environments, such as using Unix file permissions, Linux ACLs, or cross-platform frameworks (e.g., gRPC, RESTful APIs in Python/Node.js).
  • Include examples of authorization using Linux user/groups, PAM, or other Linux-native mechanisms.
  • When discussing WCF and ASP.NET, mention cross-platform alternatives (e.g., .NET Core, gRPC, REST APIs) and how authorization is handled outside Windows.
  • Avoid using Windows-specific terminology exclusively; add notes or examples for non-Windows equivalents.
  • Reorder examples or add parallel Linux/macOS examples to ensure parity.
GitHub Create Pull Request
Security Input Validation - Microsoft Threat Modeling Tool - Azure | Microsoft Docs ...urity/develop/threat-modeling-tool-input-validation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows-centric technologies and patterns, such as .NET, IIS, MSXML, and WCF. All code examples are in C# and reference Windows-specific APIs, configuration files (web.config), and services (IIS, http.sys). There is little to no mention of Linux or cross-platform equivalents, and Linux-specific patterns or tools are absent. Even generic recommendations (e.g., HTTP headers) are shown first in a Windows/IIS context, with no Apache/Nginx or Linux example. References and links are predominantly Microsoft/Windows-focused.
Recommendations
  • Add Linux/macOS-specific examples for each mitigation, such as showing how to set HTTP headers in Apache (httpd.conf) or Nginx (nginx.conf), and how to perform input validation in popular Linux frameworks (e.g., Python Flask, Node.js Express).
  • Include cross-platform code samples (e.g., Java, Python, Node.js) alongside C#/.NET examples.
  • Reference Linux tools and libraries for XML parsing, file upload validation, and output encoding (e.g., lxml, bleach, python-magic, etc.).
  • When discussing configuration (e.g., MIME sniffing), provide instructions for both Windows (IIS/web.config) and Linux (Apache/Nginx) environments.
  • Balance references and links to include non-Microsoft resources (OWASP, Linux man pages, etc.).
  • Explicitly state when a mitigation is platform-specific, and offer alternatives for other platforms.
GitHub Create Pull Request
Security Sensitive Data - Microsoft Threat Modeling Tool - Azure | Microsoft Docs ...ecurity/develop/threat-modeling-tool-sensitive-data.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias, with several sections referencing Windows-specific technologies (EFS, DPAPI, BitLocker, Intune) and tools (CryptoObfuscator) without providing equivalent Linux/macOS alternatives or examples. Windows technologies are often mentioned first or exclusively, and Linux options (e.g., dm-crypt) are only briefly referenced in one section. There are no Linux/macOS code samples, and some mitigation steps are described only in terms of Windows features.
Recommendations
  • For each Windows-specific technology (e.g., EFS, DPAPI, BitLocker), add equivalent Linux/macOS options and examples (e.g., eCryptfs, LUKS/dm-crypt, GNOME Keyring, macOS Keychain).
  • Provide Linux/macOS code samples and configuration snippets alongside Windows/.NET examples.
  • Mention Linux/macOS tools and patterns before or alongside Windows ones, not only as afterthoughts.
  • Where third-party tools are recommended (e.g., CryptoObfuscator), suggest cross-platform alternatives.
  • Clarify which mitigations are cross-platform and which are Windows-only, and provide guidance for non-Windows environments.
GitHub Create Pull Request
Security Platform code integrity - Azure Security .../main/articles/security/fundamentals/code-integrity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily discusses code integrity as a Windows Server feature, mentioning its availability since Windows Server 2016 and describing its operation in detail. While DM-Verity is briefly referenced as a 'similar system' for Linux, no further explanation, examples, or parity details are provided for Linux or macOS. The build and deployment process is described in a Windows-centric context, with no Linux-specific guidance or examples.
Recommendations
  • Expand the section on Linux by providing a brief overview of DM-Verity, including how it is configured and used in production environments.
  • Include example workflows or commands for setting up code integrity on Linux (e.g., configuring DM-Verity, signing binaries, enforcing policies).
  • If applicable, mention macOS equivalents (such as System Integrity Protection) and how they fit into Azure's platform integrity strategy.
  • Present Windows and Linux solutions side-by-side or in parallel sections to ensure equal visibility and guidance.
  • Clarify whether Azure's build and deployment integrity checks apply to Linux workloads, and describe any differences.
GitHub Create Pull Request
Security Security Recommendations for Azure Marketplace Images | Microsoft Docs ...cles/security/fundamentals/azure-marketplace-images.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides separate checklists for Linux and Windows images, but there are signs of Windows bias. Windows terminology (e.g., 'Windows Server roles') appears in the Linux section, and some checks are described with Windows-centric language. Windows tools like BitLocker are mentioned, but Linux equivalents (e.g., LUKS) are not. Some configuration examples (like auto-update) are given for Windows but not for Linux. The Linux section is more detailed, but certain recommendations (such as disk encryption) lack Linux-specific guidance.
Recommendations
  • Replace or clarify Windows-specific terms in the Linux section (e.g., 'Windows Server roles') to use Linux equivalents (e.g., 'Linux services', 'daemons').
  • Add Linux-specific disk encryption recommendations (e.g., suggest LUKS or dm-crypt as alternatives to BitLocker).
  • Provide Linux examples for auto-updating security patches (e.g., using unattended-upgrades or dnf-automatic).
  • Ensure that all recommendations are equally actionable for both platforms, with platform-specific tools and commands included.
  • Review the order and prominence of examples to avoid Windows-first language or patterns.
GitHub Create Pull Request
Security Hypervisor security on the Azure fleet - Azure Security ...blob/main/articles/security/fundamentals/hypervisor.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows technologies, specifically Hyper-V, with no mention of Linux-based hypervisors or management tools. All terminology and security features are described in the context of Windows and Hyper-V, and there are no examples or guidance for Linux or cross-platform scenarios.
Recommendations
  • Include references to Linux-based hypervisors (e.g., KVM, Xen) and how Azure secures these workloads.
  • Provide examples or explanations for Linux VM security boundaries and mitigations within Azure.
  • Clarify whether the described security features apply to all Azure VMs regardless of guest OS, or only to Windows/Hyper-V guests.
  • Add links or sections about managing and securing Linux VMs in Azure, including relevant tools and best practices.
GitHub Create Pull Request
Security Azure identity & access security best practices | Microsoft Docs ...ity/fundamentals/identity-management-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It frequently references Windows-specific tools (Active Directory, Windows Server, Windows Hello for Business, Privileged Access Workstations), and PowerShell is mentioned as a primary automation method. Linux/macOS equivalents or cross-platform alternatives are rarely mentioned, and examples or guidance for non-Windows environments are missing. Windows-centric terminology and solutions are presented first or exclusively, which may create friction for Linux/macOS users seeking parity.
Recommendations
  • Include explicit guidance and examples for Linux/macOS environments, especially for automation (e.g., Azure CLI, Bash scripting) and workstation security.
  • Reference cross-platform identity management tools and patterns, such as LDAP, Kerberos, or SSSD, where appropriate.
  • When discussing admin workstations, mention Linux/macOS hardening strategies and tools alongside Windows PAWs.
  • Provide parity in authentication examples (e.g., FIDO2, passkeys) for Linux/macOS, not just Windows Hello.
  • Clarify which features and recommendations are platform-agnostic and which are Windows-specific.
  • Add links to Azure CLI documentation and usage for Linux/macOS throughout, not just PowerShell.
  • When referencing password protection agents, note availability or alternatives for non-Windows environments.
GitHub Create Pull Request
Security Azure information system components and boundaries ...les/security/fundamentals/infrastructure-components.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by referencing Windows Firewall as the default security tool on Azure VMs and stating that Azure VMs run a customized version of Windows Server at the host layer. There is no mention of Linux equivalents (e.g., iptables, firewalld) or Linux-based host images, nor are Linux-specific management or security patterns discussed. The examples and descriptions focus exclusively on Windows technologies and do not provide parity for Linux or macOS users.
Recommendations
  • Explicitly mention support for Linux-based VMs and host images in Azure, including how security boundaries and firewalls are managed on Linux (e.g., iptables, firewalld).
  • Provide examples or descriptions of how Linux VMs are provisioned, managed, and secured within the Azure architecture.
  • Clarify whether the host layer can run Linux or if it is strictly Windows Server, and discuss implications for Linux workloads.
  • Include references to Linux administrative tools and patterns where relevant, such as SSH for remote access, SELinux/AppArmor for hardening, and Linux-based secure admin workstations.
  • Ensure that documentation sections describing VM security, management, and boundaries address both Windows and Linux scenarios.
GitHub Create Pull Request
Security Cloud feature availability for commercial and US Government customers ...articles/security/fundamentals/feature-availability.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of PowerShell for administration examples and references to Windows-centric tools and environments (e.g., Microsoft 365 Apps, Office, PowerShell). Linux-specific administration methods, CLI examples, or parity in tooling are not mentioned, and Windows/PowerShell approaches are presented as the default or only option for several tasks. However, the page is mostly focused on feature availability tables and does not include step-by-step examples, so the impact is mitigated.
Recommendations
  • Include equivalent Linux/macOS administration instructions (e.g., Azure CLI, Bash scripts) alongside PowerShell examples.
  • Explicitly mention cross-platform support for tools and clients where applicable.
  • Add notes or links to Linux/macOS documentation for relevant features (e.g., AIP scanner, Defender for Cloud).
  • Ensure that any references to client software (e.g., Microsoft 365 Apps) clarify OS support and alternatives for non-Windows users.
GitHub Create Pull Request
Security Security best practices for IaaS workloads in Azure | Microsoft Docs ...-docs/blob/main/articles/security/fundamentals/iaas.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Several examples and tool references are Windows-centric, such as PowerShell cmdlets (Add-AzKeyVaultKey, Set-AzVMDiskEncryptionExtension), Windows Defender, WSUS, and backup/snapshot instructions that link to Windows-specific articles. Linux equivalents are sometimes mentioned, but often lack detailed examples, and Windows tools or instructions are frequently presented first or exclusively. This creates friction for Linux users, who may need to seek additional documentation to complete equivalent tasks.
Recommendations
  • Provide Linux-specific command-line examples (e.g., Azure CLI, Bash scripts) alongside PowerShell cmdlets.
  • Include links to Linux-focused documentation for tasks like disk encryption, backup, and snapshots, not just Windows versions.
  • Mention and detail Linux endpoint protection solutions (e.g., ClamAV, Sophos) with equal prominence as Windows Defender.
  • Ensure that instructions for monitoring, diagnostics, and update management explicitly cover Linux workflows and tools.
  • Present examples for both Windows and Linux in parallel, rather than defaulting to Windows-first.
  • Clarify when a tool or feature is Windows-only, and offer Linux alternatives or workarounds.
GitHub Create Pull Request
Security Isolation in the Azure Public Cloud | Microsoft Docs ...in/articles/security/fundamentals/isolation-choices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and terminology (e.g., Windows Firewall, BitLocker, Active Directory Federation Services, Group Policy) are referenced frequently and often before their Linux equivalents. Examples and explanations for Linux users (such as dm-crypt, mdadm, LVM) are present but less detailed and sometimes referenced after Windows solutions. There are no explicit command-line examples for either platform, but Windows-centric patterns and technologies are described more thoroughly. Some features (e.g., Group Policy, BitLocker) are described only in the context of Windows, with Linux alternatives mentioned briefly or as secondary options.
Recommendations
  • Provide Linux/macOS-specific examples and explanations alongside Windows ones, especially for security and management tools.
  • Ensure that Linux technologies (e.g., dm-crypt, iptables, SELinux, systemd) are described with equal detail and prominence as Windows tools.
  • When referencing features like Group Policy or BitLocker, include equivalent Linux approaches (e.g., configuration management tools, dm-crypt) and link to relevant documentation.
  • Avoid using Windows terminology as the default; use cross-platform or neutral terms where possible.
  • Add explicit command-line examples for both Windows (PowerShell, CMD) and Linux (Bash, CLI tools) where relevant.
GitHub Create Pull Request
Security Securing PaaS web & mobile applications ...y/fundamentals/paas-applications-using-app-services.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits mild Windows bias, particularly in the section on restricting incoming source IP addresses. It specifically mentions configuring web.config for dynamic IP security on App Service for Windows and links to IIS documentation, without providing equivalent guidance or examples for Linux-based App Service environments. No Linux or cross-platform alternatives are discussed, and the Windows method is presented first and exclusively.
Recommendations
  • Include instructions or examples for restricting IP addresses on App Service for Linux, such as using .htaccess, nginx configuration, or Azure-native controls.
  • Explicitly state platform differences and provide parity in documentation for both Windows and Linux App Service environments.
  • Reference Linux-relevant documentation or tools alongside Windows/IIS examples.
  • Consider reordering or grouping platform-specific guidance to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Security Azure Operational Security | Microsoft Docs ...articles/security/fundamentals/operational-security.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (e.g., 'Windows Azure', 'Windows Server', 'Windows event logs') is used frequently and often appears before or instead of Linux equivalents. Examples and references to Windows-specific tools and logs (such as Windows event logs, IIS logs, System Center Data Protection Manager) are provided, while Linux-specific examples (e.g., syslog) are mentioned only in passing and lack detail. Some sections, such as Azure Diagnostics, focus on Windows VMs and services, with Linux support only briefly acknowledged. There are no explicit Linux command-line or syslog configuration examples, and Windows-centric tools are referenced more often.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for log collection, diagnostics, and backup scenarios.
  • Mention Linux tools (e.g., journalctl, rsyslog, logrotate) and how they integrate with Azure Monitor and Defender for Cloud.
  • Ensure references to agents, diagnostics, and monitoring explicitly state Linux support and provide parity in detail.
  • Avoid using 'Windows Azure' and 'Windows Server' as the default terminology; use 'Azure' and 'virtual machines' to be platform-neutral.
  • Include sample syslog, auditd, or other Linux log sources and how to configure them for Azure services.
GitHub Create Pull Request
Security Introduction to Azure security | Microsoft Docs ...s/blob/main/articles/security/fundamentals/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform in its descriptions, but there are several areas where Windows-specific tools, terminology, and examples are prioritized or exclusively mentioned. Windows and PowerShell are referenced before Linux equivalents, and some features (such as Microsoft Entra join) are described as Windows-only. PowerShell is mentioned as the automation tool for certain tasks (e.g., SQL VM TDE integration), with no mention of Bash or Linux CLI alternatives. Windows-centric features and terminology (IIS, BitLocker, Windows 10 device management) are highlighted, while Linux equivalents are not discussed or are referenced only in passing.
Recommendations
  • Provide Linux/Bash CLI examples alongside PowerShell for automation and configuration tasks.
  • Explicitly mention Linux equivalents for features such as device management, disk encryption, and logging.
  • Ensure that Linux and macOS support is described for all security features, especially in sections where Windows tools are highlighted.
  • Avoid listing Windows tools or features first unless there is a technical reason; alternate ordering or group by platform.
  • Where features are Windows-only (e.g., Microsoft Entra join), clarify Linux/macOS alternatives or limitations.
GitHub Create Pull Request
Security Detect and respond to ransomware attacks ...les/security/fundamentals/ransomware-detect-respond.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools and patterns (e.g., Security Event log, PowerShell Operational logs, Defender for Endpoint isolation links pointing to Windows documentation) and does not provide equivalent Linux examples or mention Linux-specific tools/logs. Windows terminology and examples are presented first and exclusively, with no guidance for Linux or macOS users managing Azure VMs or responding to ransomware attacks.
Recommendations
  • Include examples and guidance for Linux VMs, such as monitoring syslog, auditd logs, and Linux-specific ransomware indicators.
  • Mention Linux equivalents for event log clearing (e.g., /var/log/auth.log, /var/log/syslog) and how to detect tampering.
  • Provide instructions for isolating Linux VMs using Defender for Endpoint or Azure tools, with links to Linux-specific documentation.
  • Reference Linux anti-malware solutions and incident response patterns alongside Windows tools.
  • Ensure all sections that mention Windows-specific logs or tools also mention Linux/macOS equivalents.
GitHub Create Pull Request
Security Best practices for protecting secrets ...ticles/security/fundamentals/secrets-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure and Microsoft-centric tools and services, many of which are primarily used or best supported on Windows. Examples and links often default to Windows tools (e.g., Azure PowerShell, Azure portal) and do not provide Linux/macOS-specific alternatives or parity in instructions. There is a lack of explicit Linux/macOS command-line examples (such as bash, Azure CLI, or open-source secret management tools), and Windows-centric terminology and patterns are presented first or exclusively.
Recommendations
  • Add Linux/macOS-specific examples for secret management, such as using Azure CLI, bash scripts, or open-source tools like HashiCorp Vault.
  • Ensure that all referenced tutorials and guides include both PowerShell and bash/CLI instructions, and clearly indicate platform compatibility.
  • Mention cross-platform secret scanning tools (e.g., TruffleHog, Gitleaks) alongside Microsoft-specific solutions.
  • Include references to Linux-native patterns for environment variable management, file permissions, and integration with Azure services.
  • When listing service-specific best practices, indicate which instructions are platform-agnostic and provide alternative steps for Linux/macOS where necessary.
GitHub Create Pull Request
Security Secure your Microsoft Entra identity infrastructure ...rticles/security/fundamentals/steps-secure-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias, primarily through frequent references to Windows-centric tools and technologies such as AD FS, Windows Server Active Directory, and features like 'AD FS Extranet Smart Lockout.' These are mentioned without Linux/macOS equivalents or alternatives, and Windows-based solutions are often presented first or exclusively. There are no examples or guidance for Linux/macOS environments, especially for hybrid identity scenarios or password protection deployments. The lack of parity may create friction for organizations with non-Windows infrastructure.
Recommendations
  • Include examples and guidance for Linux and macOS environments, especially for hybrid identity scenarios.
  • Mention or link to cross-platform alternatives for features like password protection, lockout mechanisms, and monitoring.
  • Clarify which recommendations are Windows-specific and provide Linux/macOS equivalents or workarounds where possible.
  • Add notes or sections on integrating Microsoft Entra ID with non-Windows identity providers and infrastructure.
  • Ensure that monitoring and automation examples include SIEM and logging tools commonly used on Linux/macOS.
GitHub Create Pull Request
Security Best practices for Azure Service Fabric security ...security/fundamentals/service-fabric-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. It frequently references Windows-specific tools and patterns, such as PowerShell modules and Windows Server certificate services, and often omits or de-emphasizes Linux equivalents. Instructions and examples for cluster creation, certificate management, and security configuration are primarily or exclusively Windows-focused, with little to no guidance for Linux users. Windows terminology and tools (e.g., Remote Desktop Connection, Active Directory, MakeCert.exe) are mentioned without Linux alternatives, and Linux-specific workflows are not addressed.
Recommendations
  • Include equivalent Linux examples and instructions for all major tasks (e.g., cluster creation, certificate management, security configuration).
  • Reference cross-platform tools (such as Azure CLI or REST APIs) alongside or instead of PowerShell.
  • Provide guidance for certificate creation and management using Linux-native tools (e.g., OpenSSL) and document how to integrate with Azure Key Vault from Linux environments.
  • Mention SSH and Linux jump server patterns when discussing remote management, not just Remote Desktop Connection.
  • Clarify which features and steps apply to Linux clusters and provide links to Linux-specific documentation where available.
  • Ensure Active Directory references are balanced with Microsoft Entra ID and other identity solutions that work cross-platform.
GitHub Create Pull Request
Security Prevent subdomain takeovers with Azure DNS alias records and Azure App Service's custom domain verification ...n/articles/security/fundamentals/subdomain-takeover.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily by exclusively referencing PowerShell scripts and tools for identifying dangling DNS entries and running Azure Resource Graph queries. There are no examples or instructions for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting alternatives). Windows/PowerShell tooling is presented as the default and only method, which may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash scripts, which are natively supported on Linux/macOS.
  • Explicitly mention cross-platform compatibility for the PowerShell scripts, or provide installation guidance for PowerShell Core on Linux/macOS.
  • Include sample commands for querying Azure Resource Graph using Azure CLI or REST API.
  • Clarify any platform-specific requirements for running the provided scripts and tools.
  • Add notes or sections highlighting how Linux/macOS users can perform the same tasks.
GitHub Create Pull Request
Security Hypervisor security on the Azure fleet - Azure Security ...blob/main/articles/security/fundamentals/hypervisor.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows technologies, specifically Hyper-V, with no mention of Linux-based hypervisors or examples relevant to Linux/macOS users. All terminology, security mechanisms, and references are centered on Windows tools and patterns, creating a Windows-centric perspective and omitting Linux equivalents.
Recommendations
  • Add context about Azure's support for Linux-based VMs and how hypervisor security applies to them.
  • Include references to Linux virtualization technologies (e.g., KVM, Xen) and clarify how Azure's hypervisor interacts with non-Windows guests.
  • Provide examples or explanations relevant to Linux/macOS administrators, such as security boundaries and mitigations from their perspective.
  • Discuss any differences in security assurance processes for Linux guests and how they are threat modeled or protected.
GitHub Create Pull Request
Security Azure information system components and boundaries ...les/security/fundamentals/infrastructure-components.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows Firewall as the default security tool on Azure VMs and describing the host operating system as a customized version of Windows Server. There are no mentions of Linux equivalents (such as iptables/firewalld) or examples for Linux-based VMs, nor is there discussion of Linux-specific management or security patterns. The narrative assumes Windows as the primary or sole operating system, with no parity for Linux users.
Recommendations
  • Explicitly mention support for Linux-based VMs in Azure and describe how network security is handled (e.g., using iptables, firewalld, or ufw).
  • Provide examples or descriptions of how Linux VM boundaries and firewall rules are managed in Azure.
  • Clarify whether the described architecture and management practices apply equally to Linux-based VMs, or note any differences.
  • Include references to Linux operating system images and their hardening/optimization processes in Azure.
  • Avoid presenting Windows tools and patterns as the default or only option; ensure Linux equivalents are given equal prominence.
GitHub Create Pull Request
Security Design secure applications on Microsoft Azure ...s/blob/main/articles/security/develop/secure-design.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. It references the Microsoft Security Development Lifecycle (SDL) with a link to a Windows-specific MSDN page, mentions remote PowerShell access to Azure management interfaces, and generally presents Microsoft-centric tools and patterns (such as Entra ID, Key Vault, and .NET) without offering Linux/macOS equivalents or examples. Windows terminology and tools are mentioned first or exclusively in several sections, and there is a lack of explicit Linux/macOS command-line or tool guidance.
Recommendations
  • Include Linux/macOS-specific examples and workflows alongside Windows ones, especially for Azure management (e.g., Azure CLI, Bash scripts).
  • Reference cross-platform SDKs and tools more explicitly, and provide links to Linux/macOS installation guides.
  • When discussing authentication and management interfaces, mention alternatives to PowerShell (such as Azure CLI, REST API, or Bash scripts) and provide usage examples.
  • Balance references to .NET and Visual Studio with examples for Java, Python, Node.js, and editors like VS Code on Linux/macOS.
  • Review links and references to ensure they are not Windows/MSDN-centric when cross-platform alternatives exist.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →