Managed Application

what is a managed application? a managed application is a microsoft marketplace offer type that deploys your solution into your customer's azure subscription , while you keep management control of the deployed resources the customer owns the subscription and pays microsoft for the infrastructure; you operate the software wetransact supports two transactable offer types saas (software as a service) managed application managed applications sit between saas (which runs entirely in your environment) and a fully customer managed deployment note a managed application is not the same as an azure application solution template both use arm (azure resource manager) templates, but only a managed application creates a locked when to use a managed application choose a managed application when your solution needs access to sensitive or regulated data that cannot leave the customer's environment — for example healthcare or financial data performs security audits, monitoring or cost analysis directly inside the customer's azure environment requires complex azure provisioning that the customer should not have to assemble themselves contains intellectual property you need to protect from inspection or modification by the customer tip default to saas saas publishes faster, updates instantly for everyone, and is simpler for both you and your customer choose a managed application only when the solution genuinely needs to run inside the customer's tenant, needs ip protection through a publisher managed resource group, or requires complex azure provisioning do not pick it "just for control" key characteristics \<font color="#f3f4f6"> aspect \</font> \<font color="#f3f4f6"> detail \</font> deployed in the customer tenant the application runs in the customer's azure subscription, which helps with compliance and data residency requirements publisher control you keep management access to the deployed resources and can operate the solution remotely ip protection by default the customer can see, but not modify or open, the resources in the managed resource group (deny assignments) automated deployment provisioning happens automatically after purchase, based on your arm template no manual publisher step updates without customer effort you apply updates, patches and new features without needing customer input pricing flat monthly fee only, optionally plus custom metered dimensions no per user and no annual term infrastructure billing charged to the customer's own azure subscription by default managed application vs saas at a glance \<font color="#f3f4f6"> saas offer \</font> \<font color="#f3f4f6"> managed application \</font> where it runs your azure subscription customer's azure subscription (managed resource group) who pays for infrastructure you (built into your price) customer, directly to microsoft pricing models flat rate, per user, custom meters; monthly or annual flat monthly fee plus optional custom meters only activation customer must land on your landing page and activate (30 day window) automatic on successful deployment, no publisher action publication time faster; updates usually reflect quickly slower; certification of the template files is manual update distribution instant for everyone (central hosting) per customer deployment, publisher managed