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-cache-for-redis/cache-remove-tls-10-11.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
@@ -18,7 +18,7 @@ To meet the industry-wide push toward the exclusive use of Transport Layer Secur
18
18
TLS versions 1.0 and 1.1 also don't support the modern encryption methods and cipher suites recommended by Payment Card Industry (PCI) compliance standards. This [TLS security blog](https://www.acunetix.com/blog/articles/tls-vulnerabilities-attacks-final-part/) explains some of these vulnerabilities in more detail.
19
19
20
20
> [!IMPORTANT]
21
-
> On November 1, 2024, the TLS 1.2 requirement will be enforced.
21
+
> Starting November 1, 2024, the TLS 1.2 requirement will be enforced.
22
22
>
23
23
>
24
24
@@ -36,7 +36,7 @@ As a part of this effort, you can expect the following changes to Azure Cache fo
36
36
| September 2023 | TLS 1.0/1.1 retirement announcement |
37
37
| March 1, 2024 | Beginning March 1, 2024, you can't create new caches with the Minimum TLS version set to 1.0 or 1.1 and you can't set the _MinimumTLSVersion_ to 1.0 or 1.1 for your existing cache. The minimum TLS version won't be updated automatically for existing caches at this point. |
38
38
| October 31, 2024 | Ensure that all your applications are connecting to Azure Cache for Redis using TLS 1.2 and Minimum TLS version on your cache settings is set to 1.2. |
39
-
| November 1, 2024 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point. |
39
+
|Starting November 1, 2024 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point. |
40
40
41
41
> [!IMPORTANT]
42
42
> The content in this article does not apply to Azure Cache for Redis Enterprise/Enterprise Flash because the Enterprise tiers only support TLS 1.2.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/manage/pay-by-invoice.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.reviewer: lishepar
6
6
ms.service: cost-management-billing
7
7
ms.subservice: billing
8
8
ms.topic: how-to
9
-
ms.date: 08/06/2024
9
+
ms.date: 10/15/2024
10
10
ms.author: banders
11
11
---
12
12
@@ -40,10 +40,7 @@ To qualify for wire transfer payments, you must:
40
40
- Have a subscription cost that exceeds a certain amount. This amount varies by service location.
41
41
42
42
> [!IMPORTANT]
43
-
> - Payment by wire transfer is available only for customers who use Azure on behalf of a company.
44
43
> - You must pay all outstanding charges before switching to payment by wire transfer.
45
-
> - Your default payment method pays any outstanding invoice. To have a wire transfer pay an outstanding invoice, you must change your default payment method to wire transfer after you're approved.
46
-
> - Currently, payment by wire transfer isn't supported for Azure global in China.
47
44
> - If you switch to payment by wire transfer, you can't switch back to paying by credit or debit card, except for one-time payments.
48
45
> - As of September 30, 2023, Microsoft no longer accepts checks as a payment method.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/reservations/prepare-buy-reservation.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
@@ -70,7 +70,7 @@ Resources that run in a subscription with other offer types don't receive the re
70
70
71
71
## Purchase reservations
72
72
73
-
When you by a reservation, the current UTC date and time are used to record the transaction.
73
+
When you buy a reservation, the current UTC date and time are used to record the transaction.
74
74
75
75
You can purchase reservations from Azure portal, APIs, PowerShell, CLI. Read the following articles that apply to you when you're ready to make a reservation purchase:
Copy file name to clipboardExpand all lines: articles/frontdoor/migrate-tier-powershell.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: duongau
6
6
ms.service: azure-frontdoor
7
7
ms.custom: devx-track-azurepowershell
8
8
ms.topic: how-to
9
-
ms.date: 06/05/2023
9
+
ms.date: 10/15/2024
10
10
ms.author: duau
11
11
---
12
12
@@ -111,7 +111,7 @@ Your new Front Door profile with the configuration has been successfully created
111
111
ProvisioningState : Succeeded
112
112
Sku : Classic_AzureFrontDoor
113
113
Tags :
114
-
Id : /subscriptions/abcdef12-3456-7890-abcd-ef1234567890/resourcegroups/myAFDResourceGroup/providers/Microsoft.Network/frontdoorwebapplicationfirewallpolicies/myClassicFrontDoorWAF
114
+
Id : /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/myAFDResourceGroup/providers/Microsoft.Network/frontdoorwebapplicationfirewallpolicies/myClassicFrontDoorWAF
115
115
Name : myFrontDoorWAF
116
116
Type :
117
117
```
@@ -120,7 +120,7 @@ Your new Front Door profile with the configuration has been successfully created
1. Run the [Start-AzFrontDoorCdnProfilePrepareMigration](/powershell/module/az.cdn/start-azfrontdoorcdnprofilepreparemigration) command to prepare for migration. Replace the values for the resource group name, resource ID, profile name with your own values. For *SkuName* use either **Standard_AzureFrontDoor** or **Premium_AzureFrontDoor**. The *SkuName* is based on the output from the [Test-AzFrontDoorCdnProfileMigration](/powershell/module/az.cdn/test-azfrontdoorcdnprofilemigration) command.
126
126
@@ -155,7 +155,7 @@ Run the [Start-AzFrontDoorCdnProfilePrepareMigration](/powershell/module/az.cdn/
@@ -219,17 +219,17 @@ This example shows how to migrate a Front Door profile with multiple WAF policie
219
219
ProvisioningState : Succeeded
220
220
Sku : Classic_AzureFrontDoor
221
221
Tags :
222
-
Id : /subscriptions/abcdef12-3456-7890-abcd-ef1234567890/resourcegroups/myAFDResourceGroup/providers/Microsoft.Network/frontdoorwebapplicationfirewallpolicies/myClassicFrontDoorWAF
222
+
Id : /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/myAFDResourceGroup/providers/Microsoft.Network/frontdoorwebapplicationfirewallpolicies/myClassicFrontDoorWAF
223
223
Name : myFrontDoorWAF
224
224
Type :
225
225
```
226
226
227
227
1. Run the [New-AzFrontDoorCdnMigrationWebApplicationFirewallMappingObject](/powershell/module/az.cdn/new-azfrontdoorcdnmigrationwebapplicationfirewallmappingobject) command to create an in-memory object for WAF policy migration. Use the WAF ID in the last step for `MigratedFromId`. To use an existing WAF policy, replace the value for `MigratedToId` with a resource ID of a WAF policy that matches the Front Door tier you're migrating to. If you're creating a new WAF policy copy, you can change the name of the WAF policy in the resource ID.
0 commit comments