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 876-900 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/schema-cscfg-networkconfiguration.md
...-extended-support/schema-cscfg-networkconfiguration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell and template deployments as the only methods for associating reserved IPs, without mentioning Linux-native tools or providing cross-platform command examples. There are no CLI (e.g., Azure CLI) or Linux shell examples, and the only tooling mentioned is PowerShell, which is historically Windows-centric.
Recommendations
- Include Azure CLI examples for all configuration and deployment tasks, especially for associating reserved IPs.
- Explicitly mention cross-platform tools (e.g., Azure CLI, Bicep) alongside or before PowerShell.
- Provide Linux shell (bash) command examples where relevant.
- Clarify that PowerShell is available cross-platform, but also offer parity with Linux-native workflows.
- Review all references to deployment tooling to ensure both Windows and Linux users are equally supported.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/non-vnet-migration.md
.../cloud-services-extended-support/non-vnet-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Portal UI steps and, in the 'Next steps' section, lists PowerShell as the only command-line migration option, with no mention of Linux CLI tools (such as Azure CLI) or Linux-specific instructions. This suggests a bias toward Windows and PowerShell users, and omits guidance for Linux administrators.
Recommendations
- Add equivalent Azure CLI (cross-platform) instructions for migration steps, alongside or before PowerShell examples.
- Include explicit mention of Linux/macOS compatibility where applicable, especially for command-line operations.
- In the 'Next steps' section, provide links to Azure CLI documentation or create a migration guide using Azure CLI.
- Ensure screenshots and UI references are not Windows-specific, or clarify that the portal experience is cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/overview.md
...//articles/cloud-services-extended-support/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows such as PowerShell and Visual Studio, both in the main text and in the 'Next steps' section. There are no explicit examples or guidance for Linux users, such as using Azure CLI or Bash scripts, and the ordering of deployment options consistently lists Windows tools before cross-platform or Linux-native alternatives. This may make it harder for Linux users to follow or feel included in the migration and deployment processes.
Recommendations
- Add explicit examples and instructions for deploying Cloud Services (extended support) using Azure CLI and Bash scripts, not just PowerShell.
- When listing deployment options, alternate or randomize the order, or explicitly mention cross-platform tools (e.g., 'Azure CLI, PowerShell, Portal, Visual Studio') to avoid always listing Windows tools first.
- Include Visual Studio Code as an alternative to Visual Studio, as it is cross-platform.
- Provide links to Linux-specific documentation or guides for common tasks such as ARM template deployment and certificate management.
- Ensure screenshots and walkthroughs include Linux terminal examples where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/post-migration-changes.md
...ud-services-extended-support/post-migration-changes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell and Visual Studio as primary tools for post-migration tasks, with no explicit Linux or cross-platform CLI examples for key operations. References to PowerShell are frequent and often listed before CLI or REST API alternatives. Visual Studio is mentioned as the default workflow for updates, and there are no Bash, Azure CLI (Linux shell), or non-Windows automation examples provided.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside or before PowerShell for all operations, especially for retrieving deployment files (.csdef, .cscfg).
- Include Bash shell script examples for automation tasks to support Linux users.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for deployment file editing and updates.
- Ensure that all references to tooling (e.g., certificate management, automation) include both Windows and Linux-compatible options.
- Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI and REST API, and provide links to relevant documentation.
- Balance the order of tool mentions (e.g., list CLI before or alongside PowerShell) to avoid 'windows_first' impression.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/schema-cscfg-file.md
...s/cloud-services-extended-support/schema-cscfg-file.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK), mentioning Visual Studio and .NET SDK tools (which are primarily Windows-centric in this context), and omitting any Linux or cross-platform equivalents for SDK installation paths or tooling. No Linux-specific instructions, examples, or file paths are provided.
Recommendations
- Include Linux and macOS equivalents for SDK installation paths (e.g., /usr/local/lib/azure-sdk or ~/.azure).
- Mention cross-platform tools or clarify if the SDK and schema files are available on non-Windows platforms.
- Provide examples or notes for configuring and validating .cscfg files using cross-platform tools or editors.
- If Visual Studio is referenced, also mention Visual Studio Code or other cross-platform IDEs.
- Explicitly state if any functionality is Windows-only, or confirm cross-platform support where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/persisting-shell-storage.md
...main//articles/cloud-shell/persisting-shell-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell commands (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, but does not offer equivalent Bash or Linux shell commands. The only command-line examples are in PowerShell, and the section 'Use PowerShell commands' is prominent, with no mention of Bash or Linux alternatives. This creates a Windows/Powershell-centric bias and may disadvantage users who prefer or use the Bash environment in Azure Cloud Shell.
Recommendations
- Provide equivalent Bash/Azure CLI commands for all PowerShell examples (e.g., show how to get file share info and unmount with Bash/CLI).
- Add a 'Use Bash commands' section alongside 'Use PowerShell commands' to ensure parity.
- When introducing commands or tools, mention both PowerShell and Bash/CLI options together, or alternate which is presented first.
- Explicitly state that both Bash and PowerShell are supported in Cloud Shell, and link to relevant documentation for each.
- Review the documentation for other implicit Windows-centric patterns (such as terminology or file paths) and ensure they are cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/schema-csdef-file.md
...s/cloud-services-extended-support/schema-csdef-file.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Windows Azure...'), mentioning the .NET SDK and Visual Studio as primary tools, and omitting any Linux or cross-platform equivalents for SDK installation paths or tooling. There are no Linux-specific instructions, examples, or references to Linux-compatible tools or file locations.
Recommendations
- Include Linux and macOS file paths for SDK installation locations alongside Windows paths.
- Mention cross-platform SDKs and tools (such as Azure CLI, VS Code, or .NET Core SDK) where applicable, not just Visual Studio.
- Add explicit notes or examples for Linux users, such as where to find schema files after SDK installation on Linux.
- Ensure that any references to tools or workflows (e.g., schema validation) include Linux-compatible alternatives.
- Consider providing a table or section that summarizes platform-specific differences for common tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/schema-csdef-webrole.md
...loud-services-extended-support/schema-csdef-webrole.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for Azure Cloud Services (extended support) WebRole schema is heavily oriented towards Windows environments. It references Windows-specific technologies (IIS 7, ASP.NET, .NET Framework), uses Windows-centric terms (certificate stores like 'CurrentUser', 'LocalMachine', and store names such as 'My', 'Root'), and describes file paths and environment variables in Windows format (e.g., %ROLEROOT%\Approot). There are no examples or mentions of Linux-based web roles, nor any guidance for Linux users. Startup tasks are described in terms of CMD/batch scripts, with no mention of shell scripts or Linux-compatible approaches.
Recommendations
- Add explicit mention of Linux support (or lack thereof) for Cloud Services (extended support) web roles, and clarify if the schema is Windows-only.
- If Linux is supported, provide parallel examples and guidance for Linux-based web roles, including startup tasks using shell scripts (.sh), Linux file paths, and environment variable conventions.
- Reference Linux web server equivalents (such as Apache or Nginx) if applicable, or clarify that IIS and .NET are Windows-specific.
- Document how certificates and local storage are handled on Linux VMs, including differences in certificate stores and file system paths.
- Ensure that all examples and attribute descriptions are platform-neutral where possible, or provide both Windows and Linux variants.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/states.md
...in//articles/cloud-services-extended-support/states.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell and Visual Studio (both Windows-centric tools) as primary deployment options, with no mention of Linux-native tools or examples. PowerShell is mentioned explicitly, and there is no reference to Azure CLI or Bash scripting, which are commonly used on Linux. The order of deployment options also places Windows tools before more cross-platform or Linux-friendly alternatives.
Recommendations
- Include Azure CLI and Bash scripting examples and links alongside or before PowerShell examples.
- Mention cross-platform deployment tools (e.g., Azure CLI, Terraform) in the 'Next steps' section.
- Reorder deployment options to avoid placing Windows tools first by default.
- Provide explicit Linux usage guidance or examples where relevant.
- Clarify which tools are cross-platform and which are Windows-only to help users choose appropriately.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/swap-cloud-service.md
.../cloud-services-extended-support/swap-cloud-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows PowerShell commands (e.g., Get-AzRole) as the only CLI example for checking role status, and by listing PowerShell and Visual Studio (both Windows-centric tools) as primary deployment options. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI), and Windows tools are mentioned before or instead of Linux alternatives.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell commands for checking role status and performing deployment operations, as Azure CLI is cross-platform.
- List deployment options in a more platform-neutral order, e.g., 'Azure portal, Azure CLI, ARM template, PowerShell, Visual Studio'.
- Explicitly mention that PowerShell and Visual Studio are Windows-centric, and provide equivalent instructions for Linux/macOS users.
- Where possible, provide screenshots or walkthroughs using cross-platform tools (Azure CLI, portal) rather than only Windows-based tools.
- Add a note or section clarifying tool/platform compatibility for all mentioned deployment and management methods.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/extensions.md
...articles/cloud-services-extended-support/extensions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows-centric bias. It references Windows-specific tools (such as PowerShell and Windows Defender), describes extension behavior only in the context of Windows Server, and omits Linux equivalents or examples. All extension descriptions and deployment instructions assume a Windows environment, with no mention of Linux-based roles or how to achieve similar functionality on Linux. The 'Next steps' section lists PowerShell and Visual Studio (both Windows-centric) before mentioning templates, and does not mention Azure CLI or Linux-based workflows.
Recommendations
- Include Linux-specific guidance for each extension, such as how to configure and use them on Linux-based roles.
- Provide Azure CLI examples alongside or before PowerShell examples, especially for deployment and configuration tasks.
- Mention Linux security tools (e.g., ClamAV) where Microsoft Antimalware/Windows Defender is referenced, or clarify if Linux is unsupported.
- Explicitly state OS support for each extension, and if Linux is not supported, make this clear to avoid confusion.
- Add references to cross-platform tools and workflows (e.g., VS Code, Azure CLI, ARM/Bicep templates) in the 'Next steps' section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/cloud-shell-predictive-intellisense.md
...les/cloud-shell/cloud-shell-predictive-intellisense.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), which are traditionally associated with Windows environments, even though Azure Cloud Shell also supports Bash. All examples, configuration steps, and customization instructions are provided exclusively for PowerShell, with no mention of Bash or Linux-native equivalents. The documentation assumes the user is using PowerShell and does not address how predictive features might work (or not) in Bash or other shells.
Recommendations
- Add equivalent sections and examples for Bash users in Azure Cloud Shell, clarifying whether predictive IntelliSense or similar features are available in Bash.
- If Bash does not support predictive IntelliSense, explicitly state this and provide links to any available Bash enhancements (e.g., bash-completion, fzf, or other suggestion tools).
- Balance the documentation by mentioning both PowerShell and Bash at the outset, making it clear which features are shell-specific.
- Provide instructions for customizing the shell experience in Bash, if possible, to achieve similar productivity improvements.
- Consider including a comparison table or FAQ addressing feature parity between PowerShell and Bash in Azure Cloud Shell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-services-extended-support/schema-csdef-workerrole.md
...d-services-extended-support/schema-csdef-workerrole.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation for Azure Cloud Services (extended support) WorkerRole schema demonstrates a Windows bias through exclusive references to Windows concepts (such as certificate store names and locations), lack of Linux-specific examples or guidance, and the use of Windows-centric terminology and patterns (e.g., CMD files, %ROLEROOT% environment variable, .NET assemblies). There are no Linux or cross-platform examples or notes, and all operational details assume a Windows environment.
Recommendations
- Add explicit guidance for Linux-based worker roles, including how certificate management, environment variables, and startup tasks differ on Linux VMs.
- Provide Linux shell script examples (e.g., Bash) alongside CMD/batch file examples for startup tasks.
- Clarify whether elements like NetFxEntryPoint and Windows certificate store references are applicable or not on Linux, and if not, suggest Linux equivalents or alternatives.
- Document any differences in file paths, environment variable expansion, and script encoding/formatting between Windows and Linux worker roles.
- Include a section or callouts for cross-platform considerations, highlighting any schema elements or behaviors that are Windows-only or have different behavior on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/features.md
...azure-docs/blob/main//articles/cloud-shell/features.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page, while describing a Linux-based environment (Azure Cloud Shell on Azure Linux), demonstrates a bias toward Windows and PowerShell in several ways. PowerShell features (such as the Azure drive and cmdlets) are given prominent, detailed coverage, and many Microsoft service integrations are described only in terms of PowerShell modules. Some tool lists and instructions mention PowerShell first or exclusively, and several Microsoft-centric tools (e.g., Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are highlighted, with no equivalent Linux-native or cross-platform alternatives discussed. While Linux tools are listed, their coverage is less detailed, and there are few, if any, Linux/Bash-specific usage examples or features highlighted.
Recommendations
- Provide parallel Bash/Linux examples for features that are described in detail for PowerShell (e.g., resource navigation, Azure drive equivalents, or common management tasks).
- Highlight cross-platform or Linux-native tools and workflows alongside PowerShell/Microsoft-centric tools, especially for Azure resource management and Microsoft service integration.
- Balance the order of tool and feature presentation so that Bash/Linux options are mentioned before or alongside PowerShell/Windows options, rather than after.
- Include more detailed descriptions or examples for Linux/Bash workflows, such as using Azure CLI, managing files, or scripting common tasks.
- Where PowerShell modules are listed for Microsoft services, mention or link to any available REST API, CLI, or open-source alternatives usable from Bash.
- Clarify when features (like the Azure drive) are PowerShell-only, and suggest Linux/Bash alternatives or workarounds where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/faq-troubleshooting.md
...blob/main//articles/cloud-shell/faq-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation displays a moderate Windows bias. PowerShell and Windows-specific features (such as the 'Azure:' drive and PowerShell provider) are discussed in detail, with Windows/Powershell examples and terminology often presented before or more prominently than Linux equivalents. In some sections, Windows tools and browser instructions are mentioned first, and PowerShell-specific features are explained without always providing equivalent Bash/Linux context.
Recommendations
- When discussing features like the 'Azure:' drive, clarify that it is a PowerShell-specific feature and provide equivalent navigation or resource access instructions for Bash users, if available.
- Ensure that Bash/Linux examples are given equal prominence and detail as PowerShell/Windows examples throughout the documentation.
- In sections where browser developer tools are referenced, include instructions for Firefox and Linux browsers alongside Edge and Chrome.
- Where possible, avoid listing Windows instructions or tools first by default; alternate the order or group by platform.
- For troubleshooting steps that use Windows-centric tools or terminology, provide Linux equivalents or note any differences in behavior.
- Explicitly state when a feature or limitation is specific to PowerShell or Windows, and offer alternative guidance for Linux/Bash users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-protect-private-zones-recordsets.md
...//articles/dns/dns-protect-private-zones-recordsets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI, and in some cases (such as record set level resource locks), only PowerShell examples are provided, with explicit notes that the Azure CLI or portal do not support the operation. There are no Linux- or Bash-specific examples or guidance, and the use of PowerShell as the primary scripting interface may be less familiar to Linux users.
Recommendations
- Wherever possible, ensure Azure CLI examples are presented before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Clearly indicate when certain operations are only possible via PowerShell, and provide alternative workflows or workarounds for Linux users (such as using Cloud Shell, which supports PowerShell Core on Linux).
- Add explicit Bash shell usage examples for Azure CLI commands, including variable assignment and command chaining, to improve accessibility for Linux administrators.
- If PowerShell is required for some operations, provide guidance on installing and using PowerShell Core on Linux, or suggest using Azure Cloud Shell, which is available in a browser and supports both Bash and PowerShell.
- Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify when the experience is the same across platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/email/email-domain-configuration-troubleshooting.md
...ts/email/email-domain-configuration-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently references the use of the nslookup tool from the Windows CMD terminal and instructs users to open 'command prompt' without mentioning Linux or macOS equivalents. There are no examples or instructions for performing the same DNS queries on Linux or macOS, and the documentation implicitly assumes a Windows environment throughout.
Recommendations
- Provide equivalent command-line instructions for Linux and macOS users, such as using 'nslookup' or 'dig' in a Unix shell/terminal.
- When referencing 'Windows CMD terminal' or 'command prompt', also mention 'Linux terminal' and 'macOS Terminal' to be inclusive.
- Include example outputs from Linux/macOS tools where screenshots or command results are shown.
- Explicitly state that the instructions apply to all platforms, or provide platform-specific sections/examples.
- Avoid implying that Windows is the default or only supported environment for these troubleshooting steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/includes/best-practices-web.md
...ation-services/concepts/includes/best-practices-web.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing platform-specific troubleshooting and UI instructions for Windows (e.g., managing camera conflicts and closing applications via the Windows taskbar), while omitting equivalent guidance for Linux users. Linux is not mentioned at all, and Linux-specific behaviors, tools, or UI patterns are not addressed, despite the cross-platform nature of web SDKs.
Recommendations
- Add Linux-specific guidance for device management, such as how to release camera devices or handle conflicts on popular Linux distributions and browsers.
- Include instructions for closing applications and stopping screen sharing on Linux desktop environments (e.g., GNOME, KDE), similar to the Windows taskbar example.
- Mention any known differences or limitations for Linux users regarding browser/device permissions, camera/microphone handling, and screen sharing.
- Ensure that all platform-specific notes (Windows, macOS, iOS, Android) are matched with Linux equivalents where applicable, or explicitly state if there are no known issues or differences on Linux.
- Where UI actions are described (e.g., right-clicking taskbar icons), provide Linux alternatives or clarify if the instructions are Windows-only.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references the MicrosoftTeams PowerShell module, which is primarily associated with Windows environments. There are no examples or instructions for Linux or macOS users, nor are cross-platform alternatives or prerequisites mentioned. The workflow assumes the user is on Windows and has access to PowerShell, leading to a strong Windows bias.
Recommendations
- Provide equivalent instructions for Linux and macOS users, including how to install and use PowerShell Core (pwsh) on those platforms.
- Clarify whether the MicrosoftTeams module is supported on PowerShell Core and, if so, provide installation and usage steps for non-Windows systems.
- Explicitly mention any platform limitations or prerequisites for running the required cmdlets.
- Consider including Bash or Azure CLI alternatives if available, or clearly state if PowerShell is the only supported method.
- Rephrase steps to be platform-neutral where possible, and avoid assuming the user is on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/teams-user/teams-shared-line-appearance.md
...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams PowerShell as the only command-line method for assigning delegates, without mentioning Linux-compatible alternatives or cross-platform command-line tools. There are no Linux-specific instructions or examples, and the only automation path described is via a Windows-centric tool (PowerShell).
Recommendations
- Provide equivalent instructions for assigning delegates using cross-platform tools, such as the Microsoft Graph API, with example commands using curl or HTTP requests.
- Explicitly state whether Teams PowerShell is available on Linux (PowerShell Core) and, if so, provide installation and usage instructions for Linux users.
- Include Linux/macOS-specific guidance or note any limitations for non-Windows platforms.
- Where possible, avoid referencing only Windows tools; instead, offer platform-agnostic alternatives or clarify the platform requirements for each method.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and the Teams Admin Center (TAC) as the only methods for configuration, without mentioning or providing equivalent Linux/macOS command-line options or cross-platform tooling. There are no examples or guidance for Linux users, and all administrative instructions assume a Windows-centric environment.
Recommendations
- Explicitly mention whether PowerShell cmdlets can be used on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
- Include equivalent instructions or examples for Linux/macOS environments, such as using Teams CLI tools, REST APIs, or Azure CLI where possible.
- Clarify if the Teams Admin Center (TAC) is web-based and accessible from any OS/browser, to avoid the impression of Windows exclusivity.
- Add a section or note addressing cross-platform administration, highlighting any differences or limitations for non-Windows users.
- Where possible, provide bash or shell script examples alongside PowerShell, or reference documentation that is OS-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/teams-user-calling.md
...cation-services/concepts/interop/teams-user-calling.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing 'Windows' as a primary supported platform in the feature matrix, but does not mention Linux as a supported platform or provide any Linux-specific guidance or examples. References to tools and APIs (such as Microsoft Entra, Microsoft Graph, and PowerShell modules) are Windows-centric, and there is no mention of Linux equivalents or instructions for Linux users. The absence of Linux in the platform support table and lack of Linux-specific instructions or troubleshooting steps indicate a lack of parity for Linux users.
Recommendations
- Explicitly state Linux support status in the platform matrix (e.g., add a 'Linux' column alongside Windows, Java (Android), Objective-C (iOS), and JavaScript).
- If Linux is supported, provide Linux-specific examples, installation instructions, and troubleshooting steps.
- Reference Linux tools and command-line patterns where relevant, not just Windows/PowerShell tools.
- If Linux is not supported, clearly state this in the documentation to set user expectations.
- Include links to Linux SDKs, dependencies, or community resources if available.
- Ensure parity in feature descriptions and DevOps/monitoring guidance for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/guest/teams-administration.md
...ervices/concepts/interop/guest/teams-administration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell modules and cmdlets for configuration tasks, listing 'Teams Admin Center or PowerShell' as the only tools for administration, and linking only to PowerShell-based configuration guides. There are no examples or mentions of Linux-compatible tools, CLI alternatives, or cross-platform scripting approaches. This may hinder Linux or macOS administrators, as PowerShell modules for Teams are not always fully supported or straightforward to use on non-Windows platforms.
Recommendations
- Include explicit guidance on using PowerShell Core on Linux/macOS, with notes on module compatibility and installation steps.
- Where possible, provide Azure CLI or Microsoft Graph API equivalents for administrative tasks, with example commands.
- Add a section or table comparing cross-platform administration options (Teams Admin Center, PowerShell, CLI, Graph API), highlighting which are supported on Linux.
- Ensure that links to configuration guides include both PowerShell and non-Windows alternatives, or at least clarify platform support.
- Consider adding sample scripts or walkthroughs for Linux/macOS environments, especially for common administrative scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-protect-zones-recordsets.md
...lob/main//articles/dns/dns-protect-zones-recordsets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While both Azure PowerShell and Azure CLI examples are provided for most operations, PowerShell (a Windows-centric tool) is consistently mentioned and shown first. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the CLI examples are not contextualized for Linux users. Additionally, for some advanced operations (like record set level resource locks), only PowerShell is supported and shown, with no Linux alternative or workaround discussed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid reinforcing a Windows-first perspective.
- Explicitly mention that Azure CLI is cross-platform and provide bash/zsh-friendly CLI examples, including notes on shell compatibility.
- Where PowerShell is the only supported method (e.g., record set level resource locks), clearly state the limitation and, if possible, provide workarounds or roadmap information for Linux users.
- Add a section or callout for Linux/macOS users, summarizing which features are available via CLI and which require PowerShell, and link to installation guides for Azure CLI on Linux.
- Where screenshots are shown, include at least one from a Linux environment (e.g., Azure CLI in a terminal) if possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-provisioning.md
.../interop/tpe/teams-phone-extensibility-provisioning.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation refers to provisioning and administration tasks using cmdlets, which are typically associated with PowerShell and Windows environments. There are no examples or mentions of equivalent Linux or cross-platform command-line tools, nor is there guidance for non-Windows administrators. The documentation assumes the use of Windows-centric tooling for Teams administration.
Recommendations
- Provide explicit cross-platform instructions, including how to perform provisioning and authorization tasks using Azure CLI, Microsoft Graph API, or other RESTful methods that work on Linux and macOS.
- Include example commands for both PowerShell (Windows) and Bash (Linux/macOS) where applicable.
- Clarify whether the cmdlets mentioned are available via cross-platform PowerShell Core, or if there are limitations on Linux/macOS.
- Reference documentation or tools that are platform-agnostic, and avoid assuming the administrator is using Windows unless strictly necessary.
- Add a section or note addressing Linux/macOS administrators and their options for completing the same tasks.