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/app-service/includes/configure-azure-storage/azure-storage-linux-container-pivot.md
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,6 +203,46 @@ To validate that the Azure Storage is mounted successfully for the app:
203
203
tcpping Storageaccount.file.core.windows.net
204
204
```
205
205
206
+
### Storage mount health checks and auto‑recovery
207
+
208
+
Azure App Service includes a built‑in health‑check mechanism to ensure that mounted Azure Storage volumes (Azure Files or Azure Blob) remain accessible and responsive. This system helps prevent application hangs caused by stale or disconnected storage mounts.
209
+
210
+
#### How the health check works
211
+
212
+
1.**Periodic I/O test**
213
+
App Service periodically performs file I/O on a marker file named `__lastCheckTime.txt`.
214
+
-**Location:** A `LogFiles` subdirectory under the mounted path (for example, `/mount/path/LogFiles/__lastCheckTime.txt`).
215
+
-**Behavior:**
216
+
- A read operation is attempted on this file.
217
+
- The file does *not* need to exist—“file not found” is treated as a successful check.
218
+
219
+
2.**Frequency**
220
+
The check runs every **5 seconds** by default.
221
+
222
+
3.**Failure handling**
223
+
- Each failed or timed‑out check increments a *failed ping counter*.
224
+
- When failures exceed the configured threshold:
225
+
-**Azure Files:** 18 failed pings
226
+
-**Azure Blob:** 15 failed pings
227
+
- The mount is marked **Faulted**, and **App Service automatically restarts the app** to restore connectivity to the share.
228
+
229
+
#### Configuration via App Settings
230
+
231
+
You can customize health‑check behavior using the following app settings.
232
+
233
+
| Storage type | Setting name | Default value | Description |
Copy file name to clipboardExpand all lines: articles/app-service/overview-managed-instance.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Managed Instance on App Service overview (preview)
3
3
description: Managed Instance on Azure App Service is a specialized hosting option that provides isolation, customization, and secure integration with Azure resources, ideal for legacy, and infrastructure-dependent web apps.
Copy file name to clipboardExpand all lines: articles/azure-vmware/faq.yml
+30-2Lines changed: 30 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -177,7 +177,35 @@ sections:
177
177
178
178
- question: What about support for ISV backup solutions?
179
179
answer: As these backup solutions are installed and managed by customers, they can reach out to the respective ISV for support.
180
-
180
+
181
+
- name: Reliability and availability
182
+
questions:
183
+
184
+
- question: Can I deploy a stretched cluster across availability zones for higher availability?
185
+
answer: Azure VMware Solution supports stretched clusters across availability zones in supported Azure regions and configurations. Availability varies by Azure VMware Solution generation and region. For more information, see [Deploy a stretched cluster](deploy-vsan-stretched-clusters.md).
186
+
187
+
- question: Does Azure VMware Solution Gen2 support Availability Zones?
188
+
answer: Yes. In Azure VMware Solution Gen2, you can select the Availability Zone where your private cloud is deployed (subject to capacity availability in that zone). You can also deploy separate private clouds in different Availability Zones as part of a disaster recovery (DR) or high-availability strategy.
189
+
190
+
- question: Does Azure VMware Solution Gen2 support vSAN stretched clusters across Availability Zones?
191
+
answer: No. vSAN stretched clusters (a single private cloud stretched across two Availability Zones) aren't supported on Azure VMware Solution Gen2 today.
192
+
193
+
- question: In Azure VMware Solution Gen1, can I choose the Availability Zone for my private cloud?
194
+
answer: No. In Azure VMware Solution Gen1, selecting an Availability Zone isn't supported when deploying a private cloud.
195
+
196
+
- question: In Azure VMware Solution Gen1 stretched clusters, what happens if the Availability Zone hosting the vSAN witness becomes unavailable?
197
+
answer: |
198
+
Azure VMware Solution Gen1 uses a single vSAN witness that is statically placed in a specific Availability Zone within a region. If the Availability Zone hosting the witness becomes unavailable, the witness becomes unreachable.
199
+
200
+
As long as sufficient data replicas remain available, data hosts and running workloads continue operating without immediate data loss. However, vSAN loses quorum awareness in this state, which prevents it from safely making placement and recovery decisions and causes certain operations (such as VM power-on after failures, rebalancing, and repairs) to be blocked.
201
+
202
+
The witness isn't automatically recreated or moved to another Availability Zone during this time.
203
+
204
+
- question: Do four-zone Azure regions change how Azure VMware Solution uses Availability Zones?
205
+
answer: No. Azure VMware Solution remains unaffected. Availability Zone capabilities depend on what Azure VMware Solution supports in that region and available capacity.
206
+
207
+
- question: Are there built-in capabilities to run workloads across multiple Azure VMware Solution private clouds for DR/HA?
208
+
answer: No. Deploying workloads across multiple private clouds (for example, across Availability Zones) typically requires customer-managed orchestration and replication. For DR, customers commonly use third-party solutions such as Jetstream, Zerto, or Azure Site Recovery, based on workload requirements.
181
209
182
210
- name: Networking and interconnectivity
183
211
questions:
@@ -330,7 +358,7 @@ sections:
330
358
answer: No. We currently don't support cloudadmin extension privileges and have no plans to support it.
331
359
332
360
333
-
- name: CSP and multi-tenancy
361
+
- name: CSP and multitenancy
334
362
questions:
335
363
336
364
- question: Does Azure VMware Solution provide an option for hoster partners to resell the service?
Copy file name to clipboardExpand all lines: articles/backup/soft-delete-azure-backup-faq.yml
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ metadata:
4
4
description: Answers to common questions about the security feature - soft delete.
5
5
ms.topic: faq
6
6
ms.service: azure-backup
7
-
ms.date: 01/31/2025
7
+
ms.date: 01/12/2026
8
8
author: AbhishekMallick-MS
9
9
ms.author: v-mallicka
10
10
@@ -33,7 +33,7 @@ sections:
33
33
- question: |
34
34
Can I perform a restore operation when my data is in soft delete state?
35
35
answer: |
36
-
No, you need to undelete the soft deleted resource in order to restore. The undeleteoperation will bring the resource back into the **Stop protection with retain data state** where you can restore to any point in time. Garbage collector remains paused in this state.
36
+
No, you need to undelete the soft deleted resource in order to restore. The undelete-operation will bring the resource back into the **Stop protection with retain data state** where you can restore to any point in time. Garbage collector remains paused in this state.
37
37
38
38
- question: |
39
39
Will my snapshots follow the same lifecycle as my recovery points in the vault?
@@ -43,7 +43,7 @@ sections:
43
43
- question: |
44
44
How can I trigger the scheduled backups again for a soft-deleted resource?
45
45
answer: |
46
-
Undelete followed by a resume operation will protect the resource again. The resumeoperation associates a backup policy to trigger the scheduled backups with the selected retention period. Also, the garbage collector runs as soon as the resumeoperation completes. If you wish to perform a restore from a recovery point that's past its expiration date, you're advised to do it before triggering the resumeoperation.
46
+
Undelete followed by a resume operation will protect the resource again. The resume-operation associates a backup policy to trigger the scheduled backups with the selected retention period. Also, the garbage collector runs as soon as the resume-operation completes. If you wish to perform a restore from a recovery point that's past its expiration date, you're advised to do it before triggering the resume-operation.
47
47
48
48
- question: |
49
49
Can I delete my vault if there are soft-deleted items in the vault?
@@ -53,7 +53,7 @@ sections:
53
53
- question: |
54
54
Can I delete the data earlier than the 14 days soft-delete period after deletion?
55
55
answer: |
56
-
No. You can't force-delete the soft-deleted items. They're automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes. You should wait for 14 days before performing any other action on the item. Soft-deleted items won't be charged. If you need to reprotect the items marked for soft-delete within 14 days in a new vault, then contact Microsoft support.
56
+
No. You can't force-delete the soft-deleted items. They're automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes. You should wait for 14 days before performing any other action on the item. Soft-deleted items won't be charged. If you need to reprotect the items marked for soft-delete within 14 days in a new vault, then contact Microsoft support.
57
57
58
58
- question: |
59
59
Can soft delete operations be performed in PowerShell or CLI?
@@ -63,4 +63,5 @@ sections:
63
63
additionalContent: |
64
64
65
65
## Next steps
66
-
[Manage the soft delete features in Azure Backup](backup-azure-security-feature-cloud.md).
66
+
- [Manage the soft delete features in Azure Backup](backup-azure-security-feature-cloud.md).
67
+
- [About enhanced soft delete for Azure Backup](backup-azure-enhanced-soft-delete-about.md).
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,6 +166,14 @@ You need to assign a public switched telephone network (PSTN) number to your Res
166
166
1. Also, if you plan to make outbound PSTN calls using your Resource Accounts assigned phone number, now is a good time to assign a [Microsoft Teams Calling Plan](/microsoftteams/calling-plans-for-office-365).
167
167
168
168
169
+
> **Note:** Proper configuration depends on the phone number service type assigned to the Resource account:
170
+
> - **Direct Routing** – The tenant must be configured for Direct Routing with a verified Session Border Controller (SBC), a Direct Routing phone number assigned to the Resource account, and a Voice Routing Policy that allows PSTN calls assigned to the Resource account.
171
+
> - **Calling Plan** – The Resource account must be assigned a Calling Plan service number and licensed with Microsoft Teams Phone Resource Account.
172
+
> - **Operator Connect** – The phone number must be provisioned by an approved Operator Connect provider that supports outbound PSTN calling for voice applications.
173
+
> - For all these connectivity options, you need to make sure you have the proper Microsoft licenses in place as detailed in the [general license prerequisite](/azure/communication-services/concepts/interop/tpe/teams-phone-extensibility-overview#prerequisites) or specifically for [Outbound license requirements](/azure/communication-services/quickstarts/tpe/teams-phone-extensibility-server-outbound-call#licensing-requirements)
174
+
175
+
176
+
169
177
### CCaaS Developer: Get Resource Account Information
170
178
171
179
We're introducing a new Graph API to get a list of Resource Accounts and phone numbers where assigned. The Graph API supports an optional filter on your Microsoft Entra first party `applicationID` / `clientId`.
Copy file name to clipboardExpand all lines: articles/container-apps/ip-restrictions.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ There are two types of restrictions:
22
22
**Allow*: Allow inbound traffic only from address ranges you specify in allow rules.
23
23
**Deny*: Deny all inbound traffic only from address ranges you specify in deny rules.
24
24
25
-
when no IP restriction rules are defined, all inbound traffic is allowed.
25
+
When no IP restriction rules are defined, all inbound traffic is allowed.
26
26
27
27
IP restrictions rules contain the following properties:
28
28
@@ -186,6 +186,16 @@ az containerapp ingress access-restriction list
186
186
187
187
::: zone-end
188
188
189
+
## Troubleshooting
190
+
191
+
Use the following information to help you troubleshoot IP-related issues in your container app.
192
+
193
+
### Access denied
194
+
195
+
An *RBAC: Access Denied* message returned to the client indicates the client is blocked by IP restrictions from the container app. To fix this, make sure the client IP address requesting access is allowed based on either the "allow" or "deny" rules.
196
+
197
+
If using an address range, make sure the blocked IP falls within an allowed range.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments