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 151-175 of 656 flagged pages
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Visual Studio Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio for development and deployment steps, providing only Windows-centric instructions and screenshots, and omitting Linux alternatives for key actions such as project creation, building, and publishing. There are no examples or guidance for using Linux tools (e.g., VS Code, CLI-based deployment, or Linux-specific .NET workflows), nor are cross-platform considerations discussed.
Recommendations
  • Add instructions for developing and deploying the bot and chat app using cross-platform tools such as VS Code, JetBrains Rider, or the .NET CLI on Linux/macOS.
  • Include Linux/macOS-specific commands and workflows for project creation, building, and publishing (e.g., using 'dotnet publish' and Azure CLI).
  • Provide screenshots and examples for Linux environments (e.g., Ubuntu terminal, VS Code on Linux).
  • Mention prerequisites for Linux/macOS (e.g., installing .NET Core SDK, using alternative editors).
  • Clarify that Visual Studio is optional and highlight cross-platform development options.
  • Ensure that all PowerShell or Command Prompt instructions are accompanied by Bash equivalents.
GitHub Create Pull Request
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias towards Windows environments, particularly in the administrator troubleshooting section, where only PowerShell commands and Windows-specific instructions are provided for resolving service principal issues. There are no equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash), and the guidance assumes the use of PowerShell and Windows tools. The troubleshooting steps and installation instructions are Windows-centric, and alternatives for Linux or macOS administrators are missing.
Recommendations
  • Provide equivalent Azure CLI or Bash commands for service principal creation and troubleshooting, suitable for Linux/macOS environments.
  • Include installation and usage instructions for Microsoft Graph and related tools on Linux and macOS, not just PowerShell.
  • Add notes or sections clarifying cross-platform support and explicitly mention how Linux/macOS administrators can perform the same tasks.
  • Ensure that code samples and troubleshooting steps are presented in a platform-neutral way, or offer both Windows and Linux/macOS alternatives side-by-side.
  • Review other sections for implicit Windows-first assumptions and update language to be inclusive of all supported platforms.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits mild Windows bias. Console instructions mention 'cmd, PowerShell, or Bash', but list Windows shells first, and do not provide any Linux- or macOS-specific guidance or troubleshooting. All command-line examples use the generic 'dotnet' CLI, which is cross-platform, but there are no explicit Linux/macOS instructions, nor are there any notes about potential platform-specific issues. No Linux-specific tools or patterns are mentioned, and the documentation implicitly assumes a Windows environment by referencing 'cmd' and 'PowerShell' before 'Bash'.
Recommendations
  • When listing console environments, alternate the order or explicitly state that all commands work identically on Windows, Linux, and macOS.
  • Add a note confirming that the .NET CLI commands are cross-platform and provide any necessary prerequisites or troubleshooting for Linux/macOS users (e.g., permissions, installing .NET SDK on Linux).
  • Include at least one explicit example of running the commands in a Linux/macOS terminal, or provide screenshots/terminal output from those platforms.
  • If there are any platform-specific caveats (such as file path separators, environment variable syntax, or permissions), document them clearly.
  • Consider linking to .NET installation instructions for Linux and macOS, not just the generic download page.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command examples specifically for Windows environments, including both Command Prompt and PowerShell, but does not include any explicit examples for Linux or macOS shells (e.g., Bash). This may lead Linux/macOS users to feel unsupported or uncertain about command syntax and usage. The documentation also lists Windows command-line tools before PowerShell, and omits Linux equivalents entirely.
Recommendations
  • Add explicit Linux/macOS shell (Bash) command examples alongside Windows Command Prompt and PowerShell examples.
  • Clarify that Maven commands are cross-platform and provide any necessary syntax differences for Linux/macOS (e.g., use of single vs double quotes, path separators).
  • Include instructions for installing Maven and Java on Linux/macOS, or link to relevant guides.
  • When listing command examples, present Bash (Linux/macOS) first or alongside Windows examples to avoid perceived prioritization.
  • Add a note indicating cross-platform compatibility and any platform-specific caveats.
GitHub Create Pull Request
Communication Services Prerequisites ...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 mentioning Bash, and by omitting explicit Linux/macOS terminal instructions or examples. All command-line instructions use generic 'dotnet' commands but do not clarify Linux-specific nuances (such as environment variable setup or file system differences). No Linux-specific tooling or troubleshooting is mentioned, and the sample code is exclusively for .NET/C#, which is more common on Windows.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when referencing console windows.
  • Provide explicit Linux/macOS instructions for setting environment variables (e.g., 'export AZURE_CLIENT_SECRET=...') and running commands.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET installation paths).
  • Reference Linux/macOS package managers for .NET installation (e.g., apt, brew).
  • Add a note or section on cross-platform compatibility and any OS-specific caveats.
GitHub Create Pull Request
Communication Services Answer Teams Phone calls from Call Automation ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell commands for key setup steps (e.g., creating Teams resource accounts, associating resources, and hosting DevTunnels). There are no equivalent Linux shell (bash) or cross-platform CLI examples, and Windows-centric tools (PowerShell, DevTunnel CLI) are referenced without mention of Linux alternatives or usage patterns. The ordering and focus of examples assume a Windows environment, potentially excluding Linux users.
Recommendations
  • Provide equivalent bash or shell commands for all PowerShell examples, especially for resource account creation and association.
  • Clarify whether DevTunnel CLI is cross-platform and, if so, provide explicit Linux/macOS installation and usage instructions.
  • Reference cross-platform Azure CLI commands where possible, or note platform-specific limitations.
  • Include notes or links for Linux users on how to perform prerequisite steps (e.g., Teams resource account creation) using REST APIs, Azure CLI, or other non-Windows tools.
  • Ensure that examples and instructions are presented in a platform-neutral manner, or clearly indicate when a step is Windows-specific.
GitHub Create Pull Request
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 →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and setup instructions. The process for enabling a user for Teams is described exclusively via the Microsoft 365 admin center GUI, which is a Windows-centric tool. Additionally, the only command-line reference for obtaining a Resource Account ObjectId is via the Get-CsOnlineApplicationInstance PowerShell cmdlet, with no mention of equivalent Graph API or CLI commands for Linux/macOS users. There are no examples or instructions for performing these steps using Linux-native tools, and Windows tools are referenced first and exclusively.
Recommendations
  • Include instructions for enabling Teams users via Microsoft Graph API or Azure CLI, which are cross-platform and accessible from Linux/macOS.
  • Provide examples for obtaining Resource Account ObjectId using REST API or Graph API, not just PowerShell.
  • Clarify that the admin center is web-based and accessible from any OS, but also offer CLI/API alternatives for automation and parity.
  • Ensure all command-line examples are provided for both Windows (PowerShell) and Linux/macOS (bash, curl, az CLI) where applicable.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a significant Windows bias. Most administrative and provisioning steps rely on PowerShell cmdlets and Windows-centric tools (Teams PowerShell, Azure PowerShell modules, Teams Admin Center, Microsoft 365 Admin Center). There are no Linux or cross-platform CLI alternatives provided for key operations such as resource account provisioning, phone number assignment, or bot creation. Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST endpoints for all administrative steps currently shown only with PowerShell.
  • Explicitly document which steps can be performed on Linux/macOS and provide instructions for those platforms.
  • Highlight any platform limitations and suggest workarounds or alternatives for non-Windows environments.
  • Include references to Teams and Microsoft 365 admin operations that can be performed via browser (where possible), and clarify OS requirements for each step.
  • Add sample scripts or code snippets using bash, curl, or other Linux-friendly tools for provisioning and configuration tasks.
GitHub Create Pull Request
Communication Services Quickstart - Teams interop calls on Azure Communication Services ...video-calling/get-started-teams-interop-group-calls.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits Windows bias in several ways. The prerequisites and instructions reference Windows-centric tools and patterns, such as Teams deployment links that point to Windows installation guides, and enabling Enterprise Voice via PowerShell (a Windows-only tool). There are no Linux-specific instructions or examples for Teams deployment, user management, or enabling features. The documentation does not mention Linux alternatives or provide parity for Linux administrators, and Windows tools (PowerShell, Azure portal screenshots) are referenced exclusively or before any cross-platform options.
Recommendations
  • Include Linux-specific instructions for Teams deployment and management, such as using Teams on Linux or managing users via cross-platform CLI tools.
  • Provide examples for enabling Enterprise Voice using Microsoft Graph API or other cross-platform methods, not just PowerShell.
  • Reference Azure portal and Graph API as primary methods for user management, with PowerShell as an alternative, not the default.
  • Add notes or sections clarifying which steps are platform-agnostic and which require Windows, and suggest alternatives for Linux/macOS users.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux where possible.
GitHub Create Pull Request
Communication Services References - How to collect verbose log from browsers ...lling/references/how-to-collect-browser-verbose-log.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Windows-specific instructions and examples for collecting verbose logs from browsers, including hardcoded Windows paths and references to Windows command line usage. There are no examples or guidance for Linux or macOS users, and only Windows tools and patterns are mentioned.
Recommendations
  • Add equivalent instructions for Linux and macOS, including example command lines using typical browser executable paths (e.g., /usr/bin/google-chrome, /usr/bin/microsoft-edge).
  • Specify how to locate log files on Linux and macOS, including default directories and file names.
  • Mention platform-specific considerations, such as using terminal instead of command prompt, and adjusting file paths and permissions.
  • Present examples for all major platforms side-by-side or in separate sections to ensure parity.
GitHub Create Pull Request
Communication Services References - How to collect diagnostic audio recordings ...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 instructions, .exe output), without mentioning Linux or macOS equivalents. There are no Linux-specific build steps, tools, or examples, and the use of Windows-centric tools and file extensions is emphasized.
Recommendations
  • Add Linux and macOS build instructions for unpack_aecdump, including required dependencies (e.g., gcc/clang, Python, depot_tools installation for Unix-like systems).
  • Reference the official Chromium/Linux build documentation for setting up the environment.
  • Show example commands for building and running unpack_aecdump on Linux (e.g., outputting an ELF binary, using ./unpack_aecdump).
  • Clarify any platform-specific differences in file paths, permissions, or tool usage.
  • Ensure screenshots and file references are not Windows-specific, or provide cross-platform alternatives.
GitHub Create Pull Request
Communication Services Detect sensitive data using Azure AI ...ion-services/samples/email-detect-sensitive-content.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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, such as registry queries and Windows-centric environment setup. Examples and instructions (e.g., checking .NET installation) use Windows commands and registry paths, with no Linux equivalents or parity. The terminal examples mention 'cmd' and 'PowerShell' before 'Bash', and links to Azure quickstarts use Windows tabs by default. There are no Linux-specific instructions or troubleshooting notes, and the overall workflow assumes a Windows environment.
Recommendations
  • Provide Linux equivalents for Windows-specific commands, such as using 'dotnet --list-sdks' or 'dotnet --info' to check .NET installation on Linux/macOS.
  • List terminal options in a neutral order (e.g., 'cmd, PowerShell, Bash') or mention Bash first to avoid Windows-first bias.
  • Add troubleshooting notes for Linux users, such as setting environment variables and file path conventions.
  • Ensure all quickstart links and code samples include Linux/macOS tabs or instructions, not just Windows.
  • Include screenshots or instructions for Azure portal steps that are OS-agnostic, and clarify any OS-specific differences.
  • Explicitly state cross-platform compatibility for all steps and tools used.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation examples and instructions. All code samples are written in PowerShell, and the prerequisite checks and installation links prioritize Windows (e.g., 'install-azps-windows', 'install-azure-cli-windows'). There are no Bash, shell script, or Linux/macOS terminal equivalents provided, nor are there any instructions or examples for running the automation on non-Windows platforms. This limits accessibility and usability for users on Linux or macOS.
Recommendations
  • Provide equivalent Bash or shell script examples for all automation steps, using standard Bash syntax and tools.
  • Include installation instructions and links for Azure CLI and PowerShell on Linux and macOS, not just Windows.
  • Add a section or callouts explaining how to adapt the PowerShell scripts for Bash or other shells, including variable handling and error management.
  • Where possible, use cross-platform scripting approaches (e.g., plain Azure CLI commands in Bash) rather than PowerShell-specific constructs.
  • Explicitly state platform compatibility and requirements for each example, and offer guidance for users on non-Windows systems.
GitHub Create Pull Request
Communication Services Tutorial - Prepare a web app for Azure Communication Services (Node.js) ...communication-services/tutorials/building-app-start.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing setup instructions and examples primarily for Windows users. The Node.js, nvm, and npm installation section links only to a Windows-specific tutorial, and PowerShell commands are used for nvm operations without Linux/macOS equivalents. File path examples use Windows conventions (e.g., C:\Users\Documents\ACS\CallingApp), and there is no mention of Linux or macOS terminal commands or installation steps. This may make it harder for Linux/macOS users to follow the tutorial.
Recommendations
  • Add explicit instructions and links for installing Node.js, nvm, and npm on Linux and macOS (e.g., link to https://github.com/nvm-sh/nvm for nvm installation on Unix-like systems).
  • Provide equivalent shell commands (bash/zsh) for nvm usage, such as 'nvm install 12.20.0' and 'nvm use 12.20.0', and clarify that these work on Linux/macOS.
  • Include Linux/macOS file path examples (e.g., ~/ACS/CallingApp) alongside Windows paths.
  • Mention that Visual Studio Code and all Azure extensions are cross-platform, and provide installation instructions for Linux/macOS.
  • Where screenshots show Windows-specific UI, note any differences for Linux/macOS users or provide alternative screenshots if possible.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by listing Visual Studio as the only required IDE, using PowerShell for package installation, and omitting Linux-friendly alternatives (e.g., VS Code, bash, or cross-platform .NET CLI instructions). No Linux-specific setup or tooling is mentioned, and all command-line examples assume a Windows context.
Recommendations
  • List cross-platform IDEs such as Visual Studio Code alongside Visual Studio in the prerequisites.
  • Provide package installation instructions using the .NET CLI (e.g., 'dotnet add package ...') in a generic shell block, not just PowerShell.
  • Explicitly mention that the SDK and tools work on Linux and macOS, and provide any relevant setup notes for those platforms.
  • If any OS-specific steps exist (e.g., environment variables, file paths), provide both Windows and Linux/macOS examples.
  • Where possible, use neutral language and tools that are not Windows-specific, or present Windows and Linux options side-by-side.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by requiring Visual Studio (a Windows-centric IDE) in the prerequisites, providing only PowerShell/dotnet CLI installation commands, and omitting any Linux/macOS-specific instructions or tooling. There are no examples or notes for Linux users regarding compatible editors, package installation, or environment setup. The focus on Windows tools and the absence of Linux alternatives or parity in setup steps may hinder cross-platform adoption.
Recommendations
  • In the prerequisites, mention that .NET development can be done on Linux and macOS, and suggest cross-platform editors like VS Code alongside Visual Studio.
  • Provide installation instructions for the Azure Communication Services Chat SDK using the dotnet CLI in a cross-platform context, and clarify that the command works on Linux/macOS terminals as well.
  • Include notes or examples for Linux/macOS users, such as using the terminal or bash shell, and reference compatible package managers or editors.
  • Avoid assuming Visual Studio is required; clarify that any .NET-compatible IDE or editor can be used.
  • Where PowerShell commands are shown, also provide equivalent bash/zsh commands if relevant, or clarify that the dotnet CLI is cross-platform.
  • Explicitly state platform compatibility in the introduction or prerequisites to reassure non-Windows users.
GitHub Create Pull Request
Communication Services What's new in Azure Communication Services ...blob/main/articles/communication-services/whats-new.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Communication Services exhibits mild Windows bias. Windows and Microsoft Teams tools are mentioned frequently, and platform-specific features often list Windows before other platforms (e.g., 'Android, iOS, and Windows'). There are several references to Windows-specific SDKs and Teams admin tools, but there are no explicit Linux or cross-platform command-line examples, nor are Linux tools or patterns mentioned. Sample code is either generic (JavaScript/C#) or references Windows, and there are no Linux-specific instructions or parity notes.
Recommendations
  • Add explicit Linux examples or instructions where platform-specific features are discussed (e.g., joining Teams meetings, SDK usage).
  • When listing supported platforms, avoid listing Windows first or exclusively; use 'Windows, Linux, and macOS' or 'all major desktop platforms' where appropriate.
  • Include parity notes for features that are not available on Linux, and provide timelines or workarounds if possible.
  • Reference cross-platform tools and patterns (such as Bash, curl, or Linux-based troubleshooting) alongside or before Windows/PowerShell equivalents.
  • Ensure that sample code and admin tool references are not exclusively tied to Windows or Teams admin tools; mention Azure portal, REST APIs, or CLI alternatives where possible.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md .../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias primarily through exclusive mention of Windows-centric tools and patterns. Specifically, emergency calling configuration is described as being performed via the Teams Admin Center (TAC) portal or PowerShell cmdlets, both of which are Windows-focused tools. No Linux equivalents or cross-platform alternatives (such as Azure CLI, REST API, or bash scripting) are mentioned, nor are examples provided for Linux environments. Windows tools are referenced before any consideration of platform neutrality, reinforcing a Windows-first approach.
Recommendations
  • Include Linux-friendly configuration options, such as using Azure CLI, REST API, or cross-platform scripting, for tasks currently described with PowerShell.
  • Provide explicit examples for both Windows (PowerShell) and Linux/macOS (bash, CLI) environments when describing administrative tasks.
  • Reference platform-neutral tools and interfaces before or alongside Windows-specific ones to avoid implying Windows is required.
  • Clarify whether the Teams Admin Center portal and PowerShell cmdlets are accessible or supported on non-Windows platforms, and suggest alternatives if not.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-powershell.md ...des/create-azure-managed-domain-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
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, which is traditionally associated with Windows environments. No examples are provided for Linux or cross-platform alternatives such as Azure CLI or Bash. The documentation assumes the use of PowerShell and Windows tools, and does not mention or prioritize Linux-compatible workflows.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (create, update, list, delete).
  • Explicitly mention cross-platform compatibility for the Azure Az PowerShell Module, or provide installation instructions for Linux/macOS if supported.
  • Include Bash or shell script examples where appropriate, especially for Linux users.
  • Reorder sections or provide parallel instructions so that Linux and Windows users are equally supported.
  • Clarify any platform-specific limitations or requirements for the tools mentioned.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp.md ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (typically .NET, often Windows-centric) and Windows PowerShell, but does not include equivalent Linux or cross-platform command-line examples (e.g., using sendmail, mailx, or Python scripts on Linux). Windows tools and patterns are emphasized, with no mention of Linux-native tools or instructions.
Recommendations
  • Add examples for sending email via SMTP using Linux command-line tools such as sendmail, mailx, or swaks.
  • Include cross-platform scripting examples, such as Python scripts that work on both Windows and Linux.
  • Ensure that the documentation explicitly mentions Linux support and provides parity in instructions for both Windows and Linux environments.
  • Consider reordering or grouping examples so that Windows and Linux instructions are presented equally, rather than Windows-first.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-java.md ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Command Prompt and PowerShell, which are Windows-specific environments, but does not include examples for Linux or macOS shells (e.g., Bash). The order of presentation puts Windows tools first, and there is no mention of Linux equivalents or instructions for running commands in a Unix-like environment. This may make it less accessible or clear for users on Linux or macOS.
Recommendations
  • Add Bash or generic shell examples alongside Command Prompt and PowerShell for all command-line instructions.
  • Explicitly mention that Maven commands can be run in Linux/macOS terminals and provide sample commands.
  • Reorder examples so that cross-platform or Linux/macOS instructions are presented first or equally with Windows examples.
  • Clarify that the steps are applicable on Linux/macOS and note any OS-specific differences if relevant.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/enable-interoperability-for-teams-tenant.md ...s/includes/enable-interoperability-for-teams-tenant.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools (PowerShell, MicrosoftTeams module), with no mention of Linux or cross-platform alternatives. All examples and instructions assume a Windows environment, omitting guidance for Linux or macOS users.
Recommendations
  • Add instructions for installing and using Microsoft Teams PowerShell module on Linux and macOS (e.g., via PowerShell Core).
  • Clarify cross-platform compatibility of the MicrosoftTeams module and provide platform-specific installation steps.
  • Include example commands for Linux/macOS environments, noting any differences in prerequisites or usage.
  • Mention alternative authentication methods if interactive login windows are not available on non-Windows platforms.
  • Explicitly state platform requirements and limitations at the start of the documentation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-interoperability-teams.md ...ices/concepts/interop/enable-interoperability-teams.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing the PowerShell Set-CsPhoneNumberAssignment cmdlet for enabling Enterprise Voice, without mentioning or providing equivalent Linux/macOS command-line options or cross-platform alternatives. The guidance assumes access to Windows tools and does not address how to perform these steps on non-Windows platforms.
Recommendations
  • Provide cross-platform instructions, such as using Azure CLI, REST API, or Microsoft Graph API, where possible.
  • Include explicit Linux/macOS examples or note any platform limitations.
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS can be used for these cmdlets, and provide installation/setup guidance if so.
  • List alternative tools or interfaces for non-Windows users to accomplish the same tasks.
  • Ensure that references to Windows-specific tools are accompanied by parity information for other platforms.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/security.md ...munication-services/concepts/interop/guest/security.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and administration patterns, such as the Microsoft Teams admin center and PowerShell, for managing Teams external user policies. There are no examples or mentions of Linux equivalents, nor are cross-platform alternatives discussed. The documentation assumes the use of Microsoft-specific tools and environments, which are primarily Windows-based.
Recommendations
  • Include instructions or examples for managing Teams external user policies using cross-platform tools or REST APIs, where available.
  • Mention whether PowerShell commands can be run on Linux or macOS, and provide guidance for those platforms.
  • Reference or link to CLI tools or SDKs that are supported on Linux for Azure Communication Services and Teams administration.
  • Explicitly state platform requirements and provide parity in examples for both Windows and Linux environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Microsoft Teams Admin Center and PowerShell as the primary methods for configuration, without mentioning Linux-compatible alternatives or providing cross-platform examples. The tools and patterns described are Windows-centric, and there is no guidance for Linux users or administrators on how to achieve similar outcomes.
Recommendations
  • Include Linux-compatible methods for configuring Teams tenant settings, such as using Azure CLI or REST APIs where possible.
  • Provide examples or references for cross-platform tools and workflows, ensuring that Linux users can follow along without relying on PowerShell or Windows-only interfaces.
  • Explicitly mention platform requirements for each tool or method, and suggest alternatives for non-Windows environments.
  • Add documentation sections or links for Linux administration of Teams and Azure Communication Services, if available.
GitHub Create Pull Request
← Previous Page 7 of 27 Next →