Skip main navigation

Container Environments: The Azure Container Service

This article looks at containers in Azure , container environments, and how to use the Azure Container Service.

Container Environments

Computing has shifted significantly since the days when only physical machines could be used. Virtual machines (VMs) opened up the possibility of running multiple instances on one machine with separate environments and applications.

Although VMs have revolutionised traditional and cloud computing, applications or processes that require large amounts of memory challenge the idea of scalability for machines.

What is the difference between containers and Virtual machines?

Containers have similarities to VMs because of how they can partition into multiple environments with separate drives and memory, but maintain isolation for applications.

The important difference is that containers don’t run full instances of operating systems. This means that a nearly infinite number of containers can run on one instance of the hosted operating system, enabling fast creation of new containers and the flexibility to spin up or release instances of containers.

The containers include an isolated application to be hosted with its dependencies, settings, and storage, but share the kernel with other containers. Since multiple containers are stored in one instance, they can be updated the same way so that there are clones of containers.

Instant startup and reliable execution

The combination of an instant startup that OS virtualisation provides and reliable execution that derives from isolation and resource governance makes containers ideal for application development and testing, and developers can quickly iterate. Because its environment and resource usage are consistent across systems, a containerised application that works on a developer’s system will work the same way on a production system.

The instant-start and small footprint also benefit cloud scenarios, because applications can scale out quickly and many more application instances can fit onto a machine than if they were each in a virtual machine, maximising resource utilisation.

With IaC, you can copy the environment for production as a container and deploy it anywhere with the configuration set up. With Docker, you create a Dockerfile that’s a short script of configuration information, and then run the script to orchestrate containers on machine instances.

Azure Container Service

Azure Container Service makes it simpler for you to create, configure, and manage a cluster of virtual machines that are preconfigured to run containerised applications. It uses an optimised configuration of popular open-source scheduling and orchestration tools.

This enables you to use your existing skills, or draw upon a large and growing body of community expertise, to deploy and manage container-based applications on Microsoft Azure.


Azure Container Service leverages the Docker container format to ensure that your application containers are fully portable. It also supports your choice of Marathon and DC/OS, Docker Swarm, or Kubernetes so that you can scale these applications to thousands of containers, or even tens of thousands.

By using Azure Container Service, you can take advantage of the enterprise-grade features of Azure, while still maintaining application portability, including portability at the orchestration layers.

This article is from the free online

Microsoft Future Ready: DevOps Development, Implementation and Azure Automation

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now