License deduplication (when All Apps licensed, suppress Single App and Acrobat license consumption)

Forum|Forum|3 days ago
July 15, 2026
1 reply
36 views

Question:

Can Adobe implement a license deduplication functionality directly within the admin console?

Details:

With SCIM in place, we can implement dynamic licensing based on Entra ID group membership. We use Intune to push individual Creative Cloud applications (e.g. Photoshop, InDesign) based on ServiceNow requests. The issue we are trying to fix is the fact that All Apps users have to be in the individual app groups as well to get the corresponding installation, meaning All Apps users end up double licensed with Single App and Acrobat.

The proposed fix is simple: If a user has All Apps assigned, either don’t assign or suppress the license requirement for any other Single App or Acrobat licenses assigned to the same user within the admin console. This seems like a relatively simple, high value change benefiting most customers that use All Apps in combination with other licenses.

Most customers using All Apps will run into issues with license juggling and overlaps. Rather than forcing every customer to invent their own convoluted workaround using whatever systems they have in place, it would be far easier to have a centralized fix on the Adobe end.

Thanks

A

AnkitVerma

Community Manager

Hi @Lukas,

Thank you for laying this out so clearly, and we completely understand what you're trying to achieve here. To get this checked, you can open a case with our support team through the Admin Console > Support. From there our team can review your entitlements and deployment setup directly and take it forward for you.
When you open the case, including the same context you shared here (the SCIM plus Entra ID group model, the Intune per app deployment tied to ServiceNow, and the licensing outcome you're working through) will help the team pick it up quickly.

Thanks,
^AV

L

LukasAuthor

Participant

Hi Ankit,

Hope you are well. This all started with a support case (E-002347247), the conclusion of which was to post a feature request on this forum. Our account manager Ernest Turay also wants this feature. Direct quote from our email chain:

“I think the hierarchical logic solution you proposed makes perfect sense (no pun intended). I would love to also see it be introduced because I think it would be well-received by some of my other customers. Please raise the feature request with our support team, and hopefully we see this get introduced in the future.”

The proposed fix in the support case was to split out deployment and licensing groups. However, it introduces additional complexity without fixing the underlying issue. Here is what I told support:

- The logic complexity scales with the number of groups as each Single App variation has its own group (3 groups: Install, Uninstall, License). The logic would also need to handle removals from groups to reshuffle licenses.

- It's not at all intuitive for service desk when they need to fix someone. We already used to have separate deployment/licensing groups for Microsoft Project and Microsoft Visio. The service desk would constantly update just 1 group without the other and that was a direct 1:1 relationship, which isn't the case here.

- The SAM team doesn't have admin rights, so we wouldn't be able to make back end optimizations to AD group memberships.

- The whole process ignores the entitlement you own. For example, while All Apps might seem optimal, we are capped out while we have lots of spare Single Apps. The dynamic process would create an artificial overage without utilizing existing licenses.

The best way to handle this isn’t for customers to try invent logic which will never be perfect if it can’t read entitlement off of the Adobe portal and will require completely custom implementation as customers use different systems and configs of those systems to manage requests/deployments. The by far simplest way is for Adobe to add a portal check and not count overlapping licenses for users covered by All Apps.

Thanks

A

AnkitVerma

Community Manager

Hi @Lukas

Thank you for the detailed write-up, and for looping in the context from support case E-002347247 and your account manager's note.

You've articulated the core issue well: the deployment/licensing group split adds implementation complexity without addressing the underlying gap, because customer-side logic can't read entitlement state from the Adobe portal. The cleaner solution you're proposing, having Adobe add a portal-side check so overlapping licenses aren't counted for users already covered by All Apps, is a product-level change rather than something that can be solved through group configuration.

For a change like this, the right channel is our feature request form at https://www.adobe.com/products/wishform.html. You can lay out the entitlement-aware reasoning there just as you have here.

We appreciate you taking the time to explain this so thoroughly.

Regards,
^AV

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.