Moodle/managedApplication
Adrian Joian 3638325318
Replacing AAD with Microsoft Entra ID
2024-01-26 14:27:18 +01:00
..
Cleanup.md Replacing AAD with Microsoft Entra ID 2024-01-26 14:27:18 +01:00
DeployMoodleManagedApp.md Add example Managed Application template. (#50) 2018-03-16 13:23:34 -07:00
Environment.md Add example Managed Application template. (#50) 2018-03-16 13:23:34 -07:00
PublishMoodleManagedApplication.md Replacing AAD with Microsoft Entra ID 2024-01-26 14:27:18 +01:00
README.md Update README.md 2018-03-28 15:00:13 -07:00
createServiceCatlogUpdate.sh Change to read/write 2021-10-06 14:02:36 -07:00
createUIDefinition.json Add example Managed Application template. (#50) 2018-03-16 13:23:34 -07:00
parameters-template.json Add example Managed Application template. (#50) 2018-03-16 13:23:34 -07:00

README.md

Azure Managed Application

Azure Managed Applications enable you to offer your Moodle based solutions to customers via the Azure Marketplace or a Service Catalog. You define the infrastructure for the solution, using the ARM templates in this repository as a starting point, along with the terms for ongoing management of the solution. The billing for your solution is handled through Azure billing.

Why the Azure Marketplace and Azure Managed Applications for Moodle Hosting Providers

The Azure Marketplace allows you the capability of offering an Azure-certified Moodle solution via a modern marketplace. When a customer runs Moodle from the Azure Marketplace they have the confidence that the Moodle solution certified and optimized to run on Azure, and that they can get support should they need it.

Until recently it was difficult for many Moodle hosting providers to offer Moodle via the Azure Marketplace, in particular because after a marketplace solution was deployed, customers would still be responsible for maintaining, updating, or servicing their environment. As customers are not always experts on cloud infrastructure this made offering a Marketplace offering with a Moodle-hoster backed SLA difficult. Moreover, a customer had full-access to the resources (i.e. VMs, databases, etc.) in the solution once deployed, meaning they could easily make a change to the underlying infrastructure (such as accidentally deleting a critical VM) that might have rendered the solution unusable.

With the advent of Azure Managed Application for the Azure Marketplace, the Moodle Hosting provider can now specify exactly which underlying infrastructure resources for a Moodle solution a customer does (and does not) have access to. This means that a Moodle hoster can now prevent a customer from make a change which could take down your Moodle solution and render your SLA void. Moreover, although customers continue to deploy your Moodle solution offering in their subscriptions just like all Azure Marketplace offerings, the customer does not have to maintain, update, or service them and troubleshooting and diagnosing of issues can be done by the Moodle hoster on-behalf of the customer.

Why Moodle Managed Applications for IT Teams?

For IT teams, managed applications enable you to offer pre-approved configuration of Moodle to users in the organization. For example, if to be compliant with organizational standards you require users deploy Moodle with certain version number, database SKUs or networking/security configurations, you can enforce compliance.

Read more about Managed Applications, or keep reading here to see how to quickly get started providing your own Moodle based services as Managed Applications.

Next Steps

  1. Publish a Managed Application Definition
  2. Deploy a Moodle Based Managed Application
  3. Learn about submitting your application to the Azure Marketplace
  4. Submit your application to the Azure Marketplace