Purchase process - Managed Application

7 min

public plan the customer finds your plan on microsoft marketplace and clicks get it now , which opens the deployment blade in the azure portal on the basics tab the customer selects the azure subscription, a resource group for the managed application resource, a region supported by the offer, an application name, and a name for the managed resource group the customer moves to the tab defined by your \ createuidefinition json \ — in this example (storage account type, container name for this example) on review + create the customer reviews pricing and legal terms, accepting the microsoft standard contract (or their enterprise agreement terms) and your terms of use they must also tick the co admin access permission box, which is what grants you administrative access to the deployed resources then they click create note the create button does not appear until the customer ticks the terms checkbox this is a common point of confusion — flag it in advance azure deploys the resources from your template into a new managed resource group in the customer's subscription when deployment completes, two objects exist in the customer's subscription the managed application resource — the control plane the customer owns this is where they can delete the application, and it links to the managed resource group the managed resource group — containing the resources your template deployed in this example, one storage account order activation unlike saas, no action is required from you the order activates automatically once deployment completes, azure starts billing for the plan from that moment, and a notification is sent to the wetransact portal where a new order appears tip customers who lose the deployment link can find their application again at managed applications in the azure portal they do not need to remember which resource group they put it in private offer csms work closely with managed application customers throughout this process, from creating the private offer through to supporting the customer during purchase a private offer can be based on an existing public plan or on a new plan created for it purchasing a private offer has two layers accepting the offer, then purchasing it accepting in the azure portal the customer goes to marketplace → private offer management , finds the offer, clicks view + accept , reviews the terms and price, and selects accept private offer the status changes to " accepted, pending purchase " deployment starts at acceptance in the managed application offer type, deployment begins when the customer accepts the offer, not at purchase waiting time the purchase button can take 30 to 40 minutes to become clickable after acceptance once clicked, completing the purchase can take up to 60 minutes set this expectation with the customer up front facts to keep in mind deployment starts at acceptance for the managed application offer type, deployment begins when the customer accepts the offer, not at purchase if you cancel the deployment after the customer accepts, the purchase button will not appear the customer can cancel at any time by deleting the managed application resource if they do this before completing the purchase, the purchase button disappears and the private offer has to be re initiated once the purchase completes, no publisher action is needed the order activates automatically and the application is deployed in the customer's subscription access control and permissions by default you have full access to the managed resource group and the customer has read only visibility, enforced through deny assignments microsoft supports four permission scenarios \ scenario \ \ your access \ \ customer access \ \ deny assignment \ publisher managed (default) management access restricted applied publisher and customer full access full access removed locked mode no access restricted applied customer managed no access full access not applied publisher set this while configuring the offer 💬 for more, contact us at \\