Document Details
Migrate Dotnet To Isolated Model
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by providing only Azure PowerShell scripts for identifying function apps, with no equivalent Bash, Azure CLI, or Linux-native instructions. The use of PowerShell as the default scripting language assumes a Windows environment or user familiarity with Windows tooling. There are no explicit Linux or cross-platform command-line examples for key operational steps, and no mention of Linux-specific considerations or parity in the migration process.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell scripts for identifying and managing function apps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, but also offer Bash or shell script alternatives for Linux users.
- Include notes or sections addressing any Linux-specific considerations for local development, deployment, or configuration (e.g., file paths, environment variables, tool installation).
- Ensure that all operational instructions (such as changing app settings or deploying code) have both Windows/PowerShell and Linux/Azure CLI examples, presented in parallel tabs or side-by-side.
- Review references to Visual Studio and clarify alternatives for Linux users, such as Visual Studio Code or command-line deployment tools.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-12 00:58 | #8 | cancelled |
 Clean
|
| 2025-07-10 05:06 | #7 | processing |
Clean
|
Flagged Code Snippets
# [.NET Framework 4.8](#tab/netframework48)
This example includes [ASP.NET Core integration] to improve performance and provide a familiar programming model when your app uses HTTP triggers. If you don't intend to use HTTP triggers, you can replace the call to `ConfigureFunctionsWebApplication` with a call to `ConfigureFunctionsWorkerDefaults`. If you do so, you can remove the reference to `Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore` from your project file. However, for the best performance, even for functions with other trigger types, you should keep the `FrameworkReference` to ASP.NET Core. # [.NET Framework 4.8](#tab/netframework48)