CSDM Best Practice for Microsoft Dynamics365
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Does anyone have a diagram or explanation on how best to model the Dynamics 365 SaaS platform in CSDM, specifically in terms of the various developed components/application?
I was wondering if an Application Service could be employed (one per environment), and instead of creating Application Services for all the developed applications, could a Technical Service / Technical Service Offering but used and consumed by the application service.
Alternatively, does the CSDM already have a specific way for recording the Dynamics365 platform and apps?
My concern is very soon we will have a 100s of applications running on Dynamics 365 and it would be hard to manage all these at the application service level.....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
If you pop over to Now Create there is a "CSDM Data Model Examples" slide deck that has O365/Dynamics and others.
They have MS Dynamics Prod as a Service Instance
Business Service Customer Relationship Service
Business Service Offerings Dynamics CRM and Dynamics Reports
https://mynow.servicenow.com/now/best-practices/assets/csdm-data-model-examples
Should give you a good start.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I do not have any specific model I could share to help you. But let me comment on what comes to my mind for your challenge. To model it, you need to ask also questions like "Are those apps supported by the same support group?", "Do they have the same owner, and where will I track it?", "Do they have different SLAs, for example?". "How are these apps used within ITSM processes?" Based on questions like these, you might get a feeling for how granular you need to know.
I assume it might be similar to ServiceNow applications, where somebody models it in a way that "ITSM Prod" is one Service Instance (Application Service), but another models it in a way that "Incident Management Prod", "Change Management Prod", etc., are separate service instances. Next to it, you always have the "ServiceNow Platform Prod" service instance as the dependency for all the apps running on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Yes
- service owner and support group are same.
- infra (SaaS) is the same as well
- SLA, RTO, RPO will be defined at the Service Commitment level which I understand links to offerings not services
This is why i'd like to have a simplified App Service level, e.g.
- D365 CRM (Prod)
- D365 CRM (Dev)
- etc
But my proposal is to use TS/TSO to record the multitude of platform application services underneath.
Would that be fundamentally incorrect?
