Hi,
As I am really excited for this new functionality, I went on to try it and implement it into my solution, but before continuing and publishing in AppSource, after I added the License metadata into my solution I went and installed it directly into a trial environment in a trial tenant, which still did not get the licenses, so when finished installation I tried to open the app, and it opened normally, without showing any "missing license error"!
so is this a known issue? is it expected?
I will go through the rest of the process and publish to AppSource, and test installing from AppSource and will give you my feedback then.
thanks,
Mohammad
Hi,
Some wild idea (or may be not that wild!!) came to my mind, once the customer installs my app from AppSource, so basically now they have all the solutions and components behind my app, well what if they go on and create a replica of my app from my app's components and start using it?!! I think, the License enforcement won't work on the replica, right? what should we do in that case?
@Captjoemcd I am in the O365 admin portal, using a native Global Admin account... I am not using delegated admin!
Which admin portal are you using in the customer tenant? You should be in the O365 admin portal, using a native Global Admin account. Currently, Delegated Admin account will not see them. The licenses should show up immediately (no caching delay when you add the licenses to the tenant).
Hi @Helpful @Captjoemcd,
I am running into something wrong... I have a trial tenant (other than my Partner tenant) for which I am trying to create a test deal. so the deal is registered and the ISV link ok in the customer trial tenant but when I add licenses to the customer tenant in Partner Center, they do not appear at the customer's Admin portal... is it something new that broke something?
Regards,
Mohammad
@Captjoemcd, we ran into some interesting things in our first license-enabled deployment from AppSource and I wondered if you could comment:
Your input would be greatly appreciated.
@malkhawaja, if you're referring to a new version published to AppSource, you can inform customers that there is an update available and the update appears in the Power Platform Admin area for that environment like this:
Don’t quite follow- your customer will need to approve license management for their tenant and you’ll include the LMS in your next solution update (and all after that)
That's good to know... thanks for the quick response...
now in case I have an update to my package, how is the customer notified for the new update?
This is all expected behavior.
System admins/global admins are not subjected to license management.
There’s up to 8 hour caching behavior between M365 admin portal and dynamics for existing users for license assignment. New users assigned a license on creation will have the license permissions immediately assigned since it’s the first time dynamics is pulling the user info from M365
Hi,
this is to complete the feedback on the whole ISV license management:
after publishing to AppSource and creating the test Deal registration, I created a test tenant, and here's my experience:
so it seems the assign/unassign licenses at the customer tenant end are still buggy!
has anyone experienced such thing?
Thanks,
Mohammad
WarrenBelz
109
Most Valuable Professional
Michael E. Gernaey
82
Super User 2025 Season 1
mmbr1606
71
Super User 2025 Season 1