Using Software Model Subscription Condition with SSO Applications

[ChadO]

We're using SAM Pro with SaaS License Management integrated with Azure AD for license management, spend, etc.  We have quite a few SSO Applications that encompass multiple AD groups for granting different license types (e.g. reader, writer, admin, etc.).  Each SSO Application is associated with a Software Model and then we have one or more Software Entitlements associated with each Software Model for tracking spend, over and under utilization, etc.  Back when we were on Rome, there was no way to associate different license costs with different license types for subscriptions associated with SSO applications.  However, San Diego introduced the "Subscription Condition" field on the Software Model, which we can use to limit what the Software Model associates with.  In the "Subscription Condition" field, we can build conditions against the SSO Application role/group.  I've created a few Software Models and set the Subscription Conditions to apply to different AD groups for one of our SSO Applications but I'm not sure how we associate those Software Models with the SSO Application.  Does the association happen automatically somehow?  Is there something else I need to do to associate the multiple Software Models with the SSO Application?  Thanks in advance.

[Srinivas Ramanu]

Hi Chad,

The association of the SSO application with the existing software model should happen automatically. Please ensure you had the DMAP on the software model and entitlements added to the same. 

[ChadO]

Hi Srinivas,

Thanks for the reply.  I do have a couple of follow-up questions.

First, if we do have multiple Software Models that we're wanting to associate with the SSO Applications (via the Subscription Conditions), which of the Software Models do we directly reference from the SSO Application since it's a required field?

Second, of the various SSO Applications some have a direct integration that can be set up, such as Dropbox, GitHub, G Suite, etc., while some only pull subscription and usage data from Azure AD, in our case, directly.  The Software Model(s) created for the direct integrations do have a DMAP and so I could follow your instruction for those.  However, for the SSO Applications that pull directly from Azure AD, there is no DMAP that gets created or associated and so I couldn't set that on any additional software models that I create.  Would that still work as you describe?

Thanks,

Chad

[James Rostron]

Hi did you ever figure this out?

I'm trying to do something similar. We have two Adobe integrations for two different (Adobe cloud) business units. I've set the software condition on the models (both have dmaps) but an automatic software model is created and I can't get my custom models to associate to the software subscription records.

[ChadO]

Hi James,

We did.  For the SSO-based subscriptions that we wanted to associate with specific software models, we set the "Subscription condition" on the software model(s).  We would create multiple software models depending on the number of different subscription types we wanted to track.  Then we would associate software entitlements with the correct financials to those software models to more accurately monitor costs and savings.

For example, with Docusign we would create a software model for Docusign users and set the "Subscription condition" to something like:

Then if we had different subscription types that we wanted to track (e.g. Docusign Admins) we would create another software model and set the "Subscription condition" to:

Hope that helps.

Chad