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/azure-functions/dotnet-isolated-process-guide.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Guide for running C# Azure Functions in an isolated worker process
3
3
description: Learn how to use the .NET isolated worker model to run your C# functions in Azure, which lets you run your functions on currently supported versions of .NET and .NET Framework.
4
4
ms.service: azure-functions
5
5
ms.topic: how-to
6
-
ms.date: 12/06/2025
6
+
ms.date: 02/24/2026
7
7
recommendations: false
8
8
ms.custom:
9
9
- template-concept
@@ -596,6 +596,15 @@ The cancellation token is signaled when the function invocation is canceled. Sev
596
596
597
597
This exception occurs when the cancellation token is canceled (as a result of one of the events described earlier) _before_ the host sends an incoming invocation request to the worker. This exception can be safely ignored and is expected when `SendCanceledInvocationsToWorker` is `false`.
598
598
599
+
## Async programming
600
+
601
+
The .NET isolated worker doesn't set a custom [`SynchronizationContext`](/dotnet/api/system.threading.synchronizationcontext). This means that `SynchronizationContext.Current` is `null` during function execution. After an `await`, continuations are scheduled on the thread pool, which is the standard .NET behavior.
602
+
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
+
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).
607
+
599
608
## Bindings
600
609
601
610
Define bindings by using attributes on methods, parameters, and return types. Bindings can provide data as strings, arrays, and serializable types, such as plain old class objects (POCOs). For some binding extensions, you can also [bind to service-specific types](#sdk-types) defined in service SDKs.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/data-protection-disaster-recovery-options.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-ahibbard
6
6
ms.service: azure-netapp-files
7
7
ms.topic: concept-article
8
-
ms.date: 08/28/2025
8
+
ms.date: 03/03/2026
9
9
ms.author: anfdocs
10
10
# Customer intent: "As a data administrator, I want to assess the data protection and disaster recovery options available in Azure NetApp Files, so that I can choose the most effective solutions to ensure data integrity and availability for my organization's needs."
11
11
---
@@ -37,7 +37,7 @@ Azure NetApp Files supports a fully managed backup solution for long-term recove
37
37
### Benefits
38
38
39
39
- Increased productivity, reliably integrated service that is easy to manage and can be set once
40
-
- Application-consistent backups with [AzAcSnap integration](azacsnap-introduction.md)
40
+
- Application-consistent backups with [AzAcSnap integration](azacsnap-introduction.md), [SnapCenter snapshot and backup orchestration](https://www.netapp.com/snapcenter/), or third-party tools
41
41
- Retain daily, weekly, monthly backups for extended periods of time on cost-efficient cloud storage without media management
42
42
43
43
To learn more, see [How snapshots can be vaulted for long-term retention and cost savings](snapshots-introduction.md#how-snapshots-can-be-vaulted-for-long-term-retention-and-cost-savings). To get started with backups, see [Configure policy-based backups for Azure NetApp Files](backup-configure-policy-based.md).
@@ -78,8 +78,8 @@ Choosing the best data protection option for your Azure NetApp Files deployment
78
78
| Use case | In-region solution | Cross-region solution |
79
79
| --- | --- | --- |
80
80
| Ad hoc backup | On-demand snapshots | - |
81
-
| Application consistent data protection | AzAcSnap | - |
82
-
| Data corruption and ransomware protection |Scheduled snapshots| Cross-region replication |
81
+
| Application consistent data protection | AzAcSnap, [SnapCenter](https://docs.netapp.com/us-en/snapcenter/get-started/concept_snapcenter_overview.html)| - |
82
+
| Data corruption and ransomware protection |Advanced ransomware protection| Cross-region replication |
**Error message**: Azure File Share Backup requires a minimum SAS expiration period of 8 hours.
333
+
334
+
**Cause**: If the SAS token expiry is shorter than 8 hours, the Backup service cannot renew the token in time. This leads to authentication failures and can interrupt ongoing backup or restore operations.
335
+
336
+
**Recommended action**: Set the SAS expiry upper limit to 8 hours or more to ensure the Backup service can successfully renew the SAS token and maintain uninterrupted backup and restore activities.
337
+
328
338
## Common policy modification errors
329
339
330
340
### BMSUserErrorConflictingProtectionOperation- Another configure protection operation is in progress for this item
@@ -100,7 +132,9 @@ Existing or new caches that match the attributes you select get the reservation
100
132
101
133
- You can update the scope of the reservation through the Azure portal, PowerShell, Azure CLI, or the API.
102
134
103
-
- You can cancel, exchange, or refund reservations with certain limitations. For more information, see [Self-service exchanges and refunds for Azure Reservations](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations).
135
+
## Exchange existing Reservations with Azure Managed Redis
136
+
137
+
You can cancel, exchange, or refund reservations with certain limitations. For more information, see [Self-service exchanges and refunds for Azure Reservations](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations).
Copy file name to clipboardExpand all lines: articles/storage/files/files-managed-identities.md
+17-13Lines changed: 17 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article explains how you can authenticate managed identities t
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: how-to
7
-
ms.date: 03/02/2026
7
+
ms.date: 03/04/2026
8
8
ms.author: kendownie
9
9
ms.custom:
10
10
- devx-track-azurepowershell
@@ -229,11 +229,11 @@ To prepare your client VM or Windows device to authenticate by using a managed i
229
229
230
230
1. Sign in to your VM or device that has the managed identity assigned and open a PowerShell window as administrator. You need either PowerShell 5.1+ or PowerShell 7+.
231
231
232
-
1. Install the [Azure Files SMB Managed Identity Client](https://www.powershellgallery.com/packages/AzFilesSmbMIClient/1.0.4) PowerShell module and import it:
232
+
1. Install the [Azure Files SMB Managed Identity Client](https://www.powershellgallery.com/packages/AzFilesSmbMIClient/) PowerShell module and import it:
233
233
234
234
```powershell
235
-
Install-Module AzFilesSMBMIClient
236
-
Import-Module AzFilesSMBMIClient
235
+
Install-Module AzFilesSmbMIClient
236
+
Import-Module AzFilesSmbMIClient
237
237
```
238
238
239
239
1. Check your current PowerShell execution policy by running the following command:
@@ -253,7 +253,7 @@ To prepare your client VM or Windows device to authenticate by using a managed i
253
253
Before you can mount the file share by using the managed identity, refresh the authentication credentials and specify your storage account endpoint. To copy your storage account URI, go to the storage account in the Azure portal and then select **Settings** > **Endpoints** from the service menu. Be sure to copy the entire URI including the trailing slash: `https://<storage-account-name>.file.core.windows.net/`
This command gets an OAuth token and inserts it in the Kerberos cache. It auto-refreshes when the token is close to expiration. You can optionally omit the `refresh`.
@@ -290,20 +290,24 @@ Run the following commands to install `azfilesauth` on Ubuntu 22.04:
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/insights.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,6 +110,8 @@ In **Triage by URL**, investigation begins with a URL path. Analysts select the
110
110
111
111
-**Scale:** Large volumes of diagnostic logs can increase query latency and storage costs.
112
112
113
+
-**Resource-specific mode:** Resource-specific tables are currently not supported. The solution relies on Diagnostic settings streaming to Log Analytics in Azure Diagnostics mode only.
114
+
113
115
## Best practices
114
116
115
117
- Always enable **both metrics and logs** to balance visibility and detail.
0 commit comments