Document Details
Batch Task Output File Conventions
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
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a strong Windows bias. All code samples are in C# and reference the .NET File Conventions library, with no mention of Linux, cross-platform, or non-Windows development environments. The instructions and code samples assume use of Visual Studio (a Windows-centric IDE), and there are no examples or guidance for using the library or conventions from Linux environments, with other languages, or via command-line tools. References to the Azure Storage client library are specific to .NET, and there is no mention of Linux-compatible alternatives or how to implement the conventions in Linux-based Batch pools.
Recommendations
- Add explicit guidance and code samples for using the File Conventions standard from Linux environments, such as with .NET Core on Linux, or with other languages (e.g., Python, Java).
- Include instructions for setting up and running the sample project on Linux (e.g., using VS Code, JetBrains Rider, or command-line .NET SDK), not just Visual Studio.
- Mention and provide examples for using Azure CLI, Azure Storage Explorer (which is cross-platform), or REST APIs to interact with persisted output files.
- Clarify that the File Conventions standard can be implemented in any language/environment, and link to or provide sample implementations for Linux users.
- Add a section or callout explicitly addressing Linux Batch pool scenarios and any platform-specific considerations.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-12 00:00 | #99 | completed |
Biased
|
| 2026-01-11 06:20 | #98 | completed |
Biased
|
| 2026-01-10 00:00 | #92 | completed |
 Clean
|
| 2026-01-06 22:28 | #78 | completed |
Clean
|
| 2025-12-29 18:00 | #48 | cancelled |
Biased
|
| 2025-12-15 00:00 | #7 | completed |
Clean
|
| 2025-12-14 05:05 | #6 | completed |
Clean
|
Flagged Code Snippets
TimeSpan stdoutFlushDelay = TimeSpan.FromSeconds(3);
string logFilePath = Path.Combine(
Environment.GetEnvironmentVariable("AZ_BATCH_TASK_DIR"), "stdout.txt");
// The primary task logic is wrapped in a using statement that sends updates to
// the stdout.txt blob in Storage every 15 seconds while the task code runs.
using (ITrackedSaveOperation stdout =
await taskStorage.SaveTrackedAsync(
TaskOutputKind.TaskLog,
logFilePath,
"stdout.txt",
TimeSpan.FromSeconds(15)))
{
/* Code to process data and produce output file(s) */
// We are tracking the disk file to save our standard output, but the
// node agent may take up to 3 seconds to flush the stdout stream to
// disk. So give the file a moment to catch up.
await Task.Delay(stdoutFlushDelay);
}