cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Helpful
Responsive Resident
Responsive Resident

Adding licensing information to an existing solution

Hi All, I'm thrilled that Microsoft is adding something to support licensing ISV apps distributed through AppSource. That being said, in its current state it's pretty confusing and the documentation does not provide much clarity on the what or how of this feature.

 

As an ISV, here's my understanding of this feature in its current form:

  • It DOES:
    • Restrict AppSource deployment of model-driven apps to only those tenants that are registered by the ISV in Partner Center
    • Allow customers to assign licenses to individual users from within their own M365 Admin Center
    • Once deployed, restrict access of ISV model-driven apps to users that are assigned a license
  • It DOES NOT:
    • Allow ISVs to add licensing to existing AppSource offers
    • Allow ISVs to add licensing to packages built with current Power Apps Build Tools (v1.0.23)
    • Allow import of unmanaged solutions that include service plans
    • Allow customers to purchase licenses at the time of clicking "Get it Now"

We have an existing offer in AppSource. It has a model-driven app and no code components. We have full ALM automation built out in Azure DevOps and everything runs pretty smoothly. We're small so making changes in an unmanaged environment and then committing to repo works for us. All deployments are automated. The only time we mess with Visual Studio is to package for AppSource. We never open command line tools.

 

Here's a little recap of my experience attempting to implement and evaluate this:

  • Copy an existing AppSource offer - this is mostly cut/paste exercise, however, it will mean the back/forth of approvals with AppSource... content, tech, and co-sell material. Also updating any marketing links to the new offer if published.
    • Add a plan to the new offer. Note the "Plan ID", you'll need it later.
  • Go to the solution in my unmanaged environment and add a "Service Plan" component - just kidding we read the steps before that: Add licensing information to your solution

Here's where things slowed down. The first step says "Clone existing solution". In our world, that means go into the unmanaged Power Apps maker environment, select the solution and click "Clone a patch" or "Clone solution". This is not what they mean and it's confusing.

  • The documentation is referring to command line tools that we don't have (Power Apps CLI) - get those.
  • Using the clone command of the Power Apps CLI does not appear to make much sense for us since we already store our unpacked, unmanaged solution files in ADO. So I download those an unzip them locally.
  • Create licensing files - two CSV files. Do not get confused by file names in the screenshots - they actually need to be ".csv" files.
  • Add the licensing information to the solution using the specified Power Apps CLI command.
    • Take a look at what that command did. Comparing the modified solution files with an old set for reference, we can see that it:
      • added a folder called "ServicePlans" (right between Roles and WebResources).
      • added two Xml files (documented below) to the new folder, populated with the values from your .CSV files.
      • added two empty nodes "<serviceplans /><serviceplanappmodulesset />" to the Customizations.xml file in the "Other" folder.
    • Had I known they needed a folder with a specific name and two files with specific names I could have done that without the extra steps.
  • Build the solution. Here's where we get stuck. The documentation for this is particularly confusing: Create a managed solution for your app
    • We have DevOps automation to build solutions so we branch our unmanaged solution, apply the changes (noted above) in the repo and use our existing automation to build a managed package.
    • Open the resulting ZIP file and the empty nodes are now represented in the Customizations.xml file, however, the two files are nowhere to be found in either the Managed or Unmanaged solution package.
      • Is there some other tool we're supposed to use to ensure those files are picked up?
    • With input from @rajyraman, we discovered that the Package Solution task of the current version of the Power Apps Build Tools is not using the latest version of SolutionPackager and, therefore, does not generate the service plan content in Customzations.xml.
    • Use SolutionPackager on command line as workaround to package both Unmanaged and Managed solutions. Confirmed the service plan XML is incorporated into Customizations.xml.
  • Tested import of unmanaged solution that has service plan information to a clean environment. This fails with the following message: "Solution "ISV Solution" failed to import: ServicePlanAppModules data can only be changed by managed solution import".
  • Package for new AppSource offer and evaluate - Update below. WE'RE PAUSING HERE FOR NOW. Hoping we see updates that make it more manageable with our existing ALM setup.

 

Looking forward to this being more supportable. As of right now, it doesn't seem to be compatible with the ALM tools in Azure DevOps that we rely on.

 

ServicePlans.xml content:

 

 

 

<?xml version="1.0" encoding="utf-8"?>
<serviceplans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <serviceplan name="[SERVICE_PLAN_ID]">
    <accessmode>4</accessmode>
    <iscustomizable>0</iscustomizable>
    <displayname>[SERVICE_PLAN_NAME]</displayname>
    <moreinfourl>[YOUR_ISV_PLAN_INFO_LINK]</moreinfourl>
  </serviceplan>
</serviceplans>

 

 

 

ServicePlanAppModules.xml content:

 

 

 

<?xml version="1.0" encoding="utf-8"?>
<serviceplanappmodulesset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <serviceplanappmodules>
    <iscustomizable>0</iscustomizable>
    <appmoduleid>
      <uniquename>[MODEL_APP_COMPONENT_NAME]</uniquename>
    </appmoduleid>
    <serviceplanid>
      <name>[SERVICE_PLAN_ID]</name>
    </serviceplanid>
  </serviceplanappmodules>
</serviceplanappmodulesset>

 

 

 

 

Documentation references:

 

13 REPLIES 13
rajyraman
Continued Contributor
Continued Contributor

@Helpful- That XML is actually in the customizations.xml after you package the solution folder using the Solution Packager tool.

rajyraman_1-1620277564909.png

 

rajyraman_0-1620277530130.png

 

Helpful
Responsive Resident
Responsive Resident

Thanks, @rajyraman. Our solution is built using Power Platform Build Tools in Azure DevOps and the XML shown above does not appear in the Customizations file.

I thought the build tools used Solution Packager behind the scenes so would assume the same behavior as if we built with SolutionPackager, but maybe that’s a bad assumption.

I’ll test this tomorrow.

rajyraman
Continued Contributor
Continued Contributor

@Helpful- Check the version of Solution Packager being used from the AzDO logs. The one I use on the local machine is 9.1.1.2.

Helpful
Responsive Resident
Responsive Resident

Thanks, @rajyraman. Sure enough, it looks like Power Apps Build Tools is using Version 9.1.0.67.

We packaged with command line and are now seeing the service plan xml nodes populated in Customizations.xml.

I guess we'll wait for the tooling to catch-up. I recall the team that was working on those was getting a fair amount of investment a year ago, but perhaps priorities have shifted.

malkhawaja
Advocate III
Advocate III

Hi @Helpful,
Thanks for the elaborate feedback... my experience was almost exactly the same, as I stuck also to pack the managed solution, then eventually found it in the SolutionPackager Command Line.

now I submitted my package for publish in AppSource, and waiting for certification.

Captjoemcd
Advocate I
Advocate I

@Helpful - As an ISV, we have a very similar dev process to you, using Azure DevOps with automated deployments to customer-specific dev environments and production environments.  Azure DevOps build tools do not currently support including the LMS as you point out, although we've communicated the need to the team responsible for the build tools. 

 

The PAC CLI does nothing other than generate the xml from the csv mapping files, and then adds it to the end of your managed solution.  The folders with the csv files don't need to be in the final solution.  Once you have that xml generated, you can copy it into the managed solution directly.  When we first got started we didn't use the PAC CLI at all and just created the service plans and mapping directly in xml, and then added to our managed solution. 

 

Editing service plan information is currently not supported with an unmanaged solution for the obvious security reasons (though this may change at some point) - this means that you have to add it every time you export a managed solution from your dev environment.  We added a powershell step in our devops pipeline to add the xml to the managed solution when we pull from core dev prior to deploying the managed solutions to customer-specific dev and production environments. 

JeffCarma
Advocate I
Advocate I

Thanks @Captjoemcd ,

 

Here's a snip of powershell to get others started. The two files it uses are the customizations.xml file that is in the "Other" folder when you unpack the solution. (I unpacked it into a folder called "tempforpacking" of course.) The license.xml file is just the license specific section of the xml that the pac cli generates. I haven't added checking to ensure the nodes were added yet, but that should be straight forward.

 

Write-Host "starting script"
Write-Host "getting license.xml and custimizations.xml"
[xml] $orig = Get-Content '.\tempforpacking\Other\Customizations.xml'
[xml] $lic = Get-Content '.\license.xml'

Write-Host "adding license.xml to custimizations.xml"
$orig.ImportExportXml.AppendChild($orig.ImportNode(($lic.ImportExportXml.serviceplans),$true))
$orig.ImportExportXml.AppendChild($orig.ImportNode(($lic.ImportExportXml.serviceplanappmodulesset),$true))

Write-Host "saving modified customizations.xml file"
$orig.Save('.\tempforpacking\Other\Customizations.xml');
kartikka
Employee
Employee

Hi Folks,
             I am the PM that worked adding the licensing capability.  I would really like to understand the paradigm a little bit better on how you want licensing to be part of the CI/CD process. I did have an exchange with Jeff in a seperate thread. But I would like to understand the broader sentiment and the CI/CD workflow in question. 

When you respond, please @ me directly so that I can get notified.

Helpful
Responsive Resident
Responsive Resident

Hi @kartikka, thanks for the opportunity to provide feedback. I will speak on behalf of our setup and am curious to hear the perspective of others.

 

Please see attached image. To make this work:

  1. License Plans can be added as components to an unmanaged solution.
  2. SolutionPackager needs a switch that optionally applies licensing for managed solutions.
  3. Power Platform Build Tools' Package Task needs to be updated to use the new SolutionPackager with "Include Licensing" option for managed solutions (default is false).

ci_cd.png

We have the approach above implemented today, but some of Step 4's tasks could be cleaned-up to use Build Tools instead of PowerShell.

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (2,080)