azure-operator-service-manager

To onboard CNFs and VNFs with Azure Operator Service Manager, you need to configure network function artifacts and map them to Azure resources using the AOSM CLI. This process involves defining Helm charts for containerized functions and setting up artifact stores for virtualized functions.

Configuring AOSM config groups requires defining schema-driven configurations that separate network function parameters from infrastructure settings. This approach allows operators to manage deployment variables dynamically across different environments using the AOSM CLI without modifying the underlying core artifacts.

Yes, Azure Operator Service Manager supports integrating with ACR-backed artifacts and Private Link configurations. This enables secure network function deployments by allowing the AOSM CLI to pull container images privately and manage artifacts through restricted network endpoints without public exposure.

Using the AOSM CLI across deployments involves executing commands to publish network function definitions and configure site resources. The CLI acts as the primary interface to push ACR-backed artifacts, manage config groups, and deploy both CNFs and VNFs consistently across Azure environments.

You need network access to verify AOSM configurations because the onboarding process requires fetching live documentation and validating artifact store connections. Network connectivity ensures that the AOSM CLI can successfully authenticate, access ACR-backed stores, and register CNF and VNF resources with Azure.