Merge pull request #181497 from v-kevinmic3/enterprise

Enterprise Tier Documentation

Author: AnnaMHuff

articles/spring-cloud/access-app-virtual-network.md

@@ -12,7 +12,9 @@ ms.devlang: azurecli
 
 # Access your application in a private network
 
-This document explains how to access an endpoint for your application in a private network.
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
+This article explains how to access an endpoint for your application in a private network.
 
 When **Assign Endpoint** on applications in an Azure Spring Cloud service instance is deployed in your virtual network, the endpoint is a private fully qualified domain name (FQDN). The domain is only accessible in the private network. Apps and services use the application endpoint. They include the *Test Endpoint* described in [View apps and deployments](./how-to-staging-environment.md#view-apps-and-deployments). *Log streaming*, described in [Stream Azure Spring Cloud app logs in real-time](./how-to-log-streaming.md), also works only within the private network.
 
@@ -53,7 +55,7 @@ Find the IP Address for your Spring Cloud services. Customize the value of your
 If you have your own DNS solution for your virtual network, like Active Directory Domain Controller, Infoblox, or another, you need to point the domain `*.private.azuremicroservices.io` to the [IP address](#find-the-ip-for-your-application). Otherwise, you can follow the following instructions to create an **Azure Private DNS Zone** in your subscription to translate/resolve the private fully qualified domain name (FQDN) to its IP address.
 
 > [!NOTE]
-> If you are using Azure China, please replace `private.azuremicroservices.io` with `private.microservices.azure.cn` in this documentation. Learn more about [Check Endpoints in Azure](/azure/china/resources-developer-guide#check-endpoints-in-azure).
+> If you are using Azure China, please replace `private.azuremicroservices.io` with `private.microservices.azure.cn` in this article. Learn more about [Check Endpoints in Azure](/azure/china/resources-developer-guide#check-endpoints-in-azure).
 
 ## Create a private DNS zone
 
@@ -172,7 +174,7 @@ Use the [IP address](#find-the-ip-for-your-application) to create the A record i
 
 ## Assign private FQDN for your application
 
-After following the procedure in [Build and deploy microservice applications](./how-to-deploy-in-azure-virtual-network.md), you can assign a private FQDN for your application.
+After following the procedure in [Deploy Azure Spring Cloud in a virtual network](./how-to-deploy-in-azure-virtual-network.md), you can assign a private FQDN for your application.
 
 #### [Portal](#tab/azure-portal)
 
@@ -210,8 +212,5 @@ After the assignment, you can access the application's private FQDN in the priva
 ## Next steps
 
 - [Expose applications to Internet - using Application Gateway](./expose-apps-gateway.md)
-
-## See also
-
 - [Troubleshooting Azure Spring Cloud in VNET](./troubleshooting-vnet.md)
 - [Customer Responsibilities for Running Azure Spring Cloud in VNET](./vnet-customer-responsibilities.md)

articles/spring-cloud/concept-app-status.md

@@ -13,34 +13,38 @@ ms.custom: devx-track-java
 
 **This article applies to:** ✔️ Java ✔️ C#
 
-The Azure Spring Cloud UI delivers information about the status of running applications.  There is an **Apps** option for each resource group in a subscription that displays general status of application types.  For each application type, there is display of **Application instances**.
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
+This article shows you how to view app status for Azure Spring Cloud.
+
+The Azure Spring Cloud UI delivers information about the status of running applications. There is an **Apps** option for each resource group in a subscription that displays general status of application types. For each application type, there's a display of **Application instances**.
 
 ## Apps status
 
 To view general status of an application type, select **Apps** in the left navigation pane of a resource group. The result displays the status of the deployed app:
 
-* **Provisioning Status** shows the deployment’s provisioning state
-* **Running instance** shows how many app instances are running/how many app instances are desired. If the app should be stopped, this column shows *stopped*.
-* **Registered Instance** shows how many app instances are registered to eureka/how many app instance are desired. If the app should be stopped, this column shows *stopped*.
+* **Provisioning Status**: Shows the deployment’s provisioning state.
+* **Running instance**: Shows how many app instances are running and how many app instances you desire. If you stop the app, this column shows **stopped**.
+* **Registered Instance**: Shows how many app instances are registered to Eureka and how many app instances you desire. If you stop the app, this column shows **stopped**. Note that Eureka is not applicable to enterprise tier. For more information if you're using the enterprise tier, see [Use Service Registry](how-to-enterprise-service-registry.md).
 
 ![Apps status](media/spring-cloud-concept-app-status/apps-ui-status.png)
 
-**The deployment status is reported as one of the following values:**
+The deployment status is reported as one of the following values:
 
-| Enum | Definition |
-|:--:|:----------------:|
+| Enum    | Definition                        |
+|---------|-----------------------------------|
 | Running | The deployment SHOULD be running. |
 | Stopped | The deployment SHOULD be stopped. |
 
-**The provisioning state is accessible only from the CLI.  It is reported as one of the following values:**
+The provisioning state is accessible only from the CLI.  It is reported as one of the following values:
 
-| Enum | Definition |
-|:--:|:----------------:|
-| Creating | The resource is creating. |
-| Updating | The resource is updating. |
+| Enum      | Definition                                              |
+|-----------|---------------------------------------------------------|
+| Creating  | The resource is creating.                               |
+| Updating  | The resource is updating.                               |
 | Succeeded | Successfully supplied resources and deploys the binary. |
-| Failed | Failed to achieve the *Succeeded* goal. |
-| Deleting | The resource is being deleted. This prevents operation, and the resource is not available in this status. |
+| Failed    | Failed to achieve the *Succeeded* goal.                 |
+| Deleting  | The resource is being deleted. This prevents operation, and the resource is not available in this status. |
 
 ## App instances status
 
@@ -51,23 +55,23 @@ To view the status of a specific instance of a deployed app, select the **Name**
 
 ![App instances status](media/spring-cloud-concept-app-status/apps-ui-instance-status.png)
 
-**The instance status is reported as one of the following values:**
+The instance status is reported as one of the following values:
 
-| Enum | Definition |
-|:--:|:----------------:|
-| Starting | The binary is successfully deployed to the given instance. Instance booting the jar file may fail because jar cannot run properly. |
-| Running | The instance works. |
-| Failed | The app instance failed to start user’s binary after several retries. |
+| Enum        | Definition |
+|-------------|------------|
+| Starting    | The binary is successfully deployed to the given instance. Instance booting the jar file may fail because jar cannot run properly. |
+| Running     | The instance works. |
+| Failed      | The app instance failed to start user’s binary after several retries. |
 | Terminating | The app instance is shutting down. |
 
-**The discovery status of the instance is reported as one of the following values:**
+The discovery status of the instance is reported as one of the following values:
 
-| Enum | Definition |
-|:--:|:----------------:|
-| UP | The app instance is registered to eureka and ready to receive traffic |
+| Enum           | Definition |
+|----------------|------------|
+| UP             | The app instance is registered to Eureka and ready to receive traffic |
 | OUT_OF_SERVICE | The app instance is registered to Eureka and able to receive traffic. but shuts down for traffic intentionally. |
-| DOWN | The app instance is not registered to Eureka or is registered but not able to receive traffic. |
+| DOWN           | The app instance is not registered to Eureka or is registered but not able to receive traffic. |
 
-## See also
+## Next steps
 
 * [Prepare a Spring or Steeltoe application for deployment in Azure Spring Cloud](how-to-prepare-app-deployment.md)

articles/spring-cloud/concept-manage-monitor-app-spring-boot-actuator.md

@@ -11,7 +11,9 @@ ms.custom: devx-track-java
 
 # Manage and monitor app with Azure Spring Boot Actuator
 
-**This article applies to:** ✔️ Java
+**This article applies to:** ✔️ Java ❌ C#
+
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
 
 After deploying new binary to your app, you may want to check the functionality and see information about your running application. This article explains how to access the API from a test endpoint provided by Azure Spring Cloud and expose the production-ready features for your app.
 

articles/spring-cloud/concept-metrics.md

@@ -11,6 +11,8 @@ ms.custom: devx-track-java
 
 # Metrics for Azure Spring Cloud
 
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
 Azure Metrics explorer is a component of the Microsoft Azure portal that allows plotting charts, visually correlating trends, and investigating spikes and dips in metrics. Use the metrics explorer to investigate the health and utilization of your resources.
 
 In Azure Spring Cloud, there are two viewpoints for metrics.

articles/spring-cloud/concept-security-controls.md

@@ -13,6 +13,8 @@ ms.custom: devx-track-java
 
 **This article applies to:** ✔️ Java ✔️ C#
 
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
 Security controls are built in into Azure Spring Cloud Service.
 
 A security control is a quality or feature of an Azure service that contributes to the service's ability to prevent, detect, and respond to security vulnerabilities.  For each control, we use *Yes* or *No* to indicate whether it is currently in place for the service.  We use *N/A* for a control that is not applicable to the service.

articles/spring-cloud/concept-understand-app-and-deployment.md

@@ -13,11 +13,13 @@ ms.custom: devx-track-java
 
 **This article applies to:** ✔️ Java ✔️ C#
 
-**App** and **Deployment** are the two key concepts in the resource model of Azure Spring Cloud. In Azure Spring Cloud, an *App* is an abstraction of one business app or one microservice.  One version of code or binary deployed as the *App* runs in a *Deployment*.  Apps run in an *Azure Spring Cloud Service Instance*, or simply *service instance*, as shown next.
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
+**App** and **Deployment** are the two key concepts in the resource model of Azure Spring Cloud. In Azure Spring Cloud, an *App* is an abstraction of one business app.  One version of code or binary deployed as the *App* runs in a *Deployment*.  Apps run in an *Azure Spring Cloud Service Instance*, or simply *service instance*, as shown next.
 
  ![Apps and Deployments](./media/spring-cloud-app-and-deployment/app-deployment-rev.png)
 
-You can have multiple service instances within a single Azure subscription, but the Azure Spring Cloud Service is easiest to use when all of the Apps that make up a business app or microservice reside within a single service instance.
+You can have multiple service instances within a single Azure subscription, but the Azure Spring Cloud Service is easiest to use when all of the Apps that make up a business app reside within a single service instance.
 
 Azure Spring Cloud standard tier allows one App to have one production deployment and one staging deployment, so that you can do blue/green deployment on it easily.
 
@@ -53,6 +55,6 @@ The following features/properties are defined on Deployment level, and will be e
 * **An App can have at most two Deployments**: Creating more than two deployments is blocked by the API. Deploy your new binary to either the existing production or staging deployment.
 * **Deployment management is not available in Basic Tier**: Use Standard tier for Blue-Green deployment capability.
 
-## See also
+## Next steps
 
 * [Set up a staging environment in Azure Spring Cloud](./how-to-staging-environment.md)

articles/spring-cloud/concepts-blue-green-deployment-strategies.md

@@ -11,6 +11,8 @@ ms.custom: devx-track-java
 
 # Blue-green deployment strategies in Azure Spring Cloud
 
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
 This article describes the blue-green deployment support in Azure Spring Cloud.
 
 Azure Spring Cloud (Standard tier and higher) permits two deployments for every app, only one of which receives production traffic. This pattern is commonly known as blue-green deployment. Azure Spring Cloud's support for blue-green deployment, together with a [Continuous Delivery (CD)](/devops/deliver/what-is-continuous-delivery) pipeline and rigorous automated testing, allows agile application deployments with high confidence.

articles/spring-cloud/connect-managed-identity-to-azure-sql.md

@@ -11,7 +11,9 @@ ms.custom: devx-track-java
 
 # Use a managed identity to connect Azure SQL Database to an Azure Spring Cloud app
 
-**This article applies to:** ✔️ Java
+**This article applies to:** ✔️ Java ❌ C#
+
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
 
 This article shows you how to create a managed identity for an Azure Spring Cloud app and use it to access Azure SQL Database.
 

articles/spring-cloud/diagnostic-services.md

@@ -13,6 +13,10 @@ ms.custom: devx-track-java
 
 **This article applies to:** ✔️ Java ✔️ C#
 
+**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
+
+This article shows you how to analyze diagnostics data in Azure Spring Cloud.
+
 Using the diagnostics functionality of Azure Spring Cloud, you can analyze logs and metrics with any of the following services:
 
 * Use Azure Log Analytics, where the data is written to Azure Storage. There is a delay when exporting logs to Log Analytics.
@@ -52,8 +56,8 @@ To get started, enable one of these services to receive the data. To learn about
 1. Select **Save**.
 
 > [!NOTE]
-> 1. There might be a gap of up to 15 minutes between when logs or metrics are emitted and when they appear in your storage account, your event hub, or Log Analytics.
-> 1. If the Azure Spring Cloud instance is deleted or moved, the operation will not cascade to the **diagnostics settings** resources. The **diagnostics settings** resources have to be deleted manually before the operation against its parent, the Azure Spring Cloud instance. Otherwise, if a new Azure Spring Cloud instance is provisioned with the same resource ID as the deleted one, or if the Azure Spring Cloud instance is moved back, the previous **diagnostics settings** resources continue extending it.
+> There might be a gap of up to 15 minutes between when logs or metrics are emitted and when they appear in your storage account, your event hub, or Log Analytics.
+> If the Azure Spring Cloud instance is deleted or moved, the operation won't cascade to the **diagnostics settings** resources. The **diagnostics settings** resources have to be deleted manually before the operation against its parent, the Azure Spring Cloud instance. Otherwise, if a new Azure Spring Cloud instance is provisioned with the same resource ID as the deleted one, or if the Azure Spring Cloud instance is moved back, the previous **diagnostics settings** resources continue extending it.
 
 ## View the logs and metrics