Skip to content

Commit a361bee

Browse files
Merge pull request #245275 from MJyot/v1-migration
Update retirement-faq.md
2 parents 8a0774d + d45342a commit a361bee

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/application-gateway/retirement-faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,19 @@ On April 28,2023 we announced retirement of Application gateway V1 on 28 April 2
1616

1717
### What is the official date Application Gateway V1 is cut off from creation?
1818

19-
New Customers aren't allowed to create v1 from 1 July 2023. However, any existing V1 customers can continue to create resources until August 2024 and manage V1 resources until the retirement date of 28 April 2026.
19+
New Customers will not be allowed to create V1 from 1 July 2023 onwards. However, any existing V1 customers can continue to create resources in existing subscriptions until August 2024 and manage V1 resources until the retirement date of 28 April 2026.
2020

2121
### What happens to existing Application Gateway V1 after 28 April 2026?
2222

2323
Once the deadline arrives V1 gateways aren't supported. Any V1 SKU resources that are still active are stopped, and force deleted.
2424

2525
### What is the definition of a new customer on Application Gateway V1 SKU?
2626

27-
Customers who didn't have Application Gateway V1 SKU in their subscriptions in the month of June 2023 are considered as new customers. These customers won’t be able to create new V1 gateways from 1 July 2023.
27+
Customers who didn't have Application Gateway V1 SKU in their subscriptions as of 4 July 2023 are considered as new customers. These customers won’t be able to create new V1 gateways going forward.
2828

2929
### What is the definition of an existing customer on Application Gateway V1 SKU?
3030

31-
Customers who had active or stopped but allocated Application Gateway V1 SKU in their subscriptions in the month of June 2023, are considered existing customers. These customers get until August 28, 2024 to create new V1 application gateways and until April 28,2026 to migrate their V1 gateways to V2.
31+
Customers who had active or stopped but allocated Application Gateway V1 SKU in their subscriptions as of 4 July 2023, are considered existing customers. These customers get until August 28, 2024 to create new V1 application gateways in their existing subscriptions and until April 28,2026 to migrate their V1 gateways to V2.
3232

3333
### Does this migration plan affect any of my existing workloads that run on Application Gateway V1 SKU?
3434

articles/application-gateway/v1-retirement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ We announced the deprecation of Application Gateway V1 on **April 28 ,2023**. St
2020

2121
- Deprecation announcement: April 28 ,2023
2222

23-
- No new subscriptions for V1 deployments: July 1,2023 - Application Gateway V1 is no longer available for deployment on new subscriptions from July 1 2023.
23+
- No new subscriptions for V1 deployments: July 1,2023 onwards - Application Gateway V1 is no longer available for deployment on new subscriptions from July 1 2023 onwards.
2424

2525
- No new V1 deployments: August 28, 2024 - V1 creation is stopped completely for all customers 28 August 2024 onwards.
2626

0 commit comments

Comments
 (0)