Adobe Creative Cloud & SaaS Manager

[RWG2022]

Hello,

Today I have integrated SaaS Manager with Adobe CC. I have a couple of questions please. When editing the license details of the managed SaaS app, I see two effective date fields and two expiration date fields. What is the difference between these please? My next question is around the provisioned field. It has defaulted to unlimited for all licenses, but my understanding is that this should auto populate based on the number of users assigned to a license.

Any help and guidance would be appreciated.

Thanks

[JohnSorensenDK]

@RWG2022 

The two effective dates (one for the license and one for the purchase) will soon (as it's still being further developed) facilitate the use case of potentially having multiple purchases over time for a single license, and potentially with different costs.

For Adobe Creative Cloud the Adobe APIs don't provide a trustworthy  total purchased count for each license, and therefore design wise it was decided to set it to 'Unlimited' for all licenses.

Thanks,

[RWG2022]

Thanks for the explanation makes sense. Regarding the total purchased count, I can see exactly how many licenses we have in the AAC, so I'm surprised it is set to report unlimited by design. I can overwrite these figures in SaaS Manager, so I guess that's the only way of having the actual number of licenses showing as opposed to unlimited. Would I use the Provisioned field to specify the number of licenses we have, or the Purchased field, or both?

Thanks

[JohnSorensenDK · Accepted solution]

@RWG2022 

The Adobe APIs don't return the total purchased count for each license.  (The Adobe APIs can return a licenseQuota field, which is applicable for each Product profile created under each Subscription. However, as licenseQuota is editable and can be updated to any value, the SaaS mgt. integration is not using that field to display the # of items allowed/Provisioned count, as it can lead to displaying incorrect values.)

It's the Provisioned field that you want to overwrite. (The Purchased field is relevant for the cost tracking, but as explained above can be left blank unless you want to track multiple purchases over time for the same license (when this feature gets fully implemented...))

Thanks,

[RWG2022]

Makes sense thanks very much.

[samccroskey]

I just got my Adobe SaaS uploaded from the Adobe Portal. The issue that I am running into and having a hard time in getting Flexera to do is to populate correctly the user count and transaction count for the Adobe Sign solution that we have. The API can see ACROBAT_SIGN_SOLUTIONS_FOR_ENTERPRISE_TRANSACTIONS but it wants to count it as a per user so my user count is incorrect, and it does not correctly show how many transactions have been done. I found under the Create Customized Licenses section, a license that I could create on my own called Adobe Sign-Enterprise TRNS. However, if I do use Adobe Sign-Enterprise TRNS and not ACROBAT_SIGN_SOLUTIONS_FOR_ENTERPRISE_TRANSACTIONS, if fixes my user count. But the Adobe portal still cannot report the number of transactions that we have done.

[samccroskey]

I also have one other question or issue. The Adobe Portal does not tell Flexera that the users are active. However, I thought I saw somewhere a possible solution to this issue, but I cannot find that post. I was wondering if there was an automated way to take a list of the users that the Adobe portal pushes to Flexera and match that with active pc users, to give you a list of active users that the Adobe SaaS could then display as active.

Thanks

[JohnSorensenDK]

@samccroskey 

You may have to leave out the ACROBAT_SIGN_SOLUTIONS_FOR_ENTERPRISE_TRANSACTIONS from the licenses being imported to avoid it misrepresenting the number of users (instead of transactions) in SaaS mgt. You can potentially leverage the Flexera SaaS Management Data Ingestion Utility to represent the transactions as a consumption based license in SaaS mgt.

The Adobe portal API doesn't expose activity data. The integration between SaaS mgt. and Flexera One ITAM reconciles the users imported from the Adobe portal API with their local use of the Adobe applications on their devices.

Thanks,