initial feedback on the new ISV License management in Partner Center and AppSource

[malkhawaja]

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

[Captjoemcd · Accepted solution]

You'll need to publish through AppSource, register the plans/licenses, and enable LMS in the target environment before the Power Platform ISV LMS enforcement will be applied

[Helpful]

Hey @malkhawaja,

Checkout our experience here: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Adding-licensing-information-to-an-existi... 

[malkhawaja · Accepted solution]

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:

1. I noticed that the global admin of the tenant can open the app without the need of any assigned license. (is this normal and intended?)
2. I created one extra user (user A), and before assigning the license I tried to open the app using a direct link and sign in as user A, and got the “Invalid License Error”… This is great and working as expected!
3. I assigned a license to user A, then tried again to open the app, but still get the same invalid license error! I removed the license, then re-assigned it again and waited for some time but no resolution. I think there is a bug here!!
4. I created another user (user B), and assigned it the license before opening the app, then, went on and opened the app with user B credentials, and the app opens and works as expected.
5. I created (user C), assigned him a license, opened the app, and the app opens normally, but then I unassigned him the license, he kept access to the app!
6. We have some extra solutions (which are not included in the AppSource package), which are an extension to the original app  (to be sold separately), I installed them, then created (user D) and tried to open the app without assigning a license, and the license error came out (i.e.: the license enforcement is still effective despite a higher layer installation, which is good in our point of view).
7. I tried to assign the license to User D but the invalid license error still exists for this user. (same as user A).
8. Installation of an updated Managed solution of the app (which DOES NOT HAVE THE LICENSE METADATA), then it broke all the license Management of the app (well, here is a note to self, DO NOT SEND ANY UPDATE OF THE APP BEFORE MAKING SURE THAT THE LICENSE METADATA IS INCLUDED!!)

so it seems the assign/unassign licenses at the customer tenant end are still buggy!

has anyone experienced such thing?

Thanks,

Mohammad

[Captjoemcd · Accepted solution]

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 

[malkhawaja]

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?

[Captjoemcd]

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)

[Helpful]

@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:

[Helpful]

@Captjoemcd, we ran into some interesting things in our first license-enabled deployment from AppSource and I wondered if you could comment:

• In customer environment, only Global Admin can "Install this product" from within M365 Admin Center
  • We expected licensed apps to be available from within the Power Platform Admin Center - why aren't they?
  • We expected a user with Power Platform Admin security role to be able to install the app - why aren't they?
• Flows do not activate
  • We expected a unlicensed admin user to perform the installation (and activation) of all solution components, including Flows, so that the platform admin is established as the owner. This avoids the problem of actual end-users eventually leaving the company and causing issues.
  • When we tried to manually activate the flow with Power Platform Admin or even Global Admin security roles we get an error message: Failed to activate component(s). Flow client error returned with status code "Forbidden" and details "{"error":{"code":"MissingAdequateQuotaPolicy","message":"The user '15bb80f5-ae6f-4761-86ad-97e2a8c70c4f' does not have a service plan adequate for the non-Standard connection. https://go.microsoft.com/fwlink/?linkid=2123710"}}".

Your input would be greatly appreciated.

[malkhawaja]

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