How to treat Azure services (e.g. Azure Kubernetes Services) in CSDM?

[Yangles]

Hi all,

We currently have Azure as a technical service offering, and I'm wondering how services within Azure should be treated in the CSDM.

Examples of Azure services are API Management, Kubenetes Services, Event Hub.

Should each of these be treated as an application service? And then related to Azure as a shared service?

I'm working on the Health Log Analytics app, which ingests logs from these services. As part of this, they need to be associated to entries in the Application Service [cmdb_ci_service_auto] table (due to how HLA is designed). So ultimately, I need application services available for these services, so I can bind the logs to them.

Thanks all!

[TreadingH2O]

Sad to see no responses here, as I'm equally interested in what others have done.  Did you ever figure out anything?

[Jacques Clement]

IMO yes, each Azure service should have its own corresponding Application Service and then use Depends on relationship type to indicate that a Business Service Offering depends on it. You need this granularity to model that one Azure service going down might affect certain Business Services and not others.

Also I would not say that your Technical Service Offering is Azure; you might have a Technical Service being Azure, and then different offerings for the different services, as most likely you're gonna have different support teams for different Azure services.