You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/automation-services.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ Provides a serverless, event-driven compute platform for automation that allows
155
155
156
156
- You can use a variety of languages to write functions in a language of your choice, such as C#, Java, JavaScript, PowerShell, or Python, and focus on specific pieces of code. Functions runtime is an open source.
157
157
- You can choose the hosting plan according to your function app scaling requirements, functionality, and resources required.
158
-
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable/durable-functions-overview.md?tabs=csharp).
158
+
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable-functions/durable-functions-overview.md?tabs=csharp).
159
159
- You should avoid large and long-running functions that can cause unexpected timeout issues. [Learn more](../azure-functions/functions-best-practices.md?tabs=csharp#write-robust-functions).
160
160
- When you write PowerShell scripts within the Function Apps, you must tweak the scripts to define how the function behaves, such as how it's triggered and its input and output parameters. [Learn more](../azure-functions/functions-reference-powershell.md?tabs=portal).
161
161
@@ -197,7 +197,7 @@ Provides a serverless, event-driven compute platform for automation that allows
197
197
198
198
- You can use a variety of languages to write functions in a language of your choice, such as C#, Java, JavaScript, PowerShell, or Python, and focus on specific pieces of code. Functions runtime is an open source.
199
199
- You can choose the hosting plan according to your function app scaling requirements, functionality, and resources required.
200
-
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable/durable-functions-overview.md?tabs=csharp).
200
+
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable-functions/durable-functions-overview.md?tabs=csharp).
201
201
- You should avoid large and long-running functions that can cause unexpected timeout issues. [Learn more](../azure-functions/functions-best-practices.md?tabs=csharp#write-robust-functions).
202
202
- When you write PowerShell scripts within Function Apps, you must tweak the scripts to define how the function behaves, such as how it's triggered and its input and output parameters. [Learn more](../azure-functions/functions-reference-powershell.md?tabs=portal).
Copy file name to clipboardExpand all lines: articles/azure-functions/concept-file-access-options.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ This article compares three ways to access files from Azure Functions: storage b
15
15
16
16
Storage bindings and external databases work on all hosting plans. Storage mounts are Linux only and aren't supported on the [Consumption](./consumption-plan.md) plan.
17
17
18
-
If you want to jump straight to working code, see the [Tutorial: Durable text analysis with a mounted Azure Files share](./durable/tutorial-durable-text-analysis-azure-files.md) for parallel file processing or [Tutorial: Process images by using FFmpeg on a mounted Azure Files share](./tutorial-ffmpeg-processing-azure-files.md) for hosting large binaries on a mount.
18
+
If you want to jump straight to working code, see the [Tutorial: Durable text analysis with a mounted Azure Files share](./durable-functions/tutorial-durable-text-analysis-azure-files.md) for parallel file processing or [Tutorial: Process images by using FFmpeg on a mounted Azure Files share](./tutorial-ffmpeg-processing-azure-files.md) for hosting large binaries on a mount.
@@ -132,7 +132,7 @@ Select each tab to view details about the specific scenario:
132
132
> **Use case:** You have 1,000 analysis tasks that all need to read from the same set of reference data files (for example, ML models, lookup tables, or corpus data).
133
133
134
134
> [!NOTE]
135
-
> For a complete walkthrough of this pattern, see [Tutorial: Durable text analysis with a mounted Azure Files share](./durable/tutorial-durable-text-analysis-azure-files.md).
135
+
> For a complete walkthrough of this pattern, see [Tutorial: Durable text analysis with a mounted Azure Files share](./durable-functions/tutorial-durable-text-analysis-azure-files.md).
136
136
137
137
**The problem:** Without mounts, you have two suboptimal options:
138
138
@@ -421,7 +421,7 @@ The following table lists common issues with Azure Files storage mounts on funct
421
421
## Related content
422
422
423
423
- [Tutorial: Process images by using FFmpeg on a mounted Azure Files share](./tutorial-ffmpeg-processing-azure-files.md)
424
-
- [Tutorial: Durable text analysis with a mounted Azure Files share](./durable/tutorial-durable-text-analysis-azure-files.md)
424
+
- [Tutorial: Durable text analysis with a mounted Azure Files share](./durable-functions/tutorial-durable-text-analysis-azure-files.md)
Copy file name to clipboardExpand all lines: articles/azure-functions/dotnet-isolated-in-process-differences.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Use the following table to compare feature and functional differences between th
30
30
|[Supported .NET versions](#supported-versions)| Long Term Support (LTS) versions,<br/>Standard Term Support (STS) versions,<br/>.NET Framework | Long Term Support (LTS) versions, ending with .NET 8 |
| Output binding interactions | Return values in an expanded model with:<br/> - single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)<br/> - arrays of outputs| Return values (single output only),<br/>`out` parameters,<br/>`IAsyncCollector`|
Copy file name to clipboardExpand all lines: articles/azure-functions/dotnet-isolated-process-guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -603,7 +603,7 @@ The .NET isolated worker doesn't set a custom [`SynchronizationContext`](/dotnet
603
603
Because there's no `SynchronizationContext` to suppress, using [`ConfigureAwait(false)`](/dotnet/api/system.threading.tasks.task.configureawait) in your function code has no practical effect. The isolated worker process runs as a standard .NET generic host (console app), so the same async/await behavior you'd expect in any ASP.NET Core or console application applies here. This is also true for .NET Framework (net48) isolated worker apps, since the worker process is always a console executable using `HostBuilder`.
604
604
605
605
> [!NOTE]
606
-
> [Durable Functions](./durable/durable-functions-overview.md) orchestrators have their own threading constraints. The orchestrator replay thread must run continuations, so using `ConfigureAwait(false)` in orchestrator functions or orchestrator middleware can interfere with orchestration execution. For more information, see the [Durable Functions code constraints](./durable/durable-functions-code-constraints.md).
606
+
> [Durable Functions](./durable-functions/durable-functions-overview.md) orchestrators have their own threading constraints. The orchestrator replay thread must run continuations, so using `ConfigureAwait(false)` in orchestrator functions or orchestrator middleware can interfere with orchestration execution. For more information, see the [Durable Functions code constraints](../durable-task/common/durable-task-code-constraints.md).
0 commit comments