Forum Discussion
Example for SaaS fulfillment Subscription APIs v2 in Microsoft commercial marketplace
Dear Ladies and Gentlemen,
I search for an Example for SaaS fulfillment Subscription APIs v2 in Microsoft commercial marketplace.
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#resolve-a-purchased-subscription
In the meantime I have learned that it is possible to offer SharePoint apps for fees through Microsoft store in the way that the SharePoint app is going in Microsoft Partner Center through the "Marketplace offers / Office store", where it is possible to make the offer only for free.
Later on it is possible to map this offer through a "Marketplace offers / Commercial marketplace" with a new offer of type "Software as a Service". On the "Offer setup" page on the bottom after selecting "Yes, I have published Teams apps, Office add-ins, or SharePoint Framework solutions that I would like to link to this SaaS offer" is possible to add a link to the SharePoint app.
However there is a time in which the SharePoint app is free to download. I think here could be made an improvement, to not allow this in case it is not wanted.
I have already also made a web hook in Azure and also a SQL Database in Azure for the storage of information about the purchases.
Now I search for some practical example of the communication between the page, where I want to offer this product on my own website and Microsoft regarding of the fulfillment of the requirements written here:
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#resolve-a-purchased-subscription
I think there shall be some practical example presented by Microsoft, which fulfills these requirements.
Thank you.
With best regards
Ladislav Stupak
- According the site “Register a SaaS application”
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-registration
According the part “Register an Azure AD-secured app”
Each SaaS offer must have own application for registration.
In the part “Get the token with an HTTP POST” in the site, where you acquire access token through the POST request to the site
https://login.microsoftonline.com/*{tenantId}*/oauth2/token
ensure that the body is written in exact this format:
grant_type=client_credentials&
client_id=CLIENT_ID_OF_YOUR_AZURE_REGISTRATION_APPLICATION&
client_secret=CLIENT_SECRET_OF_YOUR_AZURE_REGISTRATION_APPLICATION&
resource=20e940b3-4c77-4b0b-9a53-9e16a1b010a7
This registration application for the concrete SaaS offer must be encapsulated in Azure Login functionality.
Here is a very good example how to create such app in React:
https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-v2-react
Around this site are also examples which use other technologies.
1 Reply
- According the site “Register a SaaS application”
https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-registration
According the part “Register an Azure AD-secured app”
Each SaaS offer must have own application for registration.
In the part “Get the token with an HTTP POST” in the site, where you acquire access token through the POST request to the site
https://login.microsoftonline.com/*{tenantId}*/oauth2/token
ensure that the body is written in exact this format:
grant_type=client_credentials&
client_id=CLIENT_ID_OF_YOUR_AZURE_REGISTRATION_APPLICATION&
client_secret=CLIENT_SECRET_OF_YOUR_AZURE_REGISTRATION_APPLICATION&
resource=20e940b3-4c77-4b0b-9a53-9e16a1b010a7
This registration application for the concrete SaaS offer must be encapsulated in Azure Login functionality.
Here is a very good example how to create such app in React:
https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-v2-react
Around this site are also examples which use other technologies.