Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a strong Windows bias. The only configuration (install) script provided is a PowerShell script (Install.ps1) that installs fonts to the C:\Windows\Fonts directory and modifies the Windows registry. All examples and instructions for OS-level customization reference Windows-specific paths, tools, and patterns. There are no equivalent examples or instructions for Linux-based App Service plans, nor is there mention of how to adapt the process for Linux environments. The runtime stack example is also Windows-specific (.NET Framework 4.8), and the font installation process is exclusively tailored to Windows.
Recommendations
- Provide equivalent Linux examples, such as a Bash shell script for font installation in Linux-based App Service plans (e.g., copying fonts to /usr/share/fonts and running fc-cache).
- Clarify whether Managed Instance supports Linux plans, and if so, include instructions for both Windows and Linux scenarios.
- When showing configuration scripts, offer both PowerShell and Bash script samples, and explain any OS-specific differences.
- Mention Linux runtime stack options (e.g., .NET Core, Node.js, Python) alongside Windows examples.
- Avoid assuming C:\Windows\Fonts as the only font directory; include Linux font directories in examples and screenshots.
- Explicitly state OS limitations or requirements for features that are Windows-only.
Create Pull Request