Benefits, Limitation and troubleshooting of Managed Applications

7 min

benefits of managed applications compliance solutions align with regulatory and security requirements for sensitive data, because nothing leaves the customer's environment publisher control simplified updates, patches and maintenance inside customer subscriptions unique azure capability no other major cloud provider offers an equivalent to managed applications scalable revenue a strong fit for enterprise deals that require deployment flexibility, with marketplace billing keeping procurement simple limitations and things to watch flat monthly fee only no per user pricing and no annual term workaround emulate a term with custom meters, accepting that renewal enforcement moves into your contract and application access settings are permanent publisher management and customer access cannot be changed once the offer is live workaround decide before publishing, and use a security group as the principal so you can change who has access later publishing is slow certification of template files is manual, so both first publication and every update take roughly a day workaround batch offer changes and plan releases around it updates are per customer no central push workaround automate with ci/cd and cross tenant management if you have the engineering capacity no proration on cancellation workaround none — set the expectation with the customer, and flag the 72 hour refund window deployment starts at private offer acceptance workaround do not cancel a deployment after acceptance, or the purchase button never appears and the private offer must be re created troubleshooting \ symptom \ \ likely cause \ \ fix \ package validation fails on upload wrong file names or casing, files not at the zip root, or a template that fails arm ttk confirm \ maintemplate json \ and \ createuidefinition json \ are exactly named and at the root; run arm ttk locally to see the specific failures purchase button never becomes clickable on a private offer still inside the 15–60 minute preparation window, or the deployment was cancelled after acceptance wait and refresh; if the deployment was cancelled, re initiate the private offer customer gets \ denyassignmentauthorizationfailed \ working as designed — the deny assignment blocks customer writes to the managed resource group explain the model; if the customer genuinely needs write access, that had to be configured before the offer went live publisher cannot see the deployment looking in the wrong blade use managed applications center , not the customer facing managed applications blade customer cannot find their deployment they do not remember the resource group send them to managed applications in the azure portal, which lists all of them create button missing on the deployment blade terms checkbox not ticked ask the customer to tick "i agree to the terms and conditions above" faqs how are managed applications updated? for existing customers you update the resources directly in the managed resource group for new customers you update the zip package in the plan both must be kept in sync automated update pipelines are possible, but most publishers do this manually who pays for infrastructure costs? the customer, directly through their own azure subscription — unless you configure the plan for isv billed infrastructure, in which case you do do customers have access to the application resources? it depends on your configuration the default is read only visibility enforced by deny assignments, but you can grant full access or restrict it further this cannot be changed after the offer is live is azure usage required for publishers? no the solution runs in customer environments, so you do not need azure consumption of your own how does a customer cancel? by deleting the managed application resource in their subscription azure removes the managed resource group and stops future billing the current month's fixed fee is charged in full — there is no proration a refund is only available if the application is deleted within 72 hours of purchase can i charge annually or per user? not with the standard price — only a flat monthly fee is supported term based pricing can be emulated with custom meters, with the trade offs described above how long does publishing take? around 24 hours for the initial publication, and about the same for republishing, because certification of the template files is manual why is the purchase button not appearing on my private offer? after acceptance it takes 15 to 60 minutes to become available it will also never appear if the deployment was cancelled after acceptance — in that case the private offer has to be re initiated what scenarios require managed applications? regulated industries, cybersecurity, and any solution that has to analyse or run inside the customer's own environment 💬 for more, contact us at \\