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-use-azure-ad.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
@@ -49,7 +49,7 @@ For Azure Automation to communicate with Microsoft Entra ID, you must retrieve t
49
49
50
50
## Create a credential asset
51
51
52
-
With the Azure credentials for Microsoft Entra available, it's time to create an Azure Automation credential asset to securely store the Microsoft Entra credentials so that runbooks and Desire State Configuration (DSC) scripts can access them. You can do this using either the Azure portal or PowerShell cmdlets.
52
+
With the Azure credentials for Microsoft Entra available, it's time to create an Azure Automation credential asset to securely store the Microsoft Entra credentials so that runbooks and Desired State Configuration (DSC) scripts can access them. You can do this using either the Azure portal or PowerShell cmdlets.
Copy file name to clipboardExpand all lines: articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.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
@@ -12,7 +12,7 @@ ms.author: v-mallicka
12
12
13
13
# Back up Azure Local virtual machines with Azure Backup Server
14
14
15
-
This article describes how to back up virtual machines running on Azure Local, versions *23 H2* and *22 H2*, using Microsoft Azure Backup Server (MABS).
15
+
This article describes how to back up virtual machines running on Azure Local using Microsoft Azure Backup Server (MABS).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-arm-restore-vms.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
@@ -273,7 +273,7 @@ In the restore process, you'll see the option **Availability Zone.** You'll see
273
273
274
274
In summary, the **Availability Zone** will only appear when
275
275
- The source VM is zone pinned and is NOT encrypted
276
-
- The recovery point is present in vault tier only (Snapshots only or snapshot and vault tier are not supported)
276
+
- The recovery point is present in vault tier (Snapshots only are not supported)
277
277
- The recovery option is to either create a new VM or to restore disks (replace disks option replaces source data and hence the availability zone option is not applicable)
278
278
- Creating VM/disks in the same region when vault's storage redundancy is ZRS (Doesn't work when vault's storage redundancy is GRS even though the source VM is zone pinned)
279
279
- Creating VM/disks in the paired region when vault's storage redundancy is enabled for Cross-Region-Restore AND if the paired region supports zones
Copy file name to clipboardExpand all lines: articles/firewall/firewall-known-issues.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,6 @@ The following zones are currently experiencing capacity constraints:
28
28
|- **Physical zone 2** in **_North Europe_** </br>- **Physical zone 3** in **_South East Asia_**| Standard and Premium | - You can't deploy a new Azure Firewall to zone 3 in South East Asia or zone 2 in North Europe. </br></br>- If you stop an existing Azure Firewall that is deployed in these zone, it can't be restarted. </br></br>For more information, see [Physical and logical availability zones](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones). | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment)|
29
29
|**Physical zone 3** in **_South Central US_**| Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 3. </br></br>Estimated date available: March 31, 2026 | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment)|
30
30
|**Physical zone 2** in **_Spain Central_**| Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 2. </br></br>Estimated date available: December 31, 2026 | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment)|
31
-
|**_US Gov Virginia_**| Premium | - There's zero capacity for Azure Firewall Premium SKU in US Gov Virginia, both zonal and nonzonal deployments are blocked. | Deploy Azure Firewall Standard SKU or deploy Premium SKU to a different region. |
32
31
|**Physical zone 3** in **_US Gov Virginia_**| Basic and Standard | - Zonal deployments are blocked in physical zone 3 in US Gov Virginia. </br></br>- You must manually select available zones for successful deployment, creating a suboptimal deployment experience. | Select zones 1 and 2 for zonal deployments or use a different region. |
33
32
|**Physical zone 2** in **_West US 2_**| Basic, Standard, and Premium | - You can't deploy a new Azure Firewall in zone 2. | We recommend you deploy a new Azure Firewall to the remaining availability zones or use a different region. To configure an existing firewall, see [How can I configure availability zones after deployment?](firewall-faq.yml#how-can-i-configure-availability-zones-after-deployment)|
34
33
|**Physical zone 1,2,3** in **Qatar Central**| Basic, Standard, and Premium | - New Azure Firewall deployments are blocked.</br></br>Estimated date available: December 31, 2026 | We recommend you deploy a new Azure Firewall in a different region.|
Copy file name to clipboardExpand all lines: articles/frontdoor/front-door-faq.yml
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -120,11 +120,11 @@ sections:
120
120
answer: |
121
121
You can redirect host, path, and query string components of a URL with Azure Front Door. To learn how to configure URL redirection, refer to [URL redirection](front-door-url-redirect.md).
122
122
- question: |
123
-
Does AFD provide telemetry to show which rules engine rule AFD processes for each request?
123
+
Does Front Door provide telemetry to show which rules engine rule Front Door processes for each request?
124
124
answer: |
125
125
Yes. Refer to the MatchedRulesSetName property under [Access Logs](front-door-diagnostics.md).
126
126
- question: |
127
-
Can AFD provide protection from ‘HTTP/2 Rapid Reset’ DDoS attacks?
127
+
Can Front Door provide protection from ‘HTTP/2 Rapid Reset’ DDoS attacks?
128
128
answer: |
129
129
Yes. For more information, see [Microsoft response to DDoS attacks against HTTP/2](front-door-ddos.md).
130
130
- question: |
@@ -362,7 +362,7 @@ sections:
362
362
- question: |
363
363
Do I get billed for the Azure Front Door resources that are disabled?
364
364
answer: |
365
-
Azure Front Door resources cannot be disabled. They can only be deleted. Variable meters like Data Transfer Out, Data Transfer In and Requests are not charged when there is no traffic but base fee is charged even if there is no traffic. Base fee will be charged till the profile is deleted. For AFD Classic, WAF policies and rules are charged regardless of their status. Even if you disable a WAF policy or rule, it still incurs costs for you.
365
+
Azure Front Door resources cannot be disabled. They can only be deleted. Variable meters like Data Transfer Out, Data Transfer In and Requests are not charged when there is no traffic but base fee is charged even if there is no traffic. Base fee will be charged till the profile is deleted. For Front Door Classic, WAF policies and rules are charged regardless of their status. Even if you disable a WAF policy or rule, it still incurs costs for you.
366
366
367
367
- name: Caching
368
368
questions:
@@ -377,9 +377,9 @@ sections:
377
377
- question: |
378
378
Is it possible to support compression for file sizes above 8 MB?
379
379
answer: |
380
-
AFD does not support dynamic compression for content greater than 8 MB. However, if the content has been already compressed by the origin, Front Door supports serving static compressed content over 8 MB as long as range request is supported and chunked transfer encoding is not enabled.
380
+
Front Door does not support dynamic compression for content greater than 8 MB. However, if the content has been already compressed by the origin, Front Door supports serving static compressed content over 8 MB as long as range request is supported and chunked transfer encoding is not enabled.
381
381
- question: |
382
-
Does AFD support setting the Authorization Header in the HTTP request if caching is enabled?
382
+
Does Front Door support setting the Authorization Header in the HTTP request if caching is enabled?
0 commit comments