Merge pull request #270509 from HollyCl/concepts328

updated quickstart-subscription and concept-lcm articles

Author: Jill Grant

articles/operator-5g-core/concept-centralized-lifecycle-management.md

@@ -5,50 +5,38 @@ author: HollyCl
 ms.author: HollyCl
 ms.service: azure-operator-5g-core
 ms.topic: concept-article #required; leave this attribute/value as-is.
-ms.date: 03/07/2024
+ms.date: 03/28/2024
 
 #CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
 ---
 
 
 # Centralized Lifecycle Management in Azure Operator 5G Core Preview
 
-The Azure Operator 5G Core (preview) Resource Provider (RP) is responsible for the lifecycle management (LCM) of the following Azure Operator 5G Core network functions:
+The Azure Operator 5G Core (preview) Resource Provider (RP) is responsible for the lifecycle management (LCM) of the following Azure Operator 5G Core network functions and the dependent shared services:
 - Access and Mobility Management Function (AMF)
 - Session Management Function (SMF)
 - User Plane Function (UPF)
 - Network Repository Function (NRF)
 - Network Slice Selection Function (NSSF)
-- Mobility Management Entity (MME)
-
- > [!NOTE]
->  AMF and MME can be deployed as combined network functions by adjusting the helm manifests. 
 
 Lifecycle Management consists of the following operations:
 - Instantiation
 - Upgrade (out of scope for Public Preview)
 - Termination
 
-The Azure Resource Manager (ARM) model that is used for lifecycle management is shown here: 
-
-> [!NOTE]
-> The CNFs are included for Public Preview while the VNFs (VNFAgent and vMME) are targeted for GA release.
+The Azure Resource Manager (ARM) model that is used for lifecycle management is shown here. 
 
 :::image type="content" source="media/concept-centralized-lifecycle-management/lifecycle-management-model.png" alt-text="Diagram showing the containerized network functions and virtualized network functions responsible for lifecycle management in Azure Operator 5G Core.":::
 
-Network function deployments require fully deployed local Platform as a Service (PaaS) components (provided by the ClusterServices resource). Any attempt to deploy a network function resource before the ClusterServices deployment fails. ARM templates are serial in nature and don't proceed until dependent templates are complete. This process prevents network function templates from being deployed before the ClusterServices template is complete. Observability deployments also fail if local PaaS deployment is incomplete.
-
-The deployments for cMME and AnyG are variations on the existing helm charts. Creation of these functions is a matter of specifying different input Helm values. The Azure Operator 5G Core RP uses the Network Function Manager (NFM) Resource Provider to perform this activity. 
+Network function deployments require fully deployed local Platform as a Service (PaaS) components (provided by the ClusterServices resource). Any attempt to deploy a network function resource before the ClusterServices deployment fails. The Azure Operator 5G Core ARM templates are serial in nature and don't proceed until dependent templates are complete. This process prevents network function templates from being deployed before the ClusterServices template is complete. Observability deployments also fail if local PaaS deployment is incomplete.
 
-Azure Operator 5G Core network function images and Helm charts are Azure-managed and accessed by the Azure Operator 5G Core Resource Provider for lifecycle management operations.  
 
 ## Local observability
 
-Local Observability is provided by Azure Operator 5G Core Observability components listed in the diagram. Because the Observability function is local, it also available in break-glass scenarios for Nexus where the interfaces can be accessed locally.
+Local Observability is provided by Azure Operator 5G Core Observability components including Prometheus, FluentD, Elastic, Grafana, and Jaegar. Because the Observability function is local, it also available in break-glass scenarios for Nexus when connectivity to Azure is down and the services can be accessed locally. 
 
-:::image type="content" source="media/concept-centralized-lifecycle-management/local-observability.png" alt-text="Diagram showing how Azure Operator 5G Core observability components are used in Azure Operator 5G Core." lightbox="media/concept-centralized-lifecycle-management/local-observability.png":::
-
-
-## Next Step
+## Related content
 
-- [Quickstart: Get Access to Azure Operator 5G Core](quickstart-subscription.md)
+- [Quickstart: Get Access to Azure Operator 5G Core](quickstart-subscription.md)
+- [Deployment order for clusters, network functions, and observability](concept-deployment-order.md)

articles/operator-5g-core/media/concept-centralized-lifecycle-management/lifecycle-management-model.png

@@ -5,7 +5,7 @@ author: HollyCl
 ms.author: HollyCl
 ms.service: azure-operator-5g-core
 ms.topic: quickstart #required; leave this attribute/value as-is
-ms.date: 03/07/2024
+ms.date: 03/28/2024
 ---
 
 # Quickstart: Get Access to Azure Operator 5G Core Preview
@@ -14,10 +14,10 @@ Access is currently limited. For now, we're working with customers that have an
 
 ## Apply for access to Azure Operator 5G Core Preview
 
-[Apply here](https://aka.ms/AO5GC-Activation-Request) for initial access.
+[Apply here](https://aka.ms/AO5GC-Activation-Request) for initial access. Contact your account lead for updates on access status.
 
 ## Related content
 
 [What is Azure Operator 5G Core?](overview-product.md)
-[Deployment order for clusters, network functions, and observability](concept-deployment-order.md)
-[Deploy Azure Operator 5G Core](quickstart-deploy-5g-core.md)
+[Deploy Azure Operator 5G Core](quickstart-deploy-5g-core.md)
+[Deployment order for clusters, network functions, and observability](concept-deployment-order.md)