Communication Services
1044
Total Pages
900
Linux-Friendly Pages
144
Pages with Bias
13.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
656 issues found
Showing 76-100 of 656 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides PowerShell-based examples and instructions for managing Azure Communication Services domain resources. All command-line operations use PowerShell cmdlets, which are native to Windows and require additional setup or adaptation on Linux/macOS. There is no mention of Azure CLI, Bash, or other cross-platform tools, nor are Linux-specific instructions or examples provided. This creates a strong Windows bias and may hinder Linux users from following the documentation easily.
Recommendations
- Add equivalent Azure CLI examples for all operations (e.g., provisioning, managing, verifying, and deleting domain resources).
- Include instructions for installing and using Azure CLI on Linux/macOS.
- Clearly indicate cross-platform compatibility for each tool and command.
- Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
- Provide troubleshooting notes for Linux users regarding PowerShell module installation (if relevant) and alternatives.
Create Pull Request
Communication Services
Add custom verified email domains
...vices/quickstarts/email/add-custom-verified-domains.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is presented as a primary automation option, and Windows-based DNS instructions are referenced for 'Other (General)' CNAME record creation. There is no mention of Linux-specific tools or shell examples (e.g., Bash, dig, nsupdate) for DNS record management, nor are Linux-native instructions provided for DNS changes. The structure and references prioritize Windows tools and workflows, with Linux parity lacking.
Recommendations
- Add Linux/Bash examples for DNS record creation and verification (e.g., using dig, nsupdate, or editing BIND zone files).
- Include instructions for managing DNS records on Linux-based DNS servers, not just Windows DNS Manager.
- Provide parity in automation examples (e.g., Bash scripts, Azure CLI commands run from Linux) alongside PowerShell.
- Reference Linux-friendly documentation links for 'Other (General)' DNS providers, not only Windows-based DNS.
- Explicitly mention cross-platform compatibility and highlight any differences or caveats for Linux users.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell module for all resource management tasks. There are no examples or instructions for Linux users, such as using Azure CLI or Bash, nor is there mention of cross-platform alternatives. The documentation assumes a Windows environment and does not address Linux or macOS usage.
Recommendations
- Add equivalent Azure CLI examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include installation instructions for Azure CLI alongside Azure Az PowerShell.
- Explicitly mention that PowerShell is available on Linux and macOS, or provide Bash script examples where appropriate.
- Reorder sections or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric examples.
- Reference documentation for both PowerShell and CLI resource group/tag management.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or instructions for Linux or cross-platform alternatives such as Azure CLI, Bash, or scripting on macOS. The documentation assumes the use of Windows tools and patterns throughout, without mentioning Linux equivalents or providing parity.
Recommendations
- Add Azure CLI examples for all operations (login, resource creation, management, deletion) alongside PowerShell commands.
- Explicitly state cross-platform compatibility and provide instructions for Linux/macOS users, including installation steps for required tools.
- Mention and link to relevant Linux documentation or guides where appropriate.
- Reorganize sections to present cross-platform or Linux alternatives before or alongside Windows/PowerShell instructions, rather than only after or not at all.
- Clarify that PowerShell Core is available on Linux/macOS, if relevant, and provide usage notes.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a bias toward Windows environments and tooling. All code examples and instructions are exclusively for C#/.NET, with commands and workflows centered around the dotnet CLI. Console instructions mention Windows tools (cmd, PowerShell) before Bash, and there are no Linux-specific examples, troubleshooting steps, or parity notes. No mention is made of Linux package managers, shell environments, or platform-specific considerations for running .NET applications on Linux.
Recommendations
- Explicitly mention Linux and macOS as supported platforms for .NET Core and the Email SDK.
- Provide example commands for common Linux shells (e.g., bash, zsh) and include screenshots or terminal output from Linux environments.
- Add troubleshooting notes for Linux users, such as permissions, environment variable setup, and dependency installation.
- Reference Linux package managers (apt, yum, etc.) for installing .NET Core, or link to official instructions for Linux installations.
- Ensure that instructions for running and building the app use generic terms like 'terminal' or 'command line', and avoid listing Windows tools first.
- Include a sample workflow or code snippet for sending email from a Linux-based environment, possibly in a Docker container.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments. Examples and instructions are centered around the .NET SDK and C#, which are traditionally Windows-centric, though .NET Core is cross-platform. Terminal instructions mention 'cmd' and 'PowerShell' before 'Bash', and all code samples are in C#. There are no explicit Linux-specific instructions, troubleshooting, or examples, and no mention of Linux package managers or environment setup. The documentation does not provide parity for Linux users in terms of environment setup, code execution, or common Linux workflows.
Recommendations
- Explicitly mention Linux and macOS compatibility for .NET Core and the SDK.
- Provide Linux-specific instructions for environment setup, such as using apt, yum, or Homebrew to install .NET Core.
- Include Bash/Zsh terminal examples and troubleshooting steps for Linux users.
- Clarify that all commands (dotnet new, dotnet build, dotnet run) work on Linux and macOS as well as Windows.
- Add a section for common issues on Linux (e.g., permissions, environment variables) and how to resolve them.
- Consider providing sample code in additional languages that are popular on Linux (e.g., Python, Java) if supported by the service.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell for all examples and instructions, with explicit references to Windows PowerShell and Windows-centric commands. There are no examples or guidance for Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API), and the prerequisite steps assume a Windows environment. This creates a strong Windows bias and limits accessibility for users on Linux or macOS.
Recommendations
- Add equivalent examples using Azure CLI, Bash, or REST API to support Linux and macOS users.
- Include installation instructions for Azure PowerShell on Linux and macOS, or mention cross-platform compatibility.
- Present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
- Clearly indicate which steps or commands are Windows-specific and provide alternatives for other operating systems.
- Add a section or links for sending email using SDKs (e.g., Python, Node.js) for broader platform support.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing any Linux-specific instructions or examples. All code samples and instructions assume the use of .NET and C#, which are cross-platform, but the terminal instructions and environment setup are described in a way that prioritizes Windows users. There are no Linux-specific troubleshooting tips, nor are there examples using common Linux mail tools or alternative programming languages popular on Linux.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console windows.
- Provide explicit instructions for installing .NET Core on Linux distributions (e.g., Ubuntu, Fedora) and macOS.
- Include Linux-specific terminal commands (e.g., using 'ls' instead of 'dir', or showing how to check .NET installation with 'dotnet --version' in Bash).
- Add troubleshooting notes for common Linux issues (e.g., firewall, SSL certificates).
- Mention or provide examples using alternative SMTP libraries or languages commonly used on Linux (e.g., Python's smtplib, sendmail command-line usage).
Communication Services
Send an email using SMTP
...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (commonly used in .NET/Windows environments) and Windows PowerShell, but does not include equivalent Linux or cross-platform examples (such as using Python, Bash, or Linux command-line tools). The explicit mention of 'Windows PowerShell' and lack of Linux alternatives suggests a Windows-centric bias.
Recommendations
- Add examples using Linux-native tools, such as sendmail, mailx, or mutt.
- Include cross-platform scripting examples, e.g., using Python's smtplib or Node.js.
- Provide guidance for sending emails via SMTP from Bash or other Linux shells.
- Ensure that examples and instructions are clearly marked as Windows-specific where appropriate, and offer Linux equivalents side-by-side.
- Consider reordering or grouping examples so that Windows and Linux options are presented equally.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use PowerShell syntax and commands, and the prerequisite instructions specifically mention 'windows powershell' without any reference to Linux or cross-platform alternatives. There is no mention of Bash, Azure CLI, or how to use the Azure Communication Services module on Linux or macOS. The installation and usage instructions are exclusively tailored to Windows environments and tools.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and works on Linux and macOS.
- Provide instructions for installing and using Azure PowerShell on Linux and macOS, including any prerequisites or differences.
- Include Bash or shell script examples for common tasks, such as sending emails or handling attachments.
- Explicitly state platform compatibility for the Azure Communication Services PowerShell module and clarify any limitations.
- Reorganize the documentation so that cross-platform or platform-neutral instructions appear before or alongside Windows-specific guidance.
- Add a section addressing how to use the service from Linux and macOS, including troubleshooting tips for non-Windows environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell commands and examples, which are most commonly associated with Windows environments. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform scripting approaches. All instructions and code samples assume the use of PowerShell, and there is no mention of how to perform these tasks on Linux or macOS systems.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
- Include installation instructions for Azure CLI and note its cross-platform compatibility.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify if Windows PowerShell is required.
- Provide Bash shell examples for common tasks, where possible.
- Reorder prerequisites and examples to present cross-platform tools (like Azure CLI) before or alongside PowerShell.
- Add a section discussing platform compatibility and tool choice for different operating systems.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell commands and referencing Windows-centric tools and patterns. All examples are provided in PowerShell syntax, with no mention or examples of equivalent Azure CLI or Bash commands that would be more familiar to Linux or macOS users. The installation and management instructions focus solely on PowerShell modules and workflows, and there is no guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for all resource creation and management tasks.
- Include installation instructions for the Azure CLI and relevant modules on Linux and macOS.
- Clearly indicate cross-platform compatibility for each command or tool.
- Provide Bash or shell script examples alongside PowerShell commands.
- Reorganize the documentation so that platform-agnostic or CLI-based instructions appear before or alongside Windows/PowerShell-specific guidance.
Communication Services
Set up and create access tokens for Teams users
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments, particularly in the administrator troubleshooting section. PowerShell is exclusively used for command-line instructions, with no mention of Linux shell equivalents or cross-platform alternatives. The guidance for installing and using the Microsoft Graph module is Windows/PowerShell-centric, and there is no discussion of how to perform these steps on Linux or macOS. The initial application example is a .NET console application, which is most commonly associated with Windows, and this is presented before other language pivots. Overall, Linux users are left without clear instructions for key administrative tasks.
Recommendations
- Provide equivalent Linux/macOS instructions for administrative tasks, such as using Azure CLI or Microsoft Graph CLI for service principal creation and consent.
- Include bash or shell script examples alongside PowerShell commands, or reference cross-platform tools.
- Clarify which steps are platform-agnostic and which require OS-specific tooling, and offer alternatives where possible.
- Ensure that troubleshooting steps do not assume a Windows environment; mention how Linux administrators can perform the same actions.
- Consider presenting language pivots in a neutral order or highlighting cross-platform options first.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides command-line instructions for both Windows Command Prompt and PowerShell, but does not include any explicit Linux or macOS shell examples (e.g., Bash). Windows-specific shells are mentioned first and exclusively, which may suggest a bias toward Windows users and leave Linux users without tailored guidance.
Recommendations
- Add Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell, especially for Maven commands.
- Explicitly mention that the instructions apply to Linux/macOS terminals where appropriate, and clarify any differences (such as quoting or path separators).
- Ensure that all command-line instructions are cross-platform or provide platform-specific notes for Linux/macOS users.
- Consider listing Bash examples first or equally with Windows examples to avoid implicit prioritization.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific terminals (cmd, PowerShell) before Bash, and by not providing any Linux-specific instructions or examples (such as shell commands for environment variable setup or OS-specific notes). All command-line examples use dotnet CLI, which is cross-platform, but there is no mention of Linux-specific considerations, nor are Linux tools or patterns discussed. The page assumes familiarity with Windows environments and omits parity for Linux users.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions for setting environment variables (e.g., export AZURE_CLIENT_SECRET=...) alongside Windows examples (set AZURE_CLIENT_SECRET=...).
- List Bash or other Linux terminals first or equally alongside Windows terminals when referencing console windows.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).
- Include screenshots or terminal output examples from Linux/macOS environments.
- Clarify that all dotnet CLI commands work on Linux/macOS and Windows.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites and setup instructions. The user enablement steps reference the Microsoft 365 admin center GUI, which is Windows-centric, and mention the PowerShell cmdlet Get-CsOnlineApplicationInstance as the method for obtaining a Resource Account ObjectId, without providing an equivalent Linux or cross-platform CLI example. There are no examples using bash, Azure CLI, or other Linux-friendly tools, and no mention of Linux-specific patterns for administrative tasks.
Recommendations
- Add equivalent instructions for enabling Teams users using cross-platform tools such as Azure CLI or Microsoft Graph API, with explicit bash or shell examples.
- Provide examples for obtaining Resource Account ObjectId using REST API or Graph API, not just PowerShell.
- Clarify that administrative steps (such as license assignment) can be performed via browser on any OS, and provide links to cross-platform documentation.
- Where PowerShell is mentioned, also include bash/CLI alternatives and note platform compatibility.
- Review all tool references and ensure Linux/macOS users are given clear, supported options for each step.
Communication Services
Answer Teams Phone calls from Call Automation
...ts/tpe/teams-phone-extensibility-answer-teams-calls.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 and references for key setup steps (e.g., creating Teams resource accounts, associating resources, and hosting DevTunnels). There are no equivalent examples or instructions for Linux or cross-platform alternatives, and Windows-centric tools (PowerShell, DevTunnel CLI) are mentioned without noting their availability or usage on Linux. The documentation assumes a Windows environment for administrative tasks and command-line operations.
Recommendations
- Provide equivalent Linux shell (bash) commands and instructions for all PowerShell examples, especially for Teams resource account management and DevTunnel setup.
- Clarify whether DevTunnel CLI is available and supported on Linux/macOS, and provide installation and usage instructions for those platforms.
- Reference cross-platform tools (e.g., Azure CLI, REST API calls via curl) where possible, and offer examples for both Windows and Linux environments.
- Explicitly state platform requirements or compatibility for each tool or command, and link to platform-specific documentation when available.
- Reorder examples or provide parallel instructions so that Linux/macOS users do not need to infer or translate Windows-centric steps.
Communication Services
Quickstart - Teams interop calls on Azure Communication Services
...video-calling/get-started-teams-interop-group-calls.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the prerequisites and setup instructions. It references enabling Teams Phone and Enterprise Voice via PowerShell, and links to Teams deployment instructions that are typically Windows-centric. There are no Linux-specific instructions, nor are Linux alternatives for Teams management or deployment mentioned. The code samples themselves are platform-neutral (JavaScript/HTML), but the operational context assumes a Windows/PowerShell environment for Teams administration.
Recommendations
- Provide Linux/macOS alternatives for Teams administration tasks, such as enabling Enterprise Voice, if available (e.g., via Microsoft Graph API or web portal).
- Explicitly mention cross-platform compatibility for the sample application and clarify that the code can be run on any OS with Node.js and a browser.
- Include links or instructions for Teams deployment and management on Linux/macOS, or clarify any limitations.
- Where PowerShell is referenced, add notes or examples for using equivalent REST APIs or Azure Portal actions that are OS-agnostic.
- Review all prerequisite links to ensure they do not implicitly assume a Windows environment, or provide parity for other operating systems.
Communication Services
Quickstart - Make a call to Teams user from an iOS app
...ce-video-calling/includes/teams-user/teams-user-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by referencing Teams deployment and user enablement steps that rely on Windows-centric tools and workflows, such as linking to PowerShell-based instructions for enabling Enterprise Voice. There are no equivalent Linux or cross-platform instructions, and Windows tools are mentioned first and exclusively in the prerequisites.
Recommendations
- Provide Linux/macOS alternatives for Teams deployment and user enablement, such as CLI or web portal instructions.
- Include links or steps for managing Teams Phone licenses and Enterprise Voice enablement via the Microsoft 365 admin center (web-based), which is cross-platform.
- Explicitly state platform requirements or limitations if certain steps are only possible on Windows, and suggest workarounds or alternatives for non-Windows users.
- Where PowerShell is referenced, mention if PowerShell Core (cross-platform) can be used, and provide example commands for Linux/macOS if applicable.
Communication Services
References - How to collect verbose log from browsers
...lling/references/how-to-collect-browser-verbose-log.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and command-line examples for collecting verbose logs from browsers on Windows, using Windows file paths and tools. There are no examples or guidance for Linux or macOS users, nor are equivalent Linux commands, file paths, or browser executable locations mentioned.
Recommendations
- Add Linux and macOS instructions for launching Edge and Chrome with verbose logging, including example command lines and typical executable paths (e.g., /usr/bin/google-chrome, /usr/bin/microsoft-edge).
- Specify where log files are located on Linux/macOS systems.
- Mention any platform-specific differences in command-line arguments or log file behavior.
- Present examples for all major platforms in parallel, or clearly indicate platform-specific sections.
Communication Services
Teams Phone Extensibility
...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Most administrative and provisioning steps for Teams Phone extensibility rely on PowerShell cmdlets and Windows-centric tools (e.g., Teams PowerShell, Azure PowerShell modules, Teams Admin Center, Microsoft 365 Admin Center). All command-line examples are given in PowerShell or Azure CLI, with no mention of Linux alternatives or cross-platform compatibility. There are no examples or instructions for performing these tasks on Linux or macOS, nor any references to Bash, shell scripts, or Linux-native tools. The documentation assumes access to Windows-based admin centers and tools, and does not address how Linux users can perform equivalent operations.
Recommendations
- Provide equivalent Bash or shell script examples for all PowerShell commands, using Azure CLI and Microsoft Graph API where possible.
- Clarify which steps can be performed using cross-platform tools (e.g., Azure CLI, REST API) and which require Windows-only tools.
- Explicitly mention platform requirements for Teams Admin Center and Microsoft 365 Admin Center, and suggest browser-based alternatives if available.
- Document how to install and use Microsoft Teams PowerShell on Linux (if supported), or provide REST API alternatives for resource account provisioning and phone number assignment.
- Add a section outlining Linux/macOS workflows for provisioning, bot creation, and resource account management, including any limitations or workarounds.
- Ensure all SDK usage examples (e.g., .NET, JavaScript, Java) are platform-agnostic and clarify any platform-specific dependencies.
Communication Services
References - How to collect diagnostic audio recordings
...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing build instructions and prerequisites exclusively for Windows (Visual Studio 2022, Windows depot_tools guide), referencing only the Windows build of the unpack_aecdump tool, and omitting Linux or macOS equivalents. No Linux-specific instructions, examples, or tool references are given, and the command examples use Windows executables.
Recommendations
- Add build instructions for Linux and macOS, including required packages and dependencies (e.g., gcc/clang, Python, depot_tools for Unix).
- Reference and provide examples for unpack_aecdump usage on Linux and macOS, including the expected binary name (e.g., unpack_aecdump instead of unpack_aecdump.exe).
- Include links to Chromium's Linux/macOS build documentation alongside the Windows guide.
- Clarify any platform-specific differences in file paths, environment setup, or tool invocation.
- Ensure screenshots and examples reflect cross-platform usage where possible.
Communication Services
Automate email resource management
...nication-services/samples/email-resource-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. Most examples for resource cleanup use PowerShell commands, which are Windows-centric, and there are no equivalent Linux shell (bash) examples provided. The Azure CLI example is present but only for deleting the main communication resource, while all other cleanup operations (email service, domain) are shown exclusively with PowerShell. The structure and order of examples also prioritize Windows tools and patterns.
Recommendations
- Provide bash/Azure CLI examples for all resource management and cleanup operations, not just for deleting the main communication resource.
- Ensure that Linux-friendly commands (e.g., az CLI) are presented alongside or before PowerShell examples.
- Explicitly mention cross-platform compatibility and clarify which commands work on Windows, Linux, and macOS.
- Add a section or pivot for Linux/macOS users, demonstrating equivalent workflows using bash and Azure CLI.
- Review included files (e.g., email-resource-management-powershell.md) to ensure Linux parity in all referenced content.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell for all automation and scripting examples, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisites and instructions assume PowerShell is installed and provide Windows-centric commands (e.g., checking PowerShell version in a command prompt). There are no Linux-specific instructions, nor any examples using tools or patterns common to Linux environments. The documentation implicitly prioritizes Windows and PowerShell, potentially excluding or inconveniencing Linux and macOS users.
Recommendations
- Add equivalent Azure CLI (az) examples for all resource creation, domain management, and DNS configuration steps, as Azure CLI is cross-platform and widely used on Linux.
- Include instructions for installing and using PowerShell Core (pwsh) on Linux and macOS, or clarify that the scripts work on PowerShell Core, not just Windows PowerShell.
- Provide prerequisite checks and environment setup steps for Linux and macOS (e.g., checking PowerShell Core version, using Bash or zsh).
- Mention and link to Azure CLI documentation as an alternative to PowerShell, and explain when users might prefer one over the other.
- Where possible, use generic, cross-platform language (e.g., 'terminal' instead of 'command prompt') and avoid assuming a Windows environment.
Communication Services
Detect sensitive data using Azure AI
...ion-services/samples/email-detect-sensitive-content.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns first (e.g., 'cmd', 'PowerShell', registry queries), omitting equivalent Linux instructions or examples, and relying on Windows-centric environment variable and setup guidance. There are no explicit Linux or cross-platform setup steps, and the only terminal example for checking .NET is a Windows registry query. The authentication and environment variable instructions do not clarify Linux differences, and the screenshots and navigation instructions are tailored to the Azure Portal, which is platform-neutral, but the command-line examples are not.
Recommendations
- Provide Linux/macOS equivalents for all command-line instructions, such as using 'dotnet --list-sdks' or 'dotnet --info' instead of Windows registry queries.
- List cross-platform terminal options equally (e.g., 'cmd, PowerShell, Bash, zsh') and avoid listing Windows shells first.
- Include explicit Linux/macOS setup steps for environment variables (e.g., 'export LANGUAGE_KEY=...' in Bash/zsh).
- Add notes or code blocks showing how to check .NET installation on Linux/macOS.
- Ensure all package installation and authentication steps are platform-agnostic or have platform-specific guidance.
- Review and update screenshots and navigation instructions to clarify any platform-specific differences, if applicable.