Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1776-1800 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md
...ced-messaging/whatsapp/includes/common-setting-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-specific commands (setx) for setting environment variables and does not include equivalent instructions or examples for Linux or macOS users. This may hinder cross-platform usability and suggests a Windows-first bias.
Recommendations
- Include equivalent Linux/macOS commands (e.g., export VAR=value for bash) alongside Windows commands when instructing users to set environment variables.
- Explicitly mention that the instructions apply to Windows and provide a separate section or tab for Linux/macOS users.
- Link to or summarize official cross-platform guidance for setting environment variables.
- Review all command-line instructions to ensure parity across major operating systems.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md
...ssaging/whatsapp/includes/common-setting-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-specific commands (using 'setx' to set environment variables) for environment setup, with no equivalent Linux/macOS instructions. There are no bash or cross-platform examples for setting environment variables, and Windows tools and patterns (such as referencing Visual Studio) are mentioned exclusively or before any Linux alternatives.
Recommendations
- Provide equivalent Linux/macOS commands for setting environment variables (e.g., 'export VAR=value' for bash).
- Include a cross-platform section or table showing how to set environment variables on Windows, Linux, and macOS.
- Avoid referencing only Windows-specific tools (like Visual Studio) or, if mentioned, also reference popular Linux/macOS editors (e.g., VS Code, JetBrains Rider).
- Ensure all setup instructions are inclusive of all major platforms, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/interactive/messages-quickstart-interactive-messages-net.md
...active/messages-quickstart-interactive-messages-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by listing Visual Studio (a Windows-centric IDE) first in the prerequisites and in the 'Run the code' section. While Visual Studio Code and .NET CLI (both cross-platform) are mentioned, there are no explicit Linux/macOS setup or run instructions, nor are any Linux-specific considerations or examples provided. All code examples are in C#/.NET, which is cross-platform, but the workflow and tooling references lean toward Windows.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions for installing the .NET SDK and running the code (e.g., using terminal commands, package managers like apt, yum, or Homebrew).
- Include a 'Run the code on Linux/macOS' tab or section alongside Visual Studio and .NET CLI, with steps for building and running from a Linux/macOS terminal.
- Clarify that Visual Studio Code and .NET CLI are fully supported on Linux/macOS, and provide links to installation guides for those platforms.
- If any platform-specific issues or configurations exist (e.g., environment variables, permissions), document them explicitly.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/connect-whatsapp-business-account.md
...essaging/whatsapp/connect-whatsapp-business-account.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the prerequisites section, where links for setting up event subscriptions and obtaining phone numbers explicitly use Windows-specific tabs or pivots (e.g., '?tabs=windows'). There are no Linux or cross-platform command-line examples or instructions provided, and no mention of Linux tools or workflows. The documentation assumes a Windows environment by default and does not offer parity for Linux users.
Recommendations
- Provide Linux-specific instructions or examples alongside Windows instructions, especially for steps involving Azure CLI, PowerShell, or other command-line tools.
- Ensure that links to Azure documentation use neutral or cross-platform pivots (e.g., '?tabs=cli' or '?tabs=bash') or provide both Windows and Linux tabs.
- Explicitly mention when a step is platform-agnostic, or clarify any platform-specific requirements.
- Include screenshots or terminal outputs from Linux environments where applicable.
- Review all referenced documentation to ensure Linux users have clear, equivalent guidance for each step.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/download-media/download-media-full-example-net.md
...udes/download-media/download-media-full-example-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides file path examples exclusively in Windows format (e.g., '@"c:\temp\media.jpg"'), with no mention of Linux or cross-platform file paths. There are no Linux or POSIX-style file path examples, and no guidance for users on non-Windows systems.
Recommendations
- Include Linux/Unix-style file path examples (e.g., '/tmp/media.jpg') alongside Windows examples.
- Add a note explaining that file paths are platform-dependent and provide guidance for both Windows and Linux users.
- Consider using Path.Combine or similar cross-platform APIs in code examples to construct file paths in a platform-agnostic way.
- Explicitly mention cross-platform compatibility and test the code on both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/reactions/messages-quickstart-reaction-messages-net.md
...reactions/messages-quickstart-reaction-messages-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by presenting Visual Studio (a Windows-centric IDE) instructions first and in more detail, while not providing explicit Linux-specific guidance or examples. Although Visual Studio Code and .NET CLI are cross-platform, there is no mention of Linux-specific setup, terminal commands, or troubleshooting, and the initial focus on Visual Studio may implicitly prioritize Windows users.
Recommendations
- Add explicit Linux (and macOS) instructions for building and running .NET applications, such as using the terminal or common Linux editors.
- Include a section or note confirming that all steps and code are cross-platform, and provide troubleshooting tips for Linux users (e.g., installing .NET SDK on Ubuntu).
- Reorder the 'Run the code' tabs to start with .NET CLI or Visual Studio Code, which are cross-platform, before Visual Studio.
- Mention Linux package managers (e.g., apt, yum) for .NET SDK installation in the prerequisites or setup section.
- Provide example terminal commands using bash/zsh where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/stickers/messages-quickstart-sticker-messages-net.md
...s/stickers/messages-quickstart-sticker-messages-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by providing explicit instructions for compiling and running code in Visual Studio (a Windows-centric IDE) before mentioning Visual Studio Code and .NET CLI, which are cross-platform. There are no Linux-specific instructions or examples, and no mention of Linux tools, shells, or environment nuances. The documentation assumes familiarity with Windows development patterns and omits any Linux or macOS-specific guidance.
Recommendations
- Add explicit instructions for running the code on Linux and macOS, such as using the terminal or shell.
- Include a section or tab for common Linux development environments (e.g., Ubuntu, Fedora) and how to install .NET SDK if not already present.
- Mention that Visual Studio Code and .NET CLI are cross-platform and provide links or notes for Linux/macOS users.
- If there are any OS-specific considerations (e.g., environment variable setup, file permissions), document them.
- Consider reordering the 'Run the code' section to present .NET CLI or Visual Studio Code (cross-platform tools) before Visual Studio (Windows-only).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/chat/includes/chat-logic-app.md
...n-services/quickstarts/chat/includes/chat-logic-app.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes steps using Power Automate and Logic Apps, which are Microsoft-centric tools primarily available on Windows or via the Azure portal. There are no examples or instructions for performing equivalent tasks using Linux-native tools, command-line interfaces, or automation frameworks (e.g., Azure CLI, Bash scripts). The workflow assumes a graphical, portal-based, or Windows-oriented automation environment, with no mention of Linux or cross-platform alternatives.
Recommendations
- Provide equivalent instructions using Azure CLI or REST API calls that can be executed from Linux, macOS, or Windows.
- Include Bash or shell script examples for common tasks such as creating users, chat threads, and sending messages.
- Mention cross-platform tools and clarify which steps can be performed from any OS using the Azure portal or CLI.
- Explicitly state if Power Automate or Logic Apps can be accessed and used from non-Windows environments, or provide alternatives for Linux users.
- Add a section or callout for Linux/macOS users, outlining any differences or additional requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/chat/includes/chat-csharp.md
...tion-services/quickstarts/chat/includes/chat-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows a mild Windows bias by listing Windows-specific tools (Visual Studio) as a prerequisite and mentioning 'cmd, PowerShell, or Bash' in that order, with PowerShell used in the package installation example. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with Windows development patterns.
Recommendations
- List cross-platform IDEs or editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites, or clarify that Visual Studio is optional.
- When referencing terminal usage, alternate the order (e.g., 'Bash, PowerShell, or cmd') or explicitly state that all commands work on Windows, Linux, and macOS.
- Use generic shell prompts (e.g., $ or #) for command-line examples, or provide both PowerShell and Bash/zsh equivalents where relevant.
- Explicitly mention that the .NET SDK and Azure CLI are cross-platform and provide links or notes for Linux/macOS installation where appropriate.
- Include troubleshooting notes or links for Linux/macOS users, especially for common issues (e.g., file permissions, path differences).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-email-resource-az-cli.md
...kstarts/email/includes/create-email-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking exclusively to the Windows installation instructions for Azure CLI in the prerequisites. There are no explicit Linux or macOS installation links or examples, and the command examples use the 'azurepowershell-interactive' code block type, which may imply a Windows/PowerShell context, even though the commands themselves are cross-platform.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
- Use a neutral code block type (e.g., 'azurecli' or 'bash') for CLI commands to emphasize cross-platform compatibility.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS terminals.
- If any platform-specific steps exist, document them for both Windows and Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/eligible-teams-licenses.md
...cation-services/quickstarts/eligible-teams-licenses.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page describes Teams license requirements and how to check assigned licenses, but only references Microsoft-centric tools and portals (Azure portal, Microsoft 365 admin center) for license checking. There are no examples or instructions for Linux users or cross-platform CLI tools, and no mention of Linux-friendly alternatives for accessing license information.
Recommendations
- Include examples using cross-platform tools such as Microsoft Graph API via curl or other REST clients, which can be run on Linux, macOS, or Windows.
- Provide PowerShell and Azure CLI examples side-by-side, noting that Azure CLI is cross-platform.
- Explicitly mention that the Azure portal and Microsoft 365 admin center are web-based and accessible from any OS, but also offer command-line alternatives for users who prefer or require non-Windows environments.
- Add a section or note for Linux/macOS users on how to retrieve license information using supported tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/get-started-with-real-time-text.md
...voice-video-calling/get-started-with-real-time-text.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows a mild Windows bias by listing Windows (C#) terminology and class names explicitly in naming conventions and property tables, while not mentioning Linux or cross-platform .NET usage. The C# example is labeled as 'Windows', and there is no explicit mention of Linux or Linux-specific instructions, even though .NET and C# are cross-platform. There are no PowerShell or Windows-only command examples, but the documentation implicitly equates C#/.NET with Windows.
Recommendations
- Clarify that C#/.NET examples are cross-platform and can be used on Linux, macOS, and Windows.
- Rename the 'Windows (C#)' column and references to 'C# (.NET)' or 'Desktop (.NET)' to avoid conflating C# with Windows.
- If there are platform-specific differences for Linux, document them explicitly.
- Consider adding a section or note about Linux support for RTT in .NET applications, including any prerequisites or limitations.
- Ensure that any references to 'Windows' are truly Windows-specific, and otherwise use neutral, cross-platform terminology.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-az-cli.md
...cludes/create-custom-managed-domain-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently uses the 'azurepowershell-interactive' code block type for all CLI examples, which may suggest a preference for Windows/PowerShell environments. The Azure CLI installation link in prerequisites points specifically to the Windows installation page, and there are no explicit Linux or macOS instructions or examples. While the commands themselves are cross-platform, the framing and code block labeling may give the impression of Windows bias.
Recommendations
- Use neutral code block labels such as 'bash' or 'azurecli' instead of 'azurepowershell-interactive' when providing Azure CLI examples, as Azure CLI is cross-platform.
- In the prerequisites, provide installation links for Azure CLI on all supported platforms (Windows, Linux, macOS), or link to the general installation page that lets users select their OS.
- Explicitly mention that the Azure CLI commands work on Linux, macOS, and Windows, and provide at least one example of running a command in a Linux/macOS shell if there are any OS-specific considerations.
- Avoid language or structure that implies Windows is the default or primary environment for these instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-sender-username-resource-az-cli.md
...ail/includes/create-sender-username-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by linking to the Windows-specific Azure CLI installation guide and labeling all CLI code blocks as 'azurepowershell-interactive', which may imply PowerShell usage. There are no explicit Linux or macOS installation instructions or terminal examples, and the documentation does not clarify cross-platform compatibility.
Recommendations
- Provide a platform-agnostic Azure CLI installation link or include separate links for Windows, Linux, and macOS.
- Label CLI code blocks as 'bash' or 'shell' where appropriate, or clarify that the commands work in any terminal (PowerShell, Bash, etc.).
- Add explicit instructions or notes for Linux/macOS users, including any differences in command usage or environment setup.
- Ensure that all examples and instructions are clearly marked as cross-platform, or provide platform-specific sections if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-virtual-network-links.md
...ain//articles/dns/private-dns-virtual-network-links.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which subtly prioritizes Windows-centric tooling. There is also a reference to PowerShell without a corresponding explicit mention of Linux-native tools or workflows, although Azure CLI is included. No Linux-specific examples or tools are highlighted, and there are no command-line examples in the main content.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section, or present them together to avoid implying a preference.
- Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Wherever possible, provide example commands for both Azure CLI and Azure PowerShell in the main body of the documentation, not just in linked articles.
- Consider including a brief note or section about managing Azure DNS resources from Linux environments, possibly linking to relevant setup or usage guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/send-email-az-cli.md
...rvices/quickstarts/email/includes/send-email-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows instructions and links before Linux/macOS equivalents, and by linking to the Windows-specific Azure CLI installation page in the prerequisites. However, the environment variable setup provides parity across Windows, macOS, and Linux, and the main CLI examples are cross-platform.
Recommendations
- In the prerequisites, link to the general Azure CLI installation page or provide links for all major platforms (Windows, macOS, Linux) equally.
- When presenting OS-specific instructions (such as setting environment variables), rotate or randomize the order, or present Linux/macOS first in some cases to avoid always privileging Windows.
- Ensure that all examples and instructions are equally detailed for each platform, and avoid referencing Windows-specific tools (e.g., Visual Studio) without mentioning cross-platform alternatives (e.g., VS Code, JetBrains Rider).
- Consider adding a short note at the start clarifying that all instructions are available for Windows, macOS, and Linux, and that the Azure CLI is fully cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-java.md
...email/send-email-advanced/includes/attachments-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a file path example using the Windows-style path ('C:/attachment.txt') without mentioning or showing a Linux/macOS equivalent. There are no Linux or cross-platform file path examples, which may confuse or exclude non-Windows users.
Recommendations
- Include both Windows and Linux/macOS file path examples, e.g., 'C:/attachment.txt' and '/home/user/attachment.txt'.
- Add a note clarifying that file paths should be adjusted according to the user's operating system.
- Consider using a variable or placeholder (e.g., '<path-to-attachment>') in the code sample to indicate that the path is platform-dependent.
- Where possible, provide guidance or links for handling file paths in a cross-platform manner in Java.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-import-export.md
...s/blob/main//articles/dns/private-dns-import-export.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by mentioning Windows DNS and its default zone file location before discussing BIND on Linux, and by referencing Windows-specific paths and tools. However, the main CLI instructions are cross-platform and there are no PowerShell-only examples or commands. Linux is acknowledged, especially in the context of BIND, but Windows is given precedence in the order of presentation and detail.
Recommendations
- Present Linux/BIND and Windows DNS options in parallel or list BIND first, as BIND is the most common DNS server globally.
- Provide explicit example commands for obtaining zone files from both Windows DNS and BIND (e.g., show a sample BIND config snippet or a Linux command to copy the zone file).
- Avoid Windows-specific path references (like %systemroot%) without also providing Linux equivalents.
- Add a note or example for verifying DNS records using Linux-native tools (e.g., dig) alongside nslookup.
- Ensure that all instructions and examples are clearly cross-platform, and highlight any platform-specific considerations equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-resolver-endpoints-rulesets.md
...n//articles/dns/private-resolver-endpoints-rulesets.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but in the 'Next steps' section, it only references Azure PowerShell and the Azure portal for getting started, omitting Azure CLI or Linux-native tooling. This subtly prioritizes Windows-centric administration patterns and may leave Linux users without clear guidance. There are no explicit PowerShell-heavy examples or exclusive mentions of Windows tools, but the ordering and omission indicate a Windows-first bias.
Recommendations
- Add explicit Azure CLI examples and links alongside Azure PowerShell in the 'Next steps' section to ensure Linux parity.
- Wherever administrative tasks are referenced, provide both PowerShell and CLI (Bash) command examples, or at least mention both options.
- Review any screenshots or UI references to ensure they are not exclusively Windows-oriented, and add notes for cross-platform compatibility where relevant.
- Consider including a section or note on managing Azure DNS Private Resolver from Linux/macOS environments, referencing appropriate tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/send-email-python.md
...rvices/quickstarts/email/includes/send-email-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by providing only Windows-style commands for activating the Python virtual environment ('.\Scripts\activate') and omitting the equivalent Linux/macOS command ('source ./bin/activate'). No explicit Linux or macOS instructions or examples are given for environment setup, which may confuse or slow down non-Windows users.
Recommendations
- Include both Windows and Linux/macOS commands for activating the Python virtual environment. For example, show both '.\Scripts\activate' (Windows) and 'source ./bin/activate' (Linux/macOS).
- Explicitly mention that the instructions apply to all platforms, and provide notes or tabs for platform-specific steps when necessary.
- Review other steps (such as file path conventions) to ensure they are platform-neutral or provide alternatives for non-Windows users.
- Consider adding a short section or note confirming cross-platform compatibility and linking to Python documentation on virtual environments for different operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md
...d-email-advanced/send-email-with-inline-attachments.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides explicit pivots for PowerShell and Azure CLI, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There is no explicit mention of Linux-specific tools or shell examples, and PowerShell is often associated with Windows-first workflows. No Linux shell (bash) or native Linux command-line examples are provided.
Recommendations
- Add explicit bash or Linux shell examples for sending emails with inline attachments, ensuring parity with PowerShell and Azure CLI.
- Clarify in the documentation that Azure CLI examples are cross-platform and can be used on Linux, macOS, and Windows.
- If PowerShell is included, consider also including bash/zsh shell script examples to serve Linux users.
- Where possible, avoid presenting PowerShell before or with equal prominence to cross-platform solutions unless justified by user base data.
- Add a note or section highlighting Linux compatibility and any Linux-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-overview.md
...e-docs/blob/main//articles/dns/private-dns-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing 'Azure PowerShell' as a primary tool. While the main content is generally platform-neutral and mentions both Azure CLI and PowerShell, the ordering and emphasis subtly prioritize Windows-centric tools. There are no explicit Linux tool examples or references to Linux-specific patterns, and the documentation does not provide Linux-first or Linux-only guidance.
Recommendations
- Alternate the order of Azure CLI and Azure PowerShell in 'Next steps' and other sections to avoid always listing PowerShell first.
- Explicitly mention that both Azure CLI and Azure PowerShell are cross-platform, and provide links to installation or usage guides for both Windows and Linux.
- Where examples or tool references are given, ensure parity by providing both PowerShell and CLI examples, or by linking to both sets of documentation equally.
- Consider including a brief note or section highlighting how Linux users can interact with Azure Private DNS, possibly mentioning Bash scripting or integration with Linux-native tools.
- Review other documentation pages linked from this overview to ensure Linux parity is maintained throughout the user journey.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/events/includes/create-event-subscription-net.md
...tarts/events/includes/create-event-subscription-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on .NET and C# code samples, which are cross-platform but traditionally associated with Windows development. There are no explicit references to Windows-only tools or PowerShell, but the lack of Linux/macOS-specific instructions, shell commands, or parity notes (e.g., for installing SDKs or managing credentials) may disadvantage Linux users. All package management and authentication steps are shown using .NET CLI and C# code, with no mention of equivalent workflows or troubleshooting for Linux environments.
Recommendations
- Add explicit notes confirming that all .NET CLI commands and code samples work identically on Linux, macOS, and Windows.
- Include Linux/macOS-specific instructions or troubleshooting tips, especially for common issues like environment variable configuration or certificate management.
- Provide shell (bash) equivalents for any command-line steps, such as installing packages or setting environment variables.
- Mention any OS-specific prerequisites or dependencies (e.g., required libraries for .NET on Linux).
- Consider including a brief section or callout for Linux/macOS users to ensure they feel equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-smtpclient.md
...send-email-smtp/includes/send-email-smtp-smtpclient.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create a new C# application. There are no Linux- or macOS-specific examples, troubleshooting tips, or notes, and all instructions are generic but implicitly assume familiarity with Windows environments. No Linux-specific tools, commands, or environment considerations are mentioned.
Recommendations
- List Bash (or 'terminal') before Windows-specific consoles (cmd, PowerShell) when describing cross-platform steps, or mention all platforms equally (e.g., 'in a terminal such as Bash, cmd, or PowerShell').
- Explicitly state that the instructions apply to Windows, Linux, and macOS, and provide any OS-specific notes if needed (e.g., file path differences, environment variable setup).
- Include troubleshooting tips or notes for Linux/macOS users, such as required dependencies or permissions.
- If referencing the Azure portal or other tools, clarify that they are web-based and not OS-specific.
- Where appropriate, provide example commands or screenshots from Linux/macOS terminals in addition to Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-no-code.md
...dentity/includes/access-tokens/access-token-no-code.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes using Azure Logic Apps and Power Automate, which are primarily accessed via web UIs and are tightly integrated with the Microsoft ecosystem. There are no examples or guidance for performing these actions using command-line tools, REST APIs, or SDKs that would be more accessible or familiar to Linux users. The workflow and screenshots are all based on the Microsoft portal and Power Automate, with no mention of Linux-friendly alternatives.
Recommendations
- Provide equivalent examples using Azure CLI, REST API, or SDKs (such as Python, Node.js, or Bash scripts) to perform user creation, token issuance, revocation, and deletion.
- Include instructions or links for automating these tasks outside of the Microsoft portal or Power Automate, making the documentation more accessible to Linux and cross-platform users.
- Explicitly mention that the described workflow is based on Microsoft tools and suggest alternative approaches for users on non-Windows platforms.
- Add a section or links to documentation for managing Azure Communication Services identities programmatically, which would benefit users who prefer or require Linux-based workflows.