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 76-90 of 90 flagged pages
Security
Azure security logging and auditing | Microsoft Docs
.../blob/main/articles/security/fundamentals/log-audit.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows tools and patterns (e.g., Windows Event Log service) are mentioned before Linux equivalents (Syslog), and examples or integration details are more explicit for Windows (e.g., referencing Azure Diagnostics for Windows). Linux logging is referenced but lacks equivalent detail or examples, and no Linux-specific integration steps or tools are highlighted.
Recommendations
- Provide Linux-specific examples for log collection and integration, such as configuring Syslog forwarding or using the Azure Monitor agent on Linux.
- Ensure parity in describing both Windows and Linux logging mechanisms, including step-by-step instructions or links for Linux users.
- Mention Linux tools (e.g., rsyslog, auditd) alongside Windows Event Log, and clarify how Azure integrates with these.
- Balance the order of presentation so that Linux and Windows are treated equally, or alternate which platform is mentioned first.
Create Pull Request
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, particularly in the 'SMB encryption' section, which exclusively references Windows versions and tools (Windows Server, Windows 8/8.1/10) without mentioning Linux or macOS SMB clients or their encryption capabilities. Additionally, Windows tools and terminology appear first or exclusively in some areas, and there are no Linux/macOS-specific examples or guidance for encryption-related tasks.
Recommendations
- Add information about SMB encryption support for Linux and macOS clients, including compatible versions and configuration steps.
- Provide cross-platform examples (Linux, macOS) for interacting with Azure services securely, such as using OpenSSL, curl, or other common tools for TLS/HTTPS connections.
- Include references to Linux and macOS VPN clients and their compatibility with Azure VPN gateways (e.g., strongSwan, OpenVPN, etc.).
- Ensure that encryption features and instructions are described in a platform-neutral way, or with parallel examples for major operating systems.
Security
Azure identity management security overview
.../security/fundamentals/identity-management-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-centric concepts and tools (Active Directory, AD DS, AD FS, Windows Hello for Business) before or instead of Linux/macOS equivalents. The security principals link points to Windows documentation, and hybrid identity management is described primarily in terms of on-premises Active Directory. No explicit Linux/macOS examples or tools are mentioned, and cross-platform scenarios are not highlighted.
Recommendations
- Include references to Linux/macOS identity management scenarios, such as integration with LDAP or other non-Windows directory services.
- Provide examples or documentation links for configuring Azure identity management features from Linux/macOS environments (e.g., using Azure CLI, REST APIs, or cross-platform tools).
- Mention cross-platform authentication methods and device registration options, clarifying support for non-Windows devices.
- Balance references to Windows-specific tools (like AD DS, AD FS, Windows Hello) with equivalent or alternative solutions for Linux/macOS.
- Link to documentation on managing Azure identities from Linux/macOS endpoints, including device registration and SSO.
Security
Azure security management and monitoring overview
...ecurity/fundamentals/management-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation generally maintains cross-platform neutrality, but there are subtle Windows biases. Azure Automation highlights PowerShell before Python, and features like 'Hotpatching' in Azure Update Manager are Windows-only. Windows terminology and tools (PowerShell, Windows Server) are mentioned before or more prominently than Linux equivalents, and some features are described as exclusive to Windows without equal Linux alternatives. However, most services are described as supporting both Windows and Linux, and no critical functionality is documented as Windows-only.
Recommendations
- Explicitly mention Linux support and provide Linux-specific examples or notes where relevant (e.g., Azure Automation runbooks, Update Manager hotpatching).
- When listing scripting or automation options, present Python and PowerShell equally, or note cross-platform compatibility.
- For features exclusive to Windows (e.g., hotpatching), clarify Linux alternatives or limitations.
- Add Linux-first or Linux-parity examples in sections that currently mention Windows tools or features first.
- Include links to Linux documentation or guides alongside Windows-focused resources.
Security
Azure operational security checklist| Microsoft Docs
...rticles/security/fundamentals/operational-checklist.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Minor Missing Linux Example
Summary
The documentation page shows minor Windows bias, most notably in the Data Protection & Storage section, where SMB (Server Message Block) 3.0 is referenced as a transport-level encryption protocol for Azure File Shares, linking to a Windows-specific documentation page. The mention of Azure Disk Encryption for Linux VMs and Windows VMs is present, but the link for both points to the Linux documentation, which could confuse users. There are no explicit Linux/macOS command-line examples, nor are Linux-specific tools or patterns discussed. The overall checklist is generic and Azure-focused, but Windows technologies are referenced first or exclusively in some cases.
Recommendations
- When mentioning SMB for Azure File Shares, also reference NFS (Network File System) for Linux users and provide a link to relevant Azure/NFS documentation.
- Ensure that links for Azure Disk Encryption for Linux and Windows VMs point to their respective documentation pages.
- Where platform-specific protocols or tools are mentioned (e.g., SMB), clarify their relevance for both Windows and Linux/macOS environments.
- Consider adding examples or notes for Linux/macOS users where operational procedures may differ.
- Review all links to ensure parity and clarity for both Windows and Linux users.
Security
Best practices for secure PaaS deployments - Microsoft Azure
...ain/articles/security/fundamentals/paas-deployments.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily through the mention of Windows-centric management interfaces (e.g., 'portal/remote PowerShell') and exclusive references to Microsoft tools and platforms. While the content is generally platform-neutral and focuses on Azure services, there are subtle indications that Windows/PowerShell patterns are assumed or prioritized, and Linux/macOS equivalents are not explicitly mentioned or illustrated.
Recommendations
- Explicitly mention and provide examples for Linux/macOS management interfaces (e.g., Azure CLI, Bash, SSH) alongside PowerShell references.
- When discussing remote management, clarify that Azure resources can be managed from any OS using cross-platform tools.
- Include links or brief instructions for using Azure CLI and other non-Windows tools for authentication, monitoring, and deployment tasks.
- Avoid language that implies Windows/PowerShell is the default or preferred method; present alternatives in parallel.
- Add examples or notes for securing PaaS deployments from Linux/macOS environments, especially in sections referencing remote management or automation.
Security
Protection of customer data in Azure
...cles/security/fundamentals/protection-customer-data.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific protocols and tools (such as Windows IPsec and SMB) before mentioning platform-neutral or Linux equivalents. No Linux-specific examples or tools are provided, and Windows terminology appears first in relevant sections. However, the overall content is mostly platform-agnostic and does not prevent Linux/macOS users from understanding or applying the guidance.
Recommendations
- Include Linux-specific protocols and tools (e.g., strongSwan for IPsec, NFS for file sharing) alongside Windows examples.
- Present platform-neutral terminology first, or provide parallel examples for both Windows and Linux.
- Add explicit statements clarifying that Azure supports both Windows and Linux VMs, and that data protection features apply equally.
- Where protocols are mentioned (e.g., IPsec, SMB), note the Linux equivalents and how to configure them in Azure.
Security
Trusted Hardware Identity Management
...y/fundamentals/trusted-hardware-identity-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux instructions for configuring Intel QPL with Trusted Hardware Identity Management, but Windows instructions (including PowerShell and registry edits) are presented before Linux equivalents. Windows-specific tools and patterns (registry, PowerShell) are described in detail, while Linux instructions are more concise. However, Linux examples are present and cover all necessary steps. The rest of the documentation (e.g., AMD collateral, AKS, DCAP library downloads) is either OS-neutral or Linux-first.
Recommendations
- Present Linux and Windows instructions in parallel or alternate their order to avoid implicit prioritization.
- Provide equally detailed step-by-step instructions for both platforms, including troubleshooting tips for Linux.
- Where possible, use OS-neutral language and tools, or clarify platform-specific requirements.
- Add macOS guidance if relevant, or clarify its support status.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific technologies (such as Windows Fabric platform and Windows administrator accounts) and tools (Endpoint Protection anti-virus) without mentioning Linux or cross-platform equivalents. There are no explicit Linux examples or references to Linux-specific security practices, monitoring agents, or anti-virus tools, and Windows terminology is used as the default context for infrastructure management and security.
Recommendations
- Include references to Linux-based Azure infrastructure components and describe how integrity and security are maintained for Linux VMs.
- Mention Linux-compatible anti-virus and endpoint protection tools used in Azure environments, if applicable.
- Clarify whether custom monitoring agents and watchdogs are cross-platform or provide Linux-specific details.
- Balance references to Windows Fabric with information about Linux orchestration or management platforms in Azure.
- Add examples or notes about administrator account management and authentication for Linux guest VMs.
Security
Trusted Hardware Identity Management
...y/fundamentals/trusted-hardware-identity-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux instructions for configuring Intel QPL with Trusted Hardware Identity Management, but Windows instructions (including PowerShell and registry edits) are presented first and in greater detail. Linux instructions are present and clear, but Windows examples and tools (such as PowerShell and registry keys) are described before their Linux equivalents. The rest of the documentation, especially for AMD collateral and Kubernetes, is platform-neutral or Linux-focused.
Recommendations
- Present Linux and Windows instructions in parallel or alternate which comes first to avoid implicit prioritization.
- Where possible, use cross-platform commands and tools, or provide equal detail for both platforms.
- Add explicit notes that both Windows and Linux are supported, and clarify any platform-specific limitations.
- Consider grouping platform-specific instructions under clear headings so users can quickly find their OS.
- Ensure that Linux instructions are as detailed as Windows instructions (e.g., permissions, service management).
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, but there are subtle signs of Windows bias. The only explicit mention of client OSes/tools is in the SMB encryption section, which lists Windows versions exclusively and does not mention Linux or macOS SMB support. Windows tools and terminology (e.g., SMB 3.0, Windows Server, Windows desktop) are referenced without Linux/macOS equivalents or examples. Additionally, Windows is mentioned first and exclusively in the context of SMB encryption, which may suggest a Windows-centric perspective.
Recommendations
- Add references to Linux and macOS support for SMB encryption, including compatible versions and configuration guides.
- Where OS-specific features or protocols are discussed (e.g., SMB, VPN clients), provide parity by mentioning Linux/macOS tools (e.g., smbclient, OpenVPN, strongSwan) and their compatibility.
- Include example commands or links for Linux/macOS where relevant, especially in sections discussing client-side encryption, VPN, and file sharing.
- Review sections for implicit assumptions about Windows environments and clarify cross-platform applicability.
Security
Azure operational security checklist| Microsoft Docs
...rticles/security/fundamentals/operational-checklist.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias, primarily through the mention of Windows-specific technologies (e.g., SMB 3.0) and links to Windows documentation before Linux equivalents. While Azure Disk Encryption for Linux VMs is mentioned, the link for both Linux and Windows VMs points to the Linux documentation, which could be confusing. There are no explicit Linux or macOS command-line examples, and Windows-centric protocols/tools are referenced without Linux alternatives.
Recommendations
- Provide explicit Linux/macOS examples or references where relevant (e.g., mounting Azure File Shares with NFS or SMB on Linux).
- Mention Linux equivalents for Windows-centric protocols/tools (e.g., discuss NFS or CIFS for Linux alongside SMB for Windows).
- Ensure links for Linux and Windows documentation point to their respective pages.
- Include cross-platform command-line examples (e.g., Bash, CLI) in addition to any PowerShell or Windows examples.
- Clarify when recommendations apply to all platforms or provide platform-specific guidance.
Security
Azure identity management security overview
.../security/fundamentals/identity-management-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily through the use of Windows-centric terminology (e.g., Active Directory, AD DS, Windows Hello for Business) and by referencing Windows tools and patterns before their Linux equivalents. The page does not provide Linux/macOS-specific examples or mention cross-platform alternatives for identity management, device registration, or authentication methods. However, most content is conceptual and not task-oriented, so Linux/macOS users are not critically blocked.
Recommendations
- Include explicit references to Linux/macOS compatibility for identity management features, such as SSO, MFA, and device registration.
- Provide examples or links for configuring Microsoft Entra ID features on Linux/macOS endpoints (e.g., device registration, authentication methods).
- Mention cross-platform authentication options (such as FIDO2, certificate-based authentication) in more detail, clarifying their support on non-Windows platforms.
- Add guidance for integrating with non-Windows on-premises directories or identity providers.
- Balance terminology by mentioning alternatives to Windows Hello (e.g., Touch ID, Linux PAM modules) where appropriate.
Security
Azure security management and monitoring overview
...ecurity/fundamentals/management-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is generally cross-platform in its descriptions, but there are subtle signs of Windows bias. Azure Automation highlights PowerShell before Python, and hotpatching is described as a Windows Server-only feature. No explicit Linux/macOS examples or tools are provided, and Windows terminology (PowerShell, registry) appears before or instead of Linux equivalents. The documentation does mention Linux support for Azure Update Manager, but does not provide parity in examples or tool references.
Recommendations
- Provide explicit Linux/macOS examples and workflows alongside Windows ones, especially for automation and update management.
- Mention Bash, shell scripts, and Linux configuration management tools (e.g., Ansible, Chef) in automation sections, not just PowerShell.
- Clarify which features are Windows-only (e.g., hotpatching) and offer Linux alternatives or workarounds.
- Include references to Linux system components (e.g., systemd, cron, package managers) where relevant.
- Ensure examples and tool mentions are balanced or alternate between platforms.
Security
Protection of customer data in Azure
...cles/security/fundamentals/protection-customer-data.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific protocols and tools (e.g., Windows IPsec, SMB) before mentioning platform-agnostic or Linux equivalents in the context of in-transit data protection. No Linux-specific examples or tools are provided, and Windows terminology appears first in relevant sections.
Recommendations
- Include Linux-specific protocols and tools (e.g., Linux IPsec, NFS, SSH) alongside Windows examples when discussing in-transit data protection.
- Present platform-agnostic options first, or provide parallel examples for both Windows and Linux environments.
- Clarify that Azure supports both Windows and Linux VMs and mention relevant security practices for each.
- Add explicit references to Linux-compatible encryption and networking solutions in Azure.