Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Consider an example of an application that processes files on behalf of the original equipment manufacturer (OEM) in the context of AVOps. This application reads files from a data lake, executes a data transformation task, and writes the results back to the data lake. This application is offered as a managed application and is deployed in a resource group that belongs to the customer subscription.
The application contains the following three elements:
A user interface that lets users manage and monitor the behavior of the tasks. You can implement the interface as a web application that accesses services on the orchestration layer. You can also implement it using Azure WebApp in any supported language.
An orchestration component that manages the necessary compute resources to run the processing tasks and performs billing. This component deploys processing logic packed in containers from a container registry to the processing component.
A processing component that reads and transforms the data. Depending on the complexity and nature of the tasks, the containers can be deployed in Azure Kubernetes Service (AKS), Azure Batch, or Azure Container instances.
A managed application has the following features:
The customer can install the application from the marketplace with a single click. The publisher must provide a deployment script as part of the offer.
The customer provides permissions and configuration to the application to access the data storage.
The publisher has read-only access to the resources in the managed application resource group. This access can help provide support (for example, logs). If there's maintenance or debugging, the publisher can request Just-in-Time (JIT) elevated access to the resource group.
The publisher defines custom meters for billing. Billing is activated by calling the Azure Billing API. Examples of custom metrics include price per file (unit), price per processed terabyte (TB), price per user, and price per month.