Mismatch between Content Library and M365 Integration DMAPs

[Elina Psch]

Our M365 integration is pulling subscription records and mapping them to a model associated with  ~DMAP150 . However, the Content Library's Software Model Definition and Entitlement Definition for this product both point to ~DMAP990, so entitlements are also created under the DMAP990 model via PPN, which the Content Library resolves automatically.

As a result, subscriptions and entitlements sit under two different models.

We are planning to update the Discovery Map on the identifier record in samp_sw_subscription_product_definition from DMAP150 to DMAP990. Before we do, we have a few questions:

1. Is it safe to update this identifier record, or what is the best practice?
2. Will existing subscription records update automatically to the correct model?
3. Has anyone dealt with a similar DMAP mismatch and what was your approach?

Any input would be really appreciated. Thank you!

[dreinhardt]

Hi @Elina Psch,

1. the mentioned table is managed by the content service and may be updated weekly and overwriting every change. Still not sure if this table can be adjusted.

2. Each imported subscription is linked with an identifier from the portal and this record is mapped to the Identifier/DMAP record from the table mentioned above in 1.

3. In case of any issues with the content data, please raise a support case and provide all details to the content team for review.

If you don’t want to change the entitlement software model DMAP to match the subscriptions, you could add the subscriptions model as suite child to get covered by the onboarded entitlements.

best, Dennis