Azure Government

38
Total Pages
19
Linux-Friendly Pages
19
Pages with Bias
50.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (29)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-extension.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/connect-with-azure-pipelines.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-ssms.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-image-gallery.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-jps.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-vs.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-aad-auth-qs.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-itar.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-ssms.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/connect-with-azure-pipelines.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-cognitiveservices.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/azure-secure-isolation-guidance.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/compare-azure-government-global-azure.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 the Az module, and PowerShell cmdlets are given equal prominence to Azure CLI, with explicit links and examples. References to Visual Studio and System Center Operations Manager further reinforce a Windows-centric perspective. While Azure CLI is mentioned and examples are provided, there is little to no mention of Linux-native tools, shells, or workflows, and Windows tools or patterns (e.g., Visual Studio, PowerShell) are often referenced first or exclusively.
Recommendations:
  • Ensure that all command-line examples are provided for both Azure CLI and PowerShell, and clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • When referencing PowerShell, also mention Bash or other Linux-native shells where appropriate, especially for scripting and automation scenarios.
  • Include examples or guidance for Linux/macOS users, such as using Bash scripts, connecting from Linux environments, or integrating with Linux-based developer tools.
  • Avoid assuming Visual Studio as the default IDE; mention alternatives like VS Code or JetBrains Rider, and provide instructions for configuring Application Insights or other services from non-Windows environments.
  • Where Windows-specific tools or workflows are discussed (e.g., System Center Operations Manager), add notes or links to equivalent Linux-native solutions or clarify if no equivalent exists.
  • Review the ordering of tool mentions to avoid always listing Windows/PowerShell first; alternate or list cross-platform tools (like Azure CLI) before platform-specific ones.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-connect-vs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation exclusively describes connecting to Azure Government using Visual Studio, a Windows-centric IDE, and does not mention or provide instructions for Linux users or alternative cross-platform tools. There are no Linux or macOS examples, nor are cross-platform command-line tools (such as Azure CLI) referenced. The workflow assumes a Windows environment by default.
Recommendations:
  • Include instructions for connecting to Azure Government using cross-platform tools such as Azure CLI or Azure PowerShell, which are available on Linux and macOS.
  • Mention and provide examples for using Visual Studio Code, which is cross-platform, as an alternative to Visual Studio.
  • Clearly state the platform requirements for Visual Studio and provide links or references to equivalent workflows for non-Windows users.
  • Add a section or links for Linux/macOS users to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-developer-guide.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-aad-auth-qs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-with-cli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-quickstarts-vm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-extension.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell-based instructions for listing VM extensions in Azure Government, with no equivalent CLI or Linux-native example. The guidance assumes use of Windows tools and patterns, and the only code sample is in PowerShell. Linux users are not given direct instructions or parity in the main workflow.
Recommendations:
  • Add equivalent Azure CLI (az) instructions for listing VM extensions, which work cross-platform (Linux, macOS, Windows).
  • Present both PowerShell and CLI examples side-by-side, or clearly indicate that the CLI example is suitable for Linux users.
  • Avoid assuming PowerShell as the default tool; mention alternatives up front.
  • Ensure that Linux workflows are described with equal prominence and clarity as Windows/PowerShell workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-image-gallery.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 Linux CLI or Bash examples for obtaining images, and Linux guidance is less prominent.
Recommendations:
  • Add equivalent Azure CLI (cross-platform) and Bash examples for listing VM images.
  • Include instructions for connecting to Azure Government using the Azure CLI.
  • Ensure Linux VM creation steps are presented with equal prominence and ordering as Windows steps.
  • Where possible, use neutral, cross-platform tooling (e.g., Azure CLI) in examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-howto-deploy-webandmobile.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 tool, and provides no examples or guidance for Linux or cross-platform workflows (such as using the Azure CLI, GitHub Actions, or VS Code). All instructions and screenshots are based on the Windows/Visual Studio experience, with no mention of Linux, macOS, or command-line alternatives.
Recommendations:
  • Add a section describing how to deploy an Azure App Services app using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include examples for deploying using GitHub Actions or Azure DevOps pipelines, which are platform-agnostic.
  • Mention and provide instructions for using Visual Studio Code, which is available on all major operating systems, as an alternative to Visual Studio 2019.
  • Ensure that screenshots and step-by-step guides are provided for both GUI (portal) and CLI-based workflows.
  • Explicitly state that the described workflow is Windows-specific and provide links to Linux/macOS deployment documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-manage-oms.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation exhibits a Windows-first bias, with Windows servers and tools (such as System Center Operations Manager and Endpoint Protection) mentioned before Linux equivalents. Visuals and examples predominantly feature Windows environments, and there is a lack of Linux-specific command-line or onboarding examples. Linux is mentioned, but often as a secondary consideration, and Linux-specific tooling or instructions are minimal or absent.
Recommendations:
  • Provide Linux onboarding examples and screenshots alongside Windows ones, ensuring parity in visual representation.
  • Include Linux-specific tooling (e.g., auditd, syslog, Linux-native antimalware solutions) in antimalware and monitoring solution discussions.
  • Present instructions for both Windows and Linux in parallel, rather than referencing Windows first or exclusively.
  • Add PowerShell and Bash/CLI examples side by side for agent installation, configuration, and automation.
  • Highlight Linux security scenarios and solutions (e.g., SELinux, AppArmor, fail2ban) in the cybersecurity solution sections.
  • Ensure that all referenced documentation links for onboarding and configuration are equally available for Linux and Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-to-storage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows bias primarily by recommending Windows-specific tools (Visual Studio) and patterns (e.g., 'Download Visual Studio 2019') as prerequisites, and by omitting explicit Linux/macOS alternatives or instructions for key development steps. While Azure Storage Explorer is cross-platform, the setup and workflow examples focus on Windows-centric development environments, with no mention of Linux/macOS equivalents for Visual Studio or command-line usage. There are no PowerShell-specific examples, but the overall workflow assumes a Windows-first audience.
Recommendations:
  • In the prerequisites, provide alternative instructions for Linux/macOS users, such as recommending VS Code or JetBrains Rider instead of only Visual Studio.
  • Explicitly state that Azure Storage Explorer is cross-platform and provide installation links or instructions for Linux/macOS.
  • For code samples, clarify that environment variables and SDKs work across platforms, and provide any necessary shell commands for Linux/macOS (e.g., setting environment variables in bash/zsh).
  • Include a section or note on how to set up the development environment on Linux/macOS, including installation of required SDKs and tools.
  • Avoid language that assumes the user is on Windows (e.g., 'Open Visual Studio'), or provide parallel instructions for other operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-overview-jps.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows-centric bias, particularly in sections discussing legacy authentication and infrastructure. It exclusively references Windows-based technologies such as Active Directory Domain Services, ADFS, and Kerberos/NTLM, and provides deployment guidance only for Windows Server environments. There are no examples or guidance for Linux-based identity solutions, nor are cross-platform alternatives mentioned. The documentation assumes the use of Windows tools and patterns, omitting Linux or open-source equivalents.
Recommendations:
  • Include examples and guidance for integrating Linux-based identity solutions (e.g., using Samba for Active Directory compatibility, or integrating with LDAP/Kerberos on Linux).
  • Mention and provide links to documentation for cross-platform identity management tools and patterns, such as Azure AD authentication libraries for Linux and open-source stacks.
  • When discussing domain controllers and federation services, acknowledge that Linux-based solutions (such as FreeIPA, Samba AD DC, or Shibboleth for federation) can be used in some scenarios, and provide high-level guidance or references.
  • Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Bash/CLI or Linux-native examples where possible.
  • Explicitly state the platform assumptions in each section and clarify whether the guidance is Windows-only or applicable to other operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-plan-security.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.