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 51-75 of 124 flagged pages
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-welcome.md
...s/azure-government/documentation-government-welcome.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell and SQL Server Management Studio (Windows-centric tools) as primary connection and development methods for Azure Government. PowerShell is mentioned explicitly as a connection method, and SQL Server Management Studio is referenced for development, both of which are traditionally Windows tools. While Azure CLI is mentioned (which is cross-platform), the ordering and inclusion of Windows-specific tools before Linux alternatives (e.g., Azure Cloud Shell, cross-platform database clients) suggests a Windows-first approach.
Recommendations
- Include explicit Linux examples and tools, such as connecting via Azure CLI on Linux or using Azure Cloud Shell.
- Mention cross-platform database clients (e.g., DBeaver, Azure Data Studio) alongside SQL Server Management Studio.
- Ensure ordering of connection guides alternates or starts with cross-platform options rather than Windows-specific tools.
- Add examples or links for using Azure Government from macOS and Linux environments.
- Clarify that PowerShell Core is available cross-platform, and provide instructions for its use on Linux/macOS.
Create Pull Request
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-cognitiveservices.md
...vernment/documentation-government-cognitiveservices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell commands for all provisioning and key retrieval steps, with no mention of Azure CLI, Bash, or Linux-native tools. All examples and instructions assume the user is on Windows, and quickstart links default to Windows/Visual Studio tabs or C# examples, further reinforcing the bias. There is no guidance for Linux or cross-platform users, nor are alternative command-line tools or shell environments discussed.
Recommendations
- Add equivalent Azure CLI commands for provisioning and managing Cognitive Services resources, with clear instructions for Linux/macOS users.
- Include Bash or shell script examples alongside PowerShell, and clarify which commands work cross-platform.
- Ensure quickstart links and code samples offer parity for Linux (e.g., tabs for Bash, Python, REST API usage from Linux/macOS).
- Explicitly mention platform compatibility and provide guidance for users on non-Windows systems.
- Review and update screenshots and UI references to avoid Windows-only imagery where possible.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/azure-secure-isolation-guidance.md
...es/azure-government/azure-secure-isolation-guidance.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows technologies (Hyper-V, BitLocker, Windows Firewall) are referenced first and in greater detail than their Linux equivalents; examples and guidance often prioritize Windows or PowerShell, with Linux/CLI alternatives mentioned secondarily or omitted; and Windows-specific tools and patterns (such as Windows Firewall, BitLocker, Hyper-V, and PowerShell) are described extensively, while Linux alternatives (DM-Crypt, iptables, SSH, etc.) receive less coverage or are only briefly referenced.
Recommendations
- Ensure that Linux-specific technologies (e.g., DM-Crypt, iptables, SELinux, Linux guest OS security controls) are described with equal detail and prominence as Windows technologies.
- Provide Linux-first or parallel examples for all operational guidance, including CLI commands and configuration steps, not just PowerShell or Windows GUI.
- Include explicit references and links to Linux documentation and best practices wherever Windows tools or patterns are mentioned.
- Balance technical deep-dives (e.g., virtualization, disk encryption, firewalling) with equal coverage of Linux implementations and security features.
- Avoid assuming Windows as the default platform; clarify when guidance applies to both Windows and Linux, and highlight any differences or considerations for Linux users.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the prominent mention and use of PowerShell (including detailed notes about the Az and AzureRM modules) and references to Windows-centric tools and workflows (e.g., Visual Studio, System Center Operations Manager). While Azure CLI is also mentioned and examples are provided, PowerShell is frequently highlighted, and Windows tools are referenced before or more prominently than their Linux or cross-platform equivalents. There is a lack of explicit Linux shell (bash) examples, and some guidance assumes familiarity with Windows environments.
Recommendations
- Provide Linux/bash shell equivalents for all PowerShell command examples, especially for az CLI usage.
- When referencing tools like Visual Studio, also mention cross-platform alternatives (e.g., VS Code) and how to configure them for Azure Government.
- Avoid presenting PowerShell as the default or primary automation tool; ensure parity in documentation for bash/CLI workflows.
- Where Windows-specific tools or modules are discussed (e.g., System Center Operations Manager), include notes or links for Linux-based monitoring or management alternatives.
- In code blocks and guidance, alternate the order of PowerShell and CLI/bash examples, or present them side-by-side to avoid a 'Windows-first' impression.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md
...government/documentation-government-developer-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools and workflows (PowerShell, Visual Studio) before Linux equivalents, and by providing explicit links to PowerShell and Visual Studio quickstarts while Linux alternatives (such as Bash, VS Code, or other editors) are not mentioned. The CLI quickstart is included, but PowerShell is listed first, and there is no explicit mention of Linux-specific guidance or examples.
Recommendations
- Add Linux-specific quickstart links, such as connecting with Bash or using Linux-native tools.
- Include examples and guidance for popular Linux editors (e.g., VS Code, Vim, Emacs) alongside Visual Studio.
- Ensure CLI instructions are platform-agnostic and clarify any OS-specific steps.
- Present PowerShell and CLI options together, or list CLI first to avoid Windows-first ordering.
- Explicitly mention Linux support and provide parity in walkthroughs and sample code.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md
...e-government/documentation-government-plan-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and Windows Server are mentioned explicitly as examples for encryption in transit (SMB 3.0), while Linux equivalents are not discussed. There is a reference to PowerShell attacks in the context of Defender for Cloud, with no comparable Linux scripting example. Windows tools and protocols (SMB, smartcard authentication, Secure Admin Workstations) are referenced without Linux alternatives or parity. Linux is mentioned only in the context of Defender for Cloud detecting attacks against Linux machines, but not in configuration or operational examples. No Linux-specific tools, patterns, or best practices are provided, and examples or explanations tend to default to Windows technologies.
Recommendations
- Include Linux-specific examples for encryption in transit, such as NFSv4.2 with Kerberos, or SSH/SFTP for secure file transfers.
- Mention Linux authentication and admin workstation equivalents, such as using SSH keys, Linux bastion hosts, or privileged access management tools for Linux.
- Provide Linux scripting attack detection examples alongside PowerShell (e.g., bash, Python, or Perl attacks).
- Discuss Linux disk encryption options (e.g., dm-crypt, LUKS) in parallel with Azure disk encryption for Windows.
- Reference Linux file sharing protocols (e.g., NFS, Samba) and their security configurations.
- Ensure that best practices and operational guidance are platform-neutral or provide parity between Windows and Linux environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, particularly in its developer guidance and command-line tooling. PowerShell is referenced prominently, with a dedicated note about the Azure PowerShell Az module and its installation, and PowerShell examples are provided alongside Azure CLI. The PowerShell example is given equal or slightly greater prominence than the Azure CLI example, and there is no mention of Bash, Linux shells, or Linux-specific tooling. Additionally, references to Visual Studio and System Center Operations Manager further reinforce a Windows-centric perspective.
Recommendations
- Include explicit Bash/Linux shell examples for all command-line instructions, especially where Azure CLI is used.
- When referencing PowerShell, ensure that equivalent Linux/Bash commands are provided and shown first or side-by-side.
- Mention cross-platform compatibility of Azure CLI and PowerShell Core (pwsh) to clarify usage on Linux and macOS.
- Add guidance for using non-Windows developer tools (e.g., VS Code, JetBrains Rider) in relevant sections.
- Avoid assuming Visual Studio or Windows-only tools; provide alternatives or clarify when a tool is cross-platform.
- Where possible, use neutral language such as 'command-line' or 'shell' instead of 'PowerShell' unless specifically required.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, particularly in its developer guidance and code examples. PowerShell is highlighted in notes and examples, and references to Windows-centric tools and patterns (such as Visual Studio and System Center Operations Manager) are prevalent. While Azure CLI is mentioned, PowerShell is often given equal or greater prominence, and Linux-specific guidance or examples are largely absent.
Recommendations
- Provide Linux/bash shell equivalents for all PowerShell code examples, especially in sections where Azure CLI is mentioned.
- Include explicit references to cross-platform tools and workflows (e.g., VS Code, Azure CLI on Linux/macOS) alongside Windows tools like Visual Studio.
- When listing command-line options, present Azure CLI (which is cross-platform) before PowerShell, or at least in parallel, to avoid the perception of Windows-first bias.
- Add guidance or links for Linux/macOS users where configuration or SDK endpoint changes are discussed, ensuring parity in instructions.
- Review sections referencing Windows-specific management tools (e.g., System Center Operations Manager, Visual Studio) and add alternatives or notes for Linux-based management and development environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, particularly in its developer guidance and example sections. PowerShell is highlighted in notes and examples, with explicit references to the Azure PowerShell Az module and AzureRM, and PowerShell cmdlets are given as a primary method for querying endpoints. Although Azure CLI is also mentioned, PowerShell receives more detailed attention and is referenced first in some cases. There is a lack of explicit Linux or Bash shell examples, and Windows-centric tools and workflows (such as Visual Studio and PowerShell) are referenced without Linux alternatives.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI commands.
- When referencing PowerShell, ensure Azure CLI (with Bash syntax) is presented with equal prominence and detail.
- Include explicit guidance for Linux/macOS users, such as using Bash, zsh, or other common shells.
- When mentioning Visual Studio or other Windows-specific tools, also mention cross-platform or Linux-friendly alternatives (e.g., VS Code, JetBrains Rider).
- Review all code snippets and notes to ensure parity between Windows and Linux development environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, primarily through the prominent mention and detailed discussion of PowerShell modules (Az and AzureRM) before Azure CLI, and by referencing Windows/PowerShell-specific tools and patterns (e.g., Visual Studio, System Center Operations Manager) without equivalent Linux or cross-platform alternatives. While Azure CLI is mentioned, PowerShell is often foregrounded or discussed in greater detail, and some example scripts are written in PowerShell syntax. There is a lack of explicit Linux shell (bash) examples, and Windows-centric tools are referenced without noting Linux alternatives.
Recommendations
- Provide Linux shell (bash) equivalents for all PowerShell command examples, especially for Azure CLI usage.
- When referencing PowerShell modules, also mention cross-platform compatibility or provide links to Linux installation guides.
- Ensure that tools like Visual Studio and System Center Operations Manager are accompanied by references to cross-platform or Linux-native alternatives where available (e.g., VS Code, open-source monitoring tools).
- In lists or instructions, avoid always mentioning Windows/PowerShell first; alternate or present CLI/bash examples first in some sections.
- Explicitly state when tools or instructions are cross-platform, and clarify any OS-specific limitations or differences.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, primarily through the prominence and prioritization of PowerShell examples and references to Windows-centric tools and workflows. PowerShell is highlighted in notes and examples, sometimes before or alongside Azure CLI, and there is an assumption of Visual Studio usage for configuration. There is little to no explicit mention of Linux shell or cross-platform scripting alternatives, and some links and guidance (such as for Redis or Application Insights) direct users to PowerShell-based instructions.
Recommendations
- Ensure that all command-line examples are provided in both PowerShell and Bash/Azure CLI formats, with equal prominence and clarity.
- When referencing tools like Visual Studio, also mention cross-platform alternatives (e.g., VS Code, JetBrains Rider) and provide equivalent configuration steps for Linux/macOS users.
- Avoid language that assumes a Windows environment by default; clarify when instructions are platform-agnostic or provide OS-specific guidance as needed.
- Where links point to PowerShell-heavy documentation (e.g., Redis management), add or reference equivalent CLI or REST API documentation.
- In developer guidance, explicitly state that all major Azure SDKs and tools are cross-platform, and provide links to Linux/macOS installation and usage guides.
- Review and update any tables or sections that reference Windows-specific endpoints, tools, or workflows to ensure Linux parity is maintained.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md
...re-government/compare-azure-government-global-azure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the developer guidance section. PowerShell is highlighted with a dedicated note about module changes, and PowerShell cmdlets are given equal prominence to Azure CLI, with explicit links and examples. References to Windows-centric tools (e.g., Visual Studio, System Center Operations Manager) are present, and some cross-platform tools are mentioned only after Windows-specific ones. There is no explicit Linux example or mention of Linux-native tools (e.g., Bash, shell scripts), and the documentation assumes familiarity with Windows-based administration patterns.
Recommendations
- Provide Linux-specific examples alongside PowerShell, such as Bash or shell script equivalents for Azure CLI usage.
- When referencing PowerShell modules, also mention and link to Azure CLI and its installation/usage guides for Linux and macOS.
- In developer tool guidance, include references to cross-platform editors (e.g., VS Code) and command-line tools, not just Visual Studio.
- For SDK and endpoint configuration, provide sample configuration snippets for both Windows and Linux environments.
- Ensure that any references to Windows tools or workflows are balanced with Linux alternatives or at least acknowledge cross-platform options.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md
...e-government/documentation-government-plan-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows and Windows Server are mentioned explicitly as examples for encryption in transit (SMB 3.0), while Linux equivalents are not discussed. There is a reference to PowerShell attacks in the security monitoring section, and several linked blog posts focus on Windows-centric attack vectors (e.g., PowerShell, Sysmon). Linux is only mentioned in passing in two blog post titles, and there are no explicit Linux or cross-platform command-line examples or tool references. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
- When mentioning Windows-specific features (e.g., SMB 3.0 encryption), also describe Linux equivalents, such as NFS with Kerberos or SMB 3.0 support on Linux.
- Include Linux command-line or configuration examples alongside any Windows or PowerShell examples.
- Reference Linux-native security tools (e.g., auditd, SELinux, AppArmor) where appropriate, especially in sections discussing monitoring and threat detection.
- Balance blog post references to include more Linux-focused security scenarios and guidance.
- Explicitly state cross-platform support and provide links to Linux documentation or guides where relevant.
- Avoid assuming the reader is using Windows; use neutral language and examples that apply to both Windows and Linux environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-image-gallery.md
...e-government/documentation-government-image-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing images, referencing connecting via PowerShell, and listing Windows VM creation steps before Linux. There are no CLI or Bash examples for Linux users, and Linux VM creation is mentioned last in the next steps.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples for listing VM images in Azure Government.
- Include instructions for connecting to Azure Government using the Azure CLI, not just PowerShell.
- Balance the order of 'Next steps' by listing Linux and Windows VM creation guides together or alternating their order.
- Explicitly mention that the PowerShell example is one of multiple options, and link to Linux/CLI documentation where appropriate.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and provides step-by-step instructions and screenshots for its use. There are no examples or guidance for connecting from Linux or using cross-platform tools. The documentation implicitly assumes a Windows environment, omitting mention of alternatives available on Linux or macOS.
Recommendations
- Include instructions for connecting to Azure Government SQL endpoints using cross-platform tools such as Azure Data Studio, sqlcmd, or third-party clients available on Linux and macOS.
- Add a section or note acknowledging that SSMS is Windows-only, and provide links or steps for Linux/macOS users.
- Present connection string examples that can be used with command-line tools or programming languages on any platform.
- Where possible, offer parity in screenshots and UI walkthroughs for cross-platform tools.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/connect-with-azure-pipelines.md
...icles/azure-government/connect-with-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line instructions and automation scripts are provided exclusively in PowerShell, with no mention or example of Bash, Azure CLI, or Linux-compatible alternatives. The prerequisites specifically require Azure PowerShell, and the service principal creation process is described only for PowerShell users. There is no guidance for users on Linux or macOS, nor are cross-platform tools like Azure CLI referenced. The workflow assumes a Windows environment (e.g., use of PowerShell, Set-ExecutionPolicy), and Windows-specific patterns are presented first and exclusively.
Recommendations
- Provide equivalent instructions and scripts using Azure CLI (az) in Bash, which is cross-platform and widely used on Linux and macOS.
- Include notes or sections for Linux/macOS users, specifying any differences in setup or execution.
- When referencing command-line tools, mention both Azure PowerShell and Azure CLI, and provide links to both installation guides.
- Avoid Windows-specific commands like Set-ExecutionPolicy unless absolutely necessary, or provide alternatives for non-Windows platforms.
- Add a table or section comparing PowerShell and Bash/Azure CLI approaches for key tasks (e.g., service principal creation).
- Explicitly state that the instructions are for Windows/PowerShell and direct users to Linux/macOS guidance if available.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes deploying an Azure App Services app using Visual Studio 2019, a Windows-centric IDE, with no mention of Linux, macOS, or cross-platform tools. All steps and screenshots are based on Windows/Visual Studio workflows, and there are no examples or instructions for deploying from Linux environments or using command-line tools like Azure CLI or GitHub Actions.
Recommendations
- Add parallel instructions for deploying using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include examples for deploying from Linux or macOS environments, such as using VS Code, Azure CLI, or Git-based deployment.
- Mention and provide steps for alternative deployment methods (e.g., GitHub Actions, Azure DevOps, FTP, or ZIP deploy) that are not tied to Visual Studio.
- Clearly indicate which steps are Windows-specific and provide equivalent steps for other operating systems.
- Add a section summarizing cross-platform deployment options and linking to relevant documentation.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-extension.md
...azure-government/documentation-government-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based instructions for listing VM extensions in Azure Government, referencing Windows-centric tools and workflows, and omitting equivalent Linux/CLI examples. Additionally, the 'Next steps' section lists Windows extension deployment before Linux, reinforcing the Windows-first pattern.
Recommendations
- Include equivalent Azure CLI or Bash examples for listing VM extensions, ensuring Linux users have clear guidance.
- Explicitly mention that PowerShell is cross-platform, or clarify if the instructions are Windows-only.
- Provide links or references to Linux/CLI documentation alongside PowerShell instructions.
- Alternate the order of 'Next steps' to avoid always listing Windows before Linux, or present both options equally.
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
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Visual Studio (a Windows-centric IDE) for application development and deployment, and by only providing .NET/ASP.NET Core code samples without mention of Linux or cross-platform development environments. There are no examples or instructions for Linux users, such as using VS Code, command-line tools, or deployment from Linux environments. The documentation assumes a Windows development workflow and omits Linux alternatives.
Recommendations
- Add instructions for setting up and configuring the application using cross-platform tools such as Visual Studio Code or JetBrains Rider, which are available on Linux.
- Include command-line examples (e.g., using dotnet CLI) for application configuration and deployment, suitable for Linux/macOS users.
- Mention and provide steps for deploying and running the ASP.NET Core application from Linux environments, including how to edit configuration files and run the app.
- Ensure that references to Visual Studio are accompanied by alternatives or notes for Linux users.
- Where possible, provide bash shell commands alongside any PowerShell or Windows-specific instructions.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-vs.md
...zure-government/documentation-government-connect-vs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes connecting to Azure Government using Visual Studio, a Windows-centric IDE, with no mention of Linux-compatible tools or workflows. All instructions, screenshots, and prerequisites assume the use of Visual Studio on Windows, with no alternatives or parity for Linux users. There are no examples or guidance for connecting from Linux environments or using cross-platform tools.
Recommendations
- Include instructions for connecting to Azure Government using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure PowerShell (which are available on Linux).
- Provide Linux-specific steps or note any differences for users on Linux or macOS.
- Mention and link to alternative tools and workflows that are supported on Linux, such as using the Azure CLI to log in to Azure Government.
- Consider rephrasing the quickstart to clarify that it is Windows/Visual Studio-specific, or provide parallel quickstarts for other platforms.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md
...e-government/documentation-government-plan-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by mentioning Windows, Windows Server, and SMB 3.0 encryption support explicitly, while omitting equivalent Linux details. There are no Linux-specific examples or mentions of Linux-compatible tools for encryption in transit or at rest. Additionally, references to client-side encryption libraries focus on Java and .NET (commonly associated with Windows), and a blog post list highlights PowerShell attacks but only includes two Linux-specific posts late in the list. There are no Linux command-line or configuration examples, nor are Linux-native tools or patterns discussed.
Recommendations
- Explicitly mention Linux support for encryption in transit and at rest, such as SMB 3.0 support on Linux clients and how to configure it.
- Provide Linux-specific examples or references for client-side encryption, such as using Python or OpenSSL.
- Include parity in documentation for both Windows and Linux, ensuring that Linux tools, commands, and best practices are described alongside Windows equivalents.
- Highlight Linux security monitoring and incident response tools (e.g., auditd, syslog, fail2ban) where relevant.
- Balance blog post references to include more Linux-focused security scenarios and investigations.
- When referencing Azure services or features, clarify their compatibility and usage patterns for both Windows and Linux environments.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md
...e-government/documentation-government-plan-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Windows and Windows Server are mentioned explicitly as examples for encryption in transit (SMB 3.0), with no mention of Linux equivalents. There are references to Windows-specific protocols and tools (e.g., SMB 3.0, PowerShell in blog post titles), and Linux is only mentioned in passing or as an afterthought in linked blog posts. There are no Linux-specific examples or guidance for common scenarios, such as encrypting data in transit or at rest, or for managing secrets. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
- Include Linux-specific examples alongside Windows examples for encryption in transit (e.g., mention NFSv4.1 with Kerberos, SSH/SCP/SFTP, or SMB 3.0 on Linux).
- Provide explicit guidance for Linux VMs regarding disk encryption (e.g., using Azure Disk Encryption with dm-crypt).
- When referencing PowerShell or Windows tools, also reference equivalent Linux command-line tools or scripts (e.g., Azure CLI, Bash, Python SDK).
- Add Linux-focused best practices for managing secrets, such as using Key Vault with Linux applications and integration patterns.
- Ensure that blog post references and documentation examples are balanced, highlighting both Windows and Linux attack detection and mitigation scenarios.
- Review all sections for implicit Windows-first language and update to be platform-neutral or to provide equal coverage for Linux.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/connect-with-azure-pipelines.md
...icles/azure-government/connect-with-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell scripts and instructions for generating a service principal, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting any equivalent Bash, Azure CLI, or Linux/macOS guidance. The step-by-step process assumes the user is on Windows, with no mention of how to accomplish the same tasks on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands and Bash scripts for service principal creation and related steps, suitable for Linux/macOS users.
- Include instructions for running scripts on Linux/macOS, such as using chmod +x and ./script.sh, and note differences in execution policy handling.
- When referencing tools, mention cross-platform options (e.g., Azure CLI, Bash) alongside PowerShell.
- Structure examples so that cross-platform (CLI/Bash) solutions are presented before or alongside Windows/PowerShell solutions, not after.
- Add a note clarifying that all steps can be performed on Linux/macOS, and link to relevant cross-platform documentation.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-cognitiveservices.md
...vernment/documentation-government-cognitiveservices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The prerequisites and provisioning steps exclusively reference PowerShell, and there are no Linux or cross-platform instructions. Quickstart links also default to Windows or Visual Studio tabs, further reinforcing a Windows-centric approach.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside PowerShell examples for provisioning and managing resources.
- Include Linux/macOS-specific setup instructions, such as installing Azure CLI and authenticating with Azure Government.
- Ensure quickstart links and code samples include tabs or options for Bash, Azure CLI, and non-Windows environments.
- Avoid language in prerequisites and instructions that assumes the user is on Windows; mention cross-platform tools first or equally.
- Add screenshots or terminal outputs from Linux/macOS environments where appropriate.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/azure-secure-isolation-guidance.md
...es/azure-government/azure-secure-isolation-guidance.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas. Windows technologies, tools, and terminology are often mentioned first or exclusively, such as Hyper-V, BitLocker, Windows Firewall, and Windows-specific security features. Powershell and Windows portal are frequently referenced as primary management interfaces, with Linux alternatives mentioned later or not at all. Some technical explanations (e.g., Drawbridge, Hypervisor, security mitigations) are deeply rooted in Windows architecture, and Linux-specific details are sometimes missing or less detailed.
Recommendations
- Ensure that Linux examples and tools (e.g., Azure CLI, SSH, Linux firewall, DM-Crypt) are presented alongside or before Windows equivalents, especially in code snippets, configuration, and management instructions.
- Provide balanced coverage of both Windows and Linux in technical explanations, including equal detail on Linux-based isolation, security, and encryption mechanisms.
- Avoid using Windows-centric terminology as the default; use cross-platform or neutral terms where possible.
- When referencing management interfaces (portal, PowerShell, CLI), always include Azure CLI and Linux-native tools in parallel with Windows/PowerShell.
- Expand sections on Linux-specific technologies (e.g., DM-Crypt, iptables, SELinux/AppArmor, SSH) to match the depth given to Windows technologies.
- Review all tables, figures, and callouts to ensure Linux is equally represented in security guidance and best practices.