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 page demonstrates a Windows bias primarily by providing only Azure PowerShell scripts for identifying function apps, with no equivalent Bash, Azure CLI, or Linux-native instructions. References to Visual Studio (a Windows-centric tool) are present, and there is no mention of cross-platform alternatives for publishing or managing Azure Functions. The documentation assumes the use of Windows tooling and does not address Linux/macOS users or provide parity in examples or instructions.
Recommendations
- Provide equivalent Azure CLI (az) commands and Bash scripts for identifying and managing function apps, alongside PowerShell examples.
- Explicitly mention and provide instructions for using cross-platform tools such as Visual Studio Code and Azure CLI for publishing and managing Azure Functions.
- Where Visual Studio is referenced, add guidance for Linux/macOS users, such as using VS Code or command-line deployment methods.
- Audit the documentation for other Windows-specific assumptions (e.g., file paths, environment variables) and ensure cross-platform compatibility is addressed.
- Add a section or callouts clarifying that all steps can be performed on Linux/macOS, and link to relevant cross-platform tooling documentation.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-02-11 00:00 | #366 | in_progress |
 Clean
|
| 2026-02-10 00:00 | #362 | completed |
Biased
|
| 2026-02-09 00:00 | #358 | completed |
Biased
|
| 2026-02-08 00:00 | #354 | completed |
Biased
|
| 2026-02-05 00:00 | #342 | completed |
Biased
|
| 2026-02-04 00:00 | #338 | completed |
Biased
|
| 2026-02-03 00:00 | #334 | completed |
Biased
|
| 2026-02-02 00:00 | #330 | completed |
Biased
|
| 2026-02-01 00:00 | #326 | completed |
Biased
|
| 2026-01-31 00:00 | #322 | completed |
Biased
|
| 2026-01-30 00:00 | #318 | completed |
Biased
|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-08-12 00:00 | #78 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
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)
# [.NET Framework 4.8](#tab/netframework48)