Azure Government
39
Total Pages
18
Linux-Friendly Pages
21
Pages with Bias
53.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
124 issues found
Showing 101-124 of 124 flagged pages
Azure Government
Azure support for export controls
...e-government/documentation-government-overview-itar.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page generally maintains platform neutrality, referencing both Linux and Windows as underlying operating systems for Azure. However, there is a subtle Windows bias in the 'FIPS 140 validated cryptography' section, where Windows-specific FIPS validation is mentioned and linked before Linux equivalents, and the validation program is described in terms of Windows modules. There are no command-line examples or tooling instructions, so no Powershell or CLI bias is present. The documentation does not provide explicit Linux examples or highlight Linux-specific tools for encryption or key management.
Recommendations
- Include explicit references to Linux FIPS 140 validation processes or modules, with links to relevant documentation.
- When describing cryptographic modules and validation, mention both Windows and Linux implementations equally and provide parity in detail.
- If referencing validation programs, include information about how Linux-based Azure infrastructure meets FIPS 140 requirements.
- Add examples or guidance for key management and encryption operations using Linux-native tools or commands, where relevant.
- Ensure that any platform-specific details (such as OS-level cryptography) are presented in parallel for both Windows and Linux.
Create Pull Request
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-jps.md
...re-government/documentation-government-overview-jps.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily in its references to Windows-specific cryptographic modules and authentication solutions. Windows tools and validation programs are mentioned explicitly (e.g., Windows FIPS validation, Windows Hello for Business), and Windows is listed before Linux when describing Azure's underlying operating systems. There are no Linux-specific examples, tools, or patterns provided, and the documentation does not offer parity in describing Linux equivalents for cryptographic validation or authentication solutions.
Recommendations
- Include explicit references to Linux cryptographic modules and their FIPS validation status in Azure environments.
- Provide examples or guidance for Linux-based authentication solutions (e.g., integration with FIDO2, smartcards, or other MFA tools on Linux).
- When listing supported operating systems or technologies, mention Linux and Windows equally, or alternate their order to avoid implicit prioritization.
- Add documentation links or sections for configuring security and compliance features on Linux-based Azure workloads.
- Highlight cross-platform compatibility for key Azure services (e.g., Azure Key Vault, confidential computing) with both Windows and Linux environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-itar.md
...e-government/documentation-government-overview-itar.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page generally avoids OS-specific examples and maintains a neutral tone regarding platform usage. However, there is a subtle Windows bias in the 'FIPS 140 validated cryptography' section, where Windows and Windows-specific validation programs are mentioned before Linux, and links are provided to Windows FIPS validation documentation. Azure's use of both Linux and Windows is acknowledged, but Windows tools and validation are referenced first and in more detail, with no equivalent Linux validation documentation or examples provided.
Recommendations
- Explicitly mention and link to Linux FIPS 140 validation resources, if available, alongside Windows references.
- Provide parity in documentation by describing how FIPS 140 validated cryptographic modules are implemented and validated on Linux within Azure.
- Ensure that any references to OS-specific features, tools, or validation programs are presented in parallel (e.g., 'Windows and Linux FIPS validation programs'), with equal detail and links.
- If examples or operational guidance are given, include both Windows and Linux scenarios to avoid implicit prioritization.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md
...government/documentation-government-developer-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing PowerShell and Visual Studio connectivity options before CLI and Python SDK options, and by specifically highlighting 'Connect with PowerShell' as a quickstart. There is no explicit Linux example or mention of Linux-specific tools, and the ordering of examples may suggest a Windows-first approach.
Recommendations
- Ensure that Linux/CLI examples are given equal prominence by listing 'Connect with CLI' before or alongside 'Connect with PowerShell' in quickstarts.
- Include explicit references to Linux development environments and workflows, such as Bash, VS Code on Linux, or Linux-based automation.
- Add quickstart links or sections for Linux users, such as 'Connect with Bash' or 'Develop on Linux', to demonstrate parity.
- Where PowerShell is mentioned, also mention Bash or other cross-platform shells to avoid implying PowerShell is the default or only option.
- Review other linked documentation (e.g., the PowerShell and CLI guides) to ensure Linux examples are present and up-to-date.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-itar.md
...e-government/documentation-government-overview-itar.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally platform-neutral but exhibits subtle Windows bias in the cryptography/FIPS 140 section, where Windows and Windows-specific validation programs are mentioned before Linux. There is also a reference to 'Azure-specific version of Windows' and the 'Windows FIPS validation program' without equivalent detail for Linux. No command-line examples (PowerShell, Bash, etc.) are present, so there is no overt example bias, but the underlying platform references favor Windows.
Recommendations
- When discussing FIPS 140 validation, provide equal detail about Linux cryptographic modules and their validation status in Azure, not just Windows.
- Reference both Windows and Linux as supported Azure operating systems in parallel, avoiding phrasing that puts Windows first or gives it more prominence.
- If mentioning validation programs or modules, include links or references to Linux equivalents (e.g., OpenSSL FIPS validation in Azure Linux VMs).
- Explicitly state that Azure supports both Linux and Windows for compliance scenarios, and provide parity in technical detail where applicable.
- If future updates add command-line or configuration examples, ensure both PowerShell/Windows and Bash/Linux examples are included.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-jps.md
...re-government/documentation-government-overview-jps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias, particularly in the sections discussing cryptography and authentication. Windows and Windows-specific tools (e.g., Windows FIPS validation, Windows Hello for Business) are mentioned explicitly and often before or instead of Linux equivalents. There are references to Azure being built with both Linux and Windows, but technical details and validation links focus on Windows modules. No Linux-specific examples, tools, or validation references are provided.
Recommendations
- Include explicit references to Linux cryptographic modules and their FIPS 140 validation status in Azure, alongside Windows.
- When discussing authentication (e.g., Windows Hello for Business), mention Linux-compatible alternatives or clarify cross-platform support for FIDO2 and smartcards.
- Provide links to documentation or guidance for configuring security and compliance features on Linux-based Azure VMs and services.
- Ensure that examples and technical details are balanced between Windows and Linux, or are presented in a platform-neutral way where possible.
- If certain features are only available or validated on Windows, clearly state this and provide guidance for Linux users.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-ssms.md
...re-government/documentation-government-connect-ssms.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and does not mention or provide guidance for Linux or cross-platform alternatives. There are no examples or instructions for connecting from Linux environments or using tools available on Linux.
Recommendations
- Include instructions for connecting to Azure Government SQL Server from cross-platform tools such as Azure Data Studio, sqlcmd, or other command-line utilities available on Linux.
- Add a section or examples for Linux and macOS users, detailing how to configure and connect using supported tools.
- Mention the platform limitations of SSMS and suggest alternatives for non-Windows users.
- Ensure parity in documentation by providing equivalent steps and screenshots for Linux/macOS tools where possible.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md
...government/documentation-government-developer-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows a mild Windows bias by listing 'Connect with PowerShell' before 'Connect with CLI' in the Quickstarts section, and by highlighting PowerShell as a primary tool for connecting to Azure Government. There is also a focus on Visual Studio, a Windows-centric IDE, before mentioning cross-platform SDKs. No explicit Linux examples or Linux-specific tools are highlighted, and the ordering subtly prioritizes Windows/PowerShell workflows.
Recommendations
- Reorder the Quickstarts section to list cross-platform tools (CLI, Python SDK) before or alongside PowerShell and Visual Studio.
- Explicitly mention Linux and macOS compatibility for CLI and SDK tools.
- Add links or references to Linux/macOS setup guides for Azure CLI and SDKs.
- Include examples or quickstart links that demonstrate connecting to Azure Government from Linux environments.
- Balance tool mentions by including cross-platform editors (e.g., VS Code) alongside Visual Studio.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-aad-auth-qs.md
...ure-government/documentation-government-aad-auth-qs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and omitting any Linux or cross-platform development environment instructions. All configuration steps and code samples assume use of Visual Studio and ASP.NET Core, with no mention of Linux tools, editors, or deployment patterns. There are no examples or guidance for Linux users.
Recommendations
- Include instructions for setting up and configuring the application using cross-platform tools such as VS Code, JetBrains Rider, or command-line interfaces available on Linux.
- Provide equivalent steps for Linux users, such as editing configuration files and running .NET Core applications using the dotnet CLI.
- Add notes or sections that explicitly mention Linux compatibility and any differences in file paths, environment variables, or deployment steps.
- Demonstrate how to deploy and test the application locally on Linux (e.g., using dotnet run) and how to register applications without relying on Visual Studio.
- Ensure that all code/configuration samples are platform-agnostic or provide both Windows and Linux variants where necessary.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-with-cli.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-with-cli.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of a local Azure CLI installation and mentions the absence of Azure Cloud Shell in Azure Government, but does not provide explicit Linux/macOS installation or usage examples. It also references launching a browser for authentication, which may behave differently on Linux. There is no mention of Linux-specific considerations or alternative authentication flows.
Recommendations
- Add explicit instructions or notes for installing and using Azure CLI on Linux/macOS, including package manager commands (e.g., apt, yum, brew).
- Clarify how the 'az login' browser-based authentication behaves on Linux and provide alternatives (such as device code login) if needed.
- Mention any Linux-specific prerequisites or troubleshooting steps.
- Include screenshots or terminal output examples from Linux environments.
- If possible, provide parity with Cloud Shell by suggesting alternative Linux-compatible shells or containers.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-quickstarts-vm.md
...-government/documentation-government-quickstarts-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively demonstrates the creation of a Windows-based virtual machine ("Data Science Virtual Machine - Windows 2016 CSP") and only describes connecting to the VM via RDP, with no mention of Linux VM options or SSH access. All examples and screenshots are centered around Windows workflows, and there are no Linux or cross-platform alternatives provided.
Recommendations
- Include parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu, CentOS) alongside the Windows example.
- Demonstrate how to connect to a Linux VM using SSH, and provide example commands for different platforms (Windows, macOS, Linux).
- Mention and show how to select Linux images from the Azure Government marketplace.
- Ensure screenshots and step-by-step instructions are not Windows-centric and reflect cross-platform usage.
- Add a section or note about differences in provisioning and connecting to Windows vs. Linux VMs in Azure Government.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-jps.md
...re-government/documentation-government-overview-jps.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a subtle Windows bias, particularly in its references to cryptographic validation and authentication. It repeatedly cites Windows-specific FIPS 140 validation programs and the use of Windows cryptographic modules as the basis for compliance. While it mentions that Azure uses both Linux and Windows, the detailed compliance and validation examples, as well as references to authentication modules, are Windows-centric. There are no Linux-specific examples, tools, or validation pathways described, and Windows is consistently mentioned first or exclusively in technical compliance contexts.
Recommendations
- Include explicit references to Linux-based cryptographic modules and their FIPS 140 validation status within Azure, if available.
- Provide parity in compliance documentation by describing how Linux-based workloads and authentication methods meet CJIS and FIPS 140 requirements.
- Add examples or guidance for Linux administrators (e.g., using OpenSSL or Linux-native tools) in relevant sections, especially where Windows tools or modules are highlighted.
- Clarify whether Azure's compliance and security assurances apply equally to Linux-based services and workloads, and provide links to Linux-specific compliance resources if available.
- Avoid referencing only Windows validation programs; instead, present a balanced view of both Windows and Linux compliance mechanisms.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally covers Azure secure isolation in a cross-platform manner, referencing both Windows and Linux where appropriate. However, there are several instances where Windows technologies, tools, and terminology are mentioned first or exclusively, such as Hyper-V, Windows Firewall, BitLocker, and PowerShell. In some sections, Windows-specific examples or references precede Linux equivalents, and Windows tools (e.g., PowerShell) are listed as primary management interfaces, even when Linux alternatives (Azure CLI, SSH, DM-Crypt) are available. These patterns may create minor friction for Linux/macOS users, though the documentation does ultimately provide Linux parity in most critical areas.
Recommendations
- When listing management tools (e.g., Azure portal, PowerShell, CLI), alternate the order or explicitly mention Linux/macOS compatibility for Azure CLI.
- Where Windows technologies (e.g., BitLocker, Windows Firewall) are referenced, ensure Linux equivalents (e.g., DM-Crypt, iptables/firewalld) are mentioned with equal prominence.
- Provide example commands for both Windows (PowerShell) and Linux (CLI/SSH) when discussing VM provisioning, disk encryption, or network configuration.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
- Where Windows terminology is used (e.g., Host OS as Windows Server), clarify the analogous Linux scenario or note platform-agnostic aspects.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and provides guidance for both Windows and Linux users, especially in VM provisioning, disk encryption, and network isolation. However, there are several instances where Windows terminology, tools, and technologies (such as Hyper-V, Windows Firewall, BitLocker, and Windows Server references) are mentioned first or more extensively than their Linux equivalents. Windows-specific tools and patterns (e.g., Windows Firewall, BitLocker, Hyper-V) are often described in detail, while Linux alternatives (e.g., DM-Crypt, Linux disk encryption, Linux VM provisioning) are referenced but with less depth or after Windows. In some sections, Windows terminology is used as the default, and Windows examples or links are shown before Linux ones.
Recommendations
- Ensure Linux tools and technologies (e.g., DM-Crypt, iptables, SELinux, Linux VM images) are described with equal depth and clarity as Windows equivalents.
- When listing cross-platform features (e.g., disk encryption, VM provisioning), alternate the order or provide Linux examples first in some cases.
- Expand explanations of Linux-specific security features and patterns (e.g., Linux firewall, Linux kernel isolation, Linux audit/logging tools) where Windows tools are discussed.
- Include explicit Linux command-line examples (e.g., Azure CLI, SSH, DM-Crypt usage) alongside or before Windows/PowerShell examples.
- Review terminology to avoid defaulting to Windows-specific language when describing general Azure features.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure secure isolation. However, there is a consistent pattern of mentioning Windows tools, technologies, and patterns first (e.g., Hyper-V, BitLocker, Windows Firewall), and Windows-specific terminology is more prevalent throughout. In a few places, PowerShell is referenced as a primary automation tool, and Windows-centric features are described in greater detail than their Linux equivalents. Linux is supported and referenced, but often appears after Windows or as an addendum.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, or alternate which platform is shown first.
- Where Windows-specific tools (e.g., BitLocker, Windows Firewall, Hyper-V) are mentioned, ensure the Linux equivalents (e.g., dm-crypt, iptables/firewalld, KVM) are also referenced with equal detail, unless the feature is Azure/Windows-only.
- When referencing automation or management tools, include Azure CLI and Bash examples alongside PowerShell.
- Review callout boxes and 'how-to' links to ensure Linux-focused resources are equally visible.
- In tables and summary sections, list Linux and Windows guidance side-by-side, not with Windows first.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Examples
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure secure isolation. However, there are several instances where Windows terminology, tools, and examples are mentioned first or exclusively, such as references to Windows Firewall, BitLocker, Hyper-V, and PowerShell. Linux equivalents are present but sometimes appear after Windows examples or are less detailed. Some sections (e.g., Hypervisor isolation, Drawbridge) are inherently Windows-centric due to Azure's underlying technology, but overall, the guidance is intended for both Windows and Linux users.
Recommendations
- Ensure Linux tools and terminology (e.g., iptables, firewalld, SELinux, DM-Crypt) are mentioned alongside or before Windows equivalents where applicable.
- Provide Linux-first or parallel examples for management tasks (e.g., using Azure CLI and Bash, not just PowerShell).
- Clarify when features or patterns are Windows-only and provide explicit Linux alternatives or guidance.
- Balance references to Windows-specific technologies (e.g., Hyper-V, BitLocker) with Linux equivalents, or note when no direct equivalent exists.
- Where management instructions are given, ensure both Azure CLI and PowerShell are covered equally, with Linux/macOS usage shown.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure secure isolation. However, there are several instances where Windows tools, technologies, and terminology are mentioned first or in greater detail, such as Hyper-V, BitLocker, Windows Firewall, and PowerShell. Examples and references to Windows-specific features (e.g., RDP, Windows Server, Windows Firewall) often precede or are more detailed than their Linux equivalents (e.g., SSH, DM-Crypt). Azure PowerShell is frequently referenced as a management tool, sometimes before Azure CLI. While Linux is supported and mentioned, Windows-centric patterns and terminology are more prominent throughout the document.
Recommendations
- Ensure that Linux and cross-platform examples (e.g., Azure CLI, SSH, DM-Crypt) are presented alongside or before Windows/PowerShell examples where applicable.
- Where Windows tools or terminology are used (e.g., BitLocker, Windows Firewall, PowerShell), provide equivalent Linux references (e.g., DM-Crypt, iptables/firewalld, Azure CLI) with equal detail.
- Explicitly state cross-platform support in sections that discuss VM management, disk encryption, and network isolation.
- Balance the use of Windows-centric terminology with neutral or platform-agnostic language when describing Azure features that apply to both Windows and Linux workloads.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure isolation. However, there is a mild Windows bias in several areas: Windows terminology and technologies (e.g., Hyper-V, Windows Firewall, BitLocker, Windows Server) are mentioned first or exclusively in some technical explanations, and PowerShell is referenced as a primary management tool before Azure CLI. Some examples and technical details (especially in compute isolation and disk encryption) are described with a Windows-first perspective, even when Linux equivalents exist and are supported.
Recommendations
- Ensure Linux tools and patterns (e.g., Azure CLI, SSH, DM-Crypt) are mentioned alongside or before Windows/PowerShell equivalents where both are supported.
- When describing technical architecture (e.g., firewalls, disk encryption), provide equal detail for Linux technologies (e.g., iptables, DM-Crypt) as for Windows ones.
- In management instructions, alternate or parallelize examples for Azure CLI and PowerShell, and clarify when both are supported.
- Review sections that reference Windows-specific technologies (e.g., Hyper-V, Windows Firewall) to ensure Linux equivalents (e.g., KVM, iptables) are referenced where applicable, or clarify if the underlying platform is Windows-only.
- Where examples or links are provided for VM provisioning, disk encryption, or remote access, ensure Linux scenarios are equally represented and not relegated to secondary mentions.
Azure Government
Azure Government developer guide
...government/documentation-government-developer-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before cross-platform or Linux-friendly options (CLI, Python SDK). The 'Quickstarts' section specifically highlights 'Connect with PowerShell' and 'Connect with Visual Studio' before mentioning CLI and Python SDK, which are more platform-agnostic. There are no explicit Linux/macOS examples or references to Linux-specific tools or workflows.
Recommendations
- Reorder the 'Quickstarts' section to list cross-platform tools (CLI, Python SDK) before Windows-specific tools (PowerShell, Visual Studio).
- Explicitly mention Linux/macOS compatibility for CLI and Python SDK steps.
- Add links or notes about using Azure Government from Linux/macOS environments, including any platform-specific setup or troubleshooting.
- Include examples or guides for Linux/macOS users where relevant, especially for common developer workflows.
Azure Government
Azure Government Security
...e-government/documentation-government-plan-security.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias, primarily through references to Windows-specific technologies and protocols (e.g., SMB 3.0 for encryption, Windows/Windows Server, PowerShell attack detection) and by mentioning Windows tools before Linux equivalents. While Linux is referenced in some blog links and attack detection scenarios, most concrete examples and tool mentions are Windows-centric, with little detail on Linux/macOS alternatives for key security patterns.
Recommendations
- Include explicit Linux/macOS examples for encryption in transit and at rest, such as NFSv4.1 encryption, Linux disk encryption (dm-crypt/LUKS), and Linux file share protocols.
- When mentioning SMB 3.0 for encryption, also discuss Linux support for SMB (e.g., using cifs-utils) and alternatives like NFS with Kerberos.
- Provide parity in attack detection examples, such as highlighting Linux/macOS-specific threat vectors and monitoring tools (e.g., auditd, syslog, SELinux).
- Reference cross-platform scripting and automation tools (e.g., Bash, Python) alongside PowerShell when discussing security automation.
- Ensure that security best practices and tool recommendations are presented in a platform-neutral order, or explicitly call out platform-specific guidance for both Windows and Linux/macOS.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Examples
Summary
The documentation is generally cross-platform and provides guidance for both Windows and Linux environments. However, there is a noticeable Windows bias in several areas: Windows technologies (such as Hyper-V, BitLocker, Windows Firewall) are referenced more frequently and in greater detail than their Linux equivalents. Windows terminology and tools (e.g., PowerShell, RDP) are often mentioned first or exclusively, with Linux alternatives (e.g., SSH, DM-Crypt) referenced secondarily or in passing. Some examples and implementation details (especially around virtualization and disk encryption) are Windows-centric, and Windows-specific security mitigations are described in depth, while Linux coverage is briefer.
Recommendations
- Ensure Linux examples and tools (e.g., SSH, DM-Crypt, iptables, SELinux) are presented with equal prominence and detail as Windows equivalents.
- When describing platform features (e.g., disk encryption, firewall configuration), provide parallel step-by-step instructions for both Windows and Linux.
- Avoid listing Windows technologies or tools first by default; alternate or group by platform.
- Expand explanations of Linux-specific security features and mitigations to match the depth given to Windows technologies.
- Include more references to Linux documentation and best practices, especially for virtualization, disk encryption, and network isolation.
Azure Government
Compare Azure Government and global Azure
...re-government/compare-azure-government-global-azure.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in its developer guidance and command-line examples. PowerShell is mentioned and explained in detail, with references to Windows-specific modules (Azure PowerShell Az, AzureRM), and PowerShell examples are provided alongside Azure CLI. The note about PowerShell modules appears before CLI instructions, and some referenced tools (Visual Studio, System Center Operations Manager) are Windows-centric. However, Azure CLI is also covered, and most examples are cross-platform. No critical functionality is locked to Windows, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform.
- Explicitly state that Azure CLI works on Linux/macOS and link to installation guides for those platforms.
- Where PowerShell modules are discussed, add equivalent Bash or shell scripting guidance for Linux/macOS users.
- When referencing Visual Studio, mention alternative IDEs/editors for non-Windows platforms.
- Audit referenced documentation links to ensure Linux/macOS parity is addressed.
Azure Government
Azure Government developer guide
...government/documentation-government-developer-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias, primarily in the ordering and emphasis of quickstart links. Windows-centric tools like PowerShell and Visual Studio are mentioned before cross-platform or Linux-friendly options like CLI and Python SDK. There are no explicit Linux/macOS examples or references to Linux-specific tools or workflows, and the documentation does not clarify parity or differences for non-Windows users.
Recommendations
- Explicitly mention Linux/macOS compatibility for CLI and SDK tools.
- Add quickstart links or sections for Linux/macOS environments, including setup and usage examples.
- Balance the ordering of quickstart links so that cross-platform tools (CLI, Python SDK) are listed before or alongside Windows-specific tools (PowerShell, Visual Studio).
- Include guidance or references for using Azure Government from Linux/macOS, such as shell commands, package installation, and troubleshooting.
- Where PowerShell is referenced, also provide Bash or shell equivalents for common tasks.
Azure Government
Azure Government Security
...e-government/documentation-government-plan-security.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows and Windows Server are mentioned explicitly as examples for SMB 3.0 encryption, while Linux equivalents are not discussed. The list of Microsoft Defender for Cloud blog posts includes a PowerShell attack example before Linux-specific attack examples. There is a general tendency to mention Windows technologies and tools first or exclusively, with limited explicit Linux guidance or parity in examples.
Recommendations
- Add explicit references to Linux support for SMB 3.0 encryption and clarify how Linux VMs can leverage encryption in transit and at rest.
- Include Linux-specific examples and guidance for client-side encryption, especially for popular languages and libraries used on Linux.
- Balance blog post references by listing Linux-related security scenarios alongside or before Windows/PowerShell examples.
- Where Windows tools or protocols are mentioned (e.g., SMB 3.0), provide equivalent Linux commands, tools, or configuration guidance.
- Ensure that all best practice sections offer platform-agnostic advice, or clearly indicate how Linux/macOS users can achieve the same security outcomes.