What is best practice if there is are 2 separate licenses for the same SaaS product

[Stu2025]

This is specifically when setting up a SaaS ootb connection - each admin user used to setup the integration app will be unique to a each SaaS account- what happens then when 2 different apps feed the data into SAM - will it recognise the same product and total the usage or handle 2 separate accounts for the same SaaS product 

[dreinhardt]

Hi @Stu2025,

by design it recognize the same product and total the usage from all SaaS integration. You can add the "Subscription profile" column to your Software model subscription tab to identify the source of each of the records.

If you can share a few more details about the use case this would be helpful!

Best, Dennis

[Stu2025]

Essentially there are 2 different Cloud licenses for the same SaaS publisher and 1 separate admin user for each account to setup the integration - just wondering from a technical standpoint should you setup 2 different connections and handle them separately - will SAM recognise both and total them or provide separate details - actually we would prefer separate handling because each application owner manages their own license

[dreinhardt]

Hi @Stu2025,

as long as all user subscription data is available in the one tenant, a single SaaS integration is sufficient – regardless of how many admin user managing licenses in the tenant portal.

The desired management is now also carried out in SAM Pro. You should maintain the corresponding “Ownership” attributes for the licenses entitlements. The admin users must also assign the respective user allocations to their managed entitlements in SAM Pro. You could think about a restriction of actions based on the ownership.

Best, Dennis