Skip to content

Commit 3a9bc2e

Browse files
authored
Merge pull request #295971 from seligj95/removenotes
Remove ASEv3 callouts in notes of all docs
2 parents 29526a8 + 01857b7 commit 3a9bc2e

11 files changed

+5
-50
lines changed

articles/app-service/environment/app-service-app-service-environment-custom-settings.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,6 @@ ms.custom: mvc, devx-track-arm-template
1616

1717
Because App Service Environments are isolated to a single customer, there are certain configuration settings that can be applied exclusively to App Service Environments. This article documents the various specific customizations that are available for App Service Environments.
1818

19-
> [!NOTE]
20-
> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
21-
>
22-
2319
If you do not have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
2420

2521
You can store App Service Environment customizations by using an array in the new **clusterSettings** attribute. This attribute is found in the "Properties" dictionary of the *hostingEnvironments* Azure Resource Manager entity.

articles/app-service/environment/auto-migration.md

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -10,29 +10,19 @@ ms.custom: references_regions
1010
# Prevent and resolve issues caused by an auto-migration of an App Service Environment
1111

1212
> [!IMPORTANT]
13-
> App Service Environment v1 and v2 are retired and no longer supported. If you have an App Service Environment v1 or v2, you must migrate to App Service Environment v3. For more information, see [Upgrade to App Service Environment v3](upgrade-to-asev3.md).
13+
> App Service Environment v1 and v2 are retired and no longer supported.
1414
>
15-
> Auto-migrations are migrations that are initiated by Microsoft. As of September 1, 2024, the platform will attempt to auto-migrate any remaining App Service Environment v1 and v2 on a best-effort basis using the [in-place migration feature](migrate.md), but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration is not feasible, your resources and associated app data will be deleted. We strongly urge you to act now to avoid either of these extreme scenarios.
15+
> Auto-migrations are migrations that are initiated by Microsoft. As of September 1, 2024, the platform auto-migrated any remaining App Service Environment v1 and v2 on a best-effort basis using the [in-place migration feature](migrate.md), but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration is not feasible, your resources and associated app data were deleted.
1616
>
1717
1818
If you have an App Service Environment v1 or v2 that was auto-migrated to App Service Environment v3, you might encounter issues with your apps or services. This article provides guidance on how to address these issues.
1919

2020
## Overview
2121

22-
After September 1, 2024, all App Service Environments v1 and v2 are eligible to be automatically migrated (auto-migrated) to App Service Environment v3 at any given time unless otherwise stated. The platform initiates auto-migrations, which are necessary to ensure that your App Service Environment is running on a supported platform.
23-
24-
> [!NOTE]
25-
> Auto-migrations and deletions are done in batches. If your App Service Environment isn't auto-migrated yet, it's subject to auto-migration or deletion at any time.
26-
>
22+
After September 1, 2024, all App Service Environments v1 and v2 were automatically migrated (auto-migrated) to App Service Environment v3. The platform initiated auto-migrations, which are necessary to ensure that your App Service Environment is running on a supported platform.
2723

2824
Auto-migrations are done using the [in-place migration feature](migrate.md). There's about one hour of downtime during the migration process. The inbound and outbound IP addresses of your App Service Environment might change during the migration process. Downtime might be longer if you have dependencies on these IP addresses. Downtime might also be longer if you use features that aren't supported in App Service Environment v3.
2925

30-
## Grace period
31-
32-
> [!NOTE]
33-
> As of January 1, 2025, grace periods aren't available. Migrate immediately or open a support ticket to discuss your options.
34-
>
35-
3626
## Auto-migration limitations
3727

3828
Auto-migrations are done using the [in-place migration feature](migrate.md). The following limitations apply to auto-migrations, similar to the [limitations of in-place migrations](migrate.md#in-place-migration-feature-limitations):
@@ -188,8 +178,6 @@ We encourage you to complete migration to Azure App Service Environment v3 as so
188178

189179
## Frequently asked questions
190180

191-
- **Why am I experiencing temporary application outages on my App Service Environment v1/v2?**
192-
The Azure platform is preparing for the retirement of Cloud Services (Classic), which is the infrastructure that App Service Environment v1 and v2 run on. As part of this preparation, you should expect temporary outages and service disruptions. To minimize the effect of these disruptions, we recommend that you migrate to App Service Environment v3 as soon as possible.
193181
- **Why was my App Service Environment auto-migrated?**
194182
App Service Environment v1 and v2 are retired and no longer supported. The supporting infrastructure for App Service Environment v1 and v2 is being decommissioned. To ensure that your App Service Environment is running on a supported platform, Microsoft initiates auto-migrations to App Service Environment v3.
195183
- **Why are my apps not working after auto-migration?**

articles/app-service/environment/configure-network-settings.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,6 @@ ms.author: madsd
1414

1515
Because App Service Environments are isolated to the individual customer, there are certain configuration settings that can be applied exclusively to App Service Environments. This article documents the various specific network customizations that are available for App Service Environment v3.
1616

17-
> [!NOTE]
18-
> This article is about App Service Environment v3, which is used with isolated v2 App Service plans.
19-
2017
If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
2118

2219
App Service Environment network customizations are stored in a subresource of the *hostingEnvironments* Azure Resource Manager entity called networking.

articles/app-service/environment/creation.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,6 @@ ms.author: madsd
1111

1212
[App Service Environment][Intro] is a single-tenant deployment of Azure App Service. You use it with an Azure virtual network. You need one subnet for a deployment of App Service Environment, and this subnet can't be used for anything else.
1313

14-
> [!NOTE]
15-
> This article is about App Service Environment v3, which is used with Isolated v2 App Service plans.
16-
1714
## Before you create your App Service Environment
1815

1916
After you create your App Service Environment, you can't change any of the following:

articles/app-service/environment/how-to-create-from-template.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,6 @@ ms.author: madsd
1111

1212
App Service Environment can be created using an Azure Resource Manager template allowing you to do repeatable deployment.
1313

14-
> [!NOTE]
15-
> This article is about App Service Environment v3, which is used with Isolated v2 App Service plans.
16-
1714
## Overview
1815

1916
Azure App Service Environment can be created with an internet-accessible endpoint or an endpoint on an internal address in an Azure Virtual Network. When created with an internal endpoint, that endpoint is provided by an Azure component called an internal load balancer (ILB). The App Service Environment on an internal IP address is called an ILB ASE. The App Service Environment with a public endpoint is called an External ASE.

articles/app-service/environment/how-to-custom-domain-suffix.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,6 @@ An App Service Environment is an Azure App Service feature that provides a fully
1515

1616
If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
1717

18-
> [!NOTE]
19-
> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
20-
>
21-
2218
The custom domain suffix defines a root domain used by the App Service Environment. In the public variation of Azure App Service, the default root domain for all web apps is *azurewebsites.net*. For ILB App Service Environments, the default root domain is *appserviceenvironment.net*. However, since an ILB App Service Environment is internal to a customer's virtual network, customers can use a root domain in addition to the default one that makes sense for use within a company's internal virtual network. For example, a hypothetical Contoso Corporation might use a default root domain of *internal.contoso.com* for apps that are intended to only be resolvable and accessible within Contoso's virtual network. An app in this virtual network could be reached by accessing *APP-NAME.internal.contoso.com*.
2319

2420
The custom domain suffix is for the App Service Environment. This feature is different from a custom domain binding on an App Service. For more information on custom domain bindings, see [Map an existing custom DNS name to Azure App Service](../app-service-web-tutorial-custom-domain.md).

articles/app-service/environment/how-to-upgrade-preference.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,6 @@ Azure App Service is regularly updated to provide new features, new runtime vers
1414

1515
If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
1616

17-
> [!NOTE]
18-
> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
19-
>
20-
2117
With App Service Environment v3, you can specify your preference for when and how the planned maintenance is applied. The upgrade can be applied automatically or manually. Even with your preference set to automatic, you have some options to influence the timing.
2218

2319
## Automatic upgrade preference

articles/app-service/environment/networking.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,6 @@ ms.author: madsd
1111

1212
App Service Environment is a single-tenant deployment of Azure App Service that hosts Windows and Linux containers, web apps, API apps, logic apps, and function apps. When you install an App Service Environment, you pick the Azure virtual network that you want it to be deployed in. All of the inbound and outbound application traffic is inside the virtual network you specify. You deploy into a single subnet in your virtual network, and nothing else can be deployed into that subnet.
1313

14-
> [!NOTE]
15-
> This article is about App Service Environment v3, which is used with Isolated v2 App Service plans.
16-
1714
## Subnet requirements
1815

1916
The following are the minimum set of requirements for the subnet your App Service Environment is in.
@@ -34,7 +31,7 @@ If you use a smaller subnet, be aware of the following limitations:
3431
- If you run out of addresses within your subnet, you can be restricted from scaling out your App Service plans in the App Service Environment. Another possibility is that you can experience increased latency during intensive traffic load, if Microsoft isn't able to scale the supporting infrastructure.
3532

3633
>[!NOTE]
37-
> Windows Containers uses an additional IP address per app for each App Service plan instance, and you need to size the subnet accordingly. If your App Service Environment has for example 2 Windows Container App Service plans each with 25 instances and each with 5 apps running, you will need 300 IP addresses and additional addresses to support horizontal (in/out) scale.
34+
> Windows Containers use an additional IP address per app for each App Service plan instance, and you need to size the subnet accordingly. If your App Service Environment has for example 2 Windows Container App Service plans each with 25 instances and each with 5 apps running, you will need 300 IP addresses and additional addresses to support horizontal (in/out) scale.
3835
>
3936
> Sample calculation:
4037
>

articles/app-service/environment/overview-certificates.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,6 @@ ms.author: madsd
88
---
99

1010
# Certificates and the App Service Environment
11-
> [!NOTE]
12-
> This article is about the App Service Environment v3, which is used with Isolated v2 App Service plans
13-
>
1411

1512
The App Service Environment is a deployment of the Azure App Service that runs within your Azure virtual network. It can be deployed with an internet accessible application endpoint or an application endpoint that is in your virtual network. If you deploy the App Service Environment with an internet accessible endpoint, that deployment is called an External App Service Environment. If you deploy the App Service Environment with an endpoint in your virtual network, that deployment is called an ILB App Service Environment. You can learn more about the ILB App Service Environment from the [Create and use an ILB App Service Environment](./creation.md) document.
1613

@@ -70,7 +67,7 @@ Export-Certificate -Cert $certThumbprint -FilePath $fileName -Type CERT
7067
If your app acts as a server in a client-server model, either behind a reverse proxy or directly with private client and you're using a private CA certificate, you need to upload the server certificate (*.pfx* file) with the full certificate chain to your app and bind the certificate to the custom domain. Because the infrastructure is dedicated to your App Service Environment, the full certificate chain is added to the trust store of the servers. You only need to upload the certificate once to use it with apps that are in the same App Service Environment.
7168

7269
>[!NOTE]
73-
> If you uploaded your certificate prior to 1. October 2023, you will need to reupload and rebind the certificate for the full certificate chain to be added to the servers.
70+
> If you uploaded your certificate prior to October 1, 2023, you need to reupload and rebind the certificate for the full certificate chain to be added to the servers.
7471
7572
Follow the [secure custom domain with TLS/SSL](../configure-ssl-bindings.md) tutorial to upload/bind your private CA rooted certificate to the app in your App Service Environment.
7673

articles/app-service/environment/overview.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,6 @@ ms.custom: "UpdateFrequency3, references_regions"
1212

1313
An App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for running App Service apps securely at high scale. Unlike the App Service public multitenant offering where supporting infrastructure is shared, with App Service Environment, compute is dedicated to a single customer. For more information on the differences between App Service Environment and App Service public multitenant, see the [comparison of the offerings](ase-multi-tenant-comparison.md).
1414

15-
> [!NOTE]
16-
> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
17-
>
1815
An App Service Environment can host your:
1916

2017
- Windows web apps

0 commit comments

Comments
 (0)