Security
116
Total Pages
38
Linux-Friendly Pages
78
Pages with Bias
67.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
380 issues found
Showing 151-175 of 380 flagged pages
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-session-management.md
...ity/develop/threat-modeling-tool-session-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-centric technologies and patterns, such as ASP.NET, ADFS, web.config, and PowerShell, with all code/configuration examples using Windows-specific frameworks and tools. There is no mention of Linux equivalents, cross-platform frameworks, or alternative approaches for non-Windows environments. This creates a strong Windows bias and leaves Linux users without guidance for session management and threat mitigation.
Recommendations
- Include examples for Linux-based web frameworks (e.g., Django, Flask, Node.js/Express, Java/Spring) alongside ASP.NET examples.
- Provide configuration and code samples for session management, secure cookies, and CSRF mitigation in Linux environments (e.g., Nginx/Apache config, Python, Node.js, Java).
- Mention cross-platform identity providers and logout patterns, such as OAuth2/OpenID Connect implementations in non-.NET stacks.
- Replace or supplement PowerShell commands with bash/shell equivalents where possible, or provide REST API alternatives.
- Reference Linux-specific documentation and best practices for session security and cookie handling.
- Clearly indicate when a mitigation is Windows/.NET-specific and offer links or guidance for other platforms.
Create Pull Request
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-cryptography.md
.../security/develop/threat-modeling-tool-cryptography.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a strong Windows bias, with Windows-specific technologies (CNG, CAPI, Win32/64, BitLocker, TPM on Windows IoT Core, SSIS, SQL Server features) mentioned exclusively or before alternatives. Code examples and recommendations focus on .NET and Windows APIs, with little to no mention of Linux equivalents (such as OpenSSL, dm-crypt, LUKS, Linux TPM tools, or Linux database encryption). Apple and Java are briefly mentioned for random number generation, but Linux is largely absent from cryptographic guidance and examples.
Recommendations
- Add Linux-specific cryptographic tool recommendations (e.g., OpenSSL, GnuPG, dm-crypt/LUKS for disk encryption, Linux TPM tools).
- Provide code examples for Linux environments (e.g., Python/openssl for key generation, bash commands for random number generation, Linux database encryption features).
- Mention Linux alternatives to Windows technologies (e.g., LUKS instead of BitLocker, OpenSSL instead of CNG/CAPI, Linux kernel crypto APIs).
- Include references to cross-platform libraries (e.g., libsodium, OpenSSL, pycryptodome) and how to use them on Linux.
- Ensure parity in IoT device security guidance by referencing Linux-based IoT OSes and their TPM support.
- Balance .NET/.Windows API references with equivalent Linux/Unix APIs or libraries.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/antimalware-code-samples.md
...cles/security/fundamentals/antimalware-code-samples.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides PowerShell code samples and Windows-centric configuration patterns for enabling and configuring Microsoft Antimalware on Azure services. All examples use PowerShell cmdlets, reference Windows file paths (e.g., C:\), and configuration formats (XML) typical of Windows environments. There is no mention of Linux equivalents, Bash/CLI examples, or guidance for Linux-based VMs or environments, despite Azure supporting both Windows and Linux workloads.
Recommendations
- Add equivalent Bash/Azure CLI examples for deploying and configuring Antimalware on Linux-based Azure VMs and services.
- Clarify whether Microsoft Antimalware is available for Linux workloads, and if not, suggest alternative solutions (such as Microsoft Defender for Endpoint for Linux).
- Include documentation or links for configuring antimalware or endpoint protection on Linux VMs in Azure.
- Avoid hardcoding Windows file paths in examples; provide cross-platform alternatives or note differences.
- Present Linux and Windows instructions side-by-side or in parallel sections to improve parity and accessibility for all users.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-input-validation.md
...urity/develop/threat-modeling-tool-input-validation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. Examples, configuration instructions, and references are almost exclusively for Windows-centric technologies (e.g., .NET, IIS, MSXML, web.config, C#, ASP.NET, WCF). Linux and cross-platform equivalents are missing or only briefly mentioned (e.g., Apple NSXMLParser). Windows tools and patterns (IIS, web.config, MSXML, .NET APIs) are presented first and often exclusively, with no parity for Linux/Unix environments (e.g., Apache/Nginx config, Python/Java code, Linux file validation tools).
Recommendations
- Add equivalent Linux/Unix examples for configuration (e.g., setting HTTP headers in Apache/Nginx, disabling XSLT scripting in libxslt, XML entity resolution in Python/Java libraries).
- Provide code samples in languages commonly used on Linux (Python, Java, Node.js, Go) alongside C#/.NET.
- Reference Linux tools and patterns (e.g., ClamAV for file scanning, Linux file signature validation, SELinux/AppArmor for file upload controls).
- Include instructions for cross-platform frameworks (e.g., Flask/Django, Spring, Express) for input validation, output encoding, and safe redirects.
- Mention how to configure security headers and validation in Linux web servers (Apache, Nginx) and cloud-native environments.
- Balance references and links to include non-Windows documentation and best practices.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/secure-design.md
...s/blob/main/articles/security/develop/secure-design.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Microsoft-centric tools, services, and patterns throughout, such as the Security Development Lifecycle (SDL), PowerShell, and Windows-specific links. Examples and guidance are almost exclusively oriented toward Microsoft technologies, with little to no mention of Linux equivalents, open-source alternatives, or cross-platform best practices. Windows terminology and tools are presented first or exclusively, and there is a lack of Linux-specific examples or guidance for Azure security practices.
Recommendations
- Include Linux-specific security practices and examples for Azure, such as using SSH, Linux-based identity management, and open-source security tools.
- Provide parity in tool recommendations, e.g., mention Bash, Linux CLI, and cross-platform SDKs alongside PowerShell.
- Reference open-source threat modeling tools and frameworks in addition to Microsoft SDL Threat Modeling Tool.
- Add links to documentation for securing Linux VMs and applications on Azure, including guidance for SELinux, AppArmor, and Linux firewall configuration.
- Ensure that examples and code snippets are provided for both Windows and Linux environments, especially for authentication, logging, and key management.
- Highlight Azure services and features that are platform-agnostic, and clarify when guidance applies equally to Linux and Windows.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-authentication.md
...ecurity/develop/threat-modeling-tool-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows authentication is recommended as the default for SQL Server connections, and Windows-based authentication is consistently listed before other options. Windows-specific tools and terminology (e.g., Kerberos, Windows Server certificate service, MakeCert.exe, MSMQ, WCF, ADFS) are referenced without Linux or cross-platform equivalents. There are no Linux-specific examples or guidance, and no mention of Linux authentication patterns or tools. Code/configuration examples (e.g., WCF, MSMQ) are Windows/.NET-centric, with no parity for Linux environments.
Recommendations
- For every mention of Windows Authentication, add equivalent guidance for Linux environments (e.g., Kerberos on Linux, SQL authentication, or integration with Linux-based identity providers).
- When listing authentication mechanisms, avoid always placing Windows-based options first; instead, order them neutrally or by relevance to cross-platform scenarios.
- Where Windows tools (e.g., MakeCert.exe, Windows Server certificate service) are mentioned, provide Linux alternatives (e.g., OpenSSL, Let's Encrypt, Linux PKI guidance).
- Include Linux-specific or cross-platform code/configuration examples, especially for authentication to SQL Server, certificate management, and service authentication.
- For WCF/MSMQ and other .NET/Windows-specific technologies, either provide Linux/.NET Core equivalents or clearly indicate platform limitations.
- Reference Linux documentation or community resources where appropriate, especially for open-source or cross-platform authentication solutions.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/azure-marketplace-images.md
...cles/security/fundamentals/azure-marketplace-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation presents recommendations for both Linux and Windows images, but there is evidence of Windows bias. Some security checks under the 'Linux and open source OS images' section reference Windows Server roles and features, which are not applicable to Linux. Windows-specific tools like BitLocker are mentioned for Windows images, while Linux equivalents (e.g., dm-crypt/LUKS) are not referenced. Additionally, certain recommendations (e.g., auto-update for security patches) are detailed for Windows but lack Linux-specific guidance or examples. The order of presentation sometimes places Windows concepts before Linux ones, and some Linux recommendations are less detailed or lack parity with Windows examples.
Recommendations
- Remove references to Windows Server roles and features from the Linux checklist, or clarify that these are Windows-specific.
- Add Linux equivalents for Windows-specific tools, such as recommending dm-crypt/LUKS for disk encryption.
- Provide Linux-specific guidance for auto-updating security patches (e.g., using unattended-upgrades or dnf-automatic).
- Ensure that recommendations for both platforms are equally detailed and include platform-appropriate examples.
- Review the order and phrasing to avoid implying Windows-first approaches in sections meant for Linux.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/data-encryption-best-practices.md
...ecurity/fundamentals/data-encryption-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-centric concepts (e.g., privileged access workstation, Microsoft PAW security model) and tools without mentioning Linux equivalents or alternatives. There are no examples or guidance for Linux-based secure workstations, endpoint protection, or key management workflows. The documentation assumes familiarity with Microsoft/Windows paradigms and omits Linux-specific best practices or tooling.
Recommendations
- Include examples and guidance for securing Linux workstations, such as using hardened Linux admin hosts, SSH best practices, and Linux endpoint protection tools.
- Reference cross-platform key management workflows, including CLI examples for both Windows (PowerShell) and Linux (Bash/Azure CLI).
- Mention Linux equivalents to privileged access workstations, such as using dedicated Linux admin VMs with strict access controls.
- Provide parity in endpoint protection recommendations, including links to Linux security solutions (e.g., SELinux, AppArmor, Linux antivirus).
- Ensure that all best practices are presented in a cross-platform manner, with explicit notes for both Windows and Linux environments.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-configuration-management.md
...velop/threat-modeling-tool-configuration-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. Most configuration and code examples are specific to Windows technologies (ASP.NET, IIS, Web.config, WCF, BitLocker, Windows Firewall, Windows Azure), with little or no mention of Linux equivalents. There are no examples for Linux-based web servers (e.g., Apache, Nginx), Linux firewalls (e.g., iptables, ufw), or disk encryption tools (e.g., LUKS, dm-crypt). Windows-specific tools and patterns (BitLocker, Windows Firewall, IIS, web.config) are referenced exclusively or before any cross-platform alternatives. Linux scenarios and commands are missing, making the documentation less useful for non-Windows environments.
Recommendations
- Provide equivalent examples for Linux environments, such as configuring HTTP headers in Apache (using .htaccess) or Nginx (using server blocks), and using iptables or ufw for firewall configuration.
- Include Linux disk encryption options (e.g., LUKS, dm-crypt) alongside BitLocker for IoT and gateway devices.
- Add cross-platform code/configuration samples for CORS, X-Frame-Options, and X-Content-Type-Options headers, showing how to set these in popular Linux web servers.
- Reference Linux and open-source alternatives where Windows-specific tools are mentioned (e.g., mention SELinux/AppArmor for endpoint security, and alternatives to Azure Key Vault such as HashiCorp Vault).
- Balance the order of presentation so that Windows and Linux options are given equal prominence, or group platform-specific instructions under clearly labeled sections.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/encryption-overview.md
.../articles/security/fundamentals/encryption-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific technologies (e.g., SMB 3.0, Windows Server versions) and mentions them exclusively or before any Linux equivalents. There are no examples or explicit mentions of Linux tools, commands, or patterns for encryption, VPN, or file sharing. The documentation does not provide parity in examples or guidance for Linux users, especially in sections discussing SMB encryption and VPN connectivity.
Recommendations
- Add Linux-specific examples and references for encryption, VPN, and file sharing (e.g., mention NFS encryption, Linux SMB clients, OpenVPN/IPsec setup on Linux).
- When discussing SMB encryption, include information about Linux support (e.g., Samba client/server encryption capabilities) and how to access Azure Files from Linux.
- Provide cross-platform command-line examples (e.g., Bash, Azure CLI on Linux) alongside any Windows/PowerShell examples.
- Explicitly mention Linux compatibility and configuration steps for Azure VPN gateways and point-to-site/site-to-site VPNs.
- Ensure that references to operating systems and tools are balanced, mentioning both Windows and Linux where applicable.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/management.md
...blob/main/articles/security/fundamentals/management.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias throughout. Windows-specific tools (AppLocker, Hyper-V, Windows Firewall, Group Policy Objects, BitLocker, Microsoft Management Console, Windows PowerShell) are referenced exclusively and repeatedly, with no mention of Linux equivalents or cross-platform alternatives. All examples and recommendations, including hardening, management, and remote access, are focused on Windows environments. There is no guidance for Linux-based management workstations, nor are Linux security tools, firewall configurations, or command-line interfaces discussed.
Recommendations
- Add equivalent Linux examples for workstation hardening, such as using SELinux, AppArmor, or systemd-hardened services.
- Include Linux firewall configuration guidance (e.g., iptables, nftables, ufw) alongside Windows Firewall.
- Mention Linux-based remote management tools (e.g., SSH, OpenVPN, WireGuard) and secure configuration practices.
- Provide examples of using Azure CLI on Linux and macOS, not just Windows PowerShell.
- Reference Linux authentication and auditing mechanisms (e.g., sudo, PAM, auditd) where appropriate.
- Discuss cross-platform virtualization options (e.g., KVM, VirtualBox) in addition to Hyper-V.
- Ensure that recommendations for certificate management, patching, and endpoint protection include Linux-specific solutions.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-auditing-and-logging.md
...y/develop/threat-modeling-tool-auditing-and-logging.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (e.g., Windows ACLs, WCF/.NET configuration), providing examples only for Windows technologies (WCF), and omitting Linux equivalents or examples (such as Linux file permissions, log rotation tools, or syslog configuration). Windows terminology and tools are mentioned exclusively or before any cross-platform alternatives, and there is a lack of parity for Linux-based environments.
Recommendations
- Include Linux equivalents for access control, such as examples using chmod, chown, and setfacl for log file permissions.
- Provide log rotation examples for Linux (e.g., logrotate configuration) alongside the Windows explanations.
- Add examples for auditing and logging in Linux environments, such as syslog, auditd, or journald configuration.
- Reference cross-platform or open-source logging frameworks (e.g., Serilog, ELK stack) where appropriate.
- When discussing WCF/.NET, mention alternatives for Linux (e.g., gRPC, REST APIs with logging middleware) and provide example configurations.
- Ensure that recommendations and steps are not solely focused on Windows technologies, and explicitly address both Windows and Linux environments.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-71610151.md
...rity/develop/threat-modeling-tool-releases-71610151.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows as the supported operating system and requires the .NET Framework, which is primarily a Windows technology. There are no mentions of Linux or cross-platform support, nor are there any Linux-specific instructions, examples, or requirements. The download and usage instructions implicitly assume a Windows environment.
Recommendations
- Explicitly state whether Linux or macOS are supported or not. If unsupported, consider providing rationale or alternatives.
- If possible, provide instructions for running the tool on Linux (e.g., via Wine, Mono, or .NET Core if applicable).
- Include Linux-specific system requirements and installation steps if cross-platform support is available.
- Mention any equivalent threat modeling tools available for Linux users if this tool is Windows-only.
- Ensure future documentation includes parity in examples and troubleshooting for non-Windows platforms.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/identity-management-overview.md
.../security/fundamentals/identity-management-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric technologies and patterns (Active Directory, Windows Hello, IIS, AD FS) without mentioning Linux equivalents or alternatives. Examples and terminology are oriented toward Windows environments, and there is a lack of guidance for Linux-based identity management, authentication, or device registration scenarios.
Recommendations
- Include examples and guidance for integrating Linux-based systems with Microsoft Entra ID, such as using SSSD, Kerberos, or LDAP for authentication.
- Mention Linux-compatible authentication methods (e.g., PAM modules, FIDO2 keys on Linux, certificate-based authentication for Linux clients).
- Provide instructions or references for registering and managing Linux devices with Microsoft Entra ID.
- When discussing hybrid identity, reference how Linux servers or non-Windows systems can participate or be managed.
- Balance references to Windows-specific tools (e.g., Windows Hello, IIS, AD FS) with Linux alternatives (e.g., Apache, NGINX, Linux desktop authentication).
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/log-audit.md
.../blob/main/articles/security/fundamentals/log-audit.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows event logs and tools before Linux equivalents, and by providing more detail about Windows logging mechanisms. Linux logging (Syslog) is mentioned only as an alternative, with less explanation and no specific Linux tooling or command-line examples. There are no Linux-specific examples or instructions, and Windows tools (such as Azure Diagnostics for Windows Event Log) are referenced explicitly, while Linux integration is only briefly noted.
Recommendations
- Provide Linux-specific examples for collecting and analyzing logs, such as using Syslog, journald, or auditd.
- Include equivalent Linux command-line instructions or tooling references alongside Windows examples.
- Ensure that Linux logging mechanisms are described with equal detail and prominence as Windows Event Log.
- Mention cross-platform tools and agents (e.g., Azure Monitor Agent) with clear instructions for both Windows and Linux.
- Avoid listing Windows tools or patterns first; alternate the order or present both platforms together.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/service-fabric-best-practices.md
...security/fundamentals/service-fabric-best-practices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: it repeatedly references Windows-specific tools (such as PowerShell and Windows Server certificate services), prioritizes Windows scenarios and terminology (e.g., standalone Windows clusters, Windows security), and omits Linux-specific guidance or examples. There are no instructions or references for Linux-based Service Fabric clusters, nor are Linux equivalents for deployment, certificate management, or security configuration mentioned.
Recommendations
- Add explicit guidance and examples for deploying and securing Service Fabric clusters on Linux, including use of Linux-native tools (e.g., Bash scripts, OpenSSL).
- Provide parity in documentation for Linux environments, such as instructions for configuring certificates using Linux utilities and managing clusters with Linux command-line tools.
- Reference Linux security mechanisms and patterns (e.g., Linux user/group management, SELinux/AppArmor, SSH for remote access) alongside Windows-specific recommendations.
- Include links to relevant Linux documentation and resources for Service Fabric where available.
- When listing best practices or scenarios, present both Windows and Linux options, or clarify which practices are platform-specific.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/iaas.md
...-docs/blob/main/articles/security/fundamentals/iaas.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and terminology (e.g., PowerShell cmdlets, Windows Defender, WSUS) are referenced more frequently and often before Linux equivalents. Many examples and instructions (such as disk encryption, backup, and key management) use Windows-centric tools or PowerShell commands without providing Linux CLI or cross-platform alternatives. Some sections (e.g., monitoring, diagnostics, antimalware) mention Windows-specific solutions or extensions first, and Linux options are either mentioned later or omitted. There is a lack of parity in examples and actionable guidance for Linux users.
Recommendations
- Provide Linux-specific examples and commands alongside Windows ones, such as Bash/CLI equivalents for PowerShell cmdlets.
- Mention Linux tools and solutions (e.g., ClamAV, Linux-native monitoring agents) with equal prominence and detail as Windows tools.
- Ensure that instructions for features like disk encryption, backup, and diagnostics include both Windows and Linux workflows, with links to relevant documentation.
- Avoid using Windows terminology (e.g., WSUS, Windows Update) without clarifying Linux equivalents (e.g., apt/yum/dnf update mechanisms).
- Structure sections so that Windows and Linux guidance are presented in parallel, rather than Windows-first ordering.
- Include cross-platform best practices and highlight any Azure features that work identically for both OS types.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/infrastructure-integrity.md
...cles/security/fundamentals/infrastructure-integrity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and concepts (such as Endpoint Protection anti-virus, Windows administrator accounts, and Windows Fabric platform-management endpoint) without mentioning Linux equivalents or providing Linux-focused examples. There is a lack of parity in describing how infrastructure integrity is maintained for Linux-based systems, and no Linux-specific security or operational patterns are discussed.
Recommendations
- Include examples and descriptions of how virus scans and endpoint protection are handled for Linux-based Azure components, mentioning common Linux anti-virus tools or security agents.
- Discuss the management of Linux administrator/root accounts and how Azure controls access on Linux guest VMs.
- Describe the Linux equivalents of Windows Fabric and platform-management endpoints, or clarify if such management is Windows-only.
- Provide information on ACLs, firewalls, and monitoring agents as they apply to Linux clusters and workloads.
- Ensure that references to operating system features, security controls, and administrative patterns are balanced between Windows and Linux, or explicitly state platform limitations.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/secrets-best-practices.md
...ticles/security/fundamentals/secrets-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns (e.g., Azure PowerShell, Windows-specific SQL Server VM integration), listing Windows-related examples before Linux equivalents, and omitting explicit Linux or cross-platform examples for secret management. Most service-specific links and guidance focus on Azure tools and workflows that are more familiar to Windows users, with little mention of Linux-native approaches or CLI alternatives.
Recommendations
- Include Linux-specific examples and instructions (e.g., Bash, Azure CLI, Linux file permissions) alongside or before Windows/PowerShell examples.
- Reference cross-platform secret management tools and patterns (such as HashiCorp Vault, environment variable management in Linux, or open-source secret scanning tools) where appropriate.
- Ensure service-specific best practices include both Windows and Linux scenarios, especially for automation, credential management, and integration guides.
- Add explicit guidance for Linux users on how to use Azure Key Vault and other Azure services from Linux environments, including sample commands and scripts.
- Balance references to Azure PowerShell with Azure CLI and REST API examples, which are platform-agnostic.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/paas-deployments.md
...ain/articles/security/fundamentals/paas-deployments.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive mention of Windows-centric tools and patterns, such as PowerShell and Microsoft Entra ID, without providing equivalent Linux or cross-platform examples. The article references remote PowerShell interfaces for management and focuses on Microsoft-specific security tooling, omitting Linux-native approaches or CLI examples. There are no Linux-specific security recommendations, nor are open-source alternatives or cross-platform command-line instructions provided. The documentation assumes a Windows-oriented environment and audience, which may hinder Linux users seeking parity.
Recommendations
- Include Linux-specific management and security examples, such as CLI commands using Azure CLI or Bash scripts.
- Provide cross-platform instructions for tasks currently described only in terms of Windows tools (e.g., remote PowerShell).
- Mention open-source or Linux-native alternatives for identity management, monitoring, and key management where applicable.
- Ensure that examples and best practices are presented in a platform-neutral way, or explicitly offer both Windows and Linux approaches side by side.
- Reference documentation for Linux integration with Azure services, such as using SSH, Linux-based authentication, and Linux-compatible monitoring agents.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/feature-availability.md
...articles/security/fundamentals/feature-availability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is the only command-line example or tool mentioned for administration and configuration tasks (especially for Azure Information Protection and Azure Attestation), with no mention of Bash, CLI, or Linux-native alternatives. Windows-centric tools and patterns (such as PowerShell for RMS service administration and AIP UL client bulk operations) are referenced exclusively. There is no parity in examples or instructions for Linux users, and Windows/PowerShell approaches are presented as the default or only option.
Recommendations
- Provide equivalent examples and instructions using Azure CLI, Bash, or other Linux-native tools alongside PowerShell for all administrative and configuration tasks.
- Explicitly mention Linux support and provide links to Linux-specific documentation where available.
- For each feature or service, clarify platform compatibility and offer step-by-step guides for both Windows and Linux environments.
- Where PowerShell is referenced, add notes or sections for Linux users, including installation and usage of PowerShell Core on Linux, or alternatives using Azure CLI.
- Review all tables and feature lists to ensure Linux tools and workflows are represented equally and not omitted.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/management-monitoring-overview.md
...ecurity/fundamentals/management-monitoring-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page generally maintains a cross-platform tone, referencing both Windows and Linux in several services (notably Azure Update Manager and Azure Automation). However, there is a subtle Windows bias: PowerShell is mentioned as a primary automation tool, with no equivalent Bash or Linux shell examples. Windows-specific features like 'Hotpatching' are highlighted, while Linux equivalents are not described. In Azure Automation, PowerShell is listed before Python, and Windows-centric configuration management (DSC) is referenced without mentioning Linux alternatives. No explicit Linux command-line or tool examples are provided, and Windows terminology (e.g., registry, services) appears in change tracking without Linux parallels.
Recommendations
- Provide Linux-specific examples and tools alongside Windows ones, such as Bash scripts or Linux shell automation in Azure Automation.
- When listing automation languages, alternate or balance the order (e.g., 'Python and PowerShell runbooks') and mention cross-platform scripting.
- Describe Linux equivalents for Windows-specific features (e.g., mention how hotpatching or update management works for Linux VMs).
- In configuration management, reference Linux-native tools (such as Ansible, Chef, or native Linux DSC support) where appropriate.
- For change tracking and inventory, include Linux concepts (e.g., file system changes, package management) alongside Windows registry/services.
- Add explicit Linux command-line examples or references in relevant sections to demonstrate parity.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/technical-capabilities.md
...ticles/security/fundamentals/technical-capabilities.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Windows terminology (e.g., 'Active Directory', 'Windows error reporting', 'Windows or Linux server machines') is used as the default or primary reference point. Windows tools and concepts (Active Directory, Windows error reporting, Microsoft Accounts) are mentioned first or exclusively, with Linux equivalents rarely discussed or only referenced in passing. There is a lack of explicit Linux/POSIX command-line examples, and most security and management scenarios are described in a Windows-centric context.
Recommendations
- Include explicit Linux-focused examples and scenarios alongside Windows ones, such as using Linux authentication mechanisms, Linux-based monitoring tools, and Linux command-line instructions for Azure management.
- When discussing identity management, clarify how Microsoft Entra ID integrates with Linux systems (e.g., PAM, LDAP, SSSD) and provide Linux-specific configuration guidance.
- For antimalware and backup solutions, list and link to supported Linux agents and describe their installation and usage.
- In sections referencing Windows error reporting or Windows-specific features, add equivalent Linux mechanisms (e.g., syslog, auditd, journald) and how Azure integrates with them.
- Ensure that references to 'Windows or Linux' are balanced, and avoid defaulting to Windows terminology unless both platforms are equally supported.
- Add Linux command-line and scripting examples (e.g., Bash, CLI, Azure CLI) wherever PowerShell or Windows GUI instructions are mentioned.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/identity-management-best-practices.md
...ity/fundamentals/identity-management-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It frequently references Windows-centric tools and patterns (e.g., Active Directory, Windows Server agents, Windows Hello for Business, Privileged Access Workstations), and omits Linux-specific equivalents or examples. Where platform-specific guidance is given (e.g., admin workstations, password protection agents), Windows solutions are mentioned exclusively or first, with no mention of Linux alternatives. There are no examples or instructions for Linux-based identity management, authentication, or privileged access scenarios.
Recommendations
- Add Linux-specific examples for identity management, authentication, and privileged access (e.g., using Azure CLI on Linux, configuring MFA for Linux-based admin workstations).
- Reference cross-platform tools and workflows (such as Azure CLI, REST API, or Terraform) alongside Windows-specific tools like PowerShell.
- When discussing admin workstations and privileged access, include recommendations for securing Linux-based systems (e.g., using Linux security hardening, SSH key management, Linux equivalents to PAW).
- Mention Linux-compatible password protection agents or provide guidance for extending password policies to Linux systems.
- Ensure that platform-agnostic approaches (e.g., SSO, RBAC, Conditional Access) are illustrated with examples for both Windows and Linux environments.
Security
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/ransomware-detect-respond.md
...les/security/fundamentals/ransomware-detect-respond.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts (such as Security Event log and PowerShell Operational logs) without mentioning Linux equivalents. It also links to Defender for Endpoint documentation that is Windows-focused and omits examples or guidance for Linux-based Azure VMs. The language and tooling recommendations are oriented toward Windows environments, with no parity for Linux detection, logging, or response patterns.
Recommendations
- Add explicit references to Linux audit and syslog equivalents when discussing event log clearing and monitoring (e.g., /var/log/auth.log, /var/log/audit/audit.log).
- Provide examples of ransomware detection and response for Linux-based Azure VMs, including relevant commands and tools (such as auditd, fail2ban, or Linux EDR integrations).
- When mentioning PowerShell logs, also mention bash/zsh history or Linux shell auditing as relevant for Linux environments.
- Ensure that links and references to Defender for Endpoint or XDR tools clarify Linux support and provide links to Linux-specific documentation.
- Balance recommendations by including both Windows and Linux perspectives in detection, containment, and recovery steps.