Merge pull request #290460 from MicrosoftDocs/release-asa-file-moves

Merge release-asa-file-moves into main

Author: Albertyang0

articles/spring-apps/.openpublishing.redirection.spring-apps.json

@@ -30,7 +30,7 @@ To find out if your applications meet expectations and to discover and predict i
 
 This article uses the well-known [PetClinic](https://github.com/azure-samples/spring-petclinic-microservices) sample app as the production application. For more information on how to deploy PetClinic to Azure Spring Apps and use MySQL as the persistent store, see the following articles:
 
-- [Deploy microservice applications to Azure Spring Apps](../enterprise/quickstart-deploy-microservice-apps.md?pivots=sc-standard&toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json)
+- [Deploy microservice applications to Azure Spring Apps](quickstart-deploy-microservice-apps.md?pivots=sc-standard)
 - [Integrate Azure Spring Apps with Azure Database for MySQL](quickstart-integrate-azure-database-mysql.md)
 
 Log Analytics and Application Insights are deeply integrated with Azure Spring Apps. You can use Log Analytics to diagnose your application with various log queries and use Application Insights to investigate production issues. For more information, see the following articles:
@@ -148,10 +148,10 @@ To use Application Insights to investigate the performance issues, use the follo
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Set up a staging environment](../enterprise/how-to-staging-environment.md)
+> [Set up a staging environment](how-to-staging-environment.md)
 
 > [!div class="nextstepaction"]
-> [Map an existing custom domain to Azure Spring Apps](../enterprise/how-to-custom-domain.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json)
+> [Map an existing custom domain to Azure Spring Apps](how-to-custom-domain.md)
 
 > [!div class="nextstepaction"]
-> [Use TLS/SSL certificates](../enterprise/how-to-use-tls-certificate.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json)
+> [Use TLS/SSL certificates](how-to-use-tls-certificate.md)

articles/spring-apps/enterprise/access-app-virtual-network.md renamed to articles/spring-apps/basic-standard/access-app-virtual-network.md

@@ -1,72 +1,72 @@
----
-title: Azure Spring Apps API breaking changes
-description: Describes the breaking changes introduced by the latest Azure Spring Apps stable API version.
-author: KarlErickson
-ms.author: yuwzho
-ms.service: azure-spring-apps
-ms.topic: how-to
-ms.date: 06/27/2024
-ms.custom: devx-track-java, devx-track-azurecli
----
-
-# Azure Spring Apps API breaking changes
-
-[!INCLUDE [deprecation-note](../includes/deprecation-note.md)]
-
-**This article applies to:** ✔️ Basic/Standard ✔️ Enterprise
-
-This article describes breaking changes introduced into the Azure Spring Apps API.
-
-The Azure Spring Apps service releases the new stable API version 2022-04-01. The new API version introduces breaking changes based on the previous stable API version 2020-07-01. We suggest that you update your API calls to the new API version.
-
-## Previous API deprecation date
-
-The previous API version 2020-07-01 will not be supported starting April, 2025.
-
-## API breaking changes from 2020-07-01 to 2022-04-01
-
-### Deprecate number value CPU and MemoryInGB in Deployments
-
-Deprecate field `properties.deploymentSettings.cpu` and `properties.deploymentSettings.memoryInGB` in the `Spring/Apps/Deployments` resource. Use `properties.deploymentSettings.resourceRequests.cpu` and `properties.deploymentSettings.resourceRequests.memory` instead.
-
-### RBAC role change for blue-green deployment
-
-Deprecate field `properties.activeDeploymentName` in the `Spring/Apps` resource. Use `POST/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.APPPLATFORM/SPRING/APPS/SETACTIVEDEPLOYMENTS` for blue-green deployment. This action needs a separate RBAC role `spring/apps/setActiveDeployments/action` to perform.
-
-### Move options from different property bags for the Spring/Apps/Deployments resource
-
-- Deprecate `properties.createdTime`. Use `systemData.createdAt`.
-- Deprecate `properties.deploymentSettings.jvmOptions`. Use `properties.source.jvmOptions`.
-- Deprecate `properties.deploymentSettings.jvmOptions`. Use `properties.source.runtimeVersion`.
-- Deprecate `properties.deploymentSettings.netCoreMainEntryPath`. Use `properties.source.netCoreMainEntryPath`.
-- Deprecate `properties.appName`, which you can extract from `id`.
-
-## Updates in the Azure CLI extension
-
-### Add new RBAC role for blue-green deployment
-
-You need to add RBAC role `spring/apps/setActiveDeployments/action` to perform the following Azure CLI commands:
-
-```azurecli
-az spring app set-deployment \
-    --resource-group <resource-group-name> \
-    --service <service-instance-name> \
-    --name <app-name> \
-    --deployment <deployment-name>
-az spring app unset-deployment \
-    --resource-group <resource-group-name> \
-    --service <service-instance-name> \
-    --name <app-name>
-```
-
-### Output updates
-
-If you're using the Azure CLI `spring-cloud` extension with a version lower than 3.0.0, and you want to upgrade the extension version or migrate to the `spring` extension, then you should take care of the following output updates.
-
-- `az spring app` command output: Remove `properties.activeDeploymentName`. Use `properties.activeDeployment.name` instead.
-- `az spring app` command output: Remove `properties.createdTime`. Use `systemData.createdAt` instead.
-- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.cpu`. Use `properties.activeDeployment.properties.deploymentSettings.resourceRequests.cpu` instead.
-- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.memoryInGB`. Use `properties.activeDeployment.properties.deploymentSettings.resourceRequests.memory` instead.
-- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.jvmOptions`. Use `properties.activeDeployment.properties.source.jvmOptions` instead.
-- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.runtimeVersion`. Use `properties.activeDeployment.properties.source.runtimeVersion` instead.
-- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.netCoreMainEntryPath`. Use `properties.activeDeployment.properties.source.netCoreMainEntryPath` instead.
+---
+title: Azure Spring Apps API breaking changes
+description: Describes the breaking changes introduced by the latest Azure Spring Apps stable API version.
+author: KarlErickson
+ms.author: yuwzho
+ms.service: azure-spring-apps
+ms.topic: how-to
+ms.date: 06/27/2024
+ms.custom: devx-track-java, devx-track-azurecli
+---
+
+# Azure Spring Apps API breaking changes
+
+[!INCLUDE [deprecation-note](../includes/deprecation-note.md)]
+
+**This article applies to:** ✔️ Basic/Standard ✔️ Enterprise
+
+This article describes breaking changes introduced into the Azure Spring Apps API.
+
+The Azure Spring Apps service releases the new stable API version 2022-04-01. The new API version introduces breaking changes based on the previous stable API version 2020-07-01. We suggest that you update your API calls to the new API version.
+
+## Previous API deprecation date
+
+The previous API version 2020-07-01 will not be supported starting April, 2025.
+
+## API breaking changes from 2020-07-01 to 2022-04-01
+
+### Deprecate number value CPU and MemoryInGB in Deployments
+
+Deprecate field `properties.deploymentSettings.cpu` and `properties.deploymentSettings.memoryInGB` in the `Spring/Apps/Deployments` resource. Use `properties.deploymentSettings.resourceRequests.cpu` and `properties.deploymentSettings.resourceRequests.memory` instead.
+
+### RBAC role change for blue-green deployment
+
+Deprecate field `properties.activeDeploymentName` in the `Spring/Apps` resource. Use `POST/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.APPPLATFORM/SPRING/APPS/SETACTIVEDEPLOYMENTS` for blue-green deployment. This action needs a separate RBAC role `spring/apps/setActiveDeployments/action` to perform.
+
+### Move options from different property bags for the Spring/Apps/Deployments resource
+
+- Deprecate `properties.createdTime`. Use `systemData.createdAt`.
+- Deprecate `properties.deploymentSettings.jvmOptions`. Use `properties.source.jvmOptions`.
+- Deprecate `properties.deploymentSettings.jvmOptions`. Use `properties.source.runtimeVersion`.
+- Deprecate `properties.deploymentSettings.netCoreMainEntryPath`. Use `properties.source.netCoreMainEntryPath`.
+- Deprecate `properties.appName`, which you can extract from `id`.
+
+## Updates in the Azure CLI extension
+
+### Add new RBAC role for blue-green deployment
+
+You need to add RBAC role `spring/apps/setActiveDeployments/action` to perform the following Azure CLI commands:
+
+```azurecli
+az spring app set-deployment \
+    --resource-group <resource-group-name> \
+    --service <service-instance-name> \
+    --name <app-name> \
+    --deployment <deployment-name>
+az spring app unset-deployment \
+    --resource-group <resource-group-name> \
+    --service <service-instance-name> \
+    --name <app-name>
+```
+
+### Output updates
+
+If you're using the Azure CLI `spring-cloud` extension with a version lower than 3.0.0, and you want to upgrade the extension version or migrate to the `spring` extension, then you should take care of the following output updates.
+
+- `az spring app` command output: Remove `properties.activeDeploymentName`. Use `properties.activeDeployment.name` instead.
+- `az spring app` command output: Remove `properties.createdTime`. Use `systemData.createdAt` instead.
+- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.cpu`. Use `properties.activeDeployment.properties.deploymentSettings.resourceRequests.cpu` instead.
+- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.memoryInGB`. Use `properties.activeDeployment.properties.deploymentSettings.resourceRequests.memory` instead.
+- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.jvmOptions`. Use `properties.activeDeployment.properties.source.jvmOptions` instead.
+- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.runtimeVersion`. Use `properties.activeDeployment.properties.source.runtimeVersion` instead.
+- `az spring app` command output: Remove `properties.activeDeployment.properties.deploymentSettings.netCoreMainEntryPath`. Use `properties.activeDeployment.properties.source.netCoreMainEntryPath` instead.

articles/spring-apps/basic-standard/application-observability.md

@@ -36,7 +36,7 @@ You can choose any version of Spring Boot or Spring Cloud that's compatible with
 
 For new versions, Azure Spring Apps supports the latest Spring Boot or Spring Cloud major version starting 30 days after its release. The latest minor version is supported as soon as it's released.
 
-For old versions, Azure Spring Apps doesn't require you to upgrade Spring Boot or Spring Cloud to receive support. However, with the officially supported new versions, you can get the best experience with some of the managed components - for example, Config Server and Eureka Server for the Standard consumption and dedicated plan and the Standard plan, [Tanzu components](vmware-tanzu-components.md) for the Enterprise plan, and metric collection for all plans.
+For old versions, Azure Spring Apps doesn't require you to upgrade Spring Boot or Spring Cloud to receive support. However, with the officially supported new versions, you can get the best experience with some of the managed components - for example, Config Server and Eureka Server for the Standard consumption and dedicated plan and the Standard plan, [Tanzu components](../enterprise/vmware-tanzu-components.md) for the Enterprise plan, and metric collection for all plans.
 
 For more information, see the official support timeline of [Spring Boot](https://spring.io/projects/spring-boot#support) and [Spring Cloud](https://spring.io/projects/spring-cloud#overview). The Enterprise plan provides commercial support for Spring Boot, while the other plans provide OSS support.
 
@@ -48,7 +48,7 @@ The following sections describe the version support that applies to the Enterpri
 
 You can deploy polyglot applications to the Enterprise plan with source code. To enjoy the best stability, use SDKs with LTS versions that are officially supported.
 
-When you deploy your polyglot applications to the Enterprise plan, assign specific LTS versions for the SDKs. Otherwise, the default SDK version might change during the regular upgrades for builder components. For more information about deploying polyglot apps, see [How to deploy polyglot apps in the Azure Spring Apps Enterprise plan](how-to-enterprise-deploy-polyglot-apps.md).
+When you deploy your polyglot applications to the Enterprise plan, assign specific LTS versions for the SDKs. Otherwise, the default SDK version might change during the regular upgrades for builder components. For more information about deploying polyglot apps, see [How to deploy polyglot apps in the Azure Spring Apps Enterprise plan](../enterprise/how-to-enterprise-deploy-polyglot-apps.md).
 
 | Type   | Support policy                                                                                        |
 |--------|-------------------------------------------------------------------------------------------------------|

articles/spring-apps/enterprise/breaking-changes.md renamed to articles/spring-apps/basic-standard/breaking-changes.md

@@ -56,7 +56,7 @@ The provisioning state is accessible only from the CLI. The status is reported a
 
 ### Registration status
 
-The app registration status shows the state in service discovery. The Basic/Standard plan uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-netflix/multi/multi__service_discovery_eureka_clients.html#_eurekas_health_checks). The Enterprise pricing plan uses [Tanzu Service Registry](how-to-enterprise-service-registry.md) for service discovery.
+The app registration status shows the state in service discovery. The Basic/Standard plan uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-netflix/multi/multi__service_discovery_eureka_clients.html#_eurekas_health_checks). The Enterprise pricing plan uses [Tanzu Service Registry](../enterprise/how-to-enterprise-service-registry.md) for service discovery.
 
 ## App instances status
 

articles/spring-apps/enterprise/concept-app-customer-responsibilities.md renamed to articles/spring-apps/basic-standard/concept-app-customer-responsibilities.md

@@ -67,9 +67,9 @@ When you open the app to the public, these actuator endpoints are exposed to the
 
 In the Enterprise plan, there are two ways to secure the access:
 
-- You can disable the public endpoint of apps and configure a routing rule in VMware Spring Cloud Gateway to disable actuator access from the public. For more information, see [Configure VMware Spring Cloud Gateway](./how-to-configure-enterprise-spring-cloud-gateway.md).
+- You can disable the public endpoint of apps and configure a routing rule in VMware Spring Cloud Gateway to disable actuator access from the public. For more information, see [Configure VMware Spring Cloud Gateway](../enterprise/how-to-configure-enterprise-spring-cloud-gateway.md).
 
-- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publically accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](./how-to-use-application-live-view.md).
+- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publically accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](../enterprise/how-to-use-application-live-view.md).
 
 ## Next steps
 

articles/spring-apps/enterprise/concept-app-status.md renamed to articles/spring-apps/basic-standard/concept-app-status.md

@@ -212,7 +212,7 @@ The following table applies to the Tanzu Spring Cloud Gateway in Enterprise plan
 
 ## Next steps
 
-* [Quickstart: Monitoring Azure Spring Apps apps with logs, metrics, and tracing](../basic-standard/quickstart-logs-metrics-tracing.md)
+* [Quickstart: Monitoring Azure Spring Apps apps with logs, metrics, and tracing](quickstart-logs-metrics-tracing.md)
 * [Analyze metrics with Azure Monitor metrics explorer](/azure/azure-monitor/essentials/analyze-metrics)
 * [Analyze logs and metrics with diagnostics settings](./diagnostic-services.md)
 * [Tutorial: Monitor Spring app resources using alerts and action groups](./tutorial-alerts-action-groups.md)