Azure Government
78
Total Pages
63
Linux-Friendly Pages
15
Pages with Bias
19.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
26 issues found
Showing 1-25 of 26 flagged pages
Azure Government
Deploy an app in Azure Government with Azure Pipelines
...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 exhibits a strong Windows bias, particularly in the 'Generate a service principal' section, which provides only a PowerShell script for service principal creation and setup. There are no equivalent instructions or examples for Linux/macOS users (e.g., Bash, Azure CLI), and the use of Windows-specific tools and patterns (PowerShell, Set-ExecutionPolicy) is assumed throughout. The prerequisites also exclusively mention Azure PowerShell, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent instructions and scripts using Azure CLI (az) for Linux/macOS users.
- Include Bash shell examples for service principal creation and setup.
- Clarify which steps are platform-agnostic and which require platform-specific tools.
- Mention cross-platform alternatives to PowerShell (e.g., Azure CLI, Bash) in the prerequisites.
- Present examples for both Windows and Linux/macOS side-by-side or indicate which commands are OS-specific.
Create Pull Request
Azure Government
Deploy an app in Azure Government with Azure Pipelines
...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, especially in the 'Generate a service principal' section, which provides only a PowerShell script for service principal creation and related instructions. There are no equivalent Bash, Azure CLI, or Linux/macOS examples. The prerequisites explicitly require Azure PowerShell, and all step-by-step instructions assume a Windows/PowerShell environment, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users and may prevent them from completing critical steps without additional research.
Recommendations
- Provide equivalent instructions and scripts using Azure CLI (az), which is cross-platform and works on Linux/macOS.
- Add notes or sections highlighting how Linux/macOS users can perform service principal creation and other steps without PowerShell.
- Reorder examples or add parallel instructions so that Windows and Linux/macOS users are equally supported.
- Explicitly mention platform compatibility for each tool and script.
- Include troubleshooting tips for common issues encountered on non-Windows platforms.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong bias towards Windows by exclusively providing PowerShell scripts and instructions for generating a service principal, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting any Linux or cross-platform alternatives. There are no Bash, Azure CLI, or cross-platform shell examples, and the instructions assume a Windows environment.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for service principal creation, suitable for Linux and macOS users.
- Include instructions for running scripts on Linux/macOS (e.g., using Azure CLI or Bash), not just PowerShell.
- Mention cross-platform tools and patterns before or alongside Windows-specific ones.
- Clarify when instructions are Windows-specific and offer alternatives for other platforms.
- Add a note or section highlighting cross-platform compatibility and linking to relevant Azure CLI documentation.
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and ASP.NET Core applications, with no mention of Linux development environments, editors, or deployment patterns. There are no Linux-specific instructions or examples, and all configuration steps assume the use of Windows tools and workflows.
Recommendations
- Add instructions for configuring Microsoft Entra authentication in popular Linux-based development environments, such as using VS Code on Linux or JetBrains Rider.
- Provide examples for deploying and running the sample application on Linux (e.g., using the dotnet CLI, configuring appsettings.json, and running the app on Linux).
- Include command-line examples (e.g., using Bash or the dotnet CLI) for registering and configuring the application, in addition to or instead of Visual Studio-centric steps.
- Mention cross-platform editors and tools, and clarify that the steps are applicable to both Windows and Linux unless otherwise noted.
- Explicitly state Linux support and provide troubleshooting tips for common Linux-specific issues.
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, for connecting to Azure Government SQL resources. There are no examples or guidance for Linux or cross-platform alternatives, such as Azure Data Studio or command-line tools. All instructions and screenshots are tailored to the Windows GUI, and no mention is made of Linux-compatible workflows.
Recommendations
- Add instructions for connecting to Azure Government SQL resources using Azure Data Studio, which is cross-platform.
- Include examples using sqlcmd or other command-line tools available on Linux.
- Explicitly mention platform compatibility and provide links or notes for Linux/macOS users.
- Consider reordering or supplementing the documentation to present cross-platform options alongside or before Windows-specific instructions.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell commands and referencing Azure PowerShell for provisioning and managing Azure AI services. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and Windows tools/patterns are mentioned first and exclusively. The quickstart links also favor Windows and Visual Studio tabs, with no mention of Linux or cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI (az) commands for all provisioning and management steps, with clear instructions for Linux/macOS users.
- Include Bash shell examples alongside PowerShell, especially for resource provider registration and account creation.
- Ensure quickstart links and code samples include Linux/macOS tabs or instructions, not just Windows/Visual Studio.
- Explicitly mention cross-platform compatibility and provide guidance for users on non-Windows platforms.
- Review and update screenshots and UI references to ensure they are not Windows-specific 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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell and Visual Studio connection guides before CLI and Python SDK options, and by providing explicit links to Windows-centric tools (PowerShell, Visual Studio) without equivalent emphasis on Linux-native tools or editors. There are no explicit Linux-specific examples or mentions of Linux-first workflows.
Recommendations
- Reorder the 'Quickstarts' section to list cross-platform tools (e.g., Azure CLI, Python SDK) before Windows-specific tools (PowerShell, Visual Studio).
- Add explicit examples or links for connecting to Azure Government using Bash or Linux-native shells.
- Include guidance or quickstarts for popular Linux editors (e.g., VS Code on Linux) alongside Visual Studio.
- Ensure that all code snippets and connection instructions are provided for both Windows (PowerShell) and Linux (Bash/CLI) environments.
- Explicitly mention Linux support and parity where possible, and link to Linux-specific documentation if available.
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 exclusively providing PowerShell commands (a Windows-centric tool) for listing Azure Government VM extensions, without offering equivalent examples for Linux users (e.g., using Azure CLI or Bash). The instructions reference connecting via PowerShell and do not mention or prioritize Linux-compatible tools or workflows. Additionally, the 'Next steps' section lists Windows before Linux.
Recommendations
- Add equivalent Azure CLI (az) command examples for Linux/macOS users to obtain the list of VM extensions.
- Explicitly mention that PowerShell is not required and that users can use Azure CLI or Cloud Shell from any platform.
- Reorder or parallelize 'Next steps' to avoid always listing Windows before Linux, or group them together as equal options.
- Provide links to both Windows and Linux extension documentation in the main body, not just in 'Next steps'.
Azure Government
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-government/documentation-government-get-started-connect-to-storage.md
...ocumentation-government-get-started-connect-to-storage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily by recommending Windows-specific tools (Visual Studio 2019) as a prerequisite for .NET development and not mentioning cross-platform alternatives. The only graphical tool discussed is Azure Storage Explorer, which is cross-platform, but no command-line or Linux-native tools (such as Azure CLI or azcopy) are mentioned. All code examples are language-based and cross-platform, but the setup and prerequisites for .NET development assume a Windows environment. There are no explicit Linux or macOS setup instructions or examples, and no mention of how to use the Storage API from Bash, Azure CLI, or PowerShell Core on Linux.
Recommendations
- In the prerequisites for .NET development, mention and provide instructions for using cross-platform editors like Visual Studio Code or JetBrains Rider, and clarify that the .NET SDK is available for Linux and macOS.
- Add examples or references for using Azure CLI (az storage ...) and/or azcopy for interacting with Azure Storage from the command line, which are popular on Linux.
- Include explicit instructions or notes for Linux/macOS users regarding environment variable setup, installation of SDKs, and running code samples.
- If Visual Studio is mentioned, clarify its availability on Windows only, and provide alternatives for other platforms.
- Consider adding a section or callout box highlighting cross-platform development options and tools.
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 is heavily biased towards Windows development environments, specifically Visual Studio, and does not provide any guidance or examples for Linux or cross-platform users. All deployment steps are described using Visual Studio, a Windows-centric tool, with no mention of Linux-compatible alternatives such as Azure CLI, GitHub Actions, or VS Code. There are no Linux or cross-platform command-line examples, and the prerequisites and workflow assume a Windows environment.
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 from Linux or macOS, such as using Git, GitHub Actions, or VS Code (which is cross-platform) with Azure extensions.
- Mention and link to documentation for non-Windows tools and workflows, such as Azure DevOps pipelines, Azure CLI, or ARM/Bicep templates.
- Reorganize the tutorial to present cross-platform or OS-neutral methods first, or provide parallel instructions for both Windows (Visual Studio) and Linux/macOS (CLI or code editors).
- Clearly state in the prerequisites that Visual Studio is only required for the Windows-specific workflow, and offer alternatives for other operating systems.
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
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for listing Azure Government Marketplace images, without offering equivalent Azure CLI or Bash examples. The 'Next steps' section lists Windows VM creation guides before Linux, and the only Linux-related link is for the portal, not for command-line tools. There is no mention of Linux tools or workflows for image discovery, and the guidance assumes use of Windows-centric tools.
Recommendations
- Add Azure CLI and Bash examples for listing VM images, alongside the PowerShell example.
- Include Linux-focused instructions for connecting to Azure Government and managing images.
- In the 'Next steps' section, provide parity by including links to Linux VM creation with CLI and PowerShell, and consider alternating the order or grouping by OS.
- Mention cross-platform tools (e.g., Azure CLI) earlier and equally with PowerShell to avoid implying Windows is the default or preferred environment.
Azure Government
Azure Government Identity
...e-government/documentation-government-plan-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in sections discussing legacy authentication and infrastructure. Active Directory, NTLM/Kerberos, and ADFS are Windows-centric technologies, and all deployment guidance links and examples reference Windows Server tools and documentation. There are no Linux equivalents or alternatives mentioned, nor are there examples for Linux-based identity management or authentication. Additionally, the guidance for extending identity to Azure IaaS focuses exclusively on deploying Windows domain controllers, with no mention of Linux-based solutions or cross-platform patterns.
Recommendations
- Include guidance or references for Linux-based identity solutions, such as integration with LDAP, FreeIPA, or SSSD.
- Provide examples for configuring authentication and identity management from Linux systems, especially for modern authentication protocols (OAuth, OpenID Connect).
- Mention cross-platform tools and patterns for hybrid identity scenarios, such as Azure AD Connect's compatibility with non-Windows environments.
- Add notes or links for Linux users on how to achieve similar outcomes, or clarify Windows-only requirements where applicable.
Azure Government
Azure AI services on Azure Government
...vernment/documentation-government-cognitiveservices.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All provisioning and key retrieval instructions use Azure PowerShell commands, with no mention of Azure CLI or Bash equivalents. There are no Linux/macOS-specific instructions or examples, and the quickstart links often default to Windows/Visual Studio tabs or C# code. This creates friction for users on Linux or macOS who may prefer or require cross-platform tools.
Recommendations
- Add Azure CLI and Bash examples for all provisioning and key retrieval steps.
- Explicitly mention that Azure CLI is supported on Linux/macOS and provide links to relevant installation guides.
- Ensure quickstart links include tabs for Linux/macOS and cross-platform languages (e.g., Python, Node.js) and tools.
- Avoid defaulting to Windows/Visual Studio tabs in code samples and quickstart links; present cross-platform options first or equally.
- Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives where needed.
Azure Government
Azure Government Marketplace images
...e-government/documentation-government-image-gallery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for listing Azure Government Marketplace images, without any equivalent Azure CLI or Bash examples for Linux/macOS users. Additionally, the 'Next steps' section lists Windows VM creation guides before Linux, and omits Linux-specific command-line instructions.
Recommendations
- Add Azure CLI and Bash examples for listing VM images in Azure Government, alongside PowerShell.
- Include links to Linux VM creation guides using command-line tools (Azure CLI, Bash) in the 'Next steps' section.
- Present Windows and Linux instructions in parallel, or alternate their order to avoid implicit prioritization.
- Explicitly mention cross-platform compatibility and provide guidance for macOS/Linux users where relevant.
Azure Government
Azure Government virtual machine extensions
...azure-government/documentation-government-extension.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively provides PowerShell commands for listing VM extensions in Azure Government, which is a Windows-centric tool. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI or Bash). Additionally, the 'Next steps' section lists Windows extension deployment before Linux, subtly prioritizing Windows.
Recommendations
- Add equivalent Azure CLI or Bash examples for listing VM extensions, suitable for Linux/macOS users.
- Explicitly mention cross-platform alternatives to PowerShell for connecting to Azure Government.
- Alternate the order of 'Next steps' to avoid consistently listing Windows before Linux.
- Clarify which tools are available on which platforms and link to installation guides for Azure CLI on Linux/macOS.
Azure Government
Azure support for public safety and justice
...re-government/documentation-government-overview-jps.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific cryptographic modules and validation programs multiple times, such as the 'Windows FIPS validation program' and 'Windows FIPS 140 Level 1' cryptographic modules for authentication. While it mentions that Azure is built with both Linux and Windows, the examples and technical details focus primarily on Windows implementations and validation, with no equivalent Linux-specific guidance or parity in examples. Windows tools and terminology are presented first and exclusively in critical sections related to compliance and authentication.
Recommendations
- Include explicit references to Linux cryptographic modules and their FIPS 140 validation status within Azure.
- Provide guidance or examples for Linux-based authentication and encryption solutions that meet CJIS and NIST requirements.
- Clarify whether Linux-based workloads in Azure receive the same compliance assurances and detail how Linux users can verify FIPS 140 compliance.
- Balance mentions of Windows and Linux tools, especially in compliance-critical sections, to ensure parity and inclusivity for cross-platform users.
Azure Government
Azure Government Overview
...s/azure-government/documentation-government-welcome.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page lists Windows-centric tools (PowerShell, SQL Server Management Studio) and places them prominently in the 'Get started' section. PowerShell is mentioned as a primary connection method, and SQL Server Management Studio is highlighted for development, both of which are traditionally Windows tools. While Azure CLI is included (cross-platform), Windows tools are listed before Linux/macOS alternatives, and no explicit Linux/macOS examples or tools are mentioned.
Recommendations
- Add explicit Linux/macOS examples and connection guides, such as using Bash with Azure CLI.
- Include cross-platform database management tools (e.g., Azure Data Studio) alongside SQL Server Management Studio.
- Ensure that Linux/macOS alternatives are listed with equal prominence and detail as Windows tools.
- Where PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide Bash equivalents.
- Consider alternating the order of tool presentation to avoid Windows-first bias.
Azure Government
Azure Government Marketplace images
...e-government/documentation-government-image-gallery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for listing Azure Government Marketplace images, with no equivalent Azure CLI or Bash examples for Linux/macOS users. Additionally, the 'Next steps' section lists Windows VM creation guides before Linux, and omits Linux examples for PowerShell and CLI.
Recommendations
- Add Azure CLI and Bash examples for listing VM images, suitable for Linux/macOS users.
- In the 'Next steps' section, include links to Linux VM creation guides for both PowerShell and CLI, or clarify cross-platform support.
- Present Windows and Linux instructions in parallel, or alternate which is shown first to avoid implicit prioritization.
Azure Government
Azure Government virtual machine extensions
...azure-government/documentation-government-extension.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively provides PowerShell commands for obtaining VM extension lists, which is a Windows-centric tool. There are no equivalent CLI or Bash examples for Linux/macOS users. The guidance for connecting to Azure Government is also PowerShell-specific, and Windows extension deployment is mentioned before Linux in the 'Next steps' section.
Recommendations
- Add Azure CLI and Bash examples for listing VM extensions, ensuring Linux/macOS users have clear instructions.
- Include guidance for connecting to Azure Government using Azure CLI, not just PowerShell.
- Present Windows and Linux extension deployment links in parallel or randomized order to avoid implicit prioritization.
- Explicitly state cross-platform options where possible.
Azure Government
Compare Azure Government and global Azure
...re-government/compare-azure-government-global-azure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits moderate Windows bias, primarily in the developer guidance and example sections. PowerShell is emphasized for Azure Government management, with explicit references to the Az and AzureRM PowerShell modules and cmdlets. PowerShell examples are provided alongside Azure CLI, but the PowerShell module installation and compatibility notes are more prominent and detailed. There is also a tendency to mention Windows-centric tools (e.g., Visual Studio) and workflows before or more thoroughly than their Linux/macOS equivalents. Linux-specific instructions, examples, or parity notes are largely absent, especially regarding SDK usage, endpoint configuration, and developer tooling.
Recommendations
- Add explicit Linux/macOS installation instructions for Azure CLI and PowerShell modules.
- Provide Bash and/or shell script examples alongside PowerShell for endpoint discovery and resource management.
- Include notes or links for using Azure CLI and SDKs on Linux/macOS, especially for tasks like Application Insights endpoint configuration.
- Mention cross-platform editors (e.g., VS Code) and workflows in developer sections, not just Visual Studio.
- Balance example ordering so that CLI and PowerShell are presented equally, or alternate which is shown first.
- Clarify that all CLI and SDK operations are supported on Linux/macOS unless otherwise noted.
Azure Government
Azure Government Overview
...s/azure-government/documentation-government-welcome.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page lists Windows-centric tools (PowerShell, SQL Server Management Studio) and places them before or alongside cross-platform options. PowerShell is highlighted as a primary connection method, and SQL Server Management Studio is mentioned without Linux/macOS alternatives. The ordering of connection guides puts the Azure CLI (cross-platform) after the portal and before PowerShell, but Windows tools are still prominent. There are no explicit Linux/macOS examples or tool recommendations.
Recommendations
- Add explicit Linux/macOS connection examples and guides, especially for Azure CLI and other cross-platform tools.
- Mention cross-platform alternatives to SQL Server Management Studio, such as Azure Data Studio.
- Ensure ordering of connection guides does not implicitly prioritize Windows tools (e.g., alternate order or group by platform).
- Where PowerShell is referenced, clarify that Azure CLI is fully supported and provide parity in example depth.
Azure Government
Azure Government developer guide
...government/documentation-government-developer-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows mild Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before Linux/macOS equivalents and providing a dedicated 'Connect with PowerShell' quickstart link. While a CLI quickstart is also present, the ordering and emphasis on PowerShell and Visual Studio may create friction for Linux/macOS users. No explicit Linux/macOS examples or tools are highlighted.
Recommendations
- Reorder quickstart links to alternate or group cross-platform tools (e.g., CLI before PowerShell, or mention both together).
- Explicitly mention Linux/macOS compatibility for CLI and SDK steps.
- Add quickstart links or sections for Linux/macOS-specific workflows (e.g., Bash, SSH, VS Code).
- Include examples or references for using Azure Government from Linux/macOS environments.
Azure Government
Azure Government Security
...e-government/documentation-government-plan-security.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific technologies (e.g., SMB 3.0 for encryption, Windows/Windows Server references) are mentioned in the encryption section, with no equivalent Linux details provided. Windows tools and protocols are referenced before Linux alternatives, and some example scenarios (e.g., file shares) are Windows-centric. However, most guidance is platform-neutral, and there are references to Linux in linked blog posts.
Recommendations
- Add explicit examples for Linux-based encryption in transit (e.g., NFS with Kerberos, SSH/SFTP, Linux SMB clients).
- Mention Linux file share encryption options alongside SMB 3.0 for Windows.
- Provide parity in describing how Linux VMs interact with Azure storage and encryption features.
- Include Linux/macOS-specific best practices for client-side encryption and secret management.
- Ensure that platform-specific references (Windows, Linux, macOS) are balanced and presented together.
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 exhibits mild Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before cross-platform or Linux-friendly options (CLI, Python SDK). The 'Quickstarts' section places 'Connect with PowerShell' and 'Connect with Visual Studio' before 'Connect with CLI' and 'Connect with Azure SDK for Python', subtly prioritizing Windows workflows. There is no explicit Linux example or mention of Linux-specific tools, and no guidance for macOS users. However, CLI and Python SDK are included, which are cross-platform.
Recommendations
- Reorder the 'Quickstarts' section to present 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 for Linux/macOS users, such as installation instructions for CLI and Python SDK on those platforms.
- Include a brief section or FAQ addressing common Linux/macOS developer scenarios.
Azure Government
Azure support for export controls
...e-government/documentation-government-overview-itar.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references both Linux and Windows as underlying operating systems for Azure, but when discussing FIPS 140 validation, it specifically highlights the 'Windows FIPS validation program' and links to Windows Server documentation. There is no equivalent mention or link for Linux FIPS validation, nor are Linux-specific cryptographic modules or validation programs discussed. The ordering and linking suggest a Windows-first perspective and a reliance on Windows tools/documentation for compliance evidence.
Recommendations
- Add references and links to Linux FIPS 140 validation programs or documentation, such as those for commonly used Linux distributions (e.g., Red Hat, Ubuntu).
- Clarify that Azure services run on both Linux and Windows, and provide parity in compliance documentation for both platforms.
- Include examples or guidance for managing cryptographic modules and compliance on Linux-based Azure resources.
- Ensure that compliance features and instructions are not Windows-centric, and explicitly address Linux scenarios where relevant.