Announcements
Portals apps seem to be designed for AppSource.
What about Azure Marketplace? If you build a prototype app in Portals and then want to publish the app to Azure Marketplace, what are the best practices for doing so?
I found this article but it was published several months ago so may be outdated
https://swimburger.net/blog/dynamics/how-to-deploy-power-apps-portals-using-azure-pipelines
If I can create an AppSource package for the Portals app, I should be able to publish the Portals app to AppSource.
To publish an app to AppSource, it seems I need to create a Dynamics 365 package.
Step 3: Create an AppSource package for your app (Microsoft Dataverse) - Power Apps | Microsoft Docs
A package lets you bundle and deploy multiple files related to your app at once.
Create a Dynamics 365 package to include the solution and configuration data files that you created in Step 2: Create a managed solution for your app. A package can also contain custom code that can run before, while, or after the package is deployed to the Microsoft Dataverse instance. For more information about creating a package file, see Create packages for the Package Deployer.
After you have created a package, your package will consist of the following things:
<PackageName> folder: This folder contains all solutions, configuration data, flat files, and the contents for your package. For example: PkgFolder.
<PackageName>.dll: The assembly contains the custom code for your package. For example: SamplePackage.dll.
Next, create a [Content_Types].xml file that provides MIME type information of the file type extensions that are included in your package. This is separate from the one that will be included again in the AppSource package. Here is the sample contents of a Content_Types].xml file with file types listed:
Share
Report
All responses (
Answers (
<?xml version="1.0" encoding="utf-8"?>
<Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types">
<Default Extension="xml" ContentType="application/octet-stream" />
<Default Extension="xaml" ContentType="application/octet-stream" />
<Default Extension="dll" ContentType="application/octet-stream" />
<Default Extension="zip" ContentType="application/octet-stream" />
<Default Extension="jpg" ContentType="application/octet-stream" />
<Default Extension="gif" ContentType="application/octet-stream" />
<Default Extension="png" ContentType="application/octet-stream" />
<Default Extension="htm" ContentType="application/octet-stream" />
<Default Extension="html" ContentType="application/octet-stream" />
<Default Extension="db" ContentType="application/octet-stream" />
<Default Extension="css" ContentType="application/octet-stream" />
<Default Extension="json" ContentType="application/octet-stream" />
<Default Extension="msapp" ContentType="application/octet-stream" />
</Types>
Compress (zip) the following files into a file called package.zip:
package folder (PkgFolder)
package dll (SamplePackage.dll)
[Content_Types].xml
To compress these files, browse to the folder where these files are present, select them all, right-click and select Send to > Compressed (zipped) folder.
Rename the .zip file to package.zip.
Microsoft Power Platform ISV Studio - Power Apps | Microsoft Docs
ISV Studio supports applications built on the Microsoft Dataverse that are published to and deployed through AppSource.
PowerApps ISV Studio is now available for public preview | Microsoft Power Apps
Per the Portals website,
Reducing call volume by 90 percent with Power Apps portals during the COVID-19 pandemic enabled the City of Kobe to help millions of citizens at scale.
When you say "doesn't work with" what do you mean?
What is the purpose of being an ISV if you can't use portal apps?
What is the purpose of providing a custom domain for portal apps if you can't sell via either marketplace?
That doesn't add up.
A few things here:
Please also take a look at these quick tips for when to use Power Apps Portals
Power Apps Portals Tip #120 - When To Use Power Apps Portals - Engineered Code - YouTube
Power Apps Portals Tip #119 When Not To Use Power Apps Portals Engineered Code - YouTube
I am looking at the total cost of ownership of Portals with AppSource versus Azure Marketplace.
Portals charges $20 per month for unlimited apps, which is good, but the starting price for authentication of $200 per month quickly makes it a less attractive option.
Are you saying Portals apps are not meant for either AppSource or Azure Marketplace? Or just not for Azure Marketplace?
Thanks
"
Using Azure Marketplace would require $0 in monthly authentication costs. Portals starts at $200 per month. I would prefer to go with the $0 per month option.
"
Well.. they are different things.. the Portals has a cost on its own to maintain the product and infrastructure. The price is calculated by login or page views. The cost here is not with regards the Portals authentication/login, the cost is to use the Portals itself.
Using Azure Marketplace would require $0 in monthly authentication costs. Portals starts at $200 per month. I would prefer to go with the $0 per month option.
https://docs.microsoft.com/en-us/azure/marketplace/plan-saas-offer
The Get it now (Free), Free trial, and Sell through Microsoft listing options have the following technical requirements:
These additional technical requirements apply to the Sell through Microsoft(transactable) listing option only:
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-webhook
When creating a transactable SaaS offer in Partner Center, the partner provides the Connection webhook URL to be used as an HTTP endpoint. This webhook is called by Microsoft by using the POST HTTP call
The publisher must implement a webhook in the SaaS service to keep the SaaS subscription status consistent with the Microsoft side. The SaaS service is required to call the Get Operation API to validate and authorize the webhook call and payload data before taking action based on the webhook notification. The publisher should return HTTP 200 to Microsoft as soon as the webhook call is processed. This value acknowledges that the webhook call has been received successfully by the publisher.
"Azure customers can discover and deploy Azure Marketplace solutions through the Create a resource option in the Azure portal. This option opens Azure Marketplace within the Azure portal, where they can search for solutions by name or by category."
https://docs.microsoft.com/en-us/azure/marketplace/marketplace-criteria-content-validation
Technical information: Configuration
Hi, do you need to use web hooks for authentication or would it be something more specific?
Portals provides with plenty of authentication options: Overview of authentication in Power Apps portals - Power Apps | Microsoft Docs
It is recommended to use Azure AD B2C as identity provider.
Do you have an estimate of how many users would be logging in per month? There are tiers so it gets a bit cheaper once you have a large number of logins
#1
Lucas001
60
Super User 2025 Season 1
#2
Fubar
55
Super User 2025 Season 1
#3
surya narayanan
35
