Skip to content

Commit 8765cba

Browse files
Merge pull request #312629 from MicrosoftDocs/main
Auto Publish – main to live - 2026-03-05 06:00 UTC
2 parents d4ca2cb + 2420449 commit 8765cba

6 files changed

Lines changed: 88 additions & 28 deletions

File tree

articles/azure-functions/dotnet-isolated-process-guide.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Guide for running C# Azure Functions in an isolated worker process
33
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.
44
ms.service: azure-functions
55
ms.topic: how-to
6-
ms.date: 12/06/2025
6+
ms.date: 02/24/2026
77
recommendations: false
88
ms.custom:
99
- template-concept
@@ -596,6 +596,15 @@ The cancellation token is signaled when the function invocation is canceled. Sev
596596

597597
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`.
598598

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+
599608
## Bindings
600609

601610
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.

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.topic: concept-article
8-
ms.date: 08/28/2025
8+
ms.date: 03/03/2026
99
ms.author: anfdocs
1010
# 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."
1111
---
@@ -37,7 +37,7 @@ Azure NetApp Files supports a fully managed backup solution for long-term recove
3737
### Benefits
3838

3939
- 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
4141
- Retain daily, weekly, monthly backups for extended periods of time on cost-efficient cloud storage without media management
4242

4343
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
7878
| Use case | In-region solution | Cross-region solution |
7979
| --- | --- | --- |
8080
| 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 |
8383
| Disaster recovery | - | Cross-region replication |
8484
Fast data recovery (whole volume) | Revert volume from snapshot | Revert volume from snapshot |
8585
| Feed current production data to test or development environment | Restore snapshot to new volume (clone) | Restore snapshot to new volume (clone) |
@@ -96,8 +96,9 @@ Fast data recovery (whole volume) | Revert volume from snapshot | Revert volume
9696
* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
9797
* [Understand Azure NetApp Files backup](backup-introduction.md)
9898
* [Understand Azure NetApp Files replication](replication.md)
99-
* [Reliability in Azure NetApp Flies](/azure/reliability/reliability-netapp-files)
99+
* [Reliability in Azure NetApp Files](/azure/reliability/reliability-netapp-files)
100100
* [What is Azure Application Consistent Snapshot tool](azacsnap-introduction.md)
101101
* [Restore individual files using single-file snapshot restore](snapshots-restore-file-single.md)
102102
* [Restore a snapshot to a new volume](snapshots-restore-new-volume.md)
103103
* [Restore a volume using snapshot revert](snapshots-revert-volume.md)
104+
* [Understand advanced ransomware protection](advanced-ransomware-protection.md)

articles/backup/troubleshoot-azure-files.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -325,6 +325,16 @@ Recommended Actions: Ensure that the following configurations in the storage acc
325325

326326
**Cause**: Storage Accounts with [Smart Tier(Preview)](../storage/blobs/access-tiers-smart.md) set are currently not supported.
327327

328+
### UserErrorStorageAccountSasPolicyNotSupported - Azure Files Backup requires a minimum SAS expiration period of 8 hours
329+
330+
**Error code**: `UserErrorStorageAccountSasPolicyNotSupported`
331+
332+
**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+
328338
## Common policy modification errors
329339

330340
### BMSUserErrorConflictingProtectionOperation- Another configure protection operation is in progress for this item

articles/redis/reserved-pricing.md

Lines changed: 43 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -35,31 +35,63 @@ The following Azure Managed Redis tiers currently support reservations:
3535

3636
| Region Name | Memory Optimized | Balanced | Compute Optimized | Flash Optimized |
3737
| ------------------- | ---------------- | -------- | ---------------- | --------------- |
38-
| UAE North | Yes | Yes | Yes | No |
3938
| Australia Central | Yes | Yes | Yes | No |
39+
| Australia Central 2 | Yes | Yes | Yes | No |
40+
| Australia East | Yes | Yes | Yes | No |
4041
| Australia Southeast | Yes | Yes | Yes | No |
42+
| Austria East | Yes | Yes | Yes | No |
43+
| Belgium Central | Yes | Yes | Yes | No |
44+
| Brazil South | Yes | Yes | Yes | No |
4145
| Brazil Southeast | Yes | Yes | Yes | No |
46+
| Canada Central | Yes | Yes | Yes | No |
4247
| Canada East | Yes | Yes | Yes | No |
43-
| Switzerland West | Yes | Yes | Yes | No |
44-
| Spain Central | Yes | Yes | Yes | No |
48+
| Central US | Yes | Yes | Yes | No |
49+
| Chile Central | Yes | Yes | Yes | No |
50+
| East Asia | Yes | Yes | Yes | No |
51+
| East US | Yes | No | Yes | No |
52+
| East US 2 | Yes | Yes | Yes | No |
4553
| France Central | Yes | Yes | Yes | No |
4654
| France South | Yes | Yes | Yes | No |
47-
| Indonesia Central | Yes | Yes | Yes | No |
48-
| Israel Central | Yes | Yes | Yes | No |
49-
| Israel Northwest | No | Yes | No | No |
55+
| Germany North | Yes | Yes | Yes | No |
56+
| Germany West Central| Yes | Yes | Yes | No |
5057
| India Central | Yes | Yes | Yes | No |
5158
| India South | Yes | Yes | Yes | No |
5259
| India West | Yes | Yes | Yes | No |
60+
| Indonesia Central | Yes | Yes | Yes | No |
61+
| Israel Central | Yes | Yes | Yes | No |
62+
| Israel Northwest | No | Yes | Yes | No |
5363
| Italy North | Yes | Yes | Yes | No |
5464
| Japan East | Yes | Yes | Yes | No |
65+
| Japan West | Yes | Yes | Yes | No |
5566
| Korea Central | Yes | Yes | Yes | No |
5667
| Korea South | Yes | Yes | Yes | No |
68+
| Malaysia West | Yes | Yes | Yes | No |
69+
| Mexico Central | Yes | Yes | Yes | No |
70+
| New Zealand North | Yes | Yes | Yes | No |
71+
| North Europe | Yes | Yes | Yes | No |
72+
| NorthCentral US | Yes | Yes | Yes | No |
5773
| Norway East | Yes | Yes | Yes | No |
74+
| Norway West | Yes | Yes | Yes | No |
5875
| Poland Central | Yes | Yes | Yes | No |
5976
| Qatar Central | Yes | Yes | Yes | No |
60-
| UK West | Yes | Yes | Yes | No |
61-
| US East | Yes | No | Yes | No |
6277
| South Africa North | Yes | Yes | Yes | No |
78+
| South Africa West | Yes | Yes | Yes | No |
79+
| South Central US | Yes | Yes | Yes | No |
80+
| SouthEast Asia | Yes | Yes | Yes | No |
81+
| Spain Central | Yes | Yes | Yes | No |
82+
| Sweden Central | Yes | Yes | Yes | No |
83+
| Sweden South | Yes | Yes | Yes | No |
84+
| Switzerland North | Yes | Yes | Yes | No |
85+
| Switzerland West | Yes | Yes | Yes | No |
86+
| UAE Central | Yes | Yes | Yes | No |
87+
| UAE North | Yes | Yes | Yes | No |
88+
| UK South | Yes | Yes | Yes | No |
89+
| UK West | Yes | Yes | Yes | No |
90+
| West Central US | Yes | Yes | Yes | No |
91+
| West Europe | Yes | Yes | Yes | No |
92+
| West US | Yes | Yes | Yes | No |
93+
| West US 2 | Yes | Yes | Yes | No |
94+
| West US 3 | Yes | Yes | Yes | No |
6395

6496
## Buy Azure Managed Redis reservations
6597

@@ -100,7 +132,9 @@ Existing or new caches that match the attributes you select get the reservation
100132

101133
- You can update the scope of the reservation through the Azure portal, PowerShell, Azure CLI, or the API.
102134

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).
104138

105139
## Related content
106140

articles/storage/files/files-managed-identities.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article explains how you can authenticate managed identities t
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: how-to
7-
ms.date: 03/02/2026
7+
ms.date: 03/04/2026
88
ms.author: kendownie
99
ms.custom:
1010
- devx-track-azurepowershell
@@ -229,11 +229,11 @@ To prepare your client VM or Windows device to authenticate by using a managed i
229229

230230
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+.
231231

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:
233233

234234
```powershell
235-
Install-Module AzFilesSMBMIClient
236-
Import-Module AzFilesSMBMIClient
235+
Install-Module AzFilesSmbMIClient
236+
Import-Module AzFilesSmbMIClient
237237
```
238238

239239
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
253253
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/`
254254

255255
```powershell
256-
AzFilesSMBMIClient.exe refresh --uri https://<storage-account-name>.file.core.windows.net/
256+
AzFilesSmbMIClient.exe refresh --uri https://<storage-account-name>.file.core.windows.net/
257257
```
258258

259259
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:
290290

291291
```bash
292292
curl -sSL -O https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb
293-
sudo dpkg -i packages-microsoft-prod.deb rm packages-microsoft-prod.deb
293+
sudo dpkg -i packages-microsoft-prod.deb
294+
rm packages-microsoft-prod.deb
294295
# the above steps update the sources.list
295-
sudo apt-get update sudo apt-get install azfilesauth
296+
sudo apt-get update
297+
sudo apt-get install -y azfilesauth
296298
```
297299

298300
#### Ubuntu 24.04
299301

300302
Run the following commands to install `azfilesauth` on Ubuntu 24.04:
301303

302304
```bash
303-
curl -SSL -O https://packages.microsoft.com/config/ubuntu/24.04/packages-microsoft-prod.deb
304-
sudo dpkg -i packages-microsoft-prod.deb rm packages-microsoft-prod.deb
305+
curl -sSL -O https://packages.microsoft.com/config/ubuntu/24.04/packages-microsoft-prod.deb
306+
sudo dpkg -i packages-microsoft-prod.deb
307+
rm packages-microsoft-prod.deb
305308
# the above steps update the sources.list
306-
sudo apt-get update sudo apt-get install azfilesauth
309+
sudo apt-get update
310+
sudo apt-get install -y azfilesauth
307311
```
308312

309313
### Configure authentication
@@ -421,7 +425,7 @@ For native applications that need direct API access, AzFilesSmbMIClient is avail
421425

422426
The native DLL exports the following core methods for credential management:
423427

424-
```cpp
428+
```c
425429
extern "C" AZFILESSMBMI_API HRESULT SmbSetCredential(
426430
_In_ PCWSTR pwszFileEndpointUri,
427431
_In_ PCWSTR pwszOauthToken,
@@ -449,7 +453,7 @@ For more information, see the [AzFilesAuthenticator project](https://github.com/
449453

450454
The shared library exports the following core methods for credential management:
451455

452-
```bash
456+
```c
453457
#ifdef __cplusplus
454458
extern "C" {
455459
#endif
@@ -484,5 +488,5 @@ The following table lists the API commands and their usage. Returned values foll
484488
485489
## See also
486490
487-
- [Overview of Azure Files identity-based authentication for SMB access](storage-files-active-directory-overview.md)
491+
- [Overview of Azure Files identity-based authentication](storage-files-active-directory-overview.md)
488492
- [Overview of Azure Files authorization and access control](storage-files-authorization-overview.md)

articles/web-application-firewall/ag/insights.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,8 @@ In **Triage by URL**, investigation begins with a URL path. Analysts select the
110110

111111
- **Scale:** Large volumes of diagnostic logs can increase query latency and storage costs.
112112

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+
113115
## Best practices
114116

115117
- Always enable **both metrics and logs** to balance visibility and detail.

0 commit comments

Comments
 (0)